MQSeries.net :: View topic - Broker creation problems after upgrade to WMB 6.1

gugs · Posted: Fri Mar 28, 2008 3:23 am Post subject:

We are having problems creating a Broker on a Solaris/Unix/Oracle 10g environment. When we created the broker it fails with the message below. We have checked all the .ini (posted below) files etc and everything is correct. The db software has been installed correctly and Oracle is working as expected. Has anyone had a similar problem? Any suggestions on how we can resolve the issue?

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 ''IM003''; Native Error Code '0'; Error Text ''[DataDirect][ODBC lib] Specified driver could not be loaded''.
The error has the following diagnostic information: SQL State ''IM003'' SQL Native Error Code '0' SQL Error Text ''[DataDirect][ODBC lib] Specified driver could not be loaded''
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 with the broker.
- Check that the database is running.
- On Windows check that an ODBC connection has been created.
- On systems which use $ODBCINI check that the file pointed to by $ODBCINI has been correctly updated.
- Check that the userid and password pair specified for ODBC connect on the mqsicreate or mqsichangebroker command are capable of being used to connect to the database using an ODBC connection.
- Check that the database has a adequate number of database connections available for use.

-----------------------------------------------------------------------------------
ODBCINI

[ODBC Data Sources]
BRKDB=DataDirect 5.2 Oracle

[BRKDB]
Driver=/opt/mqsi/ODBC32/V5.2/lib/UKor822.so
Description=DataDirect 5.2 Oracle
EnableDescribeParam=1
OptimizePrepare=1
ServerName=TESTDB.WORLD
WorkArounds=536870912
ProcedureRetResults=1
ColumnSizeAsCharacter=1

ODBCINI64

[ODBC Data Sources]
BRKDB=DataDirect 5.2 64bit Oracle Wire Protocol

[BRKDB]
Driver=/opt/mqsi/ODBC64/V5.2/lib/UKora22.so
Description=DataDirect 5.2 64bit Oracle Wire Protocol
HostName=testHost
PortNumber=1526
SID=TESTDB
CatalogOptions=0
EnableStaticCursorsForLongData=0
ApplicationUsingThreads=1
EnableDescribeParam=1
OptimizePrepare=1
WorkArounds=536870912
ProcedureRetResults=1
ColumnSizeAsCharacter=1
_________________
Thanks in advance