Why Are There Old Log Files That Are Not Removed For ISS? (Doc ID 2231248.1)

Last updated on FEBRUARY 08, 2017

Applies to:

Oracle Communications Indexing and Search Service - Version 1.0.5 and later
Information in this document applies to any platform.

Goal

We are still seeing old index service logs from February 2016 for ISS under the log directory in the current month of January 2017:

/gcs/app/mail/jiss/logs$ ls -alrt iss-indexsvc.log.*
  .
  .
-rw-r----- 1 imsadmin ims 200000123 Feb 17 2016 iss-indexsvc.log.103
-rw-r----- 1 imsadmin ims 200004511 Feb 17 2016 iss-indexsvc.log.102
-rw-r----- 1 imsadmin ims 200000087 Feb 17 2016 iss-indexsvc.log.101
-rw-r----- 1 imsadmin ims 200000326 Feb 17 2016 iss-indexsvc.log.100
-rw-r----- 1 imsadmin ims 0 Jan 9 05:10 iss-indexsvc.log.0.lck
-rw-r----- 1 imsadmin ims 200009274 Jan 17 12:39 iss-indexsvc.log.99
-rw-r----- 1 imsadmin ims 200000134 Jan 17 14:39 iss-indexsvc.log.98
-rw-r----- 1 imsadmin ims 200000191 Jan 17 16:39 iss-indexsvc.log.97
  .
  .

1) What controls the sequence number space used for that renaming? (i.e. *.log.nn)

2) Is it just the numbers of the existing log files? or is the number stored somewhere else?

3) Why do we still have 100 files (numbers .100 to .199) from more than a year ago?
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms