| Author |
Message
|
| mk |
 Posted: Tue Jun 23, 2009 9:16 am Post subject: [SOLVED] ODBC Error while creating broker |
 |
|
Novice
Joined: 27 Feb 2009
Posts: 21
|
Hi Guys!
I've been busy today trying to set up a remote connection from a WMB 6.1 Broker to a DB2 V9.5 server. Both nodes are running on HP-UX 11iv3 and I have installed the DB2 Runtime Client on the Broker node.
I have configured and catalogued the remote database, set the correct svcename, set the DB2COMM registry variable, checkt /etc/services for the correct values and CAN connect to the remote DB2 database by using DB2's CLI 
But when I'm trying to connect to this database during the broker creation I always get the following error.
| Quote: |
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.
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 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 ''402''; Native Error Code '0'; Error Text ''523 400''.
The error has the following diagnostic information: SQL State ''402'' SQL Native Error Code '0' SQL Error Text ''523 400''
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.
BIP8040E: Unable to connect to the database.
The database cannot be accessed with the specified user Id and password pair.
- Check that the database is running.
- On Windows, check that an ODBC connection has been created.
- On systems that use $ODBCINI, check that the file pointed to by $ODBCINI has been correctly updated.
- Use mqsichangebroker brokername -a xxx to set the password to the correct value and try again.
Use mqsichangeconfigmgr configmgr -a xxx to set the password to the correct value and try again.
- Check that the database has an adequate number of database connections available for use.
|
My odbc64.ini file looks like this:
| Quote: |
[ODBC Data Sources]
BRK1DB=IBM DB2 ODBC Driver
ORACLEDB=DataDirect 5.3 64bit Oracle Wire Protocol
ORACLERACDB=DataDirect 5.3 64bit Oracle Wire Protocol (Real Application Clusters)
SYBASEDB=DataDirect 5.3 64bit Sybase Wire Protocol
SYBASEDBUTF8=DataDirect 5.3 64bit Sybase UTF8 Wire Protocol
###########################################
###### Individual data source stanzas #####
###########################################
# DB2 stanza
[BRK1DB]
DRIVER=libdb2Wrapper.so
#Driver=/home/db2inst1/sqllib/lib64/libdb2.so
Description=Remote Broker Database
Database=BRK1DB |
Any help is really appreciated since I have no further idea what to to... 
Last edited by mk on Sun Jul 05, 2009 2:24 am; edited 1 time in total |
|
| Back to top |
|
 |
| mymq |
| Posted: Tue Jun 23, 2009 7:28 pm Post subject: |
|
|
Centurion
Joined: 01 Mar 2007
Posts: 101
Location: US-Greenwille
|
did u check with any DB2 administrator on your UNIX server settings with respect to remote DB connection
_________________
--SRK-- |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Tue Jun 23, 2009 10:44 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
This is likely to be such things as incorrect datasource or table names
before executing the broker commands
What i suggest you is
there is an utility isql available in UNIX, Please use this and test the DB connectivity
where you have to pass the user id , Password and DSN values in the utility
Try out this
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| mk |
| Posted: Tue Jun 23, 2009 11:19 pm Post subject: |
|
|
Novice
Joined: 27 Feb 2009
Posts: 21
|
Thanks for your answers.
This is only a test environment because we have limited experience with this combination. So there is no DB2 admin that could assist me...
Regarding isql: Do I need to install any additional software? I can't find isql on my hp-ux machine. |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Tue Jun 23, 2009 11:22 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| mk wrote: |
| Regarding isql: Do I need to install any additional software? I can't find isql on my hp-ux machine. |
Did you try out by just executing isql it usually comes along with the OS
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| mk |
| Posted: Wed Jun 24, 2009 12:59 am Post subject: |
|
|
Novice
Joined: 27 Feb 2009
Posts: 21
|
|
| Back to top |
|
|
| mk |
| Posted: Sun Jul 05, 2009 2:22 am Post subject: solved |
|
|
Novice
Joined: 27 Feb 2009
Posts: 21
|
I finally got it to work... After spending hours trying to figure out if I missed any ODBC/db2cli configurations I found out that I specified the wrong driver in the odbc64.ini.
After specifying the whole path /opt/IBM/mqsi/6.1/lib/libdb2Wrapper.so it worked.
 |
|
| Back to top |
|
|
|
|
