| Author |
Message
|
| ngupta |
 Posted: Tue Aug 29, 2006 11:08 am Post subject: Migration of WBI 5.0 to WBI 6.0 |
 |
|
Newbie
Joined: 07 Aug 2006
Posts: 9
|
We are in the process of migrating from WBI 5.0 to WBI 6.0.
My broker is running on unix platform(Version of solaris is 9.0). Can anyone please let me know what steps to follow in migration of broker and configration manager. I have gone with the migration document by IBM, but lots of things are not clear.
Thanks |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Aug 29, 2006 1:56 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What specific things aren't clear?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ngupta |
| Posted: Thu Aug 31, 2006 11:11 am Post subject: |
|
|
Newbie
Joined: 07 Aug 2006
Posts: 9
|
Migration of Broker :
1) One of my broker is running on Unix environment. According to migration document, we can install 6.0 on the same location as 5.0. I have still not tested this? If anyone has migrated in Unix environment please let me know.
2) Other broker is running on Windows. According to migration document, I am installing Configuration Manager and toolkit in different directory. But I dont know what about Broker ? Do I need to install on the same location(5.0) or different location along with Configration Manager and toolkit.
Please suggest.
Thanks |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Aug 31, 2006 11:18 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
For your #1 - you just want someone to say "I did it on Unix and it worked"? Why wait? Why not test it yourself on the development server that of course you have for just such things.
As to your #2 - is it possible to install Broker into a different directory than Configuration Manager?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ngupta |
| Posted: Fri Sep 01, 2006 11:25 am Post subject: |
|
|
Newbie
Joined: 07 Aug 2006
Posts: 9
|
I have successfully migrted WBI Toolkit 6.0 and at present my broker and config manager with 5.0 version are working fine with 6.0 toolkit.
Now I am planning to migrate ConfigMgr 5.0 to 6.0. I have done the following :
1) Installed 6.0 Config manager on different directory as 5.0 Config manager. It is successfully installed.
2) Stopped the config manager.
3) When I am giving this command I am getting the following error:
C:\IBM\MQSI\6.0>mqsimigratecomponents ConfigMgr -c
BIP8674I: Configuration Manager 'ConfigMgr' (Version 5.0) specified for migration.
BIP8040E: Unable to connect to the database.
BIP8040E: Unable to connect to the database.
BIP8681W: Pre-migration check failed.
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 obtaine
d 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 ''08001''; Native Error Code '-30082'; Error Text ''[IBM][CLI Driver] SQL30082N Attempt to establish connection failed with
security reason "3" ("PASSWORD MISSING"). SQLSTATE=08001 ''.
The error has the following diagnostic information: SQL State ''08001'' SQL Native Error Code '-30082' SQL Error Text ''[IBM][CLI
Driver] SQL30082N Attempt to establish connection failed with security reason "3" ("PASSWORD MISSING"). SQLSTATE=08001 ''
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 accomp
anying messages to determine the cause of the error.
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 obtaine
d 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 ''08001''; Native Error Code '-30082'; Error Text ''[IBM][CLI Driver] SQL30082N Attempt to establish connection failed with
security reason "3" ("PASSWORD MISSING"). SQLSTATE=08001 ''.
The error has the following diagnostic information: SQL State ''08001'' SQL Native Error Code '-30082' SQL Error Text ''[IBM][CLI
Driver] SQL30082N Attempt to establish connection failed with security reason "3" ("PASSWORD MISSING"). SQLSTATE=08001 ''
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 accomp
anying messages to determine the cause of the error.
BIP8040E: Unable to connect to the database.
The database cannot be accessed with the userid and password that were specified when the broker was created.
Check that the database is running, that an ODBC connection has been created and that the userid and password pair specified for ODBC connect on the mqsicreate
command are capable of being used to connect to the database using an ODBC connection. Also ensure that the database has a adequate number of database connectio
ns available for use.
Note : I am able to connect to the database, the user name and password are correct.
Please advice |
|
| Back to top |
|
|
|
|
