| Author |
Message
|
| paustin_ours |
 Posted: Thu Feb 23, 2006 3:34 pm Post subject: odbc connection |
 |
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
how do i check a ODBC connection on AIX?
i am not able to create the broker.
i can use the same service id and password from db2 prompt to connect but it returns with cannot connect when i issue the create broker command.
any thoughts?
Also,where do i look to see if the ODBC drivers are installed? |
|
| Back to top |
|
 |
| seeknee |
| Posted: Thu Feb 23, 2006 5:00 pm Post subject: |
|
|
Apprentice
Joined: 08 Aug 2002
Posts: 41
Location: Melbourne, Australia
|
Hi
I think this is what you need to do
Run mqsi_setupdatabase "Oracle /home directory" to set up softlink on broker server.
Set up broker service ID db2admin/admindb2 as a user on Oracle database
The db2admin should has permission to SELECT, DELETE, INSERT and UPDATE.
Modify odbc.ini file - Have a look in /opt/mqsi/merant/odbc.ini
Hopefully this helps
_________________
IBM Certified Specialist MQSeries
IBM Certified Specialist WebSphere MQ Integrator
IBM Certified Solution Designer WebSphere Business Integration Message Broker V5
"Good judgement comes from experience, and experience comes from poor judgement" |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Feb 23, 2006 5:02 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| seeknee wrote: |
| Set up broker service ID db2admin/admindb2 as a user on Oracle database |
Where did Oracle come into this picture?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Feb 23, 2006 5:14 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
| I can use the same service id and password from db2 prompt to connect but it returns with cannot connect when i issue the create broker command. |
can you paste the error?
_________________
-wayne |
|
| Back to top |
|
|
| JT |
| Posted: Thu Feb 23, 2006 7:27 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Also, post the content of the .odbc.ini file. |
|
| Back to top |
|
|
| paustin_ours |
| Posted: Fri Feb 24, 2006 7:48 am Post subject: |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
Here you go Masters and commanders 
this is the error i get on create command.
BIP2321E: Database error: ODBC return code '-1'.
The message broker encountered an error whilst executing a database operation. T
he ODBC return code was '-1'. See the following messages for information obtaine
d from the database pertaining to this error.
Use the following messages to determine the cause of the error. This is likely t
o be such things as incorrect datasource or table names. Then correct either the
database or message broker configuration.
BIP2322E: Database error: SQL State 'S1000'; Native Error Code '80'; Error Text
''.
The error has the following diagnostic information: SQL State 'S
1000' SQL Native Error Code '80' SQL Error Text ''
This message may be accompanied by other messages describing the effect on the m
essage broker itself. Use the reason identified in this message with the accomp
anying 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 conne
ction. Also ensure that the database has a adequate number of database connections available for use.
I have my database name in the place where there is MYDB.
Do i have to define a DSN name? I already ran a mqsisetupdatabase command with my database name.
do i have to manually create a DSN name for the database and use the DSN name instead of the actual database name
in the odbc.ini file and mqsisetupdatabase command?
[ODBC Data Sources]
MYDB=IBM DB2 ODBC Driver
ORACLEDB=DataDirect 410 Oracle 8 Driver
SYBASEDB=DataDirect 410 Sybase ASE Driver
[MYDB]
Driver=/u/db2inst1/sqllib/lib/libdb2.a
Description=MYDB DB2 ODBC Database
Database=MYDB
[ORACLEDB]
Driver=/usr/opt/wmqi/merant/lib/UKor818.so
WorkArounds=536870912
WorkArounds2=2
Description=Oracle8
ServerName=YourServerName
EnableDescribeParam=1
OptimizePrepare=1
[SYBASEDB]
Driver=/usr/opt/wmqi/merant/lib/UKase18.so
Description=Sybase11
Database=sybasedb
ServerName=YourServerName
WorkstationID=id
EnableDescribeParam=1
OptimizePrepare=1
SelectMethod=0
NetworkAddress=10.30.14.72,5000
SelectUserName=1
[ODBC]
Trace=0
TraceFile=/var/wmqi/odbc/odbctrace.out
TraceDll=/usr/opt/wmqi/merant/lib/odbctrac.so
InstallDir=/usr/opt/wmqi/merant |
|
| Back to top |
|
|
| JT |
| Posted: Fri Feb 24, 2006 7:52 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Post the exact mqsicreatebroker command you issued. |
|
| Back to top |
|
|
| paustin_ours |
| Posted: Fri Feb 24, 2006 8:04 am Post subject: |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
mqsicreatebroker **BRK –i username –a <user-id password> –q QMNAME –n <BrokerDBName>  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Feb 24, 2006 8:08 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
so, for <BrokerDBName> you are entering "MYDB" - which is both the name of the database and the name of the DSN.
And you have verified that you can issue "db2 connect to MYDB", while looged in as the broker user?
And you ensured that you are sourcing the db2 profile in your broker profile?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| paustin_ours |
| Posted: Fri Feb 24, 2006 8:22 am Post subject: |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
YES i am using the database name MYDB for BrokerDBName. how can i tell if there is a DSN name associated with the database with the same name. i tried to run the LIST ODBC DATA SOURCES but it errors out saying it is not supported.
YES and YES for the next two questions. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Feb 24, 2006 8:43 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The name of the DSN is simply what is specified in the ODBC.ini.
Yes, you have to manually create this - I assumed this was already done from the sections you posted.
If you have done that, and you are still getting this authorization error, then it is time to start tracing this from the DB2 side. You can open a PMR with IBM to get help with this, or ask your DB2 admin.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| paustin_ours |
| Posted: Fri Feb 24, 2006 10:22 am Post subject: |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
|
| Back to top |
|
|
| wschutz |
| Posted: Fri Feb 24, 2006 11:20 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
just one more thoguht, (and I don't remember whether db2 on aix supports this syntax):
| Code: |
db2 connect to mydb user username using <user-id password>
|
does that work?
_________________
-wayne |
|
| Back to top |
|
|
| paustin_ours |
| Posted: Tue Feb 28, 2006 11:30 am Post subject: |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
that does work. found that the db2 instance on our server is a 64-bit instance and the kernel is 64 bit aswell. I know broker V5 does not support 64 bit instance. does the 64 bit kernel support broker? we have a 32 bit MQ install that works fine.
now is there a way to make the broker work under the 64 bit instance?
i was looking for 32 bit libraries in the install directory but couldn't find them.
any thoughts, suggestions? |
|
| Back to top |
|
|
|
|
