Results 1 to 4 of 4
  1. #1
    Join Date
    Jan 2009
    Posts
    3

    Unanswered: error message in db2diag.log

    Server Environemnt: DB2 8.2 in AIX 5.3
    Client : Db2 Admin Client on Windows XP

    db2diag.log file contains many entries like this one:

    2008-12-01-09.44.48.729489-300 I23608418A435 LEVEL: Severe
    PID : 942292 TID : 1 PROC : db2agent (instance) 0
    INSTANCE: myinst NODE : 000 DB : mydb
    APPHDL : 0-1396 APPID: GB460770.B804.025442144445
    FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
    RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
    "External Comm error"


    This error message is being recorded even when the user is not trying to connect to database.

    What this error message mean? Could someone provide me IBM link that explains this error message? Looked into all previous postings in this and other forumns, but, those didn't help.

    Thanks.

  2. #2
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Try turning off the Health Monitor (DBM config) and turning off automatic maintenance (db config).
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  3. #3
    Join Date
    Jan 2009
    Posts
    3

    still the same

    Health monitor parameter in the server is already in "Off" state only. Auto maintenance feature is not there in v8.2.

    what puzzles me is why the client is attemting attach to the instance (though there was no attempt made by the user)? This is like security issue - if someone gets the connection parameter for a database, he/she can overwhlem the server with these error messages, make the db2diag.log file to grow very huge...

    Also, why there is no proper documentation from IBM on this error message?

    Since I can get the clinet IP Address from the error message (one good thing!), I could turn off the workstation (and the error messages do not appear) as a temporary fix.

    Thanks.

  4. #4
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Quote Originally Posted by balla_09
    Also, why there is no proper documentation from IBM on this error message?
    A ZRC error is meant to be analyzed by IBM support, not by customers. It is bug in the DB2 code, not a user error.

    You could install the latest DB2 8.2 fixpack and see if if the problem is resolved, or call IBM support.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •