Friday, June 10, 2011

Purging and performence related Concurrent Requests for 11i and R12

The below seeded purging requests will help you to reduce the unwanted data and increase the performence of the oracle Applications.
These requests are applicable to both 11i and R12.

Note :Please note the purging request will delete the data permanently, So if you have any other business requierements please be cautious.

1)The "WORKFLOW CONTROL QUEUE CLEANUP" concurrent program should be scheduled to run at least every 12 HOURS.
 
2)Request Set with the following parameters:

For instances using Oracle Applications Release 11.5.8 or later, a concurrent request set consisting of the "PURGE OBSOLETE WORKFLOW RUNTIME DATA" and "COMPLETE DEFUNCT HR WORKFLOW PROCESSES" concurrent programs should be scheduled to run daily with the following parameters:
    "Purge Obsolete Workflow Runtime Data":
      Item Type: NULL
      Item Key: NULL
      Age: 7
      Persistence Type: select meaning
                        from fnd_lookups
                        where lookup_type = 'FND_WF_PERSISTENCE_TYPE'
                        and lookup_code = 'TEMP';

    "Complete Defunct HR Workflow Processes":
      Item Type: HR
      Age: 7
      Transaction Status: ALL

In addition, the stages of the request set should be linked such that the "Complete Defunct HR Workflow Processes" concurrent program only runs if the "Purge Obsolete Workflow Runtime Data" concurrent program returns Success or Warning.
 


3)The "GATHER SCHEMA STATISTICS" concurrent program should be scheduled to run at least every 7 DAYS.
 
4) For instances using Oracle Applications Release 11.5.8 or later, if PO is licensed, then the "PURGE OBSOLETE WORKFLOW RUNTIME DATA" concurrent program should be scheduled to run every week with the following parameters:

    Item Type: PO Approval
   
5)The program "PURGE CONCURRENT REQUEST AND/OR MANAGER DATA" should be scheduled to run within the next 24 hours with the following parameter(s): Entity=ALL, Mode=Age, Mode Value=30
  
6)The "PURGE OBSOLETE GENERIC FILE MANAGER DATA" concurrent program should be scheduled to run at least once a month with the following parameters:

     Expired=Yes
     Program Name=NULL
     Program Tag=NULL
    
7)The program "PURGE SIGNON AUDIT DATA" should be scheduled to run within  the next 30 days with the following parameter value:

      Audit date: <30 days prior to the scheduled run date>
In addition, the "Increment date parameters each run" scheduling option should be selected for the scheduled run of the program.
    

3 comments:

  1. Regards
    Sridevi Koduru (Senior Oracle Apps Trainer Oracleappstechnical.com)
    LinkedIn profile - https://in.linkedin.com/in/sridevi-koduru-9b876a8b
    Please Contact for One to One Online Training on Oracle Apps Technical, Financials, SCM, Oracle Manufacturing, OAF, ADF, SQL, PL/SQL, D2K at sridevikoduru@oracleappstechnical.com | +91 - 9581017828.

    ReplyDelete
  2. want to recover purged wf runtime data with age0 and persistence type temp

    ReplyDelete