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

oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/create-autonomous-database-gcp-key-details.txt

@@ -17,7 +17,7 @@
 Description
 ===========
 
-Creates a new Autonomous Database.
+Creates a new Autonomous AI Database.
 
 
 Usage
@@ -31,7 +31,7 @@ Required Parameters
 
 --compartment-id, -c [text]
 
-The OCID of the compartment of the Autonomous Database.
+The OCID of the compartment of the Autonomous AI Database.
 
 --encryption-key-key-name [text]
 
@@ -56,36 +56,37 @@ Optional Parameters
 --admin-password [text]
 
 **Important** The *adminPassword* or *secretId* must be specified for
-all Autonomous Databases except for refreshable clones. The password
-must be between 12 and 30 characters long, and must contain at least 1
-uppercase, 1 lowercase, and 1 numeric character. It cannot contain the
-double quote symbol (“) or the username “admin”, regardless of casing.
+all Autonomous AI Databases except for refreshable clones. The
+password must be between 12 and 30 characters long, and must contain
+at least 1 uppercase, 1 lowercase, and 1 numeric character. It cannot
+contain the double quote symbol (“) or the username “admin”,
+regardless of casing.
 
 This cannot be used in conjunction with with OCI vault secrets
 (secretId).
 
 --are-primary-whitelisted-ips-used [boolean]
 
-This field will be null if the Autonomous Database is not Data Guard
-enabled or Access Control is disabled. It’s value would be *TRUE* if
-Autonomous Database is Data Guard enabled and Access Control is
-enabled and if the Autonomous Database uses primary IP access control
-list (ACL) for standby. It’s value would be *FALSE* if Autonomous
-Database is Data Guard enabled and Access Control is enabled and if
-the Autonomous Database uses different IP access control list (ACL)
-for standby compared to primary.
+This field will be null if the Autonomous AI Database is not Data
+Guard enabled or Access Control is disabled. It’s value would be
+*TRUE* if Autonomous AI Database is Data Guard enabled and Access
+Control is enabled and if the Autonomous AI Database uses primary IP
+access control list (ACL) for standby. It’s value would be *FALSE* if
+Autonomous AI Database is Data Guard enabled and Access Control is
+enabled and if the Autonomous AI Database uses different IP access
+control list (ACL) for standby compared to primary.
 
 --autonomous-container-database-id [text]
 
-The Autonomous Container Database OCID. Used only by Autonomous
+The Autonomous Container Database OCID. Used only by Autonomous AI
 Database on Dedicated Exadata Infrastructure.
 
 --autonomous-maintenance-schedule-type [text]
 
-The maintenance schedule type of the Autonomous Database Serverless.
-An EARLY maintenance schedule follows a schedule applying patches
-prior to the REGULAR schedule. A REGULAR maintenance schedule follows
-the normal cycle
+The maintenance schedule type of the Autonomous AI Database
+Serverless. An EARLY maintenance schedule follows a schedule applying
+patches prior to the REGULAR schedule. A REGULAR maintenance schedule
+follows the normal cycle
 
 Accepted values are:
 
@@ -104,11 +105,11 @@ Included and billed.
 
 --character-set [text]
 
-The character set for the autonomous database. The default is
-AL32UTF8. Allowed values for an Autonomous Database Serverless
-instance as as returned by List Autonomous Database Character Sets
+The character set for the Autonomous AI Database. The default is
+AL32UTF8. Allowed values for an Autonomous AI Database Serverless
+instance as as returned by List Autonomous AI Database Character Sets
 
-For an Autonomous Database on dedicated infrastructure, the allowed
+For an Autonomous AI Database on dedicated infrastructure, the allowed
 values are:
 
 AL32UTF8, AR8ADOS710, AR8ADOS720, AR8APTEC715, AR8ARABICMACS,
@@ -137,10 +138,10 @@ ZHT32TRIS
 
 The compute amount (CPUs) available to the database. Minimum and
 maximum values depend on the compute model and whether the database is
-an Autonomous Database Serverless instance or an Autonomous Database
-on Dedicated Exadata Infrastructure. The ‘ECPU’ compute model requires
-a minimum value of one, for databases in the elastic resource pool and
-minimum value of two, otherwise. Required when using the
+an Autonomous AI Database Serverless instance or an Autonomous AI
+Database on Dedicated Exadata Infrastructure. The ‘ECPU’ compute model
+requires a minimum value of one, for databases in the elastic resource
+pool and minimum value of two, otherwise. Required when using the
 *computeModel* parameter. When using *cpuCoreCount* parameter, it is
 an error to specify computeCount to a non-null value. Providing
 *computeModel* and *computeCount* is the preferred method for both
@@ -148,7 +149,7 @@ OCPU and ECPU.
 
 --compute-model [text]
 
-The compute model of the Autonomous Database. This is required if
+The compute model of the Autonomous AI Database. This is required if
 using the *computeCount* parameter. If using *cpuCoreCount* then it is
 an error to specify *computeModel* to a non-null value. ECPU compute
 model is the recommended model and OCPU compute model is legacy.
@@ -160,8 +161,8 @@ Accepted values are:
 --cpu-core-count [integer]
 
 The number of CPU cores to be made available to the database. For
-Autonomous Databases on dedicated Exadata infrastructure, the maximum
-number of cores is determined by the infrastructure shape. See
+Autonomous AI Databases on dedicated Exadata infrastructure, the
+maximum number of cores is determined by the infrastructure shape. See
 Characteristics of Infrastructure Shapes for shape details.
 
 **Note:** This parameter cannot be used with the *ocpuCount*
@@ -198,19 +199,19 @@ infrastructure. - This parameter cannot be used with the
 
 The size, in terabytes, of the data volume that will be created and
 attached to the database. This storage can later be scaled up if
-needed. For Autonomous Databases on dedicated Exadata infrastructure,
-the maximum storage value is determined by the infrastructure shape.
-See Characteristics of Infrastructure Shapes for shape details. A full
-Exadata service is allocated when the Autonomous Database size is set
-to the upper limit (384 TB).
+needed. For Autonomous AI Databases on dedicated Exadata
+infrastructure, the maximum storage value is determined by the
+infrastructure shape. See Characteristics of Infrastructure Shapes for
+shape details. A full Exadata service is allocated when the Autonomous
+AI Database size is set to the upper limit (384 TB).
 
 **Note:** This parameter cannot be used with the
 *dataStorageSizeInGBs* parameter.
 
 --database-edition [text]
 
-The Oracle Database Edition that applies to the Autonomous databases.
-This parameter accepts options *STANDARD_EDITION* and
+The Oracle AI Database Edition that applies to the Autonomous AI
+Databases. This parameter accepts options *STANDARD_EDITION* and
 *ENTERPRISE_EDITION*.
 
 --db-name [text]
@@ -246,16 +247,17 @@ via the file:// syntax.
 
 --db-version [text]
 
-A valid Oracle Database version for Autonomous Database.
+A valid Oracle AI Database version for Autonomous AI Database.
 
 --db-workload [text]
 
-The Autonomous Database workload type. The following values are valid:
-
-* OLTP - indicates an Autonomous Transaction Processing database - DW
-  - indicates an Autonomous Data Warehouse database - AJD - indicates
-  an Autonomous JSON Database - APEX - indicates an Autonomous
-  Database with the Oracle APEX Application Development workload type.
+The Autonomous AI Database workload type. The following values are
+valid: - OLTP - indicates an Autonomous AI Transaction Processing
+database - DW - indicates an Autonomous AI Lakehouse database - AJD -
+indicates an Autonomous AI JSON Database - APEX - indicates an
+Autonomous AI Database with the Oracle APEX AI Application Development
+workload type. - LH - indicates an Oracle Autonomous AI Lakehouse
+database
 
 This cannot be updated in parallel with any of the following:
 licenseModel, dbEdition, cpuCoreCount, computeCount, computeModel,
@@ -266,7 +268,7 @@ isFreeTier.
 
 Accepted values are:
 
-   AJD, APEX, DW, OLTP
+   AJD, APEX, DW, LH, OLTP
 
 --defined-tags [complex type]
 
@@ -283,8 +285,8 @@ via the file:// syntax.
 
 --display-name [text]
 
-The user-friendly name for the Autonomous Database. The name does not
-have to be unique.
+The user-friendly name for the Autonomous AI Database. The name does
+not have to be unique.
 
 --encryption-key-kms-rest-endpoint [text]
 
@@ -334,8 +336,8 @@ nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
 --in-memory-percentage [integer]
 
 The percentage of the System Global Area(SGA) assigned to In-Memory
-tables in Autonomous Database. This property is applicable only to
-Autonomous Databases on the Exadata Cloud@Customer platform.
+tables in Autonomous AI Database. This property is applicable only to
+Autonomous AI Databases on the Exadata Cloud@Customer platform.
 
 --is-access-control-enabled [boolean]
 
@@ -351,30 +353,30 @@ When creating a database clone, the desired access control setting
 should be specified. By default, database-level access control will be
 disabled for the clone.
 
-This property is applicable only to Autonomous Databases on the
-Exadata Cloud@Customer platform. For Autonomous Database Serverless
+This property is applicable only to Autonomous AI Databases on the
+Exadata Cloud@Customer platform. For Autonomous AI Database Serverless
 instances, *whitelistedIps* is used.
 
 --is-auto-scaling-enabled [boolean]
 
-Indicates if auto scaling is enabled for the Autonomous Database CPU
-core count. The default value is *TRUE*.
+Indicates if auto scaling is enabled for the Autonomous AI Database
+CPU core count. The default value is *TRUE*.
 
 --is-auto-scaling-for-storage-enabled [boolean]
 
-Indicates if auto scaling is enabled for the Autonomous Database
+Indicates if auto scaling is enabled for the Autonomous AI Database
 storage. The default value is *FALSE*.
 
 --is-backup-retention-locked [boolean]
 
-True if the Autonomous Database is backup retention locked.
+True if the Autonomous AI Database is backup retention locked.
 
 --is-data-guard-enabled [boolean]
 
-**Deprecated.** Indicates whether the Autonomous Database has local
+**Deprecated.** Indicates whether the Autonomous AI Database has local
 (in-region) Data Guard enabled. Not applicable to cross-region
-Autonomous Data Guard associations, or to Autonomous Databases using
-dedicated Exadata infrastructure or Exadata Cloud@Customer
+Autonomous Data Guard associations, or to Autonomous AI Databases
+using dedicated Exadata infrastructure or Exadata Cloud@Customer
 infrastructure.
 
 --is-dedicated [boolean]
@@ -383,7 +385,7 @@ True if the database is on dedicated Exadata infrastructure.
 
 --is-dev-tier [boolean]
 
-Autonomous Database for Developers are fixed-shape Autonomous
+Autonomous AI Database for Developers are fixed-shape Autonomous AI
 Databases that developers can use to build and test new applications.
 On Serverless, these are low-cost and billed per instance, on
 Dedicated and Cloud@Customer there is no additional cost to create
@@ -395,8 +397,9 @@ upgrade to a full paid production database.
 --is-free-tier [boolean]
 
 Indicates if this is an Always Free resource. The default value is
-false. Note that Always Free Autonomous Databases have 1 CPU and 20GB
-of memory. For Always Free databases, memory and CPU cannot be scaled.
+false. Note that Always Free Autonomous AI Databases have 1 CPU and
+20GB of memory. For Always Free databases, memory and CPU cannot be
+scaled.
 
 This cannot be updated in parallel with any of the following:
 licenseModel, dbEdition, cpuCoreCount, computeCount, computeModel,
@@ -407,14 +410,14 @@ isLocalDataGuardEnabled
 
 --is-local-data-guard-enabled [boolean]
 
-Indicates whether the Autonomous Database has local (in-region) Data
-Guard enabled. Not applicable to cross-region Autonomous Data Guard
-associations, or to Autonomous Databases using dedicated Exadata
-infrastructure or Exadata Cloud@Customer infrastructure.
+Indicates whether the Autonomous AI Database has local (in-region)
+Data Guard enabled. Not applicable to cross-region Autonomous Data
+Guard associations, or to Autonomous AI Databases using dedicated
+Exadata infrastructure or Exadata Cloud@Customer infrastructure.
 
 --is-mtls-connection-required [boolean]
 
-Specifies if the Autonomous Database requires mTLS connections.
+Specifies if the Autonomous AI Database requires mTLS connections.
 
 This may not be updated in parallel with any of the following:
 licenseModel, databaseEdition, cpuCoreCount, computeCount,
@@ -428,9 +431,9 @@ attribute will change from true to false on July 1, 2023 in the
 following APIs: - CreateAutonomousDatabase - GetAutonomousDatabase -
 UpdateAutonomousDatabase Details: Prior to the July 1, 2023 change,
 the isMTLSConnectionRequired attribute default value was true. This
-applies to Autonomous Database Serverless. Does this impact me? If you
-use or maintain custom scripts or Terraform scripts referencing the
-CreateAutonomousDatabase, GetAutonomousDatabase, or
+applies to Autonomous AI Database Serverless. Does this impact me? If
+you use or maintain custom scripts or Terraform scripts referencing
+the CreateAutonomousDatabase, GetAutonomousDatabase, or
 UpdateAutonomousDatabase APIs, you want to check, and possibly modify,
 the scripts for the changed default value of the attribute. Should you
 choose not to leave your scripts unchanged, the API calls containing
@@ -441,10 +444,10 @@ set the isMTLSConnectionRequired attribute to true.
 
 --is-preview-version-with-service-terms-accepted [boolean]
 
-If set to *TRUE*, indicates that an Autonomous Database preview
+If set to *TRUE*, indicates that an Autonomous AI Database preview
 version is being provisioned, and that the preview version’s terms of
 service have been accepted. Note that preview version software is only
-available for Autonomous Database Serverless instances
+available for Autonomous AI Database Serverless instances
 (https://docs.oracle.com/en/cloud/paas/autonomous-
 database/serverless/).
 
@@ -455,17 +458,17 @@ key in database transparent data encryption (TDE) operations.
 
 --license-model [text]
 
-The Oracle license model that applies to the Oracle Autonomous
+The Oracle license model that applies to the Oracle Autonomous AI
 Database. Bring your own license (BYOL) allows you to apply your
 current on-premises Oracle software licenses to equivalent, highly
 automated Oracle services in the cloud. License Included allows you to
-subscribe to new Oracle Database software licenses and the Oracle
-Database service. Note that when provisioning an Autonomous Database
-on dedicated Exadata infrastructure, this attribute must be null. It
-is already set at the Autonomous Exadata Infrastructure level. When
-provisioning an Autonomous Database Serverless  database, if a value
-is not specified, the system defaults the value to
-*BRING_YOUR_OWN_LICENSE*. Bring your own license (BYOL) also allows
+subscribe to new Oracle AI Database software licenses and the Oracle
+AI Database service. Note that when provisioning an Autonomous AI
+Database on dedicated Exadata infrastructure, this attribute must be
+null. It is already set at the Autonomous Exadata Infrastructure
+level. When provisioning an Autonomous AI Database Serverless
+database, if a value is not specified, the system defaults the value
+to *BRING_YOUR_OWN_LICENSE*. Bring your own license (BYOL) also allows
 you to select the DB edition using the optional parameter.
 
 This cannot be updated in parallel with any of the following:
@@ -484,11 +487,11 @@ defined by "--wait-for-state". Defaults to 1200 seconds.
 
 --ncharacter-set [text]
 
-The character set for the Autonomous Database. The default is
-AL32UTF8. Use List Autonomous Database Character Sets to list the
-allowed values for an Autonomous Database Serverless instance. For an
-Autonomous Database on dedicated Exadata infrastructure, the allowed
-values are: AL16UTF16 or UTF8.
+The character set for the Autonomous AI Database. The default is
+AL32UTF8. Use List Autonomous AI Database Character Sets to list the
+allowed values for an Autonomous AI Database Serverless instance. For
+an Autonomous AI Database on dedicated Exadata infrastructure, the
+allowed values are: AL16UTF16 or UTF8.
 
 --nsg-ids [complex type]
 
@@ -496,8 +499,8 @@ The list of OCIDs for the network security groups (NSGs) to which this
 resource belongs. Setting this to an empty list removes all resources
 from all NSGs. For more information about NSGs, see Security Rules.
 **NsgIds restrictions:** - A network security group (NSG) is optional
-for Autonomous Databases with private access. The nsgIds list can be
-empty. This is a complex type whose value must be valid JSON. The
+for Autonomous AI Databases with private access. The nsgIds list can
+be empty. 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.
 
@@ -510,20 +513,20 @@ via the file:// syntax.
 
 The number of OCPU cores to be made available to the database.
 
-The following points apply: - For Autonomous Databases on Dedicated
+The following points apply: - For Autonomous AI Databases on Dedicated
 Exadata infrastructure, to provision less than 1 core, enter a
 fractional value in an increment of 0.1. For example, you can
 provision 0.3 or 0.4 cores, but not 0.35 cores. (Note that fractional
-OCPU values are not supported for Autonomous Database Serverless
+OCPU values are not supported for Autonomous AI Database Serverless
 instances.) - To provision 1 or more cores, you must enter an integer
 between 1 and the maximum number of cores available for the
 infrastructure shape. For example, you can provision 2 cores or 3
-cores, but not 2.5 cores. This applies to an Autonomous Database
-Serverless instance or an Autonomous Database on Dedicated Exadata
-Infrastructure. - For Autonomous Database Serverless instances, this
-parameter is not used.
+cores, but not 2.5 cores. This applies to an Autonomous AI Database
+Serverless instance or an Autonomous AI Database on Dedicated Exadata
+Infrastructure. - For Autonomous AI Database Serverless instances,
+this parameter is not used.
 
-For Autonomous Databases on Dedicated Exadata infrastructure, the
+For Autonomous AI Databases on Dedicated Exadata infrastructure, the
 maximum number of cores is determined by the infrastructure shape. See
 Characteristics of Infrastructure Shapes for shape details.
 
@@ -558,7 +561,7 @@ or isFreeTier.
 
 --resource-pool-leader-id [text]
 
-The unique identifier for leader autonomous database OCID OCID.
+The unique identifier for leader Autonomous AI Database OCID OCID.
 
 --resource-pool-summary [complex type]
 
@@ -623,14 +626,14 @@ via the file:// syntax.
 --standby-whitelisted-ips [complex type]
 
 The client IP access control list (ACL). This feature is available for
-Autonomous Database Serverless  and on Exadata Cloud@Customer. Only
+Autonomous AI Database Serverless  and on Exadata Cloud@Customer. Only
 clients connecting from an IP address included in the ACL may access
-the Autonomous Database instance. If *arePrimaryWhitelistedIpsUsed* is
-‘TRUE’ then Autonomous Database uses this primary’s IP access control
-list (ACL) for the disaster recovery peer called
+the Autonomous AI Database instance. If *arePrimaryWhitelistedIpsUsed*
+is ‘TRUE’ then Autonomous AI Database uses this primary’s IP access
+control list (ACL) for the disaster recovery peer called
 *standbywhitelistedips*.
 
-For Autonomous Database Serverless, this is an array of CIDR
+For Autonomous AI Database Serverless, this is an array of CIDR
 (classless inter-domain routing) notations for a subnet or VCN OCID
 (virtual cloud network Oracle Cloud ID). Multiple IPs and VCN OCIDs
 should be separate strings separated by commas, but if it’s other
@@ -666,7 +669,7 @@ The OCID of the subnet the resource is associated with.
 node virtual machine DB systems, do not use a subnet that overlaps
 with 192.168.16.16/28. - For Exadata and virtual machine 2-node RAC
 systems, do not use a subnet that overlaps with 192.168.128.0/20. -
-For Autonomous Database, setting this will disable public secure
+For Autonomous AI Database, setting this will disable public secure
 access to the database.
 
 These subnets are used by the Oracle Clusterware private interconnect
@@ -708,14 +711,14 @@ reached the lifecycle state defined by "--wait-for-state". Defaults to
 --whitelisted-ips [complex type]
 
 The client IP access control list (ACL). This feature is available for
-Autonomous Database Serverless  and on Exadata Cloud@Customer. Only
+Autonomous AI Database Serverless  and on Exadata Cloud@Customer. Only
 clients connecting from an IP address included in the ACL may access
-the Autonomous Database instance. If *arePrimaryWhitelistedIpsUsed* is
-‘TRUE’ then Autonomous Database uses this primary’s IP access control
-list (ACL) for the disaster recovery peer called
+the Autonomous AI Database instance. If *arePrimaryWhitelistedIpsUsed*
+is ‘TRUE’ then Autonomous AI Database uses this primary’s IP access
+control list (ACL) for the disaster recovery peer called
 *standbywhitelistedips*.
 
-For Autonomous Database Serverless, this is an array of CIDR
+For Autonomous AI Database Serverless, this is an array of CIDR
 (classless inter-domain routing) notations for a subnet or VCN OCID
 (virtual cloud network Oracle Cloud ID). Multiple IPs and VCN OCIDs
 should be separate strings separated by commas, but if it’s other