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

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

@@ -17,9 +17,9 @@
 Description
 ===========
 
-Updates one or more attributes of the specified Autonomous Database.
-See the UpdateAutonomousDatabaseDetails resource for a full list of
-attributes that can be updated.
+Updates one or more attributes of the specified Autonomous AI
+Database. See the UpdateAutonomousDatabaseDetails resource for a full
+list of attributes that can be updated.
 
 
 Usage
@@ -57,13 +57,14 @@ dbName, or isFreeTier.
 
 --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. *TRUE* if the Autonomous
-Database has Data Guard and Access Control enabled, and the Autonomous
-Database uses the primary’s IP access control list (ACL) for standby.
-*FALSE* if the Autonomous Database has Data Guard and Access Control
-enabled, and the Autonomous Database uses a 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. *TRUE* if the Autonomous
+AI Database has Data Guard and Access Control enabled, and the
+Autonomous AI Database uses the primary’s IP access control list (ACL)
+for standby. *FALSE* if the Autonomous AI Database has Data Guard and
+Access Control enabled, and the Autonomous AI Database uses a
+different IP access control list (ACL) for standby compared to
+primary.
 
 --auto-refresh-frequency-in-seconds [integer]
 
@@ -82,10 +83,10 @@ refresh happens.
 
 --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:
 
@@ -106,10 +107,10 @@ Included and billed.
 
 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
@@ -123,7 +124,7 @@ scheduledOperations, dbToolsDetails, or isFreeTier.
 
 --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.
@@ -134,8 +135,8 @@ Accepted values are:
 
 --cpu-core-count [integer]
 
-The number of CPUs to be made available to the Autonomous
-Database.<br> For Autonomous Databases on Dedicated Exadata
+The number of CPUs to be made available to the Autonomous AI
+Database.<br> For Autonomous AI Databases on Dedicated Exadata
 Infrastructure: - The CPU type (OCPUs or ECPUs) is determined by the
 parent Autonomous Exadata VM Cluster’s compute model. - It is
 suggested to use ‘computeCount’ parameter if you want to use
@@ -185,11 +186,11 @@ details.
 --data-storage-size-in-tbs [integer]
 
 The size, in terabytes, of the data volume that will be created and
-attached to the database. For Autonomous Databases on dedicated
+attached to the database. 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
-Database size is set to the upper limit (384 TB).
+AI Database size is set to the upper limit (384 TB).
 
 **Note:** This parameter cannot be used with the
 *dataStorageSizeInGBs* parameter.
@@ -202,8 +203,8 @@ scheduledOperations, dbToolsDetails, or isFreeTier.
 
 --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*.
 
 This cannot be updated in parallel with any of the following:
@@ -214,10 +215,10 @@ dbToolsDetails, or isFreeTier.
 
 --db-name [text]
 
-New name for this Autonomous Database. For Autonomous Databases on
-Dedicated Exadata Infrastructure, the name must begin with an
+New name for this Autonomous AI Database. For Autonomous AI Databases
+on Dedicated Exadata Infrastructure, the name must begin with an
 alphabetic character, and can contain a maximum of eight alphanumeric
-characters. Special characters are not permitted. For Autonomous
+characters. Special characters are not permitted. For Autonomous AI
 Database Serverless instances, the name must begin with an alphabetic
 character, and can contain a maximum of 30 alphanumeric characters.
 Special characters are not permitted. The database name must be unique
@@ -253,16 +254,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,
@@ -273,7 +275,7 @@ isFreeTier.
 
 Accepted values are:
 
-   AJD, APEX, DW, OLTP
+   AJD, APEX, DW, LH, OLTP
 
 --defined-tags [complex type]
 
@@ -290,10 +292,10 @@ via the file:// syntax.
 
 --display-name [text]
 
-The user-friendly name for the Autonomous Database. The name does not
-have to be unique. The display name can only be updated for Autonomous
-Databases using dedicated Exadata Infrastructure. This parameter may
-not be updated in parallel with dbVersion.
+The user-friendly name for the Autonomous AI Database. The name does
+not have to be unique. The display name can only be updated for
+Autonomous AI Databases using dedicated Exadata Infrastructure. This
+parameter may not be updated in parallel with dbVersion.
 
 --encryption-key [complex type]
 
@@ -362,8 +364,8 @@ current etag value.
 --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-acl-enabled [boolean]
 
@@ -384,36 +386,36 @@ Exadata Cloud@Customer platform.
 
 --is-auto-scaling-enabled [boolean]
 
-Indicates whether auto scaling is enabled for the Autonomous Database
-CPU core count. Setting to *TRUE* enables auto scaling. Setting to
-*FALSE* disables auto scaling. The default value is *TRUE*. Auto
-scaling is only available for Autonomous Database Serverless
+Indicates whether auto scaling is enabled for the Autonomous AI
+Database CPU core count. Setting to *TRUE* enables auto scaling.
+Setting to *FALSE* disables auto scaling. The default value is *TRUE*.
+Auto scaling is only available for Autonomous AI Database Serverless
 instances.
 
 --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 a
+** Deprecated. ** Indicates whether the Autonomous AI Database has a
 local (in-region) standby database. Not applicable when creating a
-cross-region Autonomous Data Guard associations, or to Autonomous
+cross-region Autonomous Data Guard associations, or to Autonomous AI
 Databases using dedicated Exadata infrastructure or Exadata
 Cloud@Customer infrastructure.
 
 To create a local standby, set to *TRUE*. To delete a local standby,
 set to *FALSE*. For more information on using Autonomous Data Guard on
-an Autonomous Database Serverless instance (local and cross-region) ,
-see About Standby Databases
+an Autonomous AI Database Serverless instance (local and cross-region)
+, see About Standby Databases
 
-To enable cross-region Autonomous Data Guard on an Autonomous Database
-Serverless instance, see Enable Autonomous Data Guard.
+To enable cross-region Autonomous Data Guard on an Autonomous AI
+Database Serverless instance, see Enable Autonomous Data Guard.
 
 To delete a cross-region standby database, provide the *peerDbId* for
 the standby database in a remote region, and set *isDataGuardEnabled*
@@ -421,7 +423,7 @@ to *FALSE*.
 
 --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
@@ -432,13 +434,13 @@ upgrade to a full paid production database.
 
 --is-disable-db-version-upgrade-schedule [boolean]
 
-True if user wants to disable Autonomous Database scheduled upgrade to
-23ai.
+True if user wants to disable Autonomous AI Database scheduled upgrade
+to 26ai.
 
 --is-disconnect-peer [boolean]
 
-If true, this will disconnect the Autonomous Database from its peer
-and the Autonomous Database can work permanently as a standalone
+If true, this will disconnect the Autonomous AI Database from its peer
+and the Autonomous AI Database can work permanently as a standalone
 database.
 
 To disconnect a cross region standby, please also provide the OCID of
@@ -447,8 +449,9 @@ the standby database in the *peerDbId* parameter.
 --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,
@@ -459,19 +462,19 @@ isLocalDataGuardEnabled
 
 --is-local-data-guard-enabled [boolean]
 
-Indicates whether the Autonomous Database has a local (in-region)
+Indicates whether the Autonomous AI Database has a local (in-region)
 standby database. Not applicable when creating a 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.
 
 To create a local standby, set to *TRUE*. To delete a local standby,
 set to *FALSE*. For more information on using Autonomous Data Guard on
-an Autonomous Database Serverless instance (local and cross-region) ,
-see About Standby Databases
+an Autonomous AI Database Serverless instance (local and cross-region)
+, see About Standby Databases
 
-To enable cross-region Autonomous Data Guard on an Autonomous Database
-Serverless instance, see Enable Autonomous Data Guard.
+To enable cross-region Autonomous Data Guard on an Autonomous AI
+Database Serverless instance, see Enable Autonomous Data Guard.
 
 This cannot be updated in parallel with any of the following:
 isMTLSRequired, dbWorkload, dbVersion, isRefreshable, dbName,
@@ -479,7 +482,7 @@ scheduledOperations, dbToolsDetails, or isFreeTier.
 
 --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,
@@ -493,9 +496,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
@@ -506,7 +509,7 @@ set the isMTLSConnectionRequired attribute to true.
 
 --is-refreshable-clone [boolean]
 
-Indicates if the Autonomous Database is a refreshable clone.
+Indicates if the Autonomous AI Database is a refreshable clone.
 
 This cannot be updated in parallel with any of the following:
 cpuCoreCount, computeCount, computeModel, adminPassword,
@@ -516,22 +519,22 @@ dbToolsDetails, isLocalDataGuardEnabled, or isFreeTier.
 
 --is-schedule-db-version-upgrade-to-earliest [boolean]
 
-True if user wants to schedule Autonomous Database upgrade to the
+True if user wants to schedule Autonomous AI Database upgrade to the
 earliest available time.
 
 --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:
@@ -571,8 +574,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.
 
@@ -583,13 +586,14 @@ via the file:// syntax.
 
 --ocpu-count [float]
 
-The number of OCPU cores to be made available to the Autonomous
+The number of OCPU cores to be made available to the Autonomous AI
 Database.
 
-For Autonomous Databases on Dedicated Exadata Infrastructure, you can
-specify a fractional value for this parameter. Fractional values are
-not supported for Autonomous Database Serverless instances. For
-Autonomous Database Serverless instances, this parameter is not used.
+For Autonomous AI Databases on Dedicated Exadata Infrastructure, you
+can specify a fractional value for this parameter. Fractional values
+are not supported for Autonomous AI Database Serverless instances. For
+Autonomous AI Database Serverless instances, this parameter is not
+used.
 
 To provision less than 1 core, enter a fractional value in an
 increment of 0.1. To provision 1 or more cores, you must enter an
@@ -611,8 +615,8 @@ only to perform validation on the submitted data.
 
 --open-mode [text]
 
-Indicates the Autonomous Database mode. The database can be opened in
-*READ_ONLY* or *READ_WRITE* mode.
+Indicates the Autonomous AI Database mode. The database can be opened
+in *READ_ONLY* or *READ_WRITE* mode.
 
 This cannot be updated in parallel with any of the following:
 cpuCoreCount, computeCount, computeModel, adminPassword,
@@ -634,7 +638,7 @@ To create or delete a local (in-region) standby, see the
 
 --permission-level [text]
 
-The Autonomous Database permission level. Restricted mode allows
+The Autonomous AI Database permission level. Restricted mode allows
 access only by admin users.
 
 This cannot be updated in parallel with any of the following:
@@ -670,7 +674,7 @@ or isFreeTier.
 --refreshable-mode [text]
 
 The refresh mode of the clone. AUTOMATIC indicates that the clone is
-automatically being refreshed with data from the source Autonomous
+automatically being refreshed with data from the source Autonomous AI
 Database.
 
 Accepted values are:
@@ -679,7 +683,7 @@ Accepted values are:
 
 --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]
 
@@ -743,14 +747,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
@@ -786,7 +790,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
@@ -797,7 +801,7 @@ both the client subnet and the backup subnet.
 --time-of-auto-refresh-start [datetime]
 
 The the date and time that auto-refreshing will begin for an
-Autonomous Database refreshable clone. This value controls only the
+Autonomous AI Database refreshable clone. This value controls only the
 start time for the first refresh operation. Subsequent (ongoing)
 refresh operations have start times controlled by the value of the
 *autoRefreshFrequencyInSeconds* parameter.
@@ -886,8 +890,8 @@ Timezone with microseconds
 
 --time-scheduled-db-version-upgrade [datetime]
 
-The date and time the Autonomous Database scheduled to upgrade to
-23ai.
+The date and time the Autonomous AI Database scheduled to upgrade to
+26ai.
 
    The following datetime formats are supported:
 
@@ -971,6 +975,17 @@ Timezone with microseconds
 
        Example: 1412195400
 
+--vanity-url-details [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.
+
 --wait-for-state [text]
 
 This operation creates, modifies or deletes a resource that has a
@@ -995,14 +1010,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

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

@@ -17,7 +17,7 @@
 Description
 ===========
 
-Creates a new Autonomous Database backup for the specified database
+Creates a new Autonomous AI Database backup for the specified database
 based on the provided request parameters.
 
 
@@ -32,7 +32,7 @@ Required Parameters
 
 --autonomous-database-id [text]
 
-The OCID of the Autonomous Database backup.
+The OCID of the Autonomous AI Database backup.
 
 
 Optional Parameters

oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database-backup/delete.txt

@@ -32,7 +32,7 @@ Required Parameters
 
 --autonomous-database-backup-id [text]
 
-The OCID of the Autonomous Database backup.
+The OCID of the Autonomous AI Database backup.
 
 
 Optional Parameters

oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database-backup/get.txt

@@ -17,7 +17,7 @@
 Description
 ===========
 
-Gets information about the specified Autonomous Database backup.
+Gets information about the specified Autonomous AI Database backup.
 
 
 Usage
@@ -31,7 +31,7 @@ Required Parameters
 
 --autonomous-database-backup-id [text]
 
-The OCID of the Autonomous Database backup.
+The OCID of the Autonomous AI Database backup.
 
 
 Optional Parameters

oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database-backup/list.txt

@@ -15,7 +15,7 @@
 Description
 ===========
 
-Gets a list of Autonomous Database backups based on either the
+Gets a list of Autonomous AI Database backups based on either the
 *autonomousDatabaseId* or *compartmentId* specified as a query
 parameter.
 

oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database-backup/update.txt

@@ -17,8 +17,8 @@
 Description
 ===========
 
-Updates the Autonomous Database backup of the specified database based
-on the request parameters.
+Updates the Autonomous AI Database backup of the specified database
+based on the request parameters.
 
 
 Usage
@@ -32,7 +32,7 @@ Required Parameters
 
 --autonomous-database-backup-id [text]
 
-The OCID of the Autonomous Database backup.
+The OCID of the Autonomous AI Database backup.
 
 
 Optional Parameters

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

@@ -5,7 +5,7 @@ autonomous-database-backup
 Description
 ===========
 
-An Autonomous Database backup.
+An Autonomous AI Database backup.
 
 
 Available Commands

oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database-character-sets/list.txt

@@ -64,15 +64,15 @@ nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
 
 --is-dedicated [boolean]
 
-Specifies if the request is for an Autonomous Database Dedicated
-instance. The default request is for an Autonomous Database Dedicated
-instance.
+Specifies if the request is for an Autonomous AI Database Dedicated
+instance. The default request is for an Autonomous AI Database
+Dedicated instance.
 
 --is-shared [boolean]
 
-Specifies whether this request is for an Autonomous Database
+Specifies whether this request is for an Autonomous AI Database
 Serverless instance. By default, this request will be for Autonomous
-Database on Dedicated Exadata Infrastructure.
+AI Database on Dedicated Exadata Infrastructure.
 
 
 Global Parameters

oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database-character-sets.txt

@@ -5,7 +5,7 @@ autonomous-database-character-sets
 Description
 ===========
 
-The Oracle Autonomous Database supported character sets.
+The Oracle Autonomous AI Database supported character sets.
 
 To use any of the API operations, you must be authorized in an IAM
 policy. If you’re not authorized, talk to an administrator. If you’re

oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database-dataguard/get.txt

@@ -19,7 +19,7 @@ Description
 
 *Deprecated.* Use the GetAutonomousContainerDatabase operation to gets
 an Autonomous Data Guard-enabled database associated with the
-specified Autonomous Database.
+specified Autonomous AI Database.
 
 
 Usage

oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database-dataguard/list.txt

@@ -19,7 +19,7 @@ Description
 
 *Deprecated.* Use the GetAutonomousContainerDatabase operation to get
 a list of the Autonomous Data Guard-enabled databases associated with
-the specified Autonomous Database.
+the specified Autonomous AI Database.
 
 
 Usage

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

@@ -6,10 +6,10 @@ Description
 ===========
 
 The properties that define dataguard association between two different
-Autonomous Databases. Note that Autonomous Databases inherit DataGuard
-association from parent Autonomous Container Database. No actions can
-be taken on AutonomousDatabaseDataguardAssociation, usage is strictly
-informational.
+Autonomous AI Databases. Note that Autonomous AI Databases inherit
+DataGuard association from parent Autonomous Container Database. No
+actions can be taken on AutonomousDatabaseDataguardAssociation, usage
+is strictly informational.
 
 
 Available Commands