My Oracle Support Banner

OPatch Failed With Error Code 135 Unable to parse the xml file,because of offending special character in the patch directory. (Doc ID 1600791.1)

Last updated on SEPTEMBER 20, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 9.2.0.1 to 12.1.0.1 [Release 9.2 to 12.1]
Information in this document applies to any platform.

Symptoms

$ opatch apply -invPtrLoc /u01/app/oracle/product/11gR2/oraInst.loc
Oracle Interim Patch Installer version 11.2.0.3.4
Copyright (c) 2012, Oracle Corporation. All rights reserved.

Interim Patch metadata parsing failure... 'Unable to parse the xml file.'
Argument(s) Error... Unable to parse the xml file.

Please check the arguments and try again.

OPatch failed with error code 135

Opatch log Shows :

[Nov 14, 2013 2:33:05 PM] OUI-67022:Interim Patch metadata parsing failure... 'Unable to parse the xml file.'
[Nov 14, 2013 2:33:05 PM] OPatch invoked as follows: 'apply -invPtrLoc /u01/app/oracle/product/11gR2/oraInst.loc '
[Nov 14, 2013 2:33:05 PM] OUI-67135:Argument(s) Error... Unable to parse the xml file.
[Nov 14, 2013 2:33:05 PM] Please check the arguments and try again.
[Nov 14, 2013 2:33:05 PM] Stack Description: java.lang.UnsupportedOperationException: Argument(s) Error... Unable to parse the xml file.
[Nov 14, 2013 2:33:05 PM] StackTrace: oracle.opatch.OPatchSession.main(OPatchSession.java:1711)
[Nov 14, 2013 2:33:05 PM] StackTrace: oracle.opatch.OPatch.main(OPatch.java:613)

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.