Refreshing a PeopleSoft non-production environment with your production environment can become a monthly, weekly, or even a daily occurrence depending on the business needs. For some, refreshing an environment can become such an ordeal. Not having updated data to test issues and develop with it can lead to potential problems when your non-production instances are not regularly refreshed with the production.
A Typical PeopleSoft Environment
A single PeopleSoft environment typically consists of a thousands of relational database tables, indexes and views. The delivered DEMO and SYS environments are created with the Data Mover tool. All other environments (Development, Test, Quality Assurance, Production, etc.), are usually created by cloning or copying an existing environment to a target.
Several methods are available to clone/copy PeopleSoft databases such as RMAN Backup/Restore. Backup/Restore – where a full backup of the source database is restored ‘over’ the target database. After the restore, some PeopleSoft tables must be edited to reflect the new database name, new server location, etc.
For this example, we will assume that the HRTST database will be refreshed from the HRPROD database. HRTST will be referred to as the target; HRPROD will be referred to as the source.
- Check for sufficient space in the source backup directory. Once the backup is completed we always check the logfile for any errors.
- Move the backup files of source backup(HRPRD) to target machine (HRTST)
Pre-refresh export backups to be taken from source database (HRTST) before dropping it and restoring prod backup (HRPROD)
3. Taking backups of the dblinks, security, roles, PIA users, projects if any from the source database(HRTST) which you want to have restored after the database restoration.
4. Any other pre-refresh tasks that would be considered necessary by you and the customer.
Preform the backup Procedure: TriCore has developed scripts and procedures that will drop the target database (HRTST) and replace it with the source database (HRPROD). Once target is up and running again we begin the post refresh steps.
Perform Post refresh steps as below
5. Import back the dblinks ,database users , security , roles, PIA users, projects to the source database (HRTST)
6. Some PeopleSoft tables must be edited to reflect the new database name, new server location, etc. We utilize custom TriCore datamover and SQL scripts to accomplish this. They include, but are not limited to the following:
a. Correcting report nodes and local nodes
b. Setting the proper PeopleSoft environment settings
c. Updating the REN server settings
d. Integration Broker settings.
7. Any Post Refresh Tasks as required by you and the customer.
As you can see we utilize our expertise and experience to ensure refreshing a PeopleSoft environment as painless as possible. We also provide the flexibility to conform to your existing business practices and can customize the refresh process to exceed your expectations.