Mainframe DB2 connection problem

sreddy · Post by **sreddy** » Wed Apr 07, 2010 2:18 pm

Hi

My job is aborted due to blew mentioned problem.

MF_READ_VNR_LVW,0: Fatal Error: Fatal: [IBM][CLI Driver] SQL0902C A system error (reason code = "18") occurred. Subsequent SQL statements cannot be processed. SQLSTATE=58005
[IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "172.24.65.53". Communication function detecting the error: "recv". Protocol specific error code(s): "*", "*", "0". SQLSTATE=08001
SQLFetch: Error retrieving results from server.

Thanks
SReddy

ray.wurlod · Post by **ray.wurlod** » Wed Apr 07, 2010 2:40 pm

A communication error has been detected.

Involve your network administrator and DB2 DBA.

sreddy · Post by **sreddy** » Mon Apr 12, 2010 7:53 am

Thank Ray

Here is the DB2 Admin reply:

You are getting below error message.

DSNT408I SQLCODE = -514, ERROR: THE CURSOR SQL_CURSH200C4 IS NOT IN A
PREPARED STATE
DSNT418I SQLSTATE = 26501 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNXERT2 SQL PROCEDURE DETECTING ERROR

Explanation: The application program has tried to use a cursor,
'cursor-name,' that is not in a prepared state. The cursor is associated
with a statement that either (1) has never been prepared, or (2) has been
invalidated by a commit or rollback operation.

=============================================
I ran the same job today, but still i am facing the same problem.

In this job i am using DB2API stage for another source mainframe DB2 tables. Those are working fine.

MF_READ_VNR_LVW,0: Fatal Error: Fatal: [IBM][CLI Driver] SQL0902C A system error (reason code = "18") occurred. Subsequent SQL statements cannot be processed. SQLSTATE=58005
[IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "172.24.65.53". Communication function detecting the error: "recv". Protocol specific error code(s): "*", "*", "0". SQLSTATE=08001
SQLFetch: Error retrieving results from server.
==========================================
Can any one resolve this problem.

Thanks
SReddy

chulett · Post by **chulett** » Mon Apr 12, 2010 8:03 am

Now involve your network administrator.

sreddy · Post by **sreddy** » Mon Apr 12, 2010 8:32 am

Thank you Hulett

For the debug purpose. i ran the separate job only particular piece DB2 source table with same SQL script write in to seq file . This is working fine.

Why specifically creating problems when i ran whole job.

Thanks
SReddy

chulett · Post by **chulett** » Mon Apr 12, 2010 8:43 pm

No idea. You are the victim of a "communication error" as noted in the log messages you posted, hence the suggestion to involve the first line of defense for issues of that nature. And I think your DB2 DBA is leading you astray, not sure where they got all of the errors they reported back to you but I would assume they were caused by the "communication error" rather than being the source of it.