Supplemental Readme - Patch Installation and Deinstallation For 12.1.0.x.x Windows Bundles (Doc ID 2032004.1)

1/28/2020 Document 2032004.
1
Switch to Cloud Support DBA (Available) (0) Contact Us Help
PowerView is Off
Dashboard Knowledge Service Requests Patches & Updates Community

Patches & Updates > Patch Search Results > Give Feedback...
Copyright (c) 2020, Oracle. All rights reserved. Oracle Confidential.
To Bottom
Supplemental Readme - Patch Installation and Deinstallation For 12.1.0.x.x Windows Bundles
(Doc ID 2032004.1)
Was this document helpful?

APPLIES TO:
Yes
Oracle Database - Enterprise Edition - Version 12.1.0.1 to 12.1.0.2 [Release 12.1] No
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Document Details
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Type: README
Status: PUBLISHED
MAIN CONTENT Last Major
Update: 04-Aug-2018
23-Dec-2019
Skip Headers
Last
This document includes the following sections: Update:
Section 1, "Patch Information"

Section 2, "Patch Installation and Deinstallation"
Related Products
Section 3, "Known Issues"
Section 4, "References" Oracle Cloud
Section 5, "Steps for Apply/Rollback Patch" Infrastructure - Database
Section 6, "Steps to Run the datapatch Utility for Single Tenant Versus Multitenant (CDB/PDB)" Service
Section 7, "Documentation Accessibility" Oracle Database Cloud
Exadata Service
1 Patch Information Oracle Database Backup
Service
Windows Bundle Patch (BP) patches are cumulative. That is, the content of all previous BPs is included in the latest BP patch. Oracle Database Exadata
These instructions can be used to apply 12.1.0.1 and 12.1.0.2 Windows Bundles in various Oracle RAC configurations. Express Cloud Service
Oracle Database Cloud
2 Patch Installation and Deinstallation Service
Show More
This section includes the following sections:
Section 2.1, "Patch Installation Prerequisites" Information Centers

Section 2.2, "OPatch Automation for GI" Platform as a Service (PaaS)
Section 2.3, "Patch Installation" and Oracle Cloud
Section 2.4, "Patch Post-Installation Instructions" Infrastructure (OCI)
Section 2.5, "Patch Deinstallation" Information Center
[2048297.2]
Section 2.6, "Unmounting ACFS File Systems"
Section 2.7, "Mounting ACFS File Systems" Index of Oracle Database
Information Centers
[1568043.2]
2.1 Patch Installation Prerequisites
Information Center: Overview
You must satisfy the conditions in the following sections before applying the patch: Database Server/Client
Installation and
Upgrade/Migration
OPatch Utility Information [1351022.2]
OCM Configuration
Validation of Oracle Inventory インフォメーション・センタ
ー: データベースおよび
Unzipping the Patch
Enterprise Manager 日本語ド
キュメント [1946305.2]
2.1.1 OPatch Utility Information Information Center: Overview
of Database Security Products
You must use the OPatch utility version12.1.0.1.5 or later to apply this patch. Oracle recommends that you use the latest [1548952.2]
released OPatch for 12.1 releases, which is available for download from My Oracle Support patch 6880880. It is recommended
that you download the Opatch utility and the patch in a shared location to be able to access them from any node in the cluster for
the patch application on each node.
Document References
No References available
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=276861904830978&id=2032004.1&_afrWindowMode=0&_adf.ctrl-state=9opt3x… 1/18
1/28/2020 Document 2032004.1
Note: for this document.
When patching the GI Home, a shared location on ACFS only needs to be unmounted on the node
where the GI Home is being patched. Recently Viewed
The new opatch utility should be updated in all the Oracle RAC database homes and the GI home that ASM on Non-First Node
are being patched. To update Opatch, use the following instructions. (Second or Others) Fails to
Start: PMON (ospid: nnnn):
terminating the instance due
to error 481 [1383737.1]
1. Download the OPatch utility to a temporary directory.
2. For each Oracle RAC database home and the GI home that is being patched, run the following commands as the home How to upgrade the JDK
installed within the 12.1.0.2
owner to extract the OPatch utility. DB ORACLE_HOME?
[2495017.1]
$ rmdir /s /q %ORACLE_HOME%\OPatch\*
Oracle HTTP Server Fails to
$ unzip <OPATCH-ZIP> -d %ORACLE_HOME% Start With the Error "Invalid
$ %ORACLE_HOME%\OPatch\opatch version argument: Could not set
permission for mutex lock"
The version output of the previous command should be 12.1.0.1.5 or later. After Applying OHS Bundle
Patch 29407043
For information about OPatch documentation, including any known issues, see My Oracle Support Note 293369.1 OPatch [2550734.1]
documentation list. Cumulative README Post-
Install Steps for Oracle HTTP
Server 12.2.1.3 Bundle
2.1.2 OCM Configuration Patches [2568225.1]
OHS Fails to Start After
Applying OHS Bundle Patch
The OPatch utility will prompt for your OCM (Oracle Configuration Manager) response file when it is run. You should enter a
29407043 [2537530.1]
complete path of OCM response file if you already have created this in your environment.
Show More
If you do not have the OCM response file (ocm.rsp), then you should run the following command to create it.
As the GI home owner execute:
$ %ORACLE_HOME%\OPatch\ocm\bin\emocmrsp
2.1.3 Validation of Oracle Inventory
Before beginning patch application, check the consistency of inventory information for GI home and each database home to be
patched. Run the following command as respective Oracle home owner to check the consistency.
$ %ORACLE_HOME%\OPatch\opatch lsinventory -oh %ORACLE_HOME%
If this command succeeds, it lists the Oracle components that are installed in the home. Save the output so you have the status
prior to the patch apply.
If you have not started patching, the output will also print out the GI home on all the nodes along with its patching level. The
patching level must be identical for all the nodes. If they are not, do not patch. Contact Oracle Support Services for assistance.
If this command fails or the patching level is not the same on all nodes, contact Oracle Support Services for assistance.
2.1.4 Unzipping the Patch
Download and unzip the patch in a shared location to be able to access it from any node in the cluster.
(In this readme, the downloaded patch location directory is referred as <UNZIPPED_PATCH_LOCATION>.)
For example, if <UNZIPPED_PATCH_LOCATION> in your environment is C:\app\patches, enter the following command:
$ cd C:\app\patches
Unzip the patch in a shared location.
$ unzip
%zipName%
2.2 OPatch Automation for GI
OPatchauto is currently not supported on Windows platform.
2.3 Patch Installation
1/28/2020 Document 2032004.1
This section will guide you through the steps required to apply this patch to Oracle RAC database homes, the Grid home, or all
relevant homes on the cluster.
The patch instructions will differ based on the configuration of the Grid infrastructure and the Oracle RAC database homes.
The patch installations will also differ based on following aspects of your existing configuration:
GI home is shared or non-shared

The Oracle RAC database home is shared or non-shared
The Oracle RAC database home software is on ACFS or non-ACFS file systems.
Patch all the Oracle RAC database and the GI homes together, or patch each home individually
You must choose the most appropriate case that is suitable based on the existing configurations and your patch intention.
Case 1: Patching Oracle RAC Database Homes and the GI Home Together
Case 2: Patching Oracle RAC Database Homes
Case 3: Patching GI Home Alone
Case 4: Patching Oracle Restart Home
Case 5: Patching a Software Only GI Home Installation or Before the GI Home Is Configured
Case 6: Patching a Flex Cluster
Case 1: Patching Oracle RAC Database Homes and the GI Home Together
Follow the instructions in this section if you would like to patch all the Oracle RAC database homes of release version 12g
Release 1
Case 1.1: GI Home Is Not Shared
Case 1.1.1: ACFS File System Is Not Configured and Database Homes Are Not Shared
Follow these instructions in this section if the GI home is not shared and none of the Oracle database homes is shared.
You must be part of Administrator group to run these commands. Execute the following commands 1 to 10 on each node of the
cluster:
1. Stop the database instance running on the node.
srvctl stop instance -d <dbname> -i <instanceName>
2. Bring down Oracle High Availability Services on the node using: (make sure ORACLE_HOME is pointing to the Grid
Infrastructure home):
%ORACLE_HOME%\perl\bin\perl -I%ORACLE_HOME%\perl\lib -I%ORACLE_HOME%\crs\install

%ORACLE_HOME%\crs\install\rootcrs.pl -prepatch
If this is an Oracle Restart Home, execute:

%ORACLE_HOME%\crs\install\roothas.pl -prepatch
3. Verify that all Oracle services on the node have stopped by running:
net start | findstr /i ora
4. If any service is found running, then use the Computer Management Services GUI or the net stop command to stop them.
Example-
net stop OracleREMExecService

net stop OracleService<SID>
5. Also stop Distributed Transaction Coordinator service using:
net stop msdtc
6. Apply the patch to Grid Home using steps: make sure ORACLE_HOME is pointing to the Grid Infrastructure home
cd <UNZIPPED_PATCH_LOCATION>
opatch apply -local
7. Apply the patch to Database Home using steps: make sure ORACLE_HOME is pointing to the Database home
opatch apply -local
8. Start Oracle High Availability Services on the node using: (make sure ORACLE_HOME is pointing to the Grid Infrastructure
home):
1/28/2020 Document 2032004.1
%ORACLE_HOME%\crs\install\rootcrs.pl -postpatch

%ORACLE_HOME%\crs\install\roothas.pl -postpatch
9. Start the database instance on the node using:
srvctl start instance -d <dbname> -i <instanceName>
10. Verify that Oracle services on the node are running using:
crsctl status resource -t
11. After all nodes have been patched using opatch, apply the SQL changes to the database by following steps listed in Section
6
Case 1.1.2A: Patching the GI Home and Database Home Together, the GI Home Is Not Shared, the Database Home Is
Shared, ACFS May Be Used
1. From the Oracle database home, make sure to stop the Oracle RAC databases running on all nodes. Execute:
%ORACLE_HOME%\bin\srvctl stop database -d <db-unique-name>
2. On the 1st node, unmount the ACFS file systems. Use instructions in Section 2.6 for unmounting ACFS file systems.
3. On the 1st node, apply the patch to the GI Home using the steps listed under Section 5
4. If the message, "A system reboot is recommended before using ACFS" is shown, then a reboot must be issued before
continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.
5. On the 1st node, remount ACFS file systems. See Section 2.7 for instructions.
6. On the 1st node, apply the patch to the Database home using the steps listed under Section 5 . Since the Database
home is shared, this operation will patch the Database home across the cluster.
7. On the 1st node only, restart the Oracle instance which you have previously stopped in Step 1. As the database home
owner execute:
$ %ORACLE_HOME%/bin/srvctl start instance -d <db-unique-name> -n <nodename>
8. On the 2nd (next) node, unmount the ACFS file systems. Use instructions in Section 2.6 for unmounting ACFS file
systems.
9. On the 2nd node, apply the patch to GI Home using the steps listed under Section 5 .
11. On the 2nd node, restart the stack using the steps listed under Section 5
12. On the 2nd node, remount ACFS file systems. See Section 2.7 for instructions.
13. On the 2nd node only, restart the Oracle instance which you have previously stopped in Step 1. As the database home
owner execute:
$ %ORACLE_HOME%/bin/srvctl start instance -d <db-unique-name> -n <nodename>
14. Repeat Steps 8 through 13 for all remaining nodes of the cluster.
15. After all nodes have been patched using opatch, apply the SQL changes to the database by following steps listed in
Section 6
Case 1.1.2B: Patching the GI Home and the Database Home Together, the GI Home Is Not Shared, the Database Home Is
Not Shared, ACFS May Be Used
For each node, perform the following steps:
1. On the local node, unmount the ACFS file systems. Use instructions in Section 2.6 for unmounting ACFS file systems.
2. On the local node, apply the patch to the GI home and to the Database home. Use the steps listed under Section 5.
Section 6
Case 1.2: GI Home Is Shared
Follow these instructions in this section if the GI home is shared.
Note:
1/28/2020 Document 2032004.1
Patching a shared GI home requires shutdown of Oracle GI stack on all the remote nodes in the
cluster. This also means you need to stop all Oracle RAC databases which depend on GI stack, ASM
for data files, or an ACFS file system.
1. From the Oracle database home, make sure to stop the Oracle RAC databases running on GI System being patched.
Execute:
2. Make sure the ACFS file systems are unmounted on all the nodes. Use instructions in Section 2.6 for unmounting ACFS
file systems.
3. As administrator user, execute the following on all the remote nodes to stop the GI stack:
# <GI_HOME>\bin\crsctl stop crs
4. Please ensure that the GI Stack is up on the local node where patching is being performed.
5. Patch the GI home. On local node, as administrator user, apply the patch to the GI Home using the steps listed under
Section 5
7. On each remote node:
a. As administrator user, run: Ensure that ORACLE_HOME point to GI Home.

%ORACLE_HOME%\crs\install\rootcrs.pl -prepatch -nonrolling
%ORACLE_HOME%\crs\install\rootcrs.pl -postpatch -nonrolling
b. If the message, "A system reboot is recommended before using ACFS" is shown, then a reboot must be issued
before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.
8. Mount ACFS file systems. See Section 2.7.
9. For each Oracle RAC database home, execute the following command on each node if the database home software is not
shared. For each database home execute the following as administrator user: make sure ORACLE_HOME is pointing to
the Database home
# opatch apply <UNZIPPED_PATCH_LOCATION>/%BUGNO% -local
Note: The previous command should be executed only once on any one node if the database
home is shared.
10. Restart the Oracle databases that you have previously stopped in step 1. Execute:
%ORACLE_HOME%\bin\srvctl start database -d <db-unique-name>
Section 6
Case 2: Patching Oracle RAC Database Homes
You should use the following instructions if you prefer to patch Oracle RAC databases alone with this patch.
Case 2.1: Non-Shared Oracle RAC Database Homes
1. Execute the following command on each node of the cluster. As an administrator user apply the patch to the Database
Home using the steps listed under Section 5.
2. After all nodes have been patched, apply the SQL changes to the database by following steps listed in Section 6
Case 2.2: Shared Oracle RAC Database Homes
1. Make sure to stop the databases running from the Oracle RAC database homes that you would like to patch. Execute the
following command to stop each database. $ %ORACLE_HOME%\bin\srvctl stop database -d <db_unique_name>
2. As an administrator user patch the Database Home using the steps listed under Section 5 only on the local node.
3. Restart the Oracle databases that were previously stopped in Step 1. Execute the following command for each database.
$ %ORACLE_HOME%\bin\srvctl start database -d <db_unique_name>
4. Apply the SQL changes to the database by following steps listed in Section 6
Case 3: Patching GI Home Alone
You should use the following instructions if you prefer to patch Oracle GI (Grid Infrastructure) home alone with this patch.
Case 3.1: Non-Shared GI Home
If the GI home is not shared then use the following instructions to patch the home.
Case 3.1.1: ACFS File System Is Not Configured
1/28/2020 Document 2032004.1
Follow these instructions in this section if the GI home is not shared and none of the Oracle database homes use ACFS file
system for its software files.
Execute the following on each node of the cluster.
As an administrator user apply the patch to the GI Home using the steps listed under Section 5
Case 3.1.2: ACFS File System Is Configured
Repeat Steps 1 through 6 for each node in the cluster:
1. From the Oracle database home, stop the Oracle RAC database running on that node. As the database home owner
execute:
$ %ORACLE_HOME%\bin\srvctl stop instance <instance-id> -d <db-unique-name> -n <node_name>
2. Unmount all ACFS file systems on this node using instructions in Section 2.6.
3. Apply the patch to the GI home on that node using the steps listed under Section 5.
5. Remount ACFS file systems on that node. See Section 2.7 for instructions.
6. Restart the Oracle database on that node that you have previously stopped in Step 1. As the database home owner
execute:
$ %ORACLE_HOME%\bin\srvctl start database -d <db-unique-name> -n <nodename>
Case 3.2: Shared GI Home
Note:
Patching a shared GI home requires shutdown of Oracle GI stack on all the remote nodes in the
cluster. This also means you need to stop all Oracle RAC databases that depend on the GI stack,
ASM for data file, or ACFS file system.
1. Make sure to stop the Oracle databases running from the Oracle RAC or Oracle RAC One Node database homes.
$ %ORACLE_HOME%\bin\srvctl stop database -d <db-unique-name>
file systems.
3. As an administrator user, execute the following on all the remote nodes to stop the CRS stack:
4. Execute the following command on the local node As an administrator user execute:
# opatch apply -local
6. On each remote node:

%ORACLE_HOME%\crs\install\rootcrs.pl -prepatch -nonrolling
%ORACLE_HOME%\crs\install\rootcrs.pl -postpatch -nonrolling
8. Restart the Oracle databases that you have previously stopped in Step 1. $ %ORACLE_HOME%\bin\srvctl start database
-d <db-unique-name>
Case 4: Patching Oracle Restart Home
Use the following instructions to patch Oracle Restart home. You must be part of Administrator group to run these commands.
Oracle Restart is used in standalone server (non-clustered) environments only.
1. Stop any databases running on the standalone server using:

srvctl stop database -d <dbname>
1/28/2020 Document 2032004.1
2. Bring down Oracle High Availability Services using: (make sure ORACLE_HOME is pointing to the Grid Infrastructure home):

OR
%ORACLE_HOME%\crs\install\roothas.bat -prepatch
3. Verify that all Oracle services on the server have stopped by running:
If any service is found running, then use the Computer Management Services GUI or the net stop command to stop them.
Example-
net stop OracleDBConsole<SID>
net stop OracleJobScheduler<SID>
net stop "Oracle <SID> VSS Writer Service"
net stop "Oracle Object Service"
net stop OraFenceService
net stop OracleMTSRecoveryService
Also stop Distributed Transaction Coordinator service using:

net stop msdtc
4. Apply the patch to Grid Home using steps:

make sure ORACLE_HOME is pointing to the Grid Infrastructure home
opatch apply
5. Apply the patch to Database Home using steps:

make sure ORACLE_HOME is pointing to the Database home
opatch apply
6. Start Oracle High Availability Services using: (make sure ORACLE_HOME is pointing to the Grid Infrastructure home):
OR
%ORACLE_HOME%\crs\install\roothas.bat -postpatch
7. Start databases stoppped during step1 using:

srvctl start database -d <dbname>
8. Verify that Oracle services on the server are running using:

To patch the ACFS software in an Oracle Restart environment:
1. Unmount all ACFS file systems. Use instructions in Section 2.6 for unmounting ACFS file systems.
2. Run <GridHome>\bin\acfsroot install.
3. If the message, "A system reboot is recommended before using ACFS" shown, then a reboot must be issued before
4. Remount ACFS file systems. See Section 2.7 for instructions.
Case 5: Patching a Software Only GI Home Installation or Before the GI Home Is Configured
1. Apply the bundle patch using. As an administrator

opatch apply -local
Case 6: Patching a Flex Cluster
Follow these instructions if the configuration is a Flex Cluster
First node must be a HUB node.The last node can be either hub/leaf node.
Case 6.1: Patching a Flex cluster with 2 or more HUB nodes
1/28/2020 Document 2032004.1
1. Make sure GI Stack is up on the first hub node and at least one other hub node.
2. Make sure stack is up on all the leaf nodes
4. On the local node, apply the patch to the GI home and to the Database home.
a. As an administrator user, apply the patch to GI home and Database home using the steps listed under Section 5.
Case 6.2: Patching a Flex cluster with Only one HUB nodes
This configuration can be patched only in NON-Rolling fashion.
1. Make sure GI Stack is down on all the leaf nodes

3. On the local node, apply the patch to the GI home and to the Database home.
a. As an administrator user, apply the patch to GI home and Database home using the steps listed under Section 5.
2.4 Patch Post-Installation Instructions
After installing the patch, perform the following actions:
2.5 Patch Deinstallation
You can use the following steps to roll back patches. Choose the instructions that apply to your needs.
Case D1: Rolling Back the Oracle RAC Database Homes and GI Homes Together
Case D2: Rolling Back from the Oracle RAC Database Homes
Case D3: Rolling Back from the GI Home Alone
Case D4: Rolling Back the Patch from Oracle Restart Home
Case D5: Rolling Back the Patch from a Software Only GI Home Installation or Before the GI Home is Configured
Case D6:Rolling Back the Patch from a Flex Cluster
Case D1: Rolling Back the Oracle RAC Database Homes and GI Homes Together
Follow the instructions in this section if you would like to rollback the patch from all the Oracle RAC database homes of release
version %VERSION% and the %VERSION% GI home.
Case D1.1: GI Home Is Not Shared
Case D1.1.1: ACFS File System Is Not Configured and Database Homes Are Not Shared
You must be part of Administrator group to run these commands. Execute the following commands on each node of the cluster:

%ORACLE_HOME%\crs\install\rootcrs.pl -prepatch -rollback

%ORACLE_HOME%\crs\install\roothas.pl -prepatch -rollback
1/28/2020 Document 2032004.1
4. If any service is found running, then use the Computer Management Services GUI or the net stop command to stop them.
Example-

net stop msdtc
6. Rollback the patch from Grid Home using steps: make sure ORACLE_HOME is pointing to the Grid Infrastructure home
opatch rollback -id <PatchNumber> -local
7. Rollback the patch from Database Home using steps: make sure ORACLE_HOME is pointing to the Database home
home):

%ORACLE_HOME%\crs\install\rootcrs.pl -postpatch -rollback

%ORACLE_HOME%\crs\install\roothas.pl -postpatch -rollback
11. After all nodes have been patched using opatch, apply the SQL changes to the database by following steps listed in Section
6
Case D1.1.2A: GI Home and the Database Home Together, the GI Home Is Not Shared, the Database Home Is Not Shared
For each node, perform the following steps:
2. On the local node, roll back the patch from the GI home and the Database home. a. As administrator user, follow the
steps under Section 5
Section 6
Case D1.1.2B: GI Home and Database Home Together, the GI Home Is Not Shared, the Database Home Is Shared
1. From the Oracle database home, make sure to stop the Oracle RAC databases running on all nodes. Execute:
2. On the 1st node, unmount the ACFS file systems. Use instructions in Section 2.6 for unmounting ACFS file systems.
3. On the 1st node, roll back the patch from the GI Home a. As administrator user, follow the steps under Section 5 to roll
back the patch from GI home.
5. On the 1st node, remount ACFS file systems. See Section 2.7 for instructions.
6. On the 1st node, roll back the patch from the Database home using the steps under Section 5 to rollback patch from
database home. This operation will rollback the patch from the Database home across the cluster given that it is a shared
ACFS home.
7. On the 1st node only, restart the Oracle instance which you have previously stopped in Step 1. Execute:
%ORACLE_HOME%\bin\srvctl start instance -d <db-unique-name> -n <nodename>
8. On the 2nd (next) node, unmount the ACFS file systems. Use instructions in Section 2.6 for unmounting ACFS file
systems.
1/28/2020 Document 2032004.1
9. On the 2nd node, roll back the patch from the GI Home As administrator user, follow the steps under Section 5 to roll back
the patch from GI home.
11. On the 2nd node, remount ACFS file systems. See Section 2.7 for instructions.
12. On the 2nd node only, restart the Oracle instance which you have previously stopped in Step 1. Execute:
%ORACLE_HOME%\bin\srvctl start instance -d <db-unique-name> -n <nodename>
Case D1.2 GI Home Is Shared
Note:
An operation on a shared GI home requires shutdown of the Oracle GI stack on all the remote nodes
in the cluster. This also means you need to stop all Oracle RAC databases that depend on the GI
stack, ASM for data file, or ACFS file system.
1. Make sure to stop the Oracle databases running from the Oracle RAC database homes.
ORACLE_HOME: Complete path of the Oracle database home.

2. Make sure the ACFS file systems are unmounted on all the nodes. Use instructions in Section 2.6 for un-mounting ACFS
file systems.
3. As root user, execute the following on all the remote nodes to stop the CRS stack:
4. Roll back the patch from the GI home.
On local node, as administrator user, roll back the patch from GI Home using the steps listed under Section 5 to roll back
the patch from GI home
5. If the message, "A system reboot is recommended before using ACFS" shown, then a reboot must be issued before
6. Start the Oracle GI stack on all the remote nodes.

%ORACLE_HOME%\crs\install\rootcrs.pl -prepatch -nonrolling -rollback
%ORACLE_HOME%\crs\install\rootcrs.pl -postpatch -nonrolling -rollback
8. For each Oracle RAC database home, execute the following command on each node if the database home software is not
shared. For each database home execute the following as administrator user: make sure ORACLE_HOME is pointing to
the Database home
# opatch rollback -id <PatchNumber> -local
Note: The previous command should be executed only once on any one node if the database
home is shared.
9. Restart the Oracle databases that you have previously stopped in Step 1. Execute:
%ORACLE_HOME%\bin\srvctl start database -d <db-unique-name>
Section 6
Case D2: Rolling Back from the Oracle RAC Database Homes
You should use the following instructions if you prefer to roll back the patch from Oracle RAC databases homes alone.
Case D2.1: Non-Shared Oracle RAC Database Homes
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=276861904830978&id=2032004.1&_afrWindowMode=0&_adf.ctrl-state=9opt3… 10/18
1/28/2020 Document 2032004.1
Execute the following command on each node of the cluster.
As an administrator user rollback the patch from the Database Home using the steps listed under Section 5 to rollback patch
from Database home.
After all nodes have been patched using opatch, apply the SQL changes to the database by following steps listed in Section 6
Case D2.2: Shared Oracle RAC Database Homes
1. Make sure to stop the databases running from the Oracle RAC database homes from which you would like to roll back the
patch. Execute the following command to stop each database. %ORACLE_HOME%\bin\srvctl stop database -d
<db_unique_name>
2. As an administrator user execute only on the local node.
3. Restart the Oracle databases that were previously stopped in Step 1. Execute the following command for each database.
%ORACLE_HOME%\bin\srvctl start database -d <db_unique_name>
Case D3: Rolling Back from the GI Home Alone
You should use the following instructions if you prefer to roll back the patch from the Oracle GI (Grid Infrastructure) home alone.
Case D3.1 Shared GI Home
Note:
An operation in a shared GI home requires shutdown of Oracle GI stack on all the remote nodes in
the cluster. This also means you need to stop all Oracle RAC databases that depend on the GI stack,
ASM for data file, or ACFS file system.
1. Make sure to stop the Oracle databases running from the Oracle RAC database homes.
file systems.
3. As an administrator user, execute the following on all the remote nodes to stop the CRS stack:
4. Execute the following command on the local node. As an administrator user execute:
6. Start the Oracle GI stack on all the remote nodes.

%ORACLE_HOME%\crs\install\rootcrs.pl -postpatch -nonrolling -rollback
8. Restart the Oracle databases that you have previously stopped in Step 1. $ %ORACLE_HOME%\bin\srvctl start database
-d <db-unique-name>
Case D3.2: Non-Shared GI Home
If the GI home is not shared, then use the following instructions to roll back the patch from the GI home.
Case D3.2.1: ACFS File System Is Not Configured
Execute the following on each node of the cluster.
As an administrator user rollback the patch from the GI Home using the steps listed under Section 5
1/28/2020 Document 2032004.1
If the message, "A system reboot is recommended before using ACFS" is shown, then a reboot must be issued before
Case D3.2.2: ACFS File System Is Configured
Repeat Steps 1 through 6 for each node in the cluster:
1. From the Oracle database home, stop the Oracle RAC database running on that node. As the database home owner
execute:
$ %ORACLE_HOME%\bin\srvctl stop instance <instance-id> -d <db-unique-name> -n <node_name>
2. Make sure the ACFS file systems are unmounted on that node. Use instructions in Section 2.6 for unmounting ACFS file
systems.
3. Roll back the patch from the GI home on that node using the steps listed under Section 5.
5. Remount ACFS file systems on that node. See Section 2.7 for instructions.
6. Restart the Oracle database on that node that you have previously stopped in Step 1. As the database home owner
execute:
$ %ORACLE_HOME%\bin\srvctl start database -d <db-unique-name> -n <nodename>
Case D4: Rolling Back the Patch from Oracle Restart Home
Use the following instructions to roll back the patch from an Oracle Restart home. You must be part of Administrator group to run
these commands.
Oracle Restart is used in standalone server (non-clustered) environments only.
1. Stop any databases running on the standalone server using:

srvctl stop database -d <dbname>
2. Bring down Oracle High Availability Services using: (make sure ORACLE_HOME is pointing to the Grid Infrastructure home):

OR
%ORACLE_HOME%\crs\install\roothas.bat -prepatch -rollback
3. Verify that all Oracle services on the server have stopped by running:
Example-
net stop OracleDBConsole<SID>
net stop OracleJobScheduler<SID>
net stop "Oracle <SID> VSS Writer Service"
net stop "Oracle Object Service"
net stop OraFenceService
net stop OracleMTSRecoveryService
Also stop Distributed Transaction Coordinator service using:

net stop msdtc
4. Roll back the patch from Grid Home using steps:

make sure ORACLE_HOME is pointing to the Grid Infrastructure home
opatch rollback -id <PatchNumber>
5. Apply the patch to Database Home using steps:

make sure ORACLE_HOME is pointing to the Database home
6. Start Oracle High Availability Services using: (make sure ORACLE_HOME is pointing to the Grid Infrastructure home):
OR
%ORACLE_HOME%\crs\install\roothas.bat -postpatch -rollback
7. Start databases stoppped during step1 using:

srvctl start database -d <dbname>
1/28/2020 Document 2032004.1
8. Verify that Oracle services on the server are running using:

To update ACFS software in an Oracle Restart configuration:
1. Unmount all ACFS file systems. Use instructions in Section 2.6 for unmounting ACFS file systems.
2. Update ACFS: <Oracle-Restart-home>\bin\acfsroot install
Case D5: Rolling Back the Patch from a Software Only GI Home Installation or Before the GI Home is Configured
1. Roll back the CRS patch. As an administrator

Case D6: Rolling Back the Patch from a Flex Cluster
Follow these instructions if the configuration is a Flex Cluster
First node must be a HUB node.The last node can be either hub/leaf node.
Case D6.1: Rolling Back the Patch from a Flex cluster with 2 or more HUB nodes
1. Make sure GI Stack is up on the first hub node and at least one other hub node.
2. Make sure stack is up on all the leaf nodes
4. On the local node, rollback the patch from the GI home and from the Database home.
a. As an administrator user, rollback the patch from the GI home and from the Database home using the steps listed
under Section 5.
Case D6.2: Rolling Back the Patch from a Flex cluster with Only one HUB nodes
This configuration can be patched only in NON-Rolling fashion.
1. Make sure GI Stack is down on all the leaf nodes

3. On the local node, rollback the patch from the GI home and from the Database home.
a. As an administrator user, rollback the patch from GI home and Database home using the steps listed under Section
5.
2.6 Unmounting ACFS File Systems
ACFS file systems can be used by Oracle RAC for hosting software files for the database. It can also be used as a general
purpose file system for non-database files. The ACFS file system is managed and administered by the Oracle GRID
Infrastructure. So ACFS file systems will be impacted when shutting down the GI stack for patching GI homes. You must be part
of Administrator group to run these commands.
Shut down the processes using the software files on ACFS and then unmount the ACFS file system.
Note:
Make sure to stop the non-Oracle processes that use ACFS file systems.
If the ACFS file system is used by Oracle database software, then perform Steps 1 and 2.
1. Execute the following command to find the names of the CRS managed ACFS file system resource.
1/28/2020 Document 2032004.1
# crsctl stat res -w "TYPE = ora.acfs.type" -p | findstr /i VOLUME
2. Execute the following command to stop the CRS managed ACFS file system resource with the resource name found from
Step 1. # srvctl stop filesystem -d <volume device path> -n <node to stop file system on>
If the ACFS file system is not used for Oracle Database software and is registered in the ACFS registry, perform the following
steps.
1. Execute the following command to find all ACFS file system mount points. # acfsutil registry
2. Unmount ACFS file systems found in Step 1. # acfsdismount /v <drive_letter> <mount-point>
3. Verify that the ACFS file systems are unmounted. Execute the following command to verify. # acfsutil info fs
The previous command should return the following message if there is no ACFS file systems mounted.
"acfsutil info fs: ACFS-03036: no mounted ACFS file systems"
2.7 Mounting ACFS File Systems
If the ACFS file system is used by Oracle database software, then perform Steps 1 and 2. You must be part of Administrator
group to run these commands.
1. Execute the following command to find the names of the CRS managed ACFS file system resource.
# crsctl stat res -w "TYPE = ora.acfs.type" -p | findstr /i VOLUME
2. Execute the following command to start and mount the CRS managed ACFS file system resource with the resource name
found from Step 1.
# srvctl start filesystem -d <volume device path> -n <node to start file system on>
If the ACFS file system is not used for Oracle Database software and is registered in the ACFS registry, these file systems
should get automatically mounted when the CRS stack comes up. Perform Steps 1 and 2 if it is not already mounted.
1. Execute the following command to find all ACFS file system mount points.
# acfsutil registry
2. Mount ACFS file systems found in Step 1.
# acfsmountvol /v <drive_letter> <mount-point>
3 Known Issues
For information about OPatch issues, see My Oracle Support Note 293369.1 OPatch documentation list.
4 References
The following documents are references for this patch.
Note 293369.1 OPatch documentation list
Note 360870.1 Impact of Java Security Vulnerabilities on Oracle Products
Note 468959.1 Enterprise Manager Grid Control Known Issues
Note 1339140.1 Opatch/Patch Questions/Issues for Oracle Clusterware (Grid Infrastructure or CRS) and RAC Environments
5 Steps for Apply/Rollback Patch

Steps for Applying the Patch to a GI Home
You must be part of Administrator group to run these commands.

%ORACLE_HOME%\crs\install\rootcrs.pl -prepatch

1/28/2020 Document 2032004.1
Example-

net stop msdtc
opatch apply -local
home):

%ORACLE_HOME%\crs\install\rootcrs.pl -postpatch

Steps for Rolling Back the Patch From a GI Home
You must be part of Administrator group to run these commands.

%ORACLE_HOME%\crs\install\rootcrs.pl -prepatch -rollback

Example-

net stop msdtc
1/28/2020 Document 2032004.1
home):

%ORACLE_HOME%\crs\install\rootcrs.pl -postpatch -rollback

Steps for Applying the Patch to an Oracle RAC Home Installation
2. Explicitly stop the following services, if they are running, use the Computer Management Services GUI or the net stop
command to stop them.

net stop msdtc
4. Apply the patch to Database Home using steps: make sure ORACLE_HOME is pointing to the Database home
opatch apply -local
Steps for Rolling Back the Patch from an Oracle RAC Home Installation
2. Explicitly stop the following services, if they are running, use the Computer Management Services GUI or the net stop
command to stop them.

net stop msdtc
4. Rollback the patch from Database Home using steps: make sure ORACLE_HOME is pointing to the Database home
6 Steps to Run the datapatch Utility for Single Tenant Versus Multitenant (CDB/PDB)
For each database instance running on the Oracle home being patched, run the datapatch utility as described in Table 3.
1. Table 3 Steps to Run the datapatch Utility for Single Tenant Versus Multitenant (CDB/PDB)
1/28/2020 Document 2032004.1
Steps Single Tenant (non-CDB/PDB) Steps Multitenant (CDB/PDB)

1 % sqlplus /nolog 1 % sqlplus /nolog
2 SQL> Connect / as sysdba 2 SQL> Connect / as sysdba
3 SQL> startup 3 SQL> startup
4 SQL> quit 4 SQL> alter pluggable database all
open;Foot 1
5 % cd $ORACLE_HOME/OPatch 5 SQL> quit
6 % ./datapatch -verbose 6 % cd $ORACLE_HOME/OPatch
7 % ./datapatch -verbose
Footnote 1 It
is recommended the Post Install step be run on all pluggable databases; however, the following command
(SQL> alter pluggable database PDB_NAME open ) could be substituted to only open certain PDBs in the
multitenant database. Doing so will result in the Post Install step only being run on the CDB and opened PDB's. To update
a pluggable database at a later date (skipped or newly plugged in), open the database using the alter pluggable
database command mentioned previously and rerun the datapatch utility. The datapatch utility will then run the
necessary rollback scripts. An entry will be added to the dba_registry_sqlpatch view reflecting the patch rollback.
7 Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are
hearing impaired.
Copyright Â© 2006, 2015, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure
and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you
may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any
part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law
for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors,
please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S.
Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S.
Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal
Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and
adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the
extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial
Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software or hardware is developed for general use in a variety of information management applications. It is not developed
or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If
you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe,
backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any
damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license
and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron
logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third
parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect
to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or
damages incurred due to your access to or use of third-party content, products, or services.
1/28/2020 Document 2032004.1
Copyright Ã Æ Ã¢â ¬Å¡Ã â Ã Â© 2006, 2012, Oracle and/or its affiliates. All rights reserved.
Didn't find what you are looking for? Ask in Community...
Related
Products
Oracle Cloud > Oracle Platform Cloud > Oracle Cloud Infrastructure - Database Service > Oracle Cloud Infrastructure - Database Service
Oracle Cloud > Oracle Platform Cloud > Oracle Database Cloud Service > Oracle Database Cloud Exadata Service
Oracle Cloud > Oracle Platform Cloud > Oracle Database Backup Service > Oracle Database Backup Service
Oracle Cloud > Oracle Platform Cloud > Oracle Database Cloud Service > Oracle Database Exadata Express Cloud Service
Oracle Cloud > Oracle Platform Cloud > Oracle Database Cloud Service > Oracle Database Cloud Service
Oracle Database Products > Oracle Database Suite > Oracle Database > Oracle Database - Enterprise Edition > Clusterware
Oracle Cloud > Oracle Platform Cloud > Oracle Database Cloud Service > Oracle Database Cloud Schema Service
Oracle Cloud > Oracle Infrastructure Cloud > Oracle Cloud at Customer > Oracle Database Exadata Cloud Machine
Back to Top
Copyright (c) 2020, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement

Supplemental Readme - Patch Installation and Deinstallation For 12.1.0.x.x Windows Bundles (Doc ID 2032004.1)

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Supplemental Readme - Patch Installation and Deinstallation For 12.1.0.x.x Windows Bundles (Doc ID 2032004.1)

Загружено:

Авторское право:

Доступные форматы

1/28/2020 Document 2032004.

Dashboard Knowledge Service Requests Patches & Updates Community

Copyright (c) 2020, Oracle. All rights reserved. Oracle Confidential.

Was this document helpful?

Section 1, "Patch Information"

Section 2.1, "Patch Installation Prerequisites" Information Centers

As the GI home owner execute:

2.1.3 Validation of Oracle Inventory

$ %ORACLE_HOME%\OPatch\opatch lsinventory -oh %ORACLE_HOME%

2.1.4 Unzipping the Patch

Unzip the patch in a shared location.

2.2 OPatch Automation for GI

OPatchauto is currently not supported on Windows platform.

2.3 Patch Installation

GI home is shared or non-shared

Case 1.1: GI Home Is Not Shared

1. Stop the database instance running on the node.

srvctl stop instance -d <dbname> -i <instanceName>

%ORACLE_HOME%\perl\bin\perl -I%ORACLE_HOME%\perl\lib -I%ORACLE_HOME%\crs\install

If this is an Oracle Restart Home, execute:

%ORACLE_HOME%\perl\bin\perl -I%ORACLE_HOME%\perl\lib -I%ORACLE_HOME%\crs\install

net start | findstr /i ora

net stop OracleREMExecService

5. Also stop Distributed Transaction Coordinator service using:

net stop msdtc

If this is an Oracle Restart Home, execute:

%ORACLE_HOME%\perl\bin\perl -I%ORACLE_HOME%\perl\lib -I%ORACLE_HOME%\crs\install

9. Start the database instance on the node using:

srvctl start instance -d <dbname> -i <instanceName>

crsctl status resource -t

%ORACLE_HOME%\bin\srvctl stop database -d <db-unique-name>

$ %ORACLE_HOME%/bin/srvctl start instance -d <db-unique-name> -n <nodename>

$ %ORACLE_HOME%/bin/srvctl start instance -d <db-unique-name> -n <nodename>

For each node, perform the following steps:

Case 1.2: GI Home Is Shared

Follow these instructions in this section if the GI home is shared.

%ORACLE_HOME%\bin\srvctl stop database -d <db-unique-name>

# <GI_HOME>\bin\crsctl stop crs

%ORACLE_HOME%\perl\bin\perl -I%ORACLE_HOME%\perl\lib -I%ORACLE_HOME%\crs\install

# opatch apply <UNZIPPED_PATCH_LOCATION>/%BUGNO% -local

%ORACLE_HOME%\bin\srvctl start database -d <db-unique-name>

Case 2: Patching Oracle RAC Database Homes

Case 2.1: Non-Shared Oracle RAC Database Homes

Case 2.2: Shared Oracle RAC Database Homes

Case 3: Patching GI Home Alone

Case 3.1: Non-Shared GI Home

Case 3.1.1: ACFS File System Is Not Configured

Execute the following on each node of the cluster.

Case 3.1.2: ACFS File System Is Configured

Repeat Steps 1 through 6 for each node in the cluster:

$ %ORACLE_HOME%\bin\srvctl stop instance <instance-id> -d <db-unique-name> -n <node_name>

$ %ORACLE_HOME%\bin\srvctl start database -d <db-unique-name> -n <nodename>

Case 3.2: Shared GI Home

Follow these instructions in this section if the GI home is shared.

$ %ORACLE_HOME%\bin\srvctl stop database -d <db-unique-name>

# <GI_HOME>\bin\crsctl stop crs

# opatch apply -local

%ORACLE_HOME%\perl\bin\perl -I%ORACLE_HOME%\perl\lib -I%ORACLE_HOME%\crs\install

Case 4: Patching Oracle Restart Home

Oracle Restart is used in standalone server (non-clustered) environments only.

1. Stop any databases running on the standalone server using:

%ORACLE_HOME%\perl\bin\perl -I%ORACLE_HOME%\perl\lib -I%ORACLE_HOME%\crs\install

Also stop Distributed Transaction Coordinator service using: