Top Banner
University of Wisconsin Hospital & Clinics Database / environment refresh steps
21

University of Wisconsin Hospital & Clinics Database / environment refresh steps.

Dec 24, 2015

Download

Documents

Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

University of Wisconsin Hospital & Clinics

Database / environment refresh steps

Page 2: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

PS Environment

• PeopleSoft Financials 9

• PeopleSoft Human Resources 8.9

• Upgrade in progress from HR 8.9 to 9.1

Page 3: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

Oracle Environment

• Oracle 10.2.0.4 running on AIX 5.3

• Oracle RMAN repository and console

Page 4: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

PS Technical

• Process schedulers on both Windows and AIX

• Application servers on Windows

• WebLogic web server on Windows

• PeopleTools 8.46

• PeopleTools 8.50

Page 5: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

Standards

• Server naming standards

• Database naming standards

Page 6: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

Cloning Overview

• Initiated by developers

• On demand, not on a schedule

• Takes about 2 hours

Page 7: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

Cloning Steps

Source -> Target

• Shut down target Application Servers and Process Schedulers

• Run a job in the OEM console

• Delete caches

• Start up target Application Servers and Process Schedulers

• Test and notify

Page 8: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

Cloning Step – AS & PS

Shut down target Application Servers and Process Schedulers

This is a manual step. Log in to the target machines and stop the services. It is possible it could be automated, but we have not automated it

Page 9: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

Cloning Step – OEM Console

Run a job in the OEM Console

If the source database does not have a current RMAN backup, you will need to perform a backup now. Most of our clones have the source databases as our production database, which means we can clone at any time without performing a backup first.

Page 10: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

Cloning Step – OEM Console

Make sure the database backup files are present.

Page 11: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

Cloning Step – OEM Console

Submit the clone job to the console

Page 12: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

Cloning Script Overview

1. Validate parameters (target not production)

2. Blackout the target database using emctl

3. Bounce the target database

4. Attempt to perform an archivelog change

5. Create the command line

6. Run the script

7. Check the log for errors and email results

8. End the blackout

Page 13: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

Cloning Script

Page 14: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

Post Clone Script

This “post clone script” is where all of the customized SQL code gets runThere is a separate “post clone script” for each target

Page 15: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

Post Clone Script

Page 16: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

Post Clone Script

Page 17: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

Manual Steps

• Up to this point, everything has been run as part of a script. Now we start the manual steps.

Page 18: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

Manual Steps

• Change the SYSADM password in the target database.

• Log on to datamover in bootstrap mode

• Log in as sysadm and the source database’s sysadm password. Run the script: CHANGE_ACCESS_PASSWORD SYSADM <new_sysadm_password>

Page 19: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

Manual Steps

• Start the Application Server and Process Schedulers on the target database

• Test the new infrastructure– Log in– Submit jobs to the process schedulers– Interfaces

Page 20: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

Manual Steps

• Notify the developers

Page 21: University of Wisconsin Hospital & Clinics Database / environment refresh steps.

Web Site

• Scripts and these PowerPoint slides are available on our OAUG PeopleSoft Technology SIG web site

• http://psofttechsig.oaug.org/