MS SQL Server :: DBCC CHECKDB Is Failing On The Msdb Database

Is It Ok To Run DBCC Checkdb On Msdb And Master?

Jun 29, 2007

Will I encounter any issues running DBCC CHECKDB on either msdb or master?

Thanks!

DBCC CHECKDB Failing

Aug 12, 2005

I am getting the following after kicking off DBCC CHECKDB 'DATABASE', REPAIR_ALLOW_DATA_LOSS) :

Executed as user: USER. Database 'TEST' consistency errors in sysobjects, sysindexes, syscolumns, or systypes prevent further CHECKDB processing. [SQLSTATE 42000] (Error 7995) Clustered index successfully restored for object 'syscolumns' in database 'TEST'. [SQLSTATE 01000] (Error 2592) DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000] (Error 2528). The step failed.

I have found this link:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_reslsyserr_2_4d2r.asp

Not good. Has anyone experianced this before.

View 7 Replies View Related

Database DBCC CHECKDB Errors

Jan 30, 2007

Hi all

I have a database that is being restored to another instance of SQL server 2000 sp4 by attatching the mdf and ldf files. I then run EXEC sp_change_users_login to sync the users. When I try to run some delete commands on the new restored database I get 'Fatal error 8908'

I then run a DBCC CHECKDB on the database and told to run it again with REPAIR_ALLOW_DATA_LOSS

I have noticed that when I create a new databse and restore a .bak over this the delete commands work.

Am I correct in thinking that I can get rid of the corruption on the original database by creating a new database then restoring a valid .bak backup on this new database.

View 3 Replies View Related

Database Problem Dbcc Checkdb

Oct 17, 2007

I've read the bad news in other post but hopefully I misunderstood them. We have a database on an old sql 2000 server which had a data drive failure. The last backup is a year old. They told me they stopped doing backups because nothing was going to change. Well, changes were made to structures and stored procedures on the production (only) server and they want to try to recover the database. Should I bother opening a support call with MS? I'm embarred to even post the question but you never know. The database is currently in emergency mode. I can't see any of the user tables or stored procedures in Mangement Studio.

Msg 8966, Level 16, State 1, Line 1

Could not read and latch page (1:17913) with latch type SH. sysobjects failed.

View 5 Replies View Related

DBCC CHECKDB And Database Maintenance Plans

Dec 14, 2000

According to the books online:

In earlier versions of SQL Server, it was recommended that DBCC statements be made a regular part of a database backup strategy.
It was recommended that databases be checked before being backed up. In SQL Server 7.0, this is no longer necessary.

Are integrity checks really no longer necessary in SQL Server 7? I have a third-party book in which the author states that he still does them
anyway. Should I continue to do DBCC CHECKDB?

Also, I am using database maintenance plans for several SQL Servers. When the integrity checks are performed will it log any errors
in the output log generated during the execution of the maintenance plan? The logs I receive look like the following:

[2] Database CPMCC_GL: Check Data and Index Linkage...

** Execution Time: 0 hrs, 39 mins, 54 secs **

If an error is detected would it be recorded here, or is this just a log to let me know that the checks were performed?

Tony

View 1 Replies View Related

Get Corrupt Database With Dbcc Checkdb Or Newalloc

Jul 8, 1999

Hi

Our supplyer of application we use say that dbcc checkdb or dbcc newalloc can
give corrupt database (use version 6.5). I wonders about this statement. Are ther some how have explanation about this

Kent vahlen

View 2 Replies View Related

DBCC CHECKDB Won't Run On Corrupted Database SQL2K

Mar 29, 2007

Let me start off by saying that under normal circumstance I would just restore from the last good backup. However in this case it appears as though the last good backup was sometime last August ... arg! After much yelling at the person responsible I've been attempting to get my blood pressure below 200 and see what data is recoverable.

First off, this was a RAID5 system that failed 1 drive. Secondly, before we got someone in there to replace said drive it failed a second drive and the system went down. We managed to massage the system back online but it appears that there is some corruption as a result which is no surprise.

I've done DB repairs in the past and it hasn't been too bad, but this time it is looking a little gnarly.

I've kicked everyone off the server and tried starting SQLServer several different ways.

I tried starting the service normally and then flagging the bad DB into single user mode with "ALTER DATABASE foo SET SINGLE_USER". I then did a select * from sysdatabases to make sure it took, which it did. I also tried starting the whole SQLServer in single user mode from the command line, "SQLServr -m".

I can run "DBCC CHECKDB('foo')" and I get a long ugly list of allocation errors. I posted it to a link as the 1349 lines returned is a little long:
http://chrisnet.net/sqlbad/dbcc_checkdb.txt

But when I attempt to bite the bullet and destroy data in an attempt to put things back together with:
"DBCC CHECKDB('foo', REPAIR_ALLOW_DATA_LOSS) WITH ALL_ERRORMSGS"
I get:
Server: Msg 7919, Level 16, State 2, Line 1
Repair statement not processed. Database needs to be in single user mode.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

But yet the database is in single user mode, according to everything I check check on. Is this just SQL's way of telling me the corruption is too severe to be repaired? No output is displayed in the shell cmd window like it is for a successful DBCC either (when running sqlservr -m).

Ideas? Or do I put a bullet through it's brain?

-Chris

View 7 Replies View Related

SQL Server 2008 :: Run DBCC CHECKDB Using Snapshot Of The Database

Dec 8, 2014

I have huge database on prod. One time I tried to run DBCC CHECKDB, it took more than a day. My question is can I created a snapshot of the prod database on the same server and run DBCC CHECKDB on the Snapshot DB? will doing this interfere production database? I don’t have option to make copy of the database on a test server and run it there.

View 9 Replies View Related

Suspect Database - DBCC CHECKDB Throws Error

Apr 13, 2007

Hi all,

we've been having this ancient database with old accounting data running in suspect mode since as long as I can remember (I started working here a year ago), and finally I had some time on my hands so I thought I'd try to get it online again. However I'm running in to problems:

DBCC CHECKDB (myDBName) gives this error:
Msg 926, Level 14, State 1, Line 1
Database 'myDBName' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.

Running sp_helpdb only does not display the suspect database and sp_helpdb 'myDBName' gives this error even though I'm a system administrator:
No permission to access database 'myDBName'.

It's possible that I might be able to dig up a backup but that would be quite tedious. Is it possible to bring the database to a state where I'm able to do a CHECKDB at least...?

--
Lumbago
"Real programmers don't document, if it was hard to write it should be hard to understand"

View 5 Replies View Related

SQL Tools :: DBCC CHECKDB Error / Internal Database Snapshot Cannot Be Created

Aug 22, 2013

We recently migrated our production server from SQL 2005 (Standard) on Win2003(32-bit) to SQL2012 (Standard; v11.0.3000) on Win2008-R2(64bit). Single-server Dell R510 with 1.2TB storage. Everything went smoothly; the only nagging issue remaining is failure of our maintenance jobs. I tracked the issue down to failure of DBCC CHECKDB. Specifically, the error is:Executed as user: NT SERVICESQLSERVERAGENT. The database could not be exclusively locked to perform the operation. [SQLSTATE 42000] (Error 5030) Check statement aborted. The database could not be checked as a database snapshot could not be created and the database or table could not be lockedI have Googled this issue and read extensively. For instance, informative blogs (albeit dated) such as these by Paul Randal (Managing

CheckDB by default takes an internal DB snapshot to get the consistent, point-in-time view of the DB that it needs. If that snapshot creation fails, then it will try to get an exclusive database lock before proceeding (same as if you had executed DBCC CHECKDB WITH TABLOCK). The root problem is not that the lock could not be obtained, it's that the internal database snapshot could not be created. msdn.microsoft.com/en-us/library/ms188796.aspx details the specific situations when an internal database snapshot is not created and table locking is attempted.

I have verified the SQLSERVERAGENT service account has full permissions on the SQLDATA directory where the databases reside and has full permissions on each database within the directory. Just for giggles, I created a job (run as SQLSERVERAGENT) that creates and then deletes a text file in the SQLDATA directory. It runs fine.

Also testedI get the snapshot creation error when manually running DBCC CHECKDB against any of our databases and when executing under a variety of administrator accounts that are members of the SQL sysadmin role and the Domain Admins security group (the Domain Admins is a member of the local Administrators group that has full permissions on all SQL directories/folders).

Additionally, the databases in question are small (200MB to 6GB) and the disk has plenty of elbow room (978GB free on 1.22TB RAID5 array) to create the internal database snapshots. CHECKDB doesn't surface an error message that is detailed enough to determine the precise cause of the error. Any example successfully running DBCC CHECKDB on the SQL2012 (Standard) on a Win2008 R2 (64-bit) server.

View 22 Replies View Related

How DBCC CHECKDB And DBCC CHECKCATALOG After Executing These Two Then Store Result

Mar 5, 2005

For Backup Database i used script
BACKUP DATABSE.

Then after that, i need to check Database inigrity, for that
i used DBCC CHECKDB and DBCC CHECKCATALOG

but, i want to store the result in a text file, after executing these two commends, how to write commend line please help me.

View 1 Replies View Related

DBCC Page / DBCC Checkdb Errors

Jan 9, 2007

Following the below topic:

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=53271

I followed the advice of Paul Randal, but Im stumped as I am not able to determin what the corruption issues are. This is SQL 2000 and the database is a Solomon database that was recently upgraded to 6.5. the error I get when running the DBCC checkdb is as follows:

Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:18645) with latch type SH. sysindexes failed.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

When I run select * from sysindexes, I get:

Server: Msg 3624, Level 20, State 1, Line 1

Location: blobman.cpp:1780
Expression: sourceLength == sizeof (TextPointer)
SPID: 53
Process ID: 256

Connection Broken

When I run dbcc page (dbname, 1, 18645, 3)
dbcc traceon(3604), It finishes with what appears to be no errors log is as follows:

PAGE: (1:18645)
---------------

BUFFER:
-------

BUF @0x0144C880
---------------
bpage = 0x681B4000 bhash = 0x00000000 bpageno = (1:18645)
bdbid = 12 breferences = 1 bstat = 0x9
bspin = 0 bnext = 0x00000000

PAGE HEADER:
------------

Page @0x681B4000
----------------
m_pageId = (1:18645) m_headerVersion = 1 m_type = 1
m_typeFlagBits = 0x0 m_level = 0 m_flagBits = 0x2
m_objId = 2 m_indexId = 0 m_prevPage = (1:505)
m_nextPage = (1:213) pminlen = 82 m_slotCnt = 16
m_freeCnt = 3988 m_freeData = 5796 m_reservedCnt = 0
m_lsn = (42700:4549:10) m_xactReserved = 0 m_xdesId = (0:2539719)
m_ghostRecCnt = 0 m_tornBits = 0

Allocation Status
-----------------
GAM (1:2) = ALLOCATED SGAM (1:3) = NOT ALLOCATED
PFS (1:16176) = 0x40 ALLOCATED 0_PCT_FULL DIFF (1:6) = CHANGED
ML (1:7) = NOT MIN_LOGGED

Slot 0 Offset 0xf8c
-------------------
Record Type = PRIMARY_RECORD
Record Attributes = NULL_BITMAP VARIABLE_COLUMNS
681B4F8C: 00520030 013f142a 00004012 00000000 0.R.*.?..@......
681B4F9C: 00010000 00000000 02600000 00010001 ..........`.....
681B4FAC: 00000000 00000000 00000000 00000000 ................
681B4FBC: 00000000 00000000 027a0000 00000022 ..........z."...
681B4FCC: 00000000 00000000 00000000 00000000 ................
681B4FDC: 001b0000 00000000 00800003 80a60096 ................
681B4FEC: 00af03af 0000000a 3400d008 00000000 ...........4....
681B4FFC: 0001000a 00000000 00010016 00000000 ................
681B500C: 006d0073 006e0049 00420076 00740061 s.m.I.n.v.B.a.t.
681B501C: 00680063 00000030 002a869d 00570000 c.h.0.....*...W.
681B502C: 00010000 0007 ......
id = 20911146
status = 16402
first = 0
indid = 1
root = 0
minlen = 608
keycnt = 1
groupid = 1
dpages = 0
reserved = 0
used = 0
rowcnt = 0
rowmodctr = 0
reserved3 = 0
reserved4 = 0
xmaxlen = 634
maxirow = 34
OrigFillFactor = 0
StatVersion = 0
reserved2 = 0
FirstIAM = 0
impid = 0
lockflags = 0
pgmodctr = 0

keys
--------------------------------
681B4FEC: 00af03af 0000000a 3400d008 00000000 ...........4....
681B4FFC: 0001000a 00000000 00010016 00000000 ................
name = smInvBatch0

statblob = [TextPointer]
------------------------------------------------
TextTimeStamp = 182647062528 RowId = (1:87:7)

Slot 1 Offset 0x12c4
--------------------
Record Type = PRIMARY_RECORD
Record Attributes = NULL_BITMAP VARIABLE_COLUMNS
681B52C4: 00520030 013f142a 00000000 00000000 0.R.*.?.........
681B52D4: 00020000 00000000 00150000 00010003 ................
681B52E4: 00000000 00000000 00000000 00000000 ................
681B52F4: 00000000 00000000 00260000 0000002c ..........&.,...
681B5304: 00000000 00000000 00000000 00000000 ................
681B5314: 001b0000 00000000 00c00003 80e600d6 ................
681B5324: 00af03af 0000000a 3400d008 00000000 ...........4....
681B5334: 00010016 00000000 00010072 00000000 ........r.......
681B5344: 00af03af 0000000a 3400d008 00000000 ...........4....
681B5354: 000b000a 00000000 000b0016 00000000 ................
681B5364: 00af03af 0000000a 3400d008 00000000 ...........4....
681B5374: 000b000a 00000000 00010016 00030000 ................
681B5384: 006d0073 006e0049 00420076 00740061 s.m.I.n.v.B.a.t.
681B5394: 00680063 00000031 002a869f 00570000 c.h.1.....*...W.
681B53A4: 00010000 0008 ......
id = 20911146
status = 0
first = 0
indid = 2
root = 0
minlen = 21
keycnt = 3
groupid = 1
dpages = 0
reserved = 0
used = 0
rowcnt = 0
rowmodctr = 0
reserved3 = 0
reserved4 = 0
xmaxlen = 38
maxirow = 44
OrigFillFactor = 0
StatVersion = 0
reserved2 = 0
FirstIAM = 0
impid = 0
lockflags = 0
pgmodctr = 0

keys
--------------------------------
681B5324: 00af03af 0000000a 3400d008 00000000 ...........4....
681B5334: 00010016 00000000 00010072 00000000 ........r.......
681B5344: 00af03af 0000000a 3400d008 00000000 ...........4....
681B5354: 000b000a 00000000 000b0016 00000000 ................
681B5364: 00af03af 0000000a 3400d008 00000000 ...........4....
681B5374: 000b000a 00000000 00010016 00030000 ................
name = smInvBatch1

statblob = [TextPointer]
------------------------------------------------
TextTimeStamp = 182647193600 RowId = (1:87:8)

Slot 2 Offset 0x1440
--------------------
Record Type = PRIMARY_RECORD
Record Attributes = NULL_BITMAP VARIABLE_COLUMNS
681B5440: 00520030 01584911 00004012 000000c6 0.R..IX..@......
681B5450: 00010001 00000095 09a20001 00010001 ................
681B5460: 00000001 00000005 00000005 00000000 ................
681B5470: 00000000 00000003 09ba0000 0000001a ................
681B5480: 00000000 00000096 00000001 00000000 ................
681B5490: 001b0000 00000000 00800003 80a60096 ................
681B54A0: 00340134 00050002 00000000 00000000 4.4.............
681B54B0: 00010020 00000000 000102c1 00000000 ...............
681B54C0: 00700052 00520074 006e0075 00690074 R.p.t.R.u.n.t.i.
681B54D0: 0065006d 00000030 002a87a9 03a00000 m.e.0.....*.....
681B54E0: 00010000 0019 ......
id = 22563089
status = 16402
first = 0
indid = 1
root = 0
minlen = 2466
keycnt = 1
groupid = 1
dpages = 1
reserved = 5
used = 5
rowcnt = 0
rowmodctr = 3
reserved3 = 0
reserved4 = 0
xmaxlen = 2490
maxirow = 26
OrigFillFactor = 0
StatVersion = 0
reserved2 = 0
FirstIAM = 0
impid = 0
lockflags = 0
pgmodctr = 0

keys
--------------------------------
681B54A0: 00340134 00050002 00000000 00000000 4.4.............
681B54B0: 00010020 00000000 000102c1 00000000 ...............
name = RptRuntime0

statblob = [TextPointer]
------------------------------------------------
TextTimeStamp = 182664626176 RowId = (1:928:25)

Slot 3 Offset 0x15bc
--------------------
Record Type = PRIMARY_RECORD
Record Attributes = NULL_BITMAP VARIABLE_COLUMNS
681B55BC: 00520030 01584911 00000000 000000e6 0.R..IX.........
681B55CC: 00020001 000000e6 00470001 00010003 ..........G.....
681B55DC: 00000001 00000002 00000002 00000000 ................
681B55EC: 00000000 00000000 00580000 0000005e ..........X.^...
681B55FC: 00000000 00000161 00000001 00000000 ....a...........
681B560C: 001b0000 00000000 00c00003 80e600d6 ................
681B561C: 00af03af 00000015 3400d008 00000000 ...........4....
681B562C: 00010008 00000000 0001004b 00000000 ........K.......
681B563C: 00af03af 0000002f 3400d008 00000000 ..../......4....
681B564C: 0016003f 00000000 0016096b 00000000 ?.......k.......
681B565C: 00340134 00050002 00000000 00000000 4.4.............
681B566C: 00450020 00000000 000102c1 00010000 .E.............
681B567C: 00700052 00520074 006e0075 00690074 R.p.t.R.u.n.t.i.
681B568C: 0065006d 00000031 002a87ab 3eb70000 m.e.1.....*....>
681B569C: 00010000 0004 ......
id = 22563089
status = 0
first = 0
indid = 2
root = 0
minlen = 71
keycnt = 3
groupid = 1
dpages = 1
reserved = 2
used = 2
rowcnt = 0
rowmodctr = 0
reserved3 = 0
reserved4 = 0
xmaxlen = 88
maxirow = 94
OrigFillFactor = 0
StatVersion = 0
reserved2 = 0
FirstIAM = 0
impid = 0
lockflags = 0
pgmodctr = 0

keys
--------------------------------
681B561C: 00af03af 00000015 3400d008 00000000 ...........4....
681B562C: 00010008 00000000 0001004b 00000000 ........K.......
681B563C: 00af03af 0000002f 3400d008 00000000 ..../......4....
681B564C: 0016003f 00000000 0016096b 00000000 ?.......k.......
681B565C: 00340134 00050002 00000000 00000000 4.4.............
681B566C: 00450020 00000000 000102c1 00010000 .E.............
name = RptRuntime1

statblob = [TextPointer]
------------------------------------------------
TextTimeStamp = 182664757248 RowId = (1:16055:4)

Slot 4 Offset 0xc04
-------------------
Record Type = PRIMARY_RECORD
Record Attributes = NULL_BITMAP VARIABLE_COLUMNS
681B4C04: 00520030 0175b502 00004012 00000000 0.R...u..@......
681B4C14: 00010000 00000000 040c0000 00010001 ................
681B4C24: 00000000 00000000 00000000 00000000 ................
681B4C34: 00000000 00000000 04270000 00000022 ..........'."...
681B4C44: 00000000 00000000 00000000 00000000 ................
681B4C54: 001b0000 00000000 00800003 80a60096 ................
681B4C64: 00af03af 0000000a 3400d008 00000000 ...........4....
681B4C74: 0001004e 00000000 000103e6 00000000 N...............
681B4C84: 006f0057 006b0072 00650043 0074006e W.o.r.k.C.e.n.t.
681B4C94: 00720065 00000030 002a84b7 55880000 e.r.0.....*....U
681B4CA4: 00010000 0007 ......
id = 24491266
status = 16402
first = 0
indid = 1
root = 0
minlen = 1036
keycnt = 1
groupid = 1
dpages = 0
reserved = 0
used = 0
rowcnt = 0
rowmodctr = 0
reserved3 = 0
reserved4 = 0
xmaxlen = 1063
maxirow = 34
OrigFillFactor = 0
StatVersion = 0
reserved2 = 0
FirstIAM = 0
impid = 0
lockflags = 0
pgmodctr = 0

keys
--------------------------------
681B4C64: 00af03af 0000000a 3400d008 00000000 ...........4....
681B4C74: 0001004e 00000000 000103e6 00000000 N...............
name = WorkCenter0

statblob = [TextPointer]
------------------------------------------------
TextTimeStamp = 182615212032 RowId = (1:21896:7)

Slot 5 Offset 0xb64
-------------------
Record Type = PRIMARY_RECORD
Record Attributes = NULL_BITMAP VARIABLE_COLUMNS
681B4B64: 00520030 01ab548a 00004012 00000000 0.R..T...@......
681B4B74: 00010000 00000000 038e0000 00010001 ................
681B4B84: 00000000 00000000 00000000 00000000 ................
681B4B94: 00000000 00000000 03b00000 0000001a ................
681B4BA4: 00000000 00000000 00000000 00000000 ................
681B4BB4: 001b0000 00000000 00800003 80a00090 ................
681B4BC4: 00af03af 00000002 3400d008 00000000 ...........4....
681B4BD4: 0001007b 00000000 000102bb 00000000 {...............
681B4BE4: 004f0053 00650053 00750074 00300070 S.O.S.e.t.u.p.0.
681B4BF4: 84010000 0000002a 00000f23 00070001 ....*...#.......
id = 28005514
status = 16402
first = 0
indid = 1
root = 0
minlen = 910
keycnt = 1
groupid = 1
dpages = 0
reserved = 0
used = 0
rowcnt = 0
rowmodctr = 0
reserved3 = 0
reserved4 = 0
xmaxlen = 944
maxirow = 26
OrigFillFactor = 0
StatVersion = 0
reserved2 = 0
FirstIAM = 0
impid = 0
lockflags = 0
pgmodctr = 0

keys
--------------------------------
681B4BC4: 00af03af 00000002 3400d008 00000000 ...........4....
681B4BD4: 0001007b 00000000 000102bb 00000000 {...............
name = SOSetup0

statblob = [TextPointer]
------------------------------------------------
TextTimeStamp = 182603284480 RowId = (1:3875:7)

Slot 6 Offset 0x58c
-------------------
Record Type = PRIMARY_RECORD
Record Attributes = NULL_BITMAP VARIABLE_COLUMNS
681B458C: 00520030 01c4f563 00004012 00000000 0.R.c....@......
681B459C: 00010000 00000000 04c70000 00010002 ................
681B45AC: 00000000 00000000 00000000 00000000 ................
681B45BC: 00000000 00000000 04e80000 00000027 ............'...
681B45CC: 00000000 00000000 00000000 00000000 ................
681B45DC: 001b0000 00000000 00a00003 80c400b4 ................
681B45EC: 00af03af 0000000a 3400d008 00000000 ...........4....
681B45FC: 00010034 00000000 0001016e 00000000 4.......n.......
681B460C: 00af03af 00000005 3400d008 00000000 ...........4....
681B461C: 000b002a 00000000 000b0135 00000000 *.......5.......
681B462C: 00750050 004f0072 00640072 00650044 P.u.r.O.r.d.D.e.
681B463C: 00300074 82fd0000 0000002a 0000068a t.0.....*.......
681B464C: 00490001 ..I.
id = 29685091
status = 16402
first = 0
indid = 1
root = 0
minlen = 1223
keycnt = 2
groupid = 1
dpages = 0
reserved = 0
used = 0
rowcnt = 0
rowmodctr = 0
reserved3 = 0
reserved4 = 0
xmaxlen = 1256
maxirow = 39
OrigFillFactor = 0
StatVersion = 0
reserved2 = 0
FirstIAM = 0
impid = 0
lockflags = 0
pgmodctr = 0

keys
--------------------------------
681B45EC: 00af03af 0000000a 3400d008 00000000 ...........4....
681B45FC: 00010034 00000000 0001016e 00000000 4.......n.......
681B460C: 00af03af 00000005 3400d008 00000000 ...........4....
681B461C: 000b002a 00000000 000b0135 00000000 *.......5.......
name = PurOrdDet0

statblob = [TextPointer]
------------------------------------------------
TextTimeStamp = 182586245120 RowId = (1:1674:73)

Slot 7 Offset 0x650
-------------------
Record Type = PRIMARY_RECORD
Record Attributes = NULL_BITMAP VARIABLE_COLUMNS
681B4650: 00520030 01c4f563 00000000 00000000 0.R.c...........
681B4660: 00020000 00000000 002e0000 00010003 ................
681B4670: 00000000 00000000 00000000 00000000 ................
681B4680: 00000000 00000000 003f0000 00000045 ..........?.E...
681B4690: 00000000 00000000 00000000 00000000 ................
681B46A0: 001b0000 00000000 00c00003 80e400d4 ................
681B46B0: 00af03af 0000001e 3400d008 00000000 ...........4....
681B46C0: 00010024 00000000 00010109 00000000 $...............
681B46D0: 00af03af 0000000a 3400d008 00000000 ...........4....
681B46E0: 001f0034 00000000 0001016e 00010000 4.......n.......
681B46F0: 00af03af 00000005 3400d008 00000000 ...........4....
681B4700: 0029002a 00000000 000b0135 00010000 *.).....5.......
681B4710: 00750050 004f0072 00640072 00650044 P.u.r.O.r.d.D.e.
681B4720: 00310074 83040000 0000002a 0000068a t.1.....*.......
681B4730: 004a0001 ..J.
id = 29685091
status = 0
first = 0
indid = 2
root = 0
minlen = 46
keycnt = 3
groupid = 1
dpages = 0
reserved = 0
used = 0
rowcnt = 0
rowmodctr = 0
reserved3 = 0
reserved4 = 0
xmaxlen = 63
maxirow = 69
OrigFillFactor = 0
StatVersion = 0
reserved2 = 0
FirstIAM = 0
impid = 0
lockflags = 0
pgmodctr = 0

keys
--------------------------------
681B46B0: 00af03af 0000001e 3400d008 00000000 ...........4....
681B46C0: 00010024 00000000 00010109 00000000 $...............
681B46D0: 00af03af 0000000a 3400d008 00000000 ...........4....
681B46E0: 001f0034 00000000 0001016e 00010000 4.......n.......
681B46F0: 00af03af 00000005 3400d008 00000000 ...........4....
681B4700: 0029002a 00000000 000b0135 00010000 *.).....5.......
name = PurOrdDet1

statblob = [TextPointer]
------------------------------------------------
TextTimeStamp = 182586703872 RowId = (1:1674:74)

Slot 8 Offset 0x734
-------------------
Record Type = PRIMARY_RECORD
Record Attributes = NULL_BITMAP VARIABLE_COLUMNS
681B4734: 00520030 01c4f563 00000000 00000000 0.R.c...........
681B4744: 00030000 00000000 00340000 00010004 ..........4.....
681B4754: 00000000 00000000 00000000 00000000 ................
681B4764: 00000000 00000000 00450000 0000004b ..........E.K...
681B4774: 00000000 00000000 00000000 00000000 ................
681B4784: 001b0000 00000000 00e00003 810400f4 ................
681B4794: 00af03af 00000006 3400d008 00000000 ...........4....
681B47A4: 00010044 00000000 000101ea 00000000 D...............
681B47B4: 00af03af 0000001e 3400d008 00000000 ...........4....
681B47C4: 00070024 00000000 00070109 00000000 $...............
681B47D4: 00af03af 0000000a 3400d008 00000000 ...........4....
681B47E4: 00250034 00000000 0001016e 00010000 4.%.....n.......
681B47F4: 00af03af 00000005 3400d008 00000000 ...........4....
681B4804: 002f002a 00000000 000b0135 00010000 *./.....5.......
681B4814: 00750050 004f0072 00640072 00650044 P.u.r.O.r.d.D.e.
681B4824: 00320074 83050000 0000002a 0000068a t.2.....*.......
681B4834: 004b0001 ..K.
id = 29685091
status = 0
first = 0
indid = 3
root = 0
minlen = 52
keycnt = 4
groupid = 1
dpages = 0
reserved = 0
used = 0
rowcnt = 0
rowmodctr = 0
reserved3 = 0
reserved4 = 0
xmaxlen = 69
maxirow = 75
OrigFillFactor = 0
StatVersion = 0
reserved2 = 0
FirstIAM = 0
impid = 0
lockflags = 0
pgmodctr = 0

keys
--------------------------------
681B4794: 00af03af 00000006 3400d008 00000000 ...........4....
681B47A4: 00010044 00000000 000101ea 00000000 D...............
681B47B4: 00af03af 0000001e 3400d008 00000000 ...........4....
681B47C4: 00070024 00000000 00070109 00000000 $...............
681B47D4: 00af03af 0000000a 3400d008 00000000 ...........4....
681B47E4: 00250034 00000000 0001016e 00010000 4.%.....n.......
681B47F4: 00af03af 00000005 3400d008 00000000 ...........4....
681B4804: 002f002a 00000000 000b0135 00010000 *./.....5.......
name = PurOrdDet2

statblob = [TextPointer]
------------------------------------------------
TextTimeStamp = 182586769408 RowId = (1:1674:75)

Slot 9 Offset 0x838
-------------------
Record Type = PRIMARY_RECORD
Record Attributes = NULL_BITMAP VARIABLE_COLUMNS
681B4838: 00520030 01c4f563 00000000 00000000 0.R.c...........
681B4848: 00040000 00000000 00120000 00010005 ................
681B4858: 00000000 00000000 00000000 00000000 ................
681B4868: 00000000 00000000 00230000 00000029 ..........#.)...
681B4878: 00000000 00000000 00000000 00000000 ................
681B4888: 001b0000 00000000 01000003 81240114 ..............$.
681B4898: 00af03af 0000000a 3400d008 00000000 ...........4....
681B48A8: 00010034 00000000 0001016e 00000000 4.......n.......
681B48B8: 00af03af 00000005 3400d008 00000000 ...........4....
681B48C8: 000b002a 00000000 000b0135 00000000 *.......5.......
681B48D8: 00340134 00050002 00000000 00000000 4.4.............
681B48E8: 00100029 00000000 00100133 00000000 ).......3.......
681B48F8: 00af03af 0000000a 3400d008 00000000 ...........4....
681B4908: 00010034 00000000 0001016e 00030000 4.......n.......
681B4918: 00af03af 00000005 3400d008 00000000 ...........4....
681B4928: 000b002a 00000000 000b0135 00030000 *.......5.......
681B4938: 00750050 004f0072 00640072 00650044 P.u.r.O.r.d.D.e.
681B4948: 00330074 83060000 0000002a 0000068a t.3.....*.......
681B4958: 004c0001 ..L.
id = 29685091
status = 0
first = 0
indid = 4
root = 0
minlen = 18
keycnt = 5
groupid = 1
dpages = 0
reserved = 0
used = 0
rowcnt = 0
rowmodctr = 0
reserved3 = 0
reserved4 = 0
xmaxlen = 35
maxirow = 41
OrigFillFactor = 0
StatVersion = 0
reserved2 = 0
FirstIAM = 0
impid = 0
lockflags = 0
pgmodctr = 0

keys
--------------------------------
681B4898: 00af03af 0000000a 3400d008 00000000 ...........4....
681B48A8: 00010034 00000000 0001016e 00000000 4.......n.......
681B48B8: 00af03af 00000005 3400d008 00000000 ...........4....
681B48C8: 000b002a 00000000 000b0135 00000000 *.......5.......
681B48D8: 00340134 00050002 00000000 00000000 4.4.............
681B48E8: 00100029 00000000 00100133 00000000 ).......3.......
681B48F8: 00af03af 0000000a 3400d008 00000000 ...........4....
681B4908: 00010034 00000000 0001016e 00030000 4.......n.......
681B4918: 00af03af 00000005 3400d008 00000000 ...........4....
681B4928: 000b002a 00000000 000b0135 00030000 *.......5.......
name = PurOrdDet3

statblob = [TextPointer]
------------------------------------------------
TextTimeStamp = 182586834944 RowId = (1:1674:76)

Slot 10 Offset 0x95c
--------------------
Record Type = PRIMARY_RECORD
Record Attributes = NULL_BITMAP VARIABLE_COLUMNS
681B495C: 00520030 01c4f563 00000000 00000000 0.R.c...........
681B496C: 00050000 00000000 003a0000 00010005 ..........:.....
681B497C: 00000000 00000000 00000000 00000000 ................
681B498C: 00000000 00000000 004b0000 00000051 ..........K.Q...
681B499C: 00000000 00000000 00000000 00000000 ................
681B49AC: 001b0000 00000000 01000003 81240114 ..............$.
681B49BC: 00af03af 0000001e 3400d008 00000000 ...........4....
681B49CC: 00010024 00000000 00010109 00000000 $...............
681B49DC: 00af03af 0000000a 3400d008 00000000 ...........4....
681B49EC: 001f005e 00000000 001f032b 00000000 ^.......+.......
681B49FC: 00340134 00050002 00000000 00000000 4.4.............
681B4A0C: 0029002f 00000000 00290154 00000000 /.).....T.).....
681B4A1C: 00af03af 0000000a 3400d008 00000000 ...........4....
681B4A2C: 002b0034 00000000 0001016e 00010000 4.+.....n.......
681B4A3C: 00af03af 00000005 3400d008 00000000 ...........4....
681B4A4C: 0035002a 00000000 000b0135 00010000 *.5.....5.......
681B4A5C: 00750050 004f0072 00640072 00650044 P.u.r.O.r.d.D.e.
681B4A6C: 00340074 83070000 0000002a 0000068a t.4.....*.......
681B4A7C: 004d0001 ..M.
id = 29685091
status = 0
first = 0
indid = 5
root = 0
minlen = 58
keycnt = 5
groupid = 1
dpages = 0
reserved = 0
used = 0
rowcnt = 0
rowmodctr = 0
reserved3 = 0
reserved4 = 0
xmaxlen = 75
maxirow = 81
OrigFillFactor = 0
StatVersion = 0
reserved2 = 0
FirstIAM = 0
impid = 0
lockflags = 0
pgmodctr = 0

keys
--------------------------------
681B49BC: 00af03af 0000001e 3400d008 00000000 ...........4....
681B49CC: 00010024 00000000 00010109 00000000 $...............
681B49DC: 00af03af 0000000a 3400d008 00000000 ...........4....
681B49EC: 001f005e 00000000 001f032b 00000000 ^.......+.......
681B49FC: 00340134 00050002 00000000 00000000 4.4.............
681B4A0C: 0029002f 00000000 00290154 00000000 /.).....T.).....
681B4A1C: 00af03af 0000000a 3400d008 00000000 ...........4....
681B4A2C: 002b0034 00000000 0001016e 00010000 4.+.....n.......
681B4A3C: 00af03af 00000005 3400d008 00000000 ...........4....
681B4A4C: 0035002a 00000000 000b0135 00010000 *.5.....5.......
name = PurOrdDet4

statblob = [TextPointer]
------------------------------------------------
TextTimeStamp = 182586900480 RowId = (1:1674:77)

Slot 11 Offset 0xa80
--------------------
Record Type = PRIMARY_RECORD
Record Attributes = NULL_BITMAP VARIABLE_COLUMNS
681B4A80: 00520030 01c4f563 00000000 00000000 0.R.c...........
681B4A90: 00060000 00000000 00200000 00010003 .......... .....
681B4AA0: 00000000 00000000 00000000 00000000 ................
681B4AB0: 00000000 00000000 00310000 00000037 ..........1.7...
681B4AC0: 00000000 00000000 00000000 00000000 ................
681B4AD0: 001b0000 00000000 00c00003 80e400d4 ................
681B4AE0: 00af03af 00000010 3400d008 00000000 ...........4....
681B4AF0: 00010036 00000000 0001017a 00000000 6.......z.......
681B4B00: 00af03af 0000000a 3400d008 00000000 ...........4....
681B4B10: 00110034 00000000 0001016e 00010000 4.......n.......
681B4B20: 00af03af 00000005 3400d008 00000000 ...........4....
681B4B30: 001b002a 00000000 000b0135 00010000 *.......5.......
681B4B40: 00750050 004f0072 00640072 00650044 P.u.r.O.r.d.D.e.
681B4B50: 00350074 83080000 0000002a 0000068a t.5.....*.......
681B4B60: 004e0001 ..N.
id = 29685091
status = 0
first = 0
indid = 6
root = 0
minlen = 32
keycnt = 3
groupid = 1
dpages = 0
reserved = 0
used = 0
rowcnt = 0
rowmodctr = 0
reserved3 = 0
reserved4 = 0
xmaxlen = 49
maxirow = 55
OrigFillFactor = 0
StatVersion = 0
reserved2 = 0
FirstIAM = 0
impid = 0
lockflags = 0
pgmodctr = 0

keys
--------------------------------
681B4AE0: 00af03af 00000010 3400d008 00000000 ...........4....
681B4AF0: 00010036 00000000 0001017a 00000000 6.......z.......
681B4B00: 00af03af 0000000a 3400d008 00000000 ...........4....
681B4B10: 00110034 00000000 0001016e 00010000 4.......n.......
681B4B20: 00af03af 00000005 3400d008 00000000 ...........4....
681B4B30: 001b002a 00000000 000b0135 00010000 *.......5.......
name = PurOrdDet5

statblob = [TextPointer]
------------------------------------------------
TextTimeStamp = 182586966016 RowId = (1:1674:78)

Slot 12 Offset 0xcac
--------------------
Record Type = PRIMARY_RECORD
Record Attributes = NULL_BITMAP VARIABLE_COLUMNS
681B4CAC: 00520030 01c4f563 00000000 00000000 0.R.c...........
681B4CBC: 00070000 00000000 00110000 00010003 ................
681B4CCC: 00000000 00000000 00000000 00000000 ................
681B4CDC: 00000000 00000000 00220000 00000028 ..........".(...
681B4CEC: 00000000 00000000 00000000 00000000 ................
681B4CFC: 001b0000 00000000 00c00003 80ee00de ................
681B4D0C: 00af03af 00000001 3400d008 00000000 ...........4....
681B4D1C: 00010033 00000000 0001016d 00000000 3.......m.......
681B4D2C: 00af03af 0000000a 3400d008 00000000 ...........4....
681B4D3C: 00020034 00000000 0001016e 00010000 4.......n.......
681B4D4C: 00af03af 00000005 3400d008 00000000 ...........4....
681B4D5C: 000c002a 00000000 000b0135 00010000 *.......5.......
681B4D6C: 00750070 006f0072 00640072 00650064 p.u.r.o.r.d.d.e.
681B4D7C: 005f0074 00740073 00610072 0000006e t._.s.t.r.a.n...
681B4D8C: 002a84c7 78450000 00010000 001d ..*...Ex......
id = 29685091
status = 0
first = 0
indid = 7
root = 0
minlen = 17
keycnt = 3
groupid = 1
dpages = 0
reserved = 0
used = 0
rowcnt = 0
rowmodctr = 0
reserved3 = 0
reserved4 = 0
xmaxlen = 34
maxirow = 40
OrigFillFactor = 0
StatVersion = 0
reserved2 = 0
FirstIAM = 0
impid = 0
lockflags = 0
pgmodctr = 0

keys
--------------------------------
681B4D0C: 00af03af 00000001 3400d008 00000000 ...........4....
681B4D1C: 00010033 00000000 0001016d 00000000 3.......m.......
681B4D2C: 00af03af 0000000a 3400d008 00000000 ...........4....
681B4D3C: 00020034 00000000 0001016e 00010000 4.......n.......
681B4D4C: 00af03af 00000005 3400d008 00000000 ...........4....
681B4D5C: 000c002a 00000000 000b0135 00010000 *.......5.......
name = purorddet_stran

statblob = [TextPointer]
------------------------------------------------
TextTimeStamp = 182616260608 RowId = (1:30789:29)

Slot 13 Offset 0xd4
-------------------
Record Type = PRIMARY_RECORD
Record Attributes = NULL_BITMAP VARIABLE_COLUMNS
681B40D4: 00520030 01d345b0 00004012 00000000 0.R..E...@......
681B40E4: 00010000 00000000 019b0000 00010006 ................
681B40F4: 00000000 00000000 00000000 00000000 ................
681B4104: 00000000 00000000 01b00000 0000007b ............{...
681B4114: 00000000 00000000 00000000 00000000 ................
681B4124: 001b0000 00000000 01200003 81460136 .......... .6.F.
681B4134: 00af03af 0000001e 3400d008 00000000 ...........4....
681B4144: 00010008 00000000 00010041 00000000 ........A.......
681B4154: 00af03af 00000004 3400d008 00000000 ...........4....
681B4164: 001f0007 00000000 001f003d 00000000 ........=.......
681B4174: 00af03af 0000001e 3400d008 00000000 ...........4....
681B4184: 00230010 00000000 00230084 00000000 ..#.......#.....
681B4194: 00af03af 00000001 3400d008 00000000 ...........4....
681B41A4: 00410006 00000000 0041003c 00000000 ..A.....<.A.....
681B41B4: 00af03af 00000004 3400d008 00000000 ...........4....
681B41C4: 00420004 00000000 0042001a 00000000 ..B.......B.....
681B41D4: 00af03af 0000001e 3400d008 00000000 ...........4....
681B41E4: 00460005 00000000 0046001e 00000000 ..F.......F.....
681B41F4: 0070004f 00440074 00700065 00780045 O.p.t.D.e.p.E.x.
681B4204: 006c0063 00000030 002a8221 4d150000 c.l.0...!.*....M
681B4214: 00010000 003f ....?.
id = 30623152
status = 16402
first = 0
indid = 1
root = 0
minlen = 411
keycnt = 6
groupid = 1
dpages = 0
reserved = 0
used = 0
rowcnt = 0
rowmodctr = 0
reserved3 = 0
reserved4 = 0
xmaxlen = 432
maxirow = 123
OrigFillFactor = 0
StatVersion = 0
reserved2 = 0
FirstIAM = 0
impid = 0
lockflags = 0
pgmodctr = 0

keys
--------------------------------
681B4134: 00af03af 0000001e 3400d008 00000000 ...........4....
681B4144: 00010008 00000000 00010041 00000000 ........A.......
681B4154: 00af03af 00000004 3400d008 00000000 ...........4....
681B4164: 001f0007 00000000 001f003d 00000000 ........=.......
681B4174: 00af03af 0000001e 3400d008 00000000 ...........4....
681B4184: 00230010 00000000 00230084 00000000 ..#.......#.....
681B4194: 00af03af 00000001 3400d008 00000000 ...........4....
681B41A4: 00410006 00000000 0041003c 00000000 ..A.....<.A.....
681B41B4: 00af03af 00000004 3400d008 00000000 ...........4....
681B41C4: 00420004 00000000 0042001a 00000000 ..B.......B.....
681B41D4: 00af03af 0000001e 3400d008 00000000 ...........4....
681B41E4: 00460005 00000000 0046001e 00000000 ..F.......F.....
name = OptDepExcl0

statblob = [TextPointer]
------------------------------------------------
TextTimeStamp = 182571827200 RowId = (1:19733:63)

Slot 14 Offset 0x21c
--------------------
Record Type = PRIMARY_RECORD
Record Attributes = NULL_BITMAP VARIABLE_COLUMNS
681B421C: 00520030 01d345b0 00000000 00000000 0.R..E..........
681B422C: 00020000 00000000 00640000 00010008 ..........d.....
681B423C: 00000000 00000000 00000000 00000000 ................
681B424C: 00000000 00000000 00750000 0000007b ..........u.{...
681B425C: 00000000 00000000 00000000 00000000 ................
681B426C: 001b0000 00000000 01600003 81860176 ..........`.v...
681B427C: 00af03af 0000001e 3400d008 00000000 ...........4....
681B428C: 00010005 00000000 0001001e 00000000 ................
681B429C: 00af03af 00000004 3400d008 00000000 ...........4....
681B42AC: 001f0004 00000000 001f001a 00000000 ................
681B42BC: 00af03af 0000001e 3400d008 00000000 ...........4....
681B42CC: 00230008 00000000 00010041 00010000 ..#.....A.......
681B42DC: 00af03af 00000004 3400d008 00000000 ...........4....
681B42EC: 00410007 00000000 001f003d 00010000 ..A.....=.......
681B42FC: 00af03af 0000001e 3400d008 00000000 ...........4....
681B430C: 00450010 00000000 00230084 00010000 ..E.......#.....
681B431C: 00af03af 00000001 3400d008 00000000 ...........4....
681B432C: 00630006 00000000 0041003c 00010000 ..c.....<.A.....
681B433C: 00af03af 00000004 3400d008 00000000 ...........4....
681B434C: 001f0004 00000000 0042001a 00030000 ..........B.....
681B435C: 00af03af 0000001e 3400d008 00000000 ...........4....
681B436C: 00010005 00000000 0046001e 00030000 ..........F.....
681B437C: 0070004f 00440074 00700065 00780045 O.p.t.D.e.p.E.x.
681B438C: 006c0063 00000031 002a8224 4d150000 c.l.1...$.*....M
681B439C: 00010000 0040 ....@.
id = 30623152
status = 0
first = 0
indid = 2
root = 0
minlen = 100
keycnt = 8
groupid = 1
dpages = 0
reserved = 0
used = 0
rowcnt = 0
rowmodctr = 0
reserved3 = 0
reserved4 = 0
xmaxlen = 117
maxirow = 123
OrigFillFactor = 0
StatVersion = 0
reserved2 = 0
FirstIAM = 0
impid = 0
lockflags = 0
pgmodctr = 0

keys
--------------------------------
681B427C: 00af03af 0000001e 3400d008 00000000 ...........4....
681B428C: 00010005 00000000 0001001e 00000000 ................
681B429C: 00af03af 00000004 3400d008 00000000 ...........4....
681B42AC: 001f0004 00000000 001f001a 00000000 ................
681B42BC: 00af03af 0000001e 3400d008 00000000 ...........4....
681B42CC: 00230008 00000000 00010041 00010000 ..#.....A.......
681B42DC: 00af03af 00000004 3400d008 00000000 ...........4....
681B42EC: 00410007 00000000 001f003d 00010000 ..A.....=.......
681B42FC: 00af03af 0000001e 3400d008 00000000 ...........4....
681B430C: 00450010 00000000 00230084 00010000 ..E.......#.....
681B431C: 00af03af 00000001 3400d008 00000000 ...........4....
681B432C: 00630006 00000000 0041003c 00010000 ..c.....<.A.....
681B433C: 00af03af 00000004 3400d008 00000000 ...........4....
681B434C: 001f0004 00000000 0042001a 00030000 ..........B.....
681B435C: 00af03af 0000001e 3400d008 00000000 ...........4....
681B436C: 00010005 00000000 0046001e 00030000 ..........F.....
name = OptDepExcl1

statblob = [TextPointer]
------------------------------------------------
TextTimeStamp = 182572023808 RowId = (1:19733:64)

Slot 15 Offset 0x3a4
--------------------
Record Type = PRIMARY_RECORD
Record Attributes = NULL_BITMAP VARIABLE_COLUMNS
681B43A4: 00520030 01d345b0 00000000 00000000 0.R..E..........
681B43B4: 00030000 00000000 00660000 0001000b ..........f.....
681B43C4: 00000000 00000000 00000000 00000000 ................
681B43D4: 00000000 00000000 00770000 0000007d ..........w.}...
681B43E4: 00000000 00000000 00000000 00000000 ................
681B43F4: 001b0000 00000000 01c00003 81e601d6 ................
681B4404: 00af03af 0000001e 3400d008 00000000 ...........4....
681B4414: 00010008 00000000 00010041 00000000 ........A.......
681B4424: 00af03af 00000004 3400d008 00000000 ...........4....
681B4434: 001f0007 00000000 001f003d 00000000 ........=.......
681B4444: 00af03af 0000001e 3400d008 00000000 ...........4....
681B4454: 00230010 00000000 00230084 00000000 ..#.......#.....
681B4464: 00af03af 00000001 3400d008 00000000 ...........4....
681B4474: 00410006 00000000 0041003c 00000000 ..A.....<.A.....
681B4484: 00340134 00050002 00000000 00000000 4.4.............
681B4494: 0042000a 00000000 00420063 00000000 ..B.....c.B.....
681B44A4: 00af03af 0000001e 3400d008 00000000 ...........4....
681B44B4: 00010008 00000000 00010041 00030000 ........A.......
681B44C4: 00af03af 00000004 3400d008 00000000 ...........4....
681B44D4: 001f0007 00000000 001f003d 00030000 ........=.......
681B44E4: 00af03af 0000001e 3400d008 00000000 ...........4....
681B44F4: 00230010 00000000 00230084 00030000 ..#.......#.....
681B4504: 00af03af 00000001 3400d008 00000000 ...........4....
681B4514: 00410006 00000000 0041003c 00030000 ..A.....<.A.....
681B4524: 00af03af 00000004 3400d008 00000000 ...........4....
681B4534: 00440004 00000000 0042001a 00010000 ..D.......B.....
681B4544: 00af03af 0000001e 3400d008 00000000 ...........4....
681B4554: 00480005 00000000 0046001e 00010000 ..H.......F.....
681B4564: 0070004f 00440074 00700065 00780045 O.p.t.D.e.p.E.x.
681B4574: 006c0063 00000032 002a8225 4d150000 c.l.2...%.*....M
681B4584: 00010000 0041 ....A.
id = 30623152
status = 0
first = 0
indid = 3
root = 0
minlen = 102
keycnt = 11
groupid = 1
dpages = 0
reserved = 0
used = 0
rowcnt = 0
rowmodctr = 0
reserved3 = 0
reserved4 = 0
xmaxlen = 119
maxirow = 125
OrigFillFactor = 0
StatVersion = 0
reserved2 = 0
FirstIAM = 0
impid = 0
lockflags = 0
pgmodctr = 0

keys
--------------------------------
681B4404: 00af03af 0000001e 3400d008 00000000 ...........4....
681B4414: 00010008 00000000 00010041 00000000 ........A.......
681B4424: 00af03af 00000004 3400d008 00000000 ...........4....
681B4434: 001f0007 00000000 001f003d 00000000 ........=.......
681B4444: 00af03af 0000001e 3400d008 00000000 ...........4....
681B4454: 00230010 00000000 00230084 00000000 ..#.......#.....
681B4464: 00af03af 00000001 3400d008 00000000 ...........4....
681B4474: 00410006 00000000 0041003c 00000000 ..A.....<.A.....
681B4484: 00340134 00050002 00000000 00000000 4.4.............
681B4494: 0042000a 00000000 00420063 00000000 ..B.....c.B.....
681B44A4: 00af03af 0000001e 3400d008 00000000 ...........4....
681B44B4: 00010008 00000000 00010041 00030000 ........A.......
681B44C4: 00af03af 00000004 3400d008 00000000 ...........4....
681B44D4: 001f0007 00000000 001f003d 00030000 ........=.......
681B44E4: 00af03af 0000001e 3400d008 00000000 ...........4....
681B44F4: 00230010 00000000 00230084 00030000 ..#.......#.....
681B4504: 00af03af 00000001 3400d008 00000000 ...........4....
681B4514: 00410006 00000000 0041003c 00030000 ..A.....<.A.....
681B4524: 00af03af 00000004 3400d008 00000000 ...........4....
681B4534: 00440004 00000000 0042001a 00010000 ..D.......B.....
681B4544: 00af03af 0000001e 3400d008 00000000 ...........4....
681B4554: 00480005 00000000 0046001e 00010000 ..H.......F.....
name = OptDepExcl2

statblob = [TextPointer]
------------------------------------------------
TextTimeStamp = 182572089344 RowId = (1:19733:65)

DBCC execution completed. If DBCC printed error messages, contact your system administrator.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Now, the bad news. I am a bit of a novice and have picked this up from someone who left my company. It appears the latch error has been around for some time and only reared up when I instituted a new back up system that runs a dbcc check befor backing up. I don't think I have any clean backups.

Any help would be greatly appreciated.

Alex Mauer

View 17 Replies View Related

TempDB Log File Running Out Of Free Space While Running DBCC CheckDB On Large Database

May 28, 2015

In my environment, there is maintenance plan configured on one of the server and while running DBCC checkdb on a database of size around 200GB, log file usage of tempdb is increasing and causing the maintenance job to fail.

What can I do to make the maintenance job run successfully, size of the tempdb database is only 50GB and recovery model is set to simple. It cannot be increased as the mount point on which it is residing is 50GB.

View 3 Replies View Related

Run Checkdb/newalloc Against Msdb And Master?

Mar 1, 1999

Hello:

I am in the process of setting up a dbcc checkdb and dbcc newalloc job for the user database in production. Do I need to include master and msdb to have checkdb and msdb run against them daily?

Any information you can provide will be greatly appreciated. Thanks.

David Spaisman

View 1 Replies View Related

CHECKDB Failing To Fix Errors.

Feb 4, 2006

Hi,

I am running SQL Server 2000 with Service Pack 4. We recently had a rather nasty corruption problem over several of our databases on our server. It primarily affected indexes and page allocation tables. As of yet, we have yet to identify the cause of this problem. We ran hardware diagnostics and no problems were returned, and nothing aside from the errors that alerted us to the issue in the first place were found in the event logs or SQL error logs.

DBCC CHECKDB was ran several times (we ran it on all DBs on the server just to be safe, several came up corrupted) and used that to repair the data, but very quickly new corruptions popped up.

However, this is not the extent of my bewilderment. Due to the need to get our server back online, a couple co-workers decided to detatch the databases and reinstall the SQL server, then reattatch the databases and try and repair them. I am not sure why this would have mattered but it seems to have prevented any new corruptions.

Anyway, while I was repairing the problem databases to bring them back online, one of them has been giving me a particular problem. Several indexes were pretty thoroughly trashed, giving over 1000 consistency errors. There were also around 25 or so allocation errors. I rebuilt all of the indexes to remove the consistency errors, however the allocation errors still remain and CHECKDB will not remove them. Here are the results of my most recent checkdb repair attempt:

Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:886000) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:886112) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:886224) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:886424) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:886520) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:886656) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:886736) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:886936) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:887024) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:887176) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:887344) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:887464) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:887624) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:887816) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:887920) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:888096) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:888248) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:888352) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:888584) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Could not repair this error.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:888704) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:888840) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:889024) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:889168) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:889328) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
CHECKDB found 24 allocation errors and 0 consistency errors not associated with any single object.
CHECKDB found 24 allocation errors and 0 consistency errors in database 'PRODUCTION_CATEGORIZER'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (PRODUCTION_CATEGORIZER repair_allow_data_loss).

As you can see, it is telling me that the errors cannot be repaired until other errors are corrected first, but there are no other errors! I cannot figure it out. The rest of our databases on the server are now clean, this is the only one that is not working. Does anyone have any suggestions before we restore to the last backup?

View 7 Replies View Related

DBCC CheckDB

Jan 27, 2000

I have a few extremely large databases in SQL Server 6.5 sp3
(soon to be 5a - but we won't talk about that!!) NT 4.0 sp4
(about 10 GIG each). I don't have a big window of down-time
in order to do any maintenance. Does anyone know of a way to
be able to run dbcc checkdb or other dbcc's that I can run to
verify the database yet complete within a reasonable amount
of time? The last time dbcc checkdb was run, it was started
Friday night and still not complete Sunday night.
Over a weekend, I may have up to a 24 hour maintenance window.

Any suggestions would be appreciated.
Thanks!
Toni

View 1 Replies View Related

DBCC CHECKDB

Nov 9, 1999

Hai ,
When I ran DBCC CHECK DB of userdatabase, its reporting along with usual messages as
Descriptor for system table '8' in database '8' not found in the descriptor hash table.
I could'nt understand being familiar error encounterd .
Any one will appreciate for the help

Thank you

View 1 Replies View Related

DBCC Checkdb

Jan 17, 1999

Hello All,

I recently took over a SQL server with 300 MB of data. I am relatively new to SQL 6.5 and have been reading that DBCC checkdb and checkalloc should be run at least once per week. Apparently the person before me never ran any of those checks. Is not running the database consistency checks for so long going to present a problem? has anyone run into problems when running those checks? Any advise is greatly appreciated.

Pauli

View 4 Replies View Related

Dbcc Checkdb

Aug 28, 2006

I ran "dbcc checkdb(MCMSdb) with no_infomsgs" and I get the following:
Server: Msg 8946, Level 16, State 12, Line 2
Table error: Allocation page (1:274992) has invalid PFS_PAGE page header values. Type is 0. Check type, object ID and page ID on the page.

What cane be done to correct this problem?
Can this error prevent a user from connecting to the database?

View 3 Replies View Related

Dbcc Checkdb

Oct 25, 2006

hi guys

I ran checkdb and found 4 error message on the db.. it seen like same object.. can anyone tell me what it is.. and how can i fix it? thanks !!!!

1.
Server: Msg 8976, Level 16, State 1, Line 35
Table error: Object ID 2094630505, index ID 1. Page (1:809859) was not seen in the scan although its parent (1:77885) and previous (1:809767) refer to it. Check any previous errors.
2.
Server: Msg 8978, Level 16, State 1, Line 35
Table error: Object ID 2094630505, index ID 1. Page (1:809860) is missing a reference from previous page (1:809859). Possible chain linkage problem.
3.
Server: Msg 8976, Level 16, State 1, Line 35
Table error: Object ID 2094630505, index ID 1. Page (1:1453795) was not seen in the scan although its parent (1:1453347) and previous (1:1453796) refer to it. Check any previous errors.
4.
Server: Msg 8978, Level 16, State 1, Line 35
Table error: Object ID 2094630505, index ID 1. Page (1:1453801) is missing a reference from previous page (1:1453795). Possible chain linkage problem.

View 2 Replies View Related

DBCC Checkdb

Dec 8, 2006

Hi All,

Does anybody know if the results of DBCC CHECKDB are stored anywhere? If yes, where?
Also, if you don't select "attempt to repair minor problems" option when you set up the maintenance plan, will SQL Server let you know about any errors Integrity check encounters? If yes, where the erros can be found?

Thanks.

View 10 Replies View Related

DBCC CHECKDB

Jul 12, 2001

Hello all,

in the SQL 6.5 documentation it says when running the DBCC CHECKDB, you should make the database read Only or DBO use only. Do you guys know if SQL 6.5 locks rows while this runs? In SQL 7.0/2000 it only locks the schema.

Thanks,

Lee E. Smith

View 1 Replies View Related

Dbcc Checkdb

Nov 11, 1998

I am using windows nt40 and sql server 6.5 on a DEC ALPHA and accidentlly
started a dbcc checkdb. Is it possible to stop the process with out damaging the database?

View 1 Replies View Related

DBCC CheckDB

Nov 8, 2000

When running dbcc checkdb from my workstation(nt) I recieve some of
the output and then I get "Connection Broken" this is on a 6.5 machine
with the service pack 5, what could be causing my ODBC connection to drop
during the proccess of running checkdb?

Kevin

View 1 Replies View Related

Dbcc Checkdb

Dec 12, 2006

Hi All,

How can I make the dbcc checkdb fail so I can get the errors displayed in the report log? DBCC Checkdb is the step in the integrity job that I run once a month. What I am trying to do is when the dbcc checkdb fails for any reason, I want to get notified so I can correct the problem. I don't want to use repair fast or any other repair parameters that you can select when you run dbcc checkdb function because most of my dbs are 24x7.

Thanks.

View 12 Replies View Related

Dbcc Checkdb

Jul 5, 2007

How often do you run it in your shop?

I'm seeing (from the new SQL Best Practices Analyzer) that MS recommends that it be done once every two weeks on SQL 2005.

I have never been in the habit of running it in production. I have never experienced database corruption in any form.

Just curious.

Regards,

hmscott

View 4 Replies View Related

Dbcc Checkdb

Aug 6, 2007

Hi All,

I have a job set up that runs the dbcc checkdb and puts the results into a table. Then I run a query against this table to check the results of dbcc checkdb. If there are errors, I get a page that lets me know that there are some problems. When I ran this job on my production server, the job failed stating that there are problems with data integrity. So I copied this db to a dev server and recreated the job just like I have in prod. The job completed successfully withou any errors. Can anybody tell me what to look at to figure out why it failed on the prod server?

Thanks.

View 4 Replies View Related

DBCC CHECKDB

Jul 11, 2005

Madhur writes "Last week DBCC CHECKDB <database name> took 2 Hrs to complete on a database.
Today again i have started but with the following command:
dbcc checkdb (<database name>, REPAIR_FAST ).

It is now running for more than 2.5 Hrs now.

Does the execution time increases even when the DB is consistent?

Can we cancel the execution in the middle? What consequences it may have on the db?

Thanks in advance."

View 2 Replies View Related

Dbcc Checkdb ?

Aug 12, 2005

I have a db that is about 50Gigs. Last night it went into a suspect mode and I have not been able to get any of my tables to display. I am running the dbcc checkdb. I have been running it for over 7 hrs. Do you have any suggestions as to what I should do or do you have any ideas as to how long this process might take?

thanks,

View 4 Replies View Related

DBCC Checkdb

Sep 5, 2005

Ricardo writes "We are consistently getting this error. We have check the hardware and nothing appears in the checkdk, can you help.

Thanks

Ricardo

dbcc checkdb (virtualrequest)
DBCC results for 'tblVRAnswers'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 370256524, index ID 3: Page (1:243518) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 370256524, index ID 3, page (1:243518). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
There are 9608 rows in 106 pages for object 'tblVRAnswers'.

CHECKDB found 0 allocation errors and 2 consistency errors in database 'VirtualRequest'.

dbcc checkdb (virtualrequest)
DBCC results for 'tblvrquestions'.
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'VirtualRequest', index 'tblVRRequestedItems.IX_NC_tblVRRequestedItems_CurrentStatusID' (ID 784825958) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:214293:372) with values (CurrentStatusID = 3 and RequestedItemID = 413260) points to the data row identified by ().
There are 6614 rows in 103 pages for object 'tblvrquestions'.

CHECKDB found 0 allocation errors and 1 consistency errors in database 'VirtualRequest'

dbcc checkdb (virtualrequest)
DBCC results for 'tblvrquestions'.
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'VirtualRequest', index 'tblVRRequestedItems.IX_NC_tblVRRequestedItems_CurrentStatusID' (ID 784825958) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:214293:372) with values (CurrentStatusID = 3 and RequestedItemID = 413260) points to the data row identified by ().
There are 6614 rows in 103 pages for object 'tblvrquestions'.

CHECKDB found 0 allocation errors and 1 consistency errors in database 'VirtualRequest'."

View 1 Replies View Related

DBCC CHECKDB

May 17, 2007

We had a bit of an accident last night.

My nightly maintenance task runs fine normally. Last night it didn't.
When it got to DBCC CHECKDB for an audit database (it gets populated from triggers in other databases; one of the tables has over a million records), the live database server shut down and did not come back up. DBCC CHECKDB completed in 6 seconds with no errors. The next task in the sequence that would have run (but the log has no message of it completing or failing) was DBCC INDEXDEFRAG on that audit table with over a million records.

Even the OFF button on the 64-bit Dell server (SQL2005, Windows Server Enterprise x64 2003 SP1, 16 gig ram) did not work. There wasn't even the blue screen of death. It was just a blue screen. A plug out and plug back in was required.

The only recent configuration change has been that we have had Dell install a piece of disk-level replication software called Double Take.

Could CheckDB have contributed to this problem?

View 20 Replies View Related

Dbcc Checkdb

Jul 16, 2007

When i run TKizers sp to check database integrity. I'm getting this error.

Executed as user: IAPESQLAdmin. ...536) DBCC results for 'sysobjects'. [SQLSTATE 01000] (Message 2536) There are 1364 rows in 23 pages for object 'sysobjects'. [SQLSTATE 01000] (Message 2593) DBCC results for 'sysindexes'. [SQLSTATE 01000] (Message 2536) There are 138 rows in 5 pages for object 'sysindexes'. [SQLSTATE 01000] (Message 2593) DBCC results for 'syscolumns'. [SQLSTATE 01000] (Message 2536) There are 5251 rows in 104 pages for object 'syscolumns'. [SQLSTATE 01000] (Message 2593) DBCC results for 'systypes'. [SQLSTATE 01000] (Message 2536) There are 26 rows in 1 pages for object 'systypes'. [SQLSTATE 01000] (Message 2593) DBCC results for 'syscomments'. [SQLSTATE 01000] (Message 2536) There are 2115 rows in 1112 pages for object 'syscomments'. [SQLSTATE 01000] (Message 2593) DBCC results for 'sysfiles1'. [SQLSTATE 01000] (Message 2536) There are 2 rows in 1 pages for object 'sysfiles1'. [SQLSTATE 01000] (Message 2593) DBCC results for 'syspermissions'. [SQLSTATE... The step failed.

=============================
http://www.sqlserverstudy.com

View 5 Replies View Related