Database error 0 at UPD access to table TBTCO

[Former Member]

Hi all,

Getting huge number of runtime errors and background jobs are failing to trigger for our ECC6 (EHP4) system with the the below error is the system log:

Database error 0 at UPD access to table TBTCO

> Microsofthttp://SQL Server Native Client 10.0[SQL

> Server]Violation of PRIMARY KEY constraint 'ALCLASTOOL~0'.

> Cannot insert duplicate key in object 'erp.ALCLASTOOL'.

Run-time error "DBIF_RSQL_SQL_ERROR" occurred

> Short dump "111120 115822 AP401-No de4_ERP_00 " generated

Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20111120115822AP401-Node4_ERP_00 SAPSYS 000 )

any advice appreciated

Thanks

Gurch

[Former Member · Accepted solution]

Hi,

Were there any recent changes to your system?

If not,

1. Check if SAP_REORG_JOBS is scheduled and running successfully.

2. Check lock entries and whether there is an active long running job.

3. Run a DB check and also check if update is active.

4. Check SAP Note 976203.

Hope this helps.

Regards,

Varun

[Former Member · Accepted solution]

Thanks for the reply Varun, it seems our issue is more sinister than I first thought.

No background are triggering at all and dumps are being generated whenever any attempts are made.

A database restore to before this issue manifested looks like the safest bet.

[former_member188883 · Accepted solution]

Hi,

Server]Violation of PRIMARY KEY constraint 'ALCLASTOOL~0'.
> Cannot insert duplicate key in object 'erp.ALCLASTOOL'.

As per the above information it seems that your index is corrupted or missing. Please check the index health using se14 tcode.

If the dump is through using a Z-program or Z-Tcode , you need to review the piece of code where modify or update statement is getting executed.

Dump mentions that an entry already exists in the table with similar primary key and you try to insert a similar entry again.

Also as varun pointed out, there could some old lock entries which is is not released. Check the same in tcode SM13.

Hope this helps.

Regards,

Deepak Kori

[Former Member]

Hi Gurch,

Please run 'Database object' and 'Runtime object' check on table ALCLASTOOL in SE14. Please go through the dump details for any clue.

Thanks,

Siva Kumar