Purge ATP Temp Tables is a concurrent program in Oracle EBS R12.2 that is used to clean up temporary tables created by the Advanced Planning and Scheduling (APS) engine. These tables are used to store intermediate results during the planning process, but they can become large and take up a significant amount of space in the database over time. These tables are created by the APS engine during the planning process, and they are used to store intermediate results. The APS Temporary tables have a naming convention of starting with ATP_TEMP_, for example, ATP_TEMP_table_name.
The Purge ATP Temp Tables concurrent program is designed to remove these unnecessary tables and free up space in the database.
When the Purge ATP Temp Tables concurrent program is run, it first identifies all the ATP temp tables that are no longer needed by the APS engine. These tables are then deleted from the database, freeing up the space they were occupying. The program also removes any associated indexes and constraints, as well as any related data in other database tables.
One of the main benefits of running the Purge ATP Temp Tables concurrent program is that it can help improve the performance of the APS engine. As the size of the ATP temp tables increases, the time it takes to execute a planning process can also increase. By regularly purging these tables, the APS engine can run more efficiently and quickly.
Another benefit of running the Purge ATP Temp Tables concurrent program is that it can help to prevent the database from running out of space. As the ATP temp tables grow in size, they can consume a large amount of space in the database, potentially causing the database to become full. Running the Purge ATP Temp Tables concurrent program on a regular basis can help to prevent this from happening by removing unnecessary tables and freeing up space in the database.
The Purge ATP Temp Tables concurrent program can be scheduled to run at regular intervals using the Oracle EBS Scheduler. It is recommended to schedule the program to run during off-peak hours to minimize the impact on other processes.
So, Purge ATP Temp Tables concurrent program in Oracle EBS R12.2 is an important tool for maintaining the performance and stability of the APS engine.
The “Purge ATP Temp Tables” concurrent program in Oracle EBS R12.2 typically has the following parameters:
- Start Date: This parameter is used to specify the start date for the purging process. Only ATP temp tables that were last accessed before this date will be deleted.
- End Date: This parameter is used to specify the end date for the purging process. Only ATP temp tables that were last accessed before this date will be deleted.
- Purge Mode: This parameter is used to specify whether the program should delete only the ATP temp tables that are no longer needed or if it should delete all ATP temp tables regardless of whether they are still needed or not.
- Keep Plan: This parameter is used to specify whether the program should keep ATP temp tables associated with a particular plan or not.
- Debug Mode: This parameter is used to specify whether the program should run in debug mode or not. When this parameter is set to “YES”, the program will generate detailed log files that can be used for troubleshooting and debugging.
- Delete Mode: This parameter is used to specify whether the program should delete the ATP temp tables or just mark them as inactive.
- Number of days to retain ATP Temp tables: This parameter is used to specify the number of days ATP temp tables should be retained before being purged.
- Parallelism : This parameter is used to specify the level of parallelism for the concurrent program.
Please note that the specific set of parameters available for the “Purge ATP Temp Tables” concurrent program may vary depending on the specific version of Oracle EBS R12.2 that you are using, and also it can be customized as per the requirement.
- Building a Scalable and Secure AI Infrastructure in the Cloud - May 12, 2024
- Harnessing the Power of AI in the Cloud for Business Transformation - March 2, 2024
- Building a Resilient Cybersecurity Framework in the Oracle Cloud - January 16, 2024