Connect to Oracle

crouse · Post by **crouse** » Mon Aug 11, 2008 8:37 am

Does DataStage use the tnsnames.ora file that you added the hosts to?

The tnsnames.ora file must be the proper place under $ORACLE_HOME as set in dsenv, or else declare via $TNS_ADMIN in dsenv.

-Craig

crouse · Post by **crouse** » Mon Aug 11, 2008 8:41 am

Does DataStage use the tnsnames.ora file that you added the hosts to?

The tnsnames.ora file must be the proper place under $ORACLE_HOME as set in dsenv, or else declare via $TNS_ADMIN in dsenv.

-Craig

keshav0307 · Post by **keshav0307** » Mon Aug 11, 2008 9:32 am

- check which services are currently known by the listener by executing: lsnrctl services <listener name>

- Check that the SERVICE_NAME parameter in the connect descriptor of the net service name used specifies a service known by the listener.

- If an easy connect naming connect identifier was used, check that the service name specified is a service known by the listener.

- Check for an event in the listener.log file.

kishorenvkb · Post by **kishorenvkb** » Mon Aug 11, 2008 2:09 pm

Actually... we do not have the databases on the same server as the DataStage.
We were using the EZCONNECT instead of tnsnames.ora. It was working before because the port that we were supposed to be using was the default port on the server.
But, with the change in the port numbers... the default port is not the port that we should be connected to and hence it was failing.
After adding the port number to the server name like in //ServName:Port/DatabaseName, the jobs started working.

Thanks for all the hints on this one.