IBM Support

LI73399: IF LOGARCHMETH2 ONLY IS SPECIFIED A ROLLFORWARD CAN FAIL WITH SQL4970N

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In V8.1-8.2 if archival logging is enabled and ONLY
    'logarchmeth2' is specified a ROLL-FORWARD operation will NOT
    attempt to retrieve the logs from the logarchmeth2 path.
    A SQL4970N may be received:
    
    SQL4970N Roll-forward recovery on database "<name>" cannot reach
              the specified stop point (end-of-log or point-in-time)
              because of missing or corrupted log file(s) on
              database partition(s) "<database-partition-list>".
              Roll-forward recovery processing has halted on log
              file
              "<log-file>".
    
    If 'logarchmeth1' is set then db2 WILL look in the path for
    logarchmeth2 and attempt to retrieve the files from there.
    

Local fix

  • 1)You can specify the path to the log files in the 'overflow log
    path in the rollforward statement.
    
    2)You can update the DB CFG parameter of OVERFLOWLOGPATH to be
    the location for the logarchmeth2 path. (FULL PATH NEEDE)
    
    3)You can update the DB CFG parameter for LOGARCHMETH1 to a
    valid path.  This will cause DB2 to look in the LOGARCHMETH2
    path for files and enable it to retrieve the archived log files.
    

Problem summary

  • IF LOGARCHMETH2 ONLY IS SPECIFIED A ROLLFORWARD CAN FAIL WITH
    SQL4970N
    

Problem conclusion

  • In V8.1-8.2 if archival logging is enabled and ONLY
    'logarchmeth2' is specified a ROLL-FORWARD operation will NOT
    attempt to retrieve the logs from the logarchmeth2 path.
    A SQL4970N may be received:
    
    SQL4970N Roll-forward recovery on database "<name>" cannot reach
              the specified stop point (end-of-log or point-in-time)
              because of missing or corrupted log file(s) on
              database partition(s) "<database-partition-list>".
              Roll-forward recovery processing has halted on log
              file
              "<log-file>".
    
    If 'logarchmeth1' is set then db2 WILL look in the path for
    logarchmeth2 and attempt to retrieve the files from there.
    

Temporary fix

  • 1)You can specify the path to the log files in the 'overflow log
    path in the rollforward statement.
    
    2)You can update the DB CFG parameter of OVERFLOWLOGPATH to be
    the location for the logarchmeth2 path. (FULL PATH NEEDE)
    
    3)You can update the DB CFG parameter for LOGARCHMETH1 to a
    valid path.  This will cause DB2 to look in the LOGARCHMETH2
    path for files and enable it to retrieve the archived log files.
    

Comments

APAR Information

  • APAR number

    LI73399

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-04-30

  • Closed date

    2009-05-01

  • Last modified date

    2009-05-01

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

    LI73327

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

Fix information

  • Fixed component name

    DB2 UDE ESE LIN

  • Fixed component ID

    5765F4104

Applicable component levels

  • R910 PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 October 2021