Multi-Threaded Database Purging Introduced In ASAP To Improve The Purging Performance
(Doc ID 2245853.1)
Last updated on AUGUST 26, 2021
Applies to:Oracle Communications ASAP - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.3.0]
Information in this document applies to any platform.
We are upgrading 7.0.2 to 7.3.0, in the latest version and we found a few brand new parameters in ASAP.cfg. Could you please confirm the following attribute definitions.
# Multi-Threaded Database Purging Parameters specific to SARM server
DB_PURGE_THREADS = 10 # Number of threads to purge the orders in parallel (Range: 1-50)
DB_PURGE_DAYS = 100 # Purge orders older than this number of days (Range: >=0)
DB_PURGE_COMMIT_ROWS = 1000 # Commit after this number of rows have been deleted (Range: >=1)
DB_PURGE_ORPHANS_ENABLED = 0 # Enable or disable the orphan purge (0 = disabled, 1 = enabled)
DB_PURGE_MAX_TIME = 0 # Maximum time (minutes) that the purge is allowed to run (Range: >=0, 0 = No limit)
DB_PURGE_LOG_INTERVAL = 5 # Time interval (minutes) between purge progress log messages (Range: >=1)
DB_PURGE_GET_RANGE_PROC = SSP_get_srqid_purge_range # Stored procedure to get SRQ_ID range of the orders
DB_PURGE_RANGE_PROC = SSP_purge_wo_in_srqid_range # Stored procedure to purge orders in a SRQ ID range
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document