1 / 21

University of Wisconsin Hospital & Clinics

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. Oracle Environment. Oracle 10.2.0.4 running on AIX 5.3 Oracle RMAN repository and console.

rhys
Download Presentation

University of Wisconsin Hospital & Clinics

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. PS Environment • PeopleSoft Financials 9 • PeopleSoft Human Resources 8.9 • Upgrade in progress from HR 8.9 to 9.1

  3. Oracle Environment • Oracle 10.2.0.4 running on AIX 5.3 • Oracle RMAN repository and console

  4. PS Technical • Process schedulers on both Windows and AIX • Application servers on Windows • WebLogic web server on Windows • PeopleTools 8.46 • PeopleTools 8.50

  5. Standards • Server naming standards • Database naming standards

  6. Cloning Overview • Initiated by developers • On demand, not on a schedule • Takes about 2 hours

  7. 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

  8. 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

  9. 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.

  10. Cloning Step – OEM Console Make sure the database backup files are present.

  11. Cloning Step – OEM Console Submit the clone job to the console

  12. Cloning Script Overview • Validate parameters (target not production) • Blackout the target database using emctl • Bounce the target database • Attempt to perform an archivelog change • Create the command line • Run the script • Check the log for errors and email results • End the blackout

  13. Cloning Script

  14. Post Clone Script This “post clone script” is where all of the customized SQL code gets run There is a separate “post clone script” for each target

  15. Post Clone Script

  16. Post Clone Script

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

  18. 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>

  19. 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

  20. Manual Steps • Notify the developers

  21. Web Site • Scripts and these PowerPoint slides are available on our OAUG PeopleSoft Technology SIG web site • http://psofttechsig.oaug.org/

More Related