IBM Support

IC70207: INVALID OVERFLOW LOG PATH (OVERFLOWLOGPATH) CAUSING DB2 BACKUP TO FAIL WITH SQL2428N.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Invalid path condition on the log overflow path results in
    terminating the attempt to find the log file rather than
    checking the log archive path as it would in the SQLO_FNEX (file
    not found) case.
    This should be corrected as the log archive path is checked if
    the overflowlogpath exists.
    

Local fix

  • Deactivate and reactivate the database so that db2 realizes the
    overflowpath defined in the dbcfg is not present and does not
    attempt to use it.  Or create the overflowlogpath manually.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 users on all hardware                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Invalid path condition on the log overflow path results in   *
    *                                                              *
    * terminating the attempt to find the log file rather than     *
    *                                                              *
    * checking the log archive path as it would in the SQLO_FNEX   *
    * (file                                                        *
    * not found) case.                                             *
    *                                                              *
    * This should be corrected as the log archive path is checked  *
    * if                                                           *
    * the overflowlogpath exists.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * upgrade to this fix.  In addition see work around in APAR    *
    * information.  Manually creating the expected overflowpath,   *
    * or activating and deactivating the database so db2 realizes  *
    * the overvlowpath does not exist.                             *
    ****************************************************************
    

Problem conclusion

  • This problem is resolved by the fix, in that the file will now
    be looked for on the archive path if the overflowpath does not
    exist.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC70207

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-07-26

  • Closed date

    2011-06-07

  • Last modified date

    2011-06-07

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

    IC66455

  • 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

  • R970 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":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
07 June 2011