The productive BW system of one of our clients had a serious problem. Some tables (SID tables of several central InfoObjects) were deleted directly from the database and could not be re-constructed. The only way to get back to a consistent state was a complete restore to a point a few hours back. The connected sources systems (ERP and CRM) were not restored.
Since many delta loads took place during the time when the process chains were stopped and the restore point, the delta information were not consistent anymore between the restored BW system and the connected ERP and CRM systems. The situation is described in note 731682 Backup in BW and OLTP: Experiences, risks & recommendations. There it is stated "Therefore, you must usually re-initialize all of the DataSources for which delta data was loaded since the backup time." Re-Initialization would have had a huge impact as it is not possible to repair the data for all data sources with selective full data loads and the consequence would have been a complete re-load. Nevertheless, even a repair full for a few dozen DataSources would have taken considerable time.
However, we were aware of one fact: Most of the InfoPackages were only executed once in the respective period. This also means that the delta information, which we were missing after the restore, was still sitting in the source system because the majority of data sources support a delta repetition (especially the critical ones like 2LIS). The above mentioned note supported us in our thinking: "You have a generic option to reload the data again by repeating the delta data request and therefore achieving a consistent status again only in the cases in which delta data was loaded precisely once since the backup time". Basically the last request in BW has to be changed to red and the relevant tables containing the delta information on source system side have to be "adjusted".
Since the information in the note is not very detailed, we will go into more depth here. If you ever come into such a situation, the information might be helpful to do the right things:
Once all deltas were captured, the normal process chains can be re-started and pick-up the delta information from the PSA.
In those cases where it did not work or where the Delta-InfoPackages were executed more than once, a repair load or a re-initialization was done. Within a few hours, the system was completely back to normal.
There are few general things, which need to be considered to get this working:
Whatever you do in such cases, you need to be careful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
11 | |
9 | |
7 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 |