Log File Management: Troubleshooting

Failure in the DB2 User Exit


The procedure for finding out the cause of the trouble is basically the same for both the ARCHIVE and RETRIEVE action of the DB2 user exit program.


  1. Check the diagnostic file db2diag.log .
  2. The entry in this file will provide information about the return code received from the user exit program. (For more information, see Messages).

  3. Look at the db2uext2 protocol, error and trace files. These files are located in the DIAGPATH (database parameter). The file names are as follows:
  4. db2uext2.log : Protocol file

    db2uext2.err : Entries for errors that occurred

    db2uext2.trc : Trace file for the last DB2 user exit processing. (For information about tracing, see Tracing.)

  5. Look at the actions table in the ADM<SID> database (not yet supported).

Failure in Log File Archiving or Log File Restoring


  1. Look at the journal.
  2. One page of the log file management notebook is called the "journal". The log file management actions are listed there. To display a detailed protocol for a particular action, double-click on the relevant action entry.

  3. Look at the protocol files.
  4. The protocol files are located in the /db2/<SID>/saparch (archiving) and db2/<SID>/saprest (restoring) directories. Their file names have the following format:

    For archiving: a<enc_ts>.<fid>
    For restoring:

    where <enc_ts> is the encrypted timestamp of the execution time and <fid> is the function ID of the log file management task (for example, "svd" stands for archive and subsequently delete a log file).

    The contents of these files are the same as you will get if you access the SAP-DB2admin: Log File Management function Journal from the DB2 Control Center.

  5. Procedure for ADSM problems.