| Author |
Message
|
| mqsiman |
 Posted: Wed Oct 02, 2013 4:03 pm Post subject: Can't create ODBC datasource on new Integration Bus 9 server |
 |
|
Novice
Joined: 01 Oct 2013
Posts: 12
|
This is my first post on this forum. Hopefully there will be many to come!
Here's my issue. My company has been developing Web Services using WebSphere Enterprise Service Bus (WESB). We are now migrating to Integration Bus 9. We don't have a lot of prior Message Broker experience.
We have developed and tested some POC services on our development machines (Windows 7) that use an ODBC datasource and are now wanting to deploy them to our freshly built DEV server.
This is the server architecture and OS:
bash-3.2$ arch
x86_64
bash-3.2$ uname
Linux
Integration Bus 9 has been installed properly and tested with some POC Web Services that used JDBC connections. Integration Bus 9 ODBC Database Extender has been installed. The $ODBCINI, $ODBCSYSINI, and $IE02_PATH environment variables have been set. The odbc.ini odbcinst.ini should be correct because I used the provided templates and modified them.
When I run the following command to test my ODBC datasource I get the error message below. I thank you in advance for any help.
bash-3.2$ mqsicvp DEVBROKER -n MDMDB
BIP8290I: Verification passed for the ODBC environment.
BIP2393E: Database error: ODBC return code '-1' from data source ''MDMDB'' using ODBC driver manager ''''.
The broker received an error when processing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database about this error.
Use the following messages to determine the cause of the error. Typical problems are an incorrect data source, or table names. Correct either the database or the broker configuration. Use the mqsicvp command to test connectivity to this database.
BIP2347E: Database error: SQL State ''IM002''; Native Error Code '0'; Error Text 'System information file not found. Please check the ODBCINI and the ODBCSYSINI environment variables are correctly set.'
The error has the following diagnostic information: SQL State ''IM002'' SQL Native Error Code '0'
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. Use the mqsicvp command to test connectivity to this database.
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.
- Check that the database has an adequate number of database connections available for use.
- 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.
- On z/OS check the BIPDSNAO member of the component's dataset, and check the DB2 64bit ODBC driver (DSNAO64C) is in the STEPLIB.
- Use mqsisetdbparms to set the password to the correct value and try again. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Oct 02, 2013 4:53 pm Post subject: Re: Can't create ODBC datasource on new Integration Bus 9 se |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqsiman wrote: |
| The $ODBCINI, $ODBCSYSINI, and $IE02_PATH environment variables have been set. |
Have they been set in the command shell the broker is using?
| mqsiman wrote: |
| The odbc.ini odbcinst.ini should be correct because I used the provided templates and modified them. |
They should be, but there is a remote change of a typographical error. Remember that Linux is case sensitive where Windows is not.
| mqsiman wrote: |
| BIP2347E: Database error: SQL State ''IM002''; Native Error Code '0'; Error Text 'System information file not found. Please check the ODBCINI and the ODBCSYSINI environment variables are correctly set.' |
This is one thing which calls me to question your confidence.
| mqsiman wrote: |
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.
- Check that the database has an adequate number of database connections available for use.
...
- On systems that use $ODBCINI, check that the file pointed to by $ODBCINI has been correctly updated. |
This is another.
| mqsiman wrote: |
| - Use mqsisetdbparms to set the password to the correct value and try again. |
Also you don't even mention this command.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqsiman |
| Posted: Wed Oct 02, 2013 6:55 pm Post subject: Re: Can't create ODBC datasource on new Integration Bus 9 se |
|
|
Novice
Joined: 01 Oct 2013
Posts: 12
|
| Vitor wrote: |
| mqsiman wrote: |
| The $ODBCINI, $ODBCSYSINI, and $IE02_PATH environment variables have been set. |
Have they been set in the command shell the broker is using?
Yes. They get set when the $. mqsiprofile command is run.
bash-3.2$ cat /var/mqsi/common/profiles/setenv.sh
export ODBCINI=/var/mqsi/odbc.ini
export ODBCSYSINI=/var/mqsi
bash-3.2$
| mqsiman wrote: |
| The odbc.ini odbcinst.ini should be correct because I used the provided templates and modified them. |
They should be, but there is a remote change of a typographical error. Remember that Linux is case sensitive where Windows is not.
Double checked this again and I don't see anything wrong.
| mqsiman wrote: |
| BIP2347E: Database error: SQL State ''IM002''; Native Error Code '0'; Error Text 'System information file not found. Please check the ODBCINI and the ODBCSYSINI environment variables are correctly set.' |
This is one thing which calls me to question your confidence.
If I don't set any of $ODBCINI, $ODBCSYSINI, or $IE02_PATH I get different errors saying that the environment variable is not set.
| mqsiman wrote: |
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.
- Check that the database has an adequate number of database connections available for use.
...
- On systems that use $ODBCINI, check that the file pointed to by $ODBCINI has been correctly updated. |
This is another.
I've double checked all of these.
| mqsiman wrote: |
| - Use mqsisetdbparms to set the password to the correct value and try again. |
Also you don't even mention this command.
I have used this command to associate the datasource with the broker. If I don't I again get a different error message (please see below).
bash-3.2$ mqsisetdbparms DEVBROKER -n MDMDB -u mdm_apps
Enter password for user ID
Retype password for user ID.
BIP8071I: Successful command completion.
bash-3.2$ mqsicvp DEVBROKER -n MDMDB
BIP8290I: Verification passed for the ODBC environment.
BIP2393E: Database error: ODBC return code '-1' from data source ''MDMDB'' using ODBC driver manager ''''.
The broker received an error when processing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database about this error.
Use the following messages to determine the cause of the error. Typical problems are an incorrect data source, or table names. Correct either the database or the broker configuration. Use the mqsicvp command to test connectivity to this database.
BIP2347E: Database error: SQL State ''IM002''; Native Error Code '0'; Error Text 'System information file not found. Please check the ODBCINI and the ODBCSYSINI environment variables are correctly set.'
The error has the following diagnostic information: SQL State ''IM002'' SQL Native Error Code '0'
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. Use the mqsicvp command to test connectivity to this database.
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.
- Check that the database has an adequate number of database connections available for use.
- 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.
- On z/OS check the BIPDSNAO member of the component's dataset, and check the DB2 64bit ODBC driver (DSNAO64C) is in the STEPLIB.
- Use mqsisetdbparms to set the password to the correct value and try again.
bash-3.2$ mqsicvp DEVBROKER -n MDMDBXXX
BIP8272E: Datasource 'MDMDBXXX' has not been associated with broker 'DEVBROKER'.
This invocation of the mqsicvp command requires that the datasource name has been associated with the broker, using the mqsisetdbparms command.
Check that this datasource has been associated with the broker.
|
|
|
| Back to top |
|
|
| Tibor |
| Posted: Wed Oct 02, 2013 11:54 pm Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Oct 03, 2013 7:37 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
Are you sure ODBCSYSINI should be pointing to a directory an not to ODBCInst.INI ? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqsiman |
| Posted: Thu Oct 03, 2013 8:47 am Post subject: |
|
|
Novice
Joined: 01 Oct 2013
Posts: 12
|
|
| Back to top |
|
|
| mqsiman |
| Posted: Thu Oct 03, 2013 8:51 am Post subject: |
|
|
Novice
Joined: 01 Oct 2013
Posts: 12
|
;##########################################################################
;# ODBC database driver manager initialisation file. #
;##########################################################################
;# It is recommended that you take a copy of this file and then edit the #
;# copy. #
;# #
;# 1. For each data source, add the name of the data source into #
;# the 'List of data sources stanza' section. #
;# #
;# 2. For each data source, create a stanza in the #
;# 'Individual data source stanzas' section. #
;# #
;##########################################################################
;#######################################
;#### List of data sources stanza ######
;#######################################
[ODBC Data Sources]
MDMDB=DataDirect 7.0 ODBC Oracle Wire Protocol
;###########################################
;###### Individual data source stanzas #####
;###########################################
;# Oracle stanza
[MDMDB]
Driver=/opt/ibm/mqsi/9.0.0.0/ODBC/V7.0/lib/UKora26.so
Description=MDM DEV Environment
HostName=myserver.mycompany.org
PortNumber=1521
ServiceName=myoracleservicename
CatalogOptions=0
EnableStaticCursorsForLongData=0
ApplicationUsingThreads=1
EnableDescribeParam=1
OptimizePrepare=1
WorkArounds=536870912
ProcedureRetResults=1
ColumnSizeAsCharacter=1
LoginTimeout=0
;###### Mandatory information stanza ######
;##########################################
[ODBC]
InstallDir=/opt/ibm/mqsi/9.0.0.0/ODBC/V7.0
UseCursorLib=0
IANAAppCodePage=4
UNICODE=UTF-8 |
|
| Back to top |
|
|
| mqsiman |
| Posted: Thu Oct 03, 2013 9:09 am Post subject: |
|
|
Novice
Joined: 01 Oct 2013
Posts: 12
|
I installed isql on the server. It’s referencing the $ODBCINI environment variable and I’m able to connect through isql. This tells me that odbc.ini is fine. However, I still get the same error message.
bash-3.2$ isql MDMDB myuser mypassword
+---------------------------------------+
| Connected! |
| |
| sql-statement |
| help [tablename] |
| quit |
| |
+---------------------------------------+
SQL> quit
bash-3.2$ mqsicvp DEVBROKER -n MDMDB
BIP8290I: Verification passed for the ODBC environment.
BIP2393E: Database error: ODBC return code '-1' from data source ''MDMDB'' using ODBC driver manager ''''.
The broker received an error when processing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database about this error.
Use the following messages to determine the cause of the error. Typical problems are an incorrect data source, or table names. Correct either the database or the broker configuration. Use the mqsicvp command to test connectivity to this database.
BIP2347E: Database error: SQL State ''IM002''; Native Error Code '0'; Error Text 'System information file not found. Please check the ODBCINI and the ODBCSYSINI environment variables are correctly set.'
The error has the following diagnostic information: SQL State ''IM002'' SQL Native Error Code '0'
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. Use the mqsicvp command to test connectivity to this database.
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.
- Check that the database has an adequate number of database connections available for use.
- 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.
- On z/OS check the BIPDSNAO member of the component's dataset, and check the DB2 64bit ODBC driver (DSNAO64C) is in the STEPLIB.
- Use mqsisetdbparms to set the password to the correct value and try again. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Oct 03, 2013 9:10 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| mqsiman |
| Posted: Thu Oct 03, 2013 11:53 am Post subject: |
|
|
Novice
Joined: 01 Oct 2013
Posts: 12
|
| lancelotlinc wrote: |
| Did you sudo to the broker service Id before you ran mqsicvp ? |
yes
bash-3.2$ whoami
mqm
bash-3.2$ ps -ef | grep mqm
mqm 4774 5021 0 Sep29 ? 00:00:00 /opt/mqm/bin/runmqlsr -r -m DEVQMGR -t TCP -p 1415
mqm 4982 1 0 Sep17 ? 00:00:00 /opt/mqm/bin/amqzxma0 -m DEVQMGR
mqm 4989 4982 0 Sep17 ? 00:00:01 /opt/mqm/bin/amqzmuc0 -m DEVQMGR
mqm 4993 4982 0 Sep17 ? 00:00:03 /opt/mqm/bin/amqzmur0 -m DEVQMGR
mqm 4996 4982 0 Sep17 ? 00:00:00 /opt/mqm/bin/amqzmuf0 -m DEVQMGR
mqm 4998 4982 0 Sep17 ? 00:00:00 /opt/mqm/bin/amqrrmfa -m DEVQMGR -t2332800 -s2592000 -p2592000 -g5184000 -c3600
mqm 5000 4982 0 Sep17 ? 00:00:00 /opt/mqm/bin/amqzdmaa -m DEVQMGR
mqm 5021 4982 0 Sep17 ? 00:00:00 /opt/mqm/bin/amqzmgr0 -m DEVQMGR
mqm 5032 4996 0 Sep17 ? 00:00:00 /opt/mqm/bin/amqfqpub -mDEVQMGR
mqm 5038 4982 0 Sep17 ? 00:00:23 /opt/mqm/bin/amqzlaa0 -mDEVQMGR -fip0
mqm 5040 5021 0 Sep17 ? 00:00:00 /opt/mqm/bin/runmqchi -m DEVQMGR -q SYSTEM.CHANNEL.INITQ -r
mqm 5042 5021 0 Sep17 ? 00:00:04 /opt/mqm/bin/amqpcsea DEVQMGR
mqm 5049 5032 0 Sep17 ? 00:00:00 /opt/mqm/bin/amqfcxba -m DEVQMGR
mqm 5081 1 0 Sep17 ? 00:00:02 ./runmqlsr -t tcp -m DEVQMGR -p 1414
mqm 5087 5081 0 Sep17 ? 00:00:51 /opt/mqm/bin/amqrmppa -m DEVQMGR
root 13471 13433 0 08:47 pts/1 00:00:00 su mqm
mqm 13472 13471 0 08:47 pts/1 00:00:00 bash
root 14133 3678 0 09:02 ? 00:00:00 sshd: mqm [priv]
mqm 14135 14133 0 09:02 ? 00:00:00 sshd: mqm@notty
mqm 14136 14135 0 09:02 ? 00:00:00 /usr/libexec/openssh/sftp-server
mqm 23094 1 0 14:49 ? 00:00:00 bipservice DEVBROKER
mqm 23099 23094 15 14:49 ? 00:00:19 bipbroker DEVBROKER
mqm 23149 23099 0 14:49 ? 00:00:00 biphttplistener DEVBROKER
mqm 23152 23099 0 14:49 ? 00:00:00 /bin/bash /opt/ibm/mqsi/9.0.0.0/bin/startDataFlowEngine DEVBROKER 804ad266-4101-0000-0080-f561fbb5ee0a ServiceIntegration
mqm 23153 23152 3 14:49 ? 00:00:04 DataFlowEngine DEVBROKER 804ad266-4101-0000-0080-f561fbb5ee0a ServiceIntegration
mqm 23155 23099 0 14:49 ? 00:00:00 /bin/bash /opt/ibm/mqsi/9.0.0.0/bin/startDataFlowEngine DEVBROKER 0afd0a60-4101-0000-0080-9fbc2df33822
mqm 23156 23155 3 14:49 ? 00:00:03 DataFlowEngine DEVBROKER 0afd0a60-4101-0000-0080-9fbc2df33822 sdzelil
mqm 23157 23099 0 14:49 ? 00:00:00 /bin/bash /opt/ibm/mqsi/9.0.0.0/bin/startDataFlowEngine DEVBROKER 7636ce2e-4101-0000-0080-f9c0cd9ecda8
mqm 23161 23099 0 14:49 ? 00:00:00 /bin/bash /opt/ibm/mqsi/9.0.0.0/bin/startDataFlowEngine DEVBROKER 16277c3b-4101-0000-0080-b963982b95fb
mqm 23162 23161 3 14:49 ? 00:00:04 DataFlowEngine DEVBROKER 16277c3b-4101-0000-0080-b963982b95fb
mqm 23172 23157 5 14:49 ? 00:00:06 DataFlowEngine DEVBROKER 7636ce2e-4101-0000-0080-f9c0cd9ecda8
mqm 23389 13472 0 14:51 pts/1 00:00:00 ps -ef
mqm 23390 13472 0 14:51 pts/1 00:00:00 grep mqm
Last edited by mqsiman on Thu Oct 03, 2013 11:58 am; edited 1 time in total |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Oct 03, 2013 11:56 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| mqsiman |
| Posted: Thu Oct 03, 2013 11:59 am Post subject: |
|
|
Novice
Joined: 01 Oct 2013
Posts: 12
|
Actually no. Someone else installed IIB9. Should that cause my error though? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Oct 03, 2013 1:35 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
| Quote: |
BIP8040E: Unable to connect to the database.
The database cannot be accessed with the specified user Id and password pair. |
Are you sure the access has been granted to your userid and your passowrd is valid?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Oct 04, 2013 3:36 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| mqsiman wrote: |
Actually no. Someone else installed IIB9. Should that cause my error though? |
Whomever installed your IIB should be kept far away from any of your other applications as their depth of knowledge is questionable.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Oct 04, 2013 3:39 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| lancelotlinc wrote: |
Whomever installed your IIB should be kept far away from any of your other applications as their depth of knowledge is questionable. |
Should it be
'Whoever CONFIGURED your broker should be....'
configuring the broker with the right username etc is what's wrong. AFAIK, they don't need to reinstall
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
