Академический Документы
Профессиональный Документы
Культура Документы
The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracles products remain at the sole discretion of Oracle.
Program Agenda
<Insert Picture Here>
10g Release 2 Upgrade Enhancements Upgrade Process Manual Upgrade Steps Database Upgrade Assistant Best Practices Questions
Pre-Upgrade Analysis
The Pre-Upgrade Information Tool checks for:
Database version and compatibility Redo log size Updated initialization parameters (e.g. shared_pool_size) Deprecated and obsolete initialization parameters Components in database (JAVAVM, Spatial, etc.) Some components require installing companion CD Tablespace estimates
Increase in total size Additional allocation for AUTOEXTEND ON SYSAUX tablespace
Simplified Upgrade
Upgrade driven from the contents of the component registry (DBA_REGISTRY view) Single top-level script, catupgrd.sql, upgrades all components in the database using the information in the DBA_REGISTRY view Supports re-run of catupgrd.sql, if necessary
Simplified Documentation
One measure of simplicity: Database Upgrade Guide documentation size is decreasing dramatically:
8.1.7 9.0.1 9.2.0 10.1.0 10.2.0 - 512 pages - 484 pages 111 steps total for all components! - 344 pages - 154 pages - 130 pages - 16 steps for manual upgrade
Upgrade Process
Prepare to Upgrade
1. Become familiar with the features of the New Oracle Database 10g Release 2 2. Determine the upgrade path 3. Choose an upgrade method 4. Choose an OFA compliant Oracle Home directory 5. Prepare a backup strategy 6. Prepare a recovery strategy 7. Develop a test plan to test your database, applications, and reports
Manual Upgrade
Use SQL*Plus to perform any necessary actions to prepare for the upgrade, run the upgrade scripts and analyze the upgrade results
Export-Import
Use Data Pump or original Export/Import
Disadvantages
Offers less control over individual upgrade steps
Disadvantages
More work Manually check spool logs for errors More error prone Harder to automate
Manual Upgrade
3. Adjust REDO logs and tablespace sizes if necessary 4. Copy existing initialization files to new ORACLE_HOME and make adjustments as recommended
6.
7.
Startup Upgrade
STARTUP UPGRADE mode will suppress normal upgrade errors
Previously, STARTUP MIGRATE in Oracle Database 9i R2 Only real errors are spooled Automatically handles setting system parameters that can otherwise cause problems during upgrade Turns off job queues Disables system triggers Allows AS SYSDBA connections only
Finally, set initialization parameter COMPATIBLE to 10.2.0 to make full use of Oracle Database 10g Release 2 features
9.2 is the minimum compatibility required for 10.2
Progress
Displays upgrade progress at a component level
Configuration Checks
Automatically makes appropriate adjustments to initialization parameters
Checks for adequate resources such as SYSTEM tablespace size, rollback segments size, redo log size
Pre-Upgrade Summary
Prior to upgrade provides summary of all actions to be taken Wizard warns user about any issues found Provides space analysis information for backup Applies required changes to network configuration files
Minimizing Downtime
Speeds up upgrade by disabling archiving Recompiles packages in parallel User interaction is not required after upgrade starts
Security features
Locks new users in the upgraded database
Customizability
Post-Upgrade Scripts
ISVs can customize DBUA to run their upgrade scripts
XML Driven
XML files drive the DBUA engine Created by Pre-Upgrade Information Tool & Post-Upgrade Status Tool
Upgrade Results
HTML Report
Displays results of upgrade process Provides Post-Upgrade database information such as Version and ORACLE_HOME
Allows DBA to unlock new database users Allows DBA to restore the original database
Backup location
backupLocation
Custom scripts
-postUpgradeScripts
Initialization parameters
initParam
Help
-help
EM configuration
emConfiguration
Welcome Screen
Tablespace
Log Files
Parallel Recompilation
Database Backup
Management Options
Recovery Configuration
Database Credentials
Upgrade Progress
Upgrade Results
Upgrade Results
Best Practices
Best Practices - 1
The three Ts: TEST, TEST, TEST
Test the upgrade Test the application(s) Test the recovery strategy
Functional Testing
Clone your production database on a machine with similar resources Use DBUA for your upgrade Run your application and tools to ensure they work
Best Practices - 2
Performance Analysis
Gather performance metrics prior to upgrade
Gather AWR or Statspack baselines during various workloads
Upgrade production systems only after performance and functional goals have been met
Pre-Upgrade Analysis
You can run DBUA without clicking finish to get a pre-upgrade analysis or utlu102i.sql Read general and platform specific release notes to catch special cases
Best Practices - 3
Automate your upgrade
Use DBUA in command line mode for automating your upgrade Useful for upgrading a large number of databases
Logging
For manual upgrade, spool upgrade results and check logs for possible issues DBUA can also do this for you
Check for sufficient space in SYSTEM, UNDO, TEMP and REDO logs
Best Practices - 4
Use Optimal Flexibility Architecture (OFA)
Offers best practices for locate your database files, configuration files and ORACLE_HOME
Best Practices - 5
Use Enterprise Manager Grid Control to manage your enterprise
Use EM to setup new features and try them out EM provides complete manageability solution for Databases, Applications, Storage, Security, Networks
Collect Object and System Statistics to improve plans generated by CBO Check for invalid objects in the database before upgrading
SQL> select owner, object_name, object_type, status from dba_objects where status<>VALID;
Best Practices- 6
Avoid upgrading in a crisis
Keep up with security alerts Keep up with critical patches needed for your applications Keep track of de-support schedules
Always upgrade to latest supported version of the RDBMS Make sure patchset is available for all your platforms
Questions?