cancel
Showing results for 
Search instead for 
Did you mean: 

Deadlock occurred with CKR1/SAPRCKR1 on CKIS table

Ganimede-Dignan
Contributor
0 Kudos

Hi,

we see several message as "Deadlock occurred" in a ECC 6.00 system during CKIS deletion due cost reorganization. We use CKR1 TCOD.

The records deletion is for a large CKIS, 80 GB for this table.

When report run it generate several update process.

Have you got any suggest?

Thank you.

Accepted Solutions (0)

Answers (3)

Answers (3)

Sriram2009
Active Contributor
0 Kudos

Hi Ganimede

1. In MS SQl DB have you enable the DB auto-growth?

2. Apply the latest Service Pack and updates

3. Lock escalation for table CKIS, the lock escalation from rowlevellocks to pagelocks should be prevented, in the Queryanalyzer: execute sp_indexoption 'CKIS', 'AllowPageLocks','FALSE' for the database

4.Kindly share you SAP instance details (kernel, SPS level)?

Thanks

Sriram

Ganimede-Dignan
Contributor
0 Kudos

Hi,

>1. In MS SQl DB have you enable the DB auto-growth?

Yes.

>2. Apply the latest Service Pack and updates

OK, now is:

Microsoft SQL Server 2005 - 9.00.3042.00 (X64)   Feb 10 2007 00:59:02   Copyright (c) 1988-2005 Microsoft Corporation  Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)

Is it supported by SAP SP4 for MSSQl 2005?

>3. Lock escalation for table CKIS, the lock escalation from rowlevellocks to

>pagelocks should be prevented, in the Queryanalyzer:

>execute sp_indexoption 'CKIS', 'AllowPageLocks','FALSE' for the database

OK

>4.Kindly share you SAP instance details (kernel, SPS level)?

ECC 6.00

Kernel 7.00 patch 247

BASIS SP: 14

ABAP SP: 14

APPL: 12

Thank you.

Regards.


Ganimede-Dignan
Contributor
0 Kudos

>execute sp_indexoption 'CKIS', 'AllowPageLocks','FALSE' for the database

it is already setted

THX.

Bye.

Sriram2009
Active Contributor
0 Kudos

Hi

1. Apply the kernel & DBSL patch to 7.00 - level 353

2. Refer the SAP Note 111291 - FAQ: Deadlock analysis for SQL server  you can enable the deadlock monitor in the database level and check

3. Go thru the SAP Note 1487003 - Deletion of Statistical tables--Avoiding an Exclusive Lock

Check and apply the SAP Note

Still are you facing problem pls raise the SAP OSS Ticket

Thanks

Sriram

former_member184473
Active Contributor
0 Kudos

Hello Ganimede,

Check the following notes:

32129 - Deadlock analysis for the SQL server

111291 - FAQ: SQL server analysis and avoiding deadlocks

Regards,

Eduardo Rezende

Former Member
0 Kudos

Hi,

In case you are deleting the cost estimates for mass item it is recommended to go through with archiving process of SAP.

With this process you can able to remove the unwanted old cost estimates from system.

For archival the transaction code is SARA

and for cost estimate archival the object is CO_COPC

in variant you have the option of deleting unwanted costing run by period basis.

Once you complete the write process you can use the delete option which will delete the file created through archival.

Note : For archival you need to create a space where intially the file will get stored (it is for safer side in case if you want to retrive the same you can able to retrive it from the same path). Also you need to provide the file path in transaction code FILE.

For details please read the archival document of SAP in help.sap.com.

Thanks & Regards

Mahesh