| Author |
Message
|
| Harshalw |
 Posted: Wed Sep 10, 2008 6:52 am Post subject: creating broker with core dump on AIX |
 |
|
Voyager
Joined: 23 Jul 2008
Posts: 77
|
Hi ,
I am trying to create a broker on AIX box. Using WMB 6.1 here.
First i tried creating a broker with odbc64.ini - it gave me the error ->
WebSphere MQ queue manager running.
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 ''[DataDirect][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 ''[DataDirect][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 with the broker.
- Check that the database is running.
- On Windows check that an ODBC connection has been created.
- On systems which use $ODBCINI check that the file pointed to by $ODBCINI has been correctly updated.
- Check that the userid and password pair specified for ODBC connect on the mqsicreate or mqsichangebroker command are capable of being used to connect to the database using an ODBC connection.
- Check that the database has a adequate number of database connections available for use.
Also when i try with odbc32.ini it gave creates the broker , howvever it also created a core dump and this broker we are not able to start it and stop it. Please help , it very urgent.
thanks |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Wed Sep 10, 2008 7:32 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
as you said it produced a core dump, raise a PMR
mean time, parallely investigate the issue
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| AkankshA |
| Posted: Wed Oct 15, 2008 2:02 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
Could you resolve this issue ??
I am also facing similar concern
mqsicreatebroker results in
| Quote: |
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 ''[DataDirect][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 ''[DataDirect][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 specified user Id and password pair.
- Check that the database is running.
- On Windows, check that an ODBC connection has been created.
- On systems that use $ODBCINI, check that the file pointed to by $ODBCINI has been correctly updated.
- Use mqsichangebroker brokername -a xxx to set the password to the correct value and try again.
Use mqsichangeconfigmgr configmgr -a xxx to set the password to the correct value and try again.
- Check that the database has an adequate number of database connections available for use.
|
WMB 6.1 with DB 8.2 on AIX 5.3.0.0[/quote]
_________________
Cheers |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Wed Oct 15, 2008 2:15 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
|
| Back to top |
|
|
| AkankshA |
| Posted: Wed Oct 15, 2008 2:24 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
both profiles sourced..
the only change is :
article dates back to 2004-09-16.. we had MB 5/6 those days and were using libdb2.a
however with 6.1 we use libdb2Wrapper64.so as DRIVER..
but somehow libdb2Wrapper64.so does not seem to work 
Note : I do hope that DB2 SDK 8.2.0 is supported with MB 6.1
_________________
Cheers |
|
| Back to top |
|
|
| tom_123 |
| Posted: Sat Oct 18, 2008 12:59 am Post subject: |
|
|
Novice
Joined: 28 Feb 2008
Posts: 15
|
Hi,
Ca you please check you Broker DB is locked by Administrator or may be some files are locked. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Oct 18, 2008 7:54 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| AkankshA wrote: |
both profiles sourced..
the only change is :
article dates back to 2004-09-16.. we had MB 5/6 those days and were using libdb2.a
however with 6.1 we use libdb2Wrapper64.so as DRIVER..
but somehow libdb2Wrapper64.so does not seem to work
Note : I do hope that DB2 SDK 8.2.0 is supported with MB 6.1 |
Did you verify that your DB2 installation is indeed a 64 bit version?? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| hallmark |
| Posted: Tue Jan 06, 2009 6:30 am Post subject: ODBC errors running mqsicreatebroker on version 6.1 |
|
|
Voyager
Joined: 10 Mar 2005
Posts: 76
|
Did anyone get anywhere with this problem, I am having very similar issues and am confused by the documentation regarding 32bit and 64bit instances.
AIX5.3
Broker 6.1.0.3
DB2 8 FP14
We are just using the DB to hold the broker configuration and while running the mqsicreatebroker command I am getting the following errors
BIP2322E: Database error: SQL State ''IM004''; Native Error Code '0'; Error Text ''[DataDirect][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 ''[DataDirect][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.
Again, both mqsiprofile and db2profile are being sourced by the broker service id profile.
We only have a 32bit instance of our datasource (BKR1) and the ODBCINI32 variable points to the odbc32.ini file. I have also created a variable ODBCINI pointing to the odbc64.ini file and would not expect this to be used.
In the syslog I am seeing the following error
Jan 6 14:23:55 aixdev040 user:err|error WebSphere Broker v6103[262324]: (BKR61)[1]BIP2391E: DB2 wrapper (64-bit) could not load the DB2 implementation librar
y using library locations '/usr/opt/db2_08_01/lib64/libdb2.a(shr_64.o)', 'libdb2.a(shr_64.o)', or the location specified by the MQSI_64BIT_DB2_LIBRARY_NAME en
vironment variable. DB2 will not be accessible in this process. : BKR61.mqsicreatebroker: /build/S610_P/src/bipodbc/wrapper/ImbDB2Wrapper.cpp: 1012: ImbDB2Wra
pper.o(loadAppropriateDB2Library): :
In the documentation a reference to this error code states
Ensure DB2 is accessible to the broker user id, and that the shared library search path is set to include the DB2 64-bit library location. Setting MQSI_64BIT_DB2_LIBRARY_NAME to point to libdb2.so (or .sl or .a) may help this problem.
I have tried to do this and still no joy, any help would be appreciated if you have seen this before, otherwise I will keep plodding along
Rob |
|
| Back to top |
|
|
| hallmark |
| Posted: Thu Jan 08, 2009 8:35 am Post subject: |
|
|
Voyager
Joined: 10 Mar 2005
Posts: 76
|
Hi all,
Me being stupid and a slight case of RTFM. My problems stem from the fact my instance is 32bit, and the installation guide states (in the Software Prereq section under Databases, a note)
If you define a connection to DB2 Version 8.2 from a broker that operates
in 64-bit mode, you must specify that you want to create a 64-bit
database instance.
Hope this helps others
Rob |
|
| Back to top |
|
|
|
|
