| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Failed to create a broker with 64bit DB2 with MB 6.0.0.0 |
« View previous topic :: View next topic » |
| Author |
Message
|
| zhywmj |
 Posted: Mon May 28, 2007 6:26 am Post subject: Failed to create a broker with 64bit DB2 with MB 6.0.0.0 |
 |
|
Newbie
Joined: 28 May 2007
Posts: 3
|
Hello, Everybody,
I cann't create the broker with 64bit DB2. I'm quiet sure that I already tried everything in the info center.
Firstly, I want to make sure if it is necessary to create 64 bit broker with upper level MB than MB6.0.0.0? Could you please help to make sure? Because I heared from somebody that with MB6.0.0.0, 64 bit broker shouldn't be created even if the info center describes it could be.
System Environment:
Broker Server
AIX 5300-05
WebSphere Message Broker V6.0.0.0
WebSphere MQ V6.0
DB2 Client V8.2 (64bit Instance)
$ mqsicreatebroker BK_02 -i picpesb2 -a picpesb2 -q QM_BK_02 -n DB_BK_02 -u picpesb2 -p picpesb2
AMQ8110: WebSphere MQ queue manager already exists.
WebSphere MQ queue manager running.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
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 ''78''; Native Error Code '0'; Error Text ''523 76''.
The error has the following diagnostic information: SQL State ''78'' SQL Native Error Code '0' SQL Error Text ''523 76''
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. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon May 28, 2007 6:33 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
There's no reason to do an install with just 6.0.0.0 of Broker.
Apply FP3 to go to 6.0.0.3 of Runtime.
If you're trying to match an existing system... apply the FP to that system too.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| zhywmj |
| Posted: Mon May 28, 2007 6:50 am Post subject: Failed to create a broker with 64bit DB2 |
|
|
Newbie
Joined: 28 May 2007
Posts: 3
|
hi,jefflowrey
Thanks for your quick response, actually, I will apply the patch, but tonight I need to give a report to customer, it is no time to do the update now. So I just want to know if MB6.0.0.3 could create 64 bit broker successfully, or do you have any successful experience on it? It is a little urgent. Thanks again. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon May 28, 2007 8:45 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I have no knowledge of a 64 bit broker.
There are however 64 bit execution groups...
Like Jeff said. First apply the Fix Pack.
Using a 64 bit DB should not pause a problem.
Check your ODBC/ODBC64 setup. What you have is a SQL ERROR and you need to resolve it.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| zhywmj |
| Posted: Mon May 28, 2007 11:21 pm Post subject: |
|
|
Newbie
Joined: 28 May 2007
Posts: 3
|
Hi, Buddies,
Thanks for your suggestion, now I have updated MB to 6.0.0.3, but the same error occurs. Have no idea now, do you have any experience on it, or any suggestion? Thanks a million |
|
| Back to top |
|
|
| latelatif |
| Posted: Wed May 30, 2007 2:15 am Post subject: |
|
|
Novice
Joined: 08 Feb 2006
Posts: 21
|
zhywmj
To create 64bit execution groups, the following should also be satisfied
i) Kernel = 64bit
ii) MQ = 64bit ( defaults to 64bit if your kernel is 64bit, so no additional configuration is needed. Just create a queue manager on a 64bit kernel)
iii) DB2 = 64bit (server and client if broker is connecting from a remote box)
After satisfying the above, just need to configure ODBC, ODBC64 ( yes both of them). ODBC.INI should point to 32 bit db2 driver and ODBC64.INI should point to the 64 bit driver. the infocenter shows this nicely.
LIBPATH and LIBPATH64 should also be setup. Post your
1) db2level > db2level.out
2) env > env.out
3) ODBC.INI
4)ODBC64.INI |
|
| 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
|
|
|
|
