Get Started: AI Resources for Oracle Cloud HCM – Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Why is the "Upgrade Time Repository for Absences" running slow
Summary:
We are running the new feature upgrade "Upgrade Time Repository for Absences" and it is very running slow in one of our dev environments. We noticed it ran in a 3-8 hours in other dev environments. Has anyone experienced the process running very slow? At this rate it will be complete in 12 days (it processed 1000 objects out of 16,733 in 20 hours) in other environments it ran ~16,000 objects in 3-8 hours.
We can't have this process running in our PROD environment this slow as there are a lot of activities taking place and will not allow employees to access their absences while this process is running. We also do not want this process to impact the pay run.
Tagged:
0