| Oracle® Fusion Applications Upgrade Guide 11g Release 7 (11.1.7) Part Number E35833-18 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Applications Upgrade Guide 11g Release 7 (11.1.7) Part Number E35833-18 |
|
|
PDF · Mobi · ePub |
This chapter describes how to update your Oracle Fusion Applications database before an upgrade.
Note:
This is a downtime activity and can be planned and performed in a separate downtime window prior to the upgrade.
If you are upgrading from Release 5, and you use Oracle Exadata Database Machine, start with Section 3.1, "Apply Exadata Patches for Release 6". If you are upgrading from Release 5 and you do not use Oracle Exadata Database Machine, start with Section 3.2, "Run RUP Lite for RDBMS for the Upgrade From Release 5 to Release 6"
If you are upgrading from Release 6, and you use Oracle Exadata Database Machine, start with Section 3.3, "Apply Exadata Patches for Release 7". If you are upgrading from Release 6, and you do not use Oracle Exadata Database Machine, start with Section 3.4, "Run RUP Lite for RDBMS for Upgrade to Release 7".
Note:
It is a best practice to apply these patches on Oracle Identity Management databases to keep both the Oracle Fusion Application database and Oracle Identity Management databases synchronized. It is also a best practice to back up your Oracle Fusion Applications and Oracle Identity Management databases before patching. For more information, see "Backing Up and Recovering Oracle Fusion Applications" in the Oracle Fusion Applications Administrator's Guide.
If you use Oracle Exadata Database Machine, manually apply the patches listed in this section, followed by any patches you downloaded in Section 2.3.5, "Download and Unzip Repository and Patches for the Upgrade from Release 5 to Release 6". Do not run RUP Lite for RDBMS.
If you are on Linux64, Solaris Sparc64, or Solaris86-64 platforms and use the Oracle Exadata Database Machine, download and apply the quarterly database patch for your platform, the generic patches in the following list, and the list of specific patches for your platform from My Oracle Support.
After applying the patches for your platform, proceed to Section 3.3, "Apply Exadata Patches for Release 7".
Apply the quarterly database patch (Patch 14474780 - QUARTERLY DATABASE PATCH FOR EXADATA (OCT 2012 - 11.2.0.3.11) for your platform:
Linux: p14474780_112030_Linux-x86-64.zip
Solaris Sparc64: p14474780_112030_SOLARIS64.zip
Solaris86-64: p14474780_112030_Solaris86-64.zip
Apply the following generic patches, which are not platform-specific:
p12317925_112030_Generic.zip
p13508115_112030_Generic.zip
p14698700_112030_Generic.zip
Apply the following Exadata patches if you are on the Linux64 platform:
p12552578_1120311ExadataDatabase_Linux-x86-64.zip
p12646746_112030_Linux-x86-64.zip
p12977501_112030_Linux-x86-64.zip
p12985184_112030_Linux-x86-64.zip
p13014128_112030_Linux-x86-64.zip
p13078786_112030_Linux-x86-64.zip
p13365700_112030_Linux-x86-64.zip
p13404129_112030_Linux-x86-64.zip
p13615767_1120311ExadataDatabase_Linux-x86-64.zip
p13632653_112030_Linux-x86-64.zip
p13714926_1120311ExadataDatabase_Linux-x86-64.zip
p13902963_1120311ExadataDatabase_Linux-x86-64.zip
p14029429_112030_Linux-x86-64.zip
p14058884_112030_Linux-x86-64.zip
p14164849_112030_Linux-x86-64.zip
p14226599_112030_Linux-x86-64.zip
p14499293_1120311ExadataDatabase_Linux-x86-64.zip
p14653598_1120311ExadataDatabase_Linux-x86-64.zip
p14679292_112030_Linux-x86-64.zip
p14741727_1120311ExadataDatabase_Linux-x86-64.zip
p14757709_1120311ExadataDatabase_Linux-x86-64.zip
p14793338_1120311ExadataDatabase_Linux-x86-64.zip
p14837414_1120311ExadataDatabase_Linux-x86-64.zip
p15843238_1120311ExadataDatabase_Linux-x86-64.zip
Apply the following Exadata patches if you are on the Solaris Sparc64 platform:
p12552578_1120311ExadataDatabase_SOLARIS64.zip
p12646746_112030_SOLARIS64.zip
p12977501_112030_SOLARIS64.zip
p12985184_112030_SOLARIS64.zip
p13014128_112030_SOLARIS64.zip
p13078786_112030_SOLARIS64.zip
p13365700_112030_SOLARIS64.zip
p13404129_112030_SOLARIS64.zip
p13615767_1120311ExadataDatabase_SOLARIS64.zip
p13632653_112030_SOLARIS64.zip
p13714926_1120311ExadataDatabase_SOLARIS64.zip
p13902963_1120311ExadataDatabase_SOLARIS64.zip
p14029429_112030_SOLARIS64.zip
p14058884_112030_SOLARIS64.zip
p14164849_112030_SOLARIS64.zip
p14226599_112030_SOLARIS64.zip
p14499293_1120311ExadataDatabase_SOLARIS64.zip
p14653598_1120311ExadataDatabase_SOLARIS64.zip
p14679292_112030_SOLARIS64.zip
p14741727_1120311ExadataDatabase_SOLARIS64.zip
p14757709_1120311ExadataDatabase_SOLARIS64.zip
p14793338_1120311ExadataDatabase_SOLARIS64.zip
p14837414_1120311ExadataDatabase_SOLARIS64.zip
p15843238_1120311ExadataDatabase_SOLARIS64.zip
Apply the following Exadata patches if you are on the Solaris X64 platform:
p12552578_1120311ExadataDatabase_Solaris86-64.zip
p12646746_112030_Solaris86-64.zip
p12977501_112030_Solaris86-64.zip
p12985184_112030_Solaris86-64.zip
p13014128_112030_Solaris86-64.zip
p13078786_112030_Solaris86-64.zip
p13365700_112030_Solaris86-64.zip
p13404129_112030_Solaris86-64.zip
p13615767_1120311ExadataDatabase_Solaris86-64.zip
p13632653_112030_Solaris86-64.zip
p13714926_1120311ExadataDatabase_Solaris86-64.zip
p13902963_1120311ExadataDatabase_Solaris86-64.zip
p14029429_112030_Solaris86-64.zip
p14058884_112030_Solaris86-64.zip
p14164849_112030_Solaris86-64.zip
p14226599_112030_Solaris86-64.zip
p14499293_1120311ExadataDatabase_Solaris86-64.zip
p14653598_1120311ExadataDatabase_Solaris86-64.zip
p14679292_112030_Solaris86-64.zip
p14741727_1120311ExadataDatabase_Solaris86-64.zip
p14757709_1120311ExadataDatabase_Solaris86-64.zip
p14793338_1120311ExadataDatabase_Solaris86-64.zip
p14837414_1120311ExadataDatabase_Solaris86-64.zip
p15843238_1120311ExadataDatabase_Solaris86-64.zip
Proceed to Section 3.3, "Apply Exadata Patches for Release 7."
Run the RUP Lite for RDBMS utility to perform the tasks required to update your Oracle Fusion Applications database before you upgrade. RUP Lite for RDBMS can be run in the following modes:
Validate mode:
Validates database parameters as described in Table 3-1
Set database parameters mode:
Sets database parameters to the values described in Table 3-1, if required
Restarts the database instance, if requested
Apply mode:
Stops the listener and shuts down the database instance (optional)
Configures Oracle Configuration Manager (OCM) in disconnected mode, if required
Unzips Opatch, if it is available in REPOSITORY_LOCATION
Applies patch set updates (PSUs) and one-off patches in REPOSITORY_LOCATION
Applies downloaded one-off patches in the 11.1.7.0.0_post_repo_patches directory
Starts the listener and the database instance (optional)
Runs catbundle.sql if any PSUs were applied
Runs catmetx.sql
Apply Post Changes mode:
Performs SQL*Plus actions after patches apply
Table 3-1 displays the recommendations for tuning the database parameters. The validate mode of RUP Lite for RDBMS verifies whether these parameters contain the recommended value. The setdbparameter mode of RUP Lite for RDBMS updates the parameters to the recommended value.
Table 3-1 Recommended Values for Database Parameters
| Parameter | Type | Location | Recommendation |
|---|---|---|---|
|
DISK_ASYNCH_IO |
Disk IO |
Spfile/pfile |
true |
|
FILESYSTEMIO_OPTIONS |
Disk IO |
Spfile/pfile |
unset so the database chooses a default value based on the platform |
|
INBOUND_CONNECT_TIMEOUT_listener_name |
Connection timeout |
TNS_ADMIN/listener.ora |
120 |
|
SQLNET.INBOUND_CONNECT_TIMEOUT |
Connection timeout |
TNS_ADMIN/sqlnet.ora |
130 |
|
ACTIVE_SESSION_LEGACY_BEHAVIOR |
Initialization |
Spfile/pfile |
true |
RUP Lite for RDBMS uses non-interactive OPatch calls to apply RDBMS patches. OPatch tries to install and configure Oracle Configuration Manager (OCM) if OCM has not already been installed and configured. This causes non-interactive OPatch calls to fail in some cases. To avoid this issue, Oracle recommends that you install OCM prior to running RUP Lite for RDBMS. If you plan to use OCM, you should configure it after you install it. If you do not plan to use OCM, you can either configure it in disconnected mode or let RUP Lite for RDBMS configure it. If you install OCM and do not configure it, RUP Lite for RDBMS will automatically configure it in disconnected mode. For more information, see "Installing Oracle Configuration Manager Using the Command Line Interface" in the Oracle Configuration Manager Installation and Administration Guide.
Run RUP Lite for RDBMS to apply the mandatory Oracle Database patches mentioned in the "Oracle Database" section of Oracle Fusion Applications release notes. This step applies Oracle Database patches that reside in both the REPOSITORY_LOCATION and the 11.1.6.0.0_post_repo_patches directories, which you downloaded in Section 2.3.5, "Download and Unzip Repository and Patches for the Upgrade from Release 5 to Release 6". Follow the steps in Section 3.2.1, "Run RUP Lite for RDBMS".
If you are running Oracle Fusion Applications on a RAC database, follow the steps in Section 3.2.2, "Run RUP Lite for RDBMS in a RAC Database".
Perform the following steps to run RUP Lite for RDBMS in three modes: validate, setdbparameters, and apply:
Verify that your OPatch version is 11.2.0.3.3. If the OPatch version is different, then apply the version of OPatch that is delivered in the Release 6 Repository. It is available at REPOSITORY_LOCATION/installers/database/opatch/p6880880_112000_Linux-x86-64.zip.
Copy the TPBundler.zip file to any temporary directory, such as work_dir in the following example:
cp REPOSITORY_LOCATION/installers/pre_install/TPBundler.zip work_dir
Unzip TPBundler.zip in the work_dir directory, which contains the following files after unzipping:
createTPBundle.jar createTPBundle.cmd createTPBundle.sh ojdl.jar tpBundleConfig_DB.xml tpBundleConfig_IDM.xml tpBundleConfig_OHS.xml README.txt
The createTPBundler utility creates the RDBMS patch bundle, DBPatches.zip, and RUP Lite for RDBMS. This patch bundle contains the mandatory prerequisite patches that are delivered in REPOSITORY_LOCATION as well as any patches you may have downloaded.
Use the following command syntax to run createTPBundler, which creates DBPatches.zip in a temporary directory, referred to as work_dir in the example. Note that work_dir must have read/write permissions.
(UNIX) sh createTPBundle.sh -shiphomelocation REPOSITORY_LOCATION -tempdir work_dir -target DB [-patchdownloadloc location_of_downloaded_patches] (Windows) createTPBundle.cmd -shiphomelocation REPOSITORY_LOCATION -tempdir work_dir -target DB [-patchdownloadloc location_of_downloaded_patches]
The following options are available for createTPBundler:
-shiphomelocation: Location of the createTPBundler repository.
-tempdir: Destination directory to which the generated zip file was copied.
-target: Target against which the copy should be initiated. Valid values are IDM, DB, OH. Use the DB value.
-patchdownloadloc: Location of the patch directory where you downloaded the patches in Section 2.3.5, "Download and Unzip Repository and Patches for the Upgrade from Release 5 to Release 6". Use this option only if you downloaded patches to a directory other than the default patch download directory, which is 11.1.6.0.0_post_repo_patches.
-logfile: Full path of the createTPbundle log file. The default is createTPBundle.log in the current directory.
-loglevel: Log level for the createTPbundler utility. Valid values are SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST. The default value is INFO.
Copy DBPatches.zip to any temporary directory on the database server host.
Log in to the database server host.
Unzip DBPatches.zip to any temporary directory on the database server host. The following subdirectories and files exist after unzipping.
|-- DB_timestamp -- db_server_bundle |-- README.txt |-- bin | |-- ruplite.bat | |-- ruplite.sh |-- metadata | |-- env.properties | |-- installer.properties | |-- plugin-metadata.txt |-- custom_db_server | -- database | -- patch | -- downloaded one-off patches |-- db_server | |-- database | |-- opatch | | -- OPatch zip file | |-- patch | | -- One-off patches in repository | |-- psu | | -- Patch Set Updates in repository |-- db | |--RUP Lite related files |-- lib | |--RUP Lite related files |-- ruplite | |--RUP Lite related files |-- techpatch | |--TPU related files
Perform this step only if you are running RUP Lite for RDBMS on an Oracle VM environment.
As the root user, change the permissions on the DB_timestamp subdirectory:
chmod -R 777 DB_timestamp
Exit out of root user to ensure that you do not perform the remaining steps as root.
Set executable permissions on ruplite.sh. (UNIX only)
chmod -R 755 DB_timestamp/db_server_bundle/bin/ruplite.sh
Set the JAVA_HOME environment variable as shown in the following example:
(UNIX) setenv JAVA_HOME java_home_location (must be jdk6) (Windows) set JAVA_HOME=java_home_location (must be jdk6)
Update the following properties in the work_dir/DB_timestamp/db_server_bundle/metadata/env.properties file. Example values are shown.
ORACLE_SID: Use an instance name that belongs to the fusionapps database.
ORACLE_HOME: Use an Oracle home directory on which patches must be applied, such as /u01/db/11.2.0.3.
TNS_ADMIN: Use a valid location that contains SQL*Net configuration files for the database.
LISTENER_NAME: Use a listener name.
PFILE=/u01/db/11.2.0.3/dbs/init.ora, for example. You can retrieve this value by running the following query:
select NAME, VALUE from v$parameter where NAME like '%file%';
Update the PFILE property if your database is started using pfile.
DBSERVER_RESTART=true or false.
To minimize downtime, you can use "false" for setdbparameters mode, and "true" for apply mode.
If DBSERVER_RESTART is set to "false", the database server, listener and other related services must be manually stopped before running RUP Lite in apply mode. Then after running RUP Lite in apply mode, you must manually run Steps a through d.
If the value for this property is set to "true", RUP Lite automatically stops the listener and database before applying patches. In addition, RUP Lite automatically performs the following actions after applying patches when DBSERVER_RESTART=true:
Start the database instance.
Start the listener.
Run catbundle.sql with arguments "psu apply" on non-windows and "winbundle apply" on windows.
(UNIX) $ORACLE_HOME/rdbms/admin/catbundle.sql psu apply (Windows) %ORACLE_HOME%\rdbms\admin\catbundle.sql winbundle apply
For a list of catbundle.sql errors that can be ignored, see Section 6.19.17, "Ignorable Errors Reported by catbundle.sql".
Run ORACLE_HOME/rdbms/admin/catmetx.sql.
(UNIX) $ORACLE_HOME/rdbms/admin/catmetx.sql (Windows) %ORACLE_HOME%\rdbms\admin\catmetx.sql
Verify that the java version is 1.6 or above by using the following command:
(UNIX) $JAVA_HOME/bin/java -version (Windows) %JAVA_HOME%\bin\java -version
If your version is lower, download 1.6 or a higher version from My Oracle Support.
Stop all user applications.
Change directory to the following location:
DB_timestamp/db_server_bundle/bin
Run RUP Lite for RDBMS in validate mode. The database instance and listener must be up.
(UNIX) ruplite.sh validate (Windows) ruplite.bat validate
Review the log file, output/logs/ruplitedbvalidate.log, to confirm whether the database parameters contain the values you set in Step 11 and the values displayed in Table 3-1, "Recommended Values for Database Parameters". If any errors occurred, you can find them in this log file.
If any of the parameters do not contain the recommended value, proceed to the next step to run RUP Lite for RDBMS in setdbparameters mode. If all parameters are correct, proceed to Step 19 to run RUP Lite for RDBMS in apply mode.
Run RUP Lite for RDBMS in setdbparameters mode. The database instance and listener must be up.
(UNIX) ruplite.sh setdbparameters (Windows) ruplite.bat setdbparameters
Review the log file, output/logs/ruplitedbsetdbparameters.log, to confirm whether the database parameters contain the values displayed in Table 3-1, "Recommended Values for Database Parameters". If any errors occurred, you can find them in this log file also.
Running RUP Lite for RDBMS in apply mode starts and stops only the Fusion Applications database listener and the database server. You must stop any other applications or processes that are running from the Oracle Fusion Applications home directory, except the OPSS Security Store, before you run RUP Lite for RDBMS. For more information, see "Starting and Stopping" in the Oracle Fusion Applications Administrator's Guide. Also confirm that the BI presentation servers are shut down.
You can set the parameter DBSERVER_RESTART (available in metadata/env.properties) to "false" if you want to manually shut down the database, stop the listener before patching, and start it up after applying the patches. For Windows, if you set DBSERVER_RESTART to "false", follow the steps in Section 3.4.3, "Stop Services on Windows Before Running RUP Lite For RDBMS".
Note:
To avoid an issue with active files while patching, ensure that no applications or processes are running from the ORACLE_HOME that is referenced in metadata/env.properties. If DBSERVER_RESTART=true, you can ignore the database instance and listener processes because RUP Lite brings them down.
Run RUP Lite for RDBMS in apply mode.
(UNIX) ruplite.sh (Windows) ruplite.bat
Review the following log files located under the output/logs directory if any errors occurred:
ruplitedb.log tp_property_editor_timestamp.log db_apply_downloaded_patches_timestamp.log db_apply_repository_patches_timestamp.log db_validate_downloaded_patches_timestamp.log db_validate_repository_patches_timestamp.log downloaded_patch_validate_results_timestamp.xml repository_patch_validate_results_timestamp.xml post_db_restart_actions_timestamp.log
If RUP Lite for RDBMS fails, resolve the issue reported in the log files. When you restart a failed session, RUP Lite for RDBMS ignores the successful actions, starts with the failed action, and proceeds from that point.
The post_db_restart_actions_timestamp.log file includes the output from catbundle.sql and catmetx.sql. For a list of catbundle.sql errors that can be ignored, see Section 6.19.17, "Ignorable Errors Reported by catbundle.sql".
If you set DBSERVER_RESTART to "false", perform the steps in Step 11, a. through d.
You must manually execute any manual steps that are documented in the README.txt file of the patches you applied with RUP Lite for RDBMS. RUP Lite for RDBMS does not execute manual steps from the README.txt file of the patch.
Proceed to Section 3.2.3, "Run Additional Post Database Start Scripts for Patches for Release 6".
Perform the following steps to run RUP Lite for RDBMS in a RAC database. You must run RUP Lite for RDBMS on all available file systems. This may involve multiple hosts and nodes. Note that a single Oracle home can be shared by multiple nodes, and in this case, running RUP Lite on a single node of such a group is sufficient.
Follow Steps 1 through 10 in Section 3.2.1, "Run RUP Lite for RDBMS".
Stop all user applications that use the Oracle home directory being patched.
Update the following properties in the work_dir/DB_timestamp/db_server_bundle/metadata/env.properties file. Example values are shown.
ORACLE_HOME: Use an Oracle home directory on which patches must be applied, such as /u01/db/11.2.0.3.
ORACLE_SID: Use an instance name that belongs to the fusionapps database and is run against the ORACLE_HOME set in the previous property.
TNS_ADMIN: Use a valid tns_admin location, which is typically located under the grid infra and contains listener.ora and sqlnet.ora files.
LISTENER_NAME: Use a listener name.
PFILE=/u01/db/11.2.0.3/dbs/init.ora, for example. You can retrieve this value by running the following query:
select NAME, VALUE from v$parameter where NAME like '%file%';
Update the PFILE property if your database is started using pfile.
DBSERVER_RESTART=false
Note that the value of DBSERVER_RESTART must be "false".
Verify that the java version is 1.6 or above by using the following command:
(UNIX) $JAVA_HOME/bin/java -version (Windows) %JAVA_HOME%\bin\java -version
Change directory to the following location:
DB_timestamp/db_server_bundle/bin
Run RUP Lite for RDBMS in validate mode. The database instance and listener must be up.
(UNIX) ruplite.sh validate (Windows) ruplite.bat validate
Review the log file, output/logs/ruplitevalidate.log, to confirm whether the database parameters contain the values you set in Step 3 and the values displayed in Table 3-1, "Recommended Values for Database Parameters". If any errors occurred, you can find them in this log file also.
If any of the parameters do not contain the recommended value, proceed to the next step to run RUP Lite for RDBMS in setdbparameters mode. If all parameters are correct, proceed to Step 10.
Run RUP Lite for RDBMS in setdbparameters mode. The database instance and listener must be up.
(UNIX) ruplite.sh setdbparameters (Windows) ruplite.bat setdbparameters
Review the log file, output/logs/ruplitesetdbparameters.log, to confirm whether the database parameters contain the values displayed in Table 3-1, "Recommended Values for Database Parameters". If any errors occurred, you can find them in this log file also.
Shut down all Oracle RAC databases on all nodes in the cluster, even those that are sharing the same host. Database instances that are running could cause issues that prevent patches from applying successfully or you could receive errors because the patches update files that are in use.
To shut down an Oracle RAC database, enter the following command in a command window, where CRS_home is the location of the Grid home directory and sales is the name of the database in the following example:
(UNIX) CRS_home/bin/srvctl stop database -d sales (Windows) CRS_home\bin\srvctl stop database -d sales
Stop the listener that is running from all Oracle homes in the cluster, using the following command. Note that all services must be shut down if the OIM and OID databases are configured on same listener.
(UNIX) CRS_home/bin/srvctl stop listener [-l listener_name] (Windows) CRS_home\bin\srvctl stop listener [-l listener_name]
To avoid an issue with active files while patching, ensure that no applications or processes are running from the ORACLE_HOME that is referenced in metadata/env.properties.
Run RUP Lite for RDBMS in apply mode.
(UNIX) ruplite.sh (Windows) ruplite.bat
Review the following log files located under the output/logs directory if any errors occurred:
ruplitedb.log tp_property_editor_timestamp.log db_apply_downloaded_patches_timestamp.log db_apply_repository_patches_timestamp.log db_validate_downloaded_patches_timestamp.log db_validate_repository_patches_timestamp.log downloaded_patch_validate_results_timestamp.xml repository_patch_validate_results_timestamp.xml post_db_restart_actions_timestamp.log
If RUP Lite for RDBMS fails, resolve the issue reported in the log files. When you restart a failed session, RUP Lite for RDBMS ignores the successful actions, starts with the failed action, and proceeds from that point.
RAC databases often share a single ORACLE_HOME for all RAC instances. If you have this configuration, continue to the next step.
If you do not have this configuration, you must update the files in the other ORACLE_HOMEs for your RAC database. To update the other ORACLE_HOMEs, repeat Steps 4 through 8 in Section 3.4.1, "Run RUP Lite for RDBMS" for RAC instances with non-shared ORACLE_HOMEs. Then repeat Steps 3 through 15 in this section for all RAC instances. Note that this may involve multiple hosts and nodes.
Start the database.
Start the listener from all Oracle homes in the cluster. For Windows, start the services described Section 3.4.3, "Stop Services on Windows Before Running RUP Lite For RDBMS".
After the database is started, run the following commands:
(UNIX) cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @catbundle.sql psu apply SQL> QUIT (Windows) cd %ORACLE_HOME%\rdbms\admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @catbundle.sql winbundle apply SQL> QUIT
For a list of catbundle.sql errors that can be ignored, see Section 6.19.17, "Ignorable Errors Reported by catbundle.sql".
(UNIX) cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @catmetx.sql SQL> QUIT (Windows) cd %ORACLE_HOME%\rdbms\admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @catmetx.sql SQL> QUIT
Proceed to Section 3.2.3, "Run Additional Post Database Start Scripts for Patches for Release 6".
Perform the following steps on the DB host by any user that has system privileges. Perform these steps on only one of the nodes in the case of a RAC setup. If any of the following steps requires a database stop and start, the same user that performs these steps must also perform the stop and start.
You must manually execute any additional manual steps that are documented in the README.txt file of the patches applied with RUP Lite for RDBMS. RUP Lite for RDBMS does not execute manual steps from the README.txt file of the patch.
If there is more than one ORACLE_HOME in the RAC database, you do not need to run SQL scripts again when patching the 2nd through the nth ORACLE_HOME, but you do need to perform any manual steps that update ORACLE_HOME.
Database patches can be found at the following locations:
SHARED_UPGRADE_LOCATION/POD_NAME/RELEASE_VERSION/DB/HOST_NAME/RUPLiteDB/DB_TIME_STAMP/db_server_bundle/db_server/database/psu (if it exists) SHARED_UPGRADE_LOCATION/POD_NAME/RELEASE_VERSION/DB/HOST_NAME/RUPLiteDB/DB_TIME_STAMP/db_server_bundle/custom_db_server/database/patch (if it exists) SHARED_UPGRADE_LOCATION/POD_NAME/RELEASE_VERSION/DB/HOST_NAME/RUPLiteDB/DB_TIME_STAMP/db_server_bundle/db_server/database/patch
Example location:
/u01/shared_location/CRM/11.1.6.0.0/DB/racNode1.mycompany.com/RUPLiteDB/DB_2012-08-06_04-44-01/db_server_bundle/db_server/database/patch/
Proceed to Section 3.4, "Run RUP Lite for RDBMS for Upgrade to Release 7".
If you are on Linux64, Solaris Sparc64, or Solaris86-64 platforms and use the Oracle Exadata Database Machine, download and apply the generic patches in the following list, and the list of specific patches for your platform from My Oracle Support.
Apply the quarterly database patch (Patch 14474780 - QUARTERLY DATABASE PATCH FOR EXADATA (OCT 2012 - 11.2.0.3.11) for your platform, if you did not apply these patches in Section 3.1.1, "Quarterly Database Patches".
Linux: p14474780_112030_Linux-x86-64.zip
Solaris Sparc64: p14474780_112030_SOLARIS64.zip
Solaris86-64: p14474780_112030_Solaris86-64.zip
Apply all of the following generic patches, which are not platform-specific:
p12317925_112030_Generic.zip
p13508115_112030_Generic.zip
p14698700_112030_Generic.zip
Apply the following Exadata patches if you are on the Linux64 platform:
p12552578_1120311ExadataDatabase_Linux-x86-64.zip
p12646746_112030_Linux-x86-64.zip
p12977501_112030_Linux-x86-64.zip
p12985184_112030_Linux-x86-64.zip
p13014128_112030_Linux-x86-64.zip
p13078786_112030_Linux-x86-64.zip
p13365700_112030_Linux-x86-64.zip
p13404129_112030_Linux-x86-64.zip
p13615767_1120311ExadataDatabase_Linux-x86-64.zip
p13632653_112030_Linux-x86-64.zip
p13743357_1120311ExadataDatabase_Linux-x86-64.zip
p13902963_1120311ExadataDatabase_Linux-x86-64.zip
p14029429_112030_Linux-x86-64.zip
p14058884_112030_Linux-x86-64.zip
p14164849_112030_Linux-x86-64.zip
p14226599_112030_Linux-x86-64.zip
p14499293_1120311ExadataDatabase_Linux-x86-64.zip
p14555370_1120311ExadataDatabase_Linux-x86-64.zip
p14653598_1120311ExadataDatabase_Linux-x86-64.zip
p14679292_112030_Linux-x86-64.zip
p14741727_1120311ExadataDatabase_Linux-x86-64.zip
p14757709_1120311ExadataDatabase_Linux-x86-64.zip
p14775679_1120311ExadataDatabase_Linux-x86-64.zip
p14808639_1120311ExadataDatabase_Linux-x86-64.zip
p14837414_1120311ExadataDatabase_Linux-x86-64.zip
p15843238_1120311ExadataDatabase_Linux-x86-64.zip
p16100861_1120311ExadataDatabase_Linux-x86-64.zip
p16207583_1120311ExadataDatabase_Linux-x86-64.zip
p16369388_1120311ExadataDatabase_Linux-x86-64.zip
Apply the following Exadata patches if you are on the Solaris Sparc64 platform:
p12552578_1120311ExadataDatabase_SOLARIS64.zip
p12646746_112030_SOLARIS64.zip
p12977501_112030_SOLARIS64.zip
p12985184_112030_SOLARIS64.zip
p13014128_112030_SOLARIS64.zip
p13078786_112030_SOLARIS64.zip
p13365700_112030_SOLARIS64.zip
p13404129_112030_SOLARIS64.zip
p13615767_1120311ExadataDatabase_SOLARIS64.zip
p13632653_112030_SOLARIS64.zip
p13743357_1120311ExadataDatabase_SOLARIS64.zip
p13902963_1120311ExadataDatabase_SOLARIS64.zip
p14029429_112030_SOLARIS64.zip
p14058884_112030_SOLARIS64.zip
p14164849_112030_SOLARIS64.zip
p14226599_112030_SOLARIS64.zip
p14499293_1120311ExadataDatabase_SOLARIS64.zip
p14555370_1120311ExadataDatabase_SOLARIS64.zip
p14653598_1120311ExadataDatabase_SOLARIS64.zip
p14679292_112030_SOLARIS64.zip
p14741727_1120311ExadataDatabase_SOLARIS64.zip
p14757709_1120311ExadataDatabase_SOLARIS64.zip
p14775679_1120311ExadataDatabase_SOLARIS64.zip
p14808639_1120311ExadataDatabase_SOLARIS64.zip
p14837414_1120311ExadataDatabase_SOLARIS64.zip
p15843238_1120311ExadataDatabase_SOLARIS64.zip
p16100861_1120311ExadataDatabase_SOLARIS64.zip
p16207583_1120311ExadataDatabase_SOLARIS64.zip
p16369388_1120311ExadataDatabase_SOLARIS64.zip
Apply the following Exadata patches if you are on the Solaris X64 platform:
p12552578_1120311ExadataDatabase_Solaris86-64.zip
p12646746_112030_Solaris86-64.zip
p12977501_112030_Solaris86-64.zip
p12985184_112030_Solaris86-64.zip
p13014128_112030_Solaris86-64.zip
p13078786_112030_Solaris86-64.zip
p13365700_112030_Solaris86-64.zip
p13404129_112030_Solaris86-64.zip
p13615767_1120311ExadataDatabase_Solaris86-64.zip
p13632653_112030_Solaris86-64.zip
p13743357_1120311ExadataDatabase_Solaris86-64.zip
p13902963_1120311ExadataDatabase_Solaris86-64.zip
p14029429_112030_Solaris86-64.zip
p14058884_112030_Solaris86-64.zip
p14164849_112030_Solaris86-64.zip
p14226599_112030_Solaris86-64.zip
p14499293_1120311ExadataDatabase_Solaris86-64.zip
p14555370_1120311ExadataDatabase_Solaris86-64.zip
p14653598_1120311ExadataDatabase_Solaris86-64.zip
p14679292_112030_Solaris86-64.zip
p14741727_1120311ExadataDatabase_Solaris86-64.zip
p14757709_1120311ExadataDatabase_Solaris86-64.zip
p14775679_1120311ExadataDatabase_Solaris86-64.zip
p14808639_1120311ExadataDatabase_Solaris86-64.zip
p14837414_1120311ExadataDatabase_Solaris86-64.zip
p15843238_1120311ExadataDatabase_Solaris86-64.zip
p16100861_1120311ExadataDatabase_Solaris86-64.zip
p16207583_1120311ExadataDatabase_Solaris86-64.zip
p16369388_1120311ExadataDatabase_Solaris86-64.zip
Run the RUP Lite for RDBMS utility to perform the tasks required to update your Oracle Fusion Applications database before you upgrade to Release 7. RUP Lite for RDBMS can be run in the following modes:
Validate mode:
Validates database parameters as described in Table 3-1
Set database parameters mode:
Sets database parameters to the values described in Table 3-1, if required
Restarts the database instance, if requested
Apply mode:
Stops the listener and shuts down the database instance (optional)
Configures Oracle Configuration Manager (OCM) in disconnected mode, if required
Unzips Opatch, if it is available in REPOSITORY_LOCATION
Applies patch set updates (PSUs) and one-off patches in REPOSITORY_LOCATION
Applies downloaded one-off patches in the 11.1.7.0.0_post_repo_patches directory
Starts the listener and the database instance (optional)
Runs catbundle.sql if any PSUs were applied
Runs catmetx.sql
Apply Post Changes mode:
Performs SQL*Plus actions after patches apply
RUP Lite for RDBMS uses non-interactive OPatch calls to apply RDBMS patches. OPatch tries to install and configure Oracle Configuration Manager (OCM) if OCM has not already been installed and configured. This causes non-interactive OPatch calls to fail in some cases. To avoid this issue, Oracle recommends that you install OCM prior to running RUP Lite for RDBMS. If you plan to use OCM, you should configure it after you install it. If you do not plan to use OCM, you can either configure it in disconnected mode or let RUP Lite for RDBMS configure it. If you install OCM and do not configure it, RUP Lite for RDBMS will automatically configure it in disconnected mode. For more information, see "Installing Oracle Configuration Manager Using the Command Line Interface" in the Oracle Configuration Manager Installation and Administration Guide.
If you do not use Oracle Exadata Database Machine, run RUP Lite for RDBMS to automatically apply the mandatory Oracle Database patches mentioned in the "Oracle Database" section of Oracle Fusion Applications release notes. This step applies Oracle Database patches that reside in both the REPOSITORY_LOCATION and the 11.1.7.0.0_post_repo_patches directories, which you downloaded in Section 2.3.6, "Download and Unzip Repository and Patches for Release 6 to Release 7 Upgrade". Follow the steps in Section 3.4.1, "Run RUP Lite for RDBMS".
If you use Oracle Exadata Database Machine, do not run RUP Lite for RDBMS.
If you are running Oracle Fusion Applications on a RAC database, follow the steps in Section 3.4.2, "Run RUP Lite for RDBMS in a RAC Database".
Perform the following steps to run RUP Lite for RDBMS in three modes: validate, setdbparameters, and apply:
Apply the version of OPatch that is delivered in the repository. It is available at REPOSITORY_LOCATION/installers/database/opatch/p6880880_112000_Linux-x86-64.zip.
Copy the TPBundler.zip file to any temporary directory, such as work_dir in the following example:
cp REPOSITORY_LOCATION/installers/pre_install/TPBundler.zip work_dir
Unzip TPBundler.zip in the work_dir directory, which contains the following files after unzipping:
createTPBundle.jar createTPBundle.cmd createTPBundle.sh ojdl.jar tpBundleConfig_DB.xml tpBundleConfig_IDM.xml tpBundleConfig_OHS.xml README.txt
The createTPBundler utility creates the RDBMS patch bundle, DBPatches.zip, and RUP Lite for RDBMS. This patch bundle contains the mandatory prerequisite patches that are delivered in REPOSITORY_LOCATION as well as any patches you may have downloaded.
Use the following command syntax to run createTPBundler, which creates DBPatches.zip in a temporary directory, referred to as work_dir in the example. Note that work_dir must have read/write permissions.
(UNIX) sh createTPBundle.sh -shiphomelocation REPOSITORY_LOCATION -tempdir work_dir -target DB [-patchdownloadloc location_of_downloaded_patches] (Windows) createTPBundle.cmd -shiphomelocation REPOSITORY_LOCATION -tempdir work_dir -target DB [-patchdownloadloc location_of_downloaded_patches]
The following options are available for createTPBundler:
-shiphomelocation: Location of the createTPBundler repository.
-tempdir: Destination directory to which the generated zip file was copied.
-target: Target against which the copy should be initiated. Valid values are IDM, DB, OH. Use the DB value.
-patchdownloadloc: Location of the patch directory where you downloaded the patches in Section 2.3.6, "Download and Unzip Repository and Patches for Release 6 to Release 7 Upgrade". Use this option only if you downloaded patches to a directory other than the default patch download directory, which is 11.1.7.0.0_post_repo_patches.
-logfile: Full path of the createTPbundle log file. The default is createTPBundle.log in the current directory.
-loglevel: Log level for the createTPbundler utility. Valid values are SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST. The default value is INFO.
Copy DBPatches.zip to any temporary directory on the database server host.
Log in to the database server host.
Unzip DBPatches.zip to any temporary directory on the database server host. The following subdirectories and files exist after unzipping.
|-- DB_timestamp -- db_server_bundle |-- README.txt |-- bin | |-- ruplite.bat | |-- ruplite.sh |-- metadata | |-- env.properties | |-- installer.properties | |-- plugin-metadata.txt |-- custom_db_server | -- database | -- patch | -- downloaded one-off patches |-- db_server | |-- database | |-- opatch | | -- OPatch zip file | |-- patch | | -- One-off patches in repository | |-- psu | | -- Patch Set Updates in repository |-- db | |--RUP Lite related files |-- lib | |--RUP Lite related files |-- ruplite | |--RUP Lite related files |-- techpatch | |--TPU related files
Perform this step only if you are running RUP Lite for RDBMS on an Oracle VM environment.
As the root user, change the permissions on the DB_timestamp subdirectory:
chmod -R 777 DB_timestamp
Exit out of root user to ensure that you do not perform the remaining steps as root.
Set executable permissions on ruplite.sh. (UNIX only)
chmod -R 755 DB_timestamp/db_server_bundle/bin/ruplite.sh
Set the JAVA_HOME environment variable as shown in the following example:
(UNIX) setenv JAVA_HOME java_home_location (must be jdk6) (Windows) set JAVA_HOME=java_home_location (must be jdk6)
Update the following properties in the work_dir/DB_timestamp/db_server_bundle/metadata/env.properties file. Example values are shown.
ORACLE_SID=Use an instance name that belongs to the fusionapps database.
ORACLE_HOME=Use an Oracle home directory on which patches must be applied, such as /u01/db/11.2.0.3.
TNS_ADMIN=Use a valid location that contains SQL*Net configuration files for the database.
LISTENER_NAME=Use a listener name.
PFILE=/u01/db/11.2.0.3/dbs/init.ora, for example. You can retrieve this value by running the following query:
select NAME, VALUE from v$parameter where NAME like '%file%';
Update PFILE if your database is started using pfile.
DBSERVER_RESTART=true or false
To minimize downtime, you can use "false" for setdbparameters mode, and "true" for apply mode.
If DBSERVER_RESTART is set to "false", the database server, listener and other related services must be manually stopped before running RUP Lite in apply mode. Then after running RUP Lite in apply mode, you must run Step 21.
If the value for this property is set to "true", RUP Lite automatically stops the listener and database before applying patches. In addition, RUP Lite automatically performs the following actions after applying patches when DBSERVER_RESTART=true:
Start the database instance.
Start the listener.
Run catbundle.sql with arguments "psu apply" on non-windows and "winbundle apply" on windows.
(UNIX) $ORACLE_HOME/rdbms/admin/catbundle.sql psu apply (Windows) %ORACLE_HOME%\rdbms\admin\catbundle.sql winbundle apply
For a list of catbundle.sql errors that can be ignored, see Section 6.19.17, "Ignorable Errors Reported by catbundle.sql".
Run ORACLE_HOME/rdbms/admin/catmetx.sql.
(UNIX) $ORACLE_HOME/rdbms/admin/catmetx.sql (Windows) %ORACLE_HOME%\rdbms\admin\catmetx.sql
For each patch applied, run the post installation script, postinstall.sql, if it exists.
Verify that the java version is 1.6 or above by using the following command:
(UNIX) $JAVA_HOME/bin/java -version (Windows) %JAVA_HOME%\bin\java -version
If your version is lower, download 1.6 or a higher version from My Oracle Support.
Stop all user applications.
Change directory to the following location:
DB_timestamp/db_server_bundle/bin
Run RUP Lite for RDBMS in validate mode. The database instance and listener must be up.
(UNIX) ruplite.sh validate (Windows) ruplite.bat validate
Review the log file, output/logs/ruplitevalidate.log, to confirm whether the database parameters contain the values you set in Step 11 and the values displayed in Table 3-1, "Recommended Values for Database Parameters". If any errors occurred, you can find them in this log file.
If any of the parameters do not contain the recommended value, proceed to the next step to run RUP Lite for RDBMS in setdbparameters mode. If all parameters are correct, proceed to Step 19 to run RUP Lite for RDBMS in apply mode.
Run RUP Lite for RDBMS in setdbparameters mode. The database instance and listener must be up.
(UNIX) ruplite.sh setdbparameters (Windows) ruplite.bat setdbparameters
Review the log file, output/logs/ruplitesetdbparameters.log, to confirm whether the database parameters contain the values displayed in Table 3-1, "Recommended Values for Database Parameters". If any errors occurred, you can find them in this log file also.
Running RUP Lite for RDBMS in apply mode starts and stops only the Fusion Applications database listener and the database server. You must stop any other applications or processes that are running from the Oracle Fusion Applications home directory, except the OPSS Security Store, before you run RUP Lite for RDBMS. For more information, see "Starting and Stopping" in the Oracle Fusion Applications Administrator's Guide. Also confirm that the BI presentation servers are shut down.
You can set the parameter DBSERVER_RESTART (available in metadata/env.properties) to "false" if you want to manually shut down the database, stop the listener before patching, and start it up after applying the patches. For Windows, if you set DBSERVER_RESTART to "false", follow the steps in Section 3.4.3, "Stop Services on Windows Before Running RUP Lite For RDBMS".
Note:
To avoid an issue with active files while patching, ensure that no applications or processes are running from the ORACLE_HOME that is referenced in metadata/env.properties. If DBSERVER_RESTART=true, you can ignore the database instance and listener processes because RUP Lite brings them down.
Run RUP Lite for RDBMS in apply mode.
(UNIX) ruplite.sh (Windows) ruplite.bat
Review the following log files located under the output/logs directory if any errors occurred:
ruplitedb.log tp_property_editor_timestamp.log db_apply_downloaded_patches_timestamp.log db_apply_repository_patches_timestamp.log db_validate_downloaded_patches_timestamp.log db_validate_repository_patches_timestamp.log downloaded_patch_validate_results_timestamp.xml repository_patch_validate_results_timestamp.xml post_db_restart_actions_timestamp.log
If RUP Lite for RDBMS fails, resolve the issue reported in the log files. When you restart a failed session, RUP Lite for RDBMS ignores the successful actions, starts with the failed action, and proceeds from that point.
The post_db_restart_actions_timestamp.log file includes the output from catbundle.sql and catmetx.sql. For a list of catbundle.sql errors that can be ignored, see Section 6.19.17, "Ignorable Errors Reported by catbundle.sql".
If you set DBSERVER_RESTART to "false", perform the following steps:
Start the database instance
Start the listener
Run RUP Lite for RDBMS in applypostchanges mode.
(UNIX) ruplite.sh applypostchanges (Windows) ruplite.bat applypostchanges
Review the following log files, located under the output/logs directory, if any errors occurred:
ruplitedbapplypostchanges.log post_db_restart_actions_timestamp.log
These log files are generated by running ruplite in applypostchanges mode. The post_db_restart_actions_timestamp.log file includes the output from catbundle.sql and catmetx.sql. For a list of catbundle.sql errors that can be ignored, see Section 6.19.17, "Ignorable Errors Reported by catbundle.sql".
You must manually execute any manual steps that are documented in the README.txt file of the patches you applied with RUP Lite for RDBMS. RUP Lite for RDBMS executes postinstall.sql if it is mentioned as a manual step. All other steps have to be done manually.
Proceed to Section 3.4.4, "Run Additional Post Database Start Scripts for Patches for Release 7".
Perform the following steps to run RUP Lite for RDBMS in a RAC database. You must run RUP Lite for RDBMS on all available file systems. This may involve multiple hosts and nodes. Note that a single Oracle home can be shared by multiple nodes, and in this case, running RUP Lite on a single node of such a group is sufficient.
Follow Steps 1 through 10 in Section 3.4.1, "Run RUP Lite for RDBMS".
Stop all user applications that use the Oracle home directory being patched.
Update the following properties in the work_dir/DB_timestamp/db_server_bundle/metadata/env.properties file. Example values are shown.
ORACLE_HOME=Use an Oracle home directory on which patches must be applied, such as /u01/db/11.2.0.3.
ORACLE_SID=Use an instance name that belongs to the fusionapps database and is run against the ORACLE_HOME set in the previous property.
TNS_ADMIN=Use a valid tns_admin location, which is typically located under the grid infra and contains listener.ora and sqlnet.ora files.
LISTENER_NAME=Use a listener name.
PFILE=/u01/db/11.2.0.3/dbs/init.ora, for example.
Update PFILE if your database is started using pfile.
DBSERVER_RESTART=false
Note that the value of DBSERVER_RESTART must be "false".
Verify that the java version is 1.6 or above by using the following command:
(UNIX) $JAVA_HOME/bin/java -version (Windows) %JAVA_HOME%\bin\java -version
Change directory to the following location:
DB_timestamp/db_server_bundle/bin
Run RUP Lite for RDBMS in validate mode. The database instance and listener must be up.
(UNIX) ruplite.sh validate (Windows) ruplite.bat validate
Review the log file, output/logs/ruplitevalidate.log, to confirm whether the database parameters contain the values you set in Step 3 and the values displayed in Table 3-1, "Recommended Values for Database Parameters". If any errors occurred, you can find them in this log file also.
If any of the parameters do not contain the recommended value, proceed to the next step to run RUP Lite for RDBMS in setdbparameters mode. If all parameters are correct, proceed to Step 10 to run RUP Lite for RDBMS in apply mode.
Run RUP Lite for RDBMS in setdbparameters mode. The database instance and listener must be up.
(UNIX) ruplite.sh setdbparameters (Windows) ruplite.bat setdbparameters
Review the log file, output/logs/ruplitesetdbparameters.log, to confirm whether the database parameters contain the values displayed in Table 3-1, "Recommended Values for Database Parameters". If any errors occurred, you can find them in this log file also.
Shut down all Oracle RAC databases on all nodes in the cluster, even those that are sharing the same host. Database instances that are running could cause issues that prevent patches from applying successfully or you could receive errors because the patches update files that are in use.
To shut down an Oracle RAC database, enter the following command in a command window, where CRS_home is the location of the Grid home directory and sales is the name of the database in the following example:
(UNIX) CRS_home/bin/srvctl stop database -d sales (Windows) CRS_home\bin\srvctl stop database -d sales
Stop the listener that is running from all Oracle homes in the cluster, using the following command:
(UNIX) CRS_home/bin/srvctl stop listener [-l listener_name] (Windows) CRS_home\bin\srvctl stop listener [-l listener_name]
To avoid an issue with active files while patching, ensure that no applications or processes are running from the ORACLE_HOME that is referenced in metadata/env.properties.
Run RUP Lite for RDBMS in apply mode.
(UNIX) ruplite.sh (Windows) ruplite.bat
Review the following log files located under the output/logs directory if any errors occurred:
ruplitedb.log tp_property_editor_timestamp.log db_apply_downloaded_patches_timestamp.log db_apply_repository_patches_timestamp.log db_validate_downloaded_patches_timestamp.log db_validate_repository_patches_timestamp.log downloaded_patch_validate_results_timestamp.xml repository_patch_validate_results_timestamp.xml
If RUP Lite for RDBMS fails, resolve the issue reported in the log files. When you restart a failed session, RUP Lite for RDBMS ignores the successful actions, starts with the failed action, and proceeds from that point.
RAC databases often share a single ORACLE_HOME for all RAC instances. If you have this configuration, continue to the next step.
If you do not have this configuration, you must update the files in the other ORACLE_HOMEs for your RAC database. To update the other ORACLE_HOMEs, repeat Steps 4 through 8 in Section 3.4.1, "Run RUP Lite for RDBMS" for RAC instances with non-shared ORACLE_HOMEs. Then repeat Steps 3 through 15 in this section for all RAC instances. Note that this may involve multiple hosts and nodes.
Start the database.
Run RUP Lite for RDBMS in applypostchanges mode.
(UNIX) ruplite.sh applypostchanges (Windows) ruplite.bat applypostchanges
Review the following log files, located under the output/logs directory, if any errors occurred:
ruplitedbapplypostchanges.log post_db_restart_actions_timestamp.log
These log files are generated by running ruplite in applypostchanges mode. The post_db_restart_actions_timestamp.log file includes the output from catbundle.sql and catmetx.sql. For a list of catbundle.sql errors that can be ignored, see Section 6.19.17, "Ignorable Errors Reported by catbundle.sql".
You must manually execute any manual steps that are documented in the README.txt file of the patches you applied with RUP Lite for RDBMS. RUP Lite for RDBMS executes postinstall.sql if it is mentioned as a manual step. All other steps have to be done manually.
If there is more than one ORACLE_HOME in the RAC database, you do not need to run SQL scripts again when patching the 2nd through the nth ORACLE_HOME, but you do need to perform any manual steps that update ORACLE_HOME.
Start the listener from all Oracle homes in the cluster. For Windows, start the services described Section 3.4.3, "Stop Services on Windows Before Running RUP Lite For RDBMS".
Proceed to Section 3.4.4, "Run Additional Post Database Start Scripts for Patches for Release 7".
For a Windows platform, the following services should be stopped before you run RUP Lite for RDBMS.
Note:
You do not shut down services if DBSERVER_RESTART=true in env.properties, which is the default case. You must shut down services only if you set DBSERVER_RESTART=false in env.properties.
OracleOraDb11g_home1TNSListenerLISTENER_<SID>
OracleOraDb11g_home1ClrAgent
OracleDBConsole<SID>
OracleJobScheduler<SID>
OracleService<SID>
OracleMTSRecoveryService
Windows Management Instrumentation
Distributed Transaction Coordinator
Oracle <SID> VSS Writer Service
If RUP Lite for RDBMS fails to stop or start a service, you can manually manage each service from the Control Panel. Select Administrative Tools, then Services. Right click on each service and choose the Stop or Start option.
RUP Lite for RDBMS consolidates the README.txt files for all applied patches into one consolidated README.txt file, which is located in the OUI_Component_readme.txt directory. You must manually execute any manual steps that are documented in the consolidated README.txt file. RUP Lite for RDBMS executes postinstall.sql if it is mentioned as a manual step. All other steps have to be performed manually on the DB host by any user that has system privileges. Perform these steps on only one of the nodes in the case of a RAC setup.
Database patches can be found at the following locations:
SHARED_UPGRADE_LOCATION/POD_NAME/RELEASE_VERSION/DB/RUPLiteDB/DB_TIME_STAMP/db_server_bundle/db_server/database/psu (if exists)
SHARED_UPGRADE_LOCATION/POD_NAME/RELEASE_VERSION/DB/RUPLiteDB/DB_TIME_STAMP/db_server_bundle/db_server/database/patch
Example location:
/u01/shared_location/CRM/11.1.7.0.0/DB/RUPLiteDB/DB_2012-08-07_03-43-22/db_server_bundle/db_server/database/patch/
|
 Copyright © 2011, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|