Peoplesoft Upgrade

UPGRADE
Terms Used in Upgrade
CoP - Copy of Production
CCD - Copy of Current Demo (It is vanilla demo of the version in which the production is.)
NRD - New Release Demo
Before the Upgrade
1. The CoP and CCD should be at the same PeopleSoft Patch Levels.
2. Verify that Upgrade path is given by PeopleSoft
3. Find out and apply if necessary the Required for Upgrade Steps.
Navigation - PeopleSoft Customer Connect -
Implement, Optimize, and Upgrade » Upgrade Guide » Upgrade Documentation and Software » Upgrade Documentation and Scripts » Release
4. Step is extremely important as generally the UPGCONVERT project comes through the above link.
Some issues faced during Upgrade -
1. DBCC CHECKDB went into errors – Running it as part of the CA Upgrade Job
There 14 inconsistencies. This happens if the database restore does not happen smoothly, some block allocation/corruptions occurs.
a. Identified all the tables which went into error – There were 11
b. 8 of them had single errors and 3 of them had 2 errors each listed
c. Total no. of Inconsistencies were 14
d. Ran the below script for each Table and their indexes
e. USE UCP83
GO
DBCC UPDATEUSAGE ('<db name>', '<table 1>', '<table 2>')
2. Compare Fields
In this step in the Upgrade job we find if any PeopleSoft delivered tools field is touch/customized.
You have to merge PPLTOOLS and PPLTLS84CUR projects in to Compare_PPLTools project in the New Release Demo and do a compare
it with CoP. Care needs to be take to do a Project level compare and not a database level compare.
3. If a compare and report is run between two instance with wrong parameter like database is chosen instead of project then the project that was compared needs to be deleted and recreated. Read peoplebooks for understanding what compare and report actually does.
Details of fields in ProjectItem table.
Source Status - 1 - Absent
- 2 - Changed
- 3 - Unchanged
- 4 - *Changed
- 5 - *Unchanged
- 6 - Same
Above applies to TargetStatus
Upgrade Action - 0 - Copy
- 1 - Delete
- 2 - None
- 3 - Copy Prop
The above details can be used to script that change the actions that need to be taken when the project is copied.
For eg. If it is decided that everything that is customised by the client needs to be copied between database then
update PSPROJECTDEFN set UPGRADEACTION = 0 where SOURCESTATUS = 4

In the latest version of PeopleSoft , in the client status we see pool and not the list of users logged in . To see the user list :
modify web.xml and turn joltpooling entry to false.
/webserv//applications/peoplesoft/PORTAL/WEB-INF/web.xml

While altering tables we get error :- in SQL SERVER

String or binary data would be truncated.

The statement has been terminated.

We get the above error when peoplesoft wants to change the column datatype.
First it creates a dummy column , populates data , drops old column , rename dummy column to the original one.
We get the above error while converting text field to varchar(2000).
set ANSI_WARNING OFF will help us complete the scrip successfully.


After upgrade .. many times we get errors while opening pages - error like
first operand null, hmcr servcies .. this is related to campus solutions. To get rid..
open PERMISSION LIST attached to all users, go to web serivices and add services in question give full access.
Run the Refresh Cache process for the HCM Service Framework on Set Up HRMS, System Administration, HCM Registry, Service Registry, HCM Interface Registry page

SQR Flags

A. (-i) This flag tells SQRW where to look for any SQC subroutines that are included in your SQR using the "#INCLUDE" command. It is very important that the path contain a trailing backslash.
Example: -iS:\EP_Master\e752f70\sqr\
B. (-m) This flag tells SQRW where to look for the startup file ALLMAXES.MAX which contains processing limits for various internal parameters.
Example: -mS:\EP_Master\e752f70\sqr\allmaxes.max

C. (-ZIF) For SQR versions 4.x, this flag points to the location of your initialization file, PSSQR.INI.
Example: -ZIFs:\EP_Master\E752f70\sqr\pssqr.ini

D. (-o) This flag is used to define your SQR log file path and name.
Example: -oC:\temp\SQR.LOG

E. (-f) This flag points to the location where your output will be directed to. It is very important that the path contain a trailing backslash.
Example: -fC:\temp\


SQRW C:\psoft\PT855\custom\sqr\fixit.sqr DBNAME/USERNAME/PWD -iC:\psoft\PT855\sqr\ -ZIFC:\psoft\PT855\sqr\pssqr.ini -oC:\temp\fixit.LOG -fC:\temp\ ' ' 'param1' 'param2' param3_number