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.3:
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.3. For example, if you are on version 5.0, you will need to upgrade to 7.0 before you can upgrade to R8.3.
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 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.
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.3, 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.3.
If you are a current jBPM user and upgrade to P6 EPPM R8.3, workflows and reviews data will not be available. You should close all workflows and reviews that are in progress before upgrading to P6 EPPM 8.3. You cannot migrate any of this data to 8.3.
