How To Rollback An Online Patch If The Database Is Down Or Removed

How To Rollback An Online Patch If The Database Is Down Or Removed

APPLIES TO:

Oracle Server - Enterprise Edition - Version 11.1.0.6 to 11.2.0.3 [Release 11.1 to 11.2]
Oracle Universal Installer - Version 11.1.0.6 to 11.2.0.3 [Release 11.1 to 11.2]
Information in this document applies to any platform.

SYMPTOMS

Rollback of an online (aka hot) patch fails if the database is down or the database has been removed from the server. An error similar to the one below may be seen in the log file.

 

INFO:Prerequisite check "CheckDBInstanceUp" failed. 

DB Instance "xxxx" is down or the given SID is invalid.

CAUSE

Online (aka hot) patches are applied to the RDBMS home when the database is up and running. Installing an online patch does not require shutting down the database instance or relinking the oracle binaries.

 

It is not possible to rollback an online patch in a normal or standard way if the database is down or if the database has been removed from the server. Online patches are a special kind of patch that can be applied or rolled back from a live database. Special instructions need to be followed if the database is down or if the database has been removed.

 

SOLUTION

 

Steps to remove an Online patch if the database is down or removed:

$ opatch rollback -id patch id -no_sysmod

 

The "no_sysmod" option specifies not to update the files in the system. It just updates the inventory. It also will not execute the pre and post scripts.

$ opatch rollback -id patch id -no_sysmod -connectString  :::

 

The "connectString" option can be used to specify a list of database instances on which the patch needs to be rolled back.

Note---> This informationmation taken from oracle metalink. all copy rights oracle only.