When dbm cfg parameter DIAGSIZE is set to a value larger then
zero, rotating log feature is activated. Once enabled db2 writes
to db2diag.<x>.log (where x is an increasing number), and should
no more write to db2diag.log. However some of the DB2 processes
still logs data to db2diag.log not to db2diag.<x>.log. For
example, we might see the below set of trace points in
db2diag.log when DIAGSIZE is set to a number greater then zero,
db2diag.0.log entries.
-----------------------
2011-02-24-10.23.28.578543+330 I14353A439 LEVEL: Warning
PID : 602178 TID : 2829 PROC : db2sysc
0
INSTANCE: db2inste NODE : 000 DB : SAMPLE
APPHDL : 0-7
EDUID : 2829 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, bsu security, sqlexLogPluginMessage, probe:20
DATA #1 : String with size, 67 bytes
Password validation for user db2inste failed with rc =
-2146500507
2011-02-24-10.28.36.923121+330 I14793A416 LEVEL: Severe
PID : 602178 TID : 2829 PROC : db2sysc
0
INSTANCE: db2inste NODE : 000 DB : SAMPLE
APPHDL : 0-9
EDUID : 2829 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, bsu security, sqlexLogPluginMessage, probe:20
DATA #1 : String with size, 45 bytes
change password failed with rc = -2146500507
db2diag.log
-----------
2011-02-24-10.28.36.921307+330 I10211A259 LEVEL: Error
PID : 692350 TID : 1
FUNCTION: DB2 UDB, oper system services, sqlochpw, probe:34
DATA #1 : String, 22 bytes
Change Password Failed
DATA #2 : String, 19 bytes
password mismatch. |
