Solution : https://service.sap.com/sap/support/notes/434645 (Connexion à SAP Service Marketplace requise)
Mots Clés :
makt physical matchcode tables secondary index tables, system automatically rolls back, ensure thatthe production system, incomplete recovery include restoring, hard disk prevents, practice document provided, current online logs, importing incorrect transports 5, adequate backup concept, regular restore tests
Notes associées :
| 1420452 | FAQ: Restore and recovery with MS SQL Server |
| 1297986 | Backup and Restore strategy for MS SQL Server |
| 1038709 | FAQ: SAP MaxDB/liveCache OneDB |
| 966117 | Oracle Flashback Database technology |
| 952783 | FAQ: MaxDB high availability |
| 820824 | FAQ: SAP MaxDB/liveCache technology |
| 605062 | FAQ: Restore and recovery |
| 533999 | Restore Until with a Unicode database terminates |
| 445814 | DBMGUI and Restore Until |
| 438820 | Point-in-time recovery in the ALE environment |
| 434647 | Point-in-time recovery in an SAP system group |
| 425825 | Consistency checks, /sapapo/om17, /sapapo/cif_deltareport |
| 365481 | Block corruptions |
| 363602 | New Compare monitor - Request for Compare |
| 319332 | Content Server backup strategies |
| 31496 | CC-INFO: Client deleted by mistake |