The following messages may be reported in the db2diag.log file,
while a logfile is archived in compressed format:
2013-10-17-13.06.51.397324+000 I2878892E600 LEVEL:
Error
PID : 13820 TID : 140414476609280 PROC :
db2sysc 0
INSTANCE: xxxxxx NODE : 000 DB : zzz
HOSTNAME: yyyyyy
EDUID : 266 EDUNAME: db2logmgr (zzz) 0
FUNCTION: DB2 UDB, data protection services,
sqlpgCompressArchiveLog, probe:7035
MESSAGE : Unexpected error from compression library
DATA #1 : signed integer, 4 bytes
101
DATA #2 : String, 12 bytes
source bytes
DATA #3 : Dumped object of size 131072 bytes at offset 0, 39
bytes
/db2/zzz/db2dump/13820.266.000.dump.bin
2013-10-17-13.06.51.444584+000 I2879493E487 LEVEL:
Error
PID : 13820 TID : 140414476609280 PROC :
db2sysc 0
INSTANCE: xxxxxx NODE : 000 DB : zzz
HOSTNAME: yyyyyy
EDUID : 266 EDUNAME: db2logmgr (zzz) 0
FUNCTION: DB2 UDB, data protection services,
sqlpgCompressArchiveLog, probe:7035
MESSAGE :
ZRC=0x8010047E=-2146433922=SQLP_LOGARCHCOMPR_LIBRARY_FAILURE
"Log archive compression library failure."
2013-10-17-13.06.51.445901+000 E2879981E517 LEVEL:
Warning
PID : 13820 TID : 140414476609280 PROC :
db2sysc 0
INSTANCE: xxxxxx NODE : 000 DB : zzz
HOSTNAME: yyyyyy
EDUID : 266 EDUNAME: db2logmgr (zzz) 0
FUNCTION: DB2 UDB, data protection services,
sqlpgArchiveLogDisk, probe:2534
MESSAGE : ADM1501W Log file compression failed on log file
"S0008625.LOG"
during archiving for "LOGARCHMETH1" for database "zzz"
on member "0".
2013-10-17-13.06.51.447845+000 I2880499E486 LEVEL:
Error
PID : 13820 TID : 140414476609280 PROC :
db2sysc 0
INSTANCE: xxxxxx NODE : 000 DB : zzz
HOSTNAME: yyyyyy
EDUID : 266 EDUNAME: db2logmgr (zzz) 0
FUNCTION: DB2 UDB, data protection services,
sqlpgArchiveLogDisk, probe:2534
DATA #1 : <preformatted>
Archive log 8625 failed due to compression error, We will try to
archive it again without compression |
