SAP Note 27953 - SAPDBA restart: Terminates after successful Exp/Imp

Symptom:

Only in 2.2D (2.1J):
If after an ORA, EXP, or IMP error, the SAPDBA restart option is used, the message "Export/Import not successfully processed" appears after a successful import or export, and processing is terminated.

If the number of errors which occurred is very large (several hundreds or thousands) (for example if during the import the DB is accidentally shutdown -> error messages for each table), this error, that is the termination after the actual successful export or import, can also occur in versions 2.2D to 2.2G and 3.00 to 3.0B.

Cause and prerequisites

SAPDBA incorrectly interprets the error messages that were already already in the log file before the restart as being current.

Solution
Rename the old log, for example .../sapreorg/1234567890.rtc -> 1234567890.rtc.old, before the restart.
SAPDBA then creates a new log 1234567890.rtc when restarting and
registers only the current export/import error messages.
or:
According to note 12741, copy the corrected version of sapdba from sapserv3/4 and redo the restart.
The first case is corrected in 2.2E, the second as of 2.2H and 2.0B.

Additional key words

SAPDBA, export, import, restart