IC89684: A TABLESPACE BACKUP DOESN'T RESPONSE INTERRUPT FROM "CTROL+C" OR "FORCE APPLICATION".

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • A tablespace backup that can be an independent tablespace
    backup or part of a database backup, doesn't response interrupt
    from "Ctrol+C" or "force application", before current tablespace
    backup is done.
    
      If size of a tablespace being backup is very big and current
    tablespace backup need a long time, then "force application"
    looks like doesn't work, even if it executes successfully.
    
    1. A database backup starts.
    
    2012-11-08-20.57.35.456745-300 E23348634E471       LEVEL: Info
    PID     : 23568                TID  : 46954818038080PROC :
    db2sysc 0
    INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE
    APPHDL  : 0-45959              APPID: *LOCAL.app007.121109015723
    AUTHID  : db2inst1
    EDUID   : 42861                EDUNAME: db2agent (SAMPLE) 0
    FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl,
    probe:1604
    MESSAGE : Starting an offline db backup.
    
    2. "force application" executes successfully.
    
    db2 force application (45959)
    DB20000I  The FORCE APPLICATION command completed successfully.
    DB21024I  This command is asynchronous and may not be effective
    immediately.
    
    3. The backup can be observed by "db2pd -utilities" after hours.
    
    Database Partition 0 -- Active -- Up 10 days 15:17:52 -- Date
    2012-11-08-23.24.22.994191
    
    Utilities:
    Address            ID         Type                   State
    Invoker    Priority   StartTime           DBName   NumPhases
    CurPhase   Description
    0x000000020588D340 3195       BACKUP                 0
    0          0          Thu Nov  8 20:57:35 SAMPLE  1           1
    online  db
    
    Progress:
    Address            ID         PhaseNum   CompletedWork
    TotalWork                    StartTime           Description
    0x000000020591E4E8 3195       1          306368386855 bytes
    1610284877612 bytes          Thu Nov  8 20:57:35 E
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Please See Error Description                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 V97FP9 or higher version.                     *
    ****************************************************************
    

Problem conclusion

  • Fixed on DB2 V97FP9 or higher version.
    

Temporary fix

  • N/A
    

Comments

APAR Information

  • APAR number

    IC89684

  • 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

    2013-01-21

  • Closed date

    2014-02-04

  • Last modified date

    2014-02-04

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

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

    IC90078 IC91779

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

9.7

Reference #:

IC89684

Modified date:

2014-02-04

Translate my page

Machine Translation

Content navigation