oci-cli 3.68.1__py3-none-any.whl → 3.70.0__py3-none-any.whl

oci_cli/help_text_producer/data_files/text/cmdref/disaster-recovery/automatic-dr-configuration/update.txt

@@ -0,0 +1,224 @@
+"update"
+********
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Update the Automatic DR configuration identified by
+*automaticDrConfigurationId*.
+
+
+Usage
+=====
+
+   oci disaster-recovery automatic-dr-configuration update [OPTIONS]
+
+
+Required Parameters
+===================
+
+--automatic-dr-configuration-id [text]
+
+The OCID of the Automatic DR configuration.
+
+Example:
+
+   ocid1.automaticDrConfiguration.oc1..uniqueID
+
+
+Optional Parameters
+===================
+
+--default-failover-dr-plan-id [text]
+
+The unique id of a Failover DR Plan.
+
+Example:
+
+   ocid1.drplan.oc1..uniqueID
+
+--default-switchover-dr-plan-id [text]
+
+The unique id of a Switchover DR Plan.
+
+Example:
+
+   ocid1.drplan.oc1..uniqueID
+
+--defined-tags [complex type]
+
+Defined tags for this resource. Each key is predefined and scoped to a
+namespace.
+
+Example:
+
+   {"Operations": {"CostCenter": "42"}}
+
+This is a complex type whose value must be valid JSON. The value can
+be provided as a string on the command line or passed in as a file
+using the file://path/to/file syntax.
+
+The "--generate-param-json-input" option can be used to generate an
+example of the JSON which must be provided. We recommend storing this
+example in a file, modifying it as needed and then passing it back in
+via the file:// syntax.
+
+--display-name [text]
+
+The display name of the Automatic DR configuration being updated.
+
+Example:
+
+   Automatic DR Configuration
+
+--force
+
+Perform update without prompting for confirmation.
+
+--freeform-tags [complex type]
+
+Simple key-value pair that is applied without any predefined name,
+type or scope. Exists for cross-compatibility only.
+
+Example:
+
+   {"Department": "Finance"}
+
+This is a complex type whose value must be valid JSON. The value can
+be provided as a string on the command line or passed in as a file
+using the file://path/to/file syntax.
+
+The "--generate-param-json-input" option can be used to generate an
+example of the JSON which must be provided. We recommend storing this
+example in a file, modifying it as needed and then passing it back in
+via the file:// syntax.
+
+--from-json [text]
+
+Provide input to this command as a JSON document from a file using the
+file://path-to/file syntax.
+
+The "--generate-full-command-json-input" option can be used to
+generate a sample json file to be used with this command option. The
+key names are pre-populated and match the command option names
+(converted to camelCase format, e.g. compartment-id –> compartmentId),
+while the values of the keys need to be populated by the user before
+using the sample file as an input to this command. For any command
+option that accepts multiple values, the value of the key can be a
+JSON array.
+
+Options can still be provided on the command line. If an option exists
+in both the JSON document and the command line then the command line
+specified value will be used.
+
+For examples on usage of this option, please see our “using CLI with
+advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
+nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
+
+--if-match [text]
+
+For optimistic concurrency control. In the PUT or DELETE call for a
+resource, set the *if-match* parameter to the value of the etag from a
+previous GET or POST response for that resource. The resource will be
+updated or deleted only if the etag you provide matches the resource’s
+current etag value.
+
+--max-wait-seconds [integer]
+
+The maximum time to wait for the work request to reach the state
+defined by "--wait-for-state". Defaults to 1200 seconds.
+
+--members [complex type]
+
+A list of members for Automatic DR configuration.
+
+This option is a JSON list with items of type
+UpdateAutomaticDrConfigurationMemberDetails.  For documentation on
+UpdateAutomaticDrConfigurationMemberDetails please see our API
+reference: https://docs.cloud.oracle.com/api/#/en/disasterrecovery/20
+220125/datatypes/UpdateAutomaticDrConfigurationMemberDetails. This is
+a complex type whose value must be valid JSON. The value can be
+provided as a string on the command line or passed in as a file using
+the file://path/to/file syntax.
+
+The "--generate-param-json-input" option can be used to generate an
+example of the JSON which must be provided. We recommend storing this
+example in a file, modifying it as needed and then passing it back in
+via the file:// syntax.
+
+--wait-for-state [text]
+
+This operation asynchronously creates, modifies or deletes a resource
+and uses a work request to track the progress of the operation.
+Specify this option to perform the action and then wait until the work
+request reaches a certain state. Multiple states can be specified,
+returning on the first state. For example, "--wait-for-state"
+SUCCEEDED "--wait-for-state" FAILED would return on whichever
+lifecycle state is reached first. If timeout is reached, a return code
+of 2 is returned. For any other error, a return code of 1 is returned.
+
+Accepted values are:
+
+   ACCEPTED, CANCELED, CANCELING, FAILED, IN_PROGRESS, NEEDS_ATTENTION, SUCCEEDED, WAITING
+
+--wait-interval-seconds [integer]
+
+Check every "--wait-interval-seconds" to see whether the work request
+has reached the state defined by "--wait-for-state". Defaults to 30
+seconds.
+
+
+Global Parameters
+=================
+
+Use "oci --help" for help on global parameters.
+
+"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
+cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
+defaults-file", "--endpoint", "--generate-full-command-json-input", "
+--generate-param-json-input", "--help", "--latest-version", "--max-
+retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
+"--output", "--profile", "--proxy", "--query", "--raw-output", "--
+read-timeout", "--realm-specific-endpoint", "--region", "--release-
+info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"
+
+
+Example using required parameter
+================================
+
+Copy and paste the following example into a JSON file, replacing the
+example parameters with your own.
+
+       oci disaster-recovery dr-protection-group create --generate-param-json-input log-location > log-location.json
+
+       oci disaster-recovery automatic-dr-configuration create --generate-param-json-input members > members.json
+
+Copy the following CLI commands into a file named example.sh. Run the
+command by typing “bash example.sh” and replacing the example
+parameters with your own.
+
+Please note this sample will only work in the POSIX-compliant bash-
+like shell. You need to set up the OCI configuration and appropriate
+security policies before trying the examples.
+
+       export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/disaster-recovery/dr-protection-group/create.html#cmdoption-compartment-id
+       export display_name=<substitute-value-of-display_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/disaster-recovery/dr-protection-group/create.html#cmdoption-display-name
+
+       dr_protection_group_id=$(oci disaster-recovery dr-protection-group create --compartment-id $compartment_id --display-name $display_name --log-location file://log-location.json --query data.id --raw-output)
+
+       automatic_dr_configuration_id=$(oci disaster-recovery automatic-dr-configuration create --display-name $display_name --dr-protection-group-id $dr_protection_group_id --members file://members.json --query data.id --raw-output)
+
+       oci disaster-recovery automatic-dr-configuration update --automatic-dr-configuration-id $automatic_dr_configuration_id

oci_cli/help_text_producer/data_files/text/cmdref/disaster-recovery/automatic-dr-configuration.txt

@@ -0,0 +1,22 @@
+automatic-dr-configuration
+**************************
+
+
+Description
+===========
+
+The details of Automatic DR configuration.
+
+
+Available Commands
+==================
+
+* create
+
+* delete
+
+* get
+
+* list
+
+* update

oci_cli/help_text_producer/data_files/text/cmdref/disaster-recovery/dr-plan-execution/update.txt

@@ -61,7 +61,7 @@ via the file:// syntax.
 
 --display-name [text]
 
-The display name of the DR protection group to update.
+The display name of the DR plan execution to update.
 
 Example:
 

oci_cli/help_text_producer/data_files/text/cmdref/disaster-recovery/dr-protection-group/list.txt

@@ -100,7 +100,7 @@ lifecycle sub-state.
 
 Accepted values are:
 
-   DR_DRILL_IN_PROGRESS
+   AUTOMATIC_DR_PLAN_EXECUTION_IN_PROGRESS, DR_DRILL_IN_PROGRESS, DR_PLAN_EXECUTION_IN_PROGRESS
 
 --limit [integer]
 

oci_cli/help_text_producer/data_files/text/cmdref/disaster-recovery.txt

@@ -16,6 +16,18 @@ application.
 Available Commands
 ==================
 
+* automatic-dr-configuration
+
+  * create
+
+  * delete
+
+  * get
+
+  * list
+
+  * update
+
 * dr-plan
 
   * create

oci_cli/help_text_producer/data_files/text/cmdref/distributed-database/distributed-autonomous-db-service/distributed-autonomous-database/change-distributed-autonomous-db-backup-config.txt

@@ -0,0 +1,159 @@
+"change-distributed-autonomous-db-backup-config"
+************************************************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Change the DbBackupConfig for the Globally distributed autonomous
+database.
+
+
+Usage
+=====
+
+   oci distributed-database distributed-autonomous-db-service distributed-autonomous-database change-distributed-autonomous-db-backup-config [OPTIONS]
+
+
+Required Parameters
+===================
+
+--db-backup-config [complex type]
+
+This is a complex type whose value must be valid JSON. The value can
+be provided as a string on the command line or passed in as a file
+using the file://path/to/file syntax.
+
+The "--generate-param-json-input" option can be used to generate an
+example of the JSON which must be provided. We recommend storing this
+example in a file, modifying it as needed and then passing it back in
+via the file:// syntax.
+
+--distributed-autonomous-database-id [text]
+
+Globally distributed autonomous database identifier
+
+
+Optional Parameters
+===================
+
+--from-json [text]
+
+Provide input to this command as a JSON document from a file using the
+file://path-to/file syntax.
+
+The "--generate-full-command-json-input" option can be used to
+generate a sample json file to be used with this command option. The
+key names are pre-populated and match the command option names
+(converted to camelCase format, e.g. compartment-id –> compartmentId),
+while the values of the keys need to be populated by the user before
+using the sample file as an input to this command. For any command
+option that accepts multiple values, the value of the key can be a
+JSON array.
+
+Options can still be provided on the command line. If an option exists
+in both the JSON document and the command line then the command line
+specified value will be used.
+
+For examples on usage of this option, please see our “using CLI with
+advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
+nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
+
+--if-match [text]
+
+For optimistic concurrency control. In the PUT or DELETE call for a
+resource, set the *if-match* parameter to the value of the etag from a
+previous GET or POST response for that resource. The resource will be
+updated or deleted only if the etag you provide matches the resource’s
+current etag value.
+
+--max-wait-seconds [integer]
+
+The maximum time to wait for the work request to reach the state
+defined by "--wait-for-state". Defaults to 1200 seconds.
+
+--wait-for-state [text]
+
+This operation asynchronously creates, modifies or deletes a resource
+and uses a work request to track the progress of the operation.
+Specify this option to perform the action and then wait until the work
+request reaches a certain state. Multiple states can be specified,
+returning on the first state. For example, "--wait-for-state"
+SUCCEEDED "--wait-for-state" FAILED would return on whichever
+lifecycle state is reached first. If timeout is reached, a return code
+of 2 is returned. For any other error, a return code of 1 is returned.
+
+Accepted values are:
+
+   ACCEPTED, CANCELED, CANCELING, FAILED, IN_PROGRESS, NEEDS_ATTENTION, SUCCEEDED, WAITING
+
+--wait-interval-seconds [integer]
+
+Check every "--wait-interval-seconds" to see whether the work request
+has reached the state defined by "--wait-for-state". Defaults to 30
+seconds.
+
+
+Global Parameters
+=================
+
+Use "oci --help" for help on global parameters.
+
+"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
+cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
+defaults-file", "--endpoint", "--generate-full-command-json-input", "
+--generate-param-json-input", "--help", "--latest-version", "--max-
+retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
+"--output", "--profile", "--proxy", "--query", "--raw-output", "--
+read-timeout", "--realm-specific-endpoint", "--region", "--release-
+info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"
+
+
+Example using required parameter
+================================
+
+Copy and paste the following example into a JSON file, replacing the
+example parameters with your own.
+
+       oci distributed-database distributed-autonomous-db-service distributed-autonomous-database create --generate-param-json-input catalog-details > catalog-details.json
+       oci distributed-database distributed-autonomous-db-service distributed-autonomous-database create --generate-param-json-input private-endpoint-ids > private-endpoint-ids.json
+       oci distributed-database distributed-autonomous-db-service distributed-autonomous-database create --generate-param-json-input shard-details > shard-details.json
+
+       oci distributed-database distributed-autonomous-db-service distributed-autonomous-database change-distributed-autonomous-db-backup-config --generate-param-json-input db-backup-config > db-backup-config.json
+
+Copy the following CLI commands into a file named example.sh. Run the
+command by typing “bash example.sh” and replacing the example
+parameters with your own.
+
+Please note this sample will only work in the POSIX-compliant bash-
+like shell. You need to set up the OCI configuration and appropriate
+security policies before trying the examples.
+
+       export character_set=<substitute-value-of-character_set> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/distributed-database/distributed-autonomous-db-service/distributed-autonomous-database/create.html#cmdoption-character-set
+       export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/distributed-database/distributed-autonomous-db-service/distributed-autonomous-database/create.html#cmdoption-compartment-id
+       export database_version=<substitute-value-of-database_version> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/distributed-database/distributed-autonomous-db-service/distributed-autonomous-database/create.html#cmdoption-database-version
+       export db_deployment_type=<substitute-value-of-db_deployment_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/distributed-database/distributed-autonomous-db-service/distributed-autonomous-database/create.html#cmdoption-db-deployment-type
+       export db_workload=<substitute-value-of-db_workload> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/distributed-database/distributed-autonomous-db-service/distributed-autonomous-database/create.html#cmdoption-db-workload
+       export display_name=<substitute-value-of-display_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/distributed-database/distributed-autonomous-db-service/distributed-autonomous-database/create.html#cmdoption-display-name
+       export listener_port=<substitute-value-of-listener_port> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/distributed-database/distributed-autonomous-db-service/distributed-autonomous-database/create.html#cmdoption-listener-port
+       export ncharacter_set=<substitute-value-of-ncharacter_set> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/distributed-database/distributed-autonomous-db-service/distributed-autonomous-database/create.html#cmdoption-ncharacter-set
+       export ons_port_local=<substitute-value-of-ons_port_local> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/distributed-database/distributed-autonomous-db-service/distributed-autonomous-database/create.html#cmdoption-ons-port-local
+       export ons_port_remote=<substitute-value-of-ons_port_remote> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/distributed-database/distributed-autonomous-db-service/distributed-autonomous-database/create.html#cmdoption-ons-port-remote
+       export prefix=<substitute-value-of-prefix> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/distributed-database/distributed-autonomous-db-service/distributed-autonomous-database/create.html#cmdoption-prefix
+       export sharding_method=<substitute-value-of-sharding_method> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/distributed-database/distributed-autonomous-db-service/distributed-autonomous-database/create.html#cmdoption-sharding-method
+
+       distributed_autonomous_database_id=$(oci distributed-database distributed-autonomous-db-service distributed-autonomous-database create --catalog-details file://catalog-details.json --character-set $character_set --compartment-id $compartment_id --database-version $database_version --db-deployment-type $db_deployment_type --db-workload $db_workload --display-name $display_name --listener-port $listener_port --ncharacter-set $ncharacter_set --ons-port-local $ons_port_local --ons-port-remote $ons_port_remote --prefix $prefix --private-endpoint-ids file://private-endpoint-ids.json --shard-details file://shard-details.json --sharding-method $sharding_method --query data.id --raw-output)
+
+       oci distributed-database distributed-autonomous-db-service distributed-autonomous-database change-distributed-autonomous-db-backup-config --db-backup-config file://db-backup-config.json --distributed-autonomous-database-id $distributed_autonomous_database_id

oci_cli/help_text_producer/data_files/text/cmdref/distributed-database/distributed-autonomous-db-service/distributed-autonomous-database/create.txt

@@ -64,7 +64,8 @@ Accepted values are:
 
 --db-workload [text]
 
-Possible workload types.
+Possible workload types. Currently only OLTP workload type is
+supported.
 
 Accepted values are:
 
@@ -77,7 +78,9 @@ The display name of the Globally distributed autonomous database.
 --listener-port [integer]
 
 The listener port number for the Globally distributed autonomous
-database.
+database. The listener port number has to be unique for a customer
+tenancy across all distributed autonomous databases. Same port number
+should not be re-used for any other distributed autonomous database.
 
 --ncharacter-set [text]
 
@@ -85,11 +88,17 @@ The national character set for the database.
 
 --ons-port-local [integer]
 
-Ons local port number.
+Ons local port number for Globally distributed autonomous database.
+The onsPortLocal has to be unique for a customer tenancy across all
+distributed autonomous databases. Same port number should not be re-
+used for any other distributed autonomous database.
 
 --ons-port-remote [integer]
 
-Ons remote port number.
+Ons remote port number for Globally distributed autonomous database.
+The onsPortRemote has to be unique for a customer tenancy across all
+distributed autonomous databases. Same port number should not be re-
+used for any other distributed autonomous database.
 
 --prefix [text]
 
@@ -136,9 +145,22 @@ Optional Parameters
 
 --chunks [integer]
 
-The default number of unique chunks in a shardspace. The value of
-chunks must be greater than 2 times the size of the largest shardgroup
-in any shardspace.
+Number of chunks in a shardspace. The value of chunks must be greater
+than 2 times the size of the largest shardgroup in any shardspace.
+Chunks is required to be provided for distributed autonomous databases
+being created with SYSTEM shardingMethod. For USER shardingMethod,
+chunks should not be set in create payload.
+
+--db-backup-config [complex type]
+
+This is a complex type whose value must be valid JSON. The value can
+be provided as a string on the command line or passed in as a file
+using the file://path/to/file syntax.
+
+The "--generate-param-json-input" option can be used to generate an
+example of the JSON which must be provided. We recommend storing this
+example in a file, modifying it as needed and then passing it back in
+via the file:// syntax.
 
 --defined-tags [complex type]
 
@@ -191,7 +213,11 @@ nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
 --listener-port-tls [integer]
 
 The TLS listener port number for Globally distributed autonomous
-database.
+database. The TLS listener port number has to be unique for a customer
+tenancy across all distributed autonomous databases. Same port number
+should not be re-used for any other distributed autonomous database.
+The listenerPortTls is mandatory for dedicated infrastructure based
+distributed autonomous databases.
 
 --max-wait-seconds [integer]
 
@@ -206,8 +232,11 @@ autonomous database. Currently supported values are 3, 5 and 7.
 --replication-method [text]
 
 The Replication method for Globally distributed autonomous database.
-Use RAFT for Raft replication, and DG for DataGuard. If
-replicationMethod is not provided, it defaults to DG.
+Use RAFT for Raft based replication. With RAFT replication, shards
+cannot have peers details set on them. In case shards need to have
+peers, please do not set RAFT replicationMethod. For all non RAFT
+replication cases (with or without peers), please set
+replicationMethod as DG or do not set any value for replicationMethod.
 
 Accepted values are:
 
@@ -215,8 +244,9 @@ Accepted values are:
 
 --replication-unit [integer]
 
-For RAFT replication based Globally distributed autonomous database,
-the value should be atleast twice the number of shards.
+The replication unit count for RAFT based distributed autonomous
+database. For RAFT replication based Globally distributed autonomous
+database, the value should be at least twice the number of shards.
 
 --wait-for-state [text]
 

oci_cli/help_text_producer/data_files/text/cmdref/distributed-database/distributed-autonomous-db-service/distributed-autonomous-database/rotate-distributed-autonomous-database-passwords.txt

@@ -17,8 +17,9 @@
 Description
 ===========
 
-Rotate passwords for different components of the Globally distributed
-autonomous database.
+Rotate the gsmuser and gsmcatuser passwords for shards and catalog of
+the Globally distributed autonomous database. This operation will also
+remove GdsCtlNodes if present.
 
 
 Usage

oci_cli/help_text_producer/data_files/text/cmdref/distributed-database/distributed-autonomous-db-service/distributed-autonomous-database.txt

@@ -15,6 +15,8 @@ Available Commands
 
 * change-compartment
 
+* change-distributed-autonomous-db-backup-config
+
 * configure-distributed-autonomous-database-gsms
 
 * configure-distributed-autonomous-database-sharding

oci_cli/help_text_producer/data_files/text/cmdref/distributed-database/distributed-autonomous-db-service.txt

@@ -18,6 +18,8 @@ Available Commands
 
   * change-compartment
 
+  * change-distributed-autonomous-db-backup-config
+
   * configure-distributed-autonomous-database-gsms
 
   * configure-distributed-autonomous-database-sharding

oci_cli/help_text_producer/data_files/text/cmdref/distributed-database/distributed-db-service/distributed-database/create.txt

@@ -68,7 +68,10 @@ The display name of the Globally distributed database.
 
 --listener-port [integer]
 
-The listener port number for the Globally distributed database.
+The listener port number for the Globally distributed database. The
+listener port number has to be unique for a customer tenancy across
+all distributed databases. Same port number should not be re-used for
+any other distributed database.
 
 --ncharacter-set [text]
 
@@ -76,11 +79,17 @@ The national character set for the database.
 
 --ons-port-local [integer]
 
-Ons local port number.
+The ons local port number for the Globally distributed database. The
+onsPortLocal has to be unique for a customer tenancy across all
+distributed databases. Same port number should not be re-used for any
+other distributed database.
 
 --ons-port-remote [integer]
 
-Ons remote port number.
+The ons remote port number for the Globally distributed database. The
+onsPortRemote has to be unique for a customer tenancy across all
+distributed databases. Same port number should not be re-used for any
+other distributed database.
 
 --prefix [text]
 
@@ -127,9 +136,11 @@ Optional Parameters
 
 --chunks [integer]
 
-The default number of unique chunks in a shardspace. The value of
-chunks must be greater than 2 times the size of the largest shardgroup
-in any shardspace.
+Number of chunks in a shardspace. The value of chunks must be greater
+than 2 times the size of the largest shardgroup in any shardspace.
+Chunks is required to be provided for distributed databases being
+created with SYSTEM shardingMethod. For USER shardingMethod, chunks
+should not be set in create payload.
 
 --db-backup-config [complex type]
 
@@ -196,7 +207,12 @@ The SSH public key for Global service manager instances.
 
 --listener-port-tls [integer]
 
-The TLS listener port number for Globally distributed database.
+The TLS listener port number for the Globally distributed database.
+The TLS listener port number has to be unique for a customer tenancy
+across all distributed databases. Same port number should not be re-
+used for any other distributed database. For BASE_DB and EXADB_XS
+based distributed databases, tls is not supported hence the
+listenerPortTls is not needed to be provided in create payload.
 
 --max-wait-seconds [integer]
 
@@ -211,8 +227,11 @@ database. Currently supported values are 3, 5 and 7.
 --replication-method [text]
 
 The Replication method for Globally distributed database. Use RAFT for
-Raft replication, and DG for DataGuard. If replicationMethod is not
-provided, it defaults to DG.
+Raft based replication. With RAFT replication, shards cannot have
+peers details set on them. In case shards need to have peers, please
+do not set RAFT replicationMethod. For all non RAFT replication cases
+(with or without peers), please set replicationMethod as DG or do not
+set any value for replicationMethod.
 
 Accepted values are:
 
@@ -220,8 +239,9 @@ Accepted values are:
 
 --replication-unit [integer]
 
-For RAFT replication based Globally distributed database, the value
-should be atleast twice the number of shards.
+The replication unit count for RAFT based distributed database. For
+RAFT replication based Globally distributed database, the value should
+be at least twice the number of shards.
 
 --wait-for-state [text]