| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMQI Broker Creation Error on Solaris |
« View previous topic :: View next topic » |
| Author |
Message
|
| Syams |
 Posted: Tue Jul 08, 2003 4:01 am Post subject: WMQI Broker Creation Error on Solaris |
 |
|
Novice
Joined: 08 Jul 2003
Posts: 10
|
Hi,
I am issuing the command to create WMQI Broker on Sun Solaris with DB2 Database
./mqsicreatebroker MQSI_BRK1 -i mqsi -a mqsi -q MQSI.BRK.QM -n MQSIBKDB -u db2inst -p db2inst.
While doing so I am getting following Errors, though Database is Working fine with db2 connect command and odbc.ini is configured properly.
The Error is like this:
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.
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 'IM004'; Native Error Code '0'; Error Text '[MERANT][ODBC lib] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed'.
The error has the following diagnostic information: SQL State 'IM004' SQL Native Error Code '0' SQL Error Text '[MERANT][ODBC lib] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed'
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.
What causes the problem and what could be the solution to it.
Regards,
Lita |
|
| Back to top |
|
 |
| kirani |
| Posted: Tue Jul 08, 2003 8:24 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Could you post the contents of your .odbc.ini file here? Also, does your DB ID have sufficient authority on DB? Please make sure that you create an empty database and have MQSIBKDB DSN configured to point it to that db before running this command.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Craig B |
| Posted: Tue Jul 08, 2003 8:35 am Post subject: |
|
|
Partisan
Joined: 18 Jun 2003
Posts: 316
Location: UK
|
What level of DB2 are you running with? Are you are on DB2 V7 FP 2A or above? If so you may need to make some changes to your driver manager libraries since there is a known problem with the interaction of the WMQI ODBC driver at this level of code. If you look at the following website :
http://www-3.ibm.com/software/integration/mqfamily/platforms/supported/wsmq_integ_for_solaris_2_1.html
Then you will see the following for the DB2 entry ....
| Quote: |
Note: There are known problems between WMQI v2.1 and DB2 v7.1 (Fix Pack 2a and above) and DB2 v7.2. There is a valid workaround which is supported and tested by WMQI. Visit this link for more details. This workaround is not required if CSD04 or above has been applied to WMQI V2.1 (see CSD memo for details under defect 28704).
|
If you click on the link on the web page, then this will take you to ....
http://www-1.ibm.com/support/docview.wss?uid=swg21042663
then this will give details of swapping the db2.o files for the db2_36.o files.
But as previously mentioned, this is only applicable to DB2 V7 FP2 or above.
This is one of the known problems which will result in the error you are experiencing with the mqsicreatebroker command.
_________________
Regards
Craig |
|
| Back to top |
|
|
| Syams |
| Posted: Wed Jul 09, 2003 9:58 pm Post subject: |
|
|
Novice
Joined: 08 Jul 2003
Posts: 10
|
Hi Craig,
Even after doing the required changes to the libdb2.so.1 with libdb2_36.so.1, giving all the required level of permission and updation to instances, still it's giving the same error, is there any other configuration issues involved ?
Regards,
Lita |
|
| Back to top |
|
|
| Craig B |
| Posted: Thu Jul 10, 2003 7:43 am Post subject: |
|
|
Partisan
Joined: 18 Jun 2003
Posts: 316
Location: UK
|
Does your LIBRARY path contain the install directory where the ODBC driver manager has been installed?
If it does then I cant really offer any other suggestions. Sorry.
_________________
Regards
Craig |
|
| Back to top |
|
|
| Syams |
| Posted: Tue Jul 15, 2003 4:50 am Post subject: Broker Creation Error for WMQI on Solaris |
|
|
Novice
Joined: 08 Jul 2003
Posts: 10
|
Hi Craig,
I tried to change the Driver for db2 but since the problem was still persisting, I prefered to apply the fixpack CSD06 to wmqi to overcome the problem of ODBC connectivity to Database through wmqi.
While applying the fixpack csd6 it gives the following error and does not install csd6.
# pkgadd -d .
The following packages are available:
1 wmqi-upd6 WebSphere MQ Integrator V2.1.0 for Sun Solaris - U487641
(SPARC_SOL2.7) Version 2 , Revision 1
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: 1
Processing package instance <wmqi-upd6> from </export/eaies/es1/bishwa/wmqi-csd>
WebSphere MQ Integrator V2.1.0 for Sun Solaris - U487641
(SPARC_SOL2.7) Version 2 , Revision 1
(C) Copyright IBM Corp. 2001
WebSphere MQ Integrator V2.1.0 for Sun Solaris - PTF Update
WARNING: Cannot find/read supersede and current ptf information.
There is no problem if this is the first update applied.
If not then contact your System Administrator or supplier.
ERROR: Cannot find the base application on this system.
pkgadd: ERROR: request script did not complete successfully
Installation of <wmqi-upd6> failed.
No changes were made to the system.
If u have any idea why it happens and how to overcome it, kindly reply.
Regards,
Lita |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
