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 » SQLConnectW return -1 using mqsicreatebroker on Solaris

Post new topic  Reply to topic
 SQLConnectW return -1 using mqsicreatebroker on Solaris « View previous topic :: View next topic » 
Author Message
AndrewGriffiths
PostPosted: Thu Jan 24, 2002 5:48 pm    Post subject: Reply with quote

Newbie

Joined: 23 Jan 2002
Posts: 2
Location: Candle Corp

Hi.

I'm encountering a problem which causes mqsicreatebroker to hang everytime
I try to create a broker while it's trying to do database access. If you turn
on odbc tracing the message

EXIT SQLConnectW with return code -1 (SQL_ERROR)

occurs.

Having checked the .odbc.ini file it appears everything is correct and the
libraries are there....and "db2 connect MQSIBKDB" works aswell...any ideas?

WMQI2.1,
Solaris
DB2 7.2 EE (Fixpack 5)

<< copy of main parts of .odbc.ini follows >>
[ODBC Data Sources]
MQSIBKDB=IBM DB2 ODBC Driver

[MQSIBKDB]
Driver=/export/home/db2inst1/sqllib/lib/libdb2.so
Description=MQSIBKDB DB2 ODBC Database
Database=MQSIBKDB

[ODBC]
Trace=1
TraceFile=/var/wmqi/odbc/odbctrace.out
TraceDll=/opt/wmqi/merant/lib/odbctrac.so
InstallDir=/opt/wmqi/merant

Andrew.
Back to top
View user's profile Send private message Send e-mail
Outdesign
PostPosted: Fri Jan 25, 2002 7:20 am    Post subject: Reply with quote

Apprentice

Joined: 16 Sep 2001
Posts: 38
Location: Hampshire, UK

Three things come to mind here ...

1. The IBM Supported Software site does not indicate that MQSeries Integrator Version 2
currently supports DB2 v7.1 FixPack 5 ?

2. How did you installed DB2 v7.1 FixPack 5 ?

DB2 v7.1 FixPack 5 is not truely accumulative and you must use the interim step of
applying FixPack 3 which effectively applies a name (version) change to DB2 v7.2 and
then apply FixPack 4 / 5.

This is my understanding and you should confirm this with DB2.

3. Are you using the DB2 Universal Database Version 7.1 FixPack 2, 2a, 3 and 7.2 workaround
of renaming the libdb2_36.so.1 file to libdb2.so.1 ?

This workaround is mandatory if you are using DB2 v7.1 FixPack 2 or higher with MQSI.

Suggest you open a problem with IBM MQSI support and they should have further info on this.
Back to top
View user's profile Send private message Visit poster's website
AndrewGriffiths
PostPosted: Tue Jan 29, 2002 3:34 pm    Post subject: Reply with quote

Newbie

Joined: 23 Jan 2002
Posts: 2
Location: Candle Corp

Thanks very much for your reply!

Your information was very useful and the problem turned out to be
that I was unaware of the workaround necessary (renaming libdb2_36.so.1 to
libdb2.so.1). Unfortunately this doesn't seem to be mentioned in the fixpack
5 readmes!

I can confirm at least that now brokers can be created without causing a
hang! and will proceed with testing operation.

Thanks again,

Andrew.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SQLConnectW return -1 using mqsicreatebroker on Solaris
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.