Manually Upgrading p6 Eppm For Microsoft SQL Server Database

Manually Upgrading P6 EPPM for Microsoft SQL Server Release 8.
April 2013
Copyright
Oracle Primavera Manually Upgrading P6 EPPM for Microsoft SQL Server Copyright 1999, 2013, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. The platform-specific hardware and software requirements included in this document were current when this document was published. However, because new platforms and operating system software versions might be certified after this document is published, review the certification matrix on the My Oracle Support Web site for the most up-to-date list of certified hardware platforms and operating system versions. The My Oracle Support Web site is available at the following URL: http://support.oracle.com/ If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
Copyright This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. This software or hardware and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services. To view the list of third party technology disclosures related to this product, please see the Commercial Notices and Disclosures document for the release.
Contents
Copyright ........................................................................................................................................... 2 Preface.............................................................................................................................................. 7 Where to Get Documentation ........................................................................................................... 7 Where To Get Training .................................................................................................................... 10 Where to Get Support ..................................................................................................................... 10 Overview of Manually Upgrading a P6 Database to P6 EPPM R8.2 ............................................... 13 Database Upgrade Considerations for P6 EPPM ............................................................................ 15 Requirements to Manually Upgrade R8.0 or Later to R8.2 .......................................................... 15 Requirements to Manually Upgrade from Version 7.0 or Earlier to R8.2 .................................... 15 Tips to Consider When Manually Upgrading to P6 EPPM R8.2 .................................................... 16 Data that is Not Migrated during the P6 EPPM Database Upgrade ............................................ 17 Risks Migration ................................................................................................................................ 18 Pre-Upgrade Procedures ................................................................................................................. 19 Running the Validate Tool for a 6.2.1 or Later Microsoft SQL Server Database ........................ 19 Converting Methodologies to Projects ........................................................................................... 20 Upgrading the P6 EPPM Microsoft SQL Server Database .............................................................. 21 Post-Upgrade Procedures ............................................................................................................... 23 Creating a Project Template From Projects ................................................................................... 23 Requirements After the Upgrade from P6 EPPM R8 or later to P6 EPPM R8.2.......................... 23 Requirements After the Upgrade from 7.0 or Earlier to P6 EPPM R8.2 ...................................... 24 Private Database Logins for P6 EPPM ............................................................................................ 26 Resetting Private Database Passwords to Use the New Encryption Algorithm ........................... 26 Modifying Private Database Logins for P6 EPPM .......................................................................... 27 Database Administration ................................................................................................................ 29 Background Processes and Clean Up in P6 EPPM ....................................................................... 29 PX Tables Clean Up Procedure ....................................................................................................... 30 RDBMS Scheduler Configuration ................................................................................................... 30 Database Settings Table................................................................................................................. 31 Reading Setting Values ................................................................................................................... 32 Using Code to Read Setting Values for Microsoft SQL Server ................................................. 32 Writing Setting Values ..................................................................................................................... 32 Using Code to Write Setting Values for Microsoft SQL Server ................................................. 32 Tracking Background Job Execution .............................................................................................. 33 High Level Status Settings ......................................................................................................... 33 The BGPLOG Table ..................................................................................................................... 33 SYMON (System Monitor) Procedures ........................................................................................... 34
Manually Upgrading P6 EPPM for Microsoft SQL Server OBSPROJ_PROCESS_QUEUE Procedure................................................................................... 34 USESSION_CLEANUP_EXPIRED Procedure .............................................................................. 35
Tracking Concurrent Usage of P6 EPPM ........................................................................... 37
DAMON (Data Monitor) Procedures ............................................................................................... 38 BGPLOG_CLEANUP Procedure .................................................................................................. 38 REFRDEL_CLEANUP Procedure ................................................................................................. 39 CLEANUP_PRMQUEUE Procedure ............................................................................................. 40 USESSION_CLEAR_LOGICAL_DELETES Procedure .................................................................. 41 CLEANUP_LOGICAL_DELETES Procedure ................................................................................. 41 PRMAUDIT_CLEANUP Procedure............................................................................................... 42 CLEANUP_USESSAUD Procedure .............................................................................................. 43 USER_DEFINED_BACKGROUND Procedure ............................................................................. 44 Oracle Database Performance ....................................................................................................... 44 Safe Deletes .................................................................................................................................... 45 Turning Off Safe Deletes ............................................................................................................ 45 Native Database Auditing ............................................................................................................... 46 Auditing Level Configuration...................................................................................................... 46 Simple Configuration ................................................................................................................. 46 Detailed Configuration ............................................................................................................... 47
Auditing Status ................................................................................................................... 47 Options Setting ................................................................................................................... 47 SETTINGS_WRITE_STRING Procedure .............................................................................. 48
The Audit Table........................................................................................................................... 48 Session Auditing ......................................................................................................................... 50 Column Audit Data ..................................................................................................................... 50 Installing P6 EPPM Applications ..................................................................................................... 50
Preface
In This Section
Where to Get Documentation.................................................................................. 7 Where To Get Training .............................................................................................. 10 Where to Get Support .............................................................................................. 10
Where to Get Documentation

For the most up-to-date versions of all manuals and technical documents related to installing, administering, and using P6 EPPM, go to: http://download.oracle.com/docs/cd/E25030_01/index.htm Most documentation assumes a standard setup of the product, with full access rights to all features and functions. You can also access the versions of the product manuals and technical documents that were available at the time of the release from the P6 EPPM Documentation Center, located in the \Documentation\Documentation_library\language folder of the P6 EPPM physical media or download. The following table describes the core documents available for P6 EPPM and lists the recommended readers by role. P6 EPPM roles are described in the Planning Your P6 EPPM Implementation guide.
Title Description
What's New in P6 EPPM Highlights the new and enhanced features included in this release. You can also use the P6 EPPM Cumulative Feature Overview Tool to identify the features that have been added since a specific release level. All users should read this guide. Planning Your P6 EPPM This book provides information on planning your Implementation implementation. It provides an installation process overview, frequently asked questions, client and server requirements, and security information. The P6 EPPM network administrator/database administrator and P6 administrator should read this guide.
Manually Upgrading P6 EPPM for Microsoft SQL Server
Title
Description
P6 EPPM Installation and Configuration Guide
This documentation set explains how to install and configure the P6 EPPM using the P6 EPPM Installation and Configuration wizards. The P6 EPPM network administrator/database administrator and P6 administrator should read this guide. This documentation set explains how to install and configure the P6 EPPM using the P6 EPPM Installation wizards, and how to manually configure individual components. The P6 EPPM network administrator/database administrator and P6 administrator should read this guide.
P6 EPPM Installation and Manual Configuration Guide
P6 EPPM Post Installation Administrator's Guide
Once you have installed and configured your P6 EPPM applications, this guide will tell you how to get started using them. You will want to complete most of the tasks in this guide before you let your users work with these applications. These tasks include information about configuring your users and security settings and privileges, setting your P6 Administrator application and P6 Progress Reporter Administrator settings, and finalizing your P6 Integration API and P6 EPPM Web Services settings. The P6 EPPM network administrator/database administrator and P6 administrator should read this guide. Lists the configurations that have been tested and verified to work with P6 EPPM. The network administrator/database administrator and P6 EPPM administrator should read this document. This guide explains how to plan, set up, and manage projects in a multiuser environment. If you are new to P6 EPPM, start with this guide to learn how to use the software effectively to plan and manage projects. When you need more detail, refer to the P6 Help. The program manager, project manager, resource/cost manager, and team leader should read this guide. This data dictionary defines fields used in P6. This guide explains how to status activities using P6 Team Member applications, which are P6 Team Member
Tested Configurations
P6 EPPM User's Guide
P6 Data Dictionary P6 Team Member User's Guide
Preface
Title
Description
Web, P6 Team Member for iPhone, and E-mail Statusing Service. P6 Team Member Web Describes how to use P6 Team Member Web to provide Help status on activities. Team members should read this Help. P6 Team Member for iPhone Help P6 Professional for EPPM Help Describes how to use the P6 Team Member for iPhone app to provide status on activities. Team members should read this Help. Explains how to use P6 Professional for EPPM to plan, set up, and manage projects in a multiuser environment. If you are new to P6 Professional, use this Help to learn how to use the software effectively to plan and manage projects. The P6 Professional administrator, program manager, project manager, resource/cost manager, and team leader should read this Help. Describes how to create, manage, plan, and schedule projects, group projects into portfolios, administer all enterprise data, application settings, user accounts, and security profiles, maintain both the organizational breakdown structure (OBS) and enterprise project structure (EPS), manage resources and roles, track risks, issues, and notebooks, create and reuse templates, evaluate budgets, analyze performance and ROI for project portfolios, participate in workflows and document reviews, approve timesheets, and generate reports. The operations executive, P6 EPPM and P6 administrator, program manager, project manager, resource/cost manager, and team leader should read this Help. Describes how to enter database connection information for the P6 Progress Reporter server and modify P6 Progress Reporter server and application settings. The P6 EPPM network administrator/database administrator should read this Help. Describes how to use P6 Progress Reporter to enter and update time spent on assignments. Team members should read this Help.
P6 Help
P6 Progress Reporter Administrator Help
P6 Progress Reporter Help
Title
Description
Primavera Timescaled Logic Diagram Help
Describes how to create, modify, and manage Timescaled Logic Diagrams. Timescaled Logic Diagrams condense the project schedule displayed in the Gantt Chart into a more readable, easier to understand format that provides a snapshot of the entire project plan and the chains of activities that drive the project schedule. The Timescaled Logic Diagram application can be used only with P6 Professional. The P6 EPPM Web Services Programmers Guide, available as an HTML help system, describes how to invoke, use, and troubleshoot the available services/operations within supported environments. The P6 EPPM Web Services Reference Manual, also available as an HTML help system, describes all services and operations available in P6 EPPM Web Services in a comprehensive manner. This guide provides best practices for migrating your P3 data to P6 EPPM, and details how P3 functionality maps to P6 EPPM functionality.
P6 EPPM Web Services Programmers Guide, and P6 EPPM Web Services Reference Manual
P3 to P6 EPPM Migration Guide
Distributing Information to the Team You can copy the online documentation to a network drive for access by project participants. Each team member can then view or print those portions that specifically relate to his or her role in the organization. Throughout this documentation, the Security Guidance icon helps you to quickly identify security-related content to consider during the installation and configuration process.
Where To Get Training

To access comprehensive training for all Primavera products, go to: http://education.oracle.com
Where to Get Support

If you have a question about using Oracle products that you or your network administrator cannot resolve with information in the documentation or help, click http://support.oracle.com/. This page provides the latest information on contacting Oracle Global Customer Support, knowledge articles, and the support renewals process.
10
Preface P6 EPPM integrates with different Oracle applications; when you create a Service Request, be sure to open the request with the proper Support team. To ensure you reach the proper Support team, enter the correct product information when you create the Service Request. Each product has its own support line.
Use the Primavera P6 EPPM support line when you are having installation,
configuration, or connection issues related to P6 EPPM. Use one of the following support lines when you are having installation or configuration issues that do not relate to P6 EPPM. Oracle WebLogic Server Oracle Server BI Publisher BPM

Universal Content Management Microsoft SharePoint Oracle Enterprise Content Management Oracle Access Manager Oracle AutoVue
Access to Oracle Support Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/us/support/contact-068555.html or visit http://www.oracle.com/us/corporate/accessibility/support/index.html if you are hearing impaired.
11
Overview of Manually Upgrading a P6 Database to P6 EPPM R8.2

To manually convert your P6 version 6.2.1 or later database to P6 EPPM R8.2, follow the procedures described in this document. Only an experienced database administrator should perform these procedures. Complete the following sections in the order specified:
Back up the existing P6 database (also known as PMDB). If you are upgrading from Version 7.0 or earlier, migrate all your methodologies. You
cannot use Project Architect after you upgrade, so you will want to migrate your methodologies before you upgrade. (See Converting Methodologies to Projects (on page 20) and Creating a Project Template From Projects (on page 23) for manual migration instructions.) Run the appropriate scripts to upgrade the P6 database structure to P6 EPPM R8.2. Perform required and recommended processes after the upgrade is complete.To configure the SQL database server for SSL, use Microsoft's documentation for instructions on configuring SQL Database Server SSL. Direct questions about Installation / Configurations to the database vendor, Microsoft.
13
Database Upgrade Considerations for P6 EPPM

You can upgrade your existing P6 EPPM database (version 6.2.1 and later) to P6 EPPM R8.2. You must upgrade your P6 EPPM database so it will work with the new version.
In This Section
Requirements to Manually Upgrade R8.0 or Later to R8.2 .................................. 15 Requirements to Manually Upgrade from Version 7.0 or Earlier to R8.2 ............ 15 Tips to Consider When Manually Upgrading to P6 EPPM R8.2 ............................ 16 Data that is Not Migrated during the P6 EPPM Database Upgrade ................. 17 Risks Migration ........................................................................................................... 18
Requirements to Manually Upgrade R8.0 or Later to R8.2

The following list summarizes requirements to upgrade from P6 EPPM R8 or later to P6 EPPM R8.2:
Back up your P6 EPPM database before beginning the upgrade process to ensure
you will not lose any data due to unexpected problems. You should back up your database before you perform any of the steps in this document since the upgrade is not reversible. If you are unsure how to back up your database, do not proceed with the upgrade. Contact your database administrator or database vendor for assistance with backing up your database before performing the database upgrade. Manually run all scripts required to upgrade your existing P6 EPPM database. Test the new database to ensure that the upgrade succeeded.
Requirements to Manually Upgrade from Version 7.0 or Earlier to R8.2

You must upgrade your P6 EPPM database so it will work with the new version.The following list summarizes the procedures required to manually upgrade your database from P6 EPPM version 7.0 or earlier to P6 EPPM R8.2: Notes: These upgrade instructions apply only if you are upgrading from 6.2.1 or later. If you are upgrading from a version earlier than 6.2.1, you cannot directly upgrade to R8.2. For example, if you are on version 5.0, you will need to upgrade to 7.0 before you can upgrade to R8.2.
15
All risk data fields are migrated when upgrading; existing fields are mapped to new fields and others will be mapped to text fields. See Risks Migration (on page 18) for more information.
Back up your P6 EPPM database before beginning the upgrade process to ensure
you will not lose any data due to unexpected problems. You should back up your database before you perform any of the steps in this document since the upgrade is not reversible. If you are unsure how to back up your database, do not proceed with the upgrade. Contact your database administrator or database vendor for assistance with backing up your database before performing the database upgrade. See Data that is Not Migrated during the P6 EPPM Database Upgrade (on page 17) for details on what information will not migrate. Convert your Methodology Management data to projects before you upgrade to P6 EPPM R8.2. See Converting Methodologies to Projects (on page 20) and Creating a Project Template From Projects (on page 23) for manual migration instructions.. Manually run all scripts required to upgrade your existing P6 EPPM database. Test the new database to ensure the upgrade succeeded. Cautions: If you are a current Apache JackRabbit user and upgrade to P6 EPPM 8.2, JackRabbit documents data will not migrate automatically. Refer to My Oracle Support's Knowledge Articles for information on manually migrating JackRabbit documents to Oracle Universal Content Management. Oracle recommends that you migrate the data before upgrading to 8.2. If you are a current jBPM user and upgrade to P6 EPPM R8.2, workflows and reviews data will not be available. You might want to close out all workflows and reviews that are in progress before upgrading to P6 EPPM 8.2. You cannot migrate any of this data to 8.2.
Tips to Consider When Manually Upgrading to P6 EPPM R8.2

Please consider the following tips before you manually upgrade to P6 EPPM R8.2: User Name and Password Tips
Starting with P6 EPPM R8, all new users must create a password with at least one
character, regardless of whether Password Policy is enabled. P6 EPPM will prompt existing users to follow the new requirement if they reset their password and the Password Policy is disabled. The ADMUSER role must have DBA privileges when upgrading or applying patches.
16
Database Upgrade Considerations for P6 EPPM Security Tips
P6 EPPM R8.2 includes an encryption algorithm that provides enhanced security for
private database logins; however, when you manually configure your database, the database does not automatically enforce the encryption algorithm. If you manually configure your database, Oracle recommends that you use this encryption algorithm. To do so, you must reset the private database login. See Resetting Private Database Passwords to Use the New Encryption Algorithm (on page 26) for instructions. If automatically installing or upgrading your database, you do not need to configure the encryption algorithm. User logins and passwords are not affected. Starting with P6 EPPM R8, P6 performs all user security and administration. Due to this change, all Admin Superusers receive Projects module access during the upgrade.To configure the SQL database server for SSL, use Microsoft's documentation for instructions on configuring SQL Database Server SSL. Direct questions about Installation / Configurations to the database vendor, Microsoft. Application Tips
Starting with R8, P6 EPPM does not support Summary-Only projects. During the P6
EPPM database upgrade, existing Summary-Only projects convert to standard projects, but lose all summary data. You can import the summary project from Microsoft Project into the converted blank project, then summarize the data. See the P6 Professional Help. P6 Professional no longer performs recurring job services. Use the Windows command line interface to run batch reports and export projects as a service. To view P6 Professional reports in P6, select the "Store report in Work Products and Documents" option when creating report batches or printing reports. See the P6 Professional Help for more information. ANSI_PADDING for a Microsoft SQL Server Database Tips
To prevent duplicate values in P6 EPPM modules appearing due to leading or trailing

spaces, ensure that the ANSI_PADDING setting in Microsoft SQL Server is Off. For example, if one user enters "Equipment" and another user enters " Equipment" (with a leading space) for resource codes, the database will store both of these as valid values if ANSI_PADDING is On. If ANSI_PADDING is Off, the database will remove the leading space in the second entry and tell the user to enter a unique ID. See the documentation included with Microsoft SQL Server for more information.
Data that is Not Migrated during the P6 EPPM Database Upgrade

When upgrading to P6 EPPM R8.2, the following data will not migrate from previous releases:
Workflows Repository (supported configuration changed from jBPM to Oracle BPM). Content Repository (if previously an Apache JackRabbit user). Refer to My Oracle
Support's Knowledge Articles for information on manually migrating JackRabbit documents to Oracle Universal Content Management.
17
Manually Upgrading P6 EPPM for Microsoft SQL Server Top Down Estimation, including estimated weights (removed). Invited Users in the Project Workspace (removed). Issue Form Categories (removed). Summary Data (new summary tables incompatible with old summary tables). Refer to My Oracle Support's Knowledge Articles for information on manually migrating Scenarios data to the new summary tables. Methodology Management (replaced with Project Templates). See Converting Methodologies to Projects (on page 20) and Creating a Project Template From Projects (on page 23) for manual migration instructions.
Risks Migration
The following table illustrates the risks data field mapping when upgrading from P6 EPPM database (version 6.2.1, 7.0, 7.0 service packs) to P6 R8.2. Note: Some fields will migrate to text fields instead of new fields because certain fields no longer correspond. The new text fields are noted below. Risks Fields Migration Table P6 EPPM database (version 6.2.1, 7.0, and 7.0 service packs) Risks Fields Risk Id risk_name risk_descr status_code risk_type_id risk_control table_name wbs_id rsrc_id obs_id priority_type P6 EPPM R8.2 Risks Field id name description status category_id notes table_name cause (with heading 'Applies to WBS' <WBS name>) cause (with heading 'Applies to Resource' <resource name>) cause (with heading 'Responsible Manager' <OBS name>) cause (with heading 'Priority' <priority type>)
18
Pre-Upgrade Procedures
P6 EPPM database (version 6.2.1, 7.0, and 7.0 service packs) Risks Fields add_date impact_date prbly_pct impact_work_qty impact_equip_qty
P6 EPPM R8.2 Risks Field cause (with heading 'Date Identified' <add_date in mmm-dd-yyyy format >) cause (with heading 'Date Identified' <add_date in mmm-dd-yyyy format >) cause (with heading 'Probability' <prbly_pct>) cause (with heading 'Impact - Labor Units' <impact_work_qty> - 2 decimals) cause (with heading 'Impact Nonlabor Units' <impact_equip_qty> - 2 decimals) cause (with heading 'Impact - Material Units' <impact_mat_qty> - 2 decimals) cause (with heading 'Impact Expenses' <impact_expense_cost> - 2 decimals)
impact_mat_qty Impact_expense_cost
Pre-Upgrade Procedures
Perform the tasks in the following topics before upgrading your database.
Related Topics
Running the Validate Tool for a 6.2.1 or Later Microsoft SQL Server Database19 Converting Methodologies to Projects .................................................................. 20
Running the Validate Tool for a 6.2.1 or Later Microsoft SQL Server Database
Use the validate tool to ensure your database is not missing objects that could cause the database to fail to upgrade. You must perform the steps below before you download the 8.2 media pack. If you run the 8.2 validate tool against your current database, it will not work. 1) Double-click validate.bat (validate.sh for Linux) in your current Database folder of the P6 EPPM physical media or download to start the validate tool.
19
Note: Ensure you use the validate file from your current Database folder, not the 8.2 database folder. 2) Provide the following: a. In the Database host address field, enter the server machine name or IP address where you installed Microsoft SQL Server. b. In the Database host port field, enter the port number that Microsoft SQL Server is using. The default is 1433. c. In the Database name field, enter the name of the existing database that you want to validate. 3) View the HTML page that the tool creates to ensure your database is not missing objects. 4) If your database is missing objects, do one of the following: If upgrading from 6.2.1 or 7.0, go to the 'Client Application' media pack, then locate the \install\database\scripts\ folder to find the scripts you need to fix. If upgrading from the 8.0 or 8.1, go to the database folder of the P6 EPPM physical media or download, then locate the \database\scripts\install\ to find the scripts you need to fix.
Converting Methodologies to Projects

To migrate Methodology Management version 7.0 or earlier data to P6 R8.2 Project Templates, you must first use Project Architect in the Project Management module (version 7.0 or earlier) to convert the data from a methodology to a project. To convert Methodology Management data to a project: 1) Create a new EPS node in P6 Professional version 7.0 where you can store all your Methodology Management projects. 2) Use Project Architect in P6 Professional version 7.0 to create projects from Methodology Management data. For more information on using Project Architect, see version 7.0 of the Oracle Primavera P6 Project Management Reference Manual. Note: You can create only one project at a time. If you want all of your Methodology Management data moved to P6 Project Templates, contact Oracle Consulting to automate the process. 3) After you have converted all your Methodology Management data to projects, upgrade P6 EPPM to 8.2. 4) Launch P6. 5) Convert your upgraded projects (formerly methodologies) to project templates. See Creating a Project Template From Projects (on page 23).
20
Upgrading the P6 EPPM Microsoft SQL Server Database

To upgrade the P6 EPPM Microsoft SQL Server Database: 1) If you haven't done so, download the Primavera P6 Enterprise Project Portfolio Management R8.2 for <platform> folder and extract the contents. 2) Go to the location of the extracted contents and locate the P6_R8.2\p6suite\database folder. Notes: Make a backup copy of any files you will modify before you edit them. You need to execute all the scripts included in this section against PMDB to upgrade.
3) Open Microsoft SQL Server Management Studio and log in as the SA user. 4) Go to \scripts\install\PM_08_02_00 and execute the sspm_create_plus_users.sql script. Notes: Running the sspm_create_plus_users.sql script creates the following user name: PxRptUser. If you have created another user name and wish to use that when running P6 EPPM database scripts, make sure to replace the PxRptUser name with your custom user name in all applicable scripts before running them. Do not use special characters in the database name, privileged user, public user, or PX reporting user name, for example: { } [ ] : ; < > , . ? ! @ # $ % ^ & * ( ) - _ | / \ ~ `
5) Go to scripts\common and execute the ss_disable_triggers.sql script. 6) Go to \scripts\upgrade\PM_08_02_00 on your local drive. Execute one of the following scripts: SSPM_p62.sql, if upgrading from P6 version 6.2.1 SSPM_p621sp1.sql, if upgrading from P6 version 6.2.1 service pack 1 SSPM_p70sp1.sql, if upgrading from P6 version 7.0, 7.0 service pack 1, or 7.0 service pack 2 SSPM_p70sp3.sql, if upgrading from P6 version 7.0 service pack 3 SSPM_p80.sql, if upgrading from P6 version 8.0 SSPM_p81.sql, if upgrading from P6 version 8.1
21
Manually Upgrading P6 EPPM for Microsoft SQL Server 7) If you're using version SSPM_p70sp1.sql or later, skip to the next step. If you're using a version before SSPM_p70sp1.sql, go to \scripts\common and execute the ss_update_usereng.sql script to grant all users with P6 Professional module access rights to the Projects section in P6. Note: Prior to P6 version 7.0, users with Project Management module access also had rights to the Projects section in P6 Web Access. For security reasons, beginning with P6 version 7.0, P6 Professional module access only grants rights to log into the P6 Professional module. 8) Go to \scripts\common and execute the ss_post_upgrade script. 9) Go to \scripts\upgrade\PM_08_02_00 and execute the sspm_grants.sql script. Note: If you changed the default user names, you must update the privuser, pubuser, and PxRptUser names in this script with your custom user names. 10) Go to \scripts\upgrade\PM_08_02_00 and execute the sspm_synonyms.sql script. Caution: The sspm_synonyms.sql script contains a table called PUBUSER, do not replace it if you have to change the pubuser user name. Note: If you changed the default user names, you must update the privuser, pubuser, and PxRptUser names in this script with your custom user names. 11) Go to \scripts\source\PM_08_02_00 and execute the sspm_src.plb script. Notes: If you changed the default privuser name, you must update the sspm_src.plb script with your custom privuser name. Do not use special characters in the database name, privileged user, public user, or PX reporting user name, for example: { } [ ] : ; < > , . ? ! @ # $ % ^ & * ( ) - _ | / \ ~ `
12) Go to \scripts\install\PM_08_02_00 and execute the sspm_database_version.sql and sspm_querylib.sql scripts. 13) Go to \scripts\common and execute the ss_enable_constraints_triggers.sql script. 14) Go to \scripts\install\PM_08_02_00 and execute the sspm_init_bgjobs.sql script. 15) Run the databaselogins.bat (on Windows) or databaselogins.sh (on Unix) to upgrade the encryption of privilege user passwords. 16) Log into the P6 EPPM database as PxRptUser or use your custom PX reporting user name if you created one.
22
Post-Upgrade Procedures 17) Go to scripts\source\PM_08_02_00 and execute the sspm_px_rpt_src.sql script.
Post-Upgrade Procedures
Consider the following after you upgrade your database.
Related Topics
Creating a Project Template From Projects .......................................................... 23 Requirements After the Upgrade from P6 EPPM R8 or later to P6 EPPM R8.2... 23 Requirements After the Upgrade from 7.0 or Earlier to P6 EPPM R8.2 ............... 24
Creating a Project Template From Projects

After you have converted your Methodology Management data to projects and upgraded your database to 8.2, you can create your project templates. To create a project template: 1) 2) 3) 4) 5) Click Projects. On the Projects navigation bar, click EPS. On the EPS page, click the Actions menu and select Add Add Project Template. In the Add Project Template dialog box, choose the General tab. On the General tab: a. In the Template ID field, type in a unique ID for the template. b. In the Template Name field, type in a unique name for the template. c. In the EPS field, click the corresponding and choose the EPS where you want to store the template. d. In the Responsible Manager field, click the corresponding and choose a responsible manager. e. In the Copy from existing project or template field, click the corresponding and choose the methodology project you created in Converting Methodologies to Projects (on page 20). f. Click Create.
Requirements After the Upgrade from P6 EPPM R8 or later to P6 EPPM R8.2

The following list summarizes the procedures to perform after the upgrade to P6 EPPM R8.2: Backup Procedures
23
Oracle recommends you make a backup of your newly upgraded database.

User Name and Password Procedures For security reasons, Oracle strongly recommends that you replace the default database users' (admuser, privuser, pubuser, bgjobuser, and pxrptuser) passwords immediately after a manual database installation or an upgrade from P6 version 7.0 and earlier. Do not use special characters in the database name, privileged user, public user, or PX reporting user name, for example: { } [ ] : ; < > , . ? ! @ # $ % ^ & * ( ) _|/\~` For instructions on how to replace the private database login, follow the instructions in Modifying Private Database Logins for P6 EPPM (on page 27). For all other database user names and passwords, use the tools included with the database. The background job user has to be reset only for manual installations.
Oracle recommends using strong passwords. Strong passwords in P6 EPPM contain between 8 and 20 characters and at least one numeric and one alpha character. To further strengthen the password, use a mixture of upper and lower case letters.
Application Configuration Procedures
Install the new P6 and P6 Progress Reporter servers, P6 Professional, and any
additional components. Starting with P6 EPPM R8, all recurring job service functions are hosted by P6. Due to this change, after upgrading to P6 EPPM R8 or later, you must configure Scheduled Services settings in the P6 Administrator application to use this functionality. See the P6 EPPM Post Installation Administrator's Guide for details. Assign new or modified privileges to users. See information about security profiles in the P6 EPPM Post Installation Administrator's Guide. Security Procedures
For security reasons, Oracle strongly recommends that you replace the default Admin Superuser (admin) immediately after a manual database installation or an upgrade from P6 version 7.0 and earlier. See the P6 EPPM Post Installation Administrator's Guide for details on the default admin superuser.
Requirements After the Upgrade from 7.0 or Earlier to P6 EPPM R8.2

The following list summarizes the procedures you need to perform after the upgrade to P6 EPPM R8.2: Backup Procedures
Oracle recommends that you make a backup of your newly upgraded database.
User Name and Password Procedures
24
Post-Upgrade Procedures For security reasons, Oracle strongly recommends you replace the default database users' (admuser, privuser, pubuser, bgjobuser, and pxrptuser) passwords immediately after a manual database installation or an upgrade from P6 version 7.0 and earlier. Do not use special characters in the database name, privileged user, public user, or PX reporting user name, for example: { } [ ] : ; < > , . ? ! @ # $ % ^ & * ( ) _|/\~` For instructions on how to replace the private database login, follow the instructions in Modifying Private Database Logins for P6 EPPM (on page 27). For all other database user names and passwords, use the tools included with Oracle Database. The background job user has to be reset only for manual installations.
Oracle recommends using strong passwords. Strong passwords in P6 EPPM contain between 8 and 20 characters and at least one numeric and one alpha character. To further strengthen the password, use a mixture of upper and lower case letters.
Application Configuration Procedures
Install the new P6 and P6 Progress Reporter servers, P6 Professional, and any
additional components. Starting with P6 EPPM R8, all recurring job service functions are hosted by P6. Due to this change, after upgrading to P6 EPPM R8 or later, you must configure Scheduled Services settings in the P6 Administrator application to use this functionality. See the P6 EPPM Post Installation Administrator's Guide for more information. Resummarize all projects to accurately reflect your summary data. See information about configuring a separate server for job services in the P6 EPPM Post Installation Administrator's Guide. Assign new or modified privileges to users. See information about security profiles in the P6 EPPM Post Installation Administrator's Guide. All previously defined module access (except Team Member module access), security profiles, OBS access, and resource security settings will still apply to existing users after the database upgrade. For users who had Team Member and P6 Professional module access, they will keep their access during the database upgrade; however, once you edit these users post-upgrade, P6 will remove Team Member module access to comply with P6 EPPM functionality. The upgrade process will remove only Team Member access during the upgrade if users had Team Member and additional module access assignments other than P6 Professional; all other assignments will remain selected. See the P6 EPPM Post Installation Administrator's Guide for information on defining module access, security profiles, OBS access, and resource security. During the upgrade to P6 EPPM 8.2, some P6 Activity Views settings will reset. After the upgrade, use the Customize Detail Windows feature to modify the settings that should appear for each view. See the P6 Help for information on how to edit Activity Views.
25
Starting with P6 EPPM R8, P6 saves filter definitions globally. Filters still work for Activity
Views, but all standard filter assignments reset during the upgrade. Due to this change, views that had Standard Filters applied will show all activities after the upgrade. Reapply filters after the upgrade finishes. See the P6 Help for information on how to edit Activity Views. Security Procedures
For security reasons, Oracle strongly recommends that you replace the default Admin Superuser (admin) immediately after a manual database installation or an upgrade from P6 version 7.0 and earlier. See the P6 EPPM Post Installation Administrator's Guide for information on changing the default admin superuser.
Private Database Logins for P6 EPPM

Private database logins are used primarily by administrators to gain direct access to a database. For example, the privileged user login that you use to access the P6 EPPM database is a private database login. You can add, modify, or delete existing logins using the Database Logins tool. P6 EPPM R8.2 includes an encryption algorithm that provides enhanced security for private database logins; however, when you manually configure your database, the database does not automatically enforce the encryption algorithm. If you manually configure your database, Oracle recommends that you use this encryption algorithm. To do so, you must reset the private database login. See Resetting Private Database Passwords to Use the New Encryption Algorithm (on page 26) for instructions. If you automatically configure your database, you do not need to configure the encryption algorithm. User logins and passwords are not affected.
Related Topics
Resetting Private Database Passwords to Use the New Encryption Algorithm 26 Modifying Private Database Logins for P6 EPPM .................................................. 27
Resetting Private Database Passwords to Use the New Encryption Algorithm

Use the steps that follow to reset private database passwords to use the new encryption algorithm. From the Database folder in the Primavera P6 Enterprise Project Portfolio Management R8.2 for <platform> folder of the physical media or download: 1) Run databaselogins.bat (databaselogins.sh for Linux). 2) On the Database Connection dialog box:
26
Private Database Logins for P6 EPPM a. Select the database. b. Type the user name and password of a privileged database user (for example, privuser). This login should have administrative rights on the database. c. Enter the host address, host port, and database/instance name specific to your installation. The Port field displays the default port for the database type you selected. d. Click Next. 3) On the Private Database Logins dialog box: a. Select the private database user name that you wish to reset. b. Highlight the password and change it (or simply re-enter the existing password). c. Click the Update Password button. Note: To reverse a change, click Undo. Undo will reverse any changes made during the current session. d. Click Save. e. Click OK to exit the Database Logins tool.
Modifying Private Database Logins for P6 EPPM

Use the steps that follow to modify private database logins. From the Database folder in the Primavera P6 Enterprise Project Portfolio Management R8.2 for <platform> folder of the physical media or download: 1) Run databaselogins.bat (databaselogins.sh for Linux). 2) On the Database Connection dialog box: a. Select the database. b. Type the user name and password of a privileged database user (for example, privuser). This login should have administrative rights on the database. c. Enter the host address, host port, and database/instance name specific to your installation. The Port field displays the default port for the database type you selected. d. Click Next. 3) On the Private Database Logins dialog box: a. Select the private database user name that you wish to modify. b. Enter a new user name. c. Highlight the password, and change it. d. Click the Update Password button. Note: To reverse a change, click Undo. Undo will reverse any changes made during the current session.
27
Manually Upgrading P6 EPPM for Microsoft SQL Server e. Click Save. f. Click OK to exit the Database Logins tool.
28
Database Administration
Read this chapter to learn how to configure the job scheduler supplied by your RDBMS, how to optimize performance of your P6 EPPM database, and how to configure the native database auditing feature to monitor edits, deletions, and additions to the databases.
In This Section
Background Processes and Clean Up in P6 EPPM ............................................... 29 PX Tables Clean Up Procedure ............................................................................... 30 RDBMS Scheduler Configuration ............................................................................ 30 Database Settings Table .......................................................................................... 31 Reading Setting Values ............................................................................................ 32 Writing Setting Values ............................................................................................... 32 Tracking Background Job Execution ..................................................................... 33 SYMON (System Monitor) Procedures .................................................................... 34 DAMON (Data Monitor) Procedures ...................................................................... 38 Oracle Database Performance.............................................................................. 44 Safe Deletes ............................................................................................................... 45 Native Database Auditing....................................................................................... 46
Background Processes and Clean Up in P6 EPPM

Because clean up tasks can be resource intensive and time consuming, in P6 EPPM, these tasks are initiated by two background jobs that run on the database server using the background job processes user name:
SYMON (System Monitor), responsible for running procedures that take less than a few
seconds to complete. DAMON (Data Monitor), responsible for running procedures that take longer than a few seconds to complete. Both of these jobs are pre-configured with default settings. Since the default settings are optimal for most environments, you generally do not need to tune them. However, if you need to optimize your background process further, you can use the background job processes user to change the settings to tune the behavior of the background jobs for specific environments.
29
PX Tables Clean Up Procedure

To avoid operational problems for P6, PX table entries are not automatically deleted when you delete data from P6 tables. You can use the following clean up procedure to clear the obsolete entries in PX tables. 1) Run the CLEAN_PX_DELETE stored procedure to purge obsolete entries in the PX tables: For a Microsoft SQL Server database: USE [ddname] GO DECLARE @return_value int EXEC @return_value = [dbo].[CLEAN_PX_DELETE] SELECT 'Return Value' = @return_value GO where ddname is the admin user name Note: You can run this procedure any time you want or you can run it as a database background job and schedule a specific time for it to run. 2) To delete batch size and max delete from each table in a single run, run the following queries: Note: You can specify the delete batch size and max delete from each table in a single run. Delete batch size is the number of rows deleted before a commit. Max delete is the max number of rows that will be deleted from a table in a single run. They have default values if you do not provide your own. They're used to avoid resource problems with the P6 operations. insert into settings (namespace, setting_name, setting_value) values ('PxService.Cleanup','DeleteMaxSize','100000'); insert into settings (namespace, setting_name, setting_value) values ('PxService.Cleanup','DeleteBatchSize','5000');
RDBMS Scheduler Configuration

Since background jobs are initiated by the job scheduler supplied by the RDBMS, you need to ensure that the scheduler for your specific RDBMS is properly configured. For a Microsoft SQL Server Database: P6 EPPM uses the SQL Agent service to automatically schedule background job execution for Microsoft SQL Server. Background jobs handles the maintenance of the utilities tables (for example, USESSION and REFRDEL). As part of background jobs, the agent runs the SYMON and DAMON stored procedures at specific intervals.
30
Database Settings Table

Settings Table Overview The settings table contains name-value pairs that configure the behavior of the background processes. Namespace The namespace component is a dot-notation string representing a formal path to the parameter. Setting Name The setting name identifies the name of the setting. Value Values in the SETTINGS table are case-sensitive. The value portion of the pair can be:
String. The string data type is a free text value. The most common string sub-type is
interval which represents an interval of time by combining a numeric portion with a unit portion as depicted in the table below. Interval Subtype Table
Unit portion Example Meaning
d Numeric portion + h m s
30d 2h 10m 30s
Thirty day interval Two hour interval Ten minute interval Thirty second interval
Numeric. The numeric data type consists of any number. Boolean. The boolean data type can have one of two values: true or false, where
zero represents false and any non-zero number represents true.
Date. The date data type consists of dates.

Setting Example The following is an example of a setting:
Namespace: database.cleanup.Usession Setting Name: ExpiredSessionTimeout Value: 2h (two hour interval)
31
Reading Setting Values

You can configure settings through the Settings API Procedures. These procedures are similar to registry or INI file procedure calls. Reading Settings Values Use the following SETTINGS_READ_* procedures to determine the current value of specific settings:
SETTINGS_READ_STRING(ret_val,namespace,settings_name,default) SETTINGS_READ_DATE(ret_val,namespace,settings_name,default) SETTINGS_READ_NUMBER(ret_val,namespace,settings_name,default) SETTINGS_READ_BOOL(ret_val,namespace,settings_name,default)
Using Code to Read Setting Values for Microsoft SQL Server

The following code snippets for the Microsoft SQL Server database demonstrate how the SETTINGS_READ_* procedures read the setting values. To retrieve the value of the KeepInterval setting in SQL: 1) Use the following code: declare @vset varchar(255) exec settings_read_string @vset OUTPUT,'database.cleanup.Usession','ExpiredSessionTimeout' print @vset 2) The following message should appear: PL/SQL procedure successfully completed. SQL> print vset
Writing Setting Values

Use the SETTINGS_WRITE_STRING procedure to set the value of a specific setting: SETTINGS_WRITE_STRING(new value,namespace,settings_name);
Using Code to Write Setting Values for Microsoft SQL Server

The following code snippets for Microsoft SQL Server databases demonstrate how the SETTINGS_WRITE_STRING procedure sets the value of the ExpiredSessionTimeout setting to twelve hours. To set the value of the ExpiredSessionTimeout setting to twelve hours in a Microsoft SQL Server database: 1) Open the Query Analyzer/SSMS and connect as privuser. 2) Select the P6 EPPM database, then run the following statement (using 12 hours as an example):
32
Database Administration exec SETTINGS_WRITE_STRING '12h','database.cleanup.Usession', 'ExpiredSessionTimeout'
Tracking Background Job Execution

You can track the execution of background jobs by monitoring the high level status settings or by inspecting the BGPLOG table.
High Level Status Settings

Each time a job runs it will update the SETTINGS table for the setting_name = 'HeartBeatTime.' The job can update this value multiple times during the execution. You can monitor the maximum difference between this time and the current date to ensure that the job is running promptly. Refer to the High Level Status Settings table below for information about the HeartBeatTime setting. High Level Status Settings
Last date and time background job SYMON ran.
Namespace Setting Name Default Setting
database.background.Symon HeartBeatTime N/A
Last date and time background job DAMON ran.
Namespace Setting Name Default Setting
database.background.Damon HeartBeatTime N/A
The BGPLOG Table

You can also track the execution of background jobs by inspecting the BGPLOG table. The BGPLOG table holds detailed entries from the background processes including informational, elapsed time, and error entries. Refer to the BGPLOG Table Descriptions for information about what this table contains. BGPLOG Table Descriptions
33
Column
Description
Value
Log_time
Time when background process made a log entry Program generating log entry Type of message Message from the background process
Datetime
Source Type Description
"system_monitor", "data_monitor" INFORMATION, ELAPSED TIME, ERROR A variable message followed by a number in parenthesis that represents the number of rows that processed. As an example, the message "Complete BGPLOG (40)" indicates that forty rows processed.
SYMON (System Monitor) Procedures

SYMON runs simple P6 EPPM tasks on a quick schedule. By default, the job runs every minute; the tasks assigned to this job should take only a few seconds to complete on each run. Do not change the scheduled run time (every minute) for this procedure. Procedures performed by SYMON The procedures run by SYMON perform these tasks:
Processing the PRMQUEUE entries for Project Security by queuing OBSPROJ updates to
the PRMQUEUE table.
Marking expired USESSION records as logically deleted.

Note: You can manually run queries to assist you with tracking concurrent usage of P6 EPPM.
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. Refer to the following table for information about the settings associated with the OBSPROJ_PROCESS_QUEUE procedure.
34
OBSPROJ_PROCESS_QUEUE Settings
Setting Description: Maximum project-level queue records to process on each run. Namespace Setting Name Default Setting Type database.obsproj.queue MaxProjectUpdates 1000 Numeric
Setting Description: Maximum EPS-level queue records to process on each run. Namespace Setting Name Default Setting Type database.obsproj.queue MaxEpsUpdate 25 Numeric
Setting Description: Maximum times to re-process a failed entry before marking it as an error. Namespace Setting Name Default Setting Type database.obsproj.queue MaxRetries 50 Numeric
USESSION_CLEANUP_EXPIRED Procedure
USESSION_CLEANUP_EXPIRED logically deletes USESSION records that have not updated their last_active_time based on the Expired Session settings. Marking expired USESSION records as logically deleted maximizes the number of module access logins that are available. Since it is not cleaning up the underlying data (physically deleting rows), the task completes quickly. Values in the SETTINGS table control the clean up of expired sessions. By default, although the clean up of expired sessions occurs every two hours, the SETTINGS table does not contain a value for this setting. Use the SETTINGS_WRITE_STRING (value, namespace, setting) stored procedure to change the default clean up value. For example, setting the value to "2d" deletes expired sessions older than two days.
35
Note: 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. Refer to the table below for information about the USESSION_CLEANUP_EXPIRED Settings.
USESSION_CLEANUP_EXPIRED Settings
Setting Description: 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. Namespace Setting Name Default Setting Type database.cleanup.Usession ExpiredSessionTimeout 2h 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: Scheduling Leveling Apply Actuals Update Progress Copy/Paste Project Create Project from Template Maintain Baselines (create new baseline) Approve Timesheets Summarize PX Publish Export Import Namespace Setting Name database.cleanup.Usession ExpiredLongSessionTimeout
36
Database Administration Default Setting Type 12h Interval
Tracking Concurrent Usage of P6 EPPM To track concurrent usage of P6 EPPM, you can run queries against the USESSION and USESSAUD tables to perform self-audits. See sample queries below. Note: See DAMON (Data Monitor) Procedures (on page 38) for information on how to set up the USESSAUD procedure. To ensure accuracy of these queries, run them before physically deleting remaining USESSION records and cleaning up the USESSAUD table.
Against the USESSION table, run the following query to determine how many users are
logged in at a given time: select count(*) from usession where delete_session_id is null
Against the USESSION table, run the following query to determine how many users are
logged into a specific P6 EPPM product at a given time: select count (*) from usession where delete_session_id is null and app_name='P6 EPPM product name' where P6 EPPM product name is the application abbreviation. Note: You can view all available application abbreviations by running the following query as an administrative database user: select distinct(db_engine_type) from usereng
Against the USESSAUD table, run a query similar to the following to determine how
many users logged into P6 EPPM on a specific date during a specified time range. You can alter the date, time range, and P6 EPPM product as needed. The following example will search for all users who logged into P6 Professional on February 17, 2010 between 9am and 10am: For a Microsoft SQL Server database: select * from usessaud where login_date between '2010-02-17 09:00' and '2011-02-17 10:00' and app_name='Project Management'
Tips See "Counting Users" in the P6 EPPM Post Installation Administrator's Guide for information on counting users and how to view the total number of licenses assigned for each module.
37
DAMON (Data Monitor) Procedures

The second database job is the DAMON data monitor job. The DAMON job runs the majority of the background processing and is responsible for running background clean up processes required by the application that can potentially take a relatively long time to run. Microsoft SQL Server and DAMON By default, DAMON runs every Saturday. You can set it to run every two weeks or on a specific day. To run DAMON every two weeks, use the following command to set the interval: -eg 2W To set DAMON to run on a specific day, use the following setting under namespace: Database.background.Damon DayOfWeek DAMON Procedures DAMON cleans the: BGPLOG table containing the background logs. REFRDEL table. PRMQUEUE table. Remaining USESSION records. Logically deleted records. PRMAUDIT table. USESSION audit table (USESSAUD).
You can also dynamically extend DAMON functionality via the user-defined procedure, USER_DEFINED_BACKGROUND.
BGPLOG_CLEANUP Procedure
This procedure keeps the BGPLOG table at a reasonable size. The default clean up interval is 5 days which will result in a table size of about 54,000 records. Refer to the following table for information about the settings associated with the BGPLOG_CLEANUP procedure.
BGPLOG_CLEANUP Settings
Setting Description: The oldest records to keep in the BGPLOG table. Namespace Setting Name Default Setting Type database.cleanup.BackGroundProcessLog KeepInterval 5d Interval
38
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. Refer to the following table for information about the settings associated with the REFRDEL_CLEANUP procedure:
REFRDEL_CLEANUP Settings
Setting Description: The oldest records to keep in the REFRDEL table. Namespace Setting Name Default Setting Type database.cleanup.Refrdel KeepInterval 5d Interval
Setting Description: Identifies the maximum number of minutes before records are deleted from the REFRDEL table. Namespace Setting Name Default Setting Type database.cleanup.Refrdel DaysToDelete 1 Interval
Setting Description: Determines the number of minutes for each step interval. Namespace Setting Name Default Setting Type database.cleanup.Refrdel IntervalStep 15m Interval
39
CLEANUP_PRMQUEUE Procedure
This procedure deletes records from the PRMQUEUE table based on the value of the KeepInterval setting. The remaining settings are similar to the REFRDEL_CLEANUP. Refer to the following table for information about the settings associated with the CLEANUP_PRMQUEUE procedure:
CLEANUP_PRMQUEUE Settings
Setting Description: The oldest records to keep in the PRMQUEUE table. Default is five days. Namespace Setting Name Default Setting Type database.cleanup.Prmqueue KeepInterval 5d Interval
Setting Description: Determines whether the procedure will delete all of the PRMQUEUE records possible on each pass. Namespace Setting Name Default Setting Type database.cleanup.Prmqueue DeleteAll 0 (false) Boolean
Setting Description: Determines whether all of the records are cleaned. If the total record count is less than this number then all the records are cleaned. Namespace Setting Name Default Setting Type database.cleanup.Prmqueue DeleteAllThreshold 1,000 Numeric
Setting Description: Percentage of records to delete on each pass. Namespace Setting Name database.cleanup.Prmqueue DeletePercentage
40
Database Administration Default Setting Type 10(%) Numeric
Setting Description: Maximum rows to delete on each pass. Namespace Setting Name Default Setting Type database.cleanup.Prmqueue MaxRowsToDelete 10,000 Numeric
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.
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. Note: The CLEANUP_LOGICAL_DELETES procedure will not delete records whose DELETE_SESSION_ID column is set to a negative value. Refer to the following table for information about the settings associated with the CLEANUP_LOGICAL_DELETES procedure:
CLEANUP_LOGICAL_DELETES Settings
Setting Description: The oldest logically deleted records to keep in tables. Namespace Setting Name Default Setting database.cleanup.LogicalDelete KeepInterval 5d
41
Manually Upgrading P6 EPPM for Microsoft SQL Server Type Interval
Setting Description: Determines whether the procedure will delete all of the logically deleted records possible on each pass. Namespace Setting Name Default Setting Type Namespace Setting Name Default Setting Type database.cleanup.LogicalDelete DeleteAll 0 (false) Boolean database.cleanup.LogicalDelete MaxRowsToDelete 10,000 Numeric
Setting Description: Maximum rows to delete on each pass.
PRMAUDIT_CLEANUP Procedure
If the auditing feature is enabled, this procedure will physically delete records from the table based on the value of the KeepInterval setting. Refer to the following table for information about the settings associated with the PRMAUDIT_CLEANUP procedure:
PRMAUDIT_CLEANUP Settings
Setting Description: Should the procedure attempt to clean up PRMAUDIT records. Namespace Setting Name Default Setting Type database.cleanup.auditing Enabled 1 (true) Boolean
Setting Description: The oldest audit records to keep in PRMAUDIT. Namespace Setting Name database.cleanup.auditing KeepInterval
42
Database Administration Default Setting Type 30d Interval
CLEANUP_USESSAUD Procedure
This procedure deletes records from the USESSAUD table based on the KeepInterval. The remaining settings are similar to the REFRDEL_CLEANUP procedure. Refer to the following table for information about the settings associated with the CLEANUP_USESSAUD procedure:
CLEANUP_USESSAUD Settings
Setting Description: The oldest records to keep in the USESSAUD table. Namespace Setting Name Default Setting Type database.cleanup.Usessaud KeepInterval 5d Interval
Setting Description: Determines whether the procedure deletes all the REFRDEL records possible on each pass. Namespace Setting Name Default Setting Type database.cleanup.Usessaud DeleteAll 0 (false) Boolean
Setting Description: Determines whether all of the records are cleaned up. If the total record count is less than this number then all records are cleaned up. Namespace Setting Name Default Setting Type database.cleanup.Usessaud DeleteAllThreshold 1,000 Numeric
Setting Description: Percentage of records to delete on each pass. If you increase this setting, you must also increase the MaxRowsToDelete setting.
43
Manually Upgrading P6 EPPM for Microsoft SQL Server Namespace Setting Name Default Setting Type Namespace Setting Name Default Setting Type database.cleanup.Usessaud DeletePercentage 10 (%) Numeric database.cleanup.Usessaud MaxRowsToDelete 10,000 Numeric
Setting Description: Maximum rows to delete on each pass.
USER_DEFINED_BACKGROUND Procedure
This procedure is an optional customer procedure that DAMON runs. This procedure does not have settings associated with it.
Oracle Database Performance

You can modify several Oracle database settings to improve the performance of your P6 EPPM database. Run the scripts as described below after you create the database. Grant access to the V_$TRANSACTION view: V_$TRANSACTION is a system view in Oracle that lists the active transactions in the system. GET_SAFETY DATE (a procedure in the Project Management schema) accesses this view to get the oldest start time of an active transaction. If the schema owner does not have privileges to this view, then it returns a safety date using the USESSION table. V_$Transaction tunes performance during a refresh action. USESSION records the login time of the logged in user, whereas data in the V_$Transaction view is recorded at a system level. The logged in user could be logged in for more than an hour (as seen from the USESSION table), but the V_$Transaction view has the current transaction datetime, regardless of the time the user logged in. Note: Access to the V_$TRANSACTION view was built into the procedure to tune performance with refreshing operations; however, third party functions could impact performance with database refresh operations that use an older time in the V_$TRANSACTION view.
44
Database Administration To grant access to this view, connect to Oracle as SYS. Run the RUN_AS_SYS.SQL script located in the \Database\scripts\common folder of the P6 EPPM physical media or download, or run the following GRANT statement: grant select on v_$transaction to admuser; Gather statistics for cost-based optimization: Oracle 10g and later supports only cost-based optimization, which relies on accurate statistics to determine the optimal access path for a query. To gather the appropriate statistics for the optimizer, which will improve database performance, run the GATHER_STATS.SQL script located in the \Database\scripts\common folder of the P6 EPPM physical media or download.
Safe Deletes
The P6 EPPM database normally handles restoring select deleted data using a safe delete setting. While using P6 Professional, the Undo command (Edit, Undo) allows users to restore certain types of data that have been deleted. Deleted data remains in the P6 EPPM database until the CLEANUP_LOGICAL_DELETES procedure clears it (after 5 days, by default). See the P6 Professional Help for more information about using undo.
Turning Off Safe Deletes

You can turn off safe deletes to save storage space. Turning off safe deletes disables undo functionality and instantly clears deleted data from the P6 EPPM database. To turn off safe deletes: 1) Verify the current state of your safe deletes setting. In the database, if the table ADMIN_CONFIG has the following row, a CONFIG_VALUE of 'N' means turn off safe deletes. CONFIG_NAME = 'SAFEDELETE.ACTIVE' and CONFIG_TYPE = 'SETTINGS' Note: This is only loaded at startup. If you change CONFIG_VALUE while a user is running P6 Professional, the setting will not apply until the user restarts the P6 Professional session. 2) Once you have determined the current state of your safe deletes setting, run one of the following statements. To turn off safe deletes for the first time: INSERT INTO ADMIN_CONFIG (CONFIG_NAME, CONFIG_TYPE, CONFIG_VALUE) VALUES ('SAFEDELETE.ACTIVE', 'SETTINGS', 'N')
To turn on safe deletes after it has been turned off: UPDATE ADMIN_CONFIG SET CONFIG_VALUE = 'Y' WHERE CONFIG_NAME = 'SAFEDELETE.ACTIVE' AND CONFIG_TYPE = 'SETTINGS'
45
Manually Upgrading P6 EPPM for Microsoft SQL Server To turn off safe deletes after it has been turned on: UPDATE ADMIN_CONFIG SET CONFIG_VALUE = 'N' WHERE CONFIG_NAME = 'SAFEDELETE.ACTIVE' AND CONFIG_TYPE = 'SETTINGS'
Native Database Auditing

Native database auditing permits you to log the edits, additions, and deletions made by users of P6 EPPM applications. When users make changes, they create a Data Manipulation Language (DML) INSERT, UPDATE, or DELETE statement. Native database auditing uses the Data Manipulation Language (DML) INSERT, UPDATE, or DELETE statement being executed against tables in the database schema. Since every application table in the schema has its own auditing trigger, you can log changes made to each table regardless of who made the change or when the change was made. The database schema owner owns the auditing trigger: you can bypass trigger execution.
Auditing Level Configuration

You can adjust the amount of information that is logged by adjusting the audit level for each table. You can refine the audit further by setting the audit level individually for insert, updates, and deletes within each table.
Auditing Levels
Level Level 0 Level 1 Level 2 Level 3
Description No audit. Row-level audit. Audit only the operation without column details Column-level Audit without blobs. Audit changes to the data at the column level but without blob changes Full Audit. Audit changes to the data at the column level. For Microsoft SQL server, column level changes to blobs are not included.
Simple Configuration
You can use two configuration procedures to provide simple control of the auditing feature:
auditing_enable(table_name, level) auditing_disable(table_name)
46
Database Administration You can set the audit level on an individual table or the same audit level for all of the tables. However, the simple configuration procedures do not allow for setting individual auditing levels for insert, update, or delete operations within a table.
Detailed Configuration
You can configure auditing trigger behavior by changing values in the settings table that enable or disable:
The auditing feature itself The auditing of specific tables The auditing of table insert, update, or delete operations within each table
Auditing Status You can enable or disable the auditing feature by using the database.audit.Enable setting. Use the settings_write_bool procedure to enable/disable the auditing feature. Microsoft SQL Server Example: To enable the auditing feature in Microsoft SQL Server, use the following code: exec settings_write_bool 1,'database.audit','Enabled' Options Setting Each table's auditing settings are controlled by the Options setting in each table's auditing namespace (for example, database.audit.TASK). The Options setting is a three character string with a numeric value in each character position representing the audit level for insert, update, and delete.
Auditing Level Options Setting by Table Operation
Operation Insert Level 0 1 Update 0 1 Delete 0 1 Description No audit. Row-level audit. Audit only the operation without column details. Column-level audit without blobs. Audit changes to the data at the column level but without blob changes.
47
Manually Upgrading P6 EPPM for Microsoft SQL Server 3 3 3 Full Audit. Audit changes to the data at the column level. For Microsoft SQL server, column level changes to blobs are not included.
The following table provides some examplesof the options setting:

Setting the Auditing Level Options Setting by Table Operation Examples
Namespace database.audit.TASK
Setting
Value 330
Description Fully audit any insert and update operations. Do not audit any delete operations. Row-level audit on deletes only. Fully audit.
Options database.audit.PROJWBS database.audit.TASKRSRC 001 333
SETTINGS_WRITE_STRING Procedure You can change table audit settings using the settings_write_string procedure. Microsoft SQL Server Example: To set the table settings to fully audit insert and update operations but ignore any delete operations, use the following code for Microsoft SQL Server: exec settings_write_string '330','database.audit.TASK','Options' Note: Changes to auditing settings will not appear immediately in the application. The program will need to close the database connection and then reconnect to the database to get the new settings.
The Audit Table

Audit records are inserted into the PRMAUDIT table. One record is inserted into the audit table for each row changed in the database.
48
PRMAUDIT Table
Column audit_date table_name pk1, pk2, pk3, pk4 oper prm_user_name
Type Date String(30) String(255) String(1) String(32)
Description Date and time of change Table Name Primary key values for audited record I=Insert, U=Update, D=Delete P6 EPPM user name if the change was made in P6 EPPM applications Column changes up to 4000 characters (Level 2 and 3 only) Blob changes and overflow from audit_info (Level 2 and 3 only) Flag for deletes that are logical (marked) rather than a physical delete Database user name (usually privuser) Operating system user name of connected session Name of program connecting to the database Computer name of connected session Name of application connected to the database IP or MAC address of connected session
audit_info audit_info_extended
String(4000) BLOB
logical_delete_flag
String(1)
rdbms_user_name* os_user_name* program* host_name* app_name* netaddress*
String(255) String(255) String(255) String(255) String(25) String(24)
* Values will differ for depending on your database.
Note: Grant select privileges to the administrative user on V_$SESSION to ensure correct values for several auditing table values.
49
Session Auditing
Activity for the USESSION table is audited with its own trigger and table. When an application user logs out of the system they logically delete, or mark, their session record in the USESSION table. One record is written to the USESSAUD table for each logout. The format of the USESSAUD table mirrors that of the USESSION table. This audit can be enabled using the usessaud_enable procedure and disabled using the usessaud_disable procedure.
Column Audit Data

The data changes for each audit are stored in the audit_info and audit_info_extended columns. The audit_info column contains all the row changes as long as they do not exceed 4000 characters. Changes over 4000 characters or any edit to a blob will be written to the audit_info_extended BLOB column. Data in the two audit_info columns has a specific format. Each column audit within the data begins with either ":O" (old data) or ":N" (new data) to distinguish between the audit of the previous (old) or the changed (new) value (for BLOB columns the data starts with :BLOBO or :BLOBN). Directly after this is the name of the column in lowercase. Following the column name is the length of the audited value in a fixed four character field. Finally the actual data is placed in the audit record. Updates will have both an old and new value for each change. Inserts will have only a new value and deletes only an old value. The following is an example of the audit record for TASK to change the task_code from 'A1010' to 'B102:' audit_info =>:Otask_code: 5:A1010:Ntask_code: 4:B102
Installing P6 EPPM Applications

You will use the setup.exe in the Primavera P6 Enterprise Project Portfolio Management R8.2 physical media or download to install the following P6 EPPM applications: Note: You do not have to install all applications; you can pick and choose what you install. However, you must install P6 to run the other P6 EPPM applications.
P6 (and its help, tutorials, and Oracle Configuration Management (OCM)) P6 Progress Reporter (and its help) P6 Team Member (includes P6 Team Member Web, P6 Team Member for iPhone,
E-mail Statusing Service)
50
Installing P6 EPPM Applications
Notes: You will need to configure E-mail Statusing Service separately. The installation wizard will provide the E-mail Statusing Service files and you will use the config.properties file to set up this service. See the P6 EPPM Post Installation Administrator's Guide. P6 Team Member for iPhone supports SSL (https) only when it has a certificate signed by a valid authority.
P6 EPPM Web Services P6 Integration API (remote mode only)

Note: Oracle provides a separate installer for P6 Integration API local mode. See the P6 Integration API Configuration Guide. Based on whether you are installing or upgrading, see one of the following books:
Installing and Configuring P6 EPPM Upgrading and Configuring P6 EPPM
51

Manually Upgrading p6 Eppm For Microsoft SQL Server Database

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Manually Upgrading p6 Eppm For Microsoft SQL Server Database

Hochgeladen von

Copyright:

Verfügbare Formate

Manually Upgrading P6 EPPM for Microsoft SQL Server Release 8.

Where to Get Documentation

Manually Upgrading P6 EPPM for Microsoft SQL Server

P6 EPPM Installation and Configuration Guide

P6 EPPM Installation and Manual Configuration Guide

P6 EPPM Post Installation Administrator's Guide

P6 EPPM User's Guide

P6 Data Dictionary P6 Team Member User's Guide

P6 Progress Reporter Administrator Help

P6 Progress Reporter Help

Manually Upgrading P6 EPPM for Microsoft SQL Server

Primavera Timescaled Logic Diagram Help

P3 to P6 EPPM Migration Guide

Where To Get Training

Where to Get Support

Overview of Manually Upgrading a P6 Database to P6 EPPM R8.2

Database Upgrade Considerations for P6 EPPM

Requirements to Manually Upgrade R8.0 or Later to R8.2

Requirements to Manually Upgrade from Version 7.0 or Earlier to R8.2

Manually Upgrading P6 EPPM for Microsoft SQL Server

Tips to Consider When Manually Upgrading to P6 EPPM R8.2

Database Upgrade Considerations for P6 EPPM Security Tips

To prevent duplicate values in P6 EPPM modules appearing due to leading or trailing

Data that is Not Migrated during the P6 EPPM Database Upgrade

Manually Upgrading P6 EPPM for Microsoft SQL Server

Converting Methodologies to Projects

Upgrading the P6 EPPM Microsoft SQL Server Database

Post-Upgrade Procedures 17) Go to scripts\source\PM_08_02_00 and execute the sspm_px_rpt_src.sql script.

Creating a Project Template From Projects

Requirements After the Upgrade from P6 EPPM R8 or later to P6 EPPM R8.2

Manually Upgrading P6 EPPM for Microsoft SQL Server

Oracle recommends you make a backup of your newly upgraded database.

Application Configuration Procedures

Requirements After the Upgrade from 7.0 or Earlier to P6 EPPM R8.2

Application Configuration Procedures

Manually Upgrading P6 EPPM for Microsoft SQL Server

Private Database Logins for P6 EPPM

Resetting Private Database Passwords to Use the New Encryption Algorithm

Modifying Private Database Logins for P6 EPPM

Background Processes and Clean Up in P6 EPPM

Manually Upgrading P6 EPPM for Microsoft SQL Server

PX Tables Clean Up Procedure

RDBMS Scheduler Configuration

Database Settings Table

30d 2h 10m 30s

Date. The date data type consists of dates.

Namespace: database.cleanup.Usession Setting Name: ExpiredSessionTimeout Value: 2h (two hour interval)

Manually Upgrading P6 EPPM for Microsoft SQL Server

Reading Setting Values

SETTINGS_READ_STRING(ret_val,namespace,settings_name,default) SETTINGS_READ_DATE(ret_val,namespace,settings_name,default) SETTINGS_READ_NUMBER(ret_val,namespace,settings_name,default) SETTINGS_READ_BOOL(ret_val,namespace,settings_name,default)

Using Code to Read Setting Values for Microsoft SQL Server

Writing Setting Values

Using Code to Write Setting Values for Microsoft SQL Server

Database Administration exec SETTINGS_WRITE_STRING '12h','database.cleanup.Usession', 'ExpiredSessionTimeout'

Tracking Background Job Execution

High Level Status Settings

Namespace Setting Name Default Setting

database.background.Symon HeartBeatTime N/A

Last date and time background job DAMON ran.

Namespace Setting Name Default Setting

database.background.Damon HeartBeatTime N/A

The BGPLOG Table

Manually Upgrading P6 EPPM for Microsoft SQL Server