| Author |
Message
|
| reddy_kal |
 Posted: Wed Sep 20, 2006 10:40 am Post subject: Error in creating MessageBroker on SUSE Linux |
 |
|
Acolyte
Joined: 04 Nov 2002
Posts: 73
|
Hello,
I am getting error when I am creating Message Broker on SUSE Linux (SLES 9).
****************************
mqsicreatebroker <BrokerName> -i <brokeruser> -a <brokerpass> -q <QueueManager> -n <databasename> -u <databaseuser> -p <databasepassword>
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 ''82''; Native Error Code '0'; Error Text ''523 80''.
The error has the following diagnostic information: SQL State ''82'' SQL Native Error Code
'0' SQL Error Text ''523 80''
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.
***********************************
When I do sqlplus, it is working fine. And even I am able to create a temporary table in the database.
Can you please help me in resolving this issue.
We are running MessageBroker 6, WMQ6 and Oracle 10G.
-Reddy |
|
| Back to top |
|
 |
| vennela |
| Posted: Wed Sep 20, 2006 10:52 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
|
| Back to top |
|
|
| reddy_kal |
| Posted: Wed Sep 20, 2006 11:02 am Post subject: |
|
|
Acolyte
Joined: 04 Nov 2002
Posts: 73
|
Hello,
Thanx for the reply and moving to the right place.
I am using the right driver in my .odbc.ini file
[eiad]
Driver=/opt/ibm/mqsi/6.0/merant/lib/UKor820.so
Description=DataDirect 5.0 Oracle
EnableDescribeParam=1
OptimizePrepare=1
ServerName=eiad
WorkArounds=536870912
ProcedureRetResults=1
But I am still getting the same error. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Sep 20, 2006 11:09 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
To confirm.
If you issue "sqlplus <brokeruser>@<tnsnames.ora name for database>", and supply <brokerpass>, then you can connect just fine?
Also, confirm that you added <ora_home>\lib32 to the front of your PATH in broker user profile (do *not* edit mqsiprofile.sh).
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| reddy_kal |
| Posted: Wed Sep 20, 2006 11:33 am Post subject: |
|
|
Acolyte
Joined: 04 Nov 2002
Posts: 73
|
Hello,
Yes when I do sqlplus <brokeruser>@database and supply the password, it works fine. And to verify the prvileges, I did create a temporary table and deleted successfully.
The .profile file for the MessageBroker user is setup
"export SHLIB_PATH=/usr/dt/lib:/usr/lib:$ORACLE_HOME/lib32:$ORACLE_HOME/lib"
Do I need to set this $ORACLE_HOME/lib32 to PATH as well?
-Reddy |
|
| Back to top |
|
|
| BrianR |
| Posted: Wed Sep 20, 2006 10:57 pm Post subject: |
|
|
Novice
Joined: 04 Nov 2005
Posts: 12
Location: London
|
Do not know if this will help, but I had problems with ODBC connections to oracle 10g on suse 10.
Have you run the mqsi_setupdatabase command?
Had you tried running
ldd /opt/ibm/mqsi/6.0/merant/lib/UKor820.so
to check all required files can be found?
Have you got unixODBC installed? If so try
isql <dsn> <userid> <password> -v
It might give some more useful info.
You mention SHLIB_PATH, I had to add the $ORACLE_HOME/lib and $ORACLE_HOME/bin directories to LD_LIBRARY_PATH
Are $ORACLE_HOME etc.. set for the user?
My problem eventually turned out to permissions to the oracle directories which I sledge hammered with
chmod -R 755 $ORACLE_HOME
Good luck !! |
|
| Back to top |
|
|
| reddy_kal |
| Posted: Thu Sep 21, 2006 6:24 am Post subject: |
|
|
Acolyte
Joined: 04 Nov 2002
Posts: 73
|
Hello Brian,
It worked now !!!!!!!!!!!!
We chnaged the permission of $ORACLE_HOME directory and all the files inside in that directory to 755 and it created message broker successfully.
I can't imagine this.
It took me whole day just to check whats wrong with this.
Anyway, Thank you all for your support. I really appreciate your help
-Reddy |
|
| Back to top |
|
|
|
|
