File storage in the cloud might be constrained so it’s important to proactively manage limited file storage services by purging old instances and payloads.
In order to keep your database and storage resources from filling up, periodically purge artifacts from previous transfers. By default, Oracle Managed File Transfer Cloud Service checks daily at 8:00 AM for files that have been around longer than seven days and purges any that it finds. You can change these default values to suit your needs. How often you purge depends on your usage as does the length of time you retain the artifacts.
The tasks in the following topics describe how to change the retention value and the schedule.
If you want to change the length of time you retain transfer artifacts such as old instances and payloads, edit the purgeInstanceData.py
file located on each MFT managed server.
By default, Oracle Managed File Transfer Cloud Service checks daily at 8:00 AM for files that have been around longer than the retention value and purges any that it finds. You can change the schedule to suit your needs. How often you purge depends on your usage.
Note:
Follow these instructions if you are using Oracle Managed File Transfer Cloud Service versions 12.1.3 or 12.2.1. If using version 12.2.1.2, you can perform this task from the Administration page of the Oracle Managed File Transfer Console.purge_schedule.py
script, stopping and deleting the original scheduler job and then running the startSchedulePurge.sh
script to start the new schedule.