web

You’re offline. This is a read only version of the page.

Dynamics 365 CommunityForums Microsoft Dynamics GP (Archived) DBCC CHECKDB ERROR on...

Microsoft Dynamics GP (Archived)

DBCC CHECKDB ERROR on SQL server 2005

(0) Share

Report

Report

Posted on by Community Member

Hello,

I ran this script on Dynamics GP 10. 0 Database on SQL 2005

'DBCC CHECKDB' and it gave a long message. Below are just the errors in the message.

DBCC results for 'PJOURNAL'.

Msg 8952, Level 16, State 1, Line 1

Table error: table 'PJOURNAL' (ID 96719397). Index row in index '_WA_Sys_BCHSOURC_2EC5E7B8' (ID 4) does not match any data row. Possible extra or invalid keys for:

Msg 8956, Level 16, State 1, Line 1

Index row (1:61364:2) with values (BCHSOURC = 'GL_Normal ' and HEAP RID = (1:197413:2)) pointing to the data row identified by (HEAP RID = (1:197413:2)).

There are 2207 rows in 2687 pages for object "PJOURNAL".

CHECKDB found 0 allocation errors and 1 consistency errors in table 'PJOURNAL' (object ID 96719397).

DBCC results for 'SEE30303'.

Msg 8951, Level 16, State 1, Line 1

Table error: table 'SEE30303' (ID 199111900). Data row does not have a matching index row in the index 'PKSEE30303' (ID 2). Possible missing or invalid keys for the index row matching:

Msg 8955, Level 16, State 1, Line 1

Data row (1:185944:6) identified by (GLPOSTDT = '2011-05-25 00:00:00.000' and ITEMNMBR = 'GIKIBUSH ' and QTYTYPE = 1 and SEQNUMBR = 8) with index values 'ITEMNMBR = 'GIKIBUSH ' and DOCDATE = '2011-06-06 00:00:00.000' and RCTSEQNM = 8 and SEQNUMBR = 8'.

Msg 8951, Level 16, State 1, Line 1

Table error: table 'SEE30303' (ID 199111900). Data row does not have a matching index row in the index 'PKSEE30303' (ID 2). Possible missing or invalid keys for the index row matching:

Msg 8955, Level 16, State 1, Line 1

Data row (1:199883:2) identified by (GLPOSTDT = '2011-05-25 00:00:00.000' and ITEMNMBR = 'GI 4100020221 ' and QTYTYPE = 1 and SEQNUMBR = 5) with index values 'ITEMNMBR = 'GI 4100020221 ' and DOCDATE = '2011-06-06 00:00:00.000' and RCTSEQNM = 5 and SEQNUMBR = 5'.

Msg 8951, Level 16, State 1, Line 1

Table error: table 'SEE30303' (ID 199111900). Data row does not have a matching index row in the index 'PKSEE30303' (ID 2). Possible missing or invalid keys for the index row matching:

Msg 8955, Level 16, State 1, Line 1

Data row (1:199883:12) identified by (GLPOSTDT = '2011-05-25 00:00:00.000' and ITEMNMBR = 'GI K00201 ' and QTYTYPE = 1 and SEQNUMBR = 2) with index values 'ITEMNMBR = 'GI K00201 ' and DOCDATE = '2011-06-06 00:00:00.000' and RCTSEQNM = 2 and SEQNUMBR = 2'.

Msg 8951, Level 16, State 1, Line 1

Table error: table 'SEE30303' (ID 199111900). Data row does not have a matching index row in the index 'AK2SEE30303' (ID 3). Possible missing or invalid keys for the index row matching:

Msg 8955, Level 16, State 1, Line 1

Data row (1:199883:2) identified by (GLPOSTDT = '2011-05-25 00:00:00.000' and ITEMNMBR = 'GI 4100020221 ' and QTYTYPE = 1 and SEQNUMBR = 5) with index values 'GLPOSTDT = '2011-05-25 00:00:00.000' and ITEMNMBR = 'GI 4100020221 ' and TRXQTY = -1.00000 and EXTDCOST = -2000.00000 and SEQNUMBR = 5'.

Msg 8951, Level 16, State 1, Line 1

Table error: table 'SEE30303' (ID 199111900). Data row does not have a matching index row in the index 'AK2SEE30303' (ID 3). Possible missing or invalid keys for the index row matching:

Msg 8955, Level 16, State 1, Line 1

Data row (1:199883:12) identified by (GLPOSTDT = '2011-05-25 00:00:00.000' and ITEMNMBR = 'GI K00201 ' and QTYTYPE = 1 and SEQNUMBR = 2) with index values 'GLPOSTDT = '2011-05-25 00:00:00.000' and ITEMNMBR = 'GI K00201 ' and TRXQTY = -1.00000 and EXTDCOST = -15000.00000 and SEQNUMBR = 2'.

Msg 8951, Level 16, State 1, Line 1

Table error: table 'SEE30303' (ID 199111900). Data row does not have a matching index row in the index 'AK3SEE30303' (ID 4). Possible missing or invalid keys for the index row matching:

Msg 8955, Level 16, State 1, Line 1

Data row (1:185944:6) identified by (GLPOSTDT = '2011-05-25 00:00:00.000' and ITEMNMBR = 'GIKIBUSH ' and QTYTYPE = 1 and SEQNUMBR = 8) with index values 'DOCDATE = '2011-06-06 00:00:00.000' and ITEMNMBR = 'GIKIBUSH ' and TRXQTY = -1.00000 and EXTDCOST = -3000.00000 and SEQNUMBR = 8'.

Msg 8951, Level 16, State 1, Line 1

Table error: table 'SEE30303' (ID 199111900). Data row does not have a matching index row in the index 'AK3SEE30303' (ID 4). Possible missing or invalid keys for the index row matching:

Msg 8955, Level 16, State 1, Line 1

Data row (1:199883:2) identified by (GLPOSTDT = '2011-05-25 00:00:00.000' and ITEMNMBR = 'GI 4100020221 ' and QTYTYPE = 1 and SEQNUMBR = 5) with index values 'DOCDATE = '2011-06-06 00:00:00.000' and ITEMNMBR = 'GI 4100020221 ' and TRXQTY = -1.00000 and EXTDCOST = -2000.00000 and SEQNUMBR = 5'.

Msg 8951, Level 16, State 1, Line 1

Table error: table 'SEE30303' (ID 199111900). Data row does not have a matching index row in the index 'AK3SEE30303' (ID 4). Possible missing or invalid keys for the index row matching:

Msg 8955, Level 16, State 1, Line 1

Data row (1:199883:12) identified by (GLPOSTDT = '2011-05-25 00:00:00.000' and ITEMNMBR = 'GI K00201 ' and QTYTYPE = 1 and SEQNUMBR = 2) with index values 'DOCDATE = '2011-06-06 00:00:00.000' and ITEMNMBR = 'GI K00201 ' and TRXQTY = -1.00000 and EXTDCOST = -15000.00000 and SEQNUMBR = 2'.

Msg 8952, Level 16, State 1, Line 1

Table error: table 'SEE30303' (ID 199111900). Index row in index 'AK3SEE30303' (ID 4) does not match any data row. Possible extra or invalid keys for:

Msg 8956, Level 16, State 1, Line 1

Index row (1:152370:32) with values (DOCDATE = '2011-05-18 00:00:00.000' and ITEMNMBR = 'GF 4747RV ' and TRXQTY = -1.00000 and EXTDCOST = -7000.00000 and SEQNUMBR = 5) pointing to the data row identified by (GLPOSTDT = '2011-05-25 00:00:00.000' and ITEMNMBR = 'GF 4747RV ' and QTYTYPE = 1 and SEQNUMBR = 5).

Msg 8952, Level 16, State 1, Line 1

Table error: table 'SEE30303' (ID 199111900). Index row in index 'AK4SEE30303' (ID 5) does not match any data row. Possible extra or invalid keys for:

Msg 8956, Level 16, State 1, Line 1

Index row (1:57968:133) with values (ITEMNMBR = 'GF 10MM-CON ' and SEQNUMBR = 2) pointing to the data row identified by (GLPOSTDT = '2011-05-25 00:00:00.000' and ITEMNMBR = 'GF 10MM-CON ' and QTYTYPE = 1 and SEQNUMBR = 2).

Msg 8952, Level 16, State 1, Line 1

Table error: table 'SEE30303' (ID 199111900). Index row in index 'AK4SEE30303' (ID 5) does not match any data row. Possible extra or invalid keys for:

Msg 8956, Level 16, State 1, Line 1

Index row (1:180473:5) with values (ITEMNMBR = 'GF 12MM-CON ' and SEQNUMBR = 2) pointing to the data row identified by (GLPOSTDT = '2011-05-25 00:00:00.000' and ITEMNMBR = 'GF 12MM-CON ' and QTYTYPE = 1 and SEQNUMBR = 2).

There are 24310 rows in 1701 pages for object "SEE30303".

CHECKDB found 0 allocation errors and 12 consistency errors in database 'GHRL'.

repair_rebuild is the minimum repair level for the errors found by DBCC CHECKDB (GHRL).

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

Please how do i resolve this error message. I need you help!

Thank you and God bless you

*This post is locked for comments

I have the same question (0)

All responses Img

All responses (3)

Answers Img

Answers (0)

Community Member on at

Like (0)

Report

Re: DBCC CHECKDB ERROR on SQL server 2005

Good day, I will start with the following, the PJOURNAL is a table that can easily be cleared out as its the posting journal, when this file is not cleared regularly (with a maintenance on your GP) postings can be really slow.

So as a suggestion MS adds a job on your SQL server (not sql express) that clears the PJOURNAL so I will start by deleting the contents of it, then you can reindex, and recreate statistics, this might clear out your problem.

Ahhh remember index names for files most likely start with PK if you see any other its either from a customization or simply was created by "someone else".

Regarding the SEE30303 if you are not using HITB (Historical Inventory Trial Balance) you can clear this table too, but if you are using it, I will recommend you to run DBCC REINDEX.

Please make sure before you attempt to follow any steps/suggestions here that you have a valid and RESTORABLE backup as I have seen many many times how things go another route and then 1.- Not having a proper backup or 2.- Having a Backup but with problems when trying to restore.

For your backup I will suggest you to create a new backup file to DISK dont append to existing and once you have it, either try to restore it into a test environment or restore into a different database to make sure you can always go back to it.

Good Day

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Re: DBCC CHECKDB ERROR on SQL server 2005

Run this... DBCC UPDATEUSAGE (dbname) ...and then rerun DBCC CHECKDB

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Re: DBCC CHECKDB ERROR on SQL server 2005

Thank you for your responce. I appreciate

Was this reply helpful? Yes No

Helpful resources

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans