分类：
2008-04-12 10:20:16
Peoplesoft HCM 89 Clone Notes
Sometimes when the peoplesoft system may be destroyed because of dba mistake or hardware issue. If you have a cold backup of the database fortunelly, you can restore the system in very short time. This document described the process for restoring it. Also we can clone a new peoplesoft system from an existing one.
For the clone, I use the same software version except for database.
Source system:
Operating System: Redhat linux 2.4.21-32.EL
Web Server: Weblogic 8.1
PeopleTools: 8.47
Application: HCM 8.9
COBOL compiler: MicroFocus ServerExpress
Tuxedo 8.1
Database: Oracle 10.1.0.1.0
Target system:
Operating System: Redhat linux 2.4.21-32.EL
Web Server: Weblogic 8.1
PeopleTools: 8.47
Application: HCM 8.9
COBOL compiler: MicroFocus ServerExpress
Tuxedo 8.1
Database: Oracle 10.2.0.1.0
If you want to clone a new system from an existing one and you want to share the same PS_HOME with it, you can skip this chapter and begin to clone database from chapter III.
Description:
Weblogic acted as a web server here only, peoplesoft uses its own application server.
Reference:
CHAPTER 2 on Enterprise PeopleTools 8.47 Installation for Oracle
Description:
The PeopleSoft application server uses BEA's middleware product, Tuxedo, to perform transaction management, messaging, and administration.
Reference:
CHAPTER 3 on Enterprise PeopleTools 8.47 Installation for Oracle
TUXEDO portal:
Description:
It is a COBOL compiler.
Reference:
CHAPTER 3 on Enterprise PeopleTools 8.47 Installation for Oracle
MicroFocus website: http://supportline.microfocus.com
Note 1:
COBOL is not needed for PeopleTools because the Process Scheduler has been re-written in C++. In addition,
COBOL is not required for applications that contain no COBOL programs. Please see for the details on whether your application requires COBOL.
Note 2:
Press ‘y’ when asked whether you want to install Micro Focus LMF. LMF is the License Management
Facility. PeopleSoft recommends that LMF be installed as part of the Server Express installation and suggest that you install LMF in its own directory, not in a subdirectory of Server Express.
.
Note 3:
You can download the LMF user manual from URL:
http://microfocus.com/000/ServerExpressLicensing_tcm21-8234.pdf
Refer to following URL for license codes for Oracle’s PeopleSoft Enterprise line of products:
Description:
It contains all the scripts, executable files for File Server, App Server, Batch Server and Database server.
Reference:
CHAPTER 4 on Enterprise PeopleTools 8.47 Installation for Oracle
Description:
It contains all the executable files and scripts for creating tables and views of HCM89, also including the demo data for it.
Reference:
CHAPTER 4 on Enterprise PeopleTools 8.47 Installation for Oracle
Note 1:
Use the same
Note 2:
To properly install a Demo database, you must select both the System Database and the Demo Database options during the installation of your PeopleSoft applications.
Description:
The Oracle RDBMS software must be installed before clone. I suggest that you use the same database version with the source system if possible.
Reference:
CHAPTER 7B on Enterprise PeopleTools 8.47 Installation for Oracle
Description：
In this section, we create a new database from the source database’s backup. There are 3 plans for different conditions.
Plan A: The database versions of source and target systems are same.
You can refer to solution A.
Plan B: The database versions of source and target systems are different, the database of source system can startup normally.
I suggest upgrade the database in the source system firstly, then clone follow solution A.
Plan C: The database versions of source and target systems are different, the database of source system are destroyed. In this condition, we must slipt the task into 2 steps; first upgrade the database file to the target version, then recovers the database.
You can refer to solution B.
Solution A:
Step 1: Upload the database files (dbf) to target system $TARGET_PATH (any directory is ok, up to you).
Step 2: Copy the init[SID].ora file to $ORACLE_HOME/dbs folder of target system. Change the parameter db_name to the new db name. Change the parameter control_files to use the new directory. Also you may also need to change the file name to include the new SID.
Step 3: Recreate control files. Refer to recreate control file script.
Step 4: Start database and reset redo logs. ALTER DATABASE OPEN RESETLOGS;
Step 5: Config the listener. You need add the new SID information to listener.ora and restart it using lsnrctl command.
Step 6: Change the db owner table. Update psdbowner set dbname=[NEW_SID] ;commit;
Solution B:
Step 1: Upload the database files (dbf) to target system $TARGET_PATH (it should be the same directory with the source system).
Step 2: Copy the init[SID].ora file to $ORACLE_HOME/dbs folder of target system. Don’t modify anything in the file because we need to do an upgrade firstly.
Step 3: Reset redo logs. ALTER DATABASE OPEN UPGRADE;
Step 4: Upgrade the 10.1.0.1 to 10.2.0.1. Excute $ORACLE_HOME/rdbms/admin/catupgrd.sql
Step 5: Restart the database.
Step 6: Till now the database files have been upgrade to the new version successfully. You can refer to solution A to change the SID, db file directory. In another word, you need do a restore from these database files.
Recreate control file script:
startup nomount pfile=$ORACLE_HOME/dbs/init[SID].ora;
CREATE CONTROLFILE REUSE set DATABASE "[SID]" RESETLOGS NOARCHIVELOG
MAXLOGFILES 8
MAXLOGMEMBERS 4
MAXDATAFILES 1021
MAXINSTANCES 1
MAXLOGHISTORY 454
LOGFILE
GROUP 1 '$TARGET_PATH/redo01.log' SIZE 100M,
GROUP 2 '$TARGET_PATH/redo02.log' SIZE 100M,
GROUP 3 '$TARGET_PATH/redo03.log' SIZE 100M
-- STANDBY LOGFILE
DATAFILE
'$TARGET_PATH/system01.dbf',
'$TARGET_PATH/psundots01.dbf',
'$TARGET_PATH/sysaux01.dbf',
'$TARGET_PATH/psdefault.dbf',
'$TARGET_PATH/aaapp.dbf',
'$TARGET_PATH/aalarge.dbf',
'$TARGET_PATH/adapp.dbf',
'$TARGET_PATH/amapp.dbf',
'$TARGET_PATH/avapp.dbf',
'$TARGET_PATH/bdapp.dbf',
'$TARGET_PATH/bnapp.dbf',
'$TARGET_PATH/bnlarge.dbf',
'$TARGET_PATH/ccapp.dbf',
'$TARGET_PATH/coapp.dbf',
'$TARGET_PATH/cuaudit.dbf',
'$TARGET_PATH/cularg1.dbf',
'$TARGET_PATH/cularg2.dbf',
'$TARGET_PATH/cularg3.dbf',
'$TARGET_PATH/cularge.dbf',
'$TARGET_PATH/diapp.dbf',
'$TARGET_PATH/dtapp.dbf',
'$TARGET_PATH/eoapp.dbf',
'$TARGET_PATH/eobfapp.dbf',
'$TARGET_PATH/eocfapp.dbf',
'$TARGET_PATH/eocmapp.dbf',
'$TARGET_PATH/eocmlrg.dbf',
'$TARGET_PATH/eocmwrk.dbf',
'$TARGET_PATH/eocuapp.dbf',
'$TARGET_PATH/eoculrg.dbf',
'$TARGET_PATH/eodsapp.dbf',
'$TARGET_PATH/eodslrg.dbf',
'$TARGET_PATH/eoecapp.dbf',
'$TARGET_PATH/eoeclrg.dbf',
'$TARGET_PATH/eoecwrk.dbf',
'$TARGET_PATH/eoeiapp.dbf',
'$TARGET_PATH/eoeilrg.dbf',
'$TARGET_PATH/eoewapp.dbf',
'$TARGET_PATH/eoewlrg.dbf',
'$TARGET_PATH/eoewwrk.dbf',
'$TARGET_PATH/eoiuapp.dbf',
'$TARGET_PATH/eoiulrg.dbf',
'$TARGET_PATH/eoiuwrk.dbf',
'$TARGET_PATH/eolarge.dbf',
'$TARGET_PATH/eoltapp.dbf',
'$TARGET_PATH/eoppapp.dbf',
'$TARGET_PATH/eopplrg.dbf',
'$TARGET_PATH/eotpapp.dbf',
'$TARGET_PATH/eotplrg.dbf',
'$TARGET_PATH/epapp.dbf',
'$TARGET_PATH/eplarge.dbf',
'$TARGET_PATH/erapp.dbf',
'$TARGET_PATH/erlarge.dbf',
'$TARGET_PATH/erwork.dbf',
'$TARGET_PATH/faapp.dbf',
'$TARGET_PATH/falarge.dbf',
'$TARGET_PATH/fgapp.dbf',
'$TARGET_PATH/fglarge.dbf',
'$TARGET_PATH/fsapp.dbf',
'$TARGET_PATH/giapp.dbf',
'$TARGET_PATH/gpapp.dbf',
'$TARGET_PATH/gpdeapp.dbf',
'$TARGET_PATH/hpapp.dbf',
'$TARGET_PATH/hrapp.dbf',
'$TARGET_PATH/hrapp1.dbf',
'$TARGET_PATH/hrapp2.dbf',
'$TARGET_PATH/hrapp3.dbf',
'$TARGET_PATH/hrapp4.dbf',
'$TARGET_PATH/hrapp5.dbf',
'$TARGET_PATH/hrapp6.dbf',
'$TARGET_PATH/hrapp7.dbf',
'$TARGET_PATH/hrimage.dbf',
'$TARGET_PATH/hrlarg1.dbf',
'$TARGET_PATH/hrlarge.dbf',
'$TARGET_PATH/hrsapp.dbf',
'$TARGET_PATH/hrsarch.dbf',
'$TARGET_PATH/hrslarge.dbf',
'$TARGET_PATH/hrswork.dbf',
'$TARGET_PATH/hrwork.dbf',
'$TARGET_PATH/htapp.dbf',
'$TARGET_PATH/inapp.dbf',
'$TARGET_PATH/paapp.dbf',
'$TARGET_PATH/palarge.dbf',
'$TARGET_PATH/pcapp.dbf',
'$TARGET_PATH/pclarge.dbf',
'$TARGET_PATH/piapp.dbf',
'$TARGET_PATH/pilarge.dbf',
'$TARGET_PATH/piwork.dbf',
'$TARGET_PATH/poapp.dbf',
'$TARGET_PATH/psimage.dbf',
'$TARGET_PATH/psimgr.dbf',
'$TARGET_PATH/psindex.dbf',
'$TARGET_PATH/psindex1.dbf',
'$TARGET_PATH/ptamsg.dbf',
'$TARGET_PATH/ptapp.dbf',
'$TARGET_PATH/ptappe.dbf',
'$TARGET_PATH/ptaudit.dbf',
'$TARGET_PATH/ptcmstar.dbf',
'$TARGET_PATH/ptlock.dbf',
'$TARGET_PATH/ptprc.dbf',
'$TARGET_PATH/ptprjwk.dbf',
'$TARGET_PATH/ptrpts.dbf',
'$TARGET_PATH/pttbl.dbf',
'$TARGET_PATH/pttlrg.dbf',
'$TARGET_PATH/pttree.dbf',
'$TARGET_PATH/ptwork.dbf',
'$TARGET_PATH/pvapp.dbf',
'$TARGET_PATH/py0lrg.dbf',
'$TARGET_PATH/pyapp.dbf',
'$TARGET_PATH/pylarge.dbf',
'$TARGET_PATH/pywork.dbf',
'$TARGET_PATH/saapp.dbf',
'$TARGET_PATH/sacapp.dbf',
'$TARGET_PATH/salarge.dbf',
'$TARGET_PATH/srapp.dbf',
'$TARGET_PATH/stapp.dbf',
'$TARGET_PATH/stlarge.dbf',
'$TARGET_PATH/stwork.dbf',
'$TARGET_PATH/tlapp.dbf',
'$TARGET_PATH/tllarge.dbf',
'$TARGET_PATH/tlwork.dbf',
'$TARGET_PATH/waapp.dbf'
CHARACTER SET UTF8
;
Note: You need add db file to TEMP tablespace manually after control file recreation.
Description:
We need create an appcalition domain here.
Reference:
CHAPTER 8B on Enterprise PeopleTools 8.47 Installation for Oracle
Enterprise PeopleTools 8.47 PeopleBook: System and Server Administration, “Using PSADMIN Menus”
Note 1:
We need set listening ports for WSL, JSL and JRAD, confirm with the system administrtor about the free ports that are not using by other applications.
Possible issue 1:
Failed to start up app server domain, invalid version of SQL library libpsora starting up app server on Linux with Oracle 10g.
PSAPPSRV.26696 (0) [06/01/06 15:53:41](1) GenMessageBox(200, 0, M): PS General SQL Routines: Missing or invalid version of SQL library libpsora (200,0)
PSAPPSRV.26696 (0) [06/01/06 15:53:41](1) GenMessageBox(0, 0, M): Database Signon: Could not sign on to database HR89DMO with user PS.
PSWATCHSRV.26695 (0) [06/01/06 15:53:43] Shutting down
Solution: SOLUTION#201016345 on Customer Connection
1) Log in as the Oracle owner.
2) cd $ORACLE_HOME/lib
ln -s $ORACLE_HOME/lib/libclntsh.so.10.1 libclntsh.so.9.0
3) cd to $PS_HOME/setup
4) Rerun PSRUN.MAK
Possible issue 2:
Cannot open message isue, like below:
Cannot open message catalog LIBTUX_CAT, set 1, num 262;
Solution: SOLUTION# 684318 on Customer Connection
The problem was that when Tuxedo was installed, the variable LANG was not set. Because of this, the subdirectory en_US was not created -- full name is $TUXDIR/locale/en_us but this subdirectory was stored : $TUXDIR/locale/C.
To resolve this issue:
1) Declare the variable LANG=en_US; export LANG; then reinstall Tuxedo to create the missing directory en_US ($TUXDIR/locale/en_US).
-or-
2) A solution that does not include reinstalling Tuxedo -- create a link in $TUXDIR/locale called "en_US" pointing to $TUXDIR/local/C. To create the link cd to $TUXDIR/locale then execute the command ln -s C en_US
3) For NT: set the following environment variable through the System in the control panel: NLSPATH=%TUXDIR%\local\c.
Description:
We set up the PIA on Weblogic here.
Reference:
CHAPTER 9B on Enterprise PeopleTools 8.47 Installation for Oracle
Note 1:
When prompted to select the type of domain to create—single server, multi server, or distributed managed server.
You must select "Multi Server Domain" if you plan to host PeopleBooks on the web server on which you are installing the PeopleSoft Pure Internet Architecture.
Reference:
CHAPTER 10B on Enterprise PeopleTools 8.47 Installation for Oracle
Enterprise PeopleTools 8.47 PeopleBook: PeopleSoft Process Scheduler
Description:
We compile and link PeopleSoft COBOL batch programs here.
Reference:
CHAPTER 12B on Enterprise PeopleTools 8.47 Installation for Oracle
Administering the License Management Facility: http://supportline.microfocus.com/documentation/books/sx40sp2/adtask.htm
Possible issue 1:
6 cobols fail to compile in HRMS and Campus Solutions 8.9 MP1 Application Unicode environment.
The six COBOLs listed below will fail to compile during the Compiling COBOL section of the Enterprise PeopleTools 8.46 Installation Guide. The errors occur because required COBOL sources are not copied to the temporary compile directory by cblbld.bat or pscbl.mak while the build runs.
FAPINAS4
FAPINAS5
FAPINAS6
IMPLUS03
IMPLUS04
IMPLUS05
Solution: SOLUTION ID: 201025418 on Customer Connection
On Unix, the errors can be ignored because pscbl.mak will copy all of the COBOLs that successfully compile to PS_HOME/cblbin directory. Also, the errors should go away after Task 2-1 is completed so subsequent recompiles should be clean. Task 2-1 describes how to successfully compile the remaining files so that all sources will be built.
On Windows, cblbld.bat will stop after the six errors occur and will not copy the compiled COBOL files to the PS_HOME\CBLBINU directory. Because of this, the compiled *.exes., *.gnts, and *.ints should be manually copied from the compile directory to the PS_HOME\cblbinu directory after cblbld.bat stops (shown below).
In an ANSI environment on Windows, the COBOL compiling process described in the Enterprise PeopleTools 8.46 Installation Guide will remove all compiled COBOLs from PS_HOME\cblbina before copying the new files in. This will also remove the INAS COBOLs that are created in this task. As a result, Task 2-1 will need to be repeated after a PeopleSoft COBOL recompile using cblbld.bat so that the INAS objects are replaced.
