|
Problem IC77415
|
Status: Closed |
DATABASE CATALOG MIGRATION TO DB2 V9.7 MAY FAIL WITH SQL0912N IF LOCKLIST CONFIGURATION IS VERY LOW |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
A database migration to DB2 Version 9.7 may fail with error
SQL0912N. This can happen if the locklist database configuration
parameter is set to a very low value, for example (LOCKLIST) =
AUTOMATIC(25) pages.
A typical error that is seen during implicit migration:
db2 "RESTORE DATABASE MYDB FROM 'C:\Program Files\IBM\temp' ON
C: INTO NEWDB"
SQL2519N The database was restored but the restored database
was not upgraded to the current release.
Error "-912" with tokens "*N" is returned.
and in db2diag.log you should find messages like this:
2011-05-25-15.51.32.381000+120 I1201435F313 LEVEL: Warning
PID : 644 TID : 4576 PROC :
db2bp.exe
INSTANCE: DB2 NODE : 000
APPID : *LOCAL.DB2.110525134946
EDUID : 4576
FUNCTION: DB2 UDB, base sys utilities, sqlemgdb, probe:30
MESSAGE : Begin db2spcat
2011-05-25-15.51.40.256000+120 I1201750F815 LEVEL: Severe
PID : 1028 TID : 1288 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : OO
APPHDL : 0-86 APPID: *LOCAL.DB2.110525134946
AUTHID : ADMINISTRATOR
EDUID : 1288 EDUNAME: db2agent (OO ) 0
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary
logging func, probe:0
MESSAGE : SYS_VIEWS: sqlcode
DATA #1 : Hexdump, 57 bytes
0x00000000303D3DB0 : 4372 6561 7465 2053 5953 5445 4D20 5649
Create SYSTEM VI
0x00000000303D3DC0 : 4557 2053 5953 4341 542E 574F 524B 4143
EW SYSCAT.WORKAC
0x00000000303D3DD0 : 5449 4F4E 5320 6661 696C 6564 2077 6974
TIONS failed wit
0x00000000303D3DE0 : 6820 7263 3D2D 3931 32
h rc=-912
A typical error symptom of that problem is that a SYSTEM VIEW
can not be created because DB2 run out of locklist memory during
migration. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Problem Description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 5. *
**************************************************************** |
| Local Fix: |
Increase locklist size manually and retry the migration. |
| available fix packs: |
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 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
|
| Solution |
First fixed in Version 9.7 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.07.2011
16.12.2011
16.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
