Message: data protection sqlpghck

[Stefan S.]

Hello,
yesterday we have upgraded the DB2 v8.1 to FP-level 4. Now we got some
messages in the db2diag.log (see snippet at the end). On our
filesystem, where the log-files are located we have sufficent space
available (>50GB). We have already reduced the LOGFILSIZ Parameter,
this hadn't any affect.
Did anyone have any idea?
Thanks

Stefan

----------------------------------------------------------------
2003-12-11-07.36.03.944225 Instance:db2inst1 Node:000
PID:4078(db2agent (BTLDB)) TID:16384
Appid:*LOCAL.db2inst1.008BA1063603
data protection sqlpgint Probe:1870

Frequent database deactivation is detected with large log file size.
Consider reduce LOGFILSIZ configuration or use ACTIVATE DATABASE
command
to
start up database.

2003-12-11-07.41.39.673391 Instance:db2inst1 Node:000
PID:4283(db2loggr (BTLDB)) TID:16384 Appid:none
data protection sqlpghck Probe:1390

ExtNum 12262, state 401, baselsn 0000000BCDF90000 nextlsn
0000000BCE1C4166

2003-12-11-08.55.04.432700 Instance:db2inst1 Node:000
PID:8109(db2loggr (BTLDB)) TID:16384 Appid:none
data protection sqlpghck Probe:1390

ExtNum 12263, state 401, baselsn 0000000BCE378000 nextlsn
0000000BCE378205
--------------------------

[PM \(pm3iinc-nospam\)]

I would have tried ACTIVATE DATABASE avenue. (see also Deactivate db...)
Basically, db2 is telling you that it thinks it has to incur the startup
cost too often ...
allocating logs, bufferpools, other-memory, ressources, ...

Unless you Activate a DB, db2 will deallocate some resources if it detects
no user is connected to a db. It will need to reallocate those resources
when
another user connects, ...

PM

"Stefan S." <st**************@cimt-ag.de> a écrit dans le message de
news:de**************************@posting.google.c om...

Hello,
yesterday we have upgraded the DB2 v8.1 to FP-level 4. Now we got some
messages in the db2diag.log (see snippet at the end). On our
filesystem, where the log-files are located we have sufficent space
available (>50GB). We have already reduced the LOGFILSIZ Parameter,
this hadn't any affect.
Did anyone have any idea?
Thanks

Stefan

----------------------------------------------------------------
2003-12-11-07.36.03.944225 Instance:db2inst1 Node:000
PID:4078(db2agent (BTLDB)) TID:16384
Appid:*LOCAL.db2inst1.008BA1063603
data protection sqlpgint Probe:1870

Frequent database deactivation is detected with large log file size.
Consider reduce LOGFILSIZ configuration or use ACTIVATE DATABASE
command
to
start up database.

2003-12-11-07.41.39.673391 Instance:db2inst1 Node:000
PID:4283(db2loggr (BTLDB)) TID:16384 Appid:none
data protection sqlpghck Probe:1390

ExtNum 12262, state 401, baselsn 0000000BCDF90000 nextlsn
0000000BCE1C4166

2003-12-11-08.55.04.432700 Instance:db2inst1 Node:000
PID:8109(db2loggr (BTLDB)) TID:16384 Appid:none
data protection sqlpghck Probe:1390

ExtNum 12263, state 401, baselsn 0000000BCE378000 nextlsn
0000000BCE378205
--------------------------