MaxDB 7.6.0.6.14 ERR-entry in knldiag

[Former Member]

Hello,

after updating MaxDB from 7.5.00.52 to 7.6.06.14 / 7.6.06.20 i recognized some ERROR-entries in knldiag. Server is an window2003/32bit

2011-10-24 17:10:34 0xFC0 20235 RTE ERROR=3

2011-10-24 17:10:34 0xFC0 20235 RTE SYSTEMERROR=3

2011-10-24 17:10:34 0xFC0 20235 RTE TRACE_OMS_ERROR=0

2011-10-24 17:10:34 0xFC0 20235 RTE TRACE_STOP_ERRORCODE=0

no further problems, sdb in online and accessible. What do the entries mean ?

[markus_doehr2]

> 2011-10-24 17:10:34 0xFC0 20235 RTE ERROR=3

> 2011-10-24 17:10:34 0xFC0 20235 RTE SYSTEMERROR=3

> 2011-10-24 17:10:34 0xFC0 20235 RTE TRACE_OMS_ERROR=0

> 2011-10-24 17:10:34 0xFC0 20235 RTE TRACE_STOP_ERRORCODE=0

Those are no errrors but parameters/settings of the RunTimeEnvironment (RTE).

Don't grep through files with "-i error" and get alerted if something is found

Markus

[Former Member]

Hi Markus,

thanks a lot. But do you have a recommendation what i can grepping instead? In the past (as ERR didn't exist as RTE parameter in the knldiag) it was an easy-to-use indicator. Is it a way to grep for the known knldiag-errors (-9000 to -9999) ?

Uwe