By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,514 Members | 1,693 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,514 IT Pros & Developers. It's quick & easy.

SQL30020N Execution failed because of a Distributed Protocol Error

P: n/a
The Error in play is
CLI Driver][DB2/6000] SQL30020N Execution failed because of a
Distributed Protocol Error that will affect the successful execution of
subsequent commands and SQL statements: Reason Code "". SQLSTATE=58009
sqlstate = 40003

My Target is a DB2/UDB 8.2.2 database on SuSE Linux.

This has been happening regularly.

First is my hope that there is a quick fix to get over this problem.

Secondly, however, I'd like to understand how connection timeouts, lock
timeouts etc affect DB2 and what are the settings to tweak and play
around with to find the optimum for my environment.

The Client in this transaction is a INFORAMTICA Workflow making
Insert/Updates in Normal Mode.

The error is from the DB2 database.

Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Ian
Zri Man wrote:
The Error in play is
CLI Driver][DB2/6000] SQL30020N Execution failed because of a
Distributed Protocol Error that will affect the successful execution of
subsequent commands and SQL statements: Reason Code "". SQLSTATE=58009
sqlstate = 40003


Are you seeing anything in the db2diag.log? What version/fixpack of the
DB2 client software are you running on the Informatica server?

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.