There is plenty information on Oracle Support to cloning/restoring PeopleSoft DB, also about cloning PeopleSoft Servers and Domains.
But post-restoration activities are personalized for each PeopleSoft client, as different implementations and environments could be implemented. Anyway I post the general activities that I execute after a DB restoration:
From Support Workstation:
- Set DBNAME in PSDBOWNER back to the target database name.
- Set GUID to ‘ ‘ in the PSOPTIONS table.
- Truncate PSACCESSLOG and history tables.
- Delete the data from the reporting tables, process scheduler tables and application messaging tables since this data isn’t relevant in the target database.
1) Run prcsclr.dms – this will cleanup process scheduler tables. (PSPRCSRQST, PSPRCSQUE, PSPRCSPARMS, PS_MESSAGE_LOG etc.)
2) Run rptclr.dms – this will cleanup Report Manager tables. (PS_CDM_LIST, PS_CDM_AUTH etc.)
3) Cleanup messaging tables, run appmsgpurgeall.dms
FROM PIA:
- For PeopleTools 8.44 and higher, update the Long name, Short name, and System Type in PeopleTools -> Utilities -> Administration -> PeopleTools Options
- Validate IB Configuration – Gateway and ASync Domains. (Advanced properties information is loaded from PSIGW Domain file, gateway.properties)
- Check Web Services URL.
- Update Report Node Configuration.
Additional Activities:
If you want to keep previous security information before the DB restoration process, surely you executed the “securityexport.dms” script, this script keeps important PeopleTools security information on objects/tables. In order to restore this data after a DB restoration/clone process you must execute the “securityimport.dms” script.
Some imported objects are:
Users – PSOPRDEFN, PSUSEREMAIL , PSUSERATTR , PSOPRALIAS , PSROLEUSE, PSUSERPRSNLOPTN, PS_ROLEXLATOPR, PS_RTE_CNTL_RUSER.
Roles – PSROLEDEFN, PSROLECLASS, PSROLECANGRANT, PSROLECLASS.
Access Profiles – PSACCESSPRFL
It also imports Permission Lists, Definition Security records, Personalization, etc.
Andrés Caro