Keep your PO server down!
Keeping SAP PO database size low is useful for keeping the system running efficiently. This blog lists housekeeping activities that can be performed to reduce database size and refers to SAP Help documentation and Community blogs that showcase how to perform these activities. Therefore, this blog serves as the index of activities for keeping database size of PO low.
Please note that this document is written based on NW AS Java 7.31 SP22.
These activities can be performed to reduce database size of PO server:
- Cleaning up Job Log
- Cancelling PI messages
- Cancelling BPM processes
Table below shows three resources that can be archived and their corresponding documentation.
|Resource||Documentation and Blogs|
|PI Messages||SAP Help document Performing Background Processing is a start point to enable PI message archiving. Ensure that you go through prerequisites therein.|
|BPM Processes||SAP Note 2365730 – BPM Archiving is a great place to start reading about BPM Archiving and links to subsequent documentation and blogs.|
|BRM Logs||SAP Help document Archiving Business Rules shows how to archive business rules using Java Archiving Cockpit. The corresponding Job Definition for BRM Archiving is brm_rules_write.|
Cleaning up Job Log
CleanJob is scheduled to execute on weekly basis to handle jobs in COMPLETED status. A recurrent job having a basic issue can quickly fill up tables with prefix BC_JOB. For example, if disk space is full and BPM archiving job is scheduled to execute daily then if went unnoticed this issue will fill up tables with prefix BC_JOB.
WARNING: Ensure that root cause analysis is performed prior to cleaning up jobs as cleaning up job log is a non-recoverable activity.
SAP Note 2356810 – Cleaning Jobs left by the Java Scheduler supplies instructions to clean jobs in different states.
Cancelling PI Messages
WARNING: Ensure that root cause analysis is performed prior to cancelling messages as cancelling messages is a non-recoverable activity.
PI messages are eligible for archiving only in their final state. COMPLETED and CANCELLED are the final states of a messages. Leaving the messages in other states for long time can pile up rows in tables with prefix BC_MSG. Cancel the messages soon after root cause analysis is finished. Once messages are cancelled, they are eligible for archiving.
Cancelling BPM Processes
WARNING: Ensure that root cause analysis is performed prior to cancelling processes as cancelling processes is a non-recoverable activity.
Similar to PI messages, BPM Processes only in COMPLETED and CANCELLED state are eligible for archiving. Many processes in SUSPENDED state will mean size of tables with prefix BC_BPEM is also large. Cancel the BPM processes soon after root cause analysis is finished.
As a result of performing housekeeping activities, the database footprint of PO server should be signigicantly lower. Therefore, PO server should be able to serve with higher speed.