Sehedule Concurrent Requests




Oracle SYSADMIN related Concurrent Requests:



1) Gather Schema Statistics

 
 Schedule: Every Weekend (Preferably on every Sat 6:00 pm server time). If this is not sufficient (if performance is not good), it can be done 2/3 times a week.

OR, 
Weekend for ALL schemas and 2/3 times during the week for only few important schemas where in there is heavy insert / update / delete happening.



Parameters:

Schema name: ALL

Parallel Worker: Number of CPUs + 2

Estimate Percent: 30

Other parameters: Default



How to submit: Login to Applications using SYSADMIN account, navigate to System Administrator responsibility, then navigate to Requests > Run





2) Purge Concurrent Request and/or Manager Data

 
Schedule: Every day, nighttime, say 11:00 PM Server time



Parameters:

Age=30 (Purge concurrent request data older than 30 days)

Other parameters: Default



Note: Age parameter needs to be agreed with Business / Customer.



How to submit: Login to Applications using SYSADMIN account, navigate to System Administrator responsibility, then navigate to Requests > Run



3) Purge Concurrent Request and/or Manager Data

 
 Schedule: Every day night time, say 11:30 Server time



Parameters:

Count: 5

Program Application: Application Object Library

Program: Workflow Background Process

Other parameters: Default



Note: Count Parameter needs to be agreed with Business / Customer.



How to submit: Login to Applications using SYSADMIN account, navigate to System Administrator responsibility, then navigate to Requests > Run



4) Workflow Background Process

 
 Schedule: Every 10 min



Parameters:

Process Deferred: Yes

Process Timeout: No



How to submit: Login to Applications using SYSADMIN account, then navigate to Oracle Applications Manager responsibility, then navigate to Workflow Manager, then use “Submit Request for “ facility (top – right hand side) (Select “Background Engines” from drop down)



5) Workflow Background Process

 Schedule: Every 60 min



Parameters:

Process Deferred Yes

Process Timeout: Yes



How to submit: Login to Applications using SYSADMIN account, then navigate to Oracle Applications Manager responsibility, then navigate to Workflow Manager, then use “Submit Request for “ facility (top – right hand side) (Select “Background Engines” from drop down)



6) Workflow Control Queue Cleanup

 Schedule: Every day, night time / early morning hours



Parameters: Default



How to submit: Login to Applications using SYSADMIN account, then navigate to Oracle Applications Manager responsibility, then navigate to Workflow Manager, then use “Submit Request for “ facility (top – right hand side) (Select “Control Queue Cleanup” from drop down)


7) Purge Obsolete Workflow Runtime Data

 Schedule: Every weekend



Parameters:

Age: 30

Other parameters: Default



Note: Age parameter needs to be agreed with Business / Customer.



How to submit: Login to Applications using SYSADMIN account, then navigate to Oracle Applications Manager responsibility, then navigate to Workflow Manager, then use “Submit Request for “ facility (top – right hand side) (Select “Purge” from drop down)



8) Synchronize WF LOCAL tables

 
 Schedule: Every day, night time / early morning hours



Parameters: Default



How to submit: Login to Applications using SYSADMIN account, navigate to System Administrator responsibility, then navigate to Requests > Run
Note: As per metalink id 1158212.1, after E-business version 11.5.10 this request generally does not need to be run.



9) OAM Applications Dashboard Collection

 
 Schedule: Every 30 min



Parameters: Default



How to submit: Login to Applications using SYSADMIN account, navigate to System Administrator responsibility, then navigate to Requests > Run



10) Purge Signon Audit data

 Schedule: Can no schedule needs to be run manually, say every week Monday / Friday morning.



Parameters: Date (By default system date)



Note: Most of customer wants this date to be, 2 to 3 months old



How to submit: Login to Applications using SYSADMIN account, navigate to System Administrator responsibility, then navigate to Requests > Run



Note for DBA’s: There will be check box “Increment data parameter for each run” which must be checked.





11) Purge Debug Log

 
 Schedule: Every day / weekend.



Parameters: Date (By default system date)



Note: Most of customer wants this date to be, 2 weeks to 3 month old



How to submit: Login to Applications using SYSADMIN account, navigate to System Administrator responsibility, then navigate to Requests > Run



Note for DBA’s: There will be check box “Increment data parameter for each run” which must be checked.



12) Resend Failed/Error Workflow Notifications

 
 Schedule: Run every 6 hours.



Parameters: ERROR / FAILED (One request for each parameter)



How to submit: Login to Applications using SYSADMIN account, navigate to System Administrator responsibility, then navigate to Requests > Run



Note for DBA’s: As this request takes date as parameter, it cannot be scheduled easily. You may have to run this physically on one particular day of week, say Monday morning.



DB Jobs


Purge old snapshots from PREFSTAT schema

No comments:

ORA-01552: cannot use system rollback segment for non-system tablespace 'TEMP'

 ORA-01552: cannot use system rollback segment for non-system tablespace "string" Cause: Used the system rollback segment for non...