X

Best Practices from Oracle Development's A‑Team

Schedule Instances and Analytics Archive Using Cron Job in PCS

Derek Kam
Consulting Solutions Architect

In PCS, you can archive instance data on demand or schedule the archive to run automatically by using PCS administration UI to select the date and time or alternatively you can use CRON entry. You can also schedule to archive the analytics data to the cloud storage and BICS in the same way.  However, there is a difference when you set the CRON tab for instances archive and analytics archive.

For Instances archive, the CRON expression frequency must be greater than or equal to the allowed 1 day threshold. In another word, it would mean that you cannot set the archive to run for every minute or every hour.  You can set the archive job to run at a specific time daily, for example, you can set it to run at 12pm every day, the CRON expression will be “0 0 12 * * ?”

PCS Archive 1

In the case of analytics archive, the CRON expression frequency must be greater than or equal to the allowed 6 hours’ threshold. That would mean that you cannot set the archive to run for every minute or every hour. However, if you want to set the analytics archive to run a few times a day, you can use the CRON hours field in the CRON expression to set the time you want to run the archive job. For example, if you want to run at 10am, 4pm, 10pm daily (with 6 hours gap in between), the CRON expression will be “0 0 10,16,22 * * ?”.

PCS Archive 2

If the analytics data synchronize to BICS job failed, PCS will retry 3 times internally with an interval of 90 secs. When the internal retries failed, you will receive an email notification with the reason of the failure, the email will contain a link for you to download the analytics archive data, so that you can import the archive data to BICS manually.

PCS Archive 3

You have 2 options to manually import the archive data:

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha

Recent Content