| Author |
Message
|
| mccara |
 Posted: Mon Jul 21, 2008 12:48 pm Post subject: WMB 6.1 ODBC error when creating a new broker |
 |
|
Newbie
Joined: 07 Nov 2006
Posts: 5
|
I have an AIX 5.3 system with WMB 6.0.0.7 already installed.
I have installed WMB 6.1.0.2 in parallel with WMB 6.0. I have created a separate userid for the wbm6.1, separate Db2 V9 database for the new broker and separate Config manager for the new broker.
I am getting an ODBC error when attempting to create the new 6.1 broker. I am using the set ODBCINI in the profile. The odbc.ini file has the following entries :
[ODBC Data Sources]
MQSI61DB=IBM DB2 ODBC Driver
[MQSI61DB]
#Driver=/usr/opt/db2_08_01/lib/libdb2.a
#Driver=/opt/IBM/db2/V9_1/lib32/libdb2.a
Driver=/opt/IBM/db2/V9_1/lib64/libdb2Wrapper64.so
Description=MQSI61DB DB2 ODBC Database
Database=MQSI61DB
[ODBC]
Trace=1
TraceFile=/tmp/odbctrace.out
#TraceDll=/opt/IBM/mqsi/6.1/merant/lib/odbctrac.so
TraceDll=/opt/IBM/mqsi/6.1/ODBC64/V5.3/lib/odbctrac.so
#InstallDir=/opt/IBM/mqsi/6.1/merant
InstallDir=/opt/IBM/mqsi/6.1/ODBC64/V5.3
UseCursorLib=0
IANAAppCodePage=4
UNICDOE=UTF-8
I am able to connect to the database outside of the broker command without issue
dms1]/home/wmqi61>db2 connect to MQSI61DB user wmqi61 using ***********
Database Connection Information
Database server = DB2/AIX64 9.1.3
SQL authorization ID = WMQI61
Local database alias = MQSI61DB
This is the error that I am getting when I issue the mqsicreatebroker command
[dms1]/home/wmqi61>mqsicreatebroker MSAD461 -i wmqi61 -a *********** -q MSAD461 -n MQSI61DB -u wmqi61 -p *********
AMQ8110: WebSphere MQ queue manager already exists.
WebSphere MQ queue manager 'MSAD461' starting.
5 log records accessed on queue manager 'MSAD461' during the log replay phase.
Log replay for queue manager 'MSAD461' complete.
Transaction manager state recovered for queue manager 'MSAD461'.
WebSphere MQ queue manager 'MSAD461' started.
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.
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.
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 ''IM003''; Native Error Code '0'; Error Text ''[DataDirect][ODBC lib] Specified driver could not be loaded''.
The error has the following diagnostic information: SQL State ''IM003'' SQL Native Error Code '0' SQL Error Text ''[DataDirect][ODBC lib] Specified driver could not be loaded''
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.
If anyone has seen this error before or has any clue - all help appreciated.
Thanks |
|
| Back to top |
|
 |
| dp111443 |
| Posted: Fri Aug 15, 2008 2:58 am Post subject: |
|
|
Voyager
Joined: 25 Feb 2004
Posts: 82
|
Hi,
Did you get this problem fixed. Coincidently, I had a broker working on linux broker 6.1.0.1 but when i upgraded to 6.1.0.2, I can't start the broker and get the same error as you.
I have raised a PMR with IBM as I've started clutching at staws.
Thanks,
Dharmesh
_________________
Integration Design/Developer
IBM Certified System Administrator -
WebSphere MQ V5.3 |
|
| Back to top |
|
|
| jeeth_m |
| Posted: Fri Aug 15, 2008 4:21 am Post subject: |
|
|
Voyager
Joined: 21 Jan 2002
Posts: 93
|
| have you tried setting the User ID and password of databse using mqsisetdbparms? |
|
| Back to top |
|
|
| dp111443 |
| Posted: Fri Aug 15, 2008 4:25 am Post subject: |
|
|
Voyager
Joined: 25 Feb 2004
Posts: 82
|
Hi,
Correct me if I'm wrong, but you only need to do the mqsisetdbparms command on the user databases (i.e. database's that you will access from your flows). The issue I'm having is with the actual broker database.
When you create the broker using mqsicreatebroker you already specify the database userid and password.
I can confirm the login credentials are all correct when connection to the database with sqlplus.
Thanks,
_________________
Integration Design/Developer
IBM Certified System Administrator -
WebSphere MQ V5.3 |
|
| Back to top |
|
|
| mccara |
| Posted: Fri Aug 15, 2008 6:04 am Post subject: |
|
|
Newbie
Joined: 07 Nov 2006
Posts: 5
|
I did get this fixed. I opened a PMR with IBM and found out that the DB2 driver that is needed in the ODBC.ini file needs to be the wrapper without the fully qualified path.
Original in ODBC.ini
Driver=/opt/IBM/db2/V9_1/lib64/libdb2Wrapper64.so
Correct way
Driver=libdb2Wrapper64.so
This allowed me to create the broker and move on |
|
| Back to top |
|
|
| dp111443 |
| Posted: Fri Aug 15, 2008 6:18 am Post subject: |
|
|
Voyager
Joined: 25 Feb 2004
Posts: 82
|
Hi Thanks for the info! My problem turned out to be completely different.
IBM got back to me pretty promply. Whilst raising the support incident I started scanning around the installation directories and started to suspect they had updated the oracle driver. Which they have now confirmed.
I had to change the odbc.ini file (to change the driver locations) and run the mqsichangebroker to reset the broker database password - which was odd. 
But any how, all is now working ok. The broker can now connect to its database happily.
For anyone else that has this problem on linux, know you know why!! 
Oh and the supporting documentation for this change can be found at:
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/topic/com.ibm.etools.mft.doc/ah01652_.htm under "Applying Service to runtime components".
BTW - The fixpak readme doesn't make this obvious.
All the best!
Dharmesh
_________________
Integration Design/Developer
IBM Certified System Administrator -
WebSphere MQ V5.3 |
|
| Back to top |
|
|
|
|
