Author |
Message
|
lohit |
Posted: Mon Jun 23, 2003 9:53 pm Post subject: Create Broker Problem Solaris / Oracle |
|
|
Novice
Joined: 29 May 2003 Posts: 20
|
Hi,
I have installed MQseries 5.2 and MQSI 2.0.1 on Solaris machine.
I have modified the .odbc.ini file as required and copied the sample profile file given. I am using Oracle 8.1.7.
I am able to tnsping my dsn by
, which works and also i can log on using
Code: |
sqlplus system/manager@mqbkdb |
While giving the command, mqsicreatebroker i get the error.
Code: |
BIP2322E: Database error: SQL State 'IM002'; Native Error Code '0'; Error Text '[MERANT][ODBC lib] Data source name not found and no default driver specified'. |
.
My .odc.ini file contents are :
Code: |
ORACLEDB=MERANT 3.60 Oracle 8 Driver
[ORACLEDB]
Driver=/opt/mqsi/merant/lib/UKor815.so
Description=Oracle8
ServerName=mqbkdb
LogonID=system
Password=manager
EnableDescribeParam=1
OptimizePrepare=1 |
My LD_LIBRARY_PATH is
Code: |
/usr/lib:/opt/oracle/product/8.1.7/lib:/opt/mqsi/merant/lib:/opt/mqsi/lib:/opt/mqsi/jre/lib/sparc/native_threads:/opt/mqsi/merant/lib:/opt1/SUNWspro/WS5.0/lib:/opt/hpnp/lib:/opt/fmc/lib:/usr/src/j2sdk1_3_0/jre/lib/sparc:/usr/local/lib |
It seems there is some problem in the ODBC connection.
Would really appreciate some advice / pointers to resolve this problem as I am stuck with it for the last month.
Thanks for your help.
Regards
Lohit[/code] |
|
Back to top |
|
 |
Craig B |
Posted: Mon Jun 23, 2003 11:21 pm Post subject: |
|
|
Partisan
Joined: 18 Jun 2003 Posts: 316 Location: UK
|
From the information you have provided it would seem that you have created a database called mqbkdb. What are you specifying in the -n parameter of the mqsicreatebroker command? Are you specifying mqsibkdb or ORACLEDB? Your ODBC.ini file has been set up with a datasource name of ORACLEDB and you have set the server to be the name of your database. Have you attempted to use a datasource alias of ORACLEDB to get to your MQBKDB database because I wasnt sure this is how you do this.
I would recommend trying the simple case first of naming your Data source the same as your database to keep the names consistent. Then if this works, if you need aliasing then attempt to set this up when you know the basic set-up is working. Therefore I would try the following :
Code: |
MQBKDB=MERANT 3.60 Oracle 8 Driver
[MQBKDB]
Driver=/opt/mqsi/merant/lib/UKor815.so
Description=Oracle8
ServerName=YourServerName
LogonID=system
Password=manager
EnableDescribeParam=1
OptimizePrepare=1
|
Then on the mqsicreatebroker command specify -n MQBKDB with appropriate -u and -p parameters for this database.
Also it should be noted that MQSI V2.01 is not supported anymore, and Im not sure what database combinations were supported before it went out of service. _________________ Regards
Craig |
|
Back to top |
|
 |
lohit |
Posted: Tue Jun 24, 2003 2:48 am Post subject: |
|
|
Novice
Joined: 29 May 2003 Posts: 20
|
Hi,
Thanks for the tip.
I am aware that Mqsi 2.01 is no longer supported by IBM but dont have a choice unfortunately.
I modified the .odbc file as you suggested.
My new odbc file looks like
Code: |
MQBKDB=MERANT 3.60 Oracle 8 Driver
[MQBKDB]
Driver=/opt/mqsi/merant/lib/UKor815.so
Description=Oracle8
ServerName=mqbkdb
LogonID=system
Password=manager
EnableDescribeParam=1
OptimizePrepare=1 |
Now when I run the command
Code: |
mqsicreatebroker MQSI_BROKER -i mqsiuser -a mqsiuser -q MQSI_BROKER_QM -n mqbkdb -u system -p manager |
I am getting this error.
Code: |
BIP2322E: Database error: SQL State '60'; Native Error Code '902'; Error Text '[MERANT][ODBC 20101 driver][20101]ORA-00902: invalid datatype
'.
The error has the following diagnostic information: SQL State '60' SQL Native Error Code '902' SQL Error Text '[MERANT][ODBC 20101 driver][20101]ORA-00902: invalid datatype
'
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.
BIP8070E: Exception accessing database table executing SQL statement 'CREATE TABLE SYSTEM.BROKERAAEG (BrokerUUID (16) NOT NULL,ExecGroupUUID (16) NOT NULL,ExecGroupLabel BLOB NOT NULL,RetryInterval ,PubSubServer ,ProcessId ,ProcessState ,DynamicState ,DynamicSync ,MsgId (24),CntlGrpMsgId (24))': SQL state '902'; exception 'ImbException'. |
Any suggestions ?
Thanks again for your help.
Regards
Lohit |
|
Back to top |
|
 |
Ian |
Posted: Tue Jun 24, 2003 4:37 am Post subject: |
|
|
Disciple
Joined: 22 Nov 2002 Posts: 152 Location: London, UK
|
Hi,
Quote: |
[MERANT][ODBC 20101 driver][20101]ORA-00902: invalid datatype
|
Data errors are logged in the format : [Driver Manager][Driver]"Error text"
When using MQSIv2.0.1 with an Oracle database, you would expect to see : [MERANT][ODBC Oracle 8 driver]"Some error text"
The database error you are receiving on the mqsicreatebroker command is : [MERANT][ODBC 20101 driver]...
It would appear the broker database connection is being told by the ODBC interface that the database type is "20101" as opposed to "Oracle 8".
The "20101" driver name is returned if the application cannot locate the localized (NLS) message catalog.
Typically this would indicate an environment problem, for example having the directory location listed more than once for several products.
This is confirmed by the multiple occurances of "/opt/mqsi/merant/lib" in your LD_LIBRARY_PATH :
Quote: |
/usr/lib:
/opt/oracle/product/8.1.7/lib:
/opt/mqsi/merant/lib:
/opt/mqsi/lib:
/opt/mqsi/jre/lib/sparc/native_threads:
/opt/mqsi/merant/lib:
/opt1/SUNWspro/WS5.0/lib:
/opt/hpnp/lib:
/opt/fmc/lib:
/usr/src/j2sdk1_3_0/jre/lib/sparc:
/usr/local/lib
|
Suggest you modify your LD_LIBRARY_PATH to include only one reference to "/opt/mqsi/merant/lib" and try re-running the mqsicreatebroker command. _________________ Regards, Ian |
|
Back to top |
|
 |
lohit |
Posted: Tue Jun 24, 2003 11:22 pm Post subject: |
|
|
Novice
Joined: 29 May 2003 Posts: 20
|
HI,
Thanks for the input, unfortunately even after modifying the LD_LIBRARY_PATH to point to a single occurance of /opt/mqsi/merant/lib.
The problem persists.
Quote: |
BIP2322E: Database error: SQL State '60'; Native Error Code '902'; Error Text '[MERANT][ODBC 20101 driver][20101]ORA-00902: invalid datatype |
Any suggestions?
Thanks ofr your help
Regards
Lohit |
|
Back to top |
|
 |
EddieA |
Posted: Wed Jun 25, 2003 9:04 am Post subject: |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
Issue 'locale'. What do you have for LC_MESSAGES.
If it's "C", then either install "en_US", or add a link "/usr/opt/mqsi/merant/locale/C" which points to usr/opt/mqsi/merant/locale/en_US".
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
lohit |
Posted: Thu Jun 26, 2003 12:58 am Post subject: |
|
|
Novice
Joined: 29 May 2003 Posts: 20
|
Hi,
Thanks a ton for your tip.
I created the link as you suggested and now have a running broker.
You have been a life saver.
Thanks again.
Regards
Lohit  |
|
Back to top |
|
 |
|