After a recovery situation occurs, old correction and transport numbers are assigned again. This creates conflicts with the files at operating system level.
The recovery was not complete, or it was only possible to restore a database version from a time before these corrections or transports were created.
The only thing you can do is make sure that no more correction/ transport numbers in the affected area are assigned. The old corrections and transports in the source system cannot be restored. They can, of course, be transported to the destination system (if this has not yet been done).
To prevent the numbers from being assigned in the affected area, you must change the table entry that contains the last assigned number. This number is the only item in table E070L. Field TRKORR must be filled with a value that is higher than the last number assigned before the crash (for safety's sake, be generous). You can at least determine the last exported number from the /usr/sap/trans/log/ALOG* file.
Table E070L can only be maintained using Database utilities.
Comment: before Release 2.1A, the "HEAD SYST" entry in table TADIR
was used instead of table E070L (pgmid="HEAD", object="SYST").
If table E070L does not exist in your system, change field
KORRNUM of this TADIR entry.
Additional key words
Enter backup. Undo.
Key word: r3slcor
No comments:
Post a Comment