Last updated on JULY 06, 2017
Applies to:PeopleSoft Enterprise HCM Absence Management - Version 9.1 and later
Information in this document applies to any platform.
Customers run successive Global Payroll or Absence Management processes (for different countries, companies, pay groups, etc) and the GPPDPRUN processes with run times that are excessive or erratic.
Temporary relief is often noticed when a change is made to the object that, by extension, invalidates the SQL execution plans, e.g. refreshing the database, flushing the shared pool, updating statistics on some table, adding an index whether it's used or not, restarting the database server, etc. But after a few similarly sized runs, the performance can change suddenly when processing a different sized group.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms