Which two statements are true regarding hot patching? (Choose two.)
A.
It requires relinking of the Oracle binary.
B.
It does not require database instance shutdown.
C.
It can detect conflicts between two online patches.
D.
It is available for installing all patches on all platforms.
E.
It works only in a single database instance environment.
Explanation:
Online Patching
Regular patches typically contain .o (object) files and/or .a (archive) libraries, and therefore
require a relink of the RDBMS binary. Online patches, however, contain .so files, which are
dynamic/shared libraries, and do not require a relink of the RDBMS binary. Consequently,
since a relink is not needed, you can apply or roll back online patches while the RDBMS
instance is running. This simplifies administration, because no downtime is needed, and also
results in a much quicker turnaround time for installing or de-installing Online Patches.A regular RDBMS patch can require many minutes to install, since it requires instance
shutdown, a relink, and instance startup. On the other hand, you can install an online patch
in just a few seconds.
Online patches are only applicable for Oracle RDBMS and not any other products. Online
patches are currently supported on the following Windows and UNIX platforms for version
11.2.0.1.0 and later:
Linux x86
Linux x86_64
HP-UX Itanium
Solaris SPARC 64-bit
Solaris AMD 64-bit
AIX (AIX 6.1 and later)
About Patch Conflicts:
All patches may not be compatible with one another. For example, if you apply a patch, all
the bugs the patch fixes could reappear after you apply another patch. This is called a
conflict situation. OPatch detects such situations and raises an error when it detects a
conflict.