DIA500C in db2diag.log

[Odd Bjørn Andersen]

We are running av db2 system on Windows 4.0 and DB2 v 7.2, fixpack 9. I get
the following message in the db2diag.log file:

2004-10-06-11.58.52.578000 Instance:DB2 Node:000
PID:266(db2syscs.exe) TID:796 Appid:none
drda_as sqljp_ddm_dict_search Probe:413
DIA5000C A DRDA AS token "RECOVERABLE" was detected. The diagnostic data
returned is (SRVDGN): "FUNCTION ID = 0144, PROBE POINT = 0413, REASON CODE =
0x0200000F, RETURN CODE 1 = 0x0000C200, RETURN CODE 2 = 0x00000000, RETURN
CODE
3 = 0x00000000, MESSAGE = Parser: DDM code point not recognized
".
Dump File:C:\PROGRA~1\SQLLIB\DB2\266796.000 Data:**** DRDA AS CB ****
Dump File:C:\PROGRA~1\SQLLIB\DB2\266796.000 Data:**** FREE CCB - CCB # 1
****
..
..
..
..
I cannot find anything about what this is. Has anybody seen this before,
and knows what it is ?

We experience some cases of lock-timeout. Don't know if the timeouts has
anything to do with the error message.

--
Regards
-----------
Odd Bjørn Andersen

ErgoSolutions AS
Postboks 4364 Nydalen, 0402 Oslo
Telefon [phone], Telefaks 23 14 50 01
Direkte tlf.nr. 23 14 46 73, Mobilnr 970 84597
www.ergogroup.no

[JamesS]

"Odd Bjørn Andersen" wrote:

We are running av db2 system on Windows 4.0 and DB2 v 7.2,
fixpack 9. I get
the following message in the db2diag.log file:

2004-10-06-11.58.52.578000 Instance:DB2 Node:000
PID:266(db2syscs.exe) TID:796 Appid:none
drda_as sqljp_ddm_dict_search Probe:413
DIA5000C A DRDA AS token "RECOVERABLE" was detected. The
diagnostic data
returned is (SRVDGN): "FUNCTION ID = 0144, PROBE POINT = 0413,
REASON CODE =
0x0200000F, RETURN CODE 1 = 0x0000C200, RETURN CODE 2 =
0x00000000, RETURN
CODE
3 = 0x00000000, MESSAGE = Parser: DDM code point not
recognized
".
Dump File:C:PROGRA~1SQLLIBDB2266796.000 Data:**** DRDA AS
CB ****
Dump File:C:PROGRA~1SQLLIBDB2266796.000 Data:**** FREE CCB
- CCB # 1
****
..
..
..
..
I cannot find anything about what this is. Has anybody seen
this before,
and knows what it is ?

We experience some cases of lock-timeout. Don't know if the
timeouts has
anything to do with the error message.

--
Regards
-----------
Odd Bjørn Andersen

ErgoSolutions AS
Postboks 4364 Nydalen, 0402 Oslo
Telefon [phone], Telefaks 23 14 50 01
Direkte tlf.nr. 23 14 46 73, Mobilnr 970 84597
www.ergogroup.no

We had this problem today and it was caused by a v8 fp 7a client
trying to access the database server. In fact we had this recurring
every 5 minutes and it turned out to be db2cc retyrying the connection
and trying to bind a package against the db.

Once we uncataloged the db the errors stopped...

--
http://www.dbForumz.com/ This article was posted by author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbForumz.com/DB2-DIA500C-...ict157809.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbForumz.com/eform.php?p=612334

[JamesS]

"JamesS" wrote:

We had this problem today and it was caused by a v8 fp 7a
client trying to access the database server. In fact we had
this recurring every 5 minutes and it turned out to be db2cc
retyrying the connection and trying to bind a package against
the db.

Once we uncataloged the db the errors stopped...

We found out who the guilty party was by looking in the dump file
created and their user id was contained on the first line.

--
http://www.dbForumz.com/ This article was posted by author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbForumz.com/DB2-DIA500C-...ict157809.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbForumz.com/eform.php?p=612431