Information Technology Reference
In-Depth Information
Physical purging
Although logical purging appears to have removed the old job data, the data is per-
sisted in the backend tables. The logically purged jobs will not show up if you search
the job history using the
Search Job Requests
report.
The logically purged jobs are marked as purged, but the rows in the
fu-
sion_ora_ess
schema continue to exist. The BatchDeleteJob will update the
de-
leted column
in the
request_history
table to
Y
. However, the rows are not phys-
ically deleted. This table is based in the
FUSION_TS_TOOLS
tablespace, and over
time, this tablespace will continue to grow.
To physically delete the job's history, the procedure
esspurge.purge_requests
needs to be executed. This procedure will physically remove all the data for jobs that
have completed and have been marked as logically deleted. The runtime command
for this process is:
execute esspurge.purge_requests(systimestamp,
100);
Search WWH ::
Custom Search