When I run a backup script from the Task Center i get these messages:

2006-02-15-21.30.08.515000+060 E21985H390 LEVEL: Error
PID : 2408 TID : 3416 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : XDKE00
APPHDL : 0-1418 APPID: *LOCAL.DB2.060215203021
FUNCTION: DB2 UDB, base sys utilities, sqleDatabaseQuiesce, probe:1
MESSAGE : ADM7506W Database quiesce has been requested.

2006-02-15-21.30.08.515000+060 E22377H406 LEVEL: Error
PID : 2408 TID : 3416 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : XDKE00
APPHDL : 0-1418 APPID: *LOCAL.DB2.060215203021
FUNCTION: DB2 UDB, base sys utilities, sqleDatabaseQuiesce, probe:2
MESSAGE : ADM7507W Database quiesce request has completed successfully.

2006-02-15-21.30.09.265000+060 I22785H391 LEVEL: Warning
PID : 2408 TID : 3416 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : XDKE00
APPHDL : 0-1071 APPID: *LOCAL.DB2.060215203022
FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl, probe:2028
MESSAGE : Starting an offline incremental db backup.

2006-02-15-21.30.36.437000+060 I23178H353 LEVEL: Warning
PID : 2408 TID : 3416 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : XDKE00
APPHDL : 0-1071 APPID: *LOCAL.DB2.060215203022
FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:130
MESSAGE : Backup Complete.

But I do not consider a database quiesce to be an error, nor a start and a
succesful completion of a database backup to deserve a warning. Can anyone
say anything about why db2 write these messages to the db2diag.log?

The diaglevel is set to 3.

Regards
Odd B Andersen
ErgoGroup, Oslo, Norway

Odd Bjørn Andersen wrote:
> When I run a backup script from the Task Center i get these messages:
>
> 2006-02-15-21.30.08.515000+060 E21985H390 LEVEL: Error
> PID : 2408 TID : 3416 PROC : db2syscs.exe
> INSTANCE: DB2 NODE : 000 DB : XDKE00
> APPHDL : 0-1418 APPID: *LOCAL.DB2.060215203021
> FUNCTION: DB2 UDB, base sys utilities, sqleDatabaseQuiesce, probe:1
> MESSAGE : ADM7506W Database quiesce has been requested.
>
> 2006-02-15-21.30.08.515000+060 E22377H406 LEVEL: Error
> PID : 2408 TID : 3416 PROC : db2syscs.exe
> INSTANCE: DB2 NODE : 000 DB : XDKE00
> APPHDL : 0-1418 APPID: *LOCAL.DB2.060215203021
> FUNCTION: DB2 UDB, base sys utilities, sqleDatabaseQuiesce, probe:2
> MESSAGE : ADM7507W Database quiesce request has completed successfully.
>
> 2006-02-15-21.30.09.265000+060 I22785H391 LEVEL: Warning
> PID : 2408 TID : 3416 PROC : db2syscs.exe
> INSTANCE: DB2 NODE : 000 DB : XDKE00
> APPHDL : 0-1071 APPID: *LOCAL.DB2.060215203022
> FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl, probe:2028
> MESSAGE : Starting an offline incremental db backup.
>
> 2006-02-15-21.30.36.437000+060 I23178H353 LEVEL: Warning
> PID : 2408 TID : 3416 PROC : db2syscs.exe
> INSTANCE: DB2 NODE : 000 DB : XDKE00
> APPHDL : 0-1071 APPID: *LOCAL.DB2.060215203022
> FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:130
> MESSAGE : Backup Complete.
>
> But I do not consider a database quiesce to be an error, nor a start and a
> succesful completion of a database backup to deserve a warning. Can anyone
> say anything about why db2 write these messages to the db2diag.log?
>
> The diaglevel is set to 3.
>
Which fixpack level are you on?
When the db2diag.log was reorganized to classify the messages, it is
known that some classification were unfortunate.
The messages should be flaggs as "Warning" or "Info"

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

Serge Rielau wrote:
> Odd Bjørn Andersen wrote:
>
>> When I run a backup script from the Task Center i get these messages:
>>
>> 2006-02-15-21.30.08.515000+060 E21985H390 LEVEL: Error
>> PID : 2408 TID : 3416 PROC : db2syscs.exe
>> INSTANCE: DB2 NODE : 000 DB : XDKE00
>> APPHDL : 0-1418 APPID: *LOCAL.DB2.060215203021
>> FUNCTION: DB2 UDB, base sys utilities, sqleDatabaseQuiesce, probe:1
>> MESSAGE : ADM7506W Database quiesce has been requested.
>>
>> 2006-02-15-21.30.08.515000+060 E22377H406 LEVEL: Error
>> PID : 2408 TID : 3416 PROC : db2syscs.exe
>> INSTANCE: DB2 NODE : 000 DB : XDKE00
>> APPHDL : 0-1418 APPID: *LOCAL.DB2.060215203021
>> FUNCTION: DB2 UDB, base sys utilities, sqleDatabaseQuiesce, probe:2
>> MESSAGE : ADM7507W Database quiesce request has completed successfully.
>>
>> 2006-02-15-21.30.09.265000+060 I22785H391 LEVEL: Warning
>> PID : 2408 TID : 3416 PROC : db2syscs.exe
>> INSTANCE: DB2 NODE : 000 DB : XDKE00
>> APPHDL : 0-1071 APPID: *LOCAL.DB2.060215203022
>> FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl, probe:2028
>> MESSAGE : Starting an offline incremental db backup.
>>
>> 2006-02-15-21.30.36.437000+060 I23178H353 LEVEL: Warning
>> PID : 2408 TID : 3416 PROC : db2syscs.exe
>> INSTANCE: DB2 NODE : 000 DB : XDKE00
>> APPHDL : 0-1071 APPID: *LOCAL.DB2.060215203022
>> FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:130
>> MESSAGE : Backup Complete.
>>
>> But I do not consider a database quiesce to be an error, nor a start
>> and a succesful completion of a database backup to deserve a warning.
>> Can anyone say anything about why db2 write these messages to the
>> db2diag.log?
>>
>> The diaglevel is set to 3.
>>
> Which fixpack level are you on?
> When the db2diag.log was reorganized to classify the messages, it is
> known that some classification were unfortunate.
> The messages should be flaggs as "Warning" or "Info"
I passed it on to development to be fixed in Viper.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab