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

getting comm errors in db2diag.log instead of sql errors

P: n/a
I have DB2 V8.2 installed on an AIX system and I want to see the sql
errors that are occurring on the system. When I look at db2diag.log
the messages all look like this:

2006-05-09-07.58.56.097229-300 I252960516G411 LEVEL: Severe
PID : 14832 TID : 3086866112 PROC : db2agent
(instance) 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-1028 APPID: GA000BEF.I70F.01A009125841
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

Everything seems to be working fine. The JAVA applications are running
and I can use the DB2 Control Center to access the database.
When I cause an sql error, it just shows up as an "External Comm
error".

What do I need to change so that I can see the sql error messages in
the log?

Thanks!

May 10 '06 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.