You maintain a SAP MaxDB/liveCache standby database as a Disaster Recovery (DR) solution by using log shipping scripts or a 3rd-party solution.
You observe that the data area of the standby database (DR database) data area keep growing and getting larger than the Production database data area. Sometimes a data volume is created automatically.
Other behavior is that after some time the log shipping script/process fails with DB FULL errors. Further checking the KnlMsg file you can see an entry like the following:
Thread 0x1B1C Task 219 2015-02-07 20:47:27 WNG Converter 20036: DB FULL: Task 219 suspended (used pages in static converter map: 11806168 requested: 12014632 max pages in map: 23820799, partition: 0)
- SAP MaxDB 7.9 releases prior to 7.9.08.22;
- SAP MaxDB/liveCache 10.0 releases prior to SAP liveCache 10.0 LCA build 20 (liveCache Kernel 7.9.08.23);
- Any operating system supported by SAP MaxDB/liveCache.
logshipping, standby, disaster, recovery, datenbank, datenbanksystem, rdbms, log ship fails, stand by fails, live cache, DR issues, DR issue, LVC, LCA, logship , KBA , BC-DB-SDB , MaxDB , BC-DB-LVC , liveCache , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.