DESCRIPTION
    This operation runs the prerequisite checks on an ORACLE_HOME.
    This command doesn't support System Patch.

SYNTAX
opatch prereq <command> [-id <Comma separated list of patch IDs>]
			[-invPtrLoc <Path to oraInst.loc> ] 
			[-jre <LOC>] [-local_node <Local node name>] 
                        [-oh <ORACLE_HOME> ] [ -online ]
	                [-ph <Path to the single patch location>]
                        [-phBaseDir <Path to the dir containing all patches>]
                        [-phBaseFile <Path to the file containing the
                      	  location of the patches to be applied>] 
		        [-property_file <Path to property file>]
	                [-remote_nodes <List of remote nodes (node1,node2)>]                        
                        [-sid <Comma separated list of database SIDs>]
                        [-connectString  <List of connect strings>]
			
COMMANDS       

       CheckActiveFilesAndExecutables
              Check if there are any file(s) that are active,
              which are touched by the patch to be applied
              or rolled back.

       CheckActiveServices
              Check for the services that are active.
              Note: Applicable for Windows platforms only.

       CheckApplicable
              Check for the presence of the required components in
              the ORACLE_HOME and check if all the actions of the 
              given patch(es) are applicable.

       CheckApplicableProduct
              Check if the patch is applicable for the given Oracle Home. 
              If the patch is marked for stand-alone homes, then it can not
              be applied on normal oui-based home and vice versa. 
              Also, a patch can be marked as a hybrid patch, where it is
              applicable for both homes.

       CheckCentralInventoryForOH
              Check if the given ORACLE_HOME is registered
              in the central inventory specified by the
              oraInst.loc file.

       CheckCentralInventoryForRWSession
              Check if a RW (read-write) session can be created
              for the given central inventory.

       CheckCentralInventoryLocation
              Validate the Central Inventory location. Check if it
              has the correct directory structure and has the 
              inventory.xml with read permissions.

       CheckComponents
              Check for the presence of the required components in
              the ORACLE_HOME.

       CheckConflictAgainstOH
              Check if there are any conflicts between the patch(es)
              to be applied and the patch(es) in the OH.

       CheckConflictAgainstOHWithDetail
              Check if there are any conflicts between the patch(es)
              to be applied and the patch(es) in the OH, by giving
              out the detailed information about the 
              conflicts/supersets.

       CheckConflictAmongPatches
              Check if there are any conflicts among the patch(es)
              to be applied.

       CheckConflictAmongPatchesWithDetail
              Check if there are any conflicts among the patch(es) 
              to be applied, by giving out the detailed information
              about the conflicts/supersets.

       CheckFileVersions
              Check if the copy actions of Fusion Applications patch(es)
              have alleast one or more file version(s) greater than the 
              version(s) installed in the Oracle Home.

       CheckFusionAppsCompatible
              Check if OUI for the Oracle Home supports patching of
              Fusion applications.

       CheckForCRSHomeIfRAC
              Check if the given Central Inventory has a CRS Home 
              registered with it, if it is a RAC setup.

       CheckForIdenticalPatchInOracleHome
              Check if the given list of patch(es) are identical with
              respect to the patch(es) installed in the Oracle Home.

       CheckForInputValues
              Check if the input values provided to OPatch are enough for
              OPatch to proceed further.

       CheckForNoOpPatches
              Check if any of the patch(es) provided by the user are no-op.
              patches.  A no-op patch. cannot be applied to the Oracle Home
              and can be skipped. This prereq will fail for no-op. patches.

       CheckIfOHLockedForPatching
              Check if the ORACLE_HOME is locked for patching
              by any previous unsuccessful OPatch Session.

       CheckInstalledOneOffs
              Check if all the patches provided by the user to rollback
              are present in the given Oracle Home.

       CheckMinimumOPatchVersion
              Check if all the patches provided by the user satisfy
              the requirement of minimum OPatch version for the OPatch
              currently being used.

       CheckOneOffSuperset
              Check if the given input Fusion Applications patch list 
              are all candidates for one-off (or) singleton supersets. 
              This prereq does not do any checks among the input patch list.

       CheckOracleHome
              Check if the given ORACLE_HOME is valid. Check if it 
              has the inventory files with proper permissions.

       CheckOraInstLocation
              Check if the oraInst.loc file is proper and has the
              read permissions. 

       CheckOUILocation
              Check the ORACLE_HOME for the presence of OUI.

       CheckOUIVersionCompatible
              Check if the OUI in the ORACLE_HOME is compatible 
              for the OPatch.

       CheckPatchApplicableOnCurrentPlatform
              Check if the given patch(es) is applicable on the
              current platform.

       CheckPatchApplyDependents
              Check if all the patch(es) required by the patch(es) 
              currently being  installed is present in the Oracle Home or not.

       CheckPatchRollbackDependents
              Check if there are any patch(es) in the Oracle Home that are
              depending on the patch(es) being currently rolled back. 

       CheckPatchShipHome
              Check if the given patch to be applied has the 
              proper structure and has the correct permissions 
              for all the files.

       CheckRACNodeList
              Check if all the nodes in the RAC setup are valid, up
              and reachable.

       CheckRemoteCommandInvocable
              Check if commands can be invoked on the remote machines.

       CheckRemoteCopyAndRemove
              Check if files can be copied to and removed from the 
              remote machines.

       CheckRequiredLibs
              Check if all the required OUI libraries are present
              in the given ORACLE_HOME.

       CheckRollbackable
              Check if the given patch(es) can be rolled back from 
              the ORACLE_HOME.

       CheckRollbackSid
	      Check if the given patch(es) can be rolled back from
              the ORACLE_HOME using the given SIDs. 
       
       CheckSystemCommandAvailable
              Check if all the commands required for applying or
              rolling back the given patch are present in the system.

       CheckSystemSpace
              Check if enough system space is available for 
              the patch(es) to be applied.

       CheckUserAdminPrivilege
              Check is the user is 'root'. 
              Note: OPatch should not be invoked by 'root', if so
                    then this check fails.

       CheckPatchingModel
              Check if the patching model of all incoming patch(es) is
              compatible with that of the Oracle Home.

OPTIONS

       -connectString
              This option can be used to specify the list of database
              instances and remote nodes. 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
              specify just the local node, provide the node name as
              empty string. This option cannot be used along with 'sid'
              option.
                    
       -id
              This option can be used to specify the patch IDs of all
              the patches that are to be rollbacked from the given OH.

   
       -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. 

       -local_node
              This option can be used to specify to OPatch the local
              node name to be used for RAC mode application of the patch.

       -oh
              The oracle home to work on. This takes precedence over
              the environment variable ORACLE_HOME.

       -online
              This option specify the online part of the given patch
              is used

       -ph    
              This option can be used to specify the path to the
              patch location. Ex: /tmp/101010

       -phBaseDir
              This option can be used to specify the path to base dir
              where all the patches to be applied are kept.
              Note: The directory should contain only non-duplicate patches
                    in zipped or unzipped format.

       -phBaseFile
              This option can be used to specify complete path to the
              file containing the location of the patches to be applied.

       -property_file
              The user defined property file for OPatch to use. The
              path to the property file should be absolute. This
              property file takes precedence over the one that is
              supplied with OPatch.

       -remote_nodes
              This option can be used to specify to OPatch the list
              of remote nodes to be used for RAC mode application of
              the patch. The node names are comma separated and
              without spaces.

       -sid   
              This option can be used to specify the SIDs of the database
              instances. This option can be used only for local system
              operations.
 
