IBM Support

LI75358: ROLLFORWARD COMMAND FAILED WITH SQL4970N ERROR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When DB2 rollforward command with stop option is issued the
    requried log file was not found. Rollforwad command can't make
    the database consistent. failed with SQL4970N error. There is
    extra logic involved that ends up creating a new copy of
    required log file. The following messsgae could be db2diag.log
    file
    2010-03-23-23.15.34.375576-240 I4028087E420        LEVEL: Info
    PID     : 12262                TID  : 183278496096 PROC :
    db2sysc 3
    INSTANCE: DB2INST1             NODE : 003          DB   : SAMPLE
    EDUID   : 34412                EDUNAME: db2loggr (RAVESTAG) 3
    FUNCTION: DB2 UDB, data protection services, sqlpgCallGIFL,
    probe:1250
    DATA #1 : <preformatted>
    New log extent 50800, PId 1269236666, StartLsn 000008D5F5014000
    

Local fix

  • Make sure all the requried log file available. Especially when
    the overflow log path is used for rollward. The following
    command is recommened: rollforward db <dbname> stop overflow log
    path (xxXX)
    

Problem summary

  • When DB2 rollforward command with stop option is issued the
    
    requried log file was not found. Rollforwad command can't make
    the database consistent. failed with SQL4970N error. There is
    extra logic involved that ends up creating a new copy of
    required log file. The following messsgae could be db2diag.log
    file
    2010-03-23-23.15.34.375576-240 I4028087E420        LEVEL: Info
    PID     : 12262                TID  : 183278496096 PROC :
    db2sysc 3
    INSTANCE: DB2INST1             NODE : 003          DB   : SAMPLE
    EDUID   : 34412                EDUNAME: db2loggr (RAVESTAG) 3
    FUNCTION: DB2 UDB, data protection services, sqlpgCallGIFL,
    probe:1250
    DATA #1 : <preformatted>
    New log extent 50800, PId 1269236666, StartLsn 000008D5F5014000
    

Problem conclusion

  • This APAR is first fixed in DB2 V9.5 Fixpak 6
    

Temporary fix

  • Make sure all the requried log file available. Especially when
    
    the overflow log path is used for rollward. The following
    command is recommened: rollforward db <dbname> stop overflow log
    path (xxXX)
    

Comments

APAR Information

  • APAR number

    LI75358

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-03-30

  • Closed date

    2010-05-14

  • Last modified date

    2010-05-14

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

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

    IC68546 IC68553

Fix information

  • Fixed component name

    DB2 UDE ESE LIN

  • Fixed component ID

    5765F4104

Applicable component levels

  • R950 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
14 May 2010