MQSeries.net :: View topic

vizwind · Posted: Wed Mar 31, 2004 6:36 pm Post subject:

Here are the software that I used:
1. IBM Websphere MQ Integrator v2.1 Sun Solaris
2. MQSeries v5.0
3. DB2 v8.1
4. Solaris v5.9

I have created the MQSIBRDB database and started the database. The userid and password for database connection are also correct. but when I run the following command line:

mqsicreatebroker MQSI_SAMPLE_BROKER -i mqsiuid -a mqsipw
-q MQSI_SAMPLE_QM -n MQSIBKDB -u <database user ID> -p <database password>

I get the following message:
AMQ8110: MQSeries queue manager already exists.
MQSeries 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.
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 'IM004'; Native Error Code '0'; Error Text '[MERANT][ODBC lib] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed'.
The error has the following diagnostic information: SQL State 'IM004' SQL Native Error Code '0' SQL Error Text '[MERANT][ODBC lib] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed'
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.

And the following is the log:
ppid=18382:pid= 4c64:1 ENTER SQLSetEnvAttr
SQLHENV 0x00176d80
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 3
SQLINTEGER 0

ppid=18382:pid= 4c64:1 EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS)
SQLHENV 0x00176d80
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 3
SQLINTEGER 0

ppid=18382:pid= 4c64:1 ENTER SQLAllocConnect
HENV 0x00176d80
HDBC * 0x00176f70

ppid=18382:pid= 4c64:1 EXIT SQLAllocConnect with return code 0 (SQL_SUCCESS)
HENV 0x00176d80
HDBC * 0x00176f70 ( 0x00174688)

ppid=18382:pid= 4c64:1 ENTER SQLSetEnvAttr
SQLHENV 0x00176d80
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 3
SQLINTEGER 0

ppid=18382:pid= 4c64:1 EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS)
SQLHENV 0x00176d80
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 3
SQLINTEGER 0

ppid=18382:pid= 4c64:1 ENTER SQLAllocConnect
HENV 0x00176d80
HDBC * 0x00176f70

ppid=18382:pid= 4c64:1 EXIT SQLAllocConnect with return code 0 (SQL_SUCCESS)
HENV 0x00176d80
HDBC * 0x00176f70 ( 0x00174688)

ppid=18382:pid= 4c64:1 ENTER SQLSetConnectOption
HDBC 0x00174688
UWORD 102
HDBC 0x00174688
UCHAR * 0xffbfba64 [ -3] "MQSIBRDB"
SWORD -3
UCHAR * 0xffbfba40 [ -3] "ppta"
SWORD -3
UCHAR * 0xffbfb764 [ -3] "******"
SWORD -3

ppid=18382:pid= 4c64:1 ENTER SQLConnectW
HDBC 0x00174688
WCHAR * 0x00169ae8 [ -3] "MQSIBRDB"
SWORD -3
WCHAR * 0x001741f8 [ -3] "ppta"
SWORD -3
WCHAR * 0xffbfb6d4 [ -3] "******"
SWORD -3

ppid=18382:pid= 4c64:1 EXIT SQLConnectW with return code -1 (SQL_ERROR)
HDBC 0x00174688
WCHAR * 0x00169ae8 [ -3] "MQSIBRDB"
SWORD -3
WCHAR * 0x001741f8 [ -3] "ppta"
SWORD -3
WCHAR * 0xffbfb6d4 [ -3] "****"
SWORD -3

ppid=18382:pid= 4c64:1 EXIT SQLConnect with return code -1 (SQL_ERROR)
HDBC 0x00174688
UCHAR * 0xffbfba64 [ -3] "MQSIBRDB"
SWORD -3
UCHAR * 0xffbfba40 [ -3] "ppta"
SWORD -3
UCHAR * 0xffbfb764 [ -3] ""
SWORD -3
:q
SWORD 1024
SWORD * 0xffbfb6de

Some guy says it need to switch to the alternative (non-Unicode) ODBC library(libdb2_36.so). Is this true? If so, where can I get this libdb2_36.so file? Can anyone help me? Thanks very much.