|
Problem IC91779
|
Status: Closed |
A TABLE SPACE BACKUP DOESN'T RESPONSE INTERRUPT FROM "CTROL+C" OR "FORCE APPLICATION". |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
A tables pace backup that can be a independent table space
backup or part of a database backup, doesn't response interrupt
from "Ctrol+C" or "force application", before current table
space backup is done.
If size of a table space being backup is very big and current
table space 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 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* A tables pace backup that can be a independent table space *
* backup or part of a database backup, doesn't response *
* interrupt *
* from "Ctrol+C" or "force application", before current table *
* space backup is done. *
* *
* If size of a table space being backup is very big and *
* current *
* table space 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 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V101FP3 or higher version. *
**************************************************************** |
| Local Fix: |
N/A |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Fixed on DB2 V101FP3 or higher version. |
| Workaround |
N/A |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.04.2013
04.11.2013
04.11.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
