Manually Upgrading the P6 Professional Database for Microsoft SQL

Server
Release 8.3

March 2013

Legal Notices
Oracle Primavera Manually Upgrading the P6 Professional Database 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.
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.
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.

Legal Notices
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.

Contents
Legal Notices .................................................................................................................................... 2
Preface.............................................................................................................................................. 7
Where to Get Documentation ........................................................................................................... 7
Where to Get Training ....................................................................................................................... 9
Where to Get Support ....................................................................................................................... 9
Overview of Manually Upgrading a P6 Professional Database to P6 Professional R8.3 ................ 11
Database Upgrade Considerations for P6 Professional ................................................................. 13
Manual Database Upgrade Process ............................................................................................... 13
Convert Methodologies to Projects ................................................................................................ 13
Risks Migration ................................................................................................................................ 14
Run the Microsoft SQL Server Database Upgrade Scripts for the P6 Professional Database ....... 17
Private Database Logins for P6 Professional ................................................................................. 18
Resetting Private Database Passwords to Use the New Encryption Algorithm ........................... 18

Preface
In This Section
Where to Get Documentation.................................................................................. 7
Where to Get Training ................................................................................................ 9
Where to Get Support ................................................................................................ 9

Where to Get Documentation

For the most up-to-date versions of all manuals and technical documents related to
installing, administering, and using P6 Professional, go to:
http://download.oracle.com/docs/cd/E35157_01/index.htm.
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 Professional Documentation
Center, located in the \Documentation\Documentation_library\language folder of the
P6 Professional physical media or download.
The following table lists the core documents available for the release, and identifies
recommended readers by role. P6 Professional roles are described in the P6 Professional
Administrator's Guide. Other, more technical documents are available on the media
pack and OTN site, but are not listed below.
Title

Description

What's New in P6
Professional

Highlights the new and enhanced features included in

this release.
You can also use the P6 Professional Cumulative
Feature Overview Tool to identify the features that have
been added since a specific release level.
All users should read this guide.

P6 Professional
Administrators Guide

Explains how to set up the P6 Professional database,

servers, and components; it also provides an overview
of all the components in the P6 Professional solution. The
guide describes the procedures required to administer
P6 Professional, including setting up security and
configuring global preferences.
The P6 Professional
network administrator/database administrator should
read this guide.

Manually Upgrading the P6 Professional Database for Microsoft SQL Server

Title

Description

Tested Configurations

Lists the configurations that have been tested and

verified to work with P6 Professional. The network
administrator/database administrator and P6
Professional administrator should read this document.

P6 Professional
Explains how to install and configure P6 Professional as a
Standalone Installation standalone application.
and Configuration
All administrators should read this guide.
Guide
P6 Professional Help

Explains how to use P6 Professional 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.

P6 Professional User's
Guide

This guide explains how to plan, set up, and manage

projects in a multiuser environment. If you are new to P6
Professional, 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 Professional
Help. The program manager, project manager,
resource/cost manager, and team leader should read
this guide.

P6 Visualizer Help

Describes how to create, modify, and manage

Timescaled Logic Diagrams and Gantt charts.
All users should read this Help.

P6 Professional SDK
Help

Describes how to use the P6 Professional SDK to connect

to the P6 Professional database. Describes the tables,
fields, and stored procedures that you can access
through the P6 Professional SDK. Provides examples
that show how you can use the P6 Professional SDK to
perform several basic tasks, such as creating a new
project or assigning a resource to a project activity. The
P6 Professional network administrator/database
administrator should read this documentation, which is
available in local drive\Program
Files\Oracle\Primavera P6 Professional\PMSDK\Doc\
by default.
Double-click the p6_pro_sdk.chm file to open the help
file.

Preface

Title

Description

P3 to P6 Professional
Migration Guide

This guide provides best practices for migrating your P3

data to P6 Professional, and details how P3 functionality
maps to P6 Professional functionality.
All administrators should read this 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

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.
Using Primavera's Support Resource Centers
Primaveras Support Resource Center provides links to important support and product
information. Primavera's Product Information Centers (PICs) organize documents found
on My Oracle Support (MOS), providing quick access to product and version specific
information such as important knowledge documents, Release Value Propositions, and
Oracle University training. PICs also offer documentation on Lifetime Management, from
planning to installs, upgrades, and maintenance.
Visit https://support.oracle.com/epmos/faces/DocumentDisplay?id=1486951.1 to
access links to all of the current PICs.
PICs also provide access to:

Communities are moderated by Oracle providing a place for collaboration among

industry peers to share best practices.
News from our development and strategy groups.

Manually Upgrading the P6 Professional Database for Microsoft SQL Server

Education contains a list of available Primavera product trainings through Oracle

University. The Oracle Advisor Webcast program brings interactive expertise straight
to the desktop using Oracle Web Conferencing technology. This capability brings you
and Oracle experts together to access information about support services, products,
technologies, best practices, and more.
For more information about working with Support, visit
https://support.oracle.com/epmos/faces/DocumentDisplay?id=888813.2.

10

Overview of Manually Upgrading a P6 Professional

Database to P6 Professional R8.3
To manually convert your P6 Professional version 6.2.1, 7.0, 8.1 or 8.2 database to P6
Professional R8.3, follow the procedures described in this document. These procedures
should be performed by an experienced database administrator. You should complete
these processes in the order specified:

Back up the existing P6 Professional database (also known as PMDB).

If you are upgrading from Version 7.0 or earlier, migrate all your methodologies. Use

Project Architect in the Project Management module (version 7.0 or earlier) to

convert the data from a methodology to a project. (See Convert Methodologies to
Projects (on page 13).)
Run the appropriate scripts to upgrade the database structure to P6 Professional R8.3.
Oracle recommends that you use SQL Plus to run scripts referenced in the following
instructions.

11

Database Upgrade Considerations for P6 Professional

You can upgrade your existing P6 Professional database (version 6.2.1 and later) to P6
Professional R8.3. You must upgrade your P6 Professional database so it will work with the
new version.

Manual Database Upgrade Process

You can upgrade your existing P6 Professional database (version v6.2.1, v7, R8.1,or R8.2)
to P6 Professional R8.3. You must upgrade your P6 Professional database so it will work
with the new version. Use the scripts provided to upgrade your database.
All risk data fields are migrated when upgrading from a version earlier than P6
Professional R8.1; existing fields are mapped to new fields. See Risks Migration (on page
14) for more information.

Convert Methodologies to Projects

To migrate Methodology Management version 7.0 or earlier data to P6 Professional R8.3
projects, use Project Architect in the Project Management module (version 7.0 or earlier)
to convert the data from a methodology to a project.
Note: You can create only one project at a time. If you want all of
your Methodology Management data moved to projects, contact
Oracle Consulting to automate the process.
To convert Methodology Management data to a project:
1) Create a new EPS node in Project Management where you can store all your
Methodology Management projects.
2) Use Project Architect in Project Management 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.
3) After you have converted all your Methodology Management data to projects,
upgrade P6 Professional.

13

Manually Upgrading the P6 Professional Database for Microsoft SQL Server

Risks Migration
This topic applies only if you are upgrading from a version earlier than P6 Professional
R8.2. The following table illustrates the risks data field mapping when upgrading from P6
Professional database (version 6.2.1 through 7.0 SP3) to P6 Professional R8.3.
Note: Some fields will migrate to text fields instead new fields
because certain fields no longer correspond. The new text fields
are noted below.
Risks Fields Migration Table
Name

P6 Professional database
(version 6.2.1 through 7.0
SP3) Risks Fields

P6 Professional R8.3 Risks Field

Risk ID

risk_id

risk_id

risk_id

risk_code (PROJRISK appended with

risk_id)

Risk Name

risk_name

risk_name

Risk
Description

risk_descr

risk_desc

Risk Status

status_code

status_code
Open= Open; Closed=Managed
(closed)

Risk Category
ID

risk_type_id

risk_type_id

Risk Control

risk_control

cause (with 'Risk Control' heading)

Risk UDFs

table_name

table_name

Applies to WBS wbs_id

cause (with 'Applies to WBS' <WBS

name> heading)

Applies to
Resource

rsrc_id

rsrc_id

Responsible
Manager

obs_id

cause (with 'Responsible Manager'

<OBS name> heading)

Priority

priority_type

cause (with 'Priority' <priority_type>

heading)

Project ID

proj_id

proj_id

Date
Identified

add_date

add_date

14

Manual Database Upgrade Process

Name

P6 Professional database
(version 6.2.1 through 7.0
SP3) Risks Fields

P6 Professional R8.3 Risks Field

Impact Date

impact_date

cause (with 'Impact Date'

<add_date in mmm-dd-yyyy format
> heading)

Probability

prbly_pct

cause (with 'Probability' <prbly_pct>

heading)

Impact Labor Units

impact_work_qty

cause (with 'Impact - Labor Units'

<impact_work_qty> - 2 decimals
heading)

Impact impact_equip_qty
Nonlabor Units

cause (with 'Impact - Nonlabor Units'

<impact_equip_qty> - 2 decimals
heading)

Impact Material Units

impact_mat_qty

cause (with 'Impact - Material Units'

<impact_mat_qty> - 2 decimals
heading)

Impact Expenses

Impact_expense_cost

cause (with 'Impact - Expenses'

<impact_expense_cost> - 2
decimals heading)

Risk Control

risk_control

cause (with 'Risk

Control'<risk_control> heading)

Risk Category

risk_type

risk_type

Risk Category seq_num

Sequence ID

seq_num

15

Run the Microsoft SQL Server Database Upgrade

Scripts for the P6 Professional Database
To update your database:
1) Copy the "scripts" folder to a local drive. The folder can be found in the Database
directory of the P6 Professional physical media or download.
Note: You need to execute all the scripts included in this section
against PMDB to upgrade.
2) Open Microsoft SQL Server Management Studio and log in as the SA user.
3) Go to scripts\common and execute the ss_disable_triggers.sql script.
4) Go to \scripts\upgrade\PPM_08_03_00 on your local drive. Execute one of the
following scripts:
SSPPM_p62.sql, if upgrading from P6 version 6.2.1
SSPPM_p621sp1.sql, if upgrading from P6 version 6.2.1 service pack 1
SSPPM_p70sp1.sql, if upgrading from P6 version 7.0 and 7.0 service pack 1
SSPPM_p70sp3.sql, if upgrading from P6 version 7.0 service pack 3
SSPPM_p81.sql, if upgrading from P6 version 8.1
SSPPM_p82.sql, if upgrading from P6 version 8.2
5) Go to \scripts\common and execute the ss_post_upgrade script.
6) Go to \scripts\upgrade\PPM_08_03_00 and execute the ssppm_grants.sql script.
Note: If you changed the default user names, you must update the
privuser and pubuser names in this script with your custom user
names.
7) Go to \scripts\upgrade\PPM_08_03_00 and execute the ssppm_synonyms.sql script.
Caution: The ssppm_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 and pubuser names in this script with your custom user
names.
8) Go to \scripts\source\PPM_08_03_00 and execute the ssppm_src.plb script.
Notes:

17

Manually Upgrading the P6 Professional Database for Microsoft SQL Server

If you changed the default privuser name, you must update the
ssppm_src.plb script with your custom privuser name.
Do not use special characters in the database name,
privileged user, or public user name, for example: { } [ ] : ; < > , . ?
!@#$%^&*()-_|/\~`

9) Go to \scripts\install\PPM_08_03_00 and execute the ssppm_database_version.sql

and ssppm_querylib.sql scripts.
10) Go to \scripts\common and execute the ss_enable_constraints_triggers.sql script.
11) Run the databaselogins.bat (on Windows) or databaselogins.sh (on Unix) to upgrade
the encryption of privilege user passwords. (See Private Database Logins for P6
Professional (on page 18) for more information.)

Private Database Logins for P6 Professional

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
Professional database is a private database login. You can add, modify, or delete
existing logins using the Database Logins tool. This can also be accomplished using the
Administration Configuration tool.
P6 Professional R8.3 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 18) for instructions. If
you automatically configure your database, you do not need to configure the
encryption algorithm.
User logins and passwords are not affected.

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 P6 Professional R8.3 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.

18

Private Database Logins for P6 Professional

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.

19