Oracle Connector error while Import and view data from 8.7

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
mandyli
Premium Member
Premium Member
Posts: 898
Joined: Wed May 26, 2004 10:45 pm
Location: Chicago

Oracle Connector error while Import and view data from 8.7

Post by mandyli »

Hi

we have migrated jobs from 8.1 to 8.7 and using ORACLE 11G .

we have DEV,QA & PROD environments. I can able to use ORACLE connector stage on QA environment and following path set same way on all the 3 (DEV,QA & PROD) servers.

ORACLE_HOME=/app/oracle/product/11.2.0/client_1
TNS_ADMIN=/app/oracle/product/11.2.0/client_1/network/admin

But when I try to use oracle connector stage and import metadata from using Table wizard from DEV I am getting following error.

" The connector could not find the tnsnames.ora file.
Verify that ORACLE_HOME or TNS_ADMIN environment varaibles are set.
Alternatively use Oracle easy connect naming method or specify a full connect descriptor "

But we have applied latest 8.7 FP1 too.

is this anything missing here ?


Thanks
Man
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

The obvious answer would be "yes". :wink:

Verify your ORACLE_HOME in DEV is what you think it is. Verify your tnsnames file is where you say it is and is accessable by your DataStage user. And just as an FYI - you only need to set TNS_ADMIN if your tnsnames file is not under $ORACLE_/network/admin. It doesn't hurt but it is... unnecessary. It's meant to be an override of the default.
-craig

"You can never have too many knives" -- Logan Nine Fingers
mandyli
Premium Member
Premium Member
Posts: 898
Joined: Wed May 26, 2004 10:45 pm
Location: Chicago

Post by mandyli »

Thanks.

But we are not using tnsnames.ora file we are using ldap.

Thanks
Man
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

OK... still, since it is working in QA & PROD, your mission is to discover what is different in DEV that is causing this failure. It could be on the LDAP, Oracle or the DataStage side, so check everywhere. I don't think anyone will be able to hand you the solution, instead it will require good old fashioned detective work on your part.
-craig

"You can never have too many knives" -- Logan Nine Fingers
mandyli
Premium Member
Premium Member
Posts: 898
Joined: Wed May 26, 2004 10:45 pm
Location: Chicago

Post by mandyli »

Thanks

we are not using tnsname.ora using ldap.ora . Is this any issue with user?


Thanks
Man
Post Reply