DSXchange

Hi,

Please help us out...

How to configure DSN for Oracle In unix .

what changes has to be done in .uvodbc.config,.odbc.ini files.

Is there any other files that i need to modify

Please guide us

George

Welcome Aboard,
No, just those two files for an odbc connection. This has been discussed here before, search on keywords.

Are you planning on using ODBC? Or OCI? If the latter, then it's a matter of configuring DataStage for Oracle and it's documented in the Install and Upgrade Guide and the Plug-In Configuration Guide.

The mindset that you need is that DataStage is just another client as far as Oracle is concerned. So the usual environment variables, such as ORACLE_HOME, need to be set up for DataStage (in the dsenv script), the DSN (for ODBC) is set up in .odbc.ini and in uvodbc.config, and Oracle client software is set up in the Oracle directory (especially tnsnames.ora).

DSguru2B wrote:Welcome Aboard,
No, just those two files for an odbc connection. This has been discussed here before, search on keywords.

Sir,

our pre prod's DSN is working well and fine.so i checked the .odbc.ini,uvodbc.config files with our Development server. The files are almost the same.

But i didnt find the DSN name entry in any of the 2 files in pre-prod also.
What i feel is there should be a file where DSN name,userid to oracle,password should be stored.
Do we need to create a file like that.
Looking forward to yur replay
George

So... you are planning on using ODBC? Why not 'go native' and use OCI?

chulett wrote:So... you are planning on using ODBC? Why not 'go native' and use OCI?

I dont mind using anything OCI or ODBC.But to import metadata i need a DSN connection its not there.Can any one show me a copy of .odbc.ini and uvodbc.config files. I think these are not created properly.

You dont need ODBC to import the metedata, you can use Plug-in Metadata definitions to do your import.

If you have DataStage Enterprise edition, import Oracle table definitions using Orchestrate (orchdbutil). It imports the data types more accurately than does the OCI stage, particularly decimal data types.

georgesebastian wrote:What i feel is there should be a file where DSN name,userid to oracle,password should be stored.
Do we need to create a file like that.

All of that would be parametrized at the end of the day. Then these parameters would be retrieved however you want to. Some store it in a file. Some prefer using DataStage directory and create user defined enivornment variables which are then defaulted to $PROJDEF. Its your choice.

Are there issues with importing tables through the orchestrate schema definitions versus the plug-in metadata definitions? I have heard that when using paralleism the table structure that is imported through the orchestrate method works better then if it is done using the plug-in meta. Is this true? I am trying to figure out the best method for bringing in all of my source tables. The orchestrate schema method would require me to do it manually table by table where as the plug-in meta option allows me to select as many tables from oracle as I need.
Thanks

Welcome aboard. :D

Technically this is hijacking the thread, which is frowned upon - your question does not relate to configuring a DSN. In future please begin a new thread (choose "Post New Topic").

The Orchestrate method is more accurate, particularly with decimal/numeric data types.

travissolt wrote:Are there issues with importing tables through the orchestrate schema definitions versus the plug-in metadata definitions? I have heard that when using paralleism the table structure that is imported through the orchestrate method works better then if it is done using the plug-in meta. Is this true? I am trying to figure out the best method for bringing in all of my source tables. The orchestrate schema method would require me to do it manually table by table where as the plug-in meta option allows me to select as many tables from oracle as I need.
Thanks

We are using server jobs, i am using plugin metadata..but finding error"unable to initialize plugin"

My compllaint was related to travissolt's post, not yours.

"Unable to initialize plugin" is typically related to the plug-in not being able to find something it requires in the shared library search path or in the command directory search path. It can also result from required database environment variables (such as ORACLE_HOME) not being set correctly.

Have you searched the forum to see how others have resolved this same question?

George has a big 'ol thread on that very topic over in the Server forum. Right now he's got bigger fish to fry as DataStage won't start for him.