Grid Infrastructure:OPatch apply (manual step) fails to apply patch because perl process is running

(Doc ID 2409442.1)

Last updated on JUNE 18, 2018

Applies to:

Oracle Database - Enterprise Edition - Version and later
Information in this document applies to any platform.


OPatch apply failed with error code 41 since was being used by perl processes.Successfully unlocked GI_HOME and clusterware was stopped.

opatch logs:

[test-cluster@node1 20302006]$ /test-cluster/64bit/crs121/OPatch/opatch apply -local
Oracle Interim Patch Installer version
Copyright (c) 2018, Oracle Corporation. All rights reserved.

Oracle Home : /test-cluster/64bit/crs121
Central Inventory : /test-cluster/64bit/app/oracle/oraInventory
from : /test-cluster/64bit/crs121/oraInst.loc
OPatch version :
OUI version :
Log file location : /test-cluster/64bit/crs121/cfgtoollogs/opatch/20302006_Jun_08_2018_09_50_23/apply2018-06-08_09-50-23AM_1.log

Applying interim patch '20302006' to OH '/test-cluster/64bit/crs121'
Verifying environment and performing prerequisite checks...
Prerequisite check "CheckActiveFilesAndExecutables" failed.
The details are:

Following executables are active :
Log file location: /test-cluster/64bit/crs121/cfgtoollogs/opatch/20302006_Jun_08_2018_09_50_23/apply2018-06-08_09-50-23AM_1.log

Recommended actions: OPatch needs to modify files which are being used by some processes.

OPatch failed with error code 41





Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms