What is the Results Purge in JDA Allocation?

Go to Action > Results Purge > Configure and set the number of days that the records should be retained. You can set different values for named and unnamed results sets.

Later, when you want to execute the purge, you can either run it manually by going to Action > Results Purge > Execute
or you can execute it from a command line or via SQL Plus:

Schedule the purge process to run from a command line on an administrator's Windows machine where Allocation Administration is installed, or execute it directly from the database package in Oracle.

Example: Windows PC command line
"C:\Program Files\JDA\JDA Allocation\Alchemy.exe" [username] [password]
%PURGE_RESULTS

Notes:

• The username and password must have System Admin privileges.
• You must successfully log in to establish a connection to the database prior to using the command line syntax to start any of the AAL applications.

The purpose of the Results Purge is to age off results sets that are no longer need. The criteria for how long to keep both unnamed and named results is sets in Allocation Administration.

Named results sets are the ones that the user saves with a name to use at a later date.
Unnamed results sets are the ones that are automatically created when results are written that the user does not save with a name. Most results sets will likely be of this variety.

The purge can either be run manually by going to Action > Results Purge > Execute
or by executing it from a command line or via SQL Plus (see below for details).

What this process does is remove all results from the database that are older than the number of days specified, as well as the associated Worklist and Shape records.

The benefit of PurgeResults are:

• Allocation performance improvement (Large amount of unneeded results will have a negative impact)
• Liberation of space in the Allocation database.

Note:

• The primary reason for allowing the results purge to be executed via administration is for test systems that don’t have a normal batch process executing the procedure.
• The WorkList lines and the associated results records are treated as a data set in Allocation. If the WorkList lines have already been deleted, then the system will not be able to purge the results.

Long running PurgeResults can be dependent of the amount of Results to purge.
Missing indexes also have been connected to lengthy PurgeResults runs. (e.g. in QUEUE_OUT table on ALLOC_NBR column)



This is the information from the Admin Guide about Results Purge:
Named and unnamed results sets and their corresponding WorkList and shape table records remain indefinitely, unless code is executed to clean them up. You can purge these potentially unneeded records either programmatically or through Allocation Administration.

First, select the Enable Results Purge parameter on Step 11 of Database Setup. Next, in Allocation Administration, specify the number of days to keep the results from the Action > Results Purge menu. Then, execute the purge process. When executed, the results purge procedure uses your configured settings to determine what should be purged. By default, unnamed results sets and their corresponding WorkList and Shape records are eligible to be purged after 14 days. Named results sets have a life of 999 days, by default.

It is expected that the procedure will be scheduled to run once daily. It will delete only results and their corresponding records for released allocations whose queue_out entry has been processed and deleted by the interface. If a queue_out record still exists for an allocation, it will not be deleted.