home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC67603 Status: Geschlossen

AFTER A DATABASE RESTORE, PATH TO LOG FILE CHANGES TO THE DEFAULT
PATH

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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
verfügbare FixPacks:
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

Lösung
AFTER A DATABASE RESTORE, PATH TO LOG FILE CHANGES TO THE 
 
DEFAULT PATH
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC68006 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.04.2010
25.05.2010
25.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList