7月最新发布11.2.0.1.2 Patch set update

2.3.1 Patch Pre-Installation Instructions

2.3.2 Patch Installation Instructions

1. If you are using a Data Guard Physical Standby database, you must first install this patch on the primary database before installing the patch on the physical standby database. It is not supported to install this patch on the physical standby database before installing the patch on the primary database. For more information, see My Oracle Support Note 278641.1.
2. Do one of the following, depending on whether this is a RAC environment:
   • If this is a RAC environment, choose one of the patch installation methods provided by OPatch (rolling, all node, or minimum downtime), and shutdown instances and listeners as appropriate for the installation method selected.This PSU patch is rolling RAC installable. Refer to My Oracle Support Note 244241.1 Rolling Patch - OPatch Support for RAC.
   • If this is not a RAC environment, shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.
3. Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:

   unzip p9654983_11201_<platform>.zip
   cd 9654983
   opatch apply
   

4. If there are errors, refer to Section 3, "Known Issues".

2.3.3 Patch Post-Installation Instructions

1. Apply conflict resolution patches as explained in Section 2.3.3.1.
2. Load modified SQL files into the database, as explained in Section 2.3.3.2.

2.3.4 Patch Post-Installation Instructions for Databases Created or Upgraded after Installation of PSU 11.2.0.1.2 in the Oracle Home

• Using DBCA (Database Configuration Assistant) to select a sample database (General, Data Warehouse, Transaction Processing)
• Using a script that was created by DBCA that creates a database from a sample database

2.4.1 Patch Deinstallation Instructions for a Non-RAC Environment

1. Verify that an $ORACLE_HOME/rdbms/admin/catbundle_PSU_<database SID>_ROLLBACK.sql file exists for each database associated with this ORACLE_HOME. If this is not the case, you must execute the steps in Section 2.3.3.2, "Loading Modified SQL Files into the Database" against the database before deinstalling the PSU.
2. Shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.
3. Run the OPatch utility specifying the rollback argument as follows.

   opatch rollback -id 9654983
   

4. If there are errors, refer to Section 3, "Known Issues".

2.4.2 Patch Post-Deinstallation Instructions for a Non-RAC Environment

1. Start all database instances running from the Oracle home. (For more information, see Oracle Database Administrator's Guide.)
2. For each database instance running out of the ORACLE_HOME, connect to the database using SQL*Plus as SYSDBA and run the rollback script as follows:

   cd $ORACLE_HOME/rdbms/admin
   sqlplus /nolog
   SQL> CONNECT / AS SYSDBA
   SQL> STARTUP
   SQL> @catbundle_PSU_<database SID>_ROLLBACK.sql
   SQL> QUIT
   

   In a RAC environment, the name of the rollback script will have the format catbundle_PSU_<database SID PREFIX>_ROLLBACK.sql.
3. Check the log file for any errors. The log file is found in $ORACLE_HOME/cfgtoollogs/catbundle and is named catbundle_PSU_<database SID>_ROLLBACK_<TIMESTAMP>.log where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to Section 3, "Known Issues".

2.4.3 Patch Deinstallation Instructions for a RAC Environment

1. Shut down the instance on the node.
2. Run the OPatch utility specifying the rollback argument as follows.

   opatch rollback -id 9654983
   

   If there are errors, refer to Section 3, "Known Issues".
3. Start the instance on the node as follows:

   srvctl start instance
   

2.4.4 Patch Post-Deinstallation Instructions for a RAC Environment