1 Copyright 2011, Oracle and/or its affiliates. All rights reserved.

Transcription

1 1 Copyright 2011, Oracle and/or its affiliates. All rights

2 Best Practices for Upgrading Oracle Database to 11g Release 2 2 Copyright 2011, Oracle and/or its affiliates. All rights Agrim Pandit & Anil Chanda Global Customer Support, Oracle

3 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 Oracle s products remains at the sole discretion of Oracle. 3 Copyright 2011, Oracle and/or its affiliates. All rights

4 Agenda Why Upgrade? ROI What is Upgrade? 10 Best Practices Common Issues Real World Examples Q&A 4 Copyright 2011, Oracle and/or its affiliates. All rights

5 Why Upgrade? Oracle Database 11g R2 is fully proven In production for 2+ years Thousands of customers have already upgraded New features of Oracle Database 11gR2 Useful and desirable for your environment. Potential cost saver Oracle support period will be for long time 11gR2 will be supported till Jan 2015 on Premier Support and Jan 2018 on Extended Support (Oracle Lifetime Support) Extended Support fee can be avoided No bug fixes unless you pay extra support fee to get extended support for critical Issues for another year- "Wake Up Call" Patchset, CPU, PSUs and other bug fixes It is essential to have the most current security fixes. And you'll get them only during the premier support period unless you pay extra for extended support. 5 Copyright 2011, Oracle and/or its affiliates. All rights

6 Why Upgrade Continued 11gR2 gives you 6+ years of premier support 6 Copyright 2011, Oracle and/or its affiliates. All rights

7 What is Upgrade? Upgrade is the process of changing the data dictionary contents of a database to reflect a particular release of the server. For each version of the database we support upgrades and downgrades from a specific set of versions. Upgrading from 10.2 to 11.2 is a major release upgrade. Upgrading from to is a patch set upgrade. Choose an Upgrade Method Manual Upgrade: A manual upgrade consists of directly using SQLplus to perform any necessary actions to prepare for the upgrade, run the upgrade script, and analyze the upgrade results Database Upgrade Assistant (DBUA) :The DBUA is a graphical user interface (GUI) tool that interactively steps you through the upgrade process and configures the database to run with the new Oracle Database release. 7 Copyright 2011, Oracle and/or its affiliates. All rights

8 8 Copyright 2011, Oracle and/or its affiliates. All rights

9 9 Copyright 2011, Oracle and/or its affiliates. All rights 10 Best Practices

10 Best Practice #1 Read the FRIENDLY manuals! 10 Copyright 2011, Oracle and/or its affiliates. All rights

11 Documentation Note Upgrade Advisors 11 Copyright 2011, Oracle and/or its affiliates. All rights

12 Documentation Note:251.1 Database Upgrades from 10.2 to Copyright 2011, Oracle and/or its affiliates. All rights

13 Documentation Note: Upgrade Companion 11g Release 2 13 Copyright 2011, Oracle and/or its affiliates. All rights

14 More useful references for upgrade Note:264.1 Database Upgrades from 9.2 to 11.2 Note: Upgrade Companion 11g Release 2 Note: Complete Checklist for Manual Upgrades to 11g Release 2 Note: Complete checklist for manual upgrades from X to Y Upgrade Guides: OTN Upgrade Page: Upgrade Blog: 14 Copyright 2011, Oracle and/or its affiliates. All rights

15 Best Practice #2 Always upgrade Grid Infrastructure (Clusterware and ASM) First! 15 Copyright 2011, Oracle and/or its affiliates. All rights

16 Best Practice #3 Use the Upgrade Planner in My Oracle Support 16 Copyright 2011, Oracle and/or its affiliates. All rights

17 Best Practice #4 Pre-upgrade Sanity operations 17 Copyright 2011, Oracle and/or its affiliates. All rights

18 18 Copyright 2011, Oracle and/or its affiliates. All rights 2010 Oracle Corporation 18 Sanity Operations: Database Components Resolve invalid database components before you upgrade: Make sure the software linked correctly. Remove components manually which are not in use. Fix components manually which are in use but invalid. Reference: Note: Information On Installed Database Components/Schemas Note Debug and Validate Invalid Objects Note: How to diagnose Components with NON VALID status Note How to Determine if XDB is Being Used in the Database?

19 Sanity Operations: Invalid Objects Always check for INVALID objects SQL> select unique OBJECT_NAME, OBJECT_TYPE, OWNER from DBA_OBJECTS where STATUS='INVALID'; Fix all INVALID objects BEFORE the upgrade/migration There should be no invalid objects in SYS and SYSTEM user schema Recompile invalid objects with utlrp.sql before the upgrade 19 Copyright 2011, Oracle and/or its affiliates. All rights

20 Sanity Operations: Duplicate Objects Always check for DUPLICATE objects in SYS/SYSTEM SQL> select OBJECT_NAME, OBJECT_TYPE from DBA_OBJECTS where OBJECT_NAME OBJECT_TYPE in (select OBJECT_NAME OBJECT_TYPE from DBA_OBJECTS where OWNER='SYS') and OWNER='SYSTEM' and OBJECT_NAME not in ('AQ$_SCHEDULES_PRIMARY', 'AQ$_SCHEDULES', 'DBMS_REPCAT_AUTH'); Fix DUPLICATE objects in SYS/SYSTEM BEFORE upgrade Note: How to Clean Up Duplicate Objects Owned by SYS and SYSTEM Schema 20 Copyright 2011, Oracle and/or its affiliates. All rights

21 Sanity Operations: Gather Schema Stats. Create dictionary statistics in Oracle 9i: SQL> exec DBMS_STATS.GATHER_SCHEMA_STATS ('SYS', options => 'GATHER',estimate_percent => DBMS_STATS.AUTO_SAMPLE_SIZE, method_opt => 'FOR ALL COLUMNS SIZE AUTO', cascade => TRUE); Create dictionary statistics in Oracle 10g/11g: SQL> exec DBMS_STATS.GATHER_DICTIONARY_STATS; 21 Copyright 2011, Oracle and/or its affiliates. All rights

22 Sanity operations : Pre-Process AUD$ record or Truncate SYS.AUD$ (if not required) How to Pre-Process SYS.AUD$ Records Pre-Upgrade From 10.1 or later to 11gR1 or later. (Doc ID ) OR SQL> truncate SYS.AUD$; Purge the recyclebin SQL> purge DBA_RECYCLEBIN; Remove old & hidden parameters _always_semi_join=off _unnest_subquery=false optimizer_features_enable=9.0.1 event = "10061 trace name context forever, level 10" 22 Copyright 2011, Oracle and/or its affiliates. All rights

23 Best Practice #5 Always run the pre-upgrade script: Download and run dbupgdiag.sql script before & after upgrade Script to Collect DB Upgrade/Migrate Diagnostic Information (dbupgdiag.sql) [ID ] 23 Copyright 2011, Oracle and/or its affiliates. All rights

24 Pre-Upgrade Checks Upgrade information script: utlu112i.sql Stored in: $OH_11g/rdbms/admin OR Download the newest version of the pre-upgrade check script utlu112i.sql: Note: Run in the environment of the source database Spool the output into a file: Checks all init parameters and displays warnings for obsolete and deprecated parameters Does checks for: Components status Tablespace SYSAUX Character set Time zone file version Cluster 24 Copyright 2011, Oracle and/or its affiliates. All rights

25 Preparation: Database Vault Switch off DATABASE VAULT (if used/installed) Oracle Database Vault Administrator's Guide: Appendix B Unix: (simplified) Relinking without Database Vault [$ make -f ins_rdbms.mk dv_off ioracle] $ chopt disable dv Windows: Rename oradv11.dll in ORACLE_HOME\bin Upon restart: $ chopt disable dv After upgrading relink with dv_on or rename the DLL and enable Database Vault again: $ chopt enable dv Note: This will just work under the assumption that DVSYS and the DV owning user have identical passwords 25 Copyright 2011, Oracle and/or its affiliates. All rights

26 Preparation: Time zone Patches - 11g Release 2 Upgrade to Oracle Database 11g Release 2: New 11.2-$OH has timezone V11 No need to patch the source $OH if TZ version < Target $OH Database only needs to be adjusted if you are using the datatype TIMESTAMP WITH TIMEZONE Conversion done after the upgrade See Note Package DBMS_DST DBMS_DST.FIND_AFFECTED_TABLES DBMS_DST.BEGIN_UPGRADE DBMS_DST.UPGRADE_DATABASE DBMS_DST.END_UPGRADE 26 Copyright 2011, Oracle and/or its affiliates. All rights

27 Prepration :Preserve performance statistics Collecting sufficient performance data prior to the upgrade is of vital importance, Sufficient means: Starting at least 4 weeks before the upgrade Gather accurate performance statistics In Oracle 8i/9i: Use STATSPACK Export the PERFSTAT user right before the upgrade Note: STATSPACK before/after upgrade In Oracle 10g/11g: Use AWR Take snapshots every minutes retention: >30 days Export the AWR with DBMS_SWRF_INTERNAL.AWR_EXTRACT Use AWR DIFF reports to compare before & after upgrade performance: DBMS_WORKLOAD_REPOSITORY.AWR_DIFF_REPORT_HTML 27 Copyright 2011, Oracle and/or its affiliates. All rights

28 Best Practice #6 Leave COMPATIBLE at the original value for a week before changing to COMPATIBLE has to be at least for an 11g database No way back once >= has been enabled Supported release downgrade to , >= , >= Flashback database to >= No ALTER DATABASE RESET COMPATIBILITY command anymore 28 Copyright 2011, Oracle and/or its affiliates. All rights

29 Best Practice #7 : Test fallback strategy In any case: Take a backup!!! Always: Create a valid and complete online backup with RMAN Test the restore and the recovery at least once!!! Make sure your fallback strategy covers both cases: Problems encountered during the upgrade Problems found days, weeks after the upgrade If anything unforeseen happens and you'll have to step back, will you be allowed to lose data (i.e. changes done to the data in the system after the upgrade): YES or NO? If YES: restore a backup, flashback (since 10g) If NO: export/import, downgrade, Oracle Streams, Oracle Golden Gate 29 Copyright 2011, Oracle and/or its affiliates. All rights

30 Fallback strategy: Issues during upgrade 30 Copyright 2011, Oracle and/or its affiliates. All rights

31 Fallback strategy: Issues After upgrade Assumption: No data loss allowed 31 Copyright 2011, Oracle and/or its affiliates. All rights

32 Best Practice #8 :Choose Upgrade PATH 32 Copyright 2011, Oracle and/or its affiliates. All rights

33 Upgrade alternatives: Minimal Downtime 33 Copyright 2011, Oracle and/or its affiliates. All rights

34 Upgrading database Step-by-Step 34 Copyright 2011, Oracle and/or its affiliates. All rights

35 Best Practice #9: Verify upgrade The DBUA has "spool" and "echo" on by default, Find the logs at: For DBUA $ORACLE_HOME/cfgtoollogs/dbua/<dbname>/upgrade<n>/ For manual method logs can be found at spooled location. Recompiling invalid objects Post-upgrade tool/utility Check if all components are valid: utlu112s.sql Dbupgdiag.sql output (run and check script to collect DB Upgrade/Migrate Diagnostic Information Note ) Check alert<sid>.log 35 Copyright 2011, Oracle and/or its affiliates. All rights

36 Best Practice #10: Post Upgrade Create system statistics during a regular workload period - otherwise non-appropriate values for the CBO will be used: SQL> exec DBMS_STATS.GATHER_SYSTEM_STATS('start');... gather statistics while running a typical workload SQL> exec DBMS_STATS.GATHER_SYSTEM_STATS('stop'); Always create an editable init.ora from the current SPFILE after the upgrade has been finished Prevents rewrite in case of setting wrong parameters or forced edit Keep in mind: The SPFILE is binary file!!! Don't edit it!! Default since Oracle 9.0 It simply will exist after using DBUA or DBCA Parameter can be changed by: SQL> create pfile='/tmp/initdb.ora' from spfile; SQL> startup force pfile=/tmp/initdb.ora SQL> create spfile from pfile; SQL> alter system set PARAMETER=VALUE scope=both; 36 Copyright 2011, Oracle and/or its affiliates. All rights

37 Common issues ORA-00904: "TZ_VERSION": invalid identifier Cause : If the registry$database table already exist in the database but does not have the TZ_VERSION column OR Time zone file version was not updated in registry$database. Solution :The error can be occurred if you have not executed the ultu112i.sql script on the source database prior to upgrade,it creates adds a TZ_VERSION column if does not exist and populate the column with TZ_VERSION value in registry$database.so make sure that you have execute the utlu112i.sql on the source database. ORA-39701: database must be mounted EXCLUSIVE for UPGRADE or DOWNGRADE Cause: It is a RAC database and was mounted for SHARED cluster access. Solution: Set the CLUSTER_DATABASE initialization parameter to FALSE in spfile/pfile and restart the server with the UPGRADE or DOWNGRADE option. 37 Copyright 2011, Oracle and/or its affiliates. All rights

38 Common issues continued ORA-01722: invalid number TimeZone Patch Cause: If the source database is using timezone files higher than default TZ version shipped with the target Oracle 11gR2 Oracle home and target Oracle home is NOT patched with the same version timezone before upgrade. Solution: Apply the TZ version patch on the target database to match the TZ version at source database then run the perupgrade script to populate the TZ_VERSION with new TZ version in the registry$database. Oracle Database Vault Cause: If the Oracle Database Vault option is TRUE. Upgrades cannot be run with the Oracle Database Vault option set to TRUE since AS SYSDBA connections are restricted. Solution: Perform a "SHUTDOWN ABORT", relink the server without the Database Vault option (but with the OLS option), and restart the server using UPGRADE. Oracle Label Security Cause: If Database Vault is installed in the database but the Oracle Label Security option is FALSE. Solution: relink the server with the OLS option (but without the Oracle Database Vault option) and restart the server using UPGRADE. 38 Copyright 2011, Oracle and/or its affiliates. All rights

39 Common issues continued ORA control file version <num> incompatible with Oracle version <num> Cause: You have set the compatible to the higher release and now try to open or downgrade the database with lower release. Solution: It is highly recommended to keep the compatible parameter to the least values.oracle recommends increasing the COMPATIBLE parameter only after complete testing of the upgraded database has been performed. Setting the compatible parameter to the highest value enables to use all of the features of the new release, but prevents from downgrading back to previous release. NOTE: If you are upgrading from x, the COMPATIBLE initialization parameter must be set to at least , which is the lowest possible setting for Oracle Database11g Release 2 (11.2) prior to the upgrade. 39 Copyright 2011, Oracle and/or its affiliates. All rights

40 Real world examples From support experience few interesting cases, Very small shared pool size when upgrading from 8i to 10g: Database upgrade run 48 hours instead of 1 hour Too small shared pool size when upgrade to 11g: ORA-4031 this leads to invalid objects Millions of audit records in SYS.AUD$ Upgrade took 24 hours once truncated upgrade completed in under 1 hour Objects of SYS users in user tablespace, upgrade fails with ora-0600 Customers forgot to analyze Dictionary Database Especially in huge dictionary database (like GSI or SAP) a big problem as we create stats while the upgrade runs 40 Copyright 2011, Oracle and/or its affiliates. All rights

41 Summary: Upgrade Best Practice Planning is a key to successful upgrade. A successful upgrade, requires minimal downtime, requires minimized, predictable efforts to upgrade, It produces a stable upgraded environment without any surprises. It identifies issues proactively and addresses them during the planning and testing phase. Drive upgrade as a project which should have Evaluate, Plan, Configure, Test, Implement stages. Upgrade Advisor Note Take consistent backup which is useful when its needed for recovery. Test upgrade in test environment, Optimize steps of upgrade to minimize upgrade window. Leverage tools of PreUpgrade, PostUpgrade even though DBUA is used. Don t underestimate test efforts, reserve enough time and resource for testing. Always use real world data for testing Create and test fallback strategy ( Does it really works?) Document all changes detailed and clearly in change log. 41 Copyright 2011, Oracle and/or its affiliates. All rights 2010 Oracle Corporation 41

42 42 Copyright 2011, Oracle and/or its affiliates. All rights Q&A