ExaSpecial PeopleSoft University of Minnesota

Agenda Introduction Running PeopleSoft on Exadata and Exalogic PeopleSoft Database Consolidation Questions and Answers

About the University of Minnesota Founded:1851 Five Campus Locations Enrollment: 69,221 (52,557 on Twin Cities campus) Alumni: ~400,000 Economic Impact: $8.6 billion into MN annually

Size of the Business

The Upgrade Enterprise System Upgrade Program (ESUP) Updating PeopleSoft systems CS from 8.9 to 9.0 HR from 8.9 to 9.2 Includes a split from CS Finance from 8.9 to 9.2 PeopleTools from 8.52.08 to 8.53.10 Implementing PeopleSoft Interaction Hub (Portal) and Secure Enterprise Search

System Architecture Infrastructure in a box Sun ZFS storage InfiniBand Gateway switches Management tools Oracle Traffic Director Running PeopleSoft Applications 5 Applications 11 Environments 110 VMs 500 Domains

Exalogic and PeopleSoft OVM Templates configured Dynamic DNS updates PeopleSoft domains deployed and managed via Python scripts NFSv4 shared mounts for PeopleSoft file systems Pure SDP protocol from web servers to Exadata

Benefits of “Exa” Architecture Full redundancy of Exalogic/Exadata Production DR on 2nd Exalogic rack InfiniBand interconnect between Exadata and Exalogic Streamlined Administration All components supported by Oracle

University of Minnesota: DBaaS Deployed in April 2011 Standardized infrastructure: Solaris → Linux Database 9.x, 10.x, 11.1 → 11.2 Single DR, backup, and HA strategies Centralized administration of databases Database “hotel” concept Exadata X2-2

DBaaS: Hotel Concept Candidate apps are typically under 50GB Currently ~150 hotel schemas Two hotel instance stacks (dev/tst/qa/prd/DR) for single- and multi-byte charsets Meets needs of 95% of database consumers Managed backups, security, DR, and compliance for all

DBaaS: Before and After 40+ database servers 225+ instances 8 FTEs 45 backup scripts 8 db servers (Exadata) ~30 instances 3 FTEs 12 backup scripts Two hotel stacks 35 customers ~150 hosted schemas $200,000/year savings

PeopleSoft Consolidation: Why Proven success with database “hotel” Provide more applications using fewer databases Positions us for Database 12c multi-tenant Support from Oracle & PeopleSoft Simplified administration, monitoring, and refreshes

PeopleSoft Support Model One team supports the PeopleSoft Architecture

PeopleSoft Database Landscape Current databases: 24 2 apps: CS/HR and Finance 14 Environments Planned databases: 18 5 apps: CS, HR, Finance, Portal, Secure Enterprise Search 11 Environments

PeopleSoft Consolidation: Details Each application has a schema Dedicated tablespace Dedicated temp tablespace Quota on undo 4-node RAC database Each application has affinity to two “primary” nodes and a designated “failover” node

Consolidation Benefits Easier administration of application stacks Better resource usage on Exadata Cross-application functionality streamlined Inter-schema table references instead of database links Complementary business cycles E.g., when CS is busy, HR and Finance are in slow phase

Consolidation Benefits Reporting snapshots are simplified One daily snapshot instead of two Data at same point in time across all applications Disaster recovery is easier All applications would be recovered to the same point in time Security is addressed across the board

Consolidation Risks Potential for resource contention If the database goes down, all applications are also down Oracle patch requirements may change in time

What’s Next ESUP project go-live is February 2015 Oracle Enterprise Manager 12c monitoring and administration Database, Exadata, and Exalogic PeopleSoft plug-in Testing in the consolidated database model has gone well

Questions

Contact Us Andy Wattenhofer, DBA Manager Brad Carlson, DBA watt0012@umn.edu Brad Carlson, DBA carl0426@umn.edu