Documentation Comments
Use this form to comment on this topic. You can also provide any general observations about the Online Documentation, or request that additional information be added in a future release.
Reality V15.2 Online Documentation (MoTW) Revision 3
Naming Convention for Clean Logs (Resilience) (m646703+cleanlogs.htm)
All clean logs must be created with meaningful names to reduce the chance of errors occurring when recovering data.
Note Clean log names are case sensitive. For example, CLOG must be entered as upper-case.
tlmenu defaults to the following naming convention for clean log files:
CLOGdate-nn
where:
dateis the current date in the format yymmdd.
nnis a sequence number, to allow more than one clean log per day. (If there are more than 99 clean logs for any one day then the logs will start to use a three-digit sequence number, nnn, up to 999.)
For example, CLOG190511-01 is the first clean log used on 11 May 2019.
CLOG is the default clean log prefix. Refer to the topic Configuration Options.
This standard format for clean log names prevents any ambiguity in identifying a clean log and enables the recovery operation to be automated easily. The reverse date format enables clean log operations logged in the database's event logs to be sorted in date order.
Note tlmenu does not support the use of duplicate clean log names.