Edit D:\app\Administrator\product\11.2.0\dbhome_1\OPatch\jlib\oracle\opatch\opatchutil\applysql

Edit D:\app\Administrator\product\11.2.0\dbhome_1\OPatch\jlib\oracle\opatch\opatchutil\applysql_help.txt

DESCRIPTION
    This operation is used to apply sql related actions(sql and
sql procedure actions) for a patch which is already applied to 
Oracle Home. This utility can be used to apply the sql
related actions of a patch, which could have been skipped 
or partially executed. It can also be used to patch other
Database instances not specified during patch apply.

This utility will also invoke the apply sql script specified 
in the patchmd.xml of the patch.

SYNTAX
opatch util ApplySql   [-connectString <List of connect strings> ]
		       [-force]   
                       [-id <List of patch IDs> ]                      
		       [-invPtrLoc <Path to oraInst.loc> ]
                       [-jre <LOC> ] [-no_inventory ] 
		       [-oh <ORACLE_HOME> ] [-ph <Patch location> ] 
                       [-phBaseDir 
                          <Directory with patch directories (or) zips ] 
                       [-phBaseFile <File having patch locations> ]
                       [-sqlScript <Path of the custom sql file ]                        
                       
OPTIONS

-connectString
              This option can be used to specify the list of database
              instances on which the patch needs to be applied. The
              value for this option is specified as per the following
              syntax "SID:User:Passwd:Node". The SID is a must, others
              can be ignored, OPatch takes default values for it.
              Ex: oracle:dba:dba:mymachine,oracle1:::.
              NOTE: If the system is not part of RAC setup, then to
              patch just the local node, provide the node name as
              empty string.

-force
             This option is used to patch the database instance, which is
             already patched.

-id 
              List of patch IDs for which the sql related actions needs
              to be applied. This option is mandatory for this operation
              except for the case where the user may need to run a custom
              sql script independently

-invPtrLoc 
              Used to locate the oraInst.loc file. Needed when the
              installation used the -invPtrLoc flag. This should be
              the path to the oraInst.loc file.

-jre
              This option tells OPatch to use JRE (java) from the
              specified location instead of the default location
              under Oracle Home.

-no_inventory
              This option can be used if the inventory to be looked for 
              the applied patch(es) is corrupted or not present. It should 
              be used in conjunction with -ph (or) -phBaseFile (or) 
              -phBaseDir options.
        
        -oh
              The oracle home to work on. This takes precedence over
              the environment variable ORACLE_HOME.

-ph
              Used to specify patch location. This option is ideally used
              when -no_inventory is specified. The id of the patch specified
              must be in the list specified by -id option.

-phBaseDir
              Used to specify a directory containing patch directories (or) zip
              files. This option is ideally used when -no_inventory is specified.
              The ids of the patch(es) specified must be in the list specified by
              -id option.

-phBaseFile
              Used to specify a file which contains patch locations delimited
              by new line. This opton is ideally used when -no_inventory is
              specified. The ids of the patch(es) specified must be in the list 
              specified by -id option.

-sqlScript
              This option is used to specify a custom sql script path to run
              on the specified db instances.

Ms-Dos/Windows Unix Write backup

jsp File Browser version 1.2 by www.vonloesch.de