Watch Private Spice
A large bank encountered error code 21 while applying the July 2024 CPU patch to 50 Oracle Homes. Standard fixes failed. Investigation revealed:
The most common reason for Error Code 21 is . Oracle uses a "fuser" mechanism to ensure that the files it is about to modify are not currently in use by the database or another process. If OPatch detects that a file to be patched is currently locked or "busy," it will fail with Code 21 to prevent data corruption. opatch failed with error code 21
This is the cause in 90% of cases. OPatch attempts to patch the Oracle Home, but it detects that a process is still holding a lock on the files. This usually happens because: A large bank encountered error code 21 while
chown -R oracle:oinstall $ORACLE_HOME
Do not guess. The opatch utility generates detailed logs located in: $ORACLE_HOME/cfgtoollogs/opatch/ Oracle uses a "fuser" mechanism to ensure that
Check available space in the Oracle home and /tmp :
Error code 21 is one of the most common yet frustrating obstacles in Oracle patching. Unlike generic "permission denied" errors, code 21 often masks a variety of underlying issues ranging from environmental misconfigurations to corrupted inventory files.