Copy/Paste, Create Baseline or Copy Baseline Service Delay Between Time Job Moves From Running State And When Service Code To Create Data Actually Begins
(Doc ID 2738487.1)
Last updated on MARCH 22, 2022
Applies to:Primavera P6 Enterprise Project Portfolio Management - Version 18.8 and later
Information in this document applies to any platform.
After creating a copy/paste project, create baseline or copy baseline job, there can be intermittent delay between:
- The time the job is moved into a running state (ie, JOBSVC.status_code='JS_Running')
- The time copy/paste service code actually begins
This can be spotted while reviewing log entries configured in debug mode.
After a copy/paste project, create baseline or copy baseline job is created and moved to a running state, the services code for creating the associated data should start immediately.
STEPS TO REPRODUCE
This example uses the Create Baseline job (and P6 Professional to initiate the job), but can also be simulated with copy/paste project and copy baseline (as well as initiating the job from other P6 EPPM modules).
- Login to P6 Professional
- Open a project
- Browse to Project > Maintain Baseline
- Click Add
- Choose option to save copy of project as a baseline
- Click OK
After the job is submitted, the delay can be observed when monitoring the log file as noted above. Also, when the JOBSVC row has been created and first moves to a running state, note the timestamp from the JOBSVC.update_date column (before it moves to a completed status) and compare to the time the "calling stored procedure" message is written to the log to determine delay.
This issue occurs when running p6 services through the p6services.jar deployment.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document