datapatch Commands

Use commands with the datapatch keyword to apply patches to the specified Oracle Database.

• rhpctl apply datapatch
  Applies datapatch to the specified Oracle Database.

rhpctl apply datapatch

Applies datapatch to the specified Oracle Database.

Syntax

rhpctl apply datapatch -workingcopy workingcopy_name [-targetnode node_name] 
  [-root | -cred cred_name | -sudouser sudo_user_name -sudopath sudo_binary_location | 
  -auth plugin_name [-arg1 name1:value1 [-arg2 name2:value2 ...]]]
  [-dbname db_name_list] [-excludedblist db_name_list] [-eval] [-schedule {timer_value | NOW | PAUSE}] 
  [-jobtag tag_name]

Parameters

Table A-27 rhpctl apply datapatch Command Parameters

Parameter	Description
-workingcopy workingcopy_name	Specify the name of the working copy to which you want to apply the datapatch.
-targetnode node_name	Optionally, you can specify the name of a node in a remote cluster that has no Fleet Patching and Provisioning Client.
-root | -cred cred_name | -sudouser sudo_user_name -sudopath sudo_binary_location | -auth plugin_name plugin_args	If you choose to use the -targetnode parameter, then you must choose either root, a credential name, sudo, or an authentication plugin to access the remote node. Choose -root to perform super user operations as root. Alternatively, you can choose either to specify a credential name to associate the user name and password credentials to access a remote node, to perform super user operations as a sudo user by specifying a sudo user name and the path to the sudo binary, or to use an authentication plugin to access the remote node.
-dbname db_name_list	Specify the unique names of the databases (DB_UNIQUE_NAME without DB_DOMAIN) that you want to move to the patched working copy. Note: If you are moving a non-clustered (single-instance) database, then, for the value of the -dbname parameter, you must specify the SID of the database instead of the database name.
-excludedblist db_name_list	Alternative to using the -dbname parameter, you can use the -excludedblist parameter to patch all databases except specific databases.
–eval	Use the –eval parameter to print auto-generated batches of nodes and sequence of moves without actually performing the move operation.
-schedule {timer_value | NOW | PAUSE}	Optionally, you can use this parameter to schedule a time to run this operation, in ISO-8601 format, as in the following example: 2018-07-25T19:13:17+05 If NOW is specified or the option is omitted, then the job is scheduled immediately. If PAUSE is specified, then the job starts in the paused state and you need to resume the job using the rhpctl resume job -jobid job_id command.
-jobtag tag_name	Optionally, you can associate a user-defined tag with the scheduled jobs.