Online redo logs fill-up due to long running SCM processes

[Former Member]

DB2 v9.7

AIX v6.1 P570

Running Standard SAP Code

Going live with SCM system running SNP/DP GATP how can we avoid having our online redo logs fill-up due to long running processes (i.e., CTM. Process Chains, BOP, DP Runs) Need to know SAP Best Practice regarding this -

Per our developers, BOP jobs performs commit when everything is processed and update table in one go at end, Hence not possible to perform commit regularly. Actually they will have to run BOP for 3200 material with 98000 sales order items.

But after just running BOP for 40 material with 22000 sales orders line items we are getting DBIF_RSQL_SQL_ERROR + CX_SY_OPEN_SQL_DB dumps

Any assistance on this would be helpful...

Thanks -

[Former Member · Accepted solution]

Fred

Check OSS notes for this error. The BOP compponent has a steady stream of corrections developed by SAP especially in older releases.

Also make sure your Livecache Build is consistent with SCM Release/ Patch level.

Rishi Menon