ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » mqsicreatebroker issue

Post new topic  Reply to topic
 mqsicreatebroker issue « View previous topic :: View next topic » 
Author Message
gobi_nathan
PostPosted: Tue Jun 22, 2004 1:01 pm    Post subject: mqsicreatebroker issue Reply with quote

Acolyte

Joined: 08 Jan 2003
Posts: 69

Hi All,

On Solaris, i have WMQIB5 ,CSD03 and Oracle9i(9.2.0.1).
I am trying to create a broker and it is giving me a database error.

I have done the following
Run the "mqsi_setupdatabase" and it has created the links.

Changed values in /var/wmqi/odbc/.odbc.ini pointing to my "DSN" which is up and running

Following is my .odbc.ini file

TESTDB=MERANT 3.70 Oracle 8 Driver

[TESTDB]
Driver=/opt/wmqi/merant/lib/UKor818.so
WorkArounds=536870912
WorkArounds2=2
Description=Oracle8
ServerName=TESTDB
LogonID=dbm
Password=dmb
EnableDescribeParam=1
OptimizePrepare=1

I am getting the folloing error message.. when i try to create Broker

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.
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 'IM003'; Native Error Code '80'; Error Text
'Specified driver could not be loaded'.
The error has the following diagnostic information: SQL State 'I
M003' 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 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 connectio
ns available for use.


I saw the same issue is already posted before in the forum.Since i haven't find any helping answer and hope those who already fixed the issues can update the solution.Sorry i am posting this again.

Regards,
Gobi
Back to top
View user's profile Send private message
garfiny
PostPosted: Wed Jul 28, 2004 11:04 pm    Post subject: i have same problem Reply with quote

Novice

Joined: 23 Jul 2004
Posts: 19

Hi all,

i have same problem as the owner's.
My enviroment is like his beside my database is DB2 v81.

Does anyone have ideas about this.

Help!

Thanks!
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Jul 29, 2004 3:24 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

It seems like gobi_nathan's problem is a database authorization problem - that the user "dmb" doesn't have necessary permissions to create or modify the tables that are necessary.

I'd suggest temporarily changing the odbc.ini file to indicate the db2 owner user (likely db2inst1).
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Jack W. Khaw
PostPosted: Thu Jul 29, 2004 5:23 am    Post subject: ODBC driver Reply with quote

Newbie

Joined: 08 Jul 2004
Posts: 7

use this driver instead.

MQSeries DataDirect 4.10 32-BIT Oracle
_________________
jkhaw
Back to top
View user's profile Send private message
gobi_nathan
PostPosted: Thu Jul 29, 2004 8:14 am    Post subject: Reply with quote

Acolyte

Joined: 08 Jan 2003
Posts: 69

Hi All,

This problem is solved after adding oracle_home/lib32 folder in the ld_library_path .

This solution is found in DataDirect support site, but not from ibm.

-Gobi
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » mqsicreatebroker issue
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.