MQSeries.net :: View topic

Roger · Posted: Mon Jun 06, 2005 8:24 am Post subject:

Looking back over the forum I have read several examples of this problem but have not managed to find the solution to my problem. My configuration will shock some and come as no surprise to others - I am unable to upgrade any element of this configuration due to the constraints of the project and sponsoring business. Basically the setup is WMQI 2.1 CSD4 with a Oracle 8i (816 merant driver). I can connect to my Oracle database with SQLPLUS and userid correctly - when I try to create my broker using this syntax:

mqsicreatebroker BMPSIS09 -i mqsi -a ******* -q BMPSIS09 -n WMQP05 -u wmqi21 -p ******* -w /var/wmqi -g 3600 -k 180

I get the following errors:

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.
BIP2321E: Database error: ODBC return code '-1'.
The message broker encountered an error whilst executing a database operation. T
he 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 t
o be such things as incorrect datasource or table names. Then correct either the
database or message broker configuration.
BIP2322E: Database error: SQL State 'HY000'; Native Error Code '12154'; Error Te
xt '[MERANT][ODBC Oracle 8 driver][Oracle 8]ORA-12154: TNS:could not resolve ser
vice name
'.
The error has the following diagnostic information: SQL State 'H
Y000' SQL Native Error Code '12154' SQL Error Text '[MERANT][ODBC
Oracle 8 driver][Oracle 8]ORA-12154: TNS:could not resolve service name
'
This message may be accompanied by other messages describing the effect on the m
essage 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 conne
ction. Also ensure that the database has an adequate number of database connections available for use.

I know some of you will recognise this old chestnut but I can assure you the tnsnames.ora file correctly maps to the database, the passwords and accounts are correct and the driver is the right one. Sorry, upgrading or migrating to WMBIMB 5 is not an option at the moment or later patches than CSD4. Any ideas, anyone? Aplogies for the length of this problem.