Step to Apply RFU patches and perform Peopletools upgrade and Application Upgrade

1) To apply RFU patches on Source database(Here Source database is LFSDMO1D)

2) To perform Peopletools upgrade from PT 8.53.28 to PT 8.58.23 .
3) To perform application upgrade from FSCM 9.1 to FSCM 9.2( with Source image 26).

RFU packages

Key points about RFU packages:

When you do an application upgrade, you need the latest PUM image to get the RFU from to apply to
the New Release Demo (NRD). Once the RFU is applied to NRD, when you perform the initial-pass, the
source is the New Release Demo that has been updated with the RFU and the target is your Copy-of-
Production. Therefore, the PUM source is needed only for to obtain the RFU and not during the actual
upgrade where the source is the NRD.

In a PeopleSoft upgrade package, you should apply the RFU (Required for Upgrade) package at the very
end of the upgrade process, after all other application changes have been made; essentially, it's the final
step in the upgrade to ensure all necessary database and configuration changes are applied that are
specifically required for the new PeopleSoft version.

Purpose:

RFU packages contain critical database updates and configuration changes that are mandatory for a
successful upgrade to the new PeopleSoft release.

Application:

Apply the RFU package only once you have completed all other application customizations and changes
within your upgrade package.

Change Assistant:

Most RFU changes are automatically generated by the Change Assistant tool, minimizing manual
intervention.

Below are the steps to apply the RFU package

a) Upload Source , target database to PUM source.

b) Create chage package to create RFU package for Source database (LFSDMO1D)
c) Navigate to PeopleTools -> Lifecycle Tools -> Upgrade Package ->

I. Select target Database (LFSDMO1D)

II. GO to Define Change Package and give package name .
III. And select application upgrades to 9.2 from 9.1 to 9.20 Image 26 from PT858, under App
upgrade options and chack Include Required fro Upgrade Fixes in package check box and
click next.
IV. Verify the upgrade path.
V. Review the change package.
VI. Both the application upgrade package and RFU are generated.
d) Create change package in change assistant which will create a change package in download
directory.
e) Apply the RFU updates on you Source database.
Errors Faced While applying RFU:

Generated Create index script from application designer and ran the same in DB.

CREATE UNIQUE iNDEX PS_PTIAMMCPKGAPPDT ON PS_PTIAMMCPKGAPPDT

(PTIASPPKGNAME,

PTIASPPKGGUID) TABLESPACE PSINDEX STORAGE (INITIAL 40000 NEXT

100000 MAXEXTENTS UNLIMITED PCTINCREASE 0) PCTFREE 10 PARALLEL

NOLOGGING

ALTER INDEX PS_PTIAMMCPKGAPPDT NOPARALLEL LOGGING

/

f) To Verify the RFU applied on DB.

Performing Peopletools Upgrade:

a) Create change package in change assistant which will create a change package for upgrade PKG
which we created above in PUM Source in download directory.
b. Next, create your upgrade job. Select Tools, Upgrade Application.
The Change Package Wizard will guide you through creating the upgrade job.
c. On the Change Package Settings page, select the download directory where you created the Upgrade
Package,
select the apply type and click Next.

d. On the Select Upgrade Target Database page, select the target database (Copy of Production
database) to
upgrade and click Next.
e. On the Select Upgrade Source Database page, select the source database and click Next.
f. On the Select Application Upgrade page, select the packages to apply and click Next.
g. Change Assistant will check the compatibility and display the status.

Faced below error, for this followed below oracle doc.

ERROR
-----------------------
"Error. No PTU Package is selected. Please define the new PS_HOME or target
environment and select one equivalent PTU package to apply!"

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Configure Change Assistant to perform the Tools and Application upgrade

SOLUTION

Please apply the solution steps below:

1. Download the zip file updPTU855.zip from the "Note 2070772.1 -

PeopleSoft PeopleTools 8.55 Upgrade Home Page"
2. Place this file into the download directory specified in Change Assistant

3. Re-test

h. Here we can select ignore warnings as we have already applied the RFU patches and proceed next.
Note :

Prior to PeopleSoft PeopleTools 8.55, two types of upgrade templates were delivered: • A
combined upgrade template that included both the PeopleSoft PeopleTools and application
upgrade steps. • An application-only upgrade template that was optimized to eliminate steps
relating to the PeopleSoft PeopleTools upgrade. As of PeopleSoft PeopleTools 8.55, if your
PeopleTools release needs to change during the application upgrade, Change Assistant will
sequentially run a PeopleTools-only upgrade job and then an application-only upgrade job to
upgrade both your PeopleSoft PeopleTools and application release levels. This applies for all
passes of your upgrade; Initial, Move to Production, and Final Move to Production.
i. Here change assistant will create 3 change packages and ss proceed next.

I. PeopleTools Upgrade Job

II. Application Upgrade Job
j. Verify the Source and target details and proceed next.
k. PT858 for Peopletools upgrade job will be loading .
Errors faces with Solution:

a) Manual Step:
D:\ps_home_853\utility>PSORADataTypesConversion.bat 10 SYSADM Summer24 LFSUAT1U c:⇒D:\
Upgrade\Output\softwareupdatePTU858{LFSDMO1D-LFSUAT1U}IP20241119121240 12

D:\ps_home_853\utility>rem
***************************************************************

D:\ps_home_853\utility>rem This software and related documentation are provided under a

D:\ps_home_853\utility>rem license agreement containing restrictions on use and

D:\ps_home_853\utility>rem disclosure and are protected by intellectual property

D:\ps_home_853\utility>rem laws. Except as expressly permitted in your license agreement

D:\ps_home_853\utility>rem or allowed by law, you may not use, copy, reproduce,

D:\ps_home_853\utility>rem translate, broadcast, modify, license, transmit, distribute,

D:\ps_home_853\utility>rem exhibit, perform, publish or display any part, in any form or

D:\ps_home_853\utility>rem by any means. Reverse engineering, disassembly, or

D:\ps_home_853\utility>rem decompilation of this software, unless required by law for

D:\ps_home_853\utility>rem interoperability, is prohibited.

D:\ps_home_853\utility>rem The information contained herein is subject to change without

D:\ps_home_853\utility>rem notice and is not warranted to be error-free. If you find any

D:\ps_home_853\utility>rem errors, please report them to us in writing.

D:\ps_home_853\utility>rem

D:\ps_home_853\utility>rem Copyright (C) 1988, 2012, Oracle and/or its affiliates.

D:\ps_home_853\utility>rem All Rights Reserved.

D:\ps_home_853\utility>rem
***************************************************************

D:\ps_home_853\utility>rem

D:\ps_home_853\utility>echo off
******************************************************************
******************************************************************
*

Executing Conversion Script Generation Program

*
java version "1.7.0_02"
Java(TM) SE Runtime Environment (build 1.7.0_02-b13)
Java HotSpot(TM) Client VM (build 22.0-b10, mixed mode)

The logfile cannot be written to. Check the c:\Users\_KKeerthipati\?D:\Upgrade\Output\

softwareupdatePTU858{LFSDMO1D-LFSUAT1U}IP20241119121240\ directory exists and is writable.
*

Conversion Script Generation completed

D:\ps_home_853\utility>
D:\ps_home_853\utility>PSORADataTypesConversion.bat 10 SYSADM Summer24 LFSUAT1U D:\
Upgrade\Output\softwareupdatePTU858{LFSDMO1D-LFSUAT1U}IP20241119121240 12

D:\ps_home_853\utility>rem
***************************************************************

D:\ps_home_853\utility>rem This software and related documentation are provided under a

D:\ps_home_853\utility>rem license agreement containing restrictions on use and

D:\ps_home_853\utility>rem disclosure and are protected by intellectual property

D:\ps_home_853\utility>rem laws. Except as expressly permitted in your license agreement

D:\ps_home_853\utility>rem or allowed by law, you may not use, copy, reproduce,

D:\ps_home_853\utility>rem translate, broadcast, modify, license, transmit, distribute,

D:\ps_home_853\utility>rem exhibit, perform, publish or display any part, in any form or

D:\ps_home_853\utility>rem by any means. Reverse engineering, disassembly, or

D:\ps_home_853\utility>rem decompilation of this software, unless required by law for

D:\ps_home_853\utility>rem interoperability, is prohibited.

D:\ps_home_853\utility>rem The information contained herein is subject to change without

D:\ps_home_853\utility>rem notice and is not warranted to be error-free. If you find any

D:\ps_home_853\utility>rem errors, please report them to us in writing.

D:\ps_home_853\utility>rem

D:\ps_home_853\utility>rem Copyright (C) 1988, 2012, Oracle and/or its affiliates.

D:\ps_home_853\utility>rem All Rights Reserved.

D:\ps_home_853\utility>rem
***************************************************************

D:\ps_home_853\utility>rem

D:\ps_home_853\utility>echo off
******************************************************************
******************************************************************
*

Executing Conversion Script Generation Program

*
java version "1.7.0_02"
Java(TM) SE Runtime Environment (build 1.7.0_02-b13)
Java HotSpot(TM) Client VM (build 22.0-b10, mixed mode)

Thu Nov 21 10:56:12 EST 2024: PsOraCnv execution starting

Exception in thread "main" java.lang.NoClassDefFoundError: oracle/jdbc/pool/OracleDataSource
at PsOraCnv.makeConnection(PsOraCnv.java:869)
at PsOraCnv.main(PsOraCnv.java:221)
Caused by: java.lang.ClassNotFoundException: oracle.jdbc.pool.OracleDataSource
at java.net.URLClassLoader$1.run(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
... 2 more
*

Conversion Script Generation completed

D:\ps_home_853\utility>
ss
E-UPG: PeopleTools Only Upgrade - Running The Step Generating Oracle
Conversion Scripts Failed With "Exception in thread "main"
java.lang.NoClassDefFoundError: oracle/jdbc/pool/OracleDataSource" (Doc ID
2522331.1)
SOLUTION

The "PeopleTools Upgrade" user’s guide (found on your Upgrade Home Page) states this task should not be
executed if you have an application database.

From the Task "Understanding Converting Database Data Types":

If you are using a PeopleSoft application database (for example, HCM, FSCM, CRM, or ELM), you should not run this
conversion as part of the PeopleTools only upgrade.
Do not run this task unnecessarily.

Mark all the steps for the task "Converting Database Data Types" as complete and Move to next task.

b) Below error in this step.

Go to D:\Upgrade\Staging\softwareupdatePTU858{LFSDMO1D-
LFSUAT1U}IP20241119121240

And modify below script .

Search below and correct the alignment by adding ) at the end of this script.

c) Skipped this step as raised ticket(RITM7000767) with DBA team to

execute

d) skipped below step as DBA team confirmed its present.

 d) Below step started at 9.20 AM to 1 : 00 PM

e) Below error in this step.

SQL Build process began on 12/4/2024 at 1:09:20 PM for database LFSUAT1U.

Error: PV_VER_LANG_VW - SQL Error. Error Position: 109 Return: 904 - ORA-00904:
"A"."VERITY_LOCALE": invalid identifier

CREATE VIEW PS_PV_VER_LANG_VW (LANGUAGE_CD, VERITY_LOCALE, VERITY_VALS, INDEXNAME) AS

SELECT A.LANGUAGE_CD , A.VERITY_LOCALE , B.LANGUAGE_MAP , B.INDEXNAME FROM PSLANGUAGES
A , PSSIDXLANGUAGE B WHERE A.LANGUAGE_CD = B.LANGUAGE_CD AND A.INSTALLED = 1

SQL Build process ended on 12/4/2024 at 1:19:55 PM.

1224 records processed, 1 errors, 0 warnings.
SQL Build script for all processes written to file D:/Upgrade/Output/softwareupdatePTU858{LFSDMO1D-
LFSUAT1U}IP20241119121240/PTUVIEW_crtvw.sql.
SQL executed online.
SQL Build log file written to D:/Upgrade/Output/softwareupdatePTU858{LFSDMO1D-
LFSUAT1U}IP20241119121240/PTUVIEW_crtvw.log.

Edit

D:\Upgrade\Output\softwareupdatePTU858{LFSDMO1D-LFSUAT1U}IP20241119121240\
PTUVIEW_crtvw.sql

Modify A.VERITY_LOCALE to A.ISO_LOCALE

f) Ignored below step

 g) Ignored below step.

Next Create app/web and prcs on upgraded tools version , here that is on PT8.58.23 .
And perform testing.
Administrator : fscm91st
System : P@ssw0rd
Ssl : password
PTWEBSERVER : PTWEBSERVER
ss
Application Upgrade Steps.
ss
select username,tablespace_name,max_bytes from dba_ts_quotas where tablespace_name='PSIMAGE';

To check if a tablespace has unlimited quota in Oracle, you can use

the query select username,tablespace_name,max_bytes from dba_ts_quotas. If
the max_bytes value is -1, then the user has unlimited quota on that
tablespace.

set linesize 124

col file_name format a75
col AUTOEXTENSIBLE format a18
SELECT FILE_NAME, BYTES/(1024*1024), MAXBYTES/(1024*1024), AUTOEXTENSIBLE from
DBA_DATA_FILES
WHERE TABLESPACE_NAME='PSIMAGE';
Task 3-7: Creating and Configuring an Upgrade Job
You must define your change packages before performing this task. To run an upgrade using PeopleSoft
Change
Assistant, you need to configure PeopleSoft Change Assistant as well as an upgrade job.
Note. You must be in Update Manager Action.
Launch PeopleSoft Change Assistant and perform the following steps:
1. Configure the PeopleSoft Change Assistant options:
a. Select Tools, Options.
b. On the General Options page, specify the high-level settings for your current environment.
c. On the Additional Options page, enter your optional email notifications settings.
d. Click OK.
2. Next, create your upgrade job. Select Tools, Upgrade Application.
The Change Package Wizard will guide you through creating the upgrade job.
3. On the Change Package Settings page, select the download directory where you created the Upgrade
Package,
select the apply type, and click Next.
4. On the Select Upgrade Target Database page, select the target database (Copy of Production
database) to
upgrade and click Next.
5. On the Select Upgrade Source Database page, select the source database and click Next.
6. On the Select Application Upgrade page, select the packages to apply and click Next.
7. Change Assistant will check the compatibility and display the status.
In PeopleSoft Change Assistant 8.55, you can apply a Required for Upgrade (RFU) Change Package to
your
upgrade source before starting the application upgrade. If you have not created an RFU package, you will
see
a warning message on the Check Compatibility page indicating that the RFU Change Package is
undefined.
You may choose to proceed, or you may cancel this process, generate the RFU package using PUM
procedures and then restart these steps.
See the PeopleSoft Update Manager Home Page on My Oracle Support (Doc ID 1641843.2) for PUM
instructions.
8. Review the checks on the Check Compatibility page and click Next.
9. On the Apply Summary page, click Finish.
10. Change Assistant will create the Application Upgrade job and open it.
11. Set the documentation directory so that PeopleSoft Change Assistant can display the HTML upgrade
documentation in the documentation pane:
a. Select Edit, Set Documentation Directory.
b. Enter or browse to the directory containing the HTML documentation and click OK.
See the product documentation for PeopleTools: Change Assistant and Update Manager for your current
release for information about configuring Change Assistant for upgrades
Task 3-6: Defining Upgrade Packages
As of PeopleSoft PeopleTools 8.55, the application upgrade template is delivered within the Update
Image and
can only be downloaded via the upgrade package. You will need to define your upgrade packages and
create your
upgrade template before performing your application upgrade in Change Assistant. The Define Upgrade
Package
component in the PeopleSoft Update Manager application will create 2 change package definitions:
• Upgrade package (UPG): This package contains the Application Upgrade template from your current
release
to 9.2
• Required for Upgrade package (RFU): This package contains all of the bugs required for upgrade
Prior to defining either type of upgrade package, apply all Required at Upgrade PRPs to your Current
Update
Image environment to ensure the generated package has the latest upgrade fixes.
To define upgrade packages:
1. In Change Assistant, configure the General Options and PUM Source.
2. Select Tools, Change Actions, then select Update Manager and click Next.
3. Select "Upload Target Database Information to Image" and click Finish.
The target database is the Upgrade Source database (New Release Demo).
4. Select the target database to upload.
5. Select "Proceed to Define or Create a New Change Package Wizard After Target Information is
Uploaded"
and click Next.
6. Click the button "Click Here to Open Browser and Connect to the PUM Source Database."
7. Sign on to the PUM Source Database.
8. Select PeopleTools, Lifecycle Tools, Update Manager, Update Manager Dashboard.
9. Expand the folder Select Target Database and click the Upgrade Source database name.
10. Expand the Define Change Package folder and select Define Upgrade Package.
The Define Upgrade Package wizard will guide you through the steps to create a change package
definition.
11. At Step 2 of the Define Upgrade Package wizard, enter a name and description for the change
package and
click Next.
12. At Step 3, the "Application Upgrade to 9.2" option is selected by default. Select the From release and
To
release (9.2 image release) from the drop-down lists and click Next.
By default, Required for Upgrade Fixes will be included in the package.
13. Step 4 does not apply to upgrade packages, so is skipped by the wizard.
14. Step 5 displays the upgrade path and the bugs to be included in the change package. Review the
bugs and
click Next.
15. When you transition to Step 6, the required for upgrade (RFU) change package and the application-
only
upgrade template (UPG) change package definitions are created and the results are displayed in the
summary
list.
16. Return to Change Assistant to create the change packages.
17. In Change Assistant, on the Create a New Change Package page, select either the UPG or RFU change
package from the drop-down list and click Finish.
18. You will receive a message "Do you need to create the corresponding UPG CP?" or "Do you need to
create
the corresponding RFU CP?" or "Change Package <name of change package> has been Successfully
Created
in the Download Directory" depending on your selection in the previous step. Click OK.
The change packages will be created.
See the product documentation for PeopleTools: Change Assistant and Update Manager for your current
release.
See the PeopleSoft Update Manager Home Page on My Oracle Support (Doc ID 1641843.2) for PUM
Instructions