ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » mqsicvp -n <dbname> -u <username>

Post new topic  Reply to topic
 mqsicvp -n <dbname> -u <username> « View previous topic :: View next topic » 
Author Message
lancelotlinc
PostPosted: Fri Apr 08, 2011 5:08 am    Post subject: mqsicvp -n <dbname> -u <username> Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Ok, fellas and ladies. I **REALLY** need your help.

I now have a good db2 Connect client fully licensed. But I am unable to use ODBC from WMB to connect to the db instance.

I believe it is a configuration issue. Here are the particulars:

Code:
db2licm -l
Product name:                     "DB2 Connect Enterprise Edition"
License type:                     "User"
Expiry date:                      "Permanent"
Product identifier:               "db2consv"
Version information:              "9.7"
Concurrent connect user policy:   "Disabled"
Enforcement policy:               "Soft Stop"
Number of licensed authorized users: "1"








Code:

mqsicvp -n <dbname> -u <username>

BIP2322E: Database error: SQL State ''     ''; Native Error Code '-1366'; Error Text ''[IBM][CLI Driver] SQL1366N  A security plug-in "IBMOSauthclient" processing error occurred on the client. Reason code = "7". ''.





Code:
db2 connect to <dbname> user <username>
Enter current password for <username>:

   Database Connection Information

 Database server        = DB2 OS/390 8.1.5
 SQL authorization ID   = <username>
 Local database alias   = <dbname>




Code:
cat $ODBCINI
;##########################################################################
;# ODBC database driver manager 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.                                                #
;#                                                                        #
;# 2. For each data source, add the name of the data source into          #
;# the 'List of data sources stanza' section.                             #
;#                                                                        #
;# 3. For each data source, create a stanza in the                        #
;# 'Individual data source stanzas' section.                              #
;##########################################################################

;#######################################
;#### List of data sources stanza ######
;#######################################

[ODBC Data Sources]
<dbname>=IBM DB2 ODBC Driver

;###########################################
;###### Individual data source stanzas #####
;###########################################

;# DB2 stanza
[dbname]
DRIVER=/opt/ibm/mqsi/7.0/lib/libdb2Wrapper64.so
Description=DB2DB DB2 ODBC Database
Database=dbname

 
;##########################################
;###### Mandatory information stanza ######
;##########################################

[ODBC]
;# To turn on ODBC trace set Trace=1
Trace=1
;#TraceOptions=3
TraceFile=/var/ibm/odbctrace.log
TraceDll=/opt/ibm/mqsi/7.0/ODBC/V6.0/lib/odbctrac.so
InstallDir=/opt/ibm/mqsi/7.0/ODBC/V6.0
UseCursorLib=0
IANAAppCodePage=4
UNICODE=UTF-8




Code:
cat odbctrace.log?

ENTER SQLSetEnvAttr
                SQLHENV             0x047e7670
                SQLINTEGER                 200 <SQL_ATTR_ODBC_VERSION>
                SQLPOINTER                 3
                SQLINTEGER                   0

EXIT  SQLSetEnvAttr  with return code 0 (SQL_SUCCESS)
                SQLHENV             0x047e7670
                SQLINTEGER                 200 <SQL_ATTR_ODBC_VERSION>
                SQLPOINTER                 3
                SQLINTEGER                   0

ENTER SQLAllocConnect
                HENV                0x047e7670
                HDBC *              0x047e88a0

EXIT  SQLAllocConnect  with return code 0 (SQL_SUCCESS)
                HENV                0x047e7670
                HDBC *              0x047e88a0 ( 0x047e8ba0)

ENTER SQLSetConnectOption
                HDBC                0x047e8ba0
                UWORD                      102
                UDWORD                     0

EXIT  SQLSetConnectOption  with return code 0 (SQL_SUCCESS)
                HDBC                0x047e8ba0
                UWORD                      102
                UDWORD                     0

ENTER SQLSetConnectOption
                HDBC                0x047e8ba0
                UWORD                     2535
                UDWORD                     0

EXIT  SQLSetConnectOption  with return code 0 (SQL_SUCCESS)
                HDBC                0x047e8ba0
                UWORD                     2535
                UDWORD                     0

ENTER SQLConnect
                HDBC                0x047e8ba0
                UCHAR *             0xd1724e70 [4294967293] "<dbname>"
                SWORD                       -3
                UCHAR *             0xd1724e40 [4294967293] "<username>"
                SWORD                       -3
                UCHAR *             0x5a6aa260 [4294967293] "******"
                SWORD                       -3

EXIT  SQLConnect  with return code -1 (SQL_ERROR)
                HDBC                0x047e8ba0
                UCHAR *             0xd1724e70 [4294967293] "<dbname>"
                SWORD                       -3
                UCHAR *             0xd1724e40 [4294967293] "<username>"
                SWORD                       -3
                UCHAR *             0x5a6aa260 [4294967293] "******"
                SWORD                       -3

ENTER SQLError
                HENV                0x00000000
                HDBC                0x047e8ba0
                HSTMT               0x00000000
                UCHAR *             0xd1724bb0 (NYI)
                SDWORD *            0xd1724bcc
                UCHAR *             0x047f3020
                SWORD                     1024
                SWORD *             0xd1724bde

EXIT  SQLError  with return code 0 (SQL_SUCCESS)
                HENV                0x00000000
                HDBC                0x047e8ba0
                HSTMT               0x00000000
                UCHAR *             0xd1724bb0 [  5] "     "
                SDWORD *            0xd1724bcc (4294965930)
                UCHAR *             0x047f3020 [     125] "[IBM][CLI Driver] SQL1366N  A security plug-in "IBMOSauthclient" processing error occurred on the client. Reason code = "7"."
                SWORD                     1024
                SWORD *             0xd1724bde (125)

ENTER SQLError
                HENV                0x00000000
                HDBC                0x047e8ba0
                HSTMT               0x00000000
                UCHAR *             0xd1724bb0 (NYI)
                SDWORD *            0xd1724bcc
                UCHAR *             0x047f3020
                SWORD                     1024
                SWORD *             0xd1724bde

EXIT  SQLError  with return code 100 (SQL_NO_DATA_FOUND)
                HENV                0x00000000
                HDBC                0x047e8ba0
                HSTMT               0x00000000
                UCHAR *             0xd1724bb0 (NYI)
                SDWORD *            0xd1724bcc
                UCHAR *             0x047f3020
                SWORD                     1024
                SWORD *             0xd1724bde



_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
mqjeff
PostPosted: Fri Apr 08, 2011 5:29 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

It's probably PMR time.



It seems to be a db2 internal issue of some kind, except for the fact that the db2 client itself works just fine.

It could be an issue with the shell setup, but it seems odd.

Did mqsicvp prompt you for a password? Otherwise you'd need to pass that in?
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Fri Apr 08, 2011 6:00 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

The command I used was:

Code:

 mqsicvp -n <dbname> -u <username> -p <pwd>


I tried it without the password and mqsicvp threw an error, missing argument.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
mqjeff
PostPosted: Fri Apr 08, 2011 6:17 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Well, I thought so, but the [code]block didn't show it...

Is the db2 profile sourced from within mqsiprofile or common/profiles?
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Fri Apr 08, 2011 6:29 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

For the moment, I manually source it prior to running mqsicvp:

Code:
 . /home/db2inst1/sqllib/db2profile

_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
lancelotlinc
PostPosted: Wed Apr 13, 2011 3:58 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Problem solved. For those that may stumble onto this thread in the future, the issue was missing export environment variable.

Code:
export MQSI_64BIT_DB2_LIBRARY_NAME=/opt/ibm/db2/V9.7/lib64/libdb2.so


I'm requesting further information from IBM on this, but wanted to post the resolution.

Thanks to all who helped.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
mqjeff
PostPosted: Wed Apr 13, 2011 4:06 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Apparently there is an internal preference for DB2 9.1 libraries by default, if they are installed.

So the environment variable overrides that internal preference. Others should only see this issue if they have v9.1 installed on the same machine as other levels of DB2, particularly newer levels.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » mqsicvp -n <dbname> -u <username>
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.