| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Migrating from 6.0 to 6.1 with 32bit config db (DB2) |
« View previous topic :: View next topic » |
| Author |
Message
|
| jonasb |
 Posted: Thu Jan 31, 2008 2:07 am Post subject: Migrating from 6.0 to 6.1 with 32bit config db (DB2) |
 |
|
Apprentice
Joined: 20 Dec 2006
Posts: 49
Location: Sweden
|
I'm trying to migrate a version 6.0 broker to a version 6.1 on AIX 5.3.
The configuration db is running on db2 8.2 (32 bit).
After having read that broker is now running on 64 bit on AIX, I'm trying to figure out how to make the migration program to connect to the
configuration db (32 bit).
I have set ODBCINI and the corresponding file (using the sample files in the documentation as template).
The error below indicates connection/driver error (IM004) but i can't figure it out. ** Every suggestion appreciated. **
I also read this (slightly disturbing) text:
"4. Check the readme.html file for your product to check whether a fix pack or other fix is required. DB2 Version 8.2 is functionally equivalent to Version 8.1 FixPak 7. If you connect to DB2 Version 8.2 with a broker that operates in 64-bit mode, you must specify that you want to create a 64-bit database instance. If you use DB2 Version 9.1, a 64-bit instance is the default instance created on 64-bit operating systems."
If you really need to run 64-bit config db on MB6.1, how do I migrate a broker with my existing (32bit) db?
************
$ mqsimigratecomponents FTFSWS08T_BRK
BIP8849I: Broker 'FTFSWS08T_BRK' (Version 6.0) with Queue Manager 'FTFSWS08T' and Data Source 'SWS08TMB' specified for migration.
BIP8040E: Unable to connect to the database.
BIP2321E: Database error: ODBC return code '-1'.
The message broker encountered an error whilst executing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database pertaining to this error.
Use the following messages to determine the cause of the error. This is likely to be such things as incorrect datasource or table names. Then correct either the database or message broker configuration.
BIP2322E: Database error: SQL State ''IM004''; Native Error Code '0'; Error Text ''[DataDirect][ODBC lib] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed''.
The error has the following diagnostic information: SQL State ''IM004'' SQL Native Error Code '0' SQL Error Text ''[DataDirect][ODBC lib] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed''
This message may be accompanied by other messages describing the effect on the message broker itself. Use the reason identified in this message with the accompanying messages to determine the cause of the error.
BIP8851S: Migration Failed
One of the migration steps failed, please see messages above for more details.
_________________
contact admin |
|
| Back to top |
|
 |
| jonasb |
| Posted: Fri Feb 01, 2008 3:17 am Post subject: A (good?) solution |
|
|
Apprentice
Joined: 20 Dec 2006
Posts: 49
Location: Sweden
|
I came up with a solution:
By creating an 64 bit client instance (using db2icrt) I could access the 32 bit broker config db with the migration tool.
However, I ran into other problems.
I do not know if they are linked with the solution i came up with or not.
After restart of the server it seemed slow. We have 7 execution groups configured, but there were more than 100 (!) copies running at the server when i ran the ps command.
Just after the ps command I ran out of virtual memory on the machine. I could not change user or issue any broker command, due to low memory. Fortunately, I could save the situation by typing a bunch of kill -9 commands (using the list that the "ps -ef" had produced just before).
I did not risk starting the broker again. I dropped and recreated the entire (relatively small) domain.
_________________
contact admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
