SQLFetch: Error retrieving results

rohitagarwal15 · Post by **rohitagarwal15** » Mon Jun 20, 2011 8:02 am

Hi,

Currently jobs keep failed at "SQLFetch: Error retrieving results from server." and more and more jobs have the problem.

What's the problem: Datastage side or DB2 side? How to fix the problem?

Data can be viewd through view data but while runnning it aborts giving above error. Also checked with DB2 team as there is no lock on any tables also..

ray.wurlod · Post by **ray.wurlod** » Mon Jun 20, 2011 6:06 pm

What other warnings/errors are logged?

Is it likely that the DataStage server/network/database server is overloaded causing timeouts to trigger?

rohitagarwal15 · Post by **rohitagarwal15** » Mon Jun 20, 2011 11:13 pm

These are the errors we get in single job run .

1)access_method_subscription_history,0: Failure during execution of operator logic.
2)access_method_subscription_history,0: Fatal Error: Fatal: SQLFetch: Error retrieving results from server.
3)node_node1: operator [access_method_subscription_history], partition 0 of 1, processID 4,280,546 on node1, player 1 terminated unexpectedly.
4)main_program: Unexpected exit status 1

We are running our jobs on two node configuration file.

ray.wurlod · Post by **ray.wurlod** » Tue Jun 21, 2011 4:41 pm

"Terminated unexpectedly" can mean that someone or something has killed a process or a network connection. Is the problem reproducible?

rohitagarwal15 · Post by **rohitagarwal15** » Tue Jun 21, 2011 11:26 pm

Once i restart the Datastage services now everything is fine but still don't know the root cause of this issue ..

ray.wurlod · Post by **ray.wurlod** » Wed Jun 22, 2011 12:53 am

"Terminated unexpectedly" can mean that someone or something has killed a process or a network connection.

chulett · Post by **chulett** » Wed Jun 22, 2011 6:52 am

Meaning, without it being reproducible you'll probably never know.

rohitagarwal15 · Post by **rohitagarwal15** » Sat Jun 25, 2011 1:16 am

But we have checked with Development team as no one has kill any process id so how can it happen as you are saying "Terminated unexpectedly" can mean that someone or something has killed a process or a network connection.
Even my connection was also not disconnected.
Pls provide valuable suggestions.!!

chulett · Post by **chulett** » Sat Jun 25, 2011 7:04 am

He said "can mean" not "does mean". Is this an ongoing issue? Since you've chaged the status, what is your 'workaround' for this?

rohitagarwal15 · Post by **rohitagarwal15** » Sun Jun 26, 2011 11:22 pm

As when i restarted my DS services then afterwards it work fine so i am using this as my temporary solution.