IC88338: ERROR DURING RETRIVAL OF LOG FILES WHILE TAKING THE DATABASE BACKUP.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • You may find the following error in the db2diag.log while the
    database backup is executing and returns backup successful on
    the command prompt.
    
    
    2012-04-03-20.12.10.452784+120 E340667A617        LEVEL: Error
    PID     : 26738736             TID  : 16194       PROC : db2sysc
    0
    INSTANCE: inst1             NODE : 000
    EDUID   : 16194                EDUNAME: db2logmgr (BCMPL001) 0
    FUNCTION: DB2 UDB, data protection services,
    sqlpgRetrieveLogVendor, probe:2516
    DATA #1 : String, 107 bytes
    The actual log file size did not match the expected file size,
    retrying retrieve. Actual / Expected / File:
    DATA #2 : signed integer, 8 bytes
    9043968
    DATA #3 : signed integer, 8 bytes
    32776192
    DATA #4 : String, 53 bytes
    
    2012-04-03-20.12.10.454078+120 E341285A461        LEVEL: Error
    PID     : 26738736             TID  : 16194       PROC : db2sysc
    0
    INSTANCE: inst1             NODE : 000
    EDUID   : 16194                EDUNAME: db2logmgr (BCMPL001) 0
    FUNCTION: DB2 UDB, data protection services,
    sqlpgRetrieveLogVendor, probe:2541
    DATA #1 : String, 37 bytes
    The bad log file was saved in.  File:
    DATA #2 : String, 53 bytes
    /db2/cmdb2ibb/NODE0000/SQL00001/SQLOGDIR/S0005801.SA1
    
    Analysis:
    
    This issue occurs since the first time the retrival is completed
    successfully
    as shown in the entries below, but when it goes for a retrival
    of logs for the second time it fails.
    
    
    2012-04-03-20.12.03.517684+120 I338679A369        LEVEL: Warning
    PID     : 26738736             TID  : 16194       PROC : db2sysc
    0
    INSTANCE: inst1             NODE : 000
    EDUID   : 16194                EDUNAME: db2logmgr (BCMPL001) 0
    FUNCTION: DB2 UDB, data protection services,
    sqlpgRetrieveLogFile, probe:4130
    MESSAGE : Started retrieve for log file S0005801.LOG.
    
    2012-04-03-20.12.06.084698+120 I339049A438        LEVEL: Warning
    PID     : 26738736             TID  : 16194       PROC : db2sysc
    0
    INSTANCE: inst1             NODE : 000
    EDUID   : 16194                EDUNAME: db2logmgr (BCMPL001) 0
    FUNCTION: DB2 UDB, data protection services,
    sqlpgRetrieveLogFile, probe:4148
    MESSAGE : Completed retrieve for log file S0005801.LOG on chain
    0 to
              /db2/cmdb2ibb/NODE0000/SQL00001/SQLOGDIR/.
    
    2. Second time the retrival logs failure
    
    2012-04-03-20.12.09.581098+120 I340297A369        LEVEL: Warning
    PID     : 26738736             TID  : 16194       PROC : db2sysc
    0
    INSTANCE: inst1             NODE : 000
    EDUID   : 16194                EDUNAME: db2logmgr (BCMPL001) 0
    FUNCTION: DB2 UDB, data protection services,
    sqlpgRetrieveLogFile, probe:4130
    
    2012-04-03-20.12.10.452784+120 E340667A617        LEVEL: Error
    PID     : 26738736             TID  : 16194       PROC : db2sysc
    0
    INSTANCE: inst1             NODE : 000
    EDUID   : 16194                EDUNAME: db2logmgr (BCMPL001) 0
    FUNCTION: DB2 UDB, data protection services,
    sqlpgRetrieveLogVendor, probe:2516
    DATA #1 : String, 107 bytes
    The actual log file size did not match the expected file size,
    retrying retrieve. Actual / Expected / File:
    DATA #2 : signed integer, 8 bytes
    9043968
    DATA #3 : signed integer, 8 bytes
    32776192
    DATA #4 : String, 53 bytes
    
    2012-04-03-20.12.10.454078+120 E341285A461        LEVEL: Error
    PID     : 26738736             TID  : 16194       PROC : db2sysc
    0
    INSTANCE: inst1             NODE : 000
    EDUID   : 16194                EDUNAME: db2logmgr (BCMPL001) 0
    FUNCTION: DB2 UDB, data protection services,
    sqlpgRetrieveLogVendor, probe:2541
    DATA #1 : String, 37 bytes
    The bad log file was saved in.  File:
    DATA #2 : String, 53 bytes
    /db2/cmdb2ibb/NODE0000/SQL00001/SQLOGDIR/S0005801.SA1
    
    The problem is related to the fact that we making extra retrieve
    requests for logs that have already been included in the backup
    image.
    
    The fix will remove these extra retrieve requests.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 10.1 FP2 or subsequent fix pack.              *
    ****************************************************************
    

Problem conclusion

  • First Fixed in DB2 Version 10.1 Fix Pack 2
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC88338

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-17

  • Closed date

    2013-04-05

  • Last modified date

    2013-04-05

  • APAR is sysrouted FROM one or more of the following:

    IC84049

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RA10 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

10.1

Reference #:

IC88338

Modified date:

2013-04-05

Translate my page

Machine Translation

Content navigation