SES: Applicant Index Delete Query Not Sensitive to Days Back on Search Definition (Doc ID 2008421.1)

Last updated on JANUARY 26, 2016

Applies to:

PeopleSoft Enterprise HCM Candidate Gateway - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

When specifying the number of days to include in the Applicant Index, the delete query does not use that date to purge old applicants. The delete process should be aware of how long to keep people on the index regardless of status.

For example, a customer initially built their Applicant Index with data going back 18 months. The total SES Index was about 40GB. After 3 months of being live, the SES index has grown to about 56GB resulting in a degraded response time and increased CPU utilization on their SES system. This resulted in an outage requiring additional memory to be configured for the SES database and additional CPUs added to the system.  In analyzing the growth in the database, it was found that Applicant data was being added but only applicants that have been hired (or some other status changes) were being removed from the Index. The customer had to limit the data to applicants from the past 18 months to manage the Index size.   

Therefore, there is no provision for this type of 'aging' of indexed applicants.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms