Connectivity issue - Oracle

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
BharathiR
Participant
Posts: 10
Joined: Tue Apr 17, 2012 3:43 am

Connectivity issue - Oracle

Post by BharathiR »

All,
We have a sequence running 6 set of jobs, its a daily run , when the sequence is triggered first 4 jobs runs without any problem and the last two jobs having issue in connecting to the database getting below error.

scRetrieveAuditFields.ETL_JOBID_LIST: The connector could not establish a connection to data source IFP1 using user ETLJOB.

All the Jobs are connecting to the same Oracle database and only the last two jobs having this issue. Resubmitting the job for multiples times goes through.

Another fatal error is as

scRetrieveAuditFields.ETL_JOBID_LIST: ODBC function "SQLConnect" reported: SQLSTATE = HYT00: Native Error Code = 0: Msg = [IBM(DataDirect OEM)][ODBC Oracle Wire Protocol driver]Timeout expired.
ODBC function "SQLConnect" reported: SQLSTATE = 08001: Native Error Code = -6: Msg = [IBM(DataDirect OEM)][ODBC Oracle Wire Protocol driver][Oracle]Network Operation Timed Out. (CC_OdbcConnection::connect, file CC_OdbcConnection.cpp, line 578)

Sufficient sessions available to connect the database as per the DBAs.

All jobs are using the same code

Please help
Bharathiraja S
priyadarshikunal
Premium Member
Premium Member
Posts: 1735
Joined: Thu Mar 01, 2007 5:44 am
Location: Troy, MI

Post by priyadarshikunal »

Seems you are trying to connect oracle database using ODBC, any reasons for not using oracle enterprise or connector?

For your error, As the description suggests, Its timing out. Did you try to get the round trip time and route from datastage box to database?
Priyadarshi Kunal

Genius may have its limitations, but stupidity is not thus handicapped. :wink:
BharathiR
Participant
Posts: 10
Joined: Tue Apr 17, 2012 3:43 am

Post by BharathiR »

Issue resolved after using the Oracle Driver in ODBC entry. Looks strange and wierd but in the end workaround helped :P
Bharathiraja S
Post Reply