|
Problem IC67603
|
Status: Closed |
AFTER A DATABASE RESTORE, PATH TO LOG FILE CHANGES TO THE DEFAULT PATH |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
During a database restore, if DB2 is unable to use the log path
specified by the backup image, it will switch to the default log
path i.e., under database directory. There will not be any error
reported back to the restore command, but the following messages
will be logged on db2diag.log. Here, the log path in the backup
image was /db2/SAMPLE/log_dir/NODE0000, but on the system, only
the directory path /db2/SAMPLE/log_dir exists i.e., there is no
NODE0000 directory.
2010-03-20-09.39.29.315242-300 E1530655A520 LEVEL: Error
PID : 495694 TID : 8226 PROC : db2sysc
0
INSTANCE: db2z91 NODE : 000 DB : SAMPLE
APPHDL : 0-116 APPID: *LOCAL.db2z91.100320143828
AUTHID : DB2Z91
EDUID : 8226 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, recovery manager, sqlprlfh, probe:550
MESSAGE : ADM1700W DB2 is unable to use the log path specified
by the backup image; Switching to the default log path.
2010-03-20-09.39.29.315711-300 I1531176A461 LEVEL: Error
PID : 495694 TID : 8226 PROC : db2sysc
0
INSTANCE: db2z91 NODE : 000 DB : SAMPLE
APPHDL : 0-116 APPID: *LOCAL.db2z91.100320143828
AUTHID : DB2Z91
EDUID : 8226 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, recovery manager, sqlprlfh, probe:550
DATA #1 : <preformatted>
Unable to use path /db2/SAMPLE/log_dir/NODE0000/. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* AFTER A DATABASE RESTORE, PATH TO LOG FILE CHANGES TO *
* THEDEFAULT PATH *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 9.7 FP2 *
**************************************************************** |
| Local Fix: |
Manually create the log path before restore |
| available fix packs: |
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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 |
AFTER A DATABASE RESTORE, PATH TO LOG FILE CHANGES TO THE
DEFAULT PATH |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC68006
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.04.2010
25.05.2010
25.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
