How to Manually Run Background Jobs for a P6 Database
(Doc ID 907869.1)
Last updated on MARCH 22, 2022
Applies to:
Primavera P6 Professional Project Management - Version 8.3.2.0 to 8.3.2.0 [Release 8.3]Primavera P6 Enterprise Project Portfolio Management - Version 6.0 and later
All Platforms
Goal
The intent of this document is to provide a set of instructions to manually run background jobs for the P6 Database.
Background jobs in general are set to run automatically. See: Error: "The Database Has Not Been Configured To Run Background Jobs." When Logging Into Project Management (Doc ID 905203.1)
- SYMON (System Monitor): responsible for running procedures that take less than a few seconds to complete.
- The procedures run by SYMON perform the following tasks:
- Processing of Project Security updates.
- Logically deleting expired USESSION records.
- DAMON (Data Monitor): responsible for running procedures that take longer than a few seconds to complete.
- The procedures run by DAMON perform the following tasks:
- Cleaning up the BGPLOG table containing the background logs.
- Cleaning up the REFRDEL table.
- Cleaning up the PRMQUEUE table.
- Physically cleaning up remaining USESSION records.
- Cleaning up logically deleted records.
- Cleaning up the PRMAUDIT table.
- Cleaning up the USESSION audit table (USESSAUD).
- Running release-specific data clean up.
- Additionally the functionality of the DAMON process can be dynamically extended via the user-defined procedure, USER_DEFINED_BACKGROUND.
OTHER GOALS
------------------
One reason to run the background jobs manually could be clear a user session for a user who cannot login (DAMON cleans up USESSION).
Solution
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
| Goal |
| Solution |
| References |