How to handle BTC inconsistencies with new standard jobs and SM65
Hello SAP experts,
I want to describe a phenomen which can occur in newer Support Packages (with the new standard job SAP_BTC_TABLE_CONSISTENCY_CHECK or the SM65 check) and also how to use the new standard jobs and SM65.
New Standard Jobs
There are two new standard jobs (note 1440439 – New Standard Jobs (2)):
1. Job name: SAP_ADS_SPOOL_CONSISTENCY_CHECK
Description: Delete “orphaned” ADS spool files
2. Job name: SAP_BTC_TABLE_CONSISTENCY_CHECK
Description: Check batch table consistency
Note: 1549293 Other terms
Implemented with the following SPs:
So all of you who have implemented ERP EhP6 SP07 for SEPA are concerned! (SAPKB73107)
To activate the new jobs go to SM36, click on standard jobs (SHIFT+F4) and click on default scheduling (please delete unnecessary Jobs like SAP_COLLECTOR_FOR_NONE_R3_STAT in a ABAP only system) or schedule it with your third party job tool (like Control-M, UC4 etc.).
If you have scheduled the standard jobs, which you definitively should (notes 1411877 and 16083 to avoid growth of you basis tables), you will have the table consistency check and automatically fix for the batch tables.
You can see the output in the SM37 job log or in SM21 system log (produced with SM65 other messages look exactly):
At first implement note 1549293 (SM65: Consistency check improvements), because during normal operation time it locks the TBTCO completely which effects the whole jobs in your system!!!
Start TA SM65, Goto Additional test and select like in this picture and execute:
If you have every day such error messages, you have to change the scheduled time for the standard jobs
Because these can occur every time when the 2 jobs SAP_REORG_JOBS and SAP_BTC_TABLE_CONSISTENCY_CHECK run at the same time! Please run first SAP_REORG_JOBS and then the other one.
If you still have such messages after you scheduled the reorg jobs:
Inconsistency detected in tables TBTCO and TBTCP
Inconsistency detected in tables TBT*
Please follow the instructions below:
- check note 924198 if table TBTCCNTXT is affected
- implement note 1381629 and run report ZDELBADCONTEXT to check and then fix the inconsistencies
SM65 is also a good tool for checking the server after an upgrade/migration like TA SICK. I think this transaction is not so widespread, but pretty cool to get an overview.
I hope I could tell something new about the BTC tables and the standard jobs.
If you have any further questions, don’t hestate to comment the blog or contact me or one of my colleagues at Q-Partners ( info_at_qpcm_dot_de )
Technology Consultant at QPCM (www.qpcm.eu)
Format adjustments after migration of the blog