LAE0181I REQUIRED LOG RANGE NOT FOUND 

Document ID : KB000118021
Last Modified Date : 29/10/2018
Show Technical Document Details
Issue:
Log Analyzer job returning the following errors:

LAE0282I SORT package detected: DFSORT 
LAE0297I Beginning Log Extract processing. 
LAE0036I Log Extract processing completed normally. 
LAE0298I Beginning Log Reporting processing. 
LAE0288I Beginning Image Copy merge processing. 
LAE0181I REQUIRED LOG RANGE NOT FOUND 
LAE0181I PFR0216E - UNABLE TO FIND CI RBA X'00000000032F5A043000' 
LAE0181I 'MV00.ARCHLOG1.D17358.T1433468.A0030479' 
LAE0181I STARTING LOG CI RBA X'00000000034AFA357000' 
LAE0290I Image Copy merge processing completed with errors. 

LAE0008E SORT terminating. Return/Abend Code: 00 
 
Environment:
CA Log Analyzer R19.0 DB2 V11 NFM
Cause:
As the general rule, it is recommended to have SHRLEVEL = U in the PARMLIB (PLA), unless there is a reason to skip the very last copy. It can occasionally happen, that the last copy is so recent, that it is inconsistent with current log contents and therefore need to be skipped, but it is a rather rare situation. 
Resolution:
After changing the default setting SHRLEVEL = S in the PARMLIB (PLA), the REDO jobs at the IMAGECOPY level have passed successfully.
For the future, it is recommended taking image copies of tablespaces, which are needed to report on with IMAGCOPY level more frequently. For instance, if log files are kept for 14 days, a copy must be taken once a week at least.