Applying Downloaded PeopleSoft Release Patchset to PeopleSoft Image

The PeopleSoft Update Image will be available on a regular schedule and is the source of all updates to your application, however there may be times when a critical fix is necessary and you can not wait for the next PeopleSoft Image. When this circumstance occurs, it will be necessary to download the PeopleSoft Release Patch from My Oracle Support (MOS).

You will apply the PRP to the current PeopleSoft Image so that you can continue to take advantage of the powerful PeopleSoft Update Manager PIA application to generate a custom change package including requisite updates that may have already been posted. The PRP change package includes the metadata required to keep your current PeopleSoft Image up to date. Every PRP will be included in the next scheduled release of the PeopleSoft Image which is cumulative of all updates.

Important! The pi_home directory requires read and write access to apply PeopleSoft Release Patchsets (PRPs). To apply PeopleSoft Release Patchsets (PRPs), use the instructions in the PeopleSoft Deployment Packages for Update Images Installation (PeopleSoft PeopleTools 8.55), “Using and Maintaining the PeopleSoft Environment”, Changing the Access for PI_HOME to change the access to read/write and disable guest login.

Warning! Because PRPs are created for specific PIs, the PRP can only be applied to the specific PI for which it was created. Change Assistant will not allow you to apply a PRP directly to your PeopleSoft environment.

To download and apply an individual fix:

  1. Discover and download the PRP from MOS.

  2. Use Change Assistant to apply the PRP to the PeopleSoft Image database.

  3. Create a new custom change package definition using Define Change Package option in the Update Manager Action.

    See Defining a New Change Package

  4. Apply the new custom change package the same as any other update from the PeopleSoft Image.

    See Applying Change Package

Before you download the change package for the PRP, make sure that you have set up a download directory on your local machine.

To discover and download the PRP:

  1. Create a download directory on your local machine.

  2. Log onto My Oracle Support and Select the Patch and Updates tab.

  3. Search for PeopleSoft Release Patchsets (PRP) by Bug Number, Product, or Product Family.

  4. Search for PRPs.

    Use the Patches and Updates tab in My Oracle Support to search for PRPs. PRPs have a classification of Critical.

  5. Open the fix details to review the fix.

  6. From the Patch Details page, click Download.

  7. Select the Include Prerequisites checkbox to list all the prerequisite change packages.

  8. In the file download window, click on the change package name and select Save.

  9. Select your download directory.

To apply the PRP to the PeopleSoft Image:

  1. In Change Assistant, select Tools > Change Actions.

    Note: If you are already in the Update Manager Action, select Tools, Apply Downloaded PeopleSoft Release Patchset to PeopleSoft Image then go to step 4.

  2. Select Update Manager and click Next.

  3. Select Apply Downloaded PeopleSoft Release Patchset to PeopleSoft Image and click Finish.

  4. Select the download directory where you downloaded the PRP change package and click Next.

  5. Select the PRP change package or packages from the list displayed and click Next.

  6. Change Assistant will verify that the package is compatible with the PI version. If it is not compatible, you will receive a message to Cancel.

  7. The Change Assistant job will start running.

Note: Use the instructions in the PeopleSoft Deployment Packages for (PeopleSoft PeopleTools 8.55) , “Using and Maintaining the PeopleSoft Environment”, Changing the Access for PI_HOME to change the access to read/write and disable guest login for the pi_home share.

After the PRP has been applied to the PeopleSoft Image database, it is now available for you to apply to your target environments using the Update Manager action. Apply the PRP as you would any other update.

See Defining a New Change Package