Specify the type of operation for which you want an audit query.

Specify the entity for which you want an audit query.

Optionally, you can choose to run a query audit on a particular user who performed Fleet Patching and Provisioning operations.

Optionally, you can choose to run a query audit on a particular client cluster where Fleet Patching and Provisioning operations were performed.

Optionally, you can specify a time interval for which to run an audit query. Timestamps must be in the format YYYY-MM-DD.

Optionally, you can specify a time before which to run an audit query. Timestamp must be in the format YYYY-MM-DD.

Optionally, you can specify a time after which to run an audit query. Timestamp must be in the format YYYY-MM-DD.

Optionally, you can specify a number of the first audit records for a given time.

Optionally, you can specify a number of the last audit records for a given time.

Optionally, you can specify a particular audit record ID.

You can choose this parameter to show the maximum record configuration.

Specify the name of the cluster in which you want to create the client.

Optionally, you can specify the path to the XML file that is created by the Fleet Patching and Provisioning Server (specific to the client cluster), which contains the information the client needs to configure its connection to the server.

Optionally, you can specify the name of a node in a remote cluster that has no Fleet Patching and Provisioning Client.

If you choose to use the -targetnode parameter, then you must choose either sudo or root to access the remote node.

If you choose sudo, then you must use the –sudouser parameter and specify a user name to run super-user operations, and a path to the location of the sudo binary.

Optionally, you can choose to specify a credential name to associate the user and password credentials to access a remote node.

Alternative to –sudouser, –root, or –cred, you can use –auth to specify an authentication plugin to access a remote node.

You can specify either built-in roles or roles that you have defined, and you can assign multiple uses to each role. Use commas to separate multiple roles and users.

Optionally, you can specify the version of the credentials file format, such as 18.0.0.0.0.

Specify the name of the Oracle Grid Infrastructure Gold Image which the resulting response file will support.

Specify a file path where the response file that RHPCTL generates will be copied. The RHPCTL command generates name of the response file and displays it while the command is running.

If you have a partially complete response file and you want it to be completed with reference to the target nodes, then specify the response file name using this parameter.

Note: The response file must include the node list, client name, and Oracle home path.

Specify a comma-delimited list of nodes on which you plan to provision Oracle Clusterware (using the resulting response file) in the following format: node_name:node_vip[:node_role][,node_name:node_vip[:node_role]...]

Specify the name of the target cluster to be probed.

Specify the location of the Oracle home.

You must choose either sudo or root to access the remote nodes.

If you choose sudo, then you must specify a user name to run super-user operations, and a path to the location of the sudo binary.

Optionally, you can choose to specify a credential name to associate the user and password credentials to access a remote node.

Alternative to –sudouser, –root, or –cred, you can use –auth to specify an authentication plugin to access a remote node.

Specify the name of the Oracle Grid Infrastructure installation user.

Specify the SCAN name.

Specify the name of the client cluster that you want to export.

Specify the path to the location of the client data file.

-client cluster_name

Specify the name of the client cluster that you want to modify.

-enabled {TRUE | FALSE}

Specify whether the client is enabled.

You can modify either built-in roles or roles that you have defined, and you can assign multiple uses to each role.

When you use the -maproles parameter, use a plus sign (+) to map more than one user to a specific role. Separate additional role/user pairs with commas.

-password

Optionally, you can specify a password to recreate the Fleet Patching and Provisioning Client credentials.

Specify the name of the image that you want to update.

Specify the name of the node on which you want to update the Fleet Patching and Provisioning Client.

Alternative to specifying a target node, you can specify batches of nodes.

Note: If you use this parameter for Oracle Database Appliance nodes, then run the command twice, in succession, specifying any one Oracle Database Appliance node for the first run, and another Oracle Database Appliance node for the second run.

Specify the name of the image.

Specify a response file to be used to provision Oracle Grid Infrastructure.

Specify a comma-delimited list of nodes on which Oracle Clusterware will be provisioned in the following format: node_name:node_vip[:node_role][,node_name:node_vip[:node_role]...]

You must choose either sudo or root to access the remote nodes.

If you choose sudo, then you must specify a user name to run super-user operations, and a path to the location of the sudo binary.

Optionally, you can choose to specify a credential name to associate the user and password credentials to access a remote node.

Alternative to –sudouser, –root, or –cred, you can use –auth to specify an authentication plugin to access a remote node.

Specify the name of the Oracle Grid Infrastructure installation user.

Specify the name of the cluster you want to verify.

Specify the SCAN name.

Specify the location of the Oracle home.

Use this parameter to ignore warnings during validation.

Use this parameter to run a fixup script, which automatically applies changes to the nodes to satisfy changes that CVU recommends.

Optionally, you can use the -setupSSH parameter to set up passwordless SSH user equivalence on the remote nodes for the provisioning user.

Specify a credential name to associate the user and password credentials to access a remote node.

You must choose either to provide root access to access a remote node or a sudo user name and path to the sudo binary to perform super user operations.

Specify the name of a working copy.

Specify the unique name of the database (DB_UNIQUE_NAME without DB_DOMAIN) that you are adding.

Specify a node or comma-delimited list of several nodes on which to create the database.

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.

Optionally, you can pass a value to the useractiondata parameter of the user action script.

Optionally, you can use this parameter to evaluate the impact of this command on the system without actually running the command.

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

Specify the name of an existing working copy for the pluggable database that you want to add.

Specify the name of the multitenant container database to which you want to add the pluggable database.

Specify a name for the pluggable database you are adding.

Optionally, you can specify the path to the data file destination location for the pluggable database.

If you choose to use the -targetnode parameter, then you must choose either sudo or root to access the remote node.

If you choose sudo, then you must specify a user name to run super-user operations, and a path to the location of the sudo binary.

Optionally, you can choose to specify a credential name to associate the user and password credentials to access a remote node.

Alternative to –sudouser, –root, or –cred, you can use –auth to specify an authentication plugin to access a remote node.

Optionally, you can specify the name of a node in the cluster on which you want to run this operation.

Optionally, you can pass a value to the useractiondata parameter of the user action script.

Specify the name of an existing working copy for the pluggable database that you want to delete.

Specify the name of the multitenant container database from which you want to delete the pluggable database.

Specify the name of the pluggable database you want to delete.

If you choose to use the -targetnode parameter, then you must choose either sudo or root to access the remote node.

If you choose sudo, then you must specify a user name to run super-user operations, and a path to the location of the sudo binary.

Optionally, you can choose to specify a credential name to associate the user and password credentials to access a remote node.

Alternative to –sudouser, –root, or –cred, you can use –auth to specify an authentication plugin to access a remote node.

Optionally, you can specify the name of a node in the cluster on which you want to run this operation.

Optionally, you can pass a value to the useractiondata parameter of the user action script.

Specify a name for the working copy for the database that you want to delete.

Specify the unique name of the database (DB_UNIQUE_NAMEwithout DB_DOMAIN) that you are deleting.

If you choose to use the -targetnode parameter, then you must choose either sudo or root to access the remote node.

If you choose sudo, then you must specify a user name to run super-user operations, and a path to the location of the sudo binary.

Optionally, you can choose to specify a credential name to associate the user and password credentials to access a remote node.

Alternative to –sudouser, –root, or –cred, you can use –auth to specify an authentication plugin to access a remote node.

Optionally, you can specify the name of a node in a remote cluster that has no Fleet Patching and Provisioning Client.

Optionally, you can pass a value to the useractiondata parameter of the user action script.

Specify the name of a working copy.

Specify the unique name of the database (DB_UNIQUE_NAME without DB_DOMAIN) that you are deleting.

Specify a node or comma-delimited list of several nodes from which to delete the database instance.

Choose either sudo or root to access the remote nodes.

If you choose sudo, then you must specify a user name to run super-user operations, and a path to the location of the sudo binary.

Optionally, you can choose to specify a credential name to associate the user and password credentials to access a remote node.

Alternative to –sudouser, –root, or –cred, you can use –auth to specify an authentication plugin to access a remote node.

Optionally, you can use this parameter to attempt to have services running on the instance that want to delete fail over to another instance.

Optionally, you can use -drain_timeout to specify the time, in seconds, allowed for resource draining to be completed. Accepted values are an empty string (""), 0, or any positive integer. The default value is an empty string, which means that this parameter is not set. If it is set to 0, then draining occurs, immediately.

The draining period is intended for planned maintenance operations. During the draining period, all current client requests are processed, but new requests are not accepted.

Optionally, you can specify a stop option for the database. Options include: ABORT, IMMEDIATE, NORMAL, TRANSACTIONAL, and TRANSACTIONAL_LOCAL.

Optionally, you can pass a value to the useractiondata parameter of the user action script.

Optionally, you can use this parameter to evaluate the impact of this command on the system without actually running the command.

Specify the name of the working copy to where you want to move the database.

Specify the name of the working copy from which the database is to be moved.

Alternatively, you can specify the source Oracle home path.

Specify the ORACLE_BASE path for provisioning the Oracle database home (required only for ORACLEDBSOFTWARE image type).

Specify the name of the client cluster.

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.

Alternative to using the -dbname parameter, you can use the -excludedblist parameter to patch all databases except specific databases.

Optionally, you can choose one of the three following methods to move a database:

• Use the -nonrolling parameter to move the database in a non-rolling mode. By default, databases move in a rolling mode.

• Use the –forcerolling parameter to force the Oracle home to move in rolling mode.

• Use the -batches parameter to specify a comma-delimited list of batches of nodes (where each batch is a comma-delimited list of node names enclosed in parentheses) enclosed in double quotation marks ("") in the format: "(nA,nB,...),(...,nY,nZ)".

• Alternatively, use the -smartmove parameter. Use the -saf availability parameter to specify a service availability factor, which is the minimum percentage of instances on which a service must remain running during the move.

Use the -separate parameter to process batches separately. When you use this parameter, the move command returns after each batch. The move operation for the first batch must specify the source home and other parameters that apply to all batches (such as -nonrolling and -keepplacement). Control subsequent batches using the -continue, -skip, and -abort parameters.

Use the –eval parameter to print auto-generated batches of nodes and sequence of moves without actually performing the move operation.

Optionally, you can use this parameter to ignore if a patched working copy is missing some patches which are present in the source path or working copy.

Use this parameter to ensure that services of administrator-managed Oracle RAC or Oracle RAC One Node databases are running on the same instances before and after the move operation.

Optionally, use the -disconnect parameter to disconnect all sessions before stopping or relocating services. If you choose to use -disconnect, then you can choose to use the -noreplay parameter to disable session replay during disconnection.

Specify the time, in seconds, allowed for resource draining to be completed. Accepted values are an empty string (""), 0, or any positive integer. The default value is an empty string, which means that this parameter is not set. If it is set to 0, then draining occurs, immediately.

The draining period is intended for planned maintenance operations. During the draining period, all current client requests are processed, but new requests are not accepted.

Optionally, you can specify a stop option for the database. Options include: ABORT, IMMEDIATE, NORMAL, TRANSACTIONAL, and TRANSACTIONAL_LOCAL.

Use this parameter to indicate not to run datapatch for databases you are moving.

Optionally, you can specify the name of a node in a remote cluster that has no Fleet Patching and Provisioning Client.

Optionally, you can supply a list of users to whom email notifications of the move will be sent, in addition to the owner of the working copy.

If a batch-mode rhpctl move database command fails at any point, then, after correcting the cause of the error, you can rerun the command with the -continue parameter to attempt to patch the failed batch. If you want to skip the failed batch and continue with the next batch, use the -continue and -skip parameters together. If you attempt to skip over the last batch, then the move operation is terminated.

If a batch-mode or non-batch-mode rhpctl move database command fails, then you can rerun the command with the -revert parameter to undo the changes that have been made, and return the configuration to its initial state.

If a batch-mode or non-batch-mode rhpctl move database command fails, then you can rerun the command with the -abort parameter to terminate the patching process and leave the cluster in its current state.

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.

Optionally, you can pass a value to the useractiondata parameter of the user action script.

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.

Optionally, you can specify either the name of the client cluster or the node on which the operation is to be run.

Optionally, you can pass a value to the useractiondata parameter of the user action script.

2019-01-07T19:13:17+05

You can also specify NOW to schedule the operation, immediately.

Specify the name of the source working copy from which you want to upgrade the database.

Alternative to specifying the name of the source working copy, you can specify the path to the source Oracle home.

If you use the -sourcehome parameter, then you can, optionally, specify a different ORACLE_BASE from the source Home.

Specify either the name of the client cluster or the name of a node in a remote cluster with no Fleet Patching and Provisioning Client on which to provision a working copy.

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.

Specify the name of the destination working copy to which the database is to be upgraded. If the destination working copy does not exist, then specify the gold image from which to create it, and optionally, the path to where to provision the working copy.

Specify the name of the database you are upgrading.

Optionally, you can pass a value to the useractiondata parameter of the user action script.

Optionally, you can use this parameter to evaluate the impact of this command on the system without actually running the command.

Specify the unique name of the database that you want to upgrade.

Specify the name of the destination working copy to which the database is to be upgraded.

Optionally, you can specify the name of the source working copy from which you want to upgrade the database.

Alternative to specifying the name of the source working copy, you can specify the path to the source Oracle home.

Specify the name of the Oracle GoldenGate source working copy.

Specify the name of the Oracle GoldenGate destination working copy.

Optionally, you can specify the name of an Oracle ASM disk group to use as a redo log location for the clones database.

Optionally, you can specify the name of an Oracle ASM disk group to use as a recovery area for the cloned database.

Optionally, you can specify the source RMAN backup location.

Optionally, you can specify the name of a node in a remote cluster with no Fleet Patching and Provisioning Client on which to provision a working copy.

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.

Optionally, you can use this parameter to specify a value to be passed to the useractiondata parameter of a useraction script

Specify the name of the working copy of the active Oracle Grid Infrastructure home that you want to install and configure on the specified node.

Alternatively, you can specify the name of the client cluster to which to add cluster nodes.

Specify a comma-delimited list of nodes on which Oracle Clusterware will be provisioned in the following format: node_name:node_vip[:node_role][,node_name:node_vip[:node_role]...]

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.

Optionally, you can specify the name of a node in a remote cluster that has no Fleet Patching and Provisioning Client.

Optionally, you can use this parameter to forcibly add nodes ignoring any previously failed add-node operation.

Sets up passwordless SSH user equivalence on the remote nodes for the provisioning user.

Optionally, you can pass a value to the useractiondata parameter of the user action script.

Optionally, you can use this parameter to evaluate the impact of this command on the system without actually running the command.

Optionally, you can schedule a time to run this command in ISO-8601 format. For example: 2018-01-21T19:13:17+05.

Specify the name of a working copy of the Oracle Grid Infrastructure home that you want to remove from the specified node.

Alternatively, you can specify the name of the client cluster from which to remove cluster nodes.

Specify a comma-delimited list of node names from which to delete Oracle Grid Infrastructure.

You must choose either sudo or root to access the remote nodes.

If you choose sudo, then you must specify a user name to run super-user operations, and a path to the location of the sudo binary.

Optionally, you can choose to specify a credential name to associate the user and password credentials to access a remote node.

Alternative to –sudouser, –root, or –cred, you can use –auth to specify an authentication plugin to access a remote node.

Name of a node in a remote cluster with no Fleet Patching and Provisioning Client.

Optionally, you can pass a value to the useractiondata parameter of the user action script.

Optionally, you can use this parameter to evaluate the impact of this command on the system without actually running the command.

Specify the name of the destination working copy to which you want to move Oracle Grid Infrastructure.

Alternative to specifying the name of the destination working copy, you can specify the path to the destination for the move of an Oracle home when you are moving the Oracle Grid Infrastructure home.

If you want to move Oracle Grid Infrastructure from a working copy, then specify the name of the source working copy from which you want to move the Grid home.

If you are moving Oracle Grid Infrastructure from an unmanaged (not provisioned by Fleet Patching and Provisioning) Oracle home, then specify the path to the Oracle home from which you want to move Oracle Grid Infrastructure.

Name of a node in a remote cluster with no Fleet Patching and Provisioning Client.

Use this parameter to ignore if the patched working copy is missing some patches which are present in the source path or working copy.

Use this parameter to move the Oracle home in a non-rolling fashion.

Specify this parameter to ensure that services of administrator-managed Oracle RAC or Oracle RAC One Node databases are running on the same instances before and after the move operation.

Specify this parameter to automatically patch databases when you patch Oracle Grid Infrastructure.

Optionally, you can specify a list of databases on which you want to perform the patching operation.

Optionally, you can exclude specific databases from the patching operation.

Optionally, you can use this parameter to indicate not to run datapatch for databases being moved.

Optionally, you can use this parameter to disconnect all sessions before stopping or relocating services.

Optionally, you can choose one of the following stop options for the database: ABORT, IMMEDIATE, NORMAL, TRANSACTIONAL, or TRANSACTIONAL_LOCAL.

Optionally, you can use this parameter to specify a service drain timeout, in seconds.

Optionally, you can specify a comma-delimited list of batches of nodes (where each batch is a comma-delimited list of node names enclosed in parentheses) enclosed in double quotation marks ("") in the format: "(nA,nB,...),(...,nY,nZ)".

Alternatively, you can use the -smartmove parameter to auto-generate a list of batches of nodes and move databases by restarting instances after each batch.

Optionally, you can use the -saf parameter to specify the service availability factor, which is the minimum percentage of instances on which a service must remain running during the move.

Optionally, you can schedule a time to run this command in ISO-8601 format. For example: 2018-01-21T19:13:17+05.

Use this parameter to continue restarting the Oracle Clusterware stack on the next batch of nodes.

Use this parameter to revert back to before the move operation.

Use this parameter to abort an ongoing move operation.

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.

When using a persistent home path for both the source and destination working copies, specify -cleanpids to ensure processes are stopped completely on the source home.

Optionally, you can pass a value to the useractiondata parameter of the user action script.

Use this parameter to evaluate the rhpctl move gihome command and print automatically generated batches of nodes and the sequence of moves without actually running the command.

Specify the name of the source working copy from which the Oracle Grid Infrastructure home needs to be upgraded.

Alternative to specifying the name of the source working copy, you can specify the path to the unmanaged Oracle Grid Infrastructure home.

In addition to specifying the source Oracle Grid Infrastructure home, you must also specify a node that is in a remote cluster that has no Fleet Patching and Provisioning Client.

Specify the name of the destination working copy to which the Oracle Grid Infrastructure home is to be upgraded.

If you choose to use the -targetnode parameter, then you must choose either sudo or root to access the remote node.

If you choose sudo, then you must specify a user name to run super-user operations, and a path to the location of the sudo binary.

Optionally, you can choose to specify a credential name to associate the user and password credentials to access a remote node.

Alternative to –sudouser, –root, or –cred, you can use –auth to specify an authentication plugin to access a remote node.

Use this parameter to ignore the CVU prerequisite checks.

Specify the name of the image that you want to add.

Specify the name of the working copy from which to create the image.

Specify the software type. ORACLEDBSOFTWARE (default) for Oracle Database software, ORACLEGISOFTWARE for Oracle Grid Infrastructure software, ORACLEGGSOFTWARE for Oracle GoldenGate software, LINUXOS for Linux operating system ISO, or SOFTWARE for all other software. If you use custom image types, then specify the name of your image type.

If you want to add an image to an image series, then specify the name of an image series.

Specify the state of the image.

Specify the name of the image to which you want to allow access.

Specify the either of the following:

• A user for which you want to allow access to the image and, optionally, the cluster name of the client cluster with the user.

• The role for which you want to allow access to the image.

Specify the name of the image you want to deploy.

Optionally, you can specify the name of a node to which you want to deploy the image. This parameter is required if the node hosting the home is not a Fleet Patching and Provisioning Client.

If you use the -targetnode parameter, then you must specify either sudo or root to perform super user operations.

Specify the name of the image to which you want to disallow access.

Specify either of the following:

• A user for which you want to disallow access to the image and, optionally, the cluster name of the client cluster with the user.

• The role for which you want to disallow access to the image.

Specify the name of the image that you want to add.

Specify the absolute path location of the software home that you want to import (for Oracle Database images, this is the ORACLE_HOME).

Specify the software type. Use ORACLEDBSOFTWARE (default) for Oracle database software, ORACLEGISOFTWARE for Oracle Grid Infrastructure software, ODAPATCHSOFTWARE, for engineered systems (Oracle Data Appliance), or SOFTWARE for all other software. For a custom image type, use the image type name.

Optionally, you can specify the version of the software you are importing.

Specify the user with read access to the files and directories under the specified path.

Note: This parameter is applicable only for non-Oracle database software homes.

Specify whether the state of the image is testable, restricted, or published.

Specify the name of the client cluster.

Specify the name of the node from which you want to import the image. This parameter is required if the node hosting the home is not an Fleet Patching and Provisioning Client.

If you use the -targetnode parameter, then you must specify either sudo or root to perform super user operations.

Optionally, you can pass a value to the useractiondata parameter of the user action script.

Specify a Fleet Patching and Provisioning Server cluster from which you want to request images.

You can request copies of gold images from a peer Fleet Patching and Provisioning Server, specifically, by image name, series name, or image type. Alternatively, you can use the -all parameter to request copies of all gold images from the peer Fleet Patching and Provisioning server.

If you choose to request images by image type, then specify ORACLEDBSOFTWARE (default) for Oracle Database software, ORACLEGISOFTWARE for Oracle Grid Infrastructure software, ORACLEGGSOFTWARE for Oracle GoldenGate software, and SOFTWARE for all other software. For a custom image type, use the image type name.

Specify the name of the image that you want to modify.

You can modify the software type. Use ORACLEDBSOFTWARE (default) for Oracle database software, ORACLEGISOFTWARE for Oracle Grid Infrastructure software, or SOFTWARE for all other software. For a custom image type, use the image type name.

Specify the name of the image you want to query.

Optionally, you can use the -dbtemplate parameter to display template file names in the default template directory.

Specify the software type. Use ORACLEDBSOFTWARE (default) for Oracle database software, ORACLEGISOFTWARE for Oracle Grid Infrastructure software, or SOFTWARE for all other software. For a custom image type, use the image type name.

Use this parameter to specify the version of the image software you are querying.

Use this parameter to specify the operating system platform to which the image corresponds.

Specify the name of the image that you want to promote.

Specify one of the following as the name of the state of the image:

• TESTABLE:
• RESTRICTED:
• PUBLISHED:

Specify a Fleet Patching and Provisioning Server cluster from which you want to stop updates.

You can updates from a peer Fleet Patching and Provisioning Server, specifically, by image name, series name, or image type. Alternatively, you can use the -all parameter to stop updates from the peer Fleet Patching and Provisioning server.

If you choose to stop updates by image type, then specify ORACLEDBSOFTWARE (default) for Oracle Database software, ORACLEGISOFTWARE for Oracle Grid Infrastructure software, ORACLEGGSOFTWARE for Oracle GoldenGate software, and SOFTWARE for all other software. For a custom image type, use the image type name.

Specify the name of the image type you are creating.

Specify a base image type on which the image type you are creating is based. Use ORACLEDBSOFTWARE (default) for Oracle Database software, ORACLEGISOFTWARE for Oracle Grid Infrastructure software, ORACLEGGSOFTWARE for Oracle GoldenGate software, and SOFTWARE for all other software.

Specify a comma-delimited list of names of user actions

Specify the name of the image type to which you are granting access. Use ORACLEDBSOFTWARE (default) for Oracle database software, ORACLEGISOFTWARE for Oracle Grid Infrastructure software, or SOFTWARE for all other software. For a custom image type, use the image type name.

Specify an operating system user to whom you are granting access to the image type. Either this parameter or the -role parameter is required.

Optionally, you can specify the name of the client cluster to which the operating system user belongs, if you choose to use the -user parameter.

Alternative to the -user parameter, you can specify a particular role to which to grant access to the image.

Specify the name of the image type from which you are revoking access. Use ORACLEDBSOFTWARE (default) for Oracle database software, ORACLEGISOFTWARE for Oracle Grid Infrastructure software, or SOFTWARE for all other software. For a custom image type, use the image type name.

Specify an operating system user from whom you are revoking access to the image type. Either this parameter or the -role parameter is required.

Optionally, you can specify the name of the client cluster to which the operating system user belongs, if you choose to use the -user parameter.

Alternative to the -user parameter, you can specify a particular role from which to revoke access to the image.

Specify the name of the image type you want to modify. Use ORACLEDBSOFTWARE (default) for Oracle database software, ORACLEGISOFTWARE for Oracle Grid Infrastructure software, ORACLEGGSOFTWARE for Oracle GoldenGate software, or SOFTWARE for all other software. For a custom image type, use the image type name.

Specify a comma-delimited list of names of user actions

Optionally, you can specify the job ID value for the job you want to delete that you obtained while scheduling the job. If you choose not to use this parameter, then RHPCTL deletes all jobs.

Use this parameter to forcibly delete a job.

Optionally, you can specify the job ID value for the job you want to query that you obtained while scheduling the job. If you choose not to use this parameter, then RHPCTL queries all jobs.

Optionally, you can specify the name of a client cluster for which you want to query jobs.

Optionally, you can specify the user name of the user for whom a software home is being provisioned.

Optionally, you can use this parameter to return only job details.

Specify the name of the client cluster.

Optionally, you can specify the name of a particular node in a cluster from which to collect configuration information.

If you use the -targetnode parameter, then you must specify either sudo or root to perform super user operations.

Specify the name of the client cluster in which you want to compare operating system configurations.

Specify the name of a node in a remote cluster.

Specify an identifier of an operating system configuration to be considered as a reference.

Specify an identifier of an operating system configuration to be compared.

Specify the name of the client cluster.

Optionally, you can specify the number of scheduled backups you want to be maintained. The default value is 37.

Optionally, you can specify a start date and time to run configuration collection according to the following example: 2018-07-23T00:00:00-07

Optionally, you can specify the configuration collection interval in number of days.

Optionally, you can use this parameter to collect configuration information, immediately.

Optionally, you can specify the name of a particular node in a cluster from which to collect configuration information.

If you use the -targetnode parameter, then you must specify either sudo or root to perform super user operations.

Optionally, you can use this parameter to forcibly modify the count for the -retaincopies parameter previously set.

Optionally, you can specify the name of the Fleet Patching and Provisioning Server cluster for which you want to view the information.

Optionally, you can specify the image policy for the peer Fleet Patching and Provisioning Server for which you want to view the information.

Specify a name for the role that you want to create.

Specify a comma-delimited list of roles to include with the new role.

• GH_AUDIT_ADMIN
• GH_USER_ADMIN
• GH_ROLE_ADMIN
• GH_SITE_ADMIN
• GH_SERIES_ADMIN
• GH_SERIES_CONTRIB
• GH_WC_ADMIN
• GH_WC_OPER
• GH_WC_USER
• GH_SUBSCRIBE_USER
• GH_SUBSCRIBE_ADMIN
• GH_IMG_ADMIN
• GH_IMG_USER
• GH_IMG_TESTABLE
• GH_IMG_RESTRICT
• GH_IMG_PUBLISH
• GH_IMG_VISIBILITY
• GH_IMGTYPE_ADMIN
• GH_IMGTYPE_ALLOW
• GH_IMGTYPE_OPER
• GH_SA
• GH_CA
• GH_OPER

Specify the name of the role that you want to grant clients or users.

Specify the name of a user. The user name that you specify must be in the form of user@rhpclient, where rhpclient is the name of the Fleet Patching and Provisioning Client.

Optionally, you can specify the name of the client cluster to which the user belongs.

Use this parameter to specify a role to which you want to grant another role.

You can map either built-in roles or roles that you have defined to either users on a specific client cluster or to specific users.

When you use the -maproles parameter, use a plus sign (+) to map more than one user to a specific role. Separate additional role/user pairs with commas.

Specify the name of the role from which you want to revoke clients or users.

Specify the name of a user and, optionally, a client cluster from which you want to revoke a role. The user name that you specify must be in the form of user@rhpclient, where rhpclient is the name of the Fleet Patching and Provisioning Client.

Specify the grantee role name.

You can map either built-in roles or roles that you have defined to specific users. Use a plus sign (+) to map more than one user to a specific role. Separate additional role/user pairs with commas. Optionally, you can also specify a client cluster.

Specify a name for the series that you want to add.

Optionally, you can specify the name of a configured image. This image becomes the first in the series.

Specify the name of the series from which you want to delete an image.

Specify the name of the image that you want to delete from a series.

-series series_name

Specify the name of the series into which you want to insert an image.

-image image_name

Specify the name of the image that you want to insert into a series.

-before image_name

Optionally, you can specify the name of an image before which you want to insert the new image.

Specify the name of the series for which you want to display the configuration.

Alternatively, you can specify the name of a configured image.

Specify the image series to which you want to subscribe a user.

Specify an operating system user to whom you are subscribing the image series.

Optionally, you can specify the name of the client cluster to which the operating system user belongs.

Specify the image series from which you want to unsubscribe a user.

Specify an operating system user from whom you are unsubscribing the image series.

Optionally, you can specify the name of the client cluster to which the operating system user belongs.

Specify the name of the Fleet Patching and Provisioning Server cluster that you want to register.

Specify the path to the file containing the Fleet Patching and Provisioning Server data.

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.

Specify the name of the user you want to delete from a Fleet Patching and Provisioning Client.

Optionally, you can specify the name of the client cluster from which you want to delete from a specific user.

Specify an operating system user whose email address you want to modify.

Specify the email address of the operating system user in the RFC 822 format.

Optionally, you can specify the name of the client cluster to which the operating system user belongs.

Specify an operating system user whose email address you want to register.

Specify the email address of the operating system user in the RFC 822 format.

Optionally, if you run the command on the Fleet Patching and Provisioning Server, then you can specify the name of the client cluster to which the operating system user belongs. Otherwise, the command applies to a user on the cluster (either the Fleet Patching and Provisioning Server or Client) where the command is run.

Specify an operating system user whose email address you want to unregister.

Optionally, you can specify the name of the client cluster to which the operating system user belongs.

Specify the name of the user action you want to add.

Associate a specific action script to run with the user action.

Optionally, you can specify an action file that is required by the user action.

Use the -pre parameter to run the user action before the add operation or the -post parameter to run the user action after.

Optionally, you can specify the operation for which the user action is configured. Options include:

• IMPORT_IMAGE
• ADD_WORKINGCOPY
• DELETE_WORKINGCOPY
• ADD_DATABASE
• DELETE_DATABASE
• MOVE_DATABASE
• MOVE_GIHOME
• UPGRADE_DATABASE
• UPGRADE_GIHOME
• ADDNODE_GIHOME
• DELETENODE_GIHOME
• ADDNODE_DATABASE
• DELETENODE_DATABASE
• ADDNODE_WORKINGCOPY
• ZDTUPGRADE_DATABASE
• ZDTUPGRADE_DATABASE_SNAPDB
• ZDTUPGRADE_DATABASE_DBUA
• ZDTUPGRADE_DATABASE_SWITCHBACK

Optionally, you can choose whether to abort or continue the operation if the user action encounters an error while it is running.

Optionally, you can specify the nodes where the user action is run. Choose ONENODE to run the user action for each database on the node on which a patch was applied to the database. Choose ALLNODES to run the user action for each database on every cluster node. Choose AUTO for a run scope based on the other command options.

Specify the name of the user action you want to modify.

Optionally, you can specify an action script to run.

Use the -pre parameter to run the user action before the modify operation or the -post parameter to run the user action after.

Optionally, you can specify the operation for which the user action is configured. Options include:

• IMPORT_IMAGE
• ADD_WORKINGCOPY
• DELETE_WORKINGCOPY
• ADD_DATABASE
• DELETE_DATABASE
• MOVE_DATABASE
• MOVE_GIHOME
• UPGRADE_DATABASE
• UPGRADE_GIHOME
• ADDNODE_GIHOME
• DELETENODE_GIHOME
• ADDNODE_DATABASE
• DELETENODE_DATABASE
• ADDNODE_WORKINGCOPY
• ZDTUPGRADE_DATABASE
• ZDTUPGRADE_DATABASE_SNAPDB
• ZDTUPGRADE_DATABASE_DBUA
• ZDTUPGRADE_DATABASE_SWITCHBACK

Optionally, you can choose whether to abort or continue the operation if the user action encounters an error while it is running.

Optionally, you can specify the nodes where the user action is run. Optionally, you can specify the nodes where the user action is run. Choose ONENODE to run the user action for each database on the node on which a patch was applied to the database. Choose ALLNODES to run the user action for each database on every cluster node. Choose AUTO for a run scope based on the other command options.

Specify the name of the user action you want to query.

Alternatively, you can specify the software type. Use ORACLEDBSOFTWARE (default) for Oracle database software, ORACLEGISOFTWARE for Oracle Grid Infrastructure software, and SOFTWARE for all other software. For a custom image type, use the image type name.

Optionally, you can specify the operation for which to run the query. Options include:

• IMPORT_IMAGE
• ADD_WORKINGCOPY
• DELETE_WORKINGCOPY
• ADD_DATABASE
• DELETE_DATABASE
• MOVE_DATABASE
• MOVE_GIHOME
• UPGRADE_DATABASE
• UPGRADE_GIHOME
• ADDNODE_GIHOME
• DELETENODE_GIHOME
• ADDNODE_DATABASE
• DELETENODE_DATABASE
• ADDNODE_WORKINGCOPY

Specify a name for the working copy that you want to create.

Specify the name of a configured image from which to create a working copy or the name of an image series from which RHPCTL takes the latest image when adding a working copy.

Specify an ORACLE_BASE path for provisioning an Oracle Database or Oracle Grid Infrastructure home. You can specify either an existing directory or a new directory.

Note: This parameter is required only for the ORACLEDBSOFTWARE and ORACLEGISOFTWARE image types.

Specify the location of the Oracle Inventory directory.

Specify the absolute path for provisioning the software home on the client side (this location must be empty). For Oracle Database images, this becomes the ORACLE_HOME.

Note: This parameter is required for LOCAL storage types, and is invalid for RHP_MANAGED.

Specify the type of storage for the software home.

Specify the name of the user that will own the working copy being provisioned.

If you do not specify this parameter, then the working copy is owned by the user running the command. If you are provisioning to a remote cluster, then the user name must be a valid user on the remote cluster. The user ID need not be the same between the two clusters, but the user name must exist on both.

Note: You cannot use -user simultaneously with the -softwareonly parameter.

Specify the name of the client cluster.

You can choose to ignore the Clusterware Verification Utility (CVU) checks or you can choose to run the recommended fixup script.

Note: These parameters are valid only when you are provisioning Oracle Grid Infrastructure.

Specify a response file to use when you provision Oracle Grid Infrastructure.

Specify a comma-delimited list of cluster node information on which to provision Oracle Clusterware.

Specify a comma-delimited list of Oracle groups, enclosed in double quotation marks (""), that you want to configure in the working copy.

For example:

-groups "OSDBA=dba,OSOPER=oper"

When you create a gold image from a source home or working copy, the gold image inherits the groups configured in the source. When you create a working copy from that gold image using rhpctl add workingcopy, by default, the new working copy inherits the same groups as the gold image.

If you use the -groups parameter on the command line, then:

• Groups configured in the gold image that you do not specify on the command line are inherited by the working copy.

• Groups configured in the gold image that you also specify on the command line are set to the value that you specify on the command line (command line parameters override the gold image).

• Groups that you specify on the command line that are not in the gold image are added to the configured groups in the gold image (the command line adds new groups).

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.

Specify this parameter to have email notifications sent to the owner of the working copy. Optionally, you can include a list of additional users who will receive notifications.

Specify the path to a file that contains Oracle ASM client data.

Specify the path to a file that contains the Grid Naming Service (GNS) data.

Optionally, you can specify the location of cluster manifest file. You can use this parameter when the Fleet Patching and Provisioning Server is on a domain services cluster and you are creating a member cluster.

Use this parameter to provision only Oracle Grid Infrastructure software on the local node.

Note: You can only use this parameter in conjunction with the -softwareonly parameter, and only when running the rhpctl add workingcopy command on a Fleet Patching and Provisioning Server.

Use this parameter to provision only Oracle Grid Infrastructure software.

Specify the name of a node in a remote cluster with no Fleet Patching and Provisioning Client on which you want to provision a working copy.

Use –agpath to specify the path to the read-write, site-specific configuration changes to set the persistent home path, and use –aupath to specify the path for the read-only gold image to set the persistent home path.

Use this parameter to set up passwordless SSH user equivalence on the remote nodes for the provisioning user.

Optionally, you can pass a value to the useractiondata parameter of the user action script.

Optionally, you can use this parameter to evaluate the impact of this command on the system without actually running the command.

Optionally, you can use the -checkwcpatches and -sourcehome parameters to compare patches in a specific source home path with the patches in the working copy you want to add.

Optionally, you can use this parameter to specify a SCAN name.

Optionally, you can use this parameter to specify a disk discovery string.

Optionally, you can use this parameter to specify a file containing the list of database servers that you want to patch, one node name in each line.

Optionally, you can use this parameter to specify a file containing a list of storage servers that you want to patch, one node name in each line.

Optionally, you can use this parameter to specify a file containing a list of InfiniBand switches that you want to patch, one node name in each line.

Optionally, you can specify a database server node name from where the patch manager is to be run.

Optionally, you can use this parameter to remove passwordless SSH access to the Oracle Exadata patch nodes from the database server node from where the patch manager is run before exit.

Optionally, you can specify an email address enclosed in double quotation marks ("") from which Fleet Patching and Provisioning sends patch manager notifications.

Optionally, you can specify several email address enclosed in double quotation marks ("") to which Fleet Patching and Provisioning sends patch manager notifications.

Optionally, you can use this parameter to run only the patching precheck operations.

Optionally, you can use this parameter to run the patchmgr -precheck command with the -modify_at_prereq option for database nodes.

Optionally, you can use this parameter to run the patchmgr -reset_force command before cell patching.

Optionally, you can use this parameter to run the patchmgr upgrade command with the -force option for ibswitches.

Specify the name of a working copy that contains the Oracle database you want to extend.

Specify a node or a comma-delimited list of nodes to which you want to extend the database.

Optionally, you can specify a node on which to run this command.

If you choose to use the -targetnode parameter, then you must choose either sudo or root to access the remote nodes.

If you choose sudo, then you must specify a user name to run super-user operations, and a path to the location of the sudo binary.

Optionally, you can choose to specify a credential name to associate the user and password credentials to access a remote node.

Alternative to –sudouser, –root, or –cred, you can use –auth to specify an authentication plugin to access a remote node.

Use this parameter to ignore the CVU prerequisite checks.

Sets up passwordless SSH user equivalence on the remote nodes for the provisioning user.

Optionally, you can pass a value to the useractiondata parameter of the user action script.

Optionally, you can use this parameter to evaluate the impact of this command on the system without actually running the command.

Specify the name of a working copy that you want to delete.

Name of a node in a remote cluster with no Fleet Patching and Provisioning Client.

Optionally, you can specify a particular node from which you want to delete a working copy.

Use this parameter to forcibly delete the database working copy.

If you choose to use the -targetnode parameter, then you must choose either sudo or root to access the remote node.

If you choose sudo, then you must specify a user name to run super-user operations, and a path to the location of the sudo binary.

Optionally, you can choose to specify a credential name to associate the user and password credentials to access a remote node.

Alternative to –sudouser, –root, or –cred, you can use –auth to specify an authentication plugin to access a remote node.

Optionally, you can pass a value to the useractiondata parameter of the user action script.

-workingcopy
 workingcopy_name

Specify the name of a working copy for which you want to display the configuration information.

-metadataonly

Use this paramter only when you use the -workingcopyy parameter to query only the metadata of the working copy, which is located in the repository and not run OPatch or connect to the target to query for extra information.

-image image_name

Alternatively, you can specify the name of a configured image you want to query.

Note: If you specify an image name, then RHPCTL lists all the working copies based on that image.

Optionally, you can specify a client cluster on which to query working copies.

Specify the name of a configured image from which to update a working copy

You can use this parameter to specify a file containing the list of database servers that you want to patch, one node name in each line.

Optionally, you can use this parameter to specify a file containing a list of storage cells that you want to patch, one cell name in each line.

Optionally, you can use this parameter to specify a file containing a list of InfiniBand switches that you want to patch, one switch name in each line.

Optionally, you can specify a database server node name from where the patch manager is to be run.

Optionally, you can use this parameter to remove passwordless SSH access to the Oracle Exadata patch nodes from the database server node from where the patch manager is run before exit.

Optionally, you can specify an email address enclosed in double quotation marks ("") from which Fleet Patching and Provisioning sends patch manager notifications.

Optionally, you can specify several email address enclosed in double quotation marks ("") to which Fleet Patching and Provisioning sends patch manager notifications.

Optionally, you can use this parameter to run only the patching precheck operations.

Optionally, you can use this parameter to run the patchmgr -precheck command with the -modify_at_prereq option for database nodes.

Optionally, you can use this parameter to run the patchmgr -reset_force command before cell patching.

Optionally, you can use this parameter to run the patchmgr upgrade command with the -force option for ibswitches.