regarding peculiar problem with datastage server

vijaykumar · Post by **vijaykumar** » Fri Dec 08, 2006 7:01 pm

Hi,
we have compiled the job and saved. even the jobs which have worked fine now facing with peculiar problem.
i got a peculiar problem, iam getting error.

[data stage][sql clinet][odbc][oracle][odbc][ora]ora-12535.

tns operation timed out.

plz help me out, we dont have any dba here, and you people are gurus , so plz do help me.

cheers;
vijay

ray.wurlod · Post by **ray.wurlod** » Fri Dec 08, 2006 9:16 pm

Get a DBA. Seriously. No Oracle site should be without one.

On the server, issue the command oerr ORA 12535 to discover what this error code means and, if you're lucky, what remedial action is appropriate.

And please do co-ordinate with your colleague so that we aren't answering the same question twice.

Oh, in relation to your subject line, it's not a DataStage issue at all.

johnthomas · Post by **johnthomas** » Sat Dec 09, 2006 6:22 am

Try connecting to oracle using toad or sqlplus .If you have problems verify whether entries tnsnames.ora are correct .I dont think this is Dstage problem .

chulett · Post by **chulett** » Sat Dec 09, 2006 9:19 am

It's not... and unfortunately you have just strayed into the DBA Woods, sometimes also known as The Forest Of No Return.

Code: Select all

$ oerr ora 12535
12535, 00000, "TNS:operation timed out"
// *Cause: The requested connection could not be completed within the timeout
// period specified by the CONNECT_TIMEOUT parameter in listener.ora. This
// error arises from the tnslsnr.
// *Action: Either reconfigure CONNECT_TIMEOUT to be 0, which means
// wait indefinitely, or reconfigure CONNECT_TIMEOUT to be some higher
// value. Or, if the timeout is unacceptably long, turn on tracing
// for further information.

The Listener must be running or I'm pretty sure you would have gotten a different error, a hard failure. As JT notes, try connecting from some other source and see if the problem persists. I'm guessing that, with no DBA (!!), you'll need to resort to stopping and restarting at least the listener if not the database as well. Or heck, it's Windows... reboot the server.

+1 to what Ray said. Get a DBA. Seriously. You really cannot run Oracle without one... at least not without a part-time, on-call, can-you-swing-by-and-help-us one. Seriously. Can you tell we're serious?