Pls help....When I try to migrate databases from 8.2 to 9.5 command ckmigr pass trough all my instances, but when I commite command "db2 migrate database ....." in one instance response is - SQL1224N The database manager is not able to acce...pt new requests, has
terminated all requests in progress, or has terminated your particular request
due to an error or a force interrupt. SQLSTATE=55032

First instance(3 databases) migrate whit no problems. What to do?

db2diag will be having more detailed info of the error

2009-09-22-16.14.28.377000+120 I87126747H284 LEVEL: Warning
PID : 3588 TID : 3592 PROC : db2bp.exe
INSTANCE: DB2 NODE : 000
EDUID : 3592
FUNCTION: DB2 UDB, base sys utilities, sqlemgdb, probe:10
MESSAGE : Begin engn migration

2009-09-22-16.14.34.115000+120 I87127033H316 LEVEL: Warning
PID : 3588 TID : 3592 PROC : db2bp.exe
INSTANCE: DB2 NODE : 000
EDUID : 3592
FUNCTION: DB2 UDB, base sys utilities, sqlemgdb, probe:20
MESSAGE : End engn migration: with rc = -1042, sqlcode = -1042

Did you migrate the instance first?

If you're migrating to v9.5 fp3, then this can be due to APAR IZ40998:
IBM IZ40998: MIGRATION OF DATABASE TO DB2 V9.5 MAY FAIL WITH SEGMENTATION FAULTS - United States

My suggestion is to install fp4/4a and try to migrate the db again. There is another v8 - v9.5 db migration APAR fixed in fp4:
IBM JR32096: MIGRATION OF A DATABASE FROM V8.2 TO V9.5 FAILS WITH SQL1224N IF DATABASE CREATED WITH USERNAME WITH MORE THAN 8 CHARACTERS - United States

Of course!

@db2girl - thx I will try this.. First link is dead.

I try everything but......My username isn't longer then 8 characters, that is not problem... We have migrated server WSE to 9.5 whit fix 4a, and all instances. Look like I have to contact IBM!

The APARs I listed are the most frequently encountered APARs during db migration/restore to v9.5. They should not apply to you since you're already on fp4a. Good luck!

I have exactly the same problem going from 8.2 to 9.1. I have a huge db2diag.log but here is the first of it. Does anyone have any ideas on this? I have looked everywhere I can think of for an answer - short of calling IBM anyway...

2009-09-23-15.15.20.311000-240 I1H935 LEVEL: Event
PID : 3376 TID : 1812 PROC : DB2STOP.EXE
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, RAS/PD component, pdLogInternal, probe:120
START : New Diagnostic Log file
DATA #1 : Build Level, 128 bytes
Instance "DB2" uses "32" bits and DB2 code release "SQL09013"
with level identifier "01040107".
Informational tokens are "DB2 v9.1.300.257", "s070719", "WR21392", Fix Pack "3".
DATA #2 : System Info, 1564 bytes
System: WIN32_NT VRISAKITEST Service Pack 1 5.2 x86 Family 6, model 15, stepping 8
CPU: total:1 online:1 Cores per socket:4 Threading degree per core:1
Physical Memory(MB): total:2000 free:1480 available:1480
Virtual Memory(MB): total:3905 free:4875
Swap Memory(MB): total:1905 free:3395
Information in this record is only valid at the time when this file was
created (see this record's time stamp)

2009-09-23-15.15.20.311000-240 E939H541 LEVEL: Info (OS)
PID : 3376 TID : 1812 PROC : DB2STOP.EXE
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqlofindf, probe:100
MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
DIA8411C A file "" could not be found.
CALLED : OS, -, unspecified_system_function
OSERR : 2 "The system cannot find the file specified."
DATA #1 : File name, 44 bytes
D:\PROGRA~1\IBM\SQLLIB\DB2\ctrl\db2nodes.add

2009-09-23-15.15.20.343000-240 I1482H1537 LEVEL: Event
PID : 3376 TID : 1812 PROC : DB2STOP.EXE
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130
DATA #1 : String, 40 bytes
D:\PROGRA~1\IBM\SQLLIB\\bin\DB2STOP2.EXE

You're migrating to v9.1 fp3 (over 2yrs old). The APARs I listed apply to v9.5. The instance can crash for a number of different reasons (ie. defects) during migration. The only way to tell which APAR you're hitting is by reviewing the db2diag.log entries relevant to the crash (the ones you pasted are not) and any other diagnostic information (ie. trap file) generated during the crash.

My suggestion is to install the latest fixpak and try to migrate again. If the problem persists, open a pmr.

Thanks Bella - will try and see if that fixes things. I am trying to catch up on releases. We are new to the whole DB2/CM world and just a wee bit behind. Thanks for your help.