mysterious disappearance of logs

[kirkmiller]

I have the following 2 full backups.

Using the parameters below, I hoped to avoid having to manually delete logs with db2adutl.

As you can see, logs necessary to rollforward the DB using the older backup (0302) are gone.

I cannot determine how they got deleted, certainly the parameters do not call for them to be deleted for 60 days.

  1 Time: 20160309210001  Oldest log: S0008274.LOG  DB Partition Number: 0    Sessions: 2 

    2 Time: 20160302210001  Oldest log: S0008106.LOG  DB Partition Number: 0    Sessions: 2 

   Earliest Log file: S0008163.LOG, Chain Num: 0, Log stream: 0, Taken at: 2016-03-05-05.29.26

AUTO_DEL_REC_OBJ = ON

REC_HIS_RETENTN = 60

   (NUM_DB_BACKUPS) = 12

   (LOGARCHMETH1) = TSM:SAP_MC02

I don't see anything in db2diag.log or NFY that tells me what happened.

---db2level----

DB21085I  This instance or install (instance name, where applicable: "db2SID")

uses "64" bits and DB2 code release "SQL10051" with level identifier

"0602010E".

Informational tokens are "DB2 v10.5.0.1", "s130816", "IP23519", and Fix Pack

"1".

Product is installed at "/db2/db2SID/v10.5".

[maria_shen]

Hello

I am not very clear with how it is concluded the log files inside backup image are missing.
Nevertheless, you can test whether you can retrieve the log files from the backup images using restore command.
db2 restore db <sid> logs from <backup destination> taken at <backup timestamp> logtarget <dir>.

If the TSM is used for backup, you may try:
db2 restore db <sid> logs use tsm open 2 sessions taken at <> logtarget <dir>

The above could be a way to check from database level. You can also check the IBM info center for the details of the command syntax.

Kind regards
Maria

[kirkmiller]

Thanks for the reply. Let me restate:

Note in List 1 there are two backups, yet 'db2adutl query logs' shows the

oldest log is about 60 logs past the oldest backup. Backup #2 cannot be

restored with rollforward because the logs are gone.                  

The next day I reran the query. Additional logs had disappeared and the

oldest log is 8195. (list 2)                                         

I need to determine how logs 8163-8194 were deleted. It should not be 

possible.    

I suspect that this is somehow related to the fact that when an online backup is done,

logs must be retrieved from TSM in order to be included in the backup.  If the retrieval destination is log_dir, 

there are too many logs in the  log path and the system somehow decides to delete them?

-----list 1 ---                                                       

    1 Time: 20160309210001  Oldest log: S0008274.LOG  DB Partition  

Number: 0    Sessions: 2                                              

    2 Time: 20160302210001  Oldest log: S0008106.LOG  DB Partition    

Number: 0    Sessions: 2      

(output of db2adutl query logs, only earliest log shown)                                      

   Log file: S0008163.LOG, Chain Num: 0, Log stream: 0, Taken at: 2016-

03-05-05.29.26                                                        

-------List 2 ----------                                              

1> db2adutl query full                                 

Retrieving FULL DATABASE BACKUP information.                          

    1 Time: 20160309210001  Oldest log: S0008274.LOG  DB Partition    

Number: 0    Sessions: 2                                              

    2 Time: 20160302210001  Oldest log: S0008106.LOG  DB Partition    

Number: 0    Sessions: 2                                              

db2adutl query logs                                 

Retrieving LOG ARCHIVE information.                                   

   Log file: S0008195.LOG, Chain Num: 0, Log stream: 0, Taken at: 2016-

03-06-13.29.26                                                        

   Log file: S0008196.LOG, Chain Num: 0, Log stream: 0, Taken at: 2016-

03-06-14.14.27                                                        

   Log file: S0008197.LOG, Chain Num: 0, Log stream: 0, Taken at: 2016-

03-06-15.29.28  

(truncated)

p.s.  TSM Server Version 6, Release 3, Level 4.300 

Number of primary log files                (LOGPRIMARY) = 60

Number of secondary log files               (LOGSECOND) = 0

Changed path to log files                  (NEWLOGPATH) =

Path to log files                                       = /db2/SID/log_dir/NODE0000/LOGSTREAM0000/

Overflow log path                     (OVERFLOWLOGPATH) =

Mirror log path                         (MIRRORLOGPATH) =

First active log file                                   = S0008471.LOG

Block log on disk full                (BLK_LOG_DSK_FUL) = YES

Block non logged operations            (BLOCKNONLOGGED) = NO

Percent max primary log space by transaction  (MAX_LOG) = 80

Num. of active log files for 1 active UOW(NUM_LOG_SPAN) = 80

First log archive method                 (LOGARCHMETH1) = TSM:SAP_MC02

Archive compression for logarchmeth1    (LOGARCHCOMPR1) = ON

[hugo_amo]

Hi Kirk,

Are you using infinite logging? logsecond = -1 ?

Regards,

Hugo