February 20, 2015 at 1:02 pm
Hello everybody,
i'm new to administrating sql-servers and just got thrown into the cold water. A customer has the following setup
Virtual Machine (VMware Esxi5.0)
SBS2011 with 800GB of virtual HDD-Space
Exchange 2010
SQL 2008 (10.50.1617)
Sharepoint (not used as far as i know)
400GB of Space is taken by the directory C:\Program Files\Microsoft SQL Server\MSSQL10_50.SHAREPOINT\MSSQL\Log
sqldump10000.txt is nearly 200GB big
I spend the a lot of time on google, started the download of the SQL SP3 and a figured out to make a DBCC CHECKDB {SHAREPOINT_AdminContent}. These are the results after 2 hours (when i stopped the debug-run):
Meldung 8934, Ebene 16, Status 2, Zeile 3
Tabellenfehler: Objekt-ID 1605580758, Index-ID 1, Partitions-ID 72057594041597952, Zuordnungseinheits-ID 72057594044416000 (In-row data-Typ). Der hohe Schlüsselwert auf Seite (1:2968) (Ebene 0) ist nicht kleiner als der niedrige Schlüsselwert im übergeordneten (0:1), Slot 0 der nächsten Seite (1:3657).
Meldung 8934, Ebene 16, Status 3, Zeile 3
Tabellenfehler: Objekt-ID 1605580758, Index-ID 1, Partitions-ID 72057594041597952, Zuordnungseinheits-ID 72057594044416000 (In-row data-Typ). Der hohe Schlüsselwert auf Seite (1:2968) (Ebene 0) ist nicht kleiner als der niedrige Schlüsselwert im übergeordneten (0:1), Slot 0 der nächsten Seite (1:3657).
Meldung 8935, Ebene 16, Status 1, Zeile 3
Tabellenfehler: Objekt-ID 1605580758, Index-ID 1, Partitions-ID 72057594041597952, Zuordnungseinheits-ID 72057594044416000 (In-row data-Typ). Der Vorgängerlink (1:2968) auf Seite (1:3657) stimmt nicht mit der vorherigen Seite (1:15102) überein, die das übergeordnete (1:2592)-Objekt, Slot 89, für diese Seite erwartet.
Meldung 8935, Ebene 16, Status 1, Zeile 3
Tabellenfehler: Objekt-ID 1605580758, Index-ID 1, Partitions-ID 72057594041597952, Zuordnungseinheits-ID 72057594044416000 (In-row data-Typ). Der Vorgängerlink (1:5233) auf Seite (1:5421) stimmt nicht mit der vorherigen Seite (1:2968) überein, die das übergeordnete (1:5423)-Objekt, Slot 57, für diese Seite erwartet.
Meldung 8978, Ebene 16, Status 1, Zeile 3
Tabellenfehler: Objekt-ID 1605580758, Index-ID 1, Partitions-ID 72057594041597952, Zuordnungseinheits-ID 72057594044416000 (In-row data-Typ). Für Seite (1:5421) fehlt ein Verweis der Vorgängerseite (1:5233). Möglicherweise liegt ein Kettenverknüpfungsproblem vor.
I now started a debug-run DBCC CHECKDB on SharePoint_ConfigurationDatabase.
To be honest i have no clue where to start solving this mess. As you can imagine the customer (or his old "admin") didn't check their backups, and i have nothing to restore from. I now have a couple of questions:
Do you think i can install the SP3 Update first and then see if this solves the problem, or at least makes it easier to understand and then solve it?
How can i figure out who is piling up the data in sqldump10000.txt and what is actually in this file?
Can i just stop the sharepoint sql db, move the files from the "..\Log" directory to a save location, and start the sharepoint sql db again? (For tempory space at least)
I have a lot of other files in this directory with the names: sqldumpXXX.txt, sqldumpXXX.mdmp, sqldumpXXX.log, sqldmpr.mdmp and sqldmpr.log and a couple of pretty big (up to 11GB) ERRORLOG files. The last (for me understandable) rows from the ERRORLOG are:
2015-02-20 20:45:13.01 spid13s 00000000771CF34D Module(kernel32+000000000001F34D)
2015-02-20 20:45:13.01 spid13s 0000000077402CA1 Module(ntdll+0000000000032CA1)
2015-02-20 20:45:13.05 spid13s * -------------------------------------------------------------------------------
2015-02-20 20:45:13.05 spid13s Stack Signature for the dump is 0x000000006F487C89
2015-02-20 20:45:13.15 spid13s External dump process return code 0x20000003.
Error - Failed to create dump file.
2015-02-20 20:45:21.38 spid20s ex_raise2: Exception raised, major=52, minor=42, state=9, severity=22, attempting to create symptom dump
2015-02-20 20:45:21.38 spid20s Using 'dbghelp.dll' version '4.0.5'
2015-02-20 20:45:22.98 spid20s **Dump thread - spid = 0, EC = 0x000000008A7D8B20
2015-02-20 20:45:22.98 spid20s *
2015-02-20 20:45:22.98 spid20s * User initiated stack dump. This is not a server exception dump.
2015-02-20 20:45:22.98 spid20s *
2015-02-20 20:45:22.98 spid20s ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10_50.SHAREPOINT\MSSQL\LOG\SQLDump10000.txt
2015-02-20 20:45:22.98 spid20s * *******************************************************************************
2015-02-20 20:45:22.98 spid20s *
2015-02-20 20:45:22.98 spid20s * BEGIN STACK DUMP:
2015-02-20 20:45:22.98 spid20s * 02/20/15 20:45:22 spid 20
2015-02-20 20:45:22.98 spid20s *
2015-02-20 20:45:22.98 spid20s * ex_raise2: Exception raised, major=52, minor=42, state=9, severity=22
I am at an point where i would we very happy about your general advise which steps to take next. I will google my *** of, but i'm to unexperienced with sql server.
Thanks that you took your time reading this and in advance for your thoughts 😉
Kind regards
Philip
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply