Sometimes you will find below errors in db2diag.log related to
log file retrieving
while an online backup (with default action to include logs) is
in progress.
At this time, a message stating backup was successful will also
be returned to your prompt :
yyyy-mm-dd-20.12.10.452784+120 xxxxxxx LEVEL: Error
PID : 26738736 TID : 16194 PROC : db2sysc
0
INSTANCE: <instance name> NODE : 000
EDUID : 16194 EDUNAME: db2logmgr
(database_name) 0
FUNCTION: DB2 UDB, data protection services,
sqlpgRetrieveLogVendor, probe:2516
DATA #1 : String, 107 bytes
The actual log file size did not match the expected file size,
retrying retrieve. Actual / Expected / File:
DATA #2 : signed integer, 8 bytes
9043968
DATA #3 : signed integer, 8 bytes
32776192
DATA #4 : String, 53 bytes
yyyy-mm-dd-20.12.10.452784+120 xxxxxxx LEVEL: Error
PID : 26738736 TID : 16194 PROC : db2sysc
0
INSTANCE: <instance name> NODE : 000
EDUID : 16194 EDUNAME: db2logmgr (datbase_name)
0
FUNCTION: DB2 UDB, data protection services,
sqlpgRetrieveLogVendor, probe:2541
DATA #1 : String, 37 bytes
The bad log file was saved in. File:
DATA #2 : String, 53 bytes
/db2/cmdb2ibb/NODE0000/SQL00001/SQLOGDIR/S0005801.SA1
Most times, it is also accompanied by the following error
messages :
yyyy-mm-dd-20.12.10.452784+120 xxxxxxx LEVEL: Error(OS)
PID : 45285486 TID : 4628 PROC : db2sysc
0
INSTANCE: <instance_name> NODE : 000
EDUID : xxxx EDUNAME: db2lfr (database_name) 0
FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80
MESSAGE : ZRC=0x870F0016=-2029060074=SQLO_SHAR "File sharing
violation." DIA8519C A file sharing violation has occurred,
filename was "".
CALLED : OS, -, open
OSERR : ETXTBSY (26) "Text file busy"
DATA #1 : Codepath, 8 bytes
4:11:12:13:22:36:37:63
DATA #2 : File name, 60 bytes
/udb/udb/data/DB/active/log/NODE0000/S0877999.LOG
DATA #3 : SQO Open File Options, PD_TYPE_SQO_FILE_OPEN_OPTIONS,
4 bytes
SQLO_REVISE, SQLO_READWRITE, SQLO_EXCLUSIVE, SQLO_WRITETHRU
DATA #4 : Hex integer, 4 bytes
0x000001A0
DATA #5 : signed integer, 4 bytes
100
DATA #6 : signed integer, 4 bytes
0
DATA #7 : String, 105 bytes
Search for ossError*Analysis probe point after this log entry
for further
self-diagnosis of this problem.
After the backup, these log files which received the "file
sharing violation" errors,
may be left in the active log path for indefinte time until a
database recycle is done or
they are deleted manually.
Analysis :
This issue occurs due to multipe retrieval requests. As you can
see below, the first
time a log file retrival is completed successfully, but when DB2
tries to retrieve the logs
for the second time it fails :
yyyy-mm-dd-20.12.03.517684+120 XXXXXX LEVEL: Warning
PID : 26738736 TID : 16194 PROC : db2sysc
0
INSTANCE: <instance name> NODE : 000
EDUID : 16194 EDUNAME: db2logmgr
(database_name) 0
FUNCTION: DB2 UDB, data protection services,
sqlpgRetrieveLogFile, probe:4130
MESSAGE : Started retrieve for log file S0005801.LOG.
yyyy-mm-dd-20.12.06.084698+120 XXXXXX LEVEL: Warning
PID : 26738736 TID : 16194 PROC : db2sysc
0
INSTANCE: <instance name> NODE : 000
EDUID : 16194 EDUNAME: db2logmgr (database
name) 0
FUNCTION: DB2 UDB, data protection services,
sqlpgRetrieveLogFile, probe:4148
MESSAGE : Completed retrieve for log file S0005801.LOG on chain
0 to
/db2/cmdb2ibb/NODE0000/SQL00001/SQLOGDIR/.
Second time retrival of logs results in failure :
yyyy-mm-dd-20.12.09.581098+120 I340297A369 LEVEL: Warning
PID : 26738736 TID : 16194 PROC : db2sysc
0
INSTANCE: <instance name> NODE : 000
EDUID : 16194 EDUNAME: db2logmgr (database
name) 0
FUNCTION: DB2 UDB, data protection
services,
sqlpgRetrieveLogFile, probe:4130
yyyy-mm-dd-20.12.10.452784+120 E340667A617 LEVEL: Error
PID : 26738736 TID : 16194 PROC : db2sysc
0
INSTANCE: <instance name> NODE : 000
EDUID : 16194 EDUNAME: db2logmgr (database
name) 0
FUNCTION: DB2 UDB, data protection services,
sqlpgRetrieveLogVendor, probe:2516
DATA #1 : String, 107 bytes
The actual log file size did not match the expected file size,
retrying retrieve. Actual / Expected / File:
DATA #2 : signed integer, 8 bytes
9043968
DATA #3 : signed integer, 8 bytes
32776192
DATA #4 : String, 53 bytes
yyyy-mm-dd-20.12.10.454078+120 E341285A461 LEVEL: Error
PID : 26738736 TID : 16194 PROC : db2sysc
0
INSTANCE: <instance name> NODE : 000
EDUID : 16194 EDUNAME: db2logmgr (database
name) 0
FUNCTION: DB2 UDB, data protection services,
sqlpgRetrieveLogVendor, probe:2541
DATA #1 : String, 37 bytes
The bad log file was saved in. File:
DATA #2 : String, 53 bytes
/db2/cmdb2ibb/NODE0000/SQL00001/SQLOGDIR/S0005801.SA1
The problem is the multiple requests for logs retrieval that
have
already been included in the backup image. Same is the cause
behind the
file sharing violation which then leads to already archived logs
being
left behind in the active log path as they are not deleted due
to the violation.
The fix will remove these extra retrieve requests. |
