Example of the Automatic Deletion and Backup of Stage Table Data
When you perform the Delete Stage Table Data task, it runs the Delete HCM Data Loader Stage Table Data process. This process maintains the HCM Data Loader stage tables automatically.
This example shows how automatic maintenance of the stage tables works in conjunction with a user request to delete stage table data.
Maintaining the Stage Tables Automatically
The user performs the Delete Stage Table Data task on 9 May 2018 to purge any data sets:
-
That weren't updated in the last 5 days
-
Whose Import and Load statuses are both Success
Configuration parameters have their default values, as follows:
Configuration Parameter |
Value |
---|---|
Days to Retain Data Sets Before Archiving |
5 |
Days to Retain Data Sets Before Deleting |
30 |
The following table shows the status of recent import and load processes when the user performs Delete Stage Table Data.
Data Set |
Imported Status |
Loaded Status |
Last Updated |
---|---|---|---|
1 |
Success |
Success |
9 May 2018 |
2 |
Success |
Error |
7 May 2018 |
3 |
Success |
Success |
1 May 2018 |
4 |
Success |
Error |
28 April 2018 |
5 |
Success |
Success |
8 April 2018 |
6 |
Success |
Error |
8 April 2018 |
These data sets are either purged or backed up as follows:
-
Data sets 3 and 5 are purged by the user's process, based on the user's parameters.
-
Data set 6 is purged automatically because it hasn't been updated in the last 30 days.
-
Data set 4 is backed up automatically. The backup occurs because the number of data lines in the stage tables still exceeds the configured Maximum Data Lines Before Archiving value.