Upgrade STAGING
PRODUCTION
DEV
TEST
Share
Clone +
Mask
Upgrade Process
Scenario: Upgrade an application
Production
Staging
Test
Development Training
Cost of Application Upgrades
• Infrastructure change
• Hardware
• Operating system
• Storage system
• Database software change
• Software upgrade
• Software patch
• Database configuration changes
• Initialization parameters
• Optimizer version
• Application performance changes
• Access structure changes (INDEX, PARTITIONS)
Lifecycle of Change Management TEST
Test
Set Up Test
Environments Promote Change
Identify Changes
Diagnose & Manage
Problems
PRODUCTION
Secret # 1: Testing Database Changes
using Real Application Testing
• Reduces risk of new
technology adoption through Deploy
higher testing quality
Test
Change
• Reduces time for effective
testing from weeks to days
Remediate
Mid-Tier
* No client/middle
tier setup
Storage
Storage
Analysis &
Capture Process Replay
Reporting
Real Application Testing with
SQL Performance Analyzer (SPA)
• Test impact of change on SQL query performance
• Capture SQL workload in production including statistics & bind variables
• Re-execute SQL queries in test environment
• Tune regressed SQL and seed SQL plans for production
Capture SQL
… … Use SQL Tuning
Oracle DB Advisor to tune
regression
Storage
Complete Change Test automation in
EM Grid Control 10.2.0.5
HR OE IX
DEPT
EMP ORDERS SALES PRODUCT PRICE
Data
Warehouse
Vendor releases application upgrades
Upgrade
What is impacted
Patch
• Data loader programs
Version 11.5.10 Version 12
• Application customizations
What has changed
• TABLES • Integration with other
• INDEXES applications
• PACKAGES
• PROCEDURES
• MATERIALED VIEWS
• TABLESPACES
• init.ora
Accelerate Planning – Dependency mapping
• Capture information on
all schema objects for an HR OE IX
application EMP
DEPT
ORDERS SALES PRODUCT PRICE
• Tables, Views, Indexes
• Procedures, Packages,
Triggers
• Users, init.ora
• Capture scope
• Database
• Schema
• Objects Base
• Version each baseline Base line
Base line 3
line 1 2
Secret #2: Map dependencies and
track changes affecting dependencies
Customization: Steps
Invoice Check Printing Module 1. Create Baseline based on
Dependencies: dependencies
• PO_VENDORS table 2. Upgrade application
(EBusiness Suite 11.5.09 to
• AP_CHECKS_PKG package &
11.5.10)
package body
3. Compare upgraded
application schema with
baseline
4. Identify changes
• Upgrade customization
modules if affected.
• Do NOTHING if unaffected
Comparison workflow
Baseline Baseline
• Compare Modes
• Baselines to Baselines
• Baselines to Database
• Database to Database
• Compare Scope
Baseline Prod
• Schemas
• Object types (Tables, Index
etc)
• Non Schema Objects (Users,
Grants, Profiles etc)
• Storage Parameters (Table Prod
spaces, extent size etc) Prod
Comparison of dependencies –
before and after the application upgrade
Agenda
Features
• Automatic database referential integrity if masking primary keys
• Implicit – database enforced
• Explicit – application enforced
• Data mask format library
• Preview sample data before masking
• Application masking templates
• Define once - execute many
Data Masking Pack
De-Identifying Sensitive Data
Benefits
Eliminate risk of moving sensitive data to dev & test environments
Share data with partners without exposing sensitive data
No impact on production database
Leverage Masking templates for common data types
Mask related columns in the same way
Agenda
• Functionality/Capability
• Gold image based cloning of software bits
• Image can be pre-patched to any level
• Image is sourced from the host itself or from the Software Library
• Optionally performs post cloning configuration eg: database
creation
• Several homes can be cloned in parallel
• Database cloning is also supported
• Database cloning uses fast,proven RMAN technology
• Benefits
• Reduce possibility of errors and improve reliability
• Faster provisioning through automation
Agenda
• Malicious SQL
• Index
• Unauthorized Access Control
changes • Tables
• PL/SQL objects
Secret # 4: Promote final changes to Production
DB