| Author |
Message
|
| kingsley |
 Posted: Fri May 06, 2005 5:19 am Post subject: MQSICreateBroker |
 |
|
Disciple
Joined: 30 Sep 2001
Posts: 175
Location: Hursley
|
Hi
After issuing mqsicreatebroker on my AIX Broker which has local DB2 database, the UserId and password are correct, i am getting the following Error.
------------------------------------------------------------------------------
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 '01000'; Native Error Code '0'; Error Text '
'.
The error has the following diagnostic information: SQL State '0
1000' SQL Native Error Code '0' 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 connectio
ns available for use.
------------------------------------------------------------------------------
I am unable to find the root cause of this. I've configured the ODBC file too
Thanks |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri May 06, 2005 5:32 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Does the database user you are specifying have permissions on the database? It needs to have full authorities.
Are you running the mqsicreatebroker command in a shell environment that has sourced the db2profile?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kingsley |
| Posted: Fri May 06, 2005 5:34 am Post subject: |
|
|
Disciple
Joined: 30 Sep 2001
Posts: 175
Location: Hursley
|
| We do have full permissions. Please explain the term sourced. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri May 06, 2005 5:42 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| kingsley wrote: |
| We do have full permissions. Please explain the term sourced. |
I guess I mean "included". The highly-overloaded "." in Unix will allow you to run a script in the current environment - rather than in a new environment.
So if you add ".<space><db2inst home>/sqlllib/db2profile" to the .profile for the broker user, then the next time you log in, it will include all of the db2 environmental information. Or you can just run that directly in the current shell, and then retry your mqsicreatebroker.
I don't think this is the problem, though, it should throw a different error - but it's always better to double check.
Likewise, double-check username and password case sensitivity.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JT |
| Posted: Fri May 06, 2005 6:04 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
An elementary question: did you issue the mqsi_setupdatabase command?
Post the contents of the odbc configuration file.
| Quote: |
| We do have full permissions. |
Have you verified this via the DB2 command line processor? |
|
| Back to top |
|
|
| kingsley |
| Posted: Fri May 06, 2005 6:40 am Post subject: |
|
|
Disciple
Joined: 30 Sep 2001
Posts: 175
Location: Hursley
|
This is the command
mqsi_setupdatabase db2 /home/db2admn
Content of .odbc.ini
----------------------------------------------------------
[ODBC Data Sources]
MQSIBKDB=IBM DB2 ODBC Driver
MYDB=IBM DB2 ODBC Driver
ORACLEDB=DataDirect 410 Oracle 8 Driver
SYBASEDB=DataDirect 410 Sybase ASE Driver
[MQSIBKDB]
Driver=/usr/opt/db2_08_01/lib/libdb2.a
Description=MQSIBKDB DB2 ODBC Database
Database=DB2CSA
[MYDB]
Driver=/usr/opt/db2_08_01/lib/libdb2.a
Description=MYDB DB2 ODBC Database
Database=DB2CSA
[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 |
|
|
| Nick Lethbridge |
| Posted: Tue May 10, 2005 2:05 am Post subject: |
|
|
Voyager
Joined: 13 Aug 2001
Posts: 88
Location: Santander, UK
|
Try setting the .odbc.ini file as follows:
Content of .odbc.ini
----------------------------------------------------------
[ODBC Data Sources]
DB2CSA=IBM DB2 ODBC Driver
[DB2CSA]
Driver=/usr/opt/db2_08_01/lib/libdb2.a
Description=DB2CSA DB2 ODBC Database
Database=DB2CSA
[ODBC]
Trace=0
TraceFile=/var/wmqi/odbc/odbctrace.out
TraceDll=/usr/opt/wmqi/merant/lib/odbctrac.so
InstallDir=/usr/opt/wmqi/merant
-----------------------------------------------------------
(I'm assuming that you are using DB2CSA as your broker database - are you also using it to store your application data? If so, it might be better to create a separate database for your own application data?)
Have you used the /usr/opt/wmqi/sample/profiles/profile.aix file as the basis for your .profile file - it includes a definition of an ODBCINI variable that is required (to point to your .odbc.ini file)?
Does the following work (when entered at a shell prompt):
db2 connect to DB2CSA user <wmqi/wbimb userid> using <password>
If not, your .profile file may not include the correct DB2 definitions, or the <wmqi/wbimb userid> may not be authorised to access the DB2 database?
Regards,
Nick. |
|
| Back to top |
|
|
| kingsley |
| Posted: Tue May 10, 2005 4:19 am Post subject: |
|
|
Disciple
Joined: 30 Sep 2001
Posts: 175
Location: Hursley
|
Nick,
along with the Stanza db2csa, we have made one more modification and i was able to create the Broker.
thanks for all the support. The Forum really has the some of the best brains
Thanks |
|
| Back to top |
|
|
|
|
