opatch auto parameters

Usage:
      opatch auto <patch directory>
                  [-oh  <oracle home location>]
                  [-och <crs home location>]
                  [-rollback]
                  [-ocmrf <ocm response file location>]
                  [-norestart]
                  [-report]
                  [-olderver]

      Options:

       patch_directory

                 Default is the current directory.
                 This is the top level directory path where the patch is
                 unzipped.

             Always unzip the gipsu/gi one-off in a empty directory
                 where there are no other directory/files existing.

             If the directory under which the patch is unzipped is /tmp/patchdir

             Example:
                 opatch auto /tmp/patchdir



     -rollback

                 The patch will be rolled back, not applied
                 This option requires patch_directory to be passed

                 Example:
                 opatch auto /tmp/patchdir -rollback

     -oh         Database/Clusterware home locations

                 comma_delimited_list_of_oralcehomes_to_patch
                 The default is all applicable Oracle Homes including
                 the clusterware home .Use this option  to patch RDBMS homes where
                 no database is registered or any specific database home or
                 clusterware home. In order to patch a 11.2 Database under Grid home of
                 version 12.1 and above, run opatch auto from the DB home.

                 Example:
                 opatch auto /tmp/patchdir -oh <oracle_home1_path,oracle_home2_path>

     -och        Grid infrastructure home location
                 absolute path of crs home location. This is only used
                 to patch Clusterware home when the clusterware stack is down

             Example:
                 opatch auto /tmp/patchdir -och <oracle_gridhome_path>

     -ocmrf      OCM response file location

                 Absolute path of the OCM response file. This is required for
                 silent mode patching

     -norestart
                 The clusterware stack and database home resources will not be
                 started after patching.

     -report
                 opatch would be run in a report mode where all the prereq checks
                 would be performed without modifying the binaries. The patch would
                 not be applied/rolled-back on the home.

     -olderver
                 This parameter must be passed when the clusterware stack is down, along
                 with the -och parameter. It must only be used if the Grid Home version is
                 11.2.0.2 or older and not for newer versions of the Grid.

                 Example:
                 opatch auto /tmp/patchdir -och <oracle_home> -olderver