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 » IIB Broker to DB2 - Connection settings

Post new topic  Reply to topic
 IIB Broker to DB2 - Connection settings « View previous topic :: View next topic » 
Author Message
kash3338
PostPosted: Thu Dec 24, 2015 12:38 am    Post subject: IIB Broker to DB2 - Connection settings Reply with quote

Shaman

Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India

Hi,

We have two AIX servers in place for IIB (IIB-1 and IIB-2) and two separate AIX servers for DB2 (DB2-1 and DB2-2).

The IIB-1 server points to DB2-1 server. Recently our Infra team took a snap shot of the complete IIB-1 server and DB2-1 server and moved to IIB-2 and DB2-2 servers respectively.

The problem that we are facing now is that, the IIB-2 server DSN is still pointing to DB2-1 server and not to DB2-2 server. We checked the below areas to verify if all the settings are correct,

- Delete the DSN from IIB-2 server and recreate them
- Verify the IP address of DB2 server in the DB2 catalog
- Created new Nodes in DB2 catalog pointing to DB2-2 server
- Created new DSN's in IIB-2 server

Even after all these, IIB-2 server is still pointing to DB2-1 DB. Since this server was setup with snapshot, is there any broker registry that needs to be cleared? What is missing here and what should be checked?

IIB v9.0.0.2
DB2 10
Back to top
View user's profile Send private message Send e-mail
smdavies99
PostPosted: Thu Dec 24, 2015 1:26 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Care to share your odbcini file with us?
_________________
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
View user's profile Send private message
kash3338
PostPosted: Thu Dec 24, 2015 2:00 am    Post subject: Reply with quote

Shaman

Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India

smdavies99 wrote:
Care to share your odbcini file with us?


Sure. The ODBC.INI does not include the IP Address of the Database server for DB2. Below is the ODBC.INI,

Code:

[ODBC Data Sources]
DB2DB=IBM DB2 ODBC Driver
ABCDB=IBM DB2 ODBC Driver
ORACLEDB=DataDirect 7.0 ODBC Oracle Wire Protocol
CBSUAT=DataDirect 7.0 ODBC Oracle RAC Wire Protocol
ORACLESSLDB=DataDirect 7.0 ODBC Oracle SSL Wire Protocol
SYBASEDB=DataDirect 7.0 ODBC Sybase Wire Protocol
SYBASEDBUTF8=DataDirect 7.0 ODBC Sybase UTF8 Wire Protocol
SQLSERVERDB=DataDirect 7.0 ODBC SQL Server Wire Protocol
JLIUAT=DataDirect 7.0 ODBC SQL Server Wire Protocol
INFORMIXDB=IBM Informix ODBC Driver
SOLIDDB_DB=IBM Solid DB ODBC Driver
IDSDB=IBM Informix Data Server Driver for ODBC and CLI

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

[ABCDB]
DRIVER=/home/mqm/sqllib/lib/db2o.o
Description=IBM DB2 ODBC Database
Trace=No
DMEnvAttr=SQL_ATTR_UNIXODBC_ENVATTR={DB2_CLI_DRIVER_INSTALL_PATH=/home/mqm/sqllib}
Database=ABCDB
FileUsage=1
DontDLClose=1

[ABCDBTEST]
DRIVER=/home/mqm/sqllib/lib/db2o.o
Description=IBM DB2 ODBC Database
Trace=No
DMEnvAttr=SQL_ATTR_UNIXODBC_ENVATTR={DB2_CLI_DRIVER_INSTALL_PATH=/home/mqm/sqllib}
Database=ABCDB
FileUsage=1
DontDLClose=1
Back to top
View user's profile Send private message Send e-mail
mqjeff
PostPosted: Thu Dec 24, 2015 5:45 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

A DB2 ODBC entry points to the configuration of the exact same named database connection definition in the DB2 client.
_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
kash3338
PostPosted: Thu Dec 24, 2015 6:58 am    Post subject: Reply with quote

Shaman

Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India

mqjeff wrote:
A DB2 ODBC entry points to the configuration of the exact same named database connection definition in the DB2 client.


Sorry mqjeff. Could not get your point here. Do you mean the DB Name and the DB alias name in the catalog should be same? Can you please elaborate more? Thanks!
Back to top
View user's profile Send private message Send e-mail
ghoshly
PostPosted: Thu Dec 24, 2015 10:21 am    Post subject: tnsname.ora entry ?? Reply with quote

Partisan

Joined: 10 Jan 2008
Posts: 333

How IIB 2 would understand to go and check to DB2 -2 database instead of DB2 -1?

Same database is pointed through both the DSN. What about the entries in the equivalent file for tnsname.ora for Oracle?
Back to top
View user's profile Send private message
kash3338
PostPosted: Thu Dec 24, 2015 5:10 pm    Post subject: Re: tnsname.ora entry ?? Reply with quote

Shaman

Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India

ghoshly wrote:
How IIB 2 would understand to go and check to DB2 -2 database instead of DB2 -1?

Same database is pointed through both the DSN. What about the entries in the equivalent file for tnsname.ora for Oracle?


The DSN's mentioned in the above ODBC.INI file is for the same DB in DB2-2 server. One was created as a new DSN in this server (ABCDBTEST) and the other was part of the initial Snapshot taken from IIB-1 server.

For DB2 Database, the IP address of the Database is given in the DB2 catalog file. We have ensured the catalog has the correct IP address of DB2-2 server. But still the DSN is pointing to DB2-1 DB. What else needs to be checked and wherelse does the Broker refer for the DB2 Database?
Back to top
View user's profile Send private message Send e-mail
smdavies99
PostPosted: Fri Dec 25, 2015 12:27 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

How does broker know about the DB2 Catalog?

In my limited (ok 14 years) experience of this product I've always used the ODBCini file to setup the IP address of the target DB.
There might be some method of using the DB2 Catalog intriduced in more recent versions of DB2 that I'm not aware of.
Do you have a link to the Documentation that says that you can use the DB2 Catalog for this? I'd like to learn how it can be done.
_________________
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
View user's profile Send private message
fjb_saper
PostPosted: Fri Dec 25, 2015 12:45 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Did you bounce the broker after your change to the ODBC.ini file?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
kash3338
PostPosted: Sun Dec 27, 2015 11:09 pm    Post subject: Reply with quote

Shaman

Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India

smdavies99 wrote:
How does broker know about the DB2 Catalog?

In my limited (ok 14 years) experience of this product I've always used the ODBCini file to setup the IP address of the target DB.
There might be some method of using the DB2 Catalog intriduced in more recent versions of DB2 that I'm not aware of.
Do you have a link to the Documentation that says that you can use the DB2 Catalog for this? I'd like to learn how it can be done.


The default sample odbc.ini that comes with the Broker does not mention the IP address in DB2 stanza. You can check here for the sample and here for the IIB Info-center details.

We will try by adding the IP address in the odbc.ini file.

fjb_saper wrote:
Did you bounce the broker after your change to the ODBC.ini file?


Yes. We did bounce the Broker every time we updated the file. No luck.
Back to top
View user's profile Send private message Send e-mail
smdavies99
PostPosted: Sun Dec 27, 2015 11:55 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Quote:
from the infocentre
n Database, type the DB2 alias. The data source name must be the same as the database alias name. If you are using a remote DB2 database, you must set up your client/server connection to resolve this alias to the correct database. For more information, see the DB2 documentation.


Have you done all of that correctly? Did your DB2 DBA help you out?
_________________
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
View user's profile Send private message
kash3338
PostPosted: Mon Dec 28, 2015 12:23 am    Post subject: Reply with quote

Shaman

Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India

smdavies99 wrote:
Quote:
from the infocentre
n Database, type the DB2 alias. The data source name must be the same as the database alias name. If you are using a remote DB2 database, you must set up your client/server connection to resolve this alias to the correct database. For more information, see the DB2 documentation.


Have you done all of that correctly? Did your DB2 DBA help you out?


We have been working with our DB2 DBA to debug this issue and the above points are taken care.

The problem is, we are not sure where the IIB Broker is referring for the IP address of the DB2 DB. The catalog file has the correct IP address of DB2-2 server, but still the data flows to DB2-1 server.

Again the same question, since the IIB-2 server was setup with a snapshot of IIB-1 server, is there a problem here? Where all does the Broker look for the DB details apart from the ODBC.ini and DB2 Catalog?
Back to top
View user's profile Send private message Send e-mail
mqjeff
PostPosted: Mon Dec 28, 2015 10:16 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

In Driver, add the full path of your DB2 installation.
In Description, type a meaningful description of the database. This field is for information only and does not affect the connection.
In Database, type the DB2 alias. The data source name must be the same as the database alias name. If you are using a remote DB2 database, you must set up your client/server connection to resolve this alias to the correct database.

If the requirement is to have multiple stanzas that refer to the same DB2 database, aliases must be created in DB2 by using the DB2 CATALOG command. These aliases can then have their own stanza in the ODBCINI file.

The ODBCINI file cannot be used to set up aliases for DB2.

_________________
chmod -R ugo-wx /
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 » IIB Broker to DB2 - Connection settings
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.