| Author |
Message
|
| rax1 |
 Posted: Mon May 07, 2007 1:27 am Post subject: How to have WBIMB' database on the remote machine. |
 |
|
Newbie
Joined: 07 May 2007
Posts: 5
|
Hi All,
My environment is AIX 5.3, DB2 8.2.5, WMQ 6.0.1.1 and WBIMB 6.0.0.2. DB2 admin client is installed on the broker machine and DB2 ESE on the remote machine.
I am getting error while creating the broker. The steps I followed are:
1. Create QM : testQM
2. start testQM.
3. create DB2 client instance- twsdb. ; (user- twsdb, password- twsdb)
3. create broker database MQSIBKDB in on the remote machine (user 'mqm', password 'mqm')
4. start the Db2 server instance.
5. catalog the remote db node.
6. catalog the remote db
7. check the connection by connecting the remote db from WBIMB machine.
8. There is no need to create odbc as this MQSIBKDB is by default configured.
5. create the testBroker. -> gives error.
mqsicreatebroker testBroker -i mqm -a mqm -q testQM -n MQSIBKDB -u mqm -p mqm
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 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 ''08001''; Native Error Code '-1013'; Error Text ''[IBM][CLI Driver] SQL1013N The database alias name or database name "MQSIBKDB" could not be found. SQLSTATE=42705 ''.
The error has the following diagnostic information: SQL State ''08001'' SQL Native Error Code '-1013' SQL Error Text ''[IBM][CLI Driver] SQL1013N The database alias name or database name "MQSIBKDB" could not be found. SQLSTATE=42705 ''
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 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 connections available for use.
am I missing something in the above steps?
Appreciate if anybody can suggest me how to use remote DB with broker with DB2 admin client installed at BRoker machine and DB2 server on the remote machine.
-Rax |
|
| Back to top |
|
 |
| pathipati |
| Posted: Mon May 07, 2007 8:58 am Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
| Did u catalog MQSIBKDB on local machine? |
|
| Back to top |
|
|
| master |
| Posted: Mon May 07, 2007 9:25 am Post subject: |
|
|
Guest
|
Add the database name in your local machine.
Control Panel->Administrative Tools->Data Sources(ODBC) |
|
| Back to top |
|
|
| rax1 |
| Posted: Tue May 08, 2007 5:10 am Post subject: |
|
|
Newbie
Joined: 07 May 2007
Posts: 5
|
Hi Pathipati,
| Quote: |
| 6. catalog the remote db |
I catalog the remote database at the Message broker machine. |
|
| Back to top |
|
|
| rax1 |
| Posted: Tue May 08, 2007 5:16 am Post subject: |
|
|
Newbie
Joined: 07 May 2007
Posts: 5
|
Hi Master,
The environment is AIX 5.3. The one you suggested is for Windows.  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue May 08, 2007 5:18 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Did you catalog the remote database with the alias the same name?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rax1 |
| Posted: Tue May 08, 2007 6:18 am Post subject: |
|
|
Newbie
Joined: 07 May 2007
Posts: 5
|
I cataloged the remote DB MQSIBKDB as MQSIBKDB.
To simplify the setup. I created the DB2 client instance in mqm user and then bind the database. (Initially, i was not binding the database).
The bind was successful. Next I tried creating the broker 'testBROKER' and failed again.
mqsicreatebroker testBROKER -i mqm -a mqm -n MQSIBRKDB -q testQM -u mqm -p mqm
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 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 ''IM002''; Native Error Code '0'; Error Text ''[DataDirect][ODBC lib] Data source name not found and no default driver specified''.
The error has the following diagnostic information: SQL State ''IM002'' SQL Native Error Code '0' SQL Error Text ''[DataDirect][ODBC lib] Data source name not found and no default driver specified''
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 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 connections available for use.
Am I missing something ?
-Rax |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue May 08, 2007 6:22 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Did you also create an entry in odbc.ini that is called 'MQSIBKDB'?
And one in odbc64.ini?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rax1 |
| Posted: Tue May 08, 2007 11:05 pm Post subject: |
|
|
Newbie
Joined: 07 May 2007
Posts: 5
|
| I have MQSIBRKDB defined in the ODBC.ini but not odbc64.ini. As this is a basic setting for the Broker (broker connecting to remote DB to store its data), do i still need to define odbc64.ini? (Remote DB2 instance is 64-bit). |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed May 09, 2007 1:45 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
There are various cases where you need to set up the 64bit ODBC connection.
I'd highly recommend going back to the Info Center and reading the entire instructions for connecting to databases again.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
