Job Role Separation: OPatch failed with error code 135 - Argument(s) Error... Given 'ocmrf' file does not exists.

(Doc ID 1931555.1)

Last updated on AUGUST 08, 2016

Applies to:

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


Using opatch auto to apply patch 18706472, it failed with error code 135:

opatchauto2014-09-23_04-21-57.log shows:

2014-09-23 04:24:41: s_run_as_user2: Running /bin/su oracle -c ' /oracle/product/11.2.0/db/OPatch/opatch napply /software_dump/latestpatch/18706472/18522509 -local -silent -ocmrf /home/grid/responsefile/file.rsp -oh /oracle/product/11.2.0/db -invPtrLoc /oracle/product/11.2.0/db/oraInst.loc '
2014-09-23 04:24:42: Removing file /tmp/filexagz0g
2014-09-23 04:24:42: Successfully removed file: /tmp/filexagz0g
2014-09-23 04:24:42: /bin/su exited with rc=135

2014-09-23 04:24:42: status of apply patch is 34560
2014-09-23 04:24:42: The apply patch output is Oracle Interim Patch Installer version
Copyright (c) 2013, Oracle Corporation. All rights reserved.

Argument(s) Error... Given 'ocmrf' file does not exists.

Please check the arguments and try again.

OPatch failed with error code 135

 ls -l shows the response file file.rsp exists:

[grid@racnode1 ~]$ ls -l /home/grid/responsefile/file.rsp
-rw-r--r-- 1 grid oinstall 621 Sep 23 03:52 /home/grid/responsefile/file.rsp



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