|
Problem IC62820
|
Status: Closed |
IF THE BACKUP DIR IS REMOVED, SQL0902C MIGHT BE RECORDED AT DIAG.LOG WHEN BACKUP ON AUTOMATED RECOVERY OBJECT REMOVAL ENABLED DB |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The db2diag.log indicates SQL0902C error like as below if DB2
cannot find the path which should include database recovery
objects to be deleted automatically.
This message in db2diag.log is harmless one, the commands which
cause this message run successfully.
.
2008-12-15-02.14.07.264693+540 I120085G729 LEVEL: Error
PID : 11150 TID : 3077565344 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-530 APPID:
*LOCAL.db2inst1.081214171115
AUTHID : db2inst1
EDUID : 19 EDUNAME: db2agent (SAMPLE)
FUNCTION: DB2 UDB, database utilities, sqluhDiskDelete,
probe:949
MESSAGE : SQL0902C A system error (reason code = "") occurred.
Subsequent SQL
statements cannot be processed.
DATA #1 : String, 30 bytes
Error returned by disk delete.
DATA #2 : String, 67 bytes
/backup/test/SAMPLE.0.db2inst1.NODE0000.CATN0000.20080725192217.
001
DATA #3 : ZRC, PD_TYPE_ZRC, 4 bytes
0x870F0011 (= SQLO_PATH)
.
2008-12-15-02.14.07.290339+540 E114434G516 LEVEL: Error
PID : 11150 TID : 3077565344 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-530 APPID:
*LOCAL.db2inst1.081214171115
AUTHID : MNT01
EDUID : 19 EDUNAME: db2agent (SAMPLE)
FUNCTION: DB2 UDB, database utilities,
sqluhPruneHistoryDeleteFile, probe:1082
MESSAGE : ADM8507N Unable to delete the backup image with
timestamp
"20080725192217".
.
The steps below illustrate one of the scenario to cause this
peoblem:
.
db2sampl
db2 update db cfg for sample using NUM_DB_BACKUPS 1
REC_HIS_RETENTN 1 AUTO_DEL_REC_OBJ ON
mkdir /tmp/sample
db2 backup db sample to /tmp/sample
<after 2 days>
rm -R /tmp/sample
db2 backup db sample to /tmp |
| Problem Summary: |
User Affected: Those using automated recovery object removal
Problem Description: If the backup directory has been removed,
SQL0902N can be reported when automated backup attempts to
remove the object.
Problem Summary: See above |
| Local Fix: |
Users can suppress this error messages by either of followings:
a) PRUNE HISTORY to delete history file entries include
nonexistent path.
$ db2 prune history 200807251930
.
b) Create the PATH where the backup images were located.
$ mkdir /backup/test |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 FixPak 1 |
| Workaround |
Users can suppress this error messages by either of following
a) PRUNE HISTORY to delete history file entries include
nonexistent path.
$ db2 prune history 200807251930
.
b) Create the PATH where the backup images were located.
$ mkdir /backup/test |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.08.2009
22.01.2010
22.01.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
