Search In The Blog

Monday 26 June 2017

autopatch analyze failed with “opatchauto bootstrapping failed with error code 1” during Oracle 12c PSU

opatchauto analyze failed with “opatchauto bootstrapping failed with error code 1” during Oracle 12c PSU

We are in process of applying JAN PSU Patch (24917825) on Grid and database Home. This was a six node RAC cluster (12.1.0.2.0) with no previous patchset. During the patch apply two node “opatchauto analyze” command failed with below error.
[root@myserver32 ~]# export GRID_HOME=/u01/app/12.1.0/grid
[root@myserver32 ~]# export PATH=$PATH:$GRID_HOME
[root@myserver32 ~]# /u01/app/12.1.0/grid/OPatch/opatchauto apply /u01/app/grid/OPatch_soft/24917825 -analyze

OPatchauto session is initiated at Sat Apr 29 10:44:29 2017
Usage: java [-options] class [args...]
           (to execute a class)
   or  java [-options] -jar jarfile [args...]
           (to execute a jar file)
where options include:
    -d32          use a 32-bit data model if available
    -d64          use a 64-bit data model if available
    -server       to select the "server" VM
                  The default VM is server,
                  because you are running on a server-class machine.


    -cp <class search path of directories and zip/jar files>
    -classpath <class search path of directories and zip/jar files>
                  A : separated list of directories, JAR archives,
                  and ZIP archives to search for class files.
    -D<name>=<value>
                  set a system property
    -verbose:[class|gc|jni]
                  enable verbose output
    -version      print product version and exit
    -version:<value>
                  require the specified version to run
    -showversion  print product version and continue
    -jre-restrict-search | -no-jre-restrict-search
                  include/exclude user private JREs in the version search
    -? -help      print this help message
    -X            print help on non-standard options
    -ea[:<packagename>...|:<classname>]
    -enableassertions[:<packagename>...|:<classname>]
                  enable assertions with specified granularity
    -da[:<packagename>...|:<classname>]
    -disableassertions[:<packagename>...|:<classname>]
                  disable assertions with specified granularity
    -esa | -enablesystemassertions
                  enable system assertions
    -dsa | -disablesystemassertions
                  disable system assertions
    -agentlib:<libname>[=<options>]
                  load native agent library <libname>, e.g. -agentlib:hprof
                  see also, -agentlib:jdwp=help and -agentlib:hprof=help
    -agentpath:<pathname>[=<options>]
                  load native agent library by full pathname
    -javaagent:<jarpath>[=<options>]
                  load Java programming language agent, see java.lang.instrument
    -splash:<imagepath>
                  show splash screen with specified image
See http://www.oracle.com/technetwork/java/javase/documentation/index.html for more details.

OPatchauto session completed at Sat Apr 29 10:44:29 2017
Time taken to complete the session 0 minute, 0 second

opatchauto bootstrapping failed with error code 1.
[root@myserver32 ~]#


Solution :

1.       Check and compare the Java version on al node – In my case it was identical.
2.       Go to $GRID_HOME/oui
take the backup of oraparam.ini file and remove the # from below line -
JRE_MEMORY_OPTIONS=" -Xms150m -Xmx256m -XX:MaxPermSize=128M"


[oracle@ myserver32 oui]$ cat oraparam.ini
[Oracle]
DISTRIBUTION=FALSE
SOURCE=
LICENSE_LOCATION=
JRE_LOCATION=../../jdk/jre
OUI_LOCATION=..
OUI_CORE_LOCATION=..
OPATCH_LOCATION=..
DEFAULT_HOME_LOCATION=
DEFAULT_HOME_NAME=
NLS_ENABLED=TRUE
JRE_MEMORY_OPTIONS=" -Xms150m -Xmx256m -XX:MaxPermSize=128M"
JRE_MEMORY_OPTIONS=" -mx2048m"
NO_BROWSE=/net
BOOTSTRAP=TRUE
CLUSTERWARE={"oracle.crs","10.1.0.2.0"}
VENDORCLUSTERWARE=TRUE
#THIN_JDBC_FILENAME is optional and defaults to classes12.jar
..
..
..
3.       Re run the autopatch analyze, it should work.

No comments:

Post a Comment