Oracle RAC Rolling Patch description

 

I have prepared several documents about Oracle patch installation, as follows:

 

Introduction to Oracle patch system and opatch tools

Http://blog.csdn.net/tianlesoftware/article/details/5809526

 

New Features of Oracle 11g -- online patching (hot Patching) Description

Http://blog.csdn.net/tianlesoftware/article/details/8214412

 

How to update the opatch tool version in Oracle

Http://blog.csdn.net/tianlesoftware/article/details/6857059

 

 

Here, let's take a look at the RAC patch. Here, we want to explain to the DB patch that if it is a rac gi upgrade or a PSR, it still needs to be stopped. The whole CRS must be stopped because of the GI upgrade. However, you can use the rolling method to install the independent patch of the database.

 

I. Several Methods of RAC patch

 

There are three different patch methods in the RAC environment:

 

1.1 All-node patch)

In this mode, opatch applies patches on the local node, applies patches on other nodes, and updates inventory. During this patch process, all instances must be shut down.

 

The procedure for this mode is as follows:

(1) Shut Down instances on all nodes.

(2) applypatch on all nodes.

(3) Start all instances.

 

1.2 use minimum downtime for patch

 

In this mode, opatch first applies opatch to the local node. Then, let the user select another node to perform the patch. Other nodes also complete the patch, and finally update the inventory.

 

In this mode, the downtime is the time between the second node and the first node.

 

The minimum downtime is as follows:

(1) shut down the instance of Node 1

(2) apply patch on node 1

(3) Shut Down instances on node 2.

(4) apply the patch on node 2.

(5) Shut Down instances on node 3.

(6) At this time, instances of Node 1 and node 2 can be started.

(7) Apply the patch on node 3.

(8) Start the instance on node 3.

 

During the above process, downtime is the time from node 3 shutdown to node 1 and 2 startup.

 

1.3 Rolling Patch (no down time required)

 

In this method, there is no downtime. Each node can be patched and other nodes can run normally. In this case, the system will not be affected.

 

Rolling patches do not always require downtime because some patches support rolling patches and some do not. For those that do not support rolling patches, you can only install them in the old method.

 

The procedure of Rolling Patch is as follows:

(1) shut down the instance of Node 1

(2) apply the patch on node 1.

(3) Start the instance on node 1.

(4) Shut Down instances on node 2.

(5) Apply the patch on node 2.

(6) Start the instance on node 2.

(7) Shut Down instances on node 3.

(8) Apply the patch on node 3.

(9) Start the instance on node 3.

 

 

1.4 how to determine which method to use

 

Only patches meeting specific conditions can be rolled. This type of patch is called Rolling updateble patch or rolling patch.

 

If you specify the minimum downtime, select the minimum downtime. If not, use the Rolling Patch. Finally, all nodes must be patched simultaneously.

 

 

 

 

2. How can I determine whether a patch is a rolling patch?

 

When Oracle releases a patch, it marks the patch as rolling or not rolling. Most patches are rolling.

 

Rolling patches have the following features:

(1) patch does not affect the database content

(2) The patch has nothing to do with the RAC internal communication structure.

(3) patch changes the program logic without modifying the common header definitions of kernel modules. The patch includes client patches, which only affect some tools, such as export, import, SQL * Plus, and SQL * loader.

 

Only independent patches are rollable. You cannot perform rolling patches for Patch sets.

 

The merge patch combined by multiple rolling patches is not a Rolling Patch.

 

Starting from Oracle 9.2.0.4, all patches are marked as rolling or not rolling patches according to the defined rules. The previous patches are marked as not rolling.

 

 

2.1 check whether the patch is a rolling patch.

 

Run the following command:

-9i or 10gr1: opatchquery-is_rolling

-10gr2: opatch query-All [unzipped patchlocation] | grep Rolling

-10gr2 on Windows: opatch query-All [unzipped patchlocation] | findstr Rolling

-Later 10gr2 or 11G: opatchquery-is_rolling_patch [unzipped patch location]

 

 

If the extracted patch path contains multiple sub-patch directories, The opatch command will not work properly.

 

-- The root user cannot execute the judgment command:

[Root @ Rac1 16056266] #/u01/APP/GRID/11.2.0/opatch query-is_rolling_patch/u01/software/16056266

The user is root. opatch cannot continue ifthe user is root.

 

 

Opatch failed with error code 255

 

[Root @ Rac1 16056266] # Su-grid

[Grid @ Rac1 ~] $/U01/APP/GRID/11.2.0/opatch query-is_rolling_patch/u01/software/16056266

Oracle interim patch installer version11.2.0.3.4

Copyright (c) 2012, oraclecorporation. All rights reserved.

 

 

Oracle Home:/u01/APP/GRID/11.2.0

Central inventory:/u01/APP/orainventory

From:/u01/APP/GRID/11.2.0/orainst. Loc

Opatch version: 11.2.0.3.4

Oui version: 11.2.0.3.0

Log File Location:/u01/APP/GRID/11.2.0/export toollogs/opatch/opatch2013-06-09_04-14-34AM_1.log

 

Failed to load the patch object. Possible causes are:

Thespecified path is not an interim patch shiphome

Meta-data files are missing from the patch area

Patch location =/u01/software/16056266

Details = input metadata files are missing.

 

Patch location "/u01/software/16056266" doesn't point to a valid patch area.

-- An error is reported because the path of/u01/software/16056266 contains other sub-patches.

 

Opatch failed with error code 75

 

[Grid @ Rac1 ~] $ CD/u01/software/16056266

[Grid @ Rac1 16056266] $ ls

13343438 13696216 13923374 14275605 14727310 16056266 patchmd. xml readme.html readme.txt

 

-- View a single patch:

[Grid @ Rac1 16056266] $/u01/APP/GRID/11.2.0/opatch query-is_rolling_patch/u01/software/16056266/13343438/

Oracle interim patch installer version11.2.0.3.4

Copyright (c) 2012, oraclecorporation. All rights reserved.

 

 

Oracle Home:/u01/APP/GRID/11.2.0

Central inventory:/u01/APP/orainventory

From:/u01/APP/GRID/11.2.0/orainst. Loc

Opatch version: 11.2.0.3.4

Oui version: 11.2.0.3.0

Log File Location:/u01/APP/GRID/11.2.0/export toollogs/opatch/opatch2013-06-09_04-15-17AM_1.log

 

--------------------------------------------------------------------------------

Patch is a Rolling Patch: True

 

Opatch succeeded.

 

[Grid @ rac116056266] $/u01/APP/GRID/11.2.0/opatch query-is_rolling_patch/u01/software/16056266/13696216

Oracle interim patch installer version11.2.0.3.4

Copyright (c) 2012, oraclecorporation. All rights reserved.

 

Oracle Home:/u01/APP/GRID/11.2.0

Central inventory:/u01/APP/orainventory

From:/u01/APP/GRID/11.2.0/orainst. Loc

Opatch version: 11.2.0.3.4

Oui version: 11.2.0.3.0

Log File Location:/u01/APP/GRID/11.2.0/export toollogs/opatch/opatch2013-06-09_04-15-32AM_1.log

 

--------------------------------------------------------------------------------

Patch is a Rolling Patch: True

 

Opatch succeeded.

 

 

2.2 limitations of patch

 

2.2.1 patch on Shared File System

Currently opatch uses the shared file system as a single instance for patch. Opatch places the patch file in the ORACLE_HOME directory. Because it is shared, other nodes can also access it.

Therefore, for the shared filesystem environment, you cannot use the opatch advanced function: rollingpatch. During the patch, all nodes must be shut down.

 

 

2.2.2 one node per patch

Patch can be performed independently on each node, that is, only the-local keyword is used during opatch, so that only the local node can be patched.

 

 

 

 

 

 

 

 

Bytes --------------------------------------------------------------------------------------------

All rights reserved. reprinted articles are allowed, but source addresses must be indicated by links. Otherwise, the documents will be held legally responsible!

QQ: 251097186

Skype: tianlesoftware

Email: tianlesoftware@gmail.com

Blog: http://blog.csdn.net/tianlesoftware

WEAVER: http://weibo.com/tianlesoftware

Twitter: http://twitter.com/tianlesoftware

Facebook: http://www.facebook.com/tianlesoftware

LinkedIn: http://cn.linkedin.com/in/tianlesoftware