| Should there be a template for posting questions to the forum? |
| Yes |
|
33% |
[ 1 ] |
| No |
|
66% |
[ 2 ] |
|
| Total Votes : 3 |
|
| Author |
Message
|
| Pete |
 Posted: Fri Jun 16, 2006 2:00 am Post subject: Error when trying to create a message broker |
 |
|
Apprentice
Joined: 25 Nov 2003
Posts: 43
|
Hi,
I'm hoping this is a trivial mistake I'm making - I'm having trouble running the mqsicreatebroker command.
Platform/Package details:
Solaris 5.9
WMBv6.0.0.1
WMQv6.0.0.0
Oracle 10.2.0.2 64bit
Environment:
| Code: |
_=/usr/bin/env
MANPATH=/usr/share/man:/usr/local/man:/opt/SUNWexplo/man:/opt/SUNWvts/man:/opt/CTEact/man
NLSPATH=/opt/IBM/mqsi/6.0/messages/%L/%N:/opt/IBM/mqsi/6.0/messages/En_US/%N:
SSH_TTY=/dev/pts/1
PATH=/dboracle/product/10.2.0.2/bin:/var/mqsi/odbc:/opt/IBM/mqsi/6.0/bin:/opt/IBM/mqsi/6.0/jre/bin:.:/usr/bin:/usr/ucb:/etc:/usr/local/bin:/dboracle/product/10.2.0.2/bin
MQSI_JARPATH=/opt/IBM/mqsi/6.0/classes:/opt/IBM/mqsi/6.0/messages
MQSI_REGISTRY=/var/mqsi
CLASSPATH=/opt/IBM/mqsi/6.0/classes/derby.jar:/opt/IBM/mqsi/6.0/classes/ConfigManagerProxy.jar:/opt/IBM/mqsi/6.0/classes/configutil.jar:/opt/mqm/java/lib/com.ibm.mq.jar:/opt/mqm/java/lib/connector.jar:/opt/IBM/mqsi/6.0/messages:
LOGNAME=wbrkadm
MQSI_FAD=3
DISTHUB_PATH=/opt/IBM/mqsi/6.0
ORACLE_SID=copal
MQSI_LILPATH=/opt/IBM/mqsi/6.0/lil:/opt/IBM/mqsi/6.0/jplugin
PS1=cbs096d002:
MQSI_DEVELOPMENT=/var/mqsi/registry
USER=wbrkadm
MQSI_LILPATH64=/opt/IBM/mqsi/6.0/lil64:/opt/IBM/mqsi/6.0/jplugin
MQSI_VERSION=6.0.0.1
MQSI_CATALINA_HOME=/opt/IBM/mqsi/6.0/catalina
SHELL=/bin/ksh
JAVA_HOME=/usr/j2se
MQSI_FILEPATH=/opt/IBM/mqsi/6.0
TMOUT=1800
ODBCINI=/var/mqsi/odbc/.odbc32.ini
HOME=/export/home/wbrkadm
MQSI_LIBPATH64=/opt/mqm/lib64:/opt/IBM/mqsi/6.0/DD64/lib:/opt/IBM/mqsi/6.0/jre/lib/sparcv9/server:/opt/IBM/mqsi/6.0/jre/lib/sparcv9:/opt/IBM/mqsi/6.0/xml4c/lib64
MQSI_VERSION_F=1
ODBCINI64=/var/mqsi/odbc/.odbc64.ini
MQSI_WORKPATH=/var/mqsi
SSH_CLIENT=10.241.55.203 1076 22
LD_LIBRARY_PATH=/opt/mqm/java/lib:/dboracle/product/10.2.0.2/lib32:/opt/IBM/mqsi/6.0/lib:/opt/IBM/mqsi/6.0/bin:/opt/IBM/mqsi/6.0/merant/lib:/opt/IBM/mqsi/6.0/jre/lib/sparc/server:/opt/IBM/mqsi/6.0/jre/lib/sparc:/opt/IBM/mqsi/6.0/xml4c/lib:/opt/IBM/mqsi/6.0/DD64/lib::/dboracle/product/10.2.0.2/lib32
MQSI_EXMLTCONFIGPATH=/opt/IBM/mqsi/6.0/exmltConfig
TERM=vt100
ORACLE_HOME=/dboracle/product/10.2.0.2
MQSI_VERSION_M=0
PWD=/export/home/wbrkadm
TZ=GB
MQSI_VERSION_V=6
MQSI_VERSION_R=0
A__z="*TMOUT
|
/var/mqsi/odbc/.odbc64.ini
| Code: |
[ODBC Data Sources]
WBRKBKDB=IBM DB2 ODBC Driver
MYDB=IBM DB2 ODBC Driver
ORACLEDB=DataDirect 5.0 64bit Oracle Wire Protocol
ORADB1=DataDirect 5.0 64bit Oracle Wire Protocol
ORACLEDB2=DataDirect 5.0 64bit Oracle Wire Protocol
SYBASEDB=DataDirect 5.0 64bit Sybase Wire Protocol
SQLSERVERDB=DataDirect 5.0 64bit SQL Server Wire Protocol
[ORACLEDB]
Driver=/opt/IBM/mqsi/6.0/DD64/lib/UKora20.so
Description=DataDirect 5.0 64bit Oracle Wire Protocol
HostName=10.24.71.85
PortNumber=1521
SID=COPAL
ServerName=10.24.71.85
CatalogOptions=0
EnableStaticCursorsForLongData=0
ApplicationUsingThreads=1
EnableDescribeParam=1
OptimizePrepare=1
WorkArounds=536870912
ProcedureRetResults=1
[ORADB1]
Driver=/opt/IBM/mqsi/6.0/DD64/lib/UKora20.so
Description=DataDirect 5.0 64bit Oracle Wire Protocol
HostName=10.24.71.85
PortNumber=1521
SID=COPAL
ServerName=10.24.71.85
CatalogOptions=0
EnableStaticCursorsForLongData=0
ApplicationUsingThreads=1
EnableDescribeParam=1
OptimizePrepare=1
WorkArounds=536870912
ProcedureRetResults=1
[ORACLEDB2]
Driver=/opt/IBM/mqsi/6.0/DD64/lib/UKora20.so
Description=DataDirect 5.0 64bit Oracle Wire Protocol
HostName=10.24.71.85
PortNumber=1522
SID=COPAL1
ServerName=10.24.71.85
CatalogOptions=0
EnableStaticCursorsForLongData=0
ApplicationUsingThreads=1
EnableDescribeParam=1
OptimizePrepare=1
WorkArounds=536870912
ProcedureRetResults=1
[ODBC]
Trace=0
TraceFile=/tmp/odbctrace.out
TraceDll=/opt/IBM/mqsi/6.0/DD64/lib/odbctrac.so
InstallDir=/opt/IBM/mqsi/6.0/DD64
UseCursorLib=0
IANAAppCodePage=4
|
Command being issued:
| Code: |
mqsicreatebroker XX.BK.CBS962T2 -i wbrkadm -a ****** -q XX.QM.CBS962T2 -n ORADB1 -u paldb -p ******
|
Error message:
| Code: |
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 ''IM002''; Native Error Code '0'; Error Text ''[DataDirect][ODBC lib] Data source name not found and no default driver specified''.
The error has the following diagnostic information: SQL State ''IM002'' SQL Native Error Code '0' SQL Error Text ''[DataDirect][ODBC lib] Data source name not found and no default driver specified''
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.
|
I am trying to create two brokers, running against seperate databases. I intend to use the databases COPAL and COPAL1, and am at the moment trying to access these using the DSN's ORADB1 and ORACLEDB2.
I have been able to successfully build a temporary broker and access the database COPAL via the DSN ORACLEDB - however this is the only DSN I can use successfully in the mqsicreatebroker command.
I have confirmed the existence of the 2 databases COPAL and COPAL1 and can connect to these using sqlplus with the given username with password.
I have also confirmed the tns names resolve using tnsping.
If any one can shed any light that would be most appreciated.
Rgds,
Pete |
|
| Back to top |
|
 |
| PieterV |
| Posted: Fri Jun 16, 2006 3:51 am Post subject: |
|
|
Disciple
Joined: 04 Jan 2006
Posts: 164
Location: Belgium
|
try using 32-bit drivers to your Oracle DB (altough your Oracle DB is 64-bit).
use them in .odbc.ini, not in odbc64.ini.
I had a similar error in my configuration.
use also the command mqsi_setupdatabase:
mqsi_setupdatabase oracle10 /dboracle/product/10.2.0.2
this will create a softlink. |
|
| Back to top |
|
|
| Pete |
| Posted: Fri Jun 16, 2006 5:15 am Post subject: |
|
|
Apprentice
Joined: 25 Nov 2003
Posts: 43
|
PieterV, many thanks for your resonse it is appreciated.
However I'm not happy to use 32bit drivers against a 64bit database - that's not progression.
The product [I believe] supports the use of a 64bit Oracle database so this SHOULD work.
I'll persevere.
Thanks again,
Pete |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jun 16, 2006 5:23 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
|
| Back to top |
|
|
| mqmaniac |
| Posted: Fri Jun 16, 2006 5:55 am Post subject: |
|
|
Master
Joined: 27 Dec 2005
Posts: 201
|
I have a question!
What Difference would it make to be on 32 bit or 64 bit drivers?
Performance? or Compatability with New Technologies? |
|
| Back to top |
|
|
| halbe01 |
| Posted: Sun Jun 25, 2006 11:52 pm Post subject: |
|
|
Novice
Joined: 02 Feb 2005
Posts: 16
|
I've been working with Pete (original poster) on this issue, and thought I'd update you with the solution:
It turns out that although the execution groups can run as true 64-bit applications on Solaris, and hence would use the 64-bit ODBC drivers, certain bits of Broker are only 32-bit (i.e. the mqsicreatebroker command). Hence you need both types of drivers configured. I'm assured that once the broker is configured, it will run as proper 64-bit (though I can't think of a way to prove that - at least it works!).
Thanks for all your suggestions.
Regards,
Ben. |
|
| Back to top |
|
|
| Pete |
| Posted: Tue Jun 27, 2006 1:17 am Post subject: |
|
|
Apprentice
Joined: 25 Nov 2003
Posts: 43
|
Good work Benjie!
Cheers for the reply.
Pete |
|
| Back to top |
|
|
|
|
