Author |
Message
|
bdrummond |
Posted: Thu Dec 20, 2007 3:02 am Post subject: Oracle upgrade errors |
|
|
Disciple
Joined: 06 May 2004 Posts: 164
|
We have upgraded our Broker DB from 9 to 10.
No however, when trying to start the broker or running the mqsilist <BROKER> command, we are getting the following errors:
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 '80'; Error Text 'Specified driver could not be loaded'.
The error has the following diagnostic information: SQL State 'IM003' SQL Native Error Code '80' SQL Error Text '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 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.
The broker DB user and password can connect to the DB using SQLPlus, the $ORACLE_HOME variable has been changed and the mqsi_setupdatabase has been run.
Unfortunately, the errors persist.
We are running WMB v 5.0.9 on Solaris
Does anyone have any idea as to what may be wrong..? |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Dec 20, 2007 3:54 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Upgrade to WMB 6.0 or 6.1. I'm not sure that WMB 5.x with Oracle 10g is a supported configuration....  _________________ MQ & Broker admin |
|
Back to top |
|
 |
bdrummond |
Posted: Thu Dec 20, 2007 4:02 am Post subject: |
|
|
Disciple
Joined: 06 May 2004 Posts: 164
|
I thpught 10g was supported from v5 csd8 and above..? |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Dec 20, 2007 4:20 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
bdrummond wrote: |
I thought 10g was supported from v5 csd8 and above..? |
Assuming the ODBC setup is correct...
In that case try following: stop broker and oracle and restart oracle then restart the broker.
I had some trouble with the DB2 db => same type of error message and recycling the DB is what fixed it for me.  _________________ MQ & Broker admin |
|
Back to top |
|
 |
bdrummond |
Posted: Thu Dec 20, 2007 6:47 am Post subject: |
|
|
Disciple
Joined: 06 May 2004 Posts: 164
|
Looks as though the problem was due to permissions of the $ORACLE_HOME/lib32 directory.
Now we have a problem with each of the execution groups reporting the following errors:
Dec 20 13:50:31 srim8199 MQSIv500[29676]: [ID 702911 user.error] (UKBRKR1D_B.EQ_Executions)[1]BIP2322E: Database error: SQL State 'HY000'; Nati
ve Error Code '1008'; Error Text '[DataDirect][ODBC Oracle driver][Oracle]ORA-01008: not all variables bound '. : UKBRKR1D_B.97aaffb9-1301-0000
-0080-bfa433c3cabe: /build/S500_P/src/DataFlowEngine/ImbOdbc.cpp: 377: ImbOdbcHandle::checkRcInner: :
Is this a problem with the database or an environment variable that I have missed somewhere..? A search indicates a permission/grant issue on the database but I'm not 100% sure.
Incidentally, which DB drivers should we be using of the following 3..:
/opt/wmqi/merant/lib/UKor818.so
/opt/wmqi/merant41/lib/UKor818.so
/opt/wmqi/merant50/lib/UKor820.so
The IBM documentation suggests we should use the last one but if we do, we get the original problems again.  |
|
Back to top |
|
 |
bdrummond |
Posted: Thu Dec 20, 2007 7:37 am Post subject: |
|
|
Disciple
Joined: 06 May 2004 Posts: 164
|
Problem solved.
We changed the name of the /opt/wmqi/merant directory, created a symbolic link to the /opt/wmqi/merant50 directory and all appears well.
 |
|
Back to top |
|
 |
|