ODBC Stage behaviour

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
harshada
Premium Member
Premium Member
Posts: 92
Joined: Tue May 29, 2007 8:40 am

ODBC Stage behaviour

Post by harshada »

This is not a query but wanted to share something which I was unaware of.

One of my jobs use ODBC stage to connect to Sybase db. Here the table definition has been imported from prod environment database. But the Datasource name, user pwd which are required to be mentioned in the 'Stage' tab of ODBC stage has the details of QA environment (different server than prod). I expected the job to point to QA database and run, but in fact it is pointing to prod d/b and running, as the table def has been imported from prod. Is this a obvious behaviour ?
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Server job (as marked) or parallel job (as posted)?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
harshada
Premium Member
Premium Member
Posts: 92
Joined: Tue May 29, 2007 8:40 am

Post by harshada »

Its a Server job
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Moved.

Where the metadata was imported from makes no difference - as long as it is correct, of course. What it actually connects to depends on the connection being used, the odbc entry your stage specifies.
-craig

"You can never have too many knives" -- Logan Nine Fingers
SURA
Premium Member
Premium Member
Posts: 1229
Joined: Sat Jul 14, 2007 5:16 am
Location: Sydney

Re: ODBC Stage behaviour

Post by SURA »

Try to use the ODBC in the administrative tool (Windows) and try to connect the DB and ensure which DB it is trying to connect.

The same DB the job will connect!!

DS User
Post Reply