Solution : https://service.sap.com/sap/support/notes/584548 (SAP Service marketplace login required)
Summary :
This SAP Note addresses the issue of unusually high redo log generation in SAP systems, which can potentially lead to system shutdowns due to full archive directories. The noted causes include inadequate application operations or configuration issues across various Oracle versions, with identified reasons ranging from tablespaces left in backup mode to bugs in Oracle software affecting rollback and DML processes on indexes. Solutions are multi-fold, involving checks and corrections in backup settings, application function diagnostics, and specific Oracle parameters adjustment. Additionally, operational recommendations are provided for index management and materialized views, ensuring better management of redo log volumes.
Key words :
st04 -> detailed analysis menu -> sql request, sqlplus <sapuser>/<password>truncate table ddlog, long-running rddexecl executions occurred, redo log frequency increases significantly, redo log data increases significantly, increased redo log frequency due, entire related 8k block, alternating large-scale inserts, large-scale redo logs, br tools parameter backup_dev_type
Related Notes :
| 912918 | Massive UNDO/REDO generation when you use ASSM |
| 741478 | FAQ: Materialized views |
| 581359 | Very high redo log amount with parallel txn rollback |
| 533455 | Terminations due to higher number of extents |
| 515762 | Index cluster DML hangs, rollb. seg. increases very quickly |
| 79341 | Checkpoint not complete |
| 4162 | Missing "end backup" |
| 3155 | Termination due to tablespace overflow |
| 391 | Archiver stuck |