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 IC83336 Status: Geschlossen

Upgrade database via restore may fail with sqlcode SQL1088W

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
The RESTORE command with implicit upgrade can fail if the 
database configuration parameter logsecond is set below 10. 
During upgrade, logsecond may need to be increased to 10 
temporarily, and updating the logsecond db cfg parameter without 
a connection to the database should be allowed. However, if you 
are upgrading via restore, such update to a db cfg parameter is 
prohibited. 
 
You may see the following error message when trying to 
restore a database requiring upgrade. 
 
db2 "restore db sample" 
SQL2517W  The database was restored and then upgraded to the 
current release. 
The database upgrade returned sqlcode "1088" and tokens "*N". 
 
Another side effect of this problem is that UPGRADE DATABASE 
command can fail with SQL1088W if LOGPRIMARY is set above 246. 
 
 db2 "upgrade db sample" 
SQL1088W  The database was created or upgraded successfully but 
an error 
occurred while binding the utilities.  The utilities are not 
bound to the 
database. 
 
 db2 connect to sample 
 
   Database Connection Information 
 
 Database server        = DB2/LINUXX8664 9.7.5 
 SQL authorization ID   = DB2V91 
 Local database alias   = SAMPLE 
 
 
 db2 list tables for all 
SQL0204N  "SYSCAT.TABLES" is an undefined name.  SQLSTATE=42704 
 
The database upgrade may appear to have completed successfully 
with a warning, however, many of the system objects were 
actually not recreated during the upgrade. 
 
You may find the below messages in db2diag.log: 
 
From logs: 
2012-06-04-08.58.46.498528-300 I209882E854         LEVEL: Severe 
PID     : 12776                TID  : 46912933718336PROC : 
db2sysc 0 
INSTANCE: db2v91               NODE : 000          DB   : SAMPLE 
APPHDL  : 0-8                  APPID: *LOCAL.db2v91.120604135734 
AUTHID  : DB2V91 
EDUID   : 16                   EDUNAME: db2agent (SAMPLE  ) 0 
FUNCTION: DB2 UDB, base sys utilities, db2spcat, probe:324 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -5153   sqlerrml: 
30 
 sqlerrmc: logprimary + logsecond <= 256 
 sqlerrp : SQL09075 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
2012-06-04-08.58.48.402859-300 I210737E687         LEVEL: 
Warning 
PID     : 13152                TID  : 46912563643232PROC : db2bp 
INSTANCE: db2v91               NODE : 000 
APPID   : *LOCAL.db2v91.120604135734 
FUNCTION: DB2 UDB, base sys utilities, sqlescdb, probe:145 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: 1088   sqlerrml: 0 
 sqlerrmc: 
 sqlerrp : SQL09075 
 sqlerrd : (1) 0xFFFFFFFF      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate:
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v97 fixpack 6.                                    * 
****************************************************************
Local-Fix:
Ensure database configuration parameter logprimary is set to 246 
or lower and logsecond set to 10 or higher prior to the database 
upgrade or restore.
verfügbare FixPacks:
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Migration via restore no longer fails when upgrading to v97 
fixpack 6.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
10.05.2012
05.06.2012
05.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.,
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList