Three passes in the Upgrade process.jpg

 

     Three passes in the Upgrade process. Test Move to Production is in the middle.  For more information, see Getting Ready for your PeopleSoft Upgrade

     on the PeopleSoft PeopleTools 8.56 Upgrade Home Page (Doc ID 2270700.1).

 

The Test Move to Production Pass

 

Application upgrades consist of 3 different passes:  the Initial Pass, and the Test Move to Production Pass (MTP), and the Final Move to Production pass.  A good big-picture explanation of the Test Move to Production Pass 

is located in the upgrade documentation in section "Understanding the Test Move to Production Passes":

 

The Test Move to Production pass is a different series of steps (from the initial upgrade pass).  It

includes a subset of the previous tasks, and takes advantage of the tasks performed during the first upgrade pass.

 

You should perform as many Test Move to Production passes as necessary to work out any issues and to be

comfortable with the process. During each Test Move to Production pass you will be able to refine the process so

that you can save time and avoid manual processes. These test passes will also let you know how long the process

takes so that you can plan your production downtime for your Move to Production weekend.

 

The steps executed in the MTP pass vary (from the initial upgrade pass) in several ways. Many of the tasks and steps

in the initial test pass will be replaced in the MTP pass with PeopleSoft Data Mover export and import scripts.

 

In the initial pass, some steps required you to make functional decisions and take time to manually set up data. That

data can be copied from the first database to the next, saving you setup time and eliminating the chance for manual

error or typos.

 

The MTP pass does not repeat the database compare/copy steps. You made the decisions once; there is no

need to repeat these steps. Instead, a PeopleSoft Data Mover script, MVPRDEXP, will export all of the tables that

contain the PeopleSoft PeopleTools objects like records and PeopleCode from the first database. Another

PeopleSoft Data Mover script, MVPRDIMP, will import those tables into the second database.

 

Anything you have done to PeopleSoft PeopleTools objects while executing or testing the first pass

   -copied objects from the Demo database

   -reapplied customizations

   -applied updates from the My Oracle Support website

 

will be moved to the second Copy of Production with these scripts.

 

Another important difference in the MTP pass is the handling of SQL scripts that create and alter tables. In the

initial pass, you generate and sometimes edit, then execute the SQL scripts. In the MTP pass, you may be able to

skip the generation steps and use the SQL that you previously generated. This is another way to save time in your

critical go-live window.

 

What are commonly asked questions regarding the Move to Production Pass?

 

Why do the MTP pass anyway?

 

Q: If the Source database requires an initial environment that is up to date,  then what is the advantage of doing a

move-to-production run?  This can only add to the amount of time to perform the upgrade.  Plus, the initial pass

does not seem as efficient to do, as a move-to-production pass.  One issue is that it seems that the Users are taken from the Source

rather that the Target.     

 

A: The Initial Pass includes tasks for the Upgrade compare and copy (you make decisions here); and a task to set aside customizations to be preserved.  The MTP does not include these tasks.  Regarding the users from Source...see next...

  

Production Changes to Psoprdefn are lost

 

Q: In the different MTPs in an upgrade, the PSOPRDEFN table is copied from Source to Target through data mover export

and import scripts (Mvprdexp.dms and Mvprdimp.dms). This procedure does not take into consideration any new values that might be in the Target environment -- because it data-replaces the table. This means that new users (i.e. new rows in PSOPRDEFN table) in the live production environment will be lost from the final move to production. Is this the expected behavior?

 

A:  Yes. The upgrade requests that you "freeze changes to production" during the course of the MTP upgrade pass.

To workaround this design see  E-UPG PT8.2x, PT8.4x, PT8.5x: How to Preserve Security through Upgrade Passes (Doc ID 642944.1).  

 

Why do the PeopleTools Upgrade in MTP?

 

Q: We are currently in the process of upgrading PeopleSoft to version 9.2. When we create a 'move to production' pass

in the Change Assistant,  a PeopleTools upgrade job is created as well. Since the application upgrade contains a step

to export and import all PeopleTools tables (Task 4-1-3: Exporting PeopleTools System Tables and Task 4-1-4:

Importing PeopleTools System Tables) can this PeopleTools upgrade be skipped?

 

A:  Go back and review the tasks in the PTools Upgrade.  You will see that they are more than just an export-import.  

 

Upgrade passes and Preserving customizations

  

Q: When applying updates, you need to select a Pass type.  What is the correct pass type to select?

 

A: Please review E-PUM How to Create a Change Package Incorporating Customizations with PeopleSoft Update Manager (PUM) (Doc ID 1566344.1).

 

Additional patches, upgrading PeopleTools, applying a Tools patch

 

Q:  When are the required-for-upgrade patches to be applied?  Is it one-and-done?

A: These are most usually applied to the Source environment as the upgrade begins.  But that’s just one time to apply them;  it is

important to frequently search for and apply the Required at Upgrade fixes for your particular application.  For more information,

See the PUM Home Page (Doc id 1641843.2) > tab Install and Upgrade > Required at Upgrade patches.  This section has instructions for applying the required at upgrade patches during the different stages of the upgrade:  beginning of the upgrade; before data conversion;  and between upgrade passes.

 

Q:  Can we upgrade PeopleTools between upgrade passes? Or, what about tools patches?

A: Oracle does not support Tools upgrades between upgrade passes.  The Upgrade Templates are written for a specific application release and PeopleTools target release.  This is found in each Upgrade Home Page’s section Upgrade Certification Path.  You are free to apply a PeopleTools patch between upgrade passes, but it is rarely required to do so. 

 

Change Assistant should point to the correct database

 

Q: We are upgrading from PeopleSoft 9.1 to 9.2, PeopleTools 8.52 to 8.55.

For the Move to Production pass, 2 jobs were created “softwareupdate.PeopleTools_Only_Upgrade.{HCM92DEV-HCM92QA}MTP”

and “UPG.HCM91TO92UPG.{HCM92DEV-HCM92QA}MTP”. The PeopleTools only upgrade ran successfully but the second job, (the HCM application upgrade) kept failing at the non-manual steps.

Step “Running the Application Filter” failed because “Change Assistant Failure: Filter Query steps are not supported

for 8.52 and lower databases.”  and  Step “Applying the UPGOPT Project” failed because “System Error : The database is at release 8.55.  The PeopleTools being run require databases at release 8.52.”

How should this be resolved?

 

A: When creating the new Change Assistant Upgrade job for the Test Move to Production pass, take care to specify the correct databases for Source and Target.

You will need to create a new PeopleSoft Change Assistant job for each test Move to Production pass.

 

 

KM references

 

E-UPG PT8.2x, PT8.4x, PT8.5x: How to Preserve Security through Upgrade Passes (Doc ID 642944.1).

E-PUM How to Create a Change Package Incorporating Customizations with PeopleSoft Update Manager (PUM) (Doc ID

  1. 1566344.1).

E-UPG: Applying Additional Maintenance in the Upgrade Passes (Not Required For Upgrade) (Doc ID 1280840.1)

HCM Upgrade: How to Preserve Queries and Tree Objects (Doc ID 2153527.1)

PUM Home Page (Doc ID 1641843.2)

E-UPG Understanding the Upgrade Certification Path section of an Upgrade Home Page (Doc ID 1970917.1)