|
Problem IC66605
|
Status: Closed |
MIGRATION MAY FAIL WITH SQL1224N WHEN REGISTRY VARIABLE DB2_MEMORY_PROTECT IS SET |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Database migration will fail with SQL1224N and the database will
trap with signal #11, when registry variable
DB2_MEMORY_PROTECT is set to YES.
Migration using restore or migrate database, may fail with this
error:
db2 "restore database sample from /backup taken at
20100115142750"
SQL2519N The database was restored but the restored database was
not upgraded to the current release. Error "-1224" with tokens
"-2097151964 * * * *SEMAPHORE WAIT "
is returned.
2010-01-12-16.36.23.398082-420 I8535888A483 LEVEL: Warning
PID : 454904 TID : 3373 PROC : db2sysc
0
INSTANCE: sample NODE : 000 DB : sample
APPHDL : 0-15 APPID: *LOCAL.xx
AUTHID : sample
EDUID : 3373 EDUNAME: db2agent (PVSS001D) 0
FUNCTION: DB2 UDB, catalog migration, sqlrlmDatapart, probe:6193
DATA #1 : <preformatted>
End migrating catalog table: SYSDATAPARTITIONS
2010-01-12-16.36.23.437718-420 I8536372A485 LEVEL: Warning
PID : 454904 TID : 3373 PROC : db2sysc
0
INSTANCE: sample NODE : 000 DB : sample
APPHDL : 0-15 APPID: *LOCAL.xx
AUTHID : sample
EDUID : 3373 EDUNAME: db2agent (PVSS001D) 0
FUNCTION: DB2 UDB, catalog migration, sqlrlm_catalog_migrate,
probe:4945
DATA #1 : <preformatted>
Begin migrating catalog table: SYSTABLES
2010-01-12-16.36.23.670411-420 I8536858A566 LEVEL: Error
PID : 454904 TID : 3373 PROC : db2sysc
0
INSTANCE: sample NODE : 000 DB : sample
APPHDL : 0-15 APPID: *LOCAL.xx
AUTHID : sample
EDUID : 3373 EDUNAME: db2agent (PVSS001D) 0
FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh,
probe:1
MESSAGE : Error in agent servicing application with coor_node:
DATA #1 : Hexdump, 2 bytes
0x070000000C408780 : 0000
Stacks:
Signal #11 Timestamp 2010-01-12-16.36.23.573833
0 sqlrlm_catalogFixup
1 sqlrlm_catalog_migrate
2 sqlefmig
3 sqlemigr
4 sqlemigr
5 sqeApplication::AppLocalStart
6 sqlelostWrp
7 sqleUCengnInit
8 sqleUCagentConnect
9 sqljsConnectAttach |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* You may hit the issue if DB2_MEMORY_PROTECT *
****************************************************************
* PROBLEM DESCRIPTION: *
* Database crashes during migration when DB2_MEMORY_PROTECT *
* isset. *
****************************************************************
* RECOMMENDATION: *
* If you have this registry set please upgrade to Fixpack *
* 2prior to migration. *
**************************************************************** |
| Local Fix: |
|
| 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 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 Fix Pack 2 |
| Workaround |
Please unset the DB2_MEMORY_PROTECT before migration and you
could set this back once migration is complete. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.02.2010
10.06.2010
10.06.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
|
 |
