BlogRead the Latest Articles

POBS Table Has Grown in Size and Affects Performance With Project Import/Export in Primavera P6

The following symptoms can be experienced in a Primavera P6 EPPM or Primavera P6 PPM database:

1.  POBS table is increasing in size.

2.  Project imports (XER) are slow due to the import of POBS data.

This issue is caused by a defect.  POBS data is not utilized by any feature of Primavera P6 Professional, but still moves data in and out of P6 through XER import/export operations, causing the reported issue to occur.

This issue has been resolved, and the fix has been included as part of the following patch set releases:

  • Primavera P6 r8.3.12.0
  • Primavera P6 r8.4.8.0
  • Primavera P6 r15.1.5.0
  • Primavera P6 r15.2.1.0
  • Note:  This functionality is automatically included in releases 16.1.0.0 and later.

As part of this fix:

  • Any POBS data in a database will not be included during an XER export operation.
  • Any POBS data in an XER file will not be included during an XER import operation.

 For Versions prior to 8.3.12, 8.4.8 and 15.1.5, 15.2.1.0 (and 8.3.x and earlier releases):

If you are currently unable to upgrade to a fixed version, the following workarounds may be used.  Please note, however, that the POBS data can re-surface.

 WORKAROUND #1:

1.  Delete all of the data from the POBS table from both the source database and target database.

 

Use SQLPLUS or other utility and connect to the database with the 'admuser' account (for a standalone installation, the user account is typically named admprm$pm)


Note, using an Oracle Database only, it is also necessary to disable the RT_POBS & RT_POBS_DEL triggers. To disable the triggers, run the following statement connected to the database as the schema owner (by default, admuser or admprm$pm if standalone):

alter trigger rt_pobs disable;
alter trigger rt_pobs_del disable;

delete from pobs;

commit;

Note:  If using a SQL Server database, use SQL Server Management Studio and connect as either user sa or privuser.

 

2.  From the source database, re-export the XER file (which will ensure the POBS data is not included), and use this updated XER to import into the target database.

WORKAROUND #2:

If you have an XER file which contains POBS data already in it and cannot obtain a new copy of the XER file (that does not contain POBS data):

  1. Delete all of the data from the POBS table from both the source database and target database using the following statement (this will prevent future occurences of POBS data from being generated):
    • Use SQLPLUS or other utility and connect to the database with the 'admuser' account (for a standalone installation, the user account is typically named admprm$pm)

delete from pobs;

commit;   (For Oracle databse only)

Note:  If using a SQL Server database, use SQL Server Management Studio and connect as either user sa or privuser.

  1. Backup the existing XER file by making a copy of the file.
  2. Download the POBS Eraser tool from POBS Eraser Tool Removes POBS Section from XER Files in Primavera P6  and use the tool to remove the POBS data from the XER file OR use one of the alternative methods shown below.
  3. Save the XER file.
  4. Import the updated XER file into Primavera P6.

Alternative methods to clear POBS date from the XER file

Option 1:  --> RECOMMENDED METHOD

  1. Download the XER parser utility from MS Excel 2003 and prior or MS Excel 2007
  2. Launch the parser utility.
  3. Load the XER in the parser utility.
  4. Note:  Macros must be enabled in Excel for this utility to work properly.
  5. Using the tabs at the bottom, select the POBS tab.  Remove ALL of the data on this tab.
  6. Save your changes -> Choose Build XER file.

 

Option 2:

Caution:  While it is possible to manually edit the XER file with a text editor, this carries risks for the quality of the data created/updated.  If the XER data is not edited properly, there is the potential for data corruption.  Option 2 is not supported by Oracle Support Services and is being provided as-is without warranty.  Prior to running any script below, a backup of the database should be made. If you are unsure how to back up your database, do not proceed with the execution of any script.

Open the XER in a text editor (Notepad++ or Textpad are easier to use for this task.)
Find the line which reads: %T POBS
Select the following lines within the XER until you reach the next %T:
%T POBS
%F (including all line content)
%R (including all line content)
Example:
highlight this line --> %T POBS
highlight this line --> %F pobs_id pobs_parent_id seq_num pobs_name pobs_descr pobs_manager
highlight this line --> %R 100 0 POBS_Root Performing Organization_Root
DO NOT HIGHLIGHT THIS LINE, ASSUMING THIS IS THE NEXT %T line listed in the XER file --> %T UDFTYPE
Delete all data highlighted from step 3.
Note: The deleted data should only be the %T (table name line for POBS), %F (field names for POBS), %R (all POBS row data)
Save the XER file changes.



Share This

PRMTransfer

A utility to import/export P6 data

Import P6 data including WBS, activity codes, resources, unit prices etc. from Excel spreadsheets easily with our utility: PRMTransfer.

A replacement for the old Primavera SDK based import

As Primavera SDK is not supported with recent Primavera P6 releases this utility may replace SDK based Excel sheets we used to utilize. PRMTransfer facilitates Primavera API for bi-directional data exchange.


Click here to download it!

 

Giriş yapmak için size sağlanan kullanıcı adını ve şifrenizi giriniz