DB is Growing Up - Cleaning Needed

If there is a performance issue on an ABAP system, BASIS Admin must think about the increasing basis tables in my opinion.

And ADMIN can do the following proactive and reactive operations.

As for the proactive operations Standart Jobs must be checked. Sap Note "16083 - Standard jobs, reorganization jobs" gives detail about reorganization and deletion jobs. Let me take the list of standart jobs also here. You can see details in the note.

For reactive operations admin can do the followings;

• Take the list of largest tables. Depending on the database type the list can be taken as below;

• Then apply the available solutions depending on the table types listed in the SAP Note 706478 - Preventing Basis tables from increasing considerably

Here is an example of an ERP system cleanup process.

DB type is MS SQL Server.

• There were some missing standart reorganize or delete jobs. They were resscheduled according to the note mentioned above.

• The list of largest tables was like below. We dealt with only these tables. This list can differ according to the system or project.

• According to the tables the following actions are done;
  • For tables EDI40, EDIDS, EDIDC
    • The item in the note says: "2. Archive old entries as described in Note 40088."
    • We had meeting with business consultants and data owner. After an aggreement data was archived with IDOC archive object. Only last 3 months data is left. After first archive some data could not be deleted because of the statuses. Then business consultants changed the statuses of the data for archiving and deletion. Second archiving and deletion is done. On each run TAANA is run tor table analysis.

• For tables BALDAT, BALHDR
  • The item in the note says: "1. Delete old entries as described in Note 195157."
  • According to the note with the discussion of data owner SBAL_DELETE job was scheduled weekly. Last 3 months data is left.

• For tables TST03
  • The item in the note says: "11. See Note 48400, which describes the options for reorganizing TemSe and spool. See also Note 666290."
  • The following standart jobs were controlled and some variants has been changed for short retention periods. 

SAP_REORG_SPOOL (RSPO1041) 

SAP_REORG_JOBS

SAP_REORG_BATCHINPUT

SAP_SPOOL_CONSISTENCY_CHECK

SAP_REORG_ORPHANED_JOBLOGS

SAP_REORG_ORPHANED_TEMSE_FILES

• For tables ARFCSDATA, ARFCSSTATE, TRFCQOUT
  • The item in the note says: "7. Check the proposals from Note 375566."
  • After aggreement with business consultants and data owner RSTRFCQDS job was scheduled. Variants were created for each qrfc queue names.

• For tables SWWLOGHIST, SWW_CONT
  • The item in the note says: "4. Archive entries that are no longer required as described in Note 49545."
  • We discussed the issue with business consultants and decided to delete data older than 3 months. For cleaning RSWWWIDE and RSWWHIDE jobs were scheduled weekly with a variant older than 3 months. 

     You can also use WORKITEM archive object to archive the workitem data depending on the business need.

• For table SNAP
  • The item in the note says: "13. See Note 11838 for further information."
  • Reorganization is done in ST22 transaciton. RSSNAPDL program is scheduled daily basis.

• For tables IDOCREL, SRRELROLES
  • The item in the note says: "3. See Note 505608 and regularly schedule RSRLDREL."
  • After aggreement with business consultants and data owner RSRLDREL job was scheduled. Variants were created according to eh link types. Note can be checked for details.

• For tables BDCP, BDCPS
  • The item in the note says: "5. See Note 513454 and regularly schedule report RBDCPCLR to delete change pointers that are no longer required."
  • After aggreement with business consultants and data owner RBDCPCLR job was scheduled.

• For tables Z* tables
  • Business Consultants and data owner has decided about the customer tables data. They built up programs for cleaning. We scheduled those programs for regular intervals.

• Out of this list of action since the DB was MS SQL Server we also applied the note "1744217 - MSSQL: Improving the database performance"

In addition to the main note for basis tables you can also use Data Management Guide that contains detailed information about avoiding and reducing data. Use below address.

http://service.sap.com/ilm

-> Data Archiving   -> Media Library   -> Literature and Brochures   -> Data Management Guide