Purging is very important activity in Oracle Apps. As a dba one needs to purge the obsolete data so that only usable data is there in system,backups and restore are faster,space is recovered and finally it makes the system faster as well. Following are some of the concurrent requests which should be scheduled for purging-
Purge Concurrent request and/or manager data--Here we specify mode=x so that it purges all the concurrent request log files,concurrent request output files and manager data which are more than 'x' days old i.e. we just keep 'x' days data.
Purge Obsolete Workflow Runtime data-Here we specify type of workflow -'Temperorary/Permanent, "Age"-which determines how old notification one wants to keep. We can also specify the 'Item Type' and 'Item key' to restrict it to purge just a particular type of workflow notifications.Note that only the closed notifications are purged.
Purge Signon Audit Data-Here we need to specify the timestamp before which the Audit data will be deleted
These are just some of the requests.There are many more!
Purge Concurrent request and/or manager data--Here we specify mode=x so that it purges all the concurrent request log files,concurrent request output files and manager data which are more than 'x' days old i.e. we just keep 'x' days data.
Purge Obsolete Workflow Runtime data-Here we specify type of workflow -'Temperorary/Permanent, "Age"-which determines how old notification one wants to keep. We can also specify the 'Item Type' and 'Item key' to restrict it to purge just a particular type of workflow notifications.Note that only the closed notifications are purged.
Purge Signon Audit Data-Here we need to specify the timestamp before which the Audit data will be deleted
No comments:
Post a Comment