rhpctl add workingcopy -workingcopy workingcopy_name -image image_name [-oraclebase oraclebase_path] [-path absolute_path] [-storagetype {NFS | LOCAL} [-user user_name] [-dbname unique_db_name [-dbtype {RACONENODE | RAC | SINGLE}] [-datafileDestination datafileDestination_path] [-dbtemplate file_path | image_name:relative_file_path {-node node_list | -serverpool server_pool_name [-pqpool pool_name | -newpqpool pool_name -pqcardinality cardinality] | -newpool server_pool_name -cardinality cardinality [-pqpool pool_name | -newpqpool pool_name -pqcardinality cardinality]} [-cdb] [-pdbprefix pdb_prefix [-pdbcount pdb_count]]] [-client cluster_name] [-ignoreprereq]
Table F-6 rhpctl add workingcopy Parameters
Parameter | Description |
---|---|
-workingcopy
workingcopy_name |
Specify a name for the working copy that you want to create. |
-image image_name |
Specify the name of a configured image from which to create a working copy. |
-oraclebase
oraclebase_path |
Specify an Note: This parameter is required only for the |
-path absolute_path |
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 Note: You cannot use this parameter if you are provisioning a working copy to a Rapid Home Provisioning Server because, in that case, Oracle ACFS creates a snapshot path within the file system. |
-storagetype {NFS | LOCAL} |
Specify the type of storage for the software home. The default is |
-user user_name |
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. |
-dbname unique_db_name |
Specify the unique name of the database ( |
-dbtype {RACONENODE | RAC | SINGLE} |
Specify whether the database is Oracle RAC One Node, Oracle RAC, or single instance (non-Oracle RAC). |
-datafileDestination
datafileDestination_path |
Specify the data file destination ___location or the name of the Oracle Automatic Storage Management (Oracle ASM) disk group. Notes:
|
-dbtemplate file_path | image_name:relative_file_path |
Specify the absolute path to a database template or the relative path to the image home directory on the Rapid Home Provisioning Server. If you do not specify a database template, then RHPCTL uses the default template. |
-node node_list |
Specify a node or comma-delimited list of several nodes on which to create the database. Note: This parameter is required when the value of |
-serverpool
server_pool_name |
Specify the name of an existing server pool. Note: This defaults to the name of the working copy. |
-newpool
server_pool_name |
Optionally, you can create a new server pool. Specify a name for the new server pool. |
-cardinality cardinality |
If you create a new server pool, then you must specify a cardinality value for the server pool. |
-pqpool
server_pool_name |
Specify the name of an existing server pool. Note: This parameter is only applicable in an Oracle Flex Cluster environment and refers to server pools (either already defined as in this case, or to be created when you use the |
-newpqpool
server_pool_name |
Optionally, you can create a new server pool. Specify a name for the new server pool. Note: This parameter is only applicable in an Oracle Flex Cluster environment because it refers to server pools running on Leaf Nodes. |
-pqcardinality cardinality |
If you create a new server pool, then you must specify a cardinality value for the server pool. Note: This parameter is only applicable in an Oracle Flex Cluster environment. |
-cdb |
Use this parameter if you want to create the database as a container database (CDB). |
-pdbprefix pdb_prefix |
Specify the pluggable database (PDB) prefix if you are creating one or more PDBs. |
-pdbcount pdb_count |
Specify the number of PDBs you want to create. |
-client cluster_name |
Specify the name of the client cluster. |
You can obtain context sensitive help for specific use cases for the rhpctl add workingcopy
command, as follows:
$ rhpctl add workingcopy -help [REMOTEPROVISIONING | STORAGETYPE | ADMINDB | POLICYDB | DBWITHPQPOOLS | DBTEMPLATE | PDB]
The following example provisions an Oracle Database software home from a gold image:
$ rhpctl add workingcopy -workingcopy workingcopy_name -image image_name -oraclebase oraclebase_path
The following example provisions an Oracle Database software home and creates a policy-managed database from a gold image:
$ rhpctl add workingcopy -workingcopy workingcopy_name -image image_name -oraclebase oraclebase_path -dbname unique_db_name -datafileDestination datafileDestination_path -serverpool pool_name
The following example provisions an Oracle Database software home on a user-specified storage ___location and creates a policy-managed database:
$ rhpctl add workingcopy -workingcopy workingcopy_name -image image_name -oraclebase oraclebase_path -storagetype LOCAL –path storage_path -dbname unique_db_name -datafileDestination datafileDestination_path -newpool server_pool_name -cardinality cardinality
Note:
If you are provisioning Oracle database software to a Rapid Home Provisioning Client that has been configured with a disk group, then do not specify the -path
parameter, so as to enable the Rapid Home Provisioning Client to use storage provided by Rapid Home Provisioning.
If the Rapid Home Provisioning Client is not configured with a disk group, then specify the -storagetype
parameter with either NFS
or LOCAL
, in addition to specifying the -path
parameter.