New Feature:Oracle SOA 12c Auto-Purge

Hello All,

This is next step to previous blog Purging Strategy.

In this blog we will see how Oracle SOA 12C auto-purging will save our time and disk space growth on parallel processing.

How to manage the growth of large numbers of flow instances, adapter reports, and fault alerts in the database with the purge scripts in Oracle Enterprise Manager Fusion Middleware Control or SQL*Plus, table partitioning for enabling schema tables to be range-partitioned on time intervals, and the truncate script for removing all records from runtime tables without dropping the tables.

Auto-Purging in Oracle SOA 12C:

Use the Auto Purge page in Oracle Enterprise Manager Fusion Middleware Control to schedule and execute jobs that automatically remove older flow instances, adapter reports, and fault alerts data from the database.

Recommendation from Oracle:

• you enable automatic purging on the Auto Purge page to optimize runtime environment performance. The status of automatic purging is displayed in the Key Configuration section of the Dashboard page at the SOA Infrastructure and individual partition levels. Automatic purging is automatically enabled for new 12c installations, but not for upgraded environments.
• Ensure that you back up important data before enabling or changing purge configurations.
• The Auto Purge page is not available if you are using the Java database included with the SOA Developer Install option. Use the truncate_soa_javadb.sql script to purge the database.

How to enable auto-purging:

1. Auto Purge Settings Page.

      2.Change Settings (Default=Enabled)

Configuration used on above image:

• Auto Purge Job:
• Run delete_instances_auto_job1 on a schedule appropriate for weekdays (Monday through Friday at midnight). This job is automatically enabled.
• Run delete_instances_auto_job2 on a weekend schedule (Saturday and Sunday) that may be more aggressive. This job is not automatically enabled.
• Enabled:
• Select to enable automatic database purging with the database purge job selected from the Auto Purge Job list.
• The purge interval begins when it is enabled. For example, If you specify seven days in the Retain Data field, data is retained from the day you re-enabled this checkbox. Newer data is retained for seven days from when it was created.
• Calendaring Expression icon:
• Click to view examples of job scheduling syntax. Copy and paste the syntax appropriate to your environment into the Job Schedule field and modify as necessary. Click More Info to access documentation about how to configure job frequency by setting the repeat_interval attribute.
• Job Schedule:
• Specify a job execution schedule to purge instances. The default schedule is to perform a daily purge at midnight. This is a required field. To specify the schedule, use valid calendaring expressions. Click the information icon or the Calendaring Expression icon to view examples of commonly used expressions. The scheduling syntax is not case sensitive.
• Purge Type:
• Single: Single, loop purged script that performs a batched purge.
• Parallel: Functionality is the same as the single, looped purge script. However, this option enables the dbms_scheduler package to spawn multiple purge jobs, with each job working on subset data.
• Retain Data:
• Specify the time interval in days for which to retain data. Data within this interval is not purged when the job runs. The default value is seven days.
• Maximum Flows to Purge:
• Select the maximum number of instance flows to purge in a single job run.
• Batch Size:
• Select the maximum number of business flows to delete at a time. The default value is 20000.
• Degree of Parallel:
• Select the number of job executions to run in parallel. The default value is 4.

• To view and configure advanced configuration properties in the System MBean Browser, click More Auto Purge Configuration Properties.
• Click PurgeJobDetails.
• The two predefined database purge jobs are displayed.
• delete_instances_auto_job1
• delete_instances_auto_job2
• Expand a job to display all properties for single and parallel purges. When either the single or parallel purge type is executed, the appropriate property values for the selected type are executed.

• View or change values, then click Apply.

Scheduler Calendaring Syntax:

Specify an execution schedule or a repeat interval schedule as shown in the examples below.

• Run every Day at Midnight
FREQ=DAILY; BYHOUR=00;
• Run every weekday at midnight
FREQ=DAILY; BYDAY=MON,TUE,WED,THU,FRI; BYHOUR=00;
• Run every weekend at midnight and 05:00AM
FREQ=DAILY; BYDAY=SAT,SUN; BYHOUR=00,05;
• Run every weekday 30 minutes past midnight
FREQ=DAILY; BYDAY=MON,TUE,WED,THU,FRI; BYHOUR=00; BYMINUTE=30;
• Run every weekend 30 minutes past midnight and 5AM
FREQ=DAILY; BYDAY=SAT,SUN; BYHOUR=00,05; BYMINUTE=30;
• Run every friday at midnight
FREQ=DAILY; BYDAY=FRI; BYHOUR=0;
• Run every other friday at midnight
FREQ=DAILY; BYDAY=FRI; BYHOUR=0;

Ref:
https://docs.oracle.com/cloud/latest/soa121300/SOAAG/GUID-DBCFFB8F-3B67-4000-9F48-404D16D503DD.htm#SOAAG98043