Transaction DB12 is checking the timestamp of the last backup for all objects in library R3<sid>DATA and - if Java is used - in SAP<sid>DB. If the timestamp is the same for all objects, the backup is considered "complete" otherwise it is incomplete.
Basically there are 3 reasons why the backup could be considered incomplete:
1. One or a few objects could not be saved, for example because they are damaged or were locked during the backup.
2. After a complete backup, one or a few objects were saved separately by a SAVOBJ command.
3. A (complete) backup was started while the data collection for DB12 was running.
Reason 3 can be identified by comparing the execution times of report RSDB4BFT with the backup times. The execution times of program RSDB4BFT can be found by looking at transaction ST03 under "Collector and Performance DB" -> "Performance Monitor Collector" -> "Execution TimeS" and checking for the execution times or report RSDB_TDB (that one is calling RSDB4BFT).
If reason 3 does not apply, double-click on the newest entry "Backup not complete" to get a list of objects that have not been saved. If you get a short list, then reason 1 does apply and you should have a closer look at your last backup logs. If you get a long list, reason 2 does apply. This usually does not require any action, you only could check who was saving those objects and what for (saving individual objects should only be done in exceptional situations). Note that the list of objects that have not been saved is only kept until you get another complete backup, so if your latest backup was complete, you will not get the list.
Kind regards,
Christian Bartels.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.