IC91006: SERVER DEADLOCKS AFTER A FALSE CHECKPOINT COMPLETION

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • In solidDB V6.5, when creating a checkpoint, the checkpoint
    flushing times out. However, only a second later, solidDB
    returns a message that a checkpoint creation has completed,
    although there might have been almost a million pages to be
    flushed. The false completion of the checkpoint might lead to a
    deadlock.
    
    2013-02-25 15:10:32 Checkpoint DBE flushing timed out, 793081 of
    793081 pages left.
    
    2013-02-25 15:10:33 Checkpoint creation completed
    2013-02-25 15:10:33 Checkpoint creation started
    2013-02-25 15:48:18 Checkpoint not started; denied by user
    callback.
    2013-02-25 15:48:18 Checkpoint not started; denied by user
    callback.
    
    
    When you try to restart the server, the startup fails with the
    following type of error. The database file is corrupted, most
    likely due to the unfinished checkpoint flushing.
    
    ------------------------------------------------------------
    2013-02-25 15:51:20
    Version: 6.5.0.5 Build 2011-03-01
    Operating system: Windows NT 6.1 AMD64 64bit MT
    IBM solidDB - Version 6.5.0.5 Build 2011-03-01 (Windows NT 6.1
    AMD64 64bit MT)
    Copyright Oy International Business Machines Ab 1993, 2011.
    Using license file C:\Solid\solid.lic
    IBM solidDB 6.5
    Current working directory changed to d:\Database\solid
    Using configuration file d:\Database\solid\solid.ini
    2013-02-25 15:51:22 IBM solidDB process has encountered an
    internal error and is unable to
    continue normally. The database file is incomplete or corrupt.
    If the file is on a hot
    standby secondary server, use the 'hotstandby copy' or
    'hotstandby netcopy'
    command to send the file from the primary server again. If you
    use the
    'hotstandby' command, make sure that
    2013-02-25 15:51:22 Server emergency shutdown.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users.                                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to IBM solidDB V6.5 Fix Pack 13.                     *
    ****************************************************************
    

Problem conclusion

  • Fix is included in IBM solidDB V6.5 Fix Pack 13.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC91006

  • Reported component name

    SOLIDDB-DB2/IDS

  • Reported component ID

    5724V1700

  • Reported release

    650

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-03-21

  • Closed date

    2013-03-21

  • Last modified date

    2013-03-21

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

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

    IC91007

Fix information

  • Fixed component name

    SOLIDDB-DB2/IDS

  • Fixed component ID

    5724V1700

Applicable component levels

  • R650 PSY

       UP

  • R700 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

IBM solidDB

Software version:

650

Reference #:

IC91006

Modified date:

2013-03-21

Translate my page

Machine Translation

Content navigation