Connecting to Instance on Multiple Instance Machine

[JDionne]

I have a DB2 Server with two instances, a DB2 Instance and a DB2TEST Instance. How do I configure the DB2 stage in DS to connect to the correct Instance?
Jim

[ogmios]

I have a DB2 Server with two instances, a DB2 Instance and a DB2TEST Instance. How do I configure the DB2 stage in DS to connect to the correct Instance?
Jim

Not... you can only connect to 1 instance which you specify somewhere in the dsenv file.

We then catalog the second instance in the first and you can access the 2 instances.

We've been able to partially get what you ask to work but we always got stuck where you are now stuck: you specify database, not instance in the stage.

Ogmios

[ray.wurlod]

Is it possible to manage this through environment variables? The job parameter can access an environment variable. Just a thought.

[ogmios]

Is it possible to manage this through environment variables? The job parameter can access an environment variable. Just a thought.

The problem is that there can only be one environment variable set for "the" db2 instance and that DB2 stage only connects to databases not instances.

You can catalog databases from one instance in the main instance to be able to access them but if you want to have a clean seperation between the 2 instances on the same machine a.g. development and test server you're out of luck.

We raised the "problem" with Ascential about a year ago, and they came back that it was not supported.

Ogmios

[JDionne]

Is it possible to manage this through environment variables? The job parameter can access an environment variable. Just a thought.

The problem is that there can only be one environment variable set for "the" db2 instance and that DB2 stage only connects to databases not instances.

You can catalog databases from one instance in the main instance to be able to access them but if you want to have a clean seperation between the 2 instances on the same machine a.g. development and test server you're out of luck.

We raised the "problem" with Ascential about a year ago, and they came back that it was not supported.

Ogmios

So basicaly I have to do a federated database?
Jim

[ogmios]

Not really federated databases.

You make one DB2 instance your default one for datastage... the one specified in some environment variable.

Then you have your dba catalog databases of the other instance in your default instance. You can now access databases of the other instance via your default instance. In DB2 Client Configuration Assistant the databases of your default instance will be called "local databases", the other ones are just "pointers" to the database in the other instance.

It's not called federated databased...

Ogmios

[JDionne]

What I did was catalog a remote Instance to my primary instance, then I cataloged the remote Test DB. In the Controle Center it is seen as expected, but DS still cant find the Database. I know this is getting more into the DBA side of this, but do you have any other thoughts or suggestions?
Jim

[ogmios]

What I did was catalog a remote Instance to my primary instance, then I cataloged the remote Test DB. In the Controle Center it is seen as expected, but DS still cant find the Database. I know this is getting more into the DBA side of this, but do you have any other thoughts or suggestions?
Jim

Login on the DataStage server using the userid that you use to run the DataStage jobs... and see whether you can connect to the remote databases.

If you can't you will probably see an error message (which should explain you more). If it does work you still have to setup up the database in DataStage of course .odbc.ini/uvodbc/...

Ogmios

[JDionne]

Its all about the middleware!!! If you catalog the databae on the ETL server then it magicaly knows the DB is there and will connect!!!!!!!
Thanks for all the help
Jim