Oracle® Database

7.1 Review Known Preinstallation Issues

Review the information in the following sections. If any of the issues apply to the Oracle installation, follow the instructions before installing the patch set.

• Upgrading Oracle E-Business Suite Databases

• Upgrading Oracle Clusterware

• Using ASM Rolling Upgrades

• Cloning an Oracle Clusterware Home

• Notes to Oracle OLAP Users

• Notes to Oracle Text Users

http://metalink.oracle.com

$ $CRS_HOME/install/preupdate.sh

7.2 Identify the Oracle Database Installation

This is not a complete software distribution. You must install it in an existing Oracle Database 11g release 11.1.0.6 Oracle home. To identify Oracle home directories, view the /etc/oratab file.

You should then cross-check this by executing the following command:

opatch lsinventory -all

7.3 Check Postrelease Updates

Before installing this patch set in a production environment, review document 454507.1, ALERT: Oracle 11g release 1 (11.1) Support Status and Alerts, available on the OracleMetaLink Web site:

http://metalink.oracle.com

To locate this document:

1. Log on to OracleMetaLink.

2. Click Advanced at the top of the OracleMetaLink page.

3. Enter 454507.1 in the Document ID field, then click Submit.

This document is created by Oracle Support Services and provides information about the status of issues discovered after this patch set was released. If you are unable to access this site, then contact Oracle Support Services before installing this patch set in a production environment.

7.4 Download and Extract the Installation Software

To download and extract the patch set installation software:

1. Download patch 6890831 for your 11.1.0.7 platform to a directory that is not the Oracle home directory or under the Oracle home directory.

2. Compare the downloaded zip file size to the actual file size on OracleMetaLink.

3. Use the unzip command to unzip and extract the patch set files.

7.5 Update Oracle Time Zone Definitions

The 11.1.0.7 patch set includes the Oracle time zone definitions Version 4. This version of the time zone definitions includes the changes to daylight savings time in the USA in 2007 and other updates.

In the Oracle database the TIMESTAMP WITH LOCAL TIME ZONE (TSLTZ) and TIMESTAMP WITH TIME ZONE (TSTZ) data types and the TZ_OFFSET function select the time zone information from the time zone files.

It may be necessary to take action on existing TIMESTAMP WITH LOCAL TIME ZONE (TSLTZ) and TIMESTAMP WITH TIME ZONE (TSTZ) data or to re-apply DST patches afterwards.

For full overview please see OracleMetaLink document 568125.1 Actions for the DSTv4 update in the 11.1.0.7 patchset.

1. When upgrading directly from a 10.2 or 10.1 release or updating 11.1.0.6 to 11.1.0.7, check the current version of the Oracle time zone definitions with the following command:

   SELECT version FROM v$timezone_file;
   

   • If the query reports version 4, no action is required.

   • If the query reports a version lower or higher then 4, see OracleMetaLink document 568125.1, Actions for the DSTv4 update in the 11.1.0.7 patchset.

2. On upgrading from Oracle9i directly to Release 11.1.0.7, see OracleMetaLink document 568125.1, Actions for the DSTv4 update in the 11.1.0.7 patchset.

7.6 Set the ORACLE_HOME and ORACLE_SID Environment Variables

Enter the following commands to set the ORACLE_HOME and ORACLE_SID environment variables:

• Bourne, Bash, or Korn shell:

  $ ORACLE_HOME=Oracle_home
  $ ORACLE_SID=sid
  $ PATH=$ORACLE_HOME/bin:$ORACLE_HOME/bin/OPatch:$PATH:
  $ export ORACLE_HOME ORACLE_SID PATH
  

• C shell:

  % setenv ORACLE_HOME Oracle_home
  % setenv ORACLE_SID sid
  % setenv PATH $ORACLE_HOME/bin:$ORACLE_HOME/bin/OPatch:$PATH
  

In these examples, Oracle_home is the Oracle home directory where the Oracle Database 11g installation that you want to upgrade is installed, and sid is the system identifier of the database that you want to upgrade. For Oracle RAC installations, sid is generally the sid prefix and the instance number. For example, ORCL1.

7.7 Stop All Processes

Go to the following sections based on the Oracle Database installation type:

• Stopping All Processes for a Single Instance Installation

• Stopping All Processes for an Oracle Clusterware Installation

• Stopping All Processes for an Oracle RAC Installation

• Stopping the Oracle Warehouse Builder (OWB) Control Center

7.8 Back Up the System

Oracle recommends that you create a backup of the Oracle Inventory, Oracle 11g home and Oracle 11g Database before you install the patch set. If you are planning to apply this patch to Oracle RAC, ensure that you create a backup of these components on all nodes before applying the patch.

8.1 Installing the Oracle Database 11g Patch Set Interactively

To install the Oracle Database 11g patch set interactively:

OUI-10091: There are no patches that need to be applied from the patch set Oracle Database 11g Release 1 Patch Set 1
11.1.0.7

1. Log in as the oracle user.

2. If you are not installing the software on the local computer, then run the following command on the remote computer to set the DISPLAY variable:

   • Bourne, Bash, or Korn shell:

     $ export DISPLAY=localhost:0.0
     

   • C shell:

     % setenv DISPLAY local_host:0.0
     

   In this example, local_host is the host name or IP address of the local computer that you want to use to display Oracle Universal Installer.

   Run the following command on the remote computer to check if the shell and the DISPLAY environment variable are set correctly:

   echo $SHELL
   echo $DISPLAY
   

   Now to enable X applications, run the following commands on the local computer:

   $ xhost + [fully_qualified_remote_host_name]
   

   To verify that X applications display is set properly, run an X11-based program that comes with the operating system such as xclock:

   $ xclock
   

   In this example, xclock_path is the directory path. For example, you can find xclock at /usr/X11R6/bin/xclocks. If the DISPLAY variable is set properly, then you can see xclock on your computer screen.

   See Also:

   PC-X Server or Operating System vendor documents for further assistance.

3. Start Oracle Universal Installer located in the unzipped area of the patch set.

   $ cd patchset_directory/Disk1
   $ ./runInstaller
   

4. On the Welcome screen, click Next.

5. In the Specify Home Details screen, select the name of the Oracle home that you want to update, or select the Path that you want to update from the list, then click Next.

6. Enter a valid email ID with password to configure Oracle Configuration manager.

   Note:

   If the page is left blank, then Oracle Configuration Manager can still be configured manually using $ORACLE_HOME/ccr/bin/setupCCR after patchset installation.

   If Oracle Configuration Manager was configured in 11.1.0.6, then this page will not be displayed. In this case, Oracle Configuration Manager would get upgraded to 10.3.0.1.0.

   Click Next.

7. If you are installing the patch set on an Oracle RAC cluster, the Selected Nodes screen appears. The patch set will be installed on these nodes. Click Next.

8. Check for errors, if any, in the Product-Specific Prerequisite Checks and click Next.

9. On the Summary screen, click Install.

   This screen lists all of the patches available for installation.

   Note:

   If you are applying this patch set to an Oracle Clusterware installation, then complete all the steps displayed by the Oracle Universal Installer.

   Oracle Clusterware installation instructions are also available in CRS_home/install/readme.txt.

10. When prompted, run the $ORACLE_HOME/root.sh script as the root user. If you are applying the patch set to an Oracle RAC installation, then run the root.sh script on each node of the cluster.

    Note:

    If you are applying this patch set to an Oracle Clusterware home, Oracle Universal Installer will guide you through several additional steps and prompt you to run the root111.sh script as the root user.

11. On the End of Installation screen, click Exit, then click Yes to exit from Oracle Universal Installer.

8.2 Installing the Oracle Database 11g Patch Set Noninteractively

To install the Oracle Database 11g patch set noninteractively:

1. Copy the response file template provided in the response directory where you unpacked the patch set archive file.

2. Edit the values for all fields labeled as <Value Required> as described by the comments and examples in the template.

3. To run Oracle Universal Installer, enter a command similar to the following, where response_file_path is the full path to the response file that you edited:

   $ ./runInstaller -silent -responseFile response_file_path
   

   Note:

   If you are applying this patch set to an Oracle Clusterware home, then complete all the steps in the CRS_home/install/readme.txt file.

4. After the installation, run the $ORACLE_HOME/root.sh script as the root user. If you are applying the patch set to an Oracle RAC installation, then run the root.sh script on each node of the cluster.

9.1 Upgrading Earlier Oracle Database to Oracle Database 11g Release 1 (11.1.0.7)

Review the following sections before upgrading an earlier Database to Oracle Database 11g release 1 (11.1.0.7):

• Upgrading Earlier Oracle Database Releases to Oracle Database 11g Release 1 (11.1.0.7)

• Upgrading a Release 9.2 Database Not Using Oracle Label Security

9.2 Upgrading Oracle Database 11g Release 11.1.0.6 to Oracle Database 11g Release 11.1.0.7

See one of the following sections for upgrading an Oracle Database 11g release 11.1.0.6 to Oracle Database 11g release 11.1.0.7:

• Upgrading a Release 11.1 Database using Oracle Database Upgrade Assistant

• Manually Upgrading a Release 11.1 Database

Oracle Database 11.1 Pre-Upgrade Information Tool    06-15-2007 09:14:02
.
**********************************************************************
Database:
**********************************************************************
--> name:          ORCL
--> version:       10.2.0.1.0
--> compatible:    10.2.0.1
--> blocksize:     8192
--> timezone file: V2
.
**********************************************************************
Tablespaces: [make adjustments in the current environment]
**********************************************************************
WARNING: --> SYSTEM tablespace is not large enough for the upgrade.
.... currently allocated size: 560 MB
.... minimum required size: 910 MB
.... increase current size by: 350 MB
.... tablespace is NOT AUTOEXTEND ENABLED.
--> UNDOTBS1 tablespace is adequate for the upgrade.
.... minimum required size: 457 MB
.... AUTOEXTEND additional space required: 352 MB
--> SYSAUX tablespace is adequate for the upgrade.
.... minimum required size: 617 MB
.... AUTOEXTEND additional space required: 287 MB
--> TEMP tablespace is adequate for the upgrade.
.... minimum required size: 61 MB
.... AUTOEXTEND additional space required: 41 MB
--> EXAMPLE tablespace is adequate for the upgrade.
.... minimum required size: 69 MB
.
**********************************************************************
Update Parameters: [Update Oracle Database 11.1 init.ora or spfile]
**********************************************************************
WARNING: --> "sga_target" needs to be increased to at least 388 MB
.
**********************************************************************
Renamed Parameters: [Update Oracle Database 11.1 init.ora or spfile]
**********************************************************************
WARNING: --> "plsql_compiler_flags" old value was "INTERPRETED";
new name is "plsql_code_type" new value is "INTERPRETED"
.
**********************************************************************
Obsolete/Deprecated Parameters: [Update Oracle Database 11.1 init.ora or spfile]
**********************************************************************
--> "max_enabled_roles"
--> "remote_os_authent"
--> "background_dump_dest" replaced by "diagnostic_dest"
--> "user_dump_dest" replaced by "diagnostic_dest"
--> "core_dump_dest" replaced by "diagnostic_dest"
.
**********************************************************************
Components: [The following database components will be upgraded or installed]
**********************************************************************
--> Oracle Catalog Views         [upgrade]  VALID
--> Oracle Packages and Types    [upgrade]  VALID
--> JServer JAVA Virtual Machine [upgrade]  VALID
--> Oracle XDK for Java          [upgrade]  VALID
--> Oracle Workspace Manager     [upgrade]  VALID
--> Messaging Gateway            [upgrade]  VALID
--> OLAP Analytic Workspace      [upgrade]  VALID
--> OLAP Catalog                 [upgrade]  VALID
--> Oracle Label Security        [upgrade]  VALID
--> EM Repository                [upgrade]  VALID
--> Oracle Text                  [upgrade]  VALID
--> Oracle XML Database          [upgrade]  VALID
--> Oracle Java Packages         [upgrade]  VALID
--> Oracle interMedia            [upgrade]  VALID
--> Spatial                      [upgrade]  VALID
--> Data Mining                  [upgrade]  VALID
--> Oracle Ultra Search          [upgrade]  VALID
--> Expression Filter            [upgrade]  VALID
--> Rule Manager                 [upgrade]  VALID
--> Oracle Application Express   [upgrade]  VALID
--> Oracle OLAP API              [upgrade]  VALID
.
**********************************************************************
Miscellaneous Warnings
**********************************************************************
WARNING: --> Database is using an old timezone file version.
.... Patch the 10.2.0.1.0 database to timezone file version 4
.... BEFORE upgrading the database. Re-run utlu111i.sql after
.... patching the database to record the new timezone file version.
WARNING: --> Database contains stale optimizer statistics.
.... Refer to the 11g Upgrade Guide for instructions to update
.... statistics prior to upgrading the database.
.... Component Schemas with stale statistics:
....   SYS
....   WMSYS
....   CTXSYS
WARNING: --> Database contains INVALID objects prior to upgrade.
.... USER PUBLIC has 7 INVALID objects.
.... USER FLOWS_010600 has 1 INVALID objects.
.... USER SYS has 1 INVALID objects.
WARNING: --> Database contains schemas with objects dependent on network packages.
.... Refer to the 11g Upgrade Guide for instructions to configure Network ACLs.
.... USER WKSYS has dependent objects.
.... USER SYSMAN has dependent objects.
WARNING: --> EM Database Control Repository exists in the database.
.... Direct downgrade of EM Database Control is not supported. Refer to the
.... 11g Upgrade Guide for instructions to save the EM data prior to upgrade. 

$ cd $ORACLE_HOME/rdbms/lib
$ make -f ins_rdbms.mk dv_off
$ cd $ORACLE_HOME/bin
$ relink oracle

9.3 Updating Oracle Time Zone Definitions

Based on the result you had in Section 7.5, "Update Oracle Time Zone Definitions" regarding the DST (Oracle time zone definitions):

• If the DST version was 4, no action is required.

• If the DST version was higher than 4, reapply the version of DST patches as described in OracleMetaLink document 568125.1, Actions for the DSTv4 update in the 11.1.0.7 patchset.

• If the DST version was lower than 4, restore TSTZ data from backup (if any) after performing the Postinstallation Tasks. For more information, see OracleMetaLink document 568125.1, Actions for the DSTv4 update in the 11.1.0.7 patchset.

9.4 Configuring Oracle Configuration Manager in a Cloned Oracle Home

If Oracle Configuration Manager was configured using Oracle Universal Installer 11.1.0.7.0 and if 11.1.0.7.0 is cloned, then follow these steps in the cloned Oracle home:

1. Run the following command from $ORACLE_HOME/ccr/state.

   rm -rf *.ll*
   

2. Run the following command from $ORACLE_HOME/ccr/inventory.

   cp core.jar pending
   

3. Run these commands from $ORACLE_HOME/ccr/bin.

   ./emSnapshotEnv
    ./deployPackages
   

4. Run this command from $ORACLE_HOME/ccr/bin, and provide the proper credentials.

   ./configCCR
   

If Oracle Configuration Manager was manually configured in 11.1.0.7 using setupCCR, and if Oracle Configuration Manager is cloned, then follow these steps in the cloned Oracle home:

1. Delete all the subdirectories of the $ORACLE_HOME/ccr/hosts directory to remove the previously configured hosts.

2. Run the following command from $ORACLE_HOME/ccr/bin:

   $ configCR -a
   

If you have installed Oracle Configuration Manager in the original Oracle home but have not configured it, then run the following command in the cloned Oracle home to configure it:

$ setupCCR

9.5 Oracle Configuration Manager Behavior in Shared RAC Home

If Oracle Configuration Manager was configured in 11.1.0.6, and the 11.1.0.7 patchset is applied from any of the nodes belonging to the cluster, Oracle Configuration Manager will be configured only on the first node. You should not run $ORACLE_HOME/ccr/bin/emCCRstatus on any of the remaining nodes of the cluster where RAC is installed in shared mode.

If Oracle Configuration Manager is configured using 11.1.0.7 Oracle Universal Installer, then it only gets configured on the nodes from where the patchset is applied.

9.6 Adding a Node in a Patched Oracle Clusterware Installation

As the root user, run the root.sh script on each new node that you add to the patched Oracle Clusterware environment. You must pass the parameter file, $CRS_OH/install/paramfile.crs as an argument to root.sh.

9.7 Locating the Oracle Warehouse Builder Readme

For late-breaking information about Oracle Warehouse Builder, see the Oracle Warehouse Builder Readme, which is installed with the database software under $ORACLE_HOME/owb/doc/ReadMe.htm.

9.8 Upgrading the Oracle Warehouse Builder Version

After upgrade to 11.1.0.7.0, DBA_REGISTRY continues to show version 11.1.0.6.0 for Oracle Warehouse Builder. Follow the steps described in $ORACLE_HOME/owb/doc/Readme.htm to manually upgrade the Oracle Warehouse Builder version from 11.1.0.6.0 to 11.1.0.7.0.

9.9 Configuring Oracle Warehouse Builder for an Oracle RAC Environment

If you use Oracle Warehouse Builder Release 11.1.0.6; that is, you set up the OWB repository and workspaces, and you are using OWB functionality in an Oracle RAC environment, perform the following steps prior to using OWB functionality in 11.1.0.7:

On the local Oracle RAC node, locate $ORACLE_HOME/bin/oratclsh and copy the binary to all the remote Oracle RAC nodes of the 11.1.0.7 installation.

9.10 Upgrading Analytic Workspace Manager and OLAP Client Applications

Please upgrade your Analytic Workspace Manager (AWM) to version 11.1.0.7.0. Go to OracleMetalink for instructions.

With AWM 11.1.0.7, you can create standard 11.1 analytic workspaces or 10.2 style analytic workspaces. To create a 10.2 style analytic workspace, choose the 10.2 cube type when creating a new analytic workspace.

If you wish to use existing OLAP 11.1.0.6.0 or 11.1.0.6.0A client applications with the 11.1.0.7.0 database, you must upgrade the run-time OLAP API JAVA code to 11.1.0.7.0.After installing the 11.1.0.7.0 RDBMS patch, locate the olap_api.jar file in ORACLE_HOME/olap/api/lib. Insert this newer 11.1.0.7.0 jar file in your application's JAVA class path, and omit any previous pointers to the 11.1.0.6.0 or 11.1.0.6.0A jar file.

9.11 Configuring a User for Oracle Data Mining

Demo programs that illustrate the Data Mining APIs (PL/SQL and Java) are installed with Oracle Database Examples. Two scripts, dmsh.sql and dmshgrants.sql, must be run prior to using the demo programs.

dmshgrants.sql assigns the privileges needed to use the demo programs. After upgrade to 11.1.0.7.0, the syntax for invoking dmshgrants.sql is:

@ $ORACLE_HOME/RDBMS/demo/dmshgrants dmuser_name

See Oracle Data Mining Administrator's Guide for details about dmsh.sql, dmshgrants.sql, and the Oracle Data Mining demo programs.

9.12 Installing 11.1.0.6 Components In an 11.1.0.7 Oracle Home

If you want to install or reinstall additional components from 11.1.0.6 (for example, Oracle Spatial) into an 11.1.0.7 Oracle Home, use the 11.1.0.7 Oracle Universal Installer found in $ORACLE_HOME/oui/bin.

10.1 Removing the Patch Set Software for Single Instance Installation

Perform the following steps for removing the 11.1.0.7 patch set:

1. Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:

   $ sqlplus /NOLOG
   SQL> CONNECT SYS AS SYSDBA
   Enter password: SYS_password
   SQL> SHUTDOWN IMMEDIATE
   SQL> EXIT
   

2. Take a backup of the following files in the Oracle home directory:

   $ORACLE_HOME/rdbms/admin/catrelod.sql
   $ORACLE_HOME/network/admin/tnsnames.ora
   

   Note:

   If the database has Database Vault configured, then disable Database Vault by following these steps before running catdwgrd.sql:

   $ cd $ORACLE_HOME/rdbms/lib
   $ make -f ins_rdbms.mk dv_off
   $ cd $ORACLE_HOME/bin
   $ relink oracle
   

3. Enter the following SQL*Plus commands:

   $ cd $ORACLE_HOME
   $ sqlplus /NOLOG
   SQL> CONNECT SYS AS SYSDBA
   Enter password:SYS_password
   SQL> STARTUP DOWNGRADE
   SQL> DROP USER SYSMAN CASCADE
   SQL> SPOOL downgrade.out
   SQL> @?/rdbms/admin/catdwgrd.sql
   SQL> SPOOL OFF
   SQL> SHUTDOWN IMMEDIATE
   SQL> EXIT
   

4. Review the downgrade.out file for errors.

5. Restore the Oracle 11g installation and central inventory that you backed up before applying the patch set. (See /etc/oraInst.loc.)

   Note:

   If the database that you backed up had Database Vault configured, then follow these steps to disable Database Vault before running catrelod.sql:

   $ cd $ORACLE_HOME/rdbms/lib
   $ make -f ins_rdbms.mk dv_off
   $ cd $ORACLE_HOME/bin 
   $ relink oracle
   

6. After restoring the original Oracle home, copy the saved version of catrelod.sql into the restored $ORACLE_HOME/rdbms/admin directory and the saved version of tnsnames.ora into the restored $ORACLE_HOME/network/admin/tnsnames.ora file.

   Perform the following steps.

   $ sqlplus /NOLOG
   SQL> CONNECT SYS AS SYSDBA
   Enter password:SYS_password
   SQL> STARTUP DOWNGRADE
   SQL> SPOOL catrelod.out
   SQL> @?/rdbms/admin/catrelod.sql
   SQL> SPOOL OFF
   SQL> SHUTDOWN IMMEDIATE
   

7. Review the catrelod.out file for errors.

   Note:

   After reloading the 11.1.0.6 release, the version number for Oracle OLAP Analytic Workspace remains at 11.1.0.7, although the downgrade process is successful. This issue is tracked with Oracle bug 6975997.

   Note:

   If the database had Database Vault configured prior to the upgrade, then re-enable Database Vault by following these steps:

   $ cd $ORACLE_HOME/rdbms/lib
   $ make -f ins_rdbms.mk dv_on
   $ cd $ORACLE_HOME/bin
   $ relink oracle
   

   For RAC installations, re-enable Database Vault on each node.

8. Start the database and recompile the remaining invalid objects:

   SQL> STARTUP
   SQL> @?/rdbms/admin/utlrp.sql
   

   Cross-check the status of installed components with the following script:

   SQL> SELECT COMP_NAME, VERSION, STATUS FROM SYS.DBA_REGISTRY;
   

9. Restore the original Enterprise Manager Database Control. Refer to Oracle Database Upgrade Guide for details.

10.2 Removing the Patch Set Software for Oracle RAC Installation

Perform the following steps for removing the patch set from the 11.1.0.7 patch release:

1. Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:

   $ sqlplus /NOLOG
   SQL> CONNECT SYS AS SYSDBA
   Enter password:SYS_password
   

2. Set the CLUSTER_DATABASE initialization parameter to FALSE:

   Note:

   If the system uses an initialization parameter file, change the value of the CLUSTER_DATABASE initialization parameters to TRUE in the initialization parameter file (initsid.ora).

   SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile; 
   

3. Exit SQL*Plus and shut down the database:

   $ srvctl stop database -d db_name
   

4. Take a backup of the following files in 11.1.0.7 Oracle home directory:

   $ORACLE_HOME/rdbms/admin/catrelod.sql
   $ORACLE_HOME/network/admin/tnsnames.ora
   

   Note:

   If the database has Database Vault configured, then disable Database Vault by following these steps before running catdwgrd.sql:

   $ cd $ORACLE_HOME/rdbms/lib
   $ make -f ins_rdbms.mk dv_off
   $ cd $ORACLE_HOME/bin
   $ relink oracle
   

   Disable Database Vault on each node.

5. Enter the following SQL*Plus commands:

   $ sqlplus /NOLOG
   SQL> CONNECT SYS AS SYSDBA
   Enter password:SYS_password
   SQL> STARTUP DOWNGRADE
   SQL> DROP USER SYSMAN CASCADE
   SQL> SPOOL catdwgrd.out
   SQL> @?/rdbms/admin/catdwgrd.sql
   SQL> SPOOL OFF
   SQL> SHUTDOWN IMMEDIATE
   SQL> EXIT
   

6. Restore the Oracle 11g installation and central inventory that you backed up before applying the patch set. (See /etc/oraInst.loc.)

   Note:

   If the database that you backed up had Database Vault configured, then follow these steps to disable Database Vault before running catrelod.sql:

   $ cd $ORACLE_HOME/rdbms/lib
   $ make -f ins_rdbms.mk dv_off
   $ cd $ORACLE_HOME/bin 
   $ relink oracle
   

   Disable Database Vault on each node.

7. After restoring the original Oracle home, copy the saved version of catrelod.sql into the restored $ORACLE_HOME/rdbms/admin directory and the saved version of tnsnames.ora into the restored $ORACLE_HOME/network/admin/tnsnames.ora file.

8. Enter the following SQL*Plus commands:

   $ sqlplus /NOLOG
   SQL> CONNECT SYS AS SYSDBA
   Enter password:SYS_password
   SQL> STARTUP DOWNGRADE
   SQL> SPOOL catrelod.out
   SQL> @$/rdbms/admin/catrelod.sql
   SQL> SPOOL OFF
   SQL> SHUTDOWN IMMEDIATE
   

9. Review the catrelod.out file for errors.

   Note:

   After reloading the 11.1.0.6 release, the version number for Oracle OLAP Analytic Workspace remains at 11.1.0.7, although the downgrade process is successful. This issue is tracked with Oracle bug 6975997.

10. Start the database and recompile the remaining invalid objects:

    SQL> STARTUP
    SQL> @?/rdbms/admin/utlrp.sql
    

    Cross-check the status of installed components with the following script:

    SQL> SELECT COMP_NAME, VERSION, STATUS FROM SYS.DBA_REGISTRY;
    

11. Set the CLUSTER_DATABASE initialization parameter to TRUE:

    Note:

    If the system uses an initialization parameter file, change the value of the CLUSTER_DATABASE initialization parameters to TRUE in the initialization parameter file (initsid.ora).

    SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;
    SQL> SHUTDOWN
    SQL> EXIT
    

12. Start the database:

    $ srvctl start database -d db_name
    

13. Restore the original Enterprise Manager Database Control. Refer to Oracle Database Upgrade Guide for details.

$ cd $ORACLE_HOME/rdbms/lib
$ make -f ins_rdbms.mk dv_on
$ cd $ORACLE_HOME/bin
$ relink oracle

12.1 Invalid Objects in Database After Downgrade from 11.1.0.7 to 10.1.0.5 Oracle RAC

After downgrading Oracle RAC from 11.1.0.7 to 10.1.0.5, the DBMS_XDBT package may be invalid.

Workaround: This problem can be fixed by applying patch 7294492 to the 10.1.0.5 database prior to downgrading.

This issue is tracked with Oracle bug 7294492.

12.2 Verify Patch Step in Oracle Enterprise Manager Database Control Reports Failure

When using Oracle Enterprise Manager Database Control to apply the 11.1.0.7 patch set to an 11.1.0.6 database, the Verify Patch step indicates failure.

Workaround: If failure of this step is reported erroneously and the patch set was applied correctly, you can ignore this step so that the deployment procedure completes the remaining deployment steps.

This issue is tracked with Oracle bug 7029376.

12.3 Oracle Text PDF Filtering Performance Issue

PDF filtering may be up to five times slower in 11.1.0.7 than it was in 11.1.0.6. In 11.1.0.7, Oracle Text uses Oracle Outside In HTML Export for document filtering. In 11.1.0.6, Oracle Text used filtering technology licensed from Autonomy, Inc.

See Notes to Oracle Text Users for information about migration to Oracle Outside In HTML Export in 11.1.0.7.

This issue is tracked with Oracle bug 7284546.

12.4 Oracle Text CTX_DOC.IFILTER() Not Preserving PDF Multi-Column Format

CTX_DOC.IFILTER() invoked on PDF content does not preserve multi-column format since migration to Oracle Outside In HTML Export in Oracle Text 11.1.0.7.

See Notes to Oracle Text Users for information about migration to Oracle Outside In HTML Export in 11.1.0.7.

This issue is tracked with Oracle bug 7321265.

12.5 Question Marks Displayed by Oracle Database Control

After upgrading from Oracle 10g to 11.1.0.7 or from Oracle 11.1.0.6 to 11.1.0.7 using Database Upgrade Assistant, several question marks are displayed on the Database Console main page.

Workaround: Drop the content in the table sysman.mgmt_db_latest_hdm_findings. Then set the NLS_LANG parameter with the correct value and restart Database Console.

This issue is tracked with Oracle bug 7331605.

12.6 SQL Developer Upgrade Issue

On upgrade to 11.1.0.7, SQL Developer 1.1.3 will not connect to an 11g database and will return an error.

Workaround: Upgrade to SQL Developer 1.5.1. It can be downloaded from http://sqldeveloper.oracle.com.

This issue is tracked with Oracle bug 6991260.

12.7 Problem Adding Oracle OLAP to an Existing 11.1.0.7 Oracle Home

The normal process for adding additional components to a patched (11.1.0.7) Oracle home consists of the following two steps:

1. Perform a "Custom" database install from the 11.1.0.6 installation media and install the additional database option.

2. Re-apply the 11.1.0.7 database patchset to this Oracle home to upgrade the newly installed option to version 11.1.0.7.

When following this procedure to add Oracle OLAP to an existing 11.1.0.7 Oracle home, you will run into an error relinking the oracle binary in step 1. This error is due to a mismatch in the 11.1.0.6 and 11.1.0.7 symbols that must be resolved before linking can succeed. These errors are ignorable, and can be safely ignored when they occur during the installation. The re-application of the 11.1.0.7 patchset in step 2 will remove this inconsistency and the oracle binary will be relinked properly as part of that step.

This issue is tracked with Oracle bug 7384140.

12.8 Section of Database Upgrade Assistant Summary Page Not Translated into Japanese

When you use the Japanese version of Oracle Database Upgrade Assistant to upgrade a database to 11.1.0.7, you will find that the Database Instance section on the Summary page is not translated into Japanese.

This issue is tracked with Oracle bug 6968202.

12.9 File Not Found Issues in Silent Log Generated for Cloning

After cloning, the Silent.log file generated as part of cloning will have the following "File not found" issues:

File not found $ClonedOH/sysman/config/lfm_efiles.template

File not found $ClonedOH/sysman/config/lfm_ifiles.template1

Workaround: Just before starting the Clone command, copy the files lfm_efiles.template and lfm_ifiles.template from source_Oracle_home/sysman/config to cloned_Oracle_home/sysman/config, and rename the files to lfm_efiles.template1 and lfm_ifiles.template1 respectively.

This issue is tracked with Oracle bug 7373611.

12.10 When Invoked by Non-Default User, Database Configuration Assistant Throws Text on Prompt

If Oracle 11.1.0.7 is installed by a user other than default user, Database Configuration Assistant will throw text such as the following on prompt:

sh: /tmp/LinuxRelease_output.txt: Permission denied

sh: /tmp/LinuxRelease_output.txt: Permission denied

Workaround: These errors can be ignored.

This issue is tracked with Oracle bug 7028409.

12.11 Downgrade Issues

Oracle may terminate with an ORA-03113 error when downgrading from 11.1.0.7 to 10.2.0.3.

Workaround: Apply patch 6118038 to the 10.2.0.3 Oracle home prior to downgrading.