This activity is used to archive event log records that are no longer needed for operational activities. The archived records will be moved to a non-transactional table and can be kept in the application for reporting and investigation purposes (e.g. regulatory reasons), until they are purged. Purging refers to the process of permanently deleting data records from the database. As the event log can quickly grow in size, it is important to set up a task to archive data continuously, to avoid potential performance issues. When archiving it is possible to define 4 parameters as the selection criteria for what to archive:
This activity can be performed as a scheduled task or executed online as a one-time action.
It is possible to schedule archiving to run on a Daily, Weekly or Monthly basis, a specific date, an interval (e.g. every 12 hours) or to use a Custom Expression (e.g. DBMS_SCHEDULER syntax like "FREQ=YEARLY;BYMONTH=JAN,JUL;BYMONTHDAY=21", which means every year on January 21 and July 21.)
Let's assume that it's 2023-08-01 (August 1, 2023) and there is a schedule set up to archive Entity SrvRequest (Request-related event log records) with a From Offset of -100 and a To Offset of -10. Event log records related to Requests, created between 2023-04-23 (April 23, 2023) and 2023-07-22 (July 22, 2023) would be archived. When this scheduled job would run the next day, event log records related to Requests, created between 2023-04-24 (April 24, 2023) and 2023-07-23 (July 23, 2023) would be archived, and so on.
It is important to note that the archiving does not take the state or status of the related entity into account, meaning that it is technically possible to archive events that belong to an active record. It is possible to restore archived records.