| Author |
Message
|
| rammer |
 Posted: Fri Apr 22, 2016 8:28 am Post subject: MQSICVP Failing |
 |
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
Message Broker 8.0.0.6
Platform AIX
DB2 10.5 Client installed
DB2 DB is remote
odbc.ini file is set up correct (I think)
;#######################################
[ODBC Data Sources]
DB2DB=IBM DB2 ODBC Driver
;###########################################
;###### Individual data source stanzas #####
;###########################################
;# DB2 stanza
[DB2DB]
DRIVER=/opt/IBM/db2/V10.5/lib64/db2o.o
Description=IBM DB2 ODBC Database
Database=DB2DB
;##########################################
;###### Mandatory information stanza ######
;##########################################
[ODBC]
InstallDir=/opt/IBM/mqsi/8.0/ODBC/V6.0
UseCursorLib=0
IANAAppCodePage=4
UNICODE=UTF-8
~
Environment variables are set and point to correct odbc
$ env | grep ODBC
ODBCSYSINI=/var/mqsi/odbc/
ODBCINI=/var/mqsi/odbc/odbc.ini
LIBPATH=/home/d2d1/sqllib/lib64:
/home/d2d1/sqllib/lib64/gskit:
/home/d2d1/sqllib/lib64/gskit:
/home/d2d1/sqllib/lib64/gskit:
/home/d2d1/sqllib/lib64/gskit:
/opt/IBM/mqsi/8.0/jre17/lib/ppc64:
/opt/IBM/mqsi/8.0/jre17/lib/ppc64/classic:
/opt/ibm/IE02/2.0.0/lib:
/opt/IBM/mqsi/8.0/xml4c/lib:
/opt/IBM/mqsi/8.0/lib:
/opt/IBM/mqsi/8.0/bin:
/opt/IBM/mqsi/8.0/ODBC/V6.0/lib:
/opt/IBM/mqsi/8.0/xlxpc/lib:
/opt/IBM/mqsi/8.0/dfdlc/lib
db2 environment set up correct
$ env | grep DB2
DB2LIB=/home/d2d1/sqllib/lib
DB2DIR=/opt/IBM/db2/V10.5
DB2_NET_CLIENT_PATH=
DB2_HOME=/home/d2d1/sqllib
DB2INSTANCE=d2d1
mqsi@b0d0mqd2:/var/mqsi/odbc>
Issue the following
db2 connect to DB2DB ..... from client works
run following and no error
$ mqsicvp TEST.BROKER
BIP8873I: Starting the component verification for component 'TEST.BROKER'.
BIP8876I: Starting the environment verification for component 'TEST.BROKER'.
BIP8894I: Verification passed for 'Registry'.
BIP8894I: Verification passed for 'MQSI_REGISTRY'.
BIP8894I: Verification passed for 'Java Version - 1.7.0 IBM AIX build pap6470sr8fp10ifix-20150313_01(SR8 FP10+IV70681)
BIP8894I: Verification passed for 'MQSI_FILEPATH'.
BIP8878I: The environment verification for component 'TEST.BROKER' has finished successfully.
BIP8882I: Starting the WebSphere MQ verification for component 'TEST.BROKER'.
BIP8886I: Verification passed for queue 'SYSTEM.BROKER.ADMIN.QUEUE' on queue manager 'TEST.BROKER'.
BIP8886I: Verification passed for queue 'SYSTEM.BROKER.EXECUTIONGROUP.QUEUE' on queue manager 'TEST.BROKER'.
BIP8886I: Verification passed for queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'TEST.BROKER'.
BIP8884I: The WebSphere MQ verification for component 'TEST.BROKER' has finished successfully.
BIP8290I: Verification passed for the ODBC environment.
BIP8874I: The component verification for 'TEST.BROKER' has finished successfully.
BIP8071I: Successful command completion.
Then run mqsicvp to test connectivity between odbc and DB by bypassing Broker at this stage and it fails not making any attempt to connect. IVe obviously got something wrong but cant spot it for life of me.
$ mqsicvp -n DB2DB -u ***** -p *****
BIP8290I: Verification passed for the ODBC environment.
BIP2393E: Database error: ODBC return code '-1' from data source ''DB2DB'' 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.
So my main problem at moment is getting mqsicvp to work before even worrying about Broker connectivity to DB.
Thanks in advance for any assistance. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Apr 22, 2016 8:34 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Look in the odbc trace log (for broker).
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| rammer |
| Posted: Fri Apr 22, 2016 8:45 am Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
If you mean this one MQJEFF, then Im having a issue with getting any output 
or Linux and UNIX operating systems using WebSphere® Message Broker ODBC Database Extender drivers:
To initiate trace for ODBC activity, edit the [ODBC] stanza in the odbcinst.ini file in the directory pointed to by your ODBCSYSINI environment variable as follows:
Change Trace=no to Trace=yes.
Specify a path and file name for TraceFile
Ensure that the TraceFile entry points to a file system that has enough space to receive the trace output
As far as I can tell the environment setting is correct for ODBCSYSINI and ODBC ie pointing to the correct one.
$ env | grep ODBC
ODBCSYSINI=/var/mqsi/odbc/
ODBCINI=/var/mqsi/odbc/odbc.ini
$ cat odbcinst.ini
;##########################################################################
;# ODBC database driver manager system initialisation file. #
;##########################################################################
;# It is recommended that you take a copy of this file and then edit the #
;# copy. #
;# #
;# 1. Complete the 'Mandatory information stanza' section #
;# at the end of the file. #
;# #
;##########################################################################
;##########################################
;###### Mandatory information stanza ######
;##########################################
[ODBC]
;# To turn on trace set Trace=yes
Trace=yes
TraceFile=/tmp/odbctrace.out
;# Threading is not a configurable property
Threading=2
But no file is generated |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Apr 22, 2016 8:31 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
| Code: |
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. |
|
So which of these steps did you follow? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rammer |
| Posted: Sun Apr 24, 2016 5:33 am Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
| fjb_saper wrote: |
| Quote: |
| Code: |
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. |
|
So which of these steps did you follow? |
All off those that are relevant.
As mentioned checked Env Settings are correct by calling the environment to log into the odbc file.
This is on AIX
I can connect ot the DB2 client fine using db2 connect
Currently using mqsicvp to bypass broker connection and just test odbc.ini > db2 which is failing. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Apr 24, 2016 9:18 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Did you check the last line in the suggested actions?
run mqsidbparms and set the user and password for the connection?
Did you bounce the broker after running mqsidbparms successfully?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rammer |
| Posted: Sun Apr 24, 2016 10:47 pm Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
| fjb_saper wrote: |
Did you check the last line in the suggested actions?
run mqsidbparms and set the user and password for the connection?
Did you bounce the broker after running mqsidbparms successfully?
|
As mentioned I am testing this command without the Broker. (However I have also tested it using broker and fails exactly the same)
<Invocation where data source names have not been associated with the broker
When you run the mqsicvp command with parameters shown in the following syntax diagram, the command provides ODBC test tool function. You can use the command to display useful information about a user data source, or compare two user data sources. On Linux and UNIX systems only, invocations of the command that use these parameters also verify that the ODBC environment (if specified) is configured correctly. In these cases, the command checks that the ODBCINI, ODBCSYSINI, and IE02_PATH variables are set.
Each data source name (DSN) is fully specified with a user name and password.
This invocation does not rely on an association between the broker and the data source, and returns information about the data source even when there is no association with a broker.> |
|
| Back to top |
|
|
| rammer |
| Posted: Thu May 05, 2016 12:11 am Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
| Jut to close this thread all is fixed. There was a mistake with the IE02_PATH variable, somebody had entered one into the .profile for broker user that was overwriting one set in mqsiprofile and had incorrect path... |
|
| Back to top |
|
|
|
|
