90 total views, 4 views today

Primavera P6 Background Job procedures and its supported ADMUSER.SETTINGS table properties

 

080717_0309_PrimaveraP61 Primavera P6 Background Job procedures and its supported ADMUSER.SETTINGS table properties

 

In this section, I summarize the list of Primavera P6 Background Job procedures and its supported ADMUSER.SETTINGS table properties. Follow the below links for more details about P6 BG Jobs 

 

What is Primavera P6 Background Job

 

How to manually delete Primavera P6 background job tables and rerun BG job

 

 

 

1) Symon Procedures – the job runs every minute

    

  • OBSPROJ_PROCESS_QUEUE Procedure
  • USESSION_CLEAUP_EXPIRED Procedure

 

1.1) OBSPROJ_PROCESS_QUEUE Procedure

 

OBSPROJ_PROCESS_QUEUE processes the PRMQUEUE entries for Project Security. It defers processing of OBSPROJ updates by queuing the updates to the PRMQUEUE table.

 

Namespace Setting Name Default Setting Type      Description:
database.obsproj.queue MaxProjectUpdates      1000      Numeric      Maximum project-level queue records to process on each run     
database.obsproj.queue MaxEpsUpdate 25 Numeric Maximum EPS-level queue records to process on each run.
database.obsproj.queue MaxRetries 50 Numeric Maximum times to re-process a failed entry before marking it as an error

 

1.2) USESSION_CLEANUP_EXPIRED Procedure

 

It logically deletes USESSION records that have not updated their last_active_time based on the Expired Session settings. It marks a record as deleted so it’s not a physical delete.

Oracle recommends that you set the ExpiredLongSessionTimeout sessions to at least one hour longer than your longest job. For example, if your longest job is a summarizer job that usually takes 12 hours, you should set the value in the SETTINGS table to at least 13

 

Namespace SettingName DefaultSetting Type Description
database.cleanup.Usession ExpiredSessionTimeout      2h Interval ExpiredSessionTimeout determines how long an inactive user session will remain in the records before it is marked deleted. User sessions are created when a P6 user logs into P6.     
database.cleanup.Usession ExpiredLongSessionTimeout 12h Interval Setting Description: ExpiredLongSessionTimeout determines how long a session that is running a job-like operation (that is still processing) will remain in the records before it is marked deleted. Job-like operations are processed by job services and some are performed by logged in P6 users. Operations that are considered job-like are:

4 Scheduling ,Leveling , Apply Actuals, Update Progress, Copy/Paste Project, Create Project from Template, Create new baselines, Approve Timesheets, Summarize, PX Publish, Export and Import

 

2) Damon Procedures – the job take long time to run, runs on every Saturday

 

  • BGPLOG_CLEANUP Procedure
  • REFRDEL_CLEANUP Procedure
  • CLEANUP_PRMQUEUE Procedure
  • USESSION_CLEAR_LOGICAL_DELETES Procedure
  • CLEANUP_LOGICAL_DELETES Procedure
  • CLEANUP_ PRMAUDIT Procedure ( From P6 16.2 Onwards, The procedure is CLEANUP_PAUDIT)
  • CLEANUP_USESSAUD Procedure
  • USER_DEFINED_BACKGROUND Procedure

 

2.1) BGPLOG_CLEANUP Procedure

 

This will clean the table BGPLOG every 5 days which will result in a table size of about 54,000 records.

 

Namespace

Setting Value

DefaultSetting

Type

Description

database.cleanup.BackGroundProcessLog     

KeepInterval     

5d

Interval

The oldest records to keep in the BGPLOG table     

 

2.2) REFRDEL_CLEANUP Procedure

 

This procedure deletes records from the REFRDEL table based on the value of the KeepInterval setting. The default setting keeps the REFRDEL records from the last five days.

 

Namespace

SettingName

DefaultSetting

Type

Description

database.cleanup.Refrdel     

KeepInterval     

5d

Interval

The oldest records to keep in the REFRDEL table.     

database.cleanup.Refrdel     

DaysToDelete     

1

Numeric

Identifies the maximum number of minutes before records are deleted from the REFRDEL table     

database.cleanup.Refrdel     

IntervalStep     

15

Numeric

Determines the number of minutes that is added to each delete step interval.     

 

2.3) CLEANUP_PRMQUEUE Procedure

 

This procedure deletes records from the PRMQUEUE table based on the value of the KeepInterval setting

 

Namespace

SettingName

Default Settings

Type

Description

database.cleanup.Prmqueue

KeepInterval     

5d

Interval

The oldest records to keep in the PRMQUEUE table. Default is five days.

database.cleanup.Prmqueue

DeleteAll

0(false)

Beelean

Determines whether the procedure will delete all of the PRMQUEUE records possible on each pass.     

database.cleanup.Prmqueue

DeleteAllThereshold

1000

Numeric

Determines whether all of the records are cleaned. If the total record count is less than this number then all the records are cleaned     

database.cleanup.Prmqueue

DeletePercentage

10(%)

Numeric

Percentage of records to delete on each pass.     

database.cleanup.Prmqueue

MaxRowsToDelete

10000

Numeric

Maximum rows to delete on each pass     

 

2.4) USESSION_CLEAR_LOGICAL_DELETES Procedure

 

This procedure physically deletes all logically deleted USESSION records. This procedure does not have settings associated with it: All logically deleted USESSION records are cleared.

 

 

2.5) CLEANUP_LOGICAL_DELETES Procedure

 

This procedure removes logically deleted rows based on the value of the KeepInterval setting. Records in the database can be marked as deleted (logically deleted) by setting the DELETE_SESSION_ID column to a non-null value. By default, records that were deleted more than 5 days ago will be deleted by this procedure.

 

Namespace SettingName Default Setting Type Description
database.cleanup.LogicalDelete KeepInterval      5d Interval The oldest logically deleted records to keep in tables.     
database.cleanup.LogicalDelete DeleteAll      0(false) Boolean Determines whether the procedure will delete all of the logically deleted records possible on each pass     
database.cleanup.LogicalDelete MaxRowsToDelete      10000 Numeric Maximum rows to delete on each pass.     

 

2.6) CLEANUP_PRMAUDIT Procedure (Or CLEANUP_PAUDIT)

 

If the auditing feature is enabled, this procedure will physically delete records from the table based on the value of the KeepInterval setting.

 

Namsepace

Setting Name

Default Settings

Type

Description

database.cleanup.auditing     

Enabled     

1 (true)     

Boolean     

Should the procedure attempt to clean up PRMAUDIT records     

database.cleanup.auditing     

KeepInterval     

30d     

Interval     

The oldest audit records to keep in PRMAUDIT     

 

2.7) CLEANUP_USESSAUD Procedure

 

The CLEANUP_USESSAUD procedure deletes records from the USESSAUD table based on the KeepInterval parameter setting.

 

Namespace

SettingName

Default Settings

Type

Description

database.cleanup.Usessaud     

KeepInterval     

5d

Interval

The oldest records to keep in the USESSAUD table. Default is five days.

database.cleanup.Usessaud

DeleteAll

0(false)

Beelean

Deletes all the REFRDEL records that satisfy the KeepInterval setting on each pass.

 

database.cleanup.Usessaud

DeleteAllThereshold

1000

Numeric

Determines whether all of the records are cleaned. If the total record count is less than this number then all the records are cleaned     

database.cleanup.Usessaud

DeletePercentage

10(%)

Numeric

Percentage of records to delete on each pass.     

database.cleanup.Usessaud

MaxRowsToDelete

10000

Numeric

Maximum rows to delete on each pass     

 

2.8) USER_DEFINED_BACKGROUND Procedure

 

This procedure is an optional customer procedure that DAMON runs. This procedure does not have settings associated with it.

govindan Primavera P6 Background Job procedures and its supported ADMUSER.SETTINGS table properties
Connect me

Govind

Thank you for visiting my personal blog. Myself Govindan, Software Developer by profession since 2006 and hence I started this blog early in 2016 and ever since I've been writing about technologies experienced and learnings of everyday life.

The views expressed on this blog are my personal views and do not necessarily reflect the views of my employer.

Please feeling free to reach me on any comments and feedbacks you have. Would be more than glad to listen and reply šŸ™‚
govindan Primavera P6 Background Job procedures and its supported ADMUSER.SETTINGS table properties
Connect me

Latest posts by Govind

By | 2017-08-07T21:01:15+00:00 August 7th, 2017|Categories: P6|Tags: |0 Comments
Like us on Facebook.
Connect!