IBM Support

IY88589: SQL1042C ON CONNECT OR ACTIVATE OR CRASH RECOVERY OF A DATABASE WITH " UNEXPECTED SIZE FOR <LOGFILE> " MESSAGE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • SQL1042C error when connecting / activating a database, or on
    crash recovery with the following error seen in the db2diag.log:
    .
    2006-03-22-17.58.04.357822-300 I273737A476       LEVEL: Error
    PID     : 23755                TID  : 1          PROC : db2loggr
    INSTANCE:                      NODE : 002        DB   :
    FUNCTION: DB2 UDB, data protection, sqlpgInitRecoverable,
              probe:5520
    MESSAGE : Unexpected size for S0000044.LOG, PageCount 3047
              ExtSize 5120
              actualFileSize:
    DATA #1 : Hexdump, 8 bytes
    0xFFFFFFFF7FFFD250 : 0000 0000 00BE 7000
    .
    2006-03-22-17.58.04.411155-300 I274381A408       LEVEL: Error
    PID     : 23755                TID  : 1          PROC : db2loggr
    INSTANCE:                      NODE : 002        DB   :
    FUNCTION: DB2 UDB, data protection, sqlpgLoggrInit, probe:430
    RETCODE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic
              Error"
              DIA8526C A fatal error occurred in data protection
              services.
    .
    The log that is mentioned in the sqlpgInitRecoverable message
    (refer above for an example) is a valid truncated log.  The
    3 values - PageCount, ExtSize, and actualFileSize - are
    valid.
    PageCount = 3047
    -> 3047 * 4096(size of one page) = 12480512 bytes
    ExtSize = 5120 (should be equal to LOGFILSIZ)
    actualFileSize = 0xBE7000 = 12480512 bytes
    The file size of the log file as seen in a directory
    listing (e.g., ls -l) matches the actualFileSize value and
    the byte-value equivalent of PageCount.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * all                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description section above.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 V9.1 FP11 or newer fix pack.                  *
    ****************************************************************
    Users affected: All.
    Problem description: as above.
    Problem summary: as above.
    

Problem conclusion

  • Problem was first fixed in Version 9.1 Fix Pack 1 (s061104).
    

Temporary fix

Comments

APAR Information

  • APAR number

    IY88589

  • Reported component name

    DB2 UDB ESE SOL

  • Reported component ID

    5765F4102

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-08-18

  • Closed date

    2006-12-20

  • Last modified date

    2012-06-18

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

    IY83275

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

Modules/Macros

  • ENGN_SQP
    

Fix information

  • Fixed component name

    DB2 UDB ESE SOL

  • Fixed component ID

    5765F4102

Applicable component levels

  • R910 PSN

       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:
08 January 2022