This document is created for use as a guideline and checklist when manually upgrading from Oracle 9iR2 (9.2), Oracle 10gR1 (10.1), Oracle 10gR2 (10.2) or Oracle 11gR1 (11.1) to Oracle 11gR2 (11.2).
Would you like to explore this topic further with other Oracle Customers, Oracle Employees, and Industry Experts?
Click here to join the discussion where you can ask questions, get help from others, and share your experiences with this specific article.
Discover discussions about other articles and helpful subjects by clicking here to access the main My Oracle Support Community page for Database /Upgrade.
Database Administrators, Support
Recommendations for Source database
1) Ensure that all database components/objects provided by Oracle are VALID in the source database prior to starting the upgrade.
2) Ensure that you do not have duplicate objects in the SYS and SYSTEM schema.
The following objects are permissible duplicate objects:
Please refer to the following article for complete instructions to remove any other duplicates.
NOTE.1030426.6 HOW TO CLEAN UP DUPLICATE OBJECTS OWNED BY SYS AND SYSTEM
3) Disable the custom triggers that would fire before/after DDL and enable them after the upgrade is complete.
4) Prior to Upgrading a database with XML Database(XDB) installed or installing XDB, be sure to run the code mentioned in Note 1573175.1 "Upgrading or Installing XDB could result in data loss if XDB_INSTALLATION_TRIGGER exists " to determine if any objects need to be dropped. Please note, failure to follow the steps listed below could result in data loss of user objects like tables, indexes
Requirements and recommendations for target database
If ASMM is configured on the database, set both parameters as indicated above to guarantee a minimum value for those pools.
Minimum version of the database that can be directly upgraded to Oracle 11g Release 2 (11.2)
|Source Database||Target Database|
|220.127.116.11 or higher||11.2.x|
|10.1.0.5 or higher||11.2.x|
|10.2.0.2 or higher||11.2.x|
|18.104.22.168 or higher||11.2.x|
The following database versions will require an indirect upgrade path:
|Source Database||Upgrade Path for Target Database||
|7.3.3 (or lower)||---->||7.3.4 -> 22.214.171.124||---->||11.2.x|
|8.0.5 (or lower)||---->||8.0.6 -> 126.96.36.199||---->||11.2.x|
|8.1.7 (or lower)||---->||188.8.131.52 -> 10.2.0.2(or any higher 10GR2 version)||---->||11.2.x|
|184.108.40.206 (or lower)||---->||220.127.116.11 -> 10.2.0.2 (or any higher 10GR2 version)||---->||11.2.x|
If source database is 18.104.22.168.0, the upgrade path to be followed is as below:
22.214.171.124.0 --> 126.96.36.199 --> 10.2.0.2(or any higher 10GR2 version)--> 11.2.x.
In this section all the steps need to be performed after having set the environment of the previous version of the Oracle Database. Note that the database must be running in normal mode in the old release.
To download and use the latest Pre-Upgrade Information Tool see the following:
How to Download and Run Oracle's Database Pre-Upgrade Utility Note 884522.1
Run the Pre-Upgrade Information Tool for Collecting Pre-Upgrade Information
Failure to run the pre-upgrade tool (utlu112i.sql) will result in the following error while running the catupgrd.sql script :
It is required to restore the database back to previous version in order to run the preupgrade tool (utlu112i.sql ) .
Check the spool file and examine the output of the Upgrade Information Tool.
The sections which follow describe the output of the Upgrade Information Tool.
For sample output, Click here
This section displays global database information about the current database, such as the database name, release number and compatibility level. A warning is displayed if you must adjust the COMPATIBLE initialization parameter before the database is upgraded.
This section displays a list of redo log files in the current database whose size is less than 4 MB. For each log file, the file name, group number and recommended size is displayed.
In a manual upgrade using SQL scripts and utilities, new files of at least 4 MB (preferably 10 MB) must be created in the current database, and any redo log files less than 4 MB must be dropped before the database is upgraded. These tasks are performed automatically by the Database Upgrade Assistant.
This section displays a list of tablespaces in the current database. For each tablespace, the tablespace name and minimum required size is displayed. In addition, a message is displayed if the tablespace is adequate for the upgrade.In a manual upgrade using SQL scripts and utilities, space must be added to tablespaces that do not have enough free space in the current database. These tablespace adjustments must be made before the database is upgraded. This task is performed automatically by the Database Upgrade Assistant.
This section displays a list of initialization parameters in the parameter file of the current database that must be adjusted before the database is upgraded. The adjustments must be made to the parameter file after it is copied to the new Oracle Database 11g release.
This section displays a list of initialization parameters in the parameter file of the current database that are deprecated in the new Oracle Database 11g release.Obsolete Parameters This section displays a list of initialization parameters in the parameter file of the current database that are obsolete in the new Oracle Database 11g release2 (11.2). Obsolete initialization parameters must be removed from the parameter file before the database is upgraded.
Appendix A: "Deprecated Initialization Parameters" for a list of initialization parameters that are deprecated in Oracle Database 11g release 2 (11.2).
This section displays a list of initialization parameters in the parameter file of the current database that are obsolete in the new Oracle Database 11g release 2 (11.2). Obsolete parameters need to be removed from the parameter file before the database is upgraded. Obsolete parameters' means parameters which are no longer valid (or) in use.
Appendix B: "Obsolete Initialization Parameters" for a list of initialization parameters that are obsolete in Oracle Database 11g release 2 (11.2)
This section displays a list of database components in the new Oracle Database 11g release 2 (11.2) that are upgraded or installed when the current database is upgraded.
This section provides warnings about specific situations that might require attention before or after the upgrade.
This section displays the minimum required size for the SYSAUX tablespace which is required in the new Oracle Database 11g release 2 (11.2). The SYSAUX tablespace must be created if it does not exist (in Oracle 9i ) after the new release is started and before the upgrade scripts are invoked.
Note : If SYSAUX was created in 9i then it must be dropped and re-created after starting in the new release. If created in 10g or later then it can be left there and used.
Preparing Database for Upgrade
Check for the integrity of the source database.
Check for the integrity of the source database prior to starting the upgrade by downloading and running the dbupgdiag.sql script from the My Oracle Support article below:
If the dbupgdiag.sql script reports any invalid objects, run $ORACLE_HOME/rdbms/admin/utlrp.sql (multiple times) to validate the invalid objects in the database until there is no change in the number of invalid objects.
After validating the invalid objects, re-run dbupgdiag.sql in the database once again and make sure that everything is fine.
Deprecated CONNECT Role
After upgrading to Oracle Database 11g Release 2 (11.2) from Oracle Database9i Release 2 (9.2) or Oracle Database 10g Release 1 (10.1), the CONNECT role has only the CREATE SESSION privilege; the other privileges granted to the CONNECT role in earlier releases are revoked during the upgrade. To identify which users and roles in your database are granted the CONNECT role, use the following query:
If users or roles require privileges other than CREATE SESSION, then grant the specific required privileges prior to upgrade.
The upgrade scripts adjust the privileges for the Oracle-supplied users.
In Oracle 9.2.x and 10.1.x CONNECT role includes the following privileges:
From Oracle 10.2, 'CONNECT' role only includes 'CREATE SESSION' privilege.
Create script for (in case the database has to be downgraded again).
During the upgrade to Oracle Database 11g Release 2 (11.2) from Oracle Database 9i Release 2 (9.2) or Oracle Database 10g Release 1 (10.1), any passwords in database links are encrypted. To downgrade to the original release, all of the database links with encrypted passwords must be dropped prior to the downgrade. Consequently, the database links do not exist in the downgraded database. If you anticipate a requirement to be able to downgrade to your original release, then save the information about affected database links from the SYS.LINK$ table, so that you can re-create the database links after the downgrade.
Check for TIMESTAMP WITH TIMEZONE Datatype
The RDBMS DST patching has been greatly improved in 11gR2.
Unlike upgrading for older versions (upgrading 10.2.0.4 to 188.8.131.52 for example) there is no need anymore to
apply "dst patches" on the old version *before* the upgrade.
If you upgrade from an older RDBMS version to 11gR2 the DST version in 11gR2 after the upgrade will be
simply the same as the DST version that was used in the older RDBMS version.
There are however a few situations where some extra steps are needed,
so please do check below notes before upgrading to 11gR2., depending on to what 11gR2 version you upgrade to
Note 1579838.1 : Actions For DST Updates When Upgrading To Or Applying The 184.108.40.206 Patchset
Note 1358166.1 : Actions For DST Updates When Upgrading To Or Applying The 220.127.116.11 Patchset
Note 1201253.1 : Actions For DST Updates When Upgrading To Or Applying The 18.104.22.168 Patchset
Note 815679.1 : Actions For DST Updates When Upgrading To 22.214.171.124 Base Release
Simply follow above note ( depending on to what 11gR2 version you upgrade to ) in most cases there will be no action to
take before the upgrade, but better be safe than sorry.
If the note say's to apply a RDBMS DST patch to the new 11gR2 home before the upgrade then please do so before going further in this note.
Make sure that
returns the RDBMS DST version of your old Oracle RDBMS version.
This is the value found in the "check your current DST version on 9i, 10g or 11.1.0.x" step of the above notes.
If this select gives an error or a different value then re-run the utlu112i.sql (Pre-Upgrade Information Tool) script and check again.
Check that the National Characterset (NLS_NCHAR_CHARACTERSET) is UTF8 or AL16UTF16.
select value from NLS_DATABASE_PARAMETERS where parameter = 'NLS_NCHAR_CHARACTERSET';
If this is UTF8 or AL16UTF16 then no action is needed.
If is not UTF8 or AL16UTF16 then refer to the following article:
When upgrading to Oracle Database 11g Release 2 (11.2), optimizer statistics are collected for dictionary tables that lack statistics. This statistics collection can be time consuming for databases with a large number of dictionary tables, but statistics gathering only occurs for those tables that lack statistics or are significantly changed during the upgrade.
To determine the schemas which lack statistics, either review the output of the utlu112i.sql script or download and run the script from the below article:
To decrease the amount of downtime incurred when collecting statistics, you can collect statistics prior to performing the actual database upgrade. As of Oracle Database 10g Release 1 (10.1), Oracle recommends that you use the DBMS_STATS.GATHER_DICTIONARY_STATS procedure to gather these statistics. For example, you can enter the following:
If you are using Oracle Database 9i Release 2 (9.2), then you should use the DBMS_STATS.GATHER_SCHEMA_STATS procedure to gather statistics. To do this, you can run the scripts provided in Appendix B.
Appendix B has a sample script, which creates the table dictstattab and exports the statistics for the RDBMS component schema into it. The statistics collection might give errors if a particular component schema does not exist in the database or if a component is not installed or is invalid.
This script is useful when you want to import the statistics back into the database
For example, the following PL/SQL subprograms import the statistics for the SYS schema after deleting the existing statistics:
Disable Oracle Database Vault
When upgrading from Oracle Database release 10.2, if you have enabled the Oracle Database Vault option in your current Oracle Home, then you must disable Oracle Database Vault in the target Oracle Home where the new release 11.2 software is installed before upgrading the database, and enable it again when the upgrade is finished. If Database Vault is enabled, then DBUA will return an error asking you to disable Database Vault prior to upgrade.
You must do this before upgrading the database. Enable Oracle Database Vault again once the upgrade is complete.
Please refer to the following Documentation/Articles for complete information to Disable/Enable Oracle Database Vault.
Disabling and Enabling Oracle Database Vault
You can also refer to the following documents for Disabling Oracle Database Vault before the upgrade and enabling it after the upgrade.
Backing up Enterprise Manager Database Control Data. This can be skipped if EM Database Control Console is not being used or not configured.
备份Enterprise Manager Database Control Data
After upgrading to Oracle Database 11g release 2 (11.2), if you want to downgrade Oracle Enterprise Manager Database Control you must save your Database Control files and data before upgrading your database. The emdwgrd utility can be used to keep a copy of your database control files and data before upgrading your database. The emdwgrd utility resides in the ORACLE_HOME/bin directory in the Oracle Database 11g release 2 (11.2) home.
1. Set ORACLE_HOME to your old Oracle Home
2. Set ORACLE_SID to the SID of the database being upgraded.
3. Set PATH, LD_LIBRARY_PATH and SHLIB_PATH to point to the Oracle home from which the database is being upgraded.
Example : export SHLIB_PATH=$ORACLE_HOME/lib:$SHLIB_PATH
4. Change directory to Oracle Database 11g release 2 (11.2) home.
5. Run the emdwgrd command.
a. Run the following command for single instance database:
where old_SID is the SID of the database being upgraded and save_directory is the path to the storage place you have chosen for your Database Control files and data.
b. For RAC database, remote copy is required across the cluster nodes. Define an environment variable to indicate which remote copy is configured. For example: setenv EM_REMCP /usr/bin/scp
Note: If 10g Oracle Home is on a shared device, add -shared to the previous command line.
The above command(s) may core dump on the -UX Itanium platform, which is a known issue. For more information, refer to following article:
6. Enter the SYS password for the database to be upgraded.
Note: On RAC databases you will be prompted to run '/tmp/racdwgrd_dbctl.sh' on each of the nodes.
Configuring Network ACL's
Oracle Database 11g Release 2 (11.2) includes fine-grained access control to the UTL_TCP, UTL_SMTP, UTL_MAIL, UTL_HTTP, or UTL_INADDR packages using Oracle XMLDB. If you have applications that use one of these packages, you must install OracleXML DB if it is not already installed. You must also configure network access control lists (ACLs) in the database before these packages can work as they did in prior releases. Actions are discussed in Post Upgrade tasks (Step 35), as the DBMS_NETWORK_ACL_ADMIN package is introduced after upgrading the database and not available in prior releases.
This optional check is introduced to spot any logical corruption in underlying objects and their dependencies.
This proactive check is introduced to avoid any failure in database upgrade at a later stage due to such corruption. If there is corruption the upgrade will most likely fail.
To check for corruption in the dictionary, use the following commands in SQL*Plus (connected as sys):
使用以下语句生产分析数据字典的脚本 (as sysdba)：
This creates a script called analyze.sql.
Now execute the following steps:
This script (analyze.sql) should not return any errors.
1. ORA-30657 might occur if there is any external table validated, which can be safely ignored as per Note 209355.1 ORA-30657: Using ANALYZE TABLE for an External Table
2. Errors shown below when executing analyze.sql can be ignored:
SP2-0734: unknown command beginning "SQL> SELEC..." - rest of line ignored.
SP2-0042: unknown command "SQL>" - rest of line ignored.
SP2-0734: unknown command beginning "SQL> spool..." - rest of line ignored.
3. "ORA-00054: resource busy and acquire with NOWAIT specified" may be returned when analyzing AWR tables (WRH$_...)
to workaround this error AWR can be temporarily disabled :
3.a) get current value for snapshot interval :
3.b) set this interval to zero to temporarily disable AWR :
3.c) Analyze the WRH$ tables
3.d) Revert back to initial value :
Before upgrading Oracle Database, you must wait until all materialized views have completed refreshing and check that replication is stopped.
Run the following query to determine if there are any materialized view refreshes still in progress:
SQL> select distinct(trunc(last_refresh)) from dba_snapshot_refresh_times;
SQL> select s.obj#,o.obj#,s.containerobj#,lastrefreshdate,pflags,xpflags,o.name,o.owner#, bitand(s.mflags, 8) from obj$ o, sum$ s
where o.obj# = s.obj# and o.type# = 42 AND bitand(s.mflags, 8) = 8;
If the second query returns any row, then use Note 1442457.1 : During 11g Upgrade, Mview refresh warning
Ensure that no files need media recovery and that no files are in backup mode.
This should return no rows.
Password protected roles.
In version 11.2 password protected roles are no longer enabled by default,
if any of your applications relies on such roles being enabled by default and you take no measures to allow
the user to enter the password with the set role command, it is recommended to remove the password
from those roles to allow for existing privileges to remain available, for more information see :
Note 745407.1 : What Roles Can Be Set as Default for a User?
Oracle Database Security Guide 10g Release 2 (10.2) Part Number B14266-07
Oracle Database Security Guide 11g Release 1 (11.1) Part Number B28531-15
Oracle Database Security Guide 11g Release 2 (11.2) Part Number E16543-09
Resolve outstanding distributed transactions prior to the upgrade.
If this returns rows you should do the following:
To check if a standby database exists, issue the following query:
If this query returns a row, then sync the standby database with the primary database.
1. Make sure all the logs are transported to the standby server after a final log switch
in the primary.
2. Start the recovery of the standby database with the NODELAY option.
Disable all batch and cron jobs.
About jobs initiated with Oracle the packages DBMS_JOB, DBMS_SCHEDULER can be used , regarding cron jobs (external jobs controlled at the OS level), this is a task for your Unix administrator
See also :
Note 404238.1 : How to Disable an Entry from DBMS_SCHEDULER
Note 1335741.1 : How To Stop A Running Job Using DBMS_JOB
Note 67695.1 : PROCEDURE DBMS_JOB.BROKEN Specification
Ensure the users SYS and SYSTEM have 'SYSTEM' as their default tablespace.
You must have sufficient space in the tablespace or be set to extents unlimited.
If DEFAULT_TABLESPACE is anything other than SYSTEM tablespace, modify the default tablespace to SYSTEM by using the below command.
Ensure that if the aud$ table exists that it is in the SYS schema and in the SYSTEM tablespace.
If the AUD$ table is not in SYSTEM tablespace and not owned by the SYS user then before doing the upgrade put it back to the SYSTEM tablespace and it should be owned by SYS .
Note: If the AUD$ table exists and is in use, upgrade performance can be effected depending on the number of records in the table.
Check whether database has any externally authenticated SSL users.
If any SSL users are found then Step 33 has to be followed after the upgrade.
Note down the location of datafiles, redo logs and control files. Also take a backup of all configuration files like listener.ora, tnsnames.ora, etc. from $ORACLE_HOME.
If the you have upgraded the Grid Infrastructure then this step is not needed as it was done as part of the GI install / upgrade
a) Stop the listener for the database.
Previous versions of the listener are not supported for use with an Oracle Database 11g Release 2 (11.2) database. However, it is possible to use the new version of the listener with previous versions of Oracle Databases.
If you are upgrading from 9i or upgrading manually without using DBUA, run Oracle Net Configuration Assistant before upgrading the Oracle RAC database.
This is a two-step option.
You must first run Oracle Net Configuration Assistant from the old Oracle Home to remove the old listener.
- Invoke the Netca
- Choose the configuration you want to do ==> Choose Listener Configuration
- Select what you want to do ==> Delete
- Select the listener you want to delete .
Then you must run Oracle Net Configuration Assistant again from the new Oracle Database 11g Release 2 (11.2) Home to create a new listener.
- Invoke the Netca
- Choose the configuration you want to do ==> Choose Listener Configuration
- Select what you want to do ==> Add
- Provide the detail that is required to configure the listener.
You must remove the old listener before creating a new one. If you attempt to create a new listener from the new Oracle Home first, and use the same name and port as the old listener, then Oracle Net Configuration Assistant returns an error.
Note: This is your only option if you want to upgrade your Oracle RAC database manually.
b) Stop other executable such as dbconsole, isqlplus, etc.
Shutdown the database.
Back up the Database
1. Perform Cold Backup
2. Take a backup using RMAN
--> backup_directory >> Location of the Database backup.
--> controlfile_backup_directory >> Location of the Controlfile backup.
- copy the initialization file from source Oracle Home to
- then process in target 11GR2 directory (
Comment out obsoleted parameters (Appendix A) and change all deprecated parameters (Appendix A).
* The DIAGNOSTIC_DEST initialization parameter replaces the USER_DUMP_DEST, BACKGROUND_DUMP_DEST.
According to Bug 8937877, CORE_DUMP_DEST is not deprecated.
Refer to the below article for understanding directory structure in 11g and DIAGNOSTIC_DEST.
* If you are upgrading from 9.2.0.x, the COMPATIBLE initialization parameter must be set to at least 10.0.0,
which is the lowest possible setting for Oracle Database11g Release 2 (11.2) prior to the upgrade.
This value must remain throughout the upgrade and can be changed to the higher value after the upgrade has been completed successfully.
(Please note, once you set the COMPATIBLE to 10.1 there is no way to downgrade to 9iR2 because of symptoms described in
Note 388604.1 : ORA-00201 while downgrading from 10gR2 to 10gR1 or 9iR2 ).
Oracle recommends increasing the COMPATIBLE parameter only after complete testing of the upgraded database has been performed.
If you are upgrading from 10.1.0.x or 10.2.0.x then you can leave the COMPATIBLE parameter set to
it's current value until the upgrade has been completed successfully.
This will avoid any unnecessary ORA-942 errors from being reported in SMON trace files during the upgrade
(because the upgrade is looking for 10.2 objects that have not yet been created).
* Adjust the values of the initialization parameters to at least the minimum value indicated by the Pre-Upgrade Information Tool.
Make sure all path names in the parameter file are fully specified. You should not have relative path names in the parameter file.
* If you are upgrading a cluster database, set the parameter CLUSTER_DATABASE=FALSE during the upgrade and set it back to true after the upgrade.
If your operating system is Windows then complete the actions in this step, else skip to the next step.
Stop the OracleServiceSID Oracle service of the database you are upgrading, where SID is the instance name. For example, if your SID is ORCL, then enter the following at a command prompt:
Set the environment to Source/Previous version (9.2 / 10.1 / 10.2 /11.1)
1. Stop the Oracle database service.
2. Delete Oracle service using ORADIM binary from which the database is upgraded to 11.2.
3. Create the Oracle Database 11g Release 2 (112) service at a command prompt using the ORADIM command of the new Oracle Database release:
If your operating system is UNIX then complete this step, else skip to the next step.
1. Make sure the following environment variables point to the Oracle 11g Release 2 (11.2) directories:
- PATH, LD_LIBRARY_PATH , SHLIB_PATH and LIBPATH ( for AIX )
Note : If ORACLE_BASE is not known, after setting PATH to 11gR2 Oracle Home, execute 'orabase', which will point the location of the base.
2. Update the oratab entry to set the new ORACLE_HOME pointing to ORCL and disable automatic startup.
Note: After /etc/oratab is updated to have SID and Oracle Home (11.2), you can execute oraenv (/usr/local/bin/oraenv) and set the environment. The input has to be the SID which is entered in /etc/oratab against the 11gR2 home.
Upgrading Database to 11gR2
At the operating system prompt, change to the $ORACLE_HOME/rdbms/admin directory of 11gR2 Oracle Home.
Note: If you are upgrading from 9.2 and the SYSAUX table already exists then drop the existing SYSAUX tablespace. The SYSAUX tablespace needs to be created immediately after the database is started in upgrade mode using 11g binaries (with Compatibility set to atleast 10.1 and just prior to the running of the catupgrd.sql scripts.
Create the SYSAUX tablespace only if you are upgrading from Oracle Database9i Release 2 (9.2) with the following mandatory attributes:
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO
The Pre-Upgrade Information Tool provides an estimate of the minimum required size for the SYSAUX tablespace in the SYSAUX Tablespace section. Refer to the output generated by the utlu112i.sql script in Step 1. The following SQL statement would create a 500 MB SYSAUX tablespace for the database:
Set the system to spool results to a log file for later verification after the upgrade is completed and start the upgrade script.
These measures are an important final step to ensure the integrity and consistency of the newly upgraded Oracle Database software. Also, if you encountered a message listing obsolete initialization parameters when you started the database for upgrade, then remove the obsolete initialization parameters from the parameter file before restarting. If necessary, convert the SPFILE to a PFILE so you can edit the file to delete parameters.
Run the Post-Upgrade Status Tool $ORACLE_HOME/rdbms/admin/utlu112s.sql which provides a summary of the upgrade at the end of the spool log. It displays the status of the database components in the upgraded database and the time required to complete each component upgrade. Any errors that occur during the upgrade are listed with each component and must be addressed.
Run catuppst.sql, located in the $ORACLE_HOME/rdbms/admin directory, to perform upgrade actions that do not require the database to be in UPGRADE mode.
This script can be run concurrently with utlrp.sql. Run utlrp.sql to recompile any remaining stored PL/SQL and Java code in another session.
Check for the integrity of the upgraded database by running dbupgdiag.sql script from the below article:
If the dbupgdiag.sql script reports any invalid objects, run $ORACLE_HOME/rdbms/admin/utlrp.sql (multiple times) to validate the invalid objects in the database, until there is no change in the number of invalid objects.
After validating the invalid objects, re-run dbupgdiag.sql in the upgraded database once again and make sure that everything is fine.
Post Upgrade Steps
Verify the listener.ora file.
For the upgraded instance(s) Verify the ORACLE_HOME parameter to point to the new ORACLE_HOME. Start the listener.
1. Make sure the following environment variables point to the Oracle 11g Release 2 (11.2) directories:
- PATH, LD_LIBRARY_PATH, SHLIB_PATH and LIBPATH ( for AIX )
Also check that your oratab file and any client scripts that set the value of ORACLE_HOME point to the Oracle Database 11g Release 2 (11.2) Home.
Note : If you are upgrading a cluster database, then perform these checks on all nodes in which this cluster database has instances configured.
2. Modify /etc/oratab entry to use automatic startup.
After the upgrade
note : this simply repeats the same actions as given in the "DST" notes referenced in step 6 of this note.
Check the current version of the Oracle time zone definitions in the upgraded database:
This should be the same as the value found before the upgrade.
if this is HIGHER than 11 (for 126.96.36.199 ) or 14 (for 188.8.131.52 and 184.108.40.206) then goto step 32
if this is 11 (for 220.127.116.11 ) or 14 (for 18.104.22.168 and 22.214.171.124) then goto step 32
if this is LOWER than 11 (for 126.96.36.199 ) or 14 (for 188.8.131.52 and 184.108.40.206) then it is *recommended* to upgrade the timezone version
*For 220.127.116.11 : update to DSTv11 (standard DST version of 18.104.22.168) by
using the scripts in Note 1585343.1 Scripts to automatically update the RDBMS DST (timezone) version in an 11gR2 or 12cR1 database .
following Note 977512.1 Updating the RDBMS DST version in 11g Release 2 (22.214.171.124 and up) using DBMS_DST
(from step 3a) onwards using "11" as (
*For 126.96.36.199 , 188.8.131.52 and 184.108.40.206 : update to DSTv14 (standard DST version of (for 220.127.116.11 , 18.104.22.168 and 22.214.171.124) by
using the scripts in Note 1585343.1 : Scripts to automatically update the RDBMS DST (timezone) version in an 11gR2 or 12cR1 database .
following Note 977512.1 Updating the RDBMS DST version in 11g Release 2 (126.96.36.199 and up) using DBMS_DST
(from step 3a) onwards using "14" as (
Upgrade Statistics Tables Created by the DBMS_STATS Package.
If you created statistics tables using the DBMS_STATS.CREATE_STAT_TABLE procedure, then upgrade these tables by executing the following procedure:
In the example, 'SYS' is the owner of the statistics table and 'dictstattab' is the name of the statistics table. Execute this procedure for each statistics table.
Upgrade Externally Authenticated SSL Users.
If you have upgraded from Oracle 9.2.0.x or 10.1.0.x, and you are using externally authenticated SSL users, then you must run the following command to upgrade those users:
If you are upgrading from 10.2.0.x (or higher), then you are not required to run this command.
Enable Database Vault
Refer to the following documents for enabling Oracle Database Vault:
Configure Fine-Grained Access to External Network Services.
To avoid "ORA-24247: network access denied by access control list (ACL)" when executing UTL packages (Network related packages), access has to be granted to user using these packages.
The following example first looks for any ACL currently assigned to host_name. If one is found, then the example grants user_name the CONNECT privilege in the ACL only if that user does not already have it. If no ACL exists for host_name, then the example creates a new ACL called ACL_name, grants the CONNECT privilege to user_name, and assigns the ACL to host_name.
acl_name.xml => Enter a name for the access control list XML file.
ACL description => 'file description',
principal => 'user_or_role',
is_grant => TRUE|FALSE,
privilege => 'connect|resolve',
host_name => host name
Refer to the below note on how to use DBMS_NETWORK_ACL_ADMIN package and also to avoid ORA-24247 : network access denied by access control list (ACL).
Create a server parameter file with an initialization parameter file.
This will create an spfile as a copy of the init.ora file located in $ORACLE_HOME/dbs (UNIX) & %ORACLE_HOME%\database (Windows).
Change passwords for Oracle-Supplied Accounts.
Depending on the release from which you upgraded, there might be new Oracle-supplied accounts. Oracle recommends that you lock all Oracle supplied accounts except for SYS and SYSTEM, and expire their passwords, thus requiring new passwords to be specified when the accounts are unlocked.
You can view the status of all accounts by issuing the following SQL statement:
To lock and expire passwords, issue the following SQL statement:
Upgrading Oracle Text
This is only needed if Oracle Text is in use.
NOTE : These steps are NOT required if you are upgrading the database within a same release ( patchset upgrade ) Example : 188.8.131.52 to 184.108.40.206.
Copy the following files from the previous Oracle Home to the new Oracle Home:
* Stemming user-dictionary files
* User-modified KOREAN_MORPH_LEXER dictionary files
* USER_FILTER executables
To obtain a list of the above files, use:
where version is 920, 101, 102
For instance, if upgrading from 10.2.0:
If your Oracle Text index uses KOREAN_LEXER which was deprecated in Oracle 9i and desupported in Oracle 10g Release 2, see below note for further information on manual migration from KOREAN_LEXER to KOREAN_MORPH_LEXER:
If you are upgrading to the 220.127.116.11 then please refer the following article for Support Note for Lexer Feature Updates
Please refer to the following article for more information on step 38.
Upgrade the Oracle Clusterware Configuration
If you are upgrading a cluster database from releases 10.2, 11.1, or 18.104.22.168, then upgrade the database configuration in Oracle Clusterware using the following command:
$ srvctl upgrade database -d db-unique-name -o oraclehome
where db-unique-name is the database name assigned to it (not the instance name), and oraclehome is the Oracle home location in which the database is being upgraded.
Configure Enterprise Manager
This step is only required if Dbconsole is used for the database , if Dbconsole is not configured or if database is monitored with the Grid Control then this step does not apply.
If your database is being managed by Oracle Enterprise Manager Database Control
then use the following command to update the configuration:
You need to run this from the new Oracle Database 11gR2 Oracle Home. When prompted, provide the Oracle Home from which the configuration is being upgraded.
Appendix A: Initialization parameters deprecated in Oracle Database 11g release 2 (11.2)
To get a list of all deprecated initialization parameters, issue the following SQL statement:
A warning message is displayed at instance startup if a deprecated parameter is specified in the parameter file. In addition, all deprecated parameters are logged to the alert log at instance startup.
Appendix A: Initialization Parameters Obsolete in Oracle Database 11g Release 2 (11.2)
TDE (Transparent Data Encryption)
If your are using Transparent Data Encryption then you will have to rekey the master key as follows:
Please see Note 1260584.1 : Ora-28374 After Migration From 10.2.0.4 To 22.214.171.124 for additional details.
Gather Fixed Object Statistics
Please create stats on fixed objects two weeks after the upgrade using the below command
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/12974804/viewspace-1062274/，如需转载，请注明出处，否则将追究法律责任。