Database Management

This section covers comprehensive tasks for managing Oracle AI Databases. It includes commands for creating (dbaascli database create), deleting (dbaascli database delete), and upgrading databases (dbaascli database upgrade). Other key tasks include adding and deleting instances (dbaascli database addInstance, dbaascli database deleteInstance), managing backups (dbaascli database backup), and handling database recovery (dbaascli database recover). You can also modify database parameters, manage pluggable databases, patch databases, and convert non-CDB databases to PDBs. These commands ensure efficient control over the entire database lifecycle.

dbaascli database addInstance

To add the database instance on the specified node, use the dbaascli database addInstance command.

Prerequisites:

Syntax:

dbaascli database addInstance --dbname <value> --node <value> [--newNodeSID <value>]

Parameters:

Parameter Description
--dbname specifies Oracle AI Database name
--node specifies the node name for the database instance
--newNodeSID specifies SID for the instance to add in the new node

Frequently Asked Questions:

Q: What is the purpose of the dbaascli database addInstance command?

A: The dbaascli database addInstance command is used to add a new database instance to a specified node in an Oracle Base Database Cloud@Customer environment.

Q: What are the prerequisites for running the dbaascli database addInstance command?

A: The command must be run as the root user to have the necessary permissions to add a database instance.

Q: What does the –dbname option represent in this command?

A: The --dbname option specifies the name of the Oracle AI Database for which you want to add a new instance.

Q: What is the –node option used for in the dbaascli database addInstance command?

A: The --node option specifies the name of the node where the new database instance will be added.

Q: What is the purpose of the –newNodeSID option in this command?

A: The --newNodeSID option allows you to specify the SID (System Identifier) for the new database instance that will be created on the specified node.

Q: Is it mandatory to specify the –newNodeSID option when adding a new instance?

A: The --newNodeSID option is optional. If not provided, Oracle will automatically generate an SID for the new database instance.

Q: When should I use the dbaascli database addInstance command?

A: Use this command when you want to scale your database by adding a new instance to an additional node in a multi-node Oracle AI Database setup.

Q: Can I add multiple database instances to different nodes using this command?

A: Yes, you can run the command multiple times to add database instances to different nodes by specifying the appropriate --node and --dbname values.

Q: What happens if the node specified in the –node option is not available?

A: The command will fail if the specified node is not available or reachable. Ensure that the node is properly configured and accessible before running the command.

Q: Can this command be used in a Data Guard environment?

A: Yes, you can use the dbaascli database addInstance command in a Data Guard environment to add instances, but it is recommended to follow the necessary Data Guard guidelines for such configurations.

Q: Will this command cause database downtime?

A: Adding an instance to a new node typically does not cause downtime for the existing database instances, but it’s recommended to check your environment for any specific dependencies.

dbaascli database backup

To configure Oracle AI Database with a backup storage destination, take database backups, query backups, and delete a backup, use the dbaascli database backup command.

Prerequisites:

Syntax:

dbaascli database backup --dbname <value>
        {
            --list
                {
                    [--backupType <value>]
                    | [--json <value>]
                }
            | --start [--level0] [--level1]
                {
                    [--archival --tag <value>]
                    | [--archivelog]
                }
            | --delete --backupTag <value>
            | --status --uuid <value> [--json <value>]
            | --getBackupReport
                {
                    --tag <value>
                    | --latest
                }
                --json <value>
            | --configure
                {
                    --configFile <value>
                    | --enableRTRT
                    | --disableRTRT
                    | --disableCatalog
                    | --deleteImmutableConfiguration
                }
            | --getConfig
                {
                    [--configFile <value>]
                    | [--showOldParams]
                }
            | --validate [--untilTime <value>]
            | --showHistory [--all]
            | --getSchedules
        }

Parameters:

Parameter Attributes Description
--dbname - specifies Oracle AI Database name
--list - returns database backup information
--list --backupType | --json -
--list --backupType specifies backupType (REGULAR-L0 | REGULAR-L1 | ARCHIVELOG | LONGTERM).
--list --json specifies file Name for JSON output.
--start - begins database backup.
--start --level0 creates a Level-0 (full) backup.
--start --level1 creates a Level-1 (incremental) backup.
--start --archival | --archivelog -
--start --archival creates an archival full backup.
--start --archival → --tag specifies backup tag.
--start --archivelog -
--delete - deletes Archival backup.
--delete --backupTag specifies backup tag to delete.
--status - displays the details about a backup job process.
--status --uuid unique identifier of the backup operation. Input format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.
--status --uuid → --json specifies file Name for JSON output.
--getBackupReport - returns BackupReport.
--getBackupReport --tag | --latest -
--getBackupReport --tag specifies backup tag.
--getBackupReport --latest returns latest backup report (all types of database backup).
--getBackupReport --json specifies file Name for JSON output.
--configure - configures database for backup.
--configure --configFile | --enableRTRT | --disableRTRT | --disableCatalog | --deleteImmutableConfiguration -
--configure --configFile specifies database backup configuration file.
--configure --enableRTRT enables Real Time Redo Transport.
--configure --disableRTRT disables Real Time Redo Transport.
--configure --disableCatalog disables recovery catalog.
--configure --deleteImmutableConfiguration -
--getConfig - returns database backup configuration.
--getConfig --configFile | --showOldParams -
--getConfig --configFile specifies database backup configuration file.
--getConfig --showOldParams returns old parameter names of backup configuration.
--validate - validates that backups are complete and corruption-free.
--validate --untilTime validates from closest Level-0 (full) backup until time provided. Input format: DD-MON-YYYY HH24:MI:SS.
--showHistory - displays history of backup operations.
--showHistory --all displays all backup operations.
--getSchedules - returns all backup schedules for a given database.

Note: enableRTRT and disableRTRT are applicable only for ZDLRA backup destination on Oracle Base Database Cloud@Customer.

Frequently Asked Questions:

Q: What is the purpose of the dbaascli database backup command?

A: The dbaascli database backup command is used to configure Oracle AI Database backup storage destinations, take backups, query backups, and delete existing backups.

Q: What are the prerequisites for running the dbaascli database backup command?

A: The command must be run as the root user to have the necessary permissions for backup management.

Q: How do I start a full backup of the Oracle AI Database using this command?

A: To start a full backup (Level-0), use the following syntax:

dbaascli database backup --dbname <value> --start --level0

Q: How do I perform an incremental backup using the dbaascli database backup command?

A: To perform a Level-1 incremental backup, use this syntax:

dbaascli database backup --dbname <value> --start --level1

Q: What is the difference between Level-0 and Level-1 backups?

A: A Level-0 backup is a full backup of the database, while a Level-1 backup is an incremental backup that only captures changes made since the last Level-0 or Level-1 backup.

Q: Can I take an archival backup using this command?

A: Yes, you can create an archival backup by using the --archival option along with the --start command:

dbaascli database backup --dbname <value> --start --archival --tag <backup_tag>

Q: How do I delete an existing archival backup?

A: To delete an archival backup, use the following syntax:

dbaascli database backup --dbname <value> --delete --backupTag <tag_value>

Q: How can I check the status of a specific backup using the command?

A: You can check the status of a backup by using the --status option with the --uuid parameter, like this:

dbaascli database backup --dbname <value> --status --uuid <backup_uuid>

Q: How do I list all backups for a database?

A: To list all available backups for a specific database, use the --list option:

dbaascli database backup --dbname <value> --list

For JSON output, add the --json option:

dbaascli database backup --dbname <value> --list --json <file_name>

Q: How can I retrieve a backup report?

A: You can get a backup report using the --getBackupReport option, either for a specific tag or for the latest backup:

dbaascli database backup --dbname <value> --getBackupReport --tag <backup_tag> --json <file_name>

Or to retrieve the latest report:

dbaascli database backup --dbname <value> --getBackupReport --latest --json <file_name>

Q: How do I configure database backup settings?

A: Use the --configure option to specify the backup configuration file or to enable/disable Real-Time Redo Transport (RTRT):

dbaascli database backup --dbname <value> --configure --configFile <config_file>

To enable RTRT:

dbaascli database backup --dbname <value> --configure --enableRTRT

Q: How do I check the current backup configuration for my database?

A: To view the current database backup configuration, use the --getConfig option:

dbaascli database backup --dbname <value> --getConfig

Q: What does the –validate option do in the dbaascli database backup command?

A: The --validate option checks if backups are complete and free from corruption. You can specify a time range using the --untilTime option:

dbaascli database backup --dbname <value> --validate --untilTime "DD-MON-YYYY HH24:MI:SS"

Q: How do I view the history of all backup operations for a database?

A: Use the --showHistory option to display the history of all backup operations:

dbaascli database backup --dbname <value> --showHistory

For complete history, including all operations:

dbaascli database backup --dbname <value> --showHistory --all

Q: What are RTRT (Real-Time Redo Transport) options and when should I use them?

A: The RTRT options (--enableRTRT and --disableRTRT) are used to control Real-Time Redo Transport, applicable only for ZDLRA (Zero Data Loss Recovery Appliance) backup destinations in Oracle Base Database Cloud@Customer environments. Enable RTRT to ensure real-time redo log shipping.

Examples:

dbaascli database bounce

To shut down and restart a specified Oracle Base Database Cloud@Customer database, use the dbaascli database bounce command.

Prerequisites:

Run the command as the oracle user.

Syntax:

dbaascli database bounce
[--dbname][--rolling <value>]

Parameters:

Parameter Description
--dbname specifies the name of the database
--rolling specifies true or false to bounce the database in a rolling manner. Default value is false.

The command performs a database shutdown in immediate mode. The database is then restarted and opened. In Oracle Database 12c or later, all of the PDBs are also opened.

Frequently Asked Questions:

Q: What is the purpose of the dbaascli database bounce command?

A: The dbaascli database bounce command is used to shut down and restart an Oracle AI Database in Oracle Base Database Cloud@Customer. It supports restarting the database in a rolling manner, ensuring minimal disruption.

Q: What are the prerequisites for running the dbaascli database bounce command?

A: The command must be run as the oracle user, which has the required privileges to shut down and restart the database.

Q: What does the –dbname option specify in this command?

A: The --dbname option specifies the name of the Oracle AI Database that you want to shut down and restart.

Q: What is the –rolling option used for in the dbaascli database bounce command?

A: The --rolling option specifies whether to bounce (restart) the database in a rolling manner. If set to true, the database instances are restarted one by one, ensuring minimal downtime. The default value is false, which restarts all instances at once.

Q: What does “bouncing the database” mean?

A: Bouncing the database refers to shutting it down and then restarting it. This operation can be used for maintenance, applying changes, or recovering from certain types of issues.

Q: Does the dbaascli database bounce command perform a graceful shutdown?

A: Yes, the command performs a shutdown in “immediate” mode, which closes the database and rolls back uncommitted transactions without waiting for users to disconnect.

Q: Will this command automatically open all PDBs in an Oracle 12c or later database?

A: Yes, if the database is running Oracle Database 12c or later, the command will automatically open all Pluggable Databases (PDBs) after restarting the database.

Q: Can the dbaascli database bounce command be used in a multi-node or RAC (Real Application Clusters) environment?

A: Yes, in a multi-node or RAC environment, you can use the --rolling option to restart the database instances one by one, minimizing downtime.

Q: What happens if I do not specify the –rolling option?

A: If the --rolling option is not specified, or if it’s set to false, the command will shut down and restart all database instances at the same time, which may cause a brief downtime.

Q: Is there a default value for the –rolling option in the dbaascli database bounce command?

A: Yes, the default value for the --rolling option is false, meaning the database will be bounced in a non-rolling fashion unless otherwise specified.

Q: How do I restart a database in rolling mode?

A: To restart the database in rolling mode, use the following syntax:

dbaascli database bounce --dbname <value> --rolling true

Q: Is it safe to run the dbaascli database bounce command during active sessions?

A: While the command uses an immediate shutdown, which rolls back uncommitted transactions, it is always recommended to ensure there are no critical or active sessions before bouncing the database.

Q: Can this command be used for specific PDBs in a multitenant database?

A: No, the dbaascli database bounce command operates on the entire database. In Oracle 12c or later, it will bounce the Container Database (CDB) and open all PDBs, but it does not allow for bouncing individual PDBs.

Q: What should I do if the database does not come back online after bouncing it?

A: If the database fails to restart, check the logs for any errors during the shutdown or startup process. Investigating the Oracle alert logs may provide insight into what caused the issue.

Example: dbaascli database bounce

dbaascli database bounce --dbname dbname

dbaascli database changepassword

To change the password of a specified Oracle AI Database user, use the dbaascli database changePassword command. When prompted enter the user name for which you want to change the password and then enter the password.

Prerequisites:

Run the command as the root or oracle user.

Syntax:

dbaascli database changePassword [--dbname <value>] [--user <value>]
{
  [--prepareStandbyBlob <value> [--blobLocation <value>]] | [--standbyBlobFromPrimary <value>]
}
[--resume [--sessionID <value>]]

Parameters:

Parameter Description
--dbname specifies the name of the Oracle AI Database that you want to act on
--user specifies the user name whose password change is required
--prepareStandbyBlob specifies true to generate a blob file containing the artifacts needed to change the password in a Data Guard environment. Valid values: true or false
--blobLocation specifies the custom path where blob file will be generated
--standbyBlobFromPrimary specifies the standby blob file, which is prepared from the primary database
--resume specifies to resume the previous execution
--sessionID specifies to resume a specific session ID

Frequently Asked Questions:

Q: What does the dbaascli database changePassword command do?

A: The dbaascli database changePassword command is used to change the password of a specified Oracle AI Database user. You will be prompted to enter the username and then the new password.

Q: What are the prerequisites for using the dbaascli database changePassword command?

A: You must run the command as either the root or oracle user to change the password for a database user.

Q: How do I specify the database when using this command?

A: Use the --dbname option to specify the name of the Oracle AI Database you want to act on. For example:

dbaascli database changePassword --dbname <db_name>

Q: How do I specify the user whose password I want to change?

A: Use the --user option to specify the username whose password needs to be changed. For example:

dbaascli database changePassword --user <username>

Q: What is the purpose of the –prepareStandbyBlob option in the dbaascli database changePassword command?

A: The --prepareStandbyBlob option is used in Data Guard environments to generate a blob file that contains the artifacts required for the password change on the standby database. This ensures password synchronization across the Data Guard environment.

Q: What does the –blobLocation option specify?

A: The --blobLocation option allows you to specify a custom path where the standby blob file should be generated. If not provided, the file will be saved in the default location.

Q: How do I use the blob generated from the primary database to change the password on the standby?

A: You can use the --standbyBlobFromPrimary option to specify the blob file prepared from the primary database to apply the password change to the standby database. For example:

dbaascli database changePassword --standbyBlobFromPrimary <blob_file_path>

Q: What is the –resume option used for in this command?

A: The --resume option is used to resume a previously interrupted password change operation. You can specify the session ID if needed using the --sessionID option.

Q: Can I resume a specific session with the dbaascli database changePassword command?

A: Yes, you can use the --resume option along with --sessionID to resume a specific password change session by specifying the session ID.

Q: Is the dbaascli database changePassword command applicable in a Data Guard environment?

A: Yes, it is. The --prepareStandbyBlob option can be used to ensure that password changes are propagated to the standby database in a Data Guard setup.

Q: What happens if I don’t provide a –blobLocation when using –prepareStandbyBlob?

A: If no --blobLocation is provided, the blob file containing the password change artifacts will be saved to the default location.

Q: How do I check the status of a resumed session using dbaascli database changePassword?

A: You can specify the session ID using the --sessionID option to resume a specific session. The system will pick up where it left off in changing the password.

Q: Can this command be used for both regular databases and those in a Data Guard environment?

A: Yes, the command works for both regular Oracle AI Databases and databases in a Data Guard environment. In Data Guard environments, additional options like --prepareStandbyBlob can be used to manage password changes on both primary and standby databases.

Example: dbaascli database changePassword

dbaascli database changepassword --dbname db19

dbaascli database convertToPDB

To convert the specified non-CDB database to PDB, use the dbaascli database convertToPDB command.

Syntax:

dbaascli database convertToPDB --dbname <value> [--cdbName <value>] [--executePrereqs]
        {
            [--copyDatafiles]
            | [--backupPrepared]
        }
        [--targetPDBName <value>] [--waitForCompletion <value>] [--resume [--sessionID <value>]]

Parameters:

Parameter Description
--dbname specifies the name of Oracle AI Database
--cdbName specifies the name of the target CDB in which the PDB will be created. If the CDB does not exist, then it will be created in the same Oracle home as the source non-CDB
--executePrereqs specifies to run only the pre-conversion checks
--copyDatafiles specifies to create a new copy of the data files instead of using the ones from the source database
--backupPrepared flag to acknowledge that a proper database backup is in place for the non-CDB prior to performing the conversion to PDB
--targetPDBName specifies the name of the PDB that will be created as part of the operation
--waitForCompletion specifies false to run the operation in the background. Valid values: true or false
--resume specifies to resume the previous execution
--sessionID specifies to resume a specific session ID

Frequently Asked Questions:

Q: What does the dbaascli database convertToPDB command do?

A: The dbaascli database convertToPDB command converts a specified non-CDB Oracle AI Database into a Pluggable Database (PDB) within a Container Database (CDB).

Q: How do I specify which database to convert?

A: Use the --dbname option to specify the name of the non-CDB Oracle AI Database that you want to convert. For example:

dbaascli database convertToPDB --dbname <db_name>

Q: How do I specify the target CDB for the PDB conversion?

A: Use the --cdbName option to specify the name of the target Container Database (CDB) in which the new PDB will be created. If the CDB does not exist, a new one will be created in the same Oracle home as the source non-CDB.

Q: What does the –executePrereqs option do?

A: The --executePrereqs option runs pre-conversion checks to ensure that the database is ready for conversion. No changes will be made to the database during this step.

Q: How do I copy the data files during the conversion?

A: You can use the --copyDatafiles option to create a new copy of the data files rather than using the original files from the source database.

Q: What is the purpose of the –keepSourceDB option?

A: The --keepSourceDB option allows you to preserve the original source non-CDB after the conversion operation is completed. If you do not use this option, the source database will be removed after conversion.

Q: How do I confirm that a backup is prepared before conversion?

A: Use the --backupPrepared flag to acknowledge that you have taken a proper backup of the non-CDB database before performing the conversion. This step is crucial to avoid data loss.

Q: How do I specify a custom name for the new PDB?

A: Use the --targetPDBName option to provide a specific name for the new PDB that will be created as part of the conversion. For example:

dbaascli database convertToPDB --dbname <db_name> --targetPDBName <pdb_name>

Q: Can I run the conversion in the background?

A: Yes, you can use the --waitForCompletion option to specify whether the operation should be run in the background. Use false to run in the background and true to wait for the operation to complete before proceeding. The default is true.

Q: How do I resume a previously interrupted conversion?

A: You can use the --resume option to resume a previously interrupted conversion process. Optionally, you can provide the --sessionID to resume a specific session.

Q: What happens if I don’t specify a CDB name?

A: If the --cdbName option is not provided, the system will create the new PDB in the same Oracle home as the source non-CDB database.

Q: Can I continue the conversion after an interruption without knowing the session ID?

A: Yes, using the --resume option without specifying a session ID will resume the last known session. If you want to resume a specific session, you can provide the --sessionID.

Q: What does the –sessionID option do?

A: The --sessionID option is used in conjunction with --resume to specify a particular session to resume, in case there were multiple interrupted sessions.

Q: Is it mandatory to have a backup before converting a non-CDB to a PDB?

A: While the --backupPrepared flag is optional, it is highly recommended to take a backup of the non-CDB before performing the conversion to PDB. This ensures that you can restore the database in case of any issues during the conversion.

Example: dbaascli database convertToPDB

To run pre-conversion prechecks:

dbaascli database convertToPDB --dbname ndb19 --cdbname cdb19 --backupPrepared --executePrereqs

To run a full conversion with a copy of the data files from the non-CDB:

dbaascli database convertToPDB --dbname tst19 --cdbname cdb19 --copyDatafiles

dbaascli database create

To create Oracle AI Database, use the dbaascli database create command. When prompted, enter the sys and tde passwords.

Use this command to create Oracle Database version 12.1.0.2 or higher with the release update JAN 2021 or higher. For databases with lower versions, it is recommended to use the OCI Console based API.

Prerequisites:

Run the command as the root user.

Syntax:

dbaascli database create --dbName {--oracleHome | --oracleHomeName}
[--dbUniqueName <value>]
[--dbSID <value>]
[--createAsCDB <value>]
[--pdbName <value>]
[--pdbAdminUserName <value>]
[--dbCharset <value>]
[--dbNCharset <value>]
[--dbLanguage <value>]
[--dbTerritory <value>]
[--sgaSizeInMB <value>]
[--pgaSizeInMB <value>]
[--datafileDestination <value>]
[--fraDestination <value>]
[--fraSizeInMB <value>]
[--nodeList <value>]
[--tdeConfigMethod <value>]
[--kmsKeyOCID <value>]
{
            [--resume [--sessionID <value>]]
            | [--revert [--sessionID <value>]]
        }
[--executePrereqs]
[--honorNodeNumberForInstance <value>]
[--lockPDBAdminAccount <value>]
[--dbcaTemplateFilePath <value>]
[--waitForCompletion]

Parameters:

Parameter Description
--dbname specifies the name of the database
--oracleHome specifies the location of the Oracle home
--oracleHomeName specifies the name of the Oracle home
--dbUniqueName specifies database unique name
--dbSID specifies the SID of the database
--createAsCDB specifies true or false to create database as CDB or Non-CDB
--pdbName specifies the name of the PDB
--pdbAdminUserName specify PDB admin user name
--dbCharset specifies database character set
--dbNCharset specifies database national character set
--dbLanguage specifies the database language
--dbTerritory specifies the database territory
--sgaSizeInMB specifies the sga_target value in megabyte unit
--pgaSizeInMB specifies the pga_aggregate_target value in megabyte unit
--datafileDestination specifies the ASM disk group name to use for database datafiles
--fraDestination specifies ASM disk group name to use for database Fast Recovery Area
--fraSizeInMB specifies the Fast Recovery Area size value in megabyte unit
--nodeList specifies a comma-delimited list of nodes for the database
--tdeConfigMethod specifies TDE configuration method. Valid values: FILE, KMS
--kmsKeyOCID specifies KMS key OCID to use for TDE. This is applicable only if KMS is selected for TDE
--resume resumes the previous execution
--revert rolls back the previous run
--sessionID resumes or reverts to a specific session ID.
--executePrereqs specifies yes to run only the prereqs for this operation. Valid values: yes or no
--honorNodeNumberForInstance specifies true or false to indicate instance name to be suffixed with the cluster node numbers. Default value: true
--lockPDBAdminAccount specifies true or false to lock the PDB admin user account. Default value is true
--dbcaTemplateFilePath specifies the absolute path of the dbca template name to create the database.
--waitForCompletion specifies false to run the operation in the background. Valid values: true or false

Frequently Asked Questions:

Q: What does the dbaascli database create command do?

A: The dbaascli database create command is used to create a new Oracle AI Database instance. It supports creating Oracle Database version 12.1.0.2 or higher with the release update JAN 2021 or higher.

Q: How do I specify the name of the Oracle AI Database to create?

A: Use the --dbName option to specify the name of the Oracle AI Database. For example:

dbaascli database create --dbName <db_name>

Q: How can I create a Container Database (CDB)?

A: Use the --createAsCDB option and specify true to create the database as a CDB. For example:

dbaascli database create --dbName <db_name> --createAsCDB true

Q: How do I specify the Oracle Home for the database?

A: You can use either the --oracleHome option to specify the location of the Oracle home or the --oracleHomeName option to specify the name of the Oracle home.

Q: How do I specify a unique database name or SID?

A: Use the --dbUniqueName option to specify a unique name for the database and the --dbSID option to specify the SID of the database.

Q: How do I create a Pluggable Database (PDB) along with a CDB?

A: You can use the --pdbName option to specify the name of the PDB, and the --pdbAdminUserName option to set the PDB admin username. For example:

dbaascli database create --dbName <db_name> --createAsCDB true --pdbName <pdb_name> --pdbAdminUserName <admin_user>

Q: How can I specify the database character set and national character set?

A: Use the --dbCharset option to specify the database character set and the --dbNCharset option to specify the national character set. For example:

dbaascli database create --dbName <db_name> --dbCharset AL32UTF8 --dbNCharset AL16UTF16

Q: How do I set the memory settings (SGA and PGA) for the database?

A: Use the --sgaSizeInMB option to specify the SGA size and the --pgaSizeInMB option to specify the PGA size, both in megabytes.

Q: How do I specify the destination for datafiles and Fast Recovery Area (FRA)?

A: Use the --datafileDestination option to specify the ASM disk group for datafiles, and the --fraDestination option to specify the ASM disk group for the FRA. You can also set the FRA size with the --fraSizeInMB option.

Q: Can I configure Transparent Data Encryption (TDE) during database creation?

A: Yes, you can configure TDE using the --tdeConfigMethod option. Valid values are FILE (for file-based encryption) or KMS (for using Oracle Key Management Service). If using KMS, provide the KMS key OCID with the --kmsKeyOCID option.

Q: How do I create the database on a specific list of nodes?

A: Use the --nodeList option to specify a comma-separated list of nodes where the database should be created.

Q: How can I resume or revert a previous database creation attempt?

A: Use the --resume option to resume the previous execution or the --revert option to roll back the previous run. You can also specify a --sessionID to resume or revert a specific session.

Q: What does the –executePrereqs option do?

A: The --executePrereqs option only runs the prerequisites for the database creation operation, without actually creating the database. Use yes or no to enable or disable this option.

Q: Can I specify a custom DBCA template for the database creation?

A: Yes, use the --dbcaTemplateFilePath option to provide the absolute path of the DBCA template file that should be used to create the database.

Q: Can I run the database creation operation in the background?

A: Yes, you can use the --waitForCompletion option to specify whether the command should wait for the database creation to complete (true) or run the operation in the background (false).

Q: What happens if I don’t specify the –dbUniqueName option?

A: If you don’t specify a unique name for the database using --dbUniqueName, the system will automatically generate one based on the provided --dbName.

Q: Can I lock the PDB admin account during the creation of a CDB?

A: Yes, you can use the --lockPDBAdminAccount option and set it to true to lock the PDB admin account after database creation. By default, this value is set to true.

Example: dbaascli database create

dbaascli database create --dbName db19 --oracleHomeName myhome19 --dbSid db19sid --nodeList node1,node2 --createAsCDB true

dbaascli database createTemplate

Use this command to create database templates (DBCA templates) that can subsequently be used to create databases.

Run the command as the root or oracle user.

Syntax:

Create a new DBCA template from the specified database.

dbaascli database createTemplate --dbname <value>
 {
   --templateLocation <value> | --uploadToObjectStorage --objectStorageLoginUser <value> --objectStorageBucketName <value> [--objectStorageUrl <value>]
 }
 [--templateName <value>] [--rmanParallelism <value>]

Parameters:

Parameter Description
--dbname specifies the name of the database
--templateLocation specifies the template name
--uploadToObjectStorage specifies to upload the template to Object Storage
--objectStorageLoginUser specifies the Object Storage login user
--objectStorageBucketName specifies the Object Storage bucket name
--objectStorageUrl specifies the Object Storage URL
--templateName specifies the name of the template
--rmanParallelism specifies the parallelism value

Frequently Asked Questions:

Q: What is the purpose of the dbaascli database createTemplate command?

A: The dbaascli database createTemplate command is used to create database templates (DBCA templates) from a specified database, which can later be used to create new databases.

Q: How do I specify the name of the database for which I want to create a template?

A: Use the --dbname option to specify the name of the Oracle AI Database from which the template will be created. For example:

dbaascli database createTemplate --dbname <db_name>

Q: How do I specify where the template should be saved?

A: Use the --templateLocation option to specify the location where the DBCA template will be saved. For example:

dbaascli database createTemplate --dbname <db_name> --templateLocation /path/to/template

Q: Can I upload the template to Object Storage directly?

A: Yes, you can use the --uploadToObjectStorage option to upload the DBCA template to Object Storage. You will need to specify the Object Storage login user and bucket name with the --objectStorageLoginUser and --objectStorageBucketName options, respectively.

Q: How do I specify the Object Storage login details when uploading the template?

A: Use the following options to specify Object Storage details:

--objectStorageLoginUser: Specifies the Object Storage login user.

--objectStorageBucketName: Specifies the Object Storage bucket name.

--objectStorageUrl: (Optional) Specifies the URL of the Object Storage if it is different from the default one.

For example:

dbaascli database createTemplate --dbname <db_name> --uploadToObjectStorage --objectStorageLoginUser <user> --objectStorageBucketName <bucket_name>

Q: How do I specify a custom name for the DBCA template?

A: Use the --templateName option to specify a custom name for the DBCA template. For example:

dbaascli database createTemplate --dbname <db_name> --templateName <template_name>

Q: What is the –rmanParallelism option used for?

A: The --rmanParallelism option specifies the level of parallelism for RMAN operations during the template creation process. For example:

dbaascli database createTemplate --dbname <db_name> --rmanParallelism 4

Q: What happens if I don’t specify the –templateLocation or –uploadToObjectStorage options?

A: If you do not specify a template location using --templateLocation or choose to upload to Object Storage using --uploadToObjectStorage, the command will not know where to store the created template, and it will fail to complete.

Q: Can I use both –templateLocation and –uploadToObjectStorage at the same time?

A: No, you should choose either --templateLocation to save the template locally or --uploadToObjectStorage to upload it to Object Storage, but not both.

Q: Is the –objectStorageUrl option mandatory when uploading the template to Object Storage?

A: No, the --objectStorageUrl option is optional. If not specified, the default Object Storage URL will be used. You only need to specify this if using a custom Object Storage URL.

Q: What user privileges are required to run the dbaascli database createTemplate command?

A: The command must be run either as the root or oracle user.

Q: Can I resume a previously failed template creation process?

A: No, the dbaascli database createTemplate command does not support resuming a failed process. You will need to restart the command from the beginning.

dbaascli database delete

To delete an Oracle AI Database, use the dbaascli database delete command.

Prerequisites:

Run the command as the root user.

Syntax:

dbaascli database delete --dbname <value>
[--deleteArchiveLogs <value>]
[--deleteBackups <value>]
[--precheckOnly <value>]
[--waitForCompletion <value>]
[--force]
[--dbSID <value>]
[--resume [--sessionID <value>]]

Parameters:

Parameter Description
--dbname specifies the name of the database.
--deleteArchiveLogs specifies true or false to indicate deletion of database archive logs.
--deleteBackups specifies true or false to indicate deletion of database backups.
--precheckOnly specifies yes to run only the prechecks for this operation. Valid values: yes or no.
--waitForCompletion specifies false to run the operation in the background. Valid values: true or false.
--force flag to force delete database.
--dbSID specify database SID.
--resume to resume the previous execution.
--sessionID to resume a specific session id.

Frequently Asked Questions:

Q: What is the purpose of the dbaascli database delete command?

A: The dbaascli database delete command is used to delete an Oracle AI Database on Oracle Base Database Cloud@Customer.

Q: How do I specify the database I want to delete?

A: Use the --dbname option to specify the name of the Oracle AI Database you want to delete. For example:

dbaascli database delete --dbname <db_name>

Q: How do I delete the archive logs when deleting a database?

A: You can delete the archive logs by setting the --deleteArchiveLogs option to true. For example:

dbaascli database delete --dbname <db_name> --deleteArchiveLogs true

Q: Can I also delete backups when deleting the database?

A: Yes, use the --deleteBackups option and set it to true to delete all associated backups. For example:

dbaascli database delete --dbname <db_name> --deleteBackups true

Q: How can I run only the prechecks for the delete operation without actually deleting the database?

A: You can use the --precheckOnly option and set it to yes to run the prechecks without deleting the database. For example:

dbaascli database delete --dbname <db_name> --precheckOnly yes

Q: How do I force the deletion of a database?

A: To force the deletion of a database, use the --force flag. This bypasses checks and forces the deletion process. For example:

dbaascli database delete --dbname <db_name> --force

Q: How do I run the delete operation in the background?

A: Use the --waitForCompletion option and set it to false to run the operation in the background. For example:

dbaascli database delete --dbname <db_name> --waitForCompletion false

Q: Can I specify the SID of the database I want to delete?

A: Yes, you can specify the SID of the database using the --dbSID option. For example:

dbaascli database delete --dbname <db_name> --dbSID <sid>

Q: How do I resume a previously interrupted delete operation?

A: To resume a previous delete execution, use the --resume option. You can also specify a session ID using the --sessionID option if needed. For example:

dbaascli database delete --dbname <db_name> --resume --sessionID <session_id>

Q: What user privileges are required to run the dbaascli database delete command?

A: The command must be run as the root user.

Q: What does the –precheckOnly option do in the dbaascli database delete command?

A: The --precheckOnly option allows you to run only the prechecks for the delete operation without actually deleting the database. It ensures that all checks pass before proceeding with the actual deletion.

Q: Can I delete a database without waiting for the operation to complete?

A: Yes, by setting the --waitForCompletion option to false, the delete operation will run in the background, and you don’t have to wait for it to complete.

Example: dbaascli database delete

dbaascli database delete --dbname db19

dbaascli database deleteInstance

To delete the database instance on the specified node, use the dbaascli database deleteInstance command.

Prerequisites:

Syntax:

dbaascli database deleteInstance --dbname <value> --node <value> [--continueOnUnreachableNode]

Parameters:

Parameter Description
--dbname specifies Oracle AI Database name
--node specifies the node name for database instance
--continueOnUnreachableNode specifies to perform the operation even if the node is unreachable

Frequently Asked Questions:

Q: What is the purpose of the dbaascli database deleteInstance command?

A: The dbaascli database deleteInstance command is used to delete a specific Oracle AI Database instance on a specified node in an Oracle Base Database Cloud@Customer environment.

Q: How do I specify which Oracle AI Database instance to delete?

A: You can specify the Oracle AI Database instance to delete by using the --dbname option to provide the database name and the --node option to provide the node name. For example:

dbaascli database deleteInstance --dbname <db_name> --node <node_name>

Q: Can I delete the instance even if the node is unreachable?

A: Yes, you can use the --continueOnUnreachableNode option to proceed with the deletion, even if the specified node is unreachable. For example:

dbaascli database deleteInstance --dbname <db_name> --node <node_name> --continueOnUnreachableNode

Q: What happens if the node specified is unreachable during the delete instance operation?

A: If the node is unreachable and the --continueOnUnreachableNode option is not used, the operation will fail. If the option is used, the operation will continue even if the node cannot be accessed.

Q: How do I delete a database instance from a specific node?

A: Use the following command to delete a database instance from a specific node:

dbaascli database deleteInstance --dbname <db_name> --node <node_name>

Q: What user privileges are required to run the dbaascli database deleteInstance command?

A: The command must be run as the root user.

Q: Can I delete an instance without specifying the node?

A: No, the --node option is required to specify which node the database instance should be deleted from.

Q: What does the –continueOnUnreachableNode option do?

A: The --continueOnUnreachableNode option allows the operation to proceed even if the specified node cannot be reached, ensuring that the instance deletion continues in scenarios where the node might be down.

Q: Is it possible to delete multiple database instances at once using this command?

A: No, the dbaascli database deleteInstance command is used to delete a single database instance on a specified node at a time. You would need to run the command separately for each instance you want to delete.

Example: dbaascli database deleteinstance

dbaascli database deleteinstance --node test-node

dbaascli database duplicate

To create a database from an active database, use the dbaascli database duplicate command.

Prerequisites:

Syntax:

dbaascli database duplicate --dbName <value> --sourceDBConnectionString <value>
        {
            --oracleHome <value>
            | --oracleHomeName <value>
        }
[--dbSID <value>]
[--dbUniqueName <value>]
[--sgaSizeInMB <value>]
[--pgaSizeInMB <value>]
[--datafileDestination <value>]
[--fraDestination <value>]
[--fraSizeInMB <value>]
[--sourceDBWalletLocation <value>]
[--nodeList <value>]
        {
            [--resume [--sessionID <value>]]
            | [--revert [--sessionID <value>]]
        }
[--rmanParallelism <value>]
[--rmanSectionSizeInGB <value>]
[--tdeConfigMethod <value>]
[--kmsKeyOCID <value>]
[--sourceDBTdeConfigMethod <value>]
[--sourceDBKmsKeyOCID <value>]
[--executePrereqs <value>]
[--waitForCompletion <value>]
[--skipPDBs <value>]

Parameters:

Parameter Description
--dbName specifies Oracle AI Database name
--sourceDBConnectionString specifies source database connection string in the format of <scan_name>:<scan_port>/<database_service_name>
--oracleHome specifies Oracle home location
--oracleHomeName specifies Oracle home name
--dbSID specifies database SID
--dbUniqueName specifies database unique name
--sgaSizeInMB specifies sga_target value in mega byte unit
--pgaSizeInMB specifies pga_aggregate_target value in mega byte unit
--datafileDestination specifies ASM disk group name to use for database datafiles
--fraDestination specifies ASM disk group name to use for database fast recovery area
--fraSizeInMB specifies fast recovery area size value in mega byte unit
--sourceDBWalletLocation specifies source database TDE wallet file location. This is required to duplicate database from active database
--nodeList specifies a comma-delimited list of nodes for the database
--resume specifies to resume the previous execution
--sessionID specifies to resume a specific session ID
--revert specifies to rollback the previous execution
--sessionID specifies to rollback a specific session ID
--rmanParallelism specifies parallelism value
--rmanSectionSizeInGB specifies RMAN section size in GB
--tdeConfigMethod specifies TDE configuration method. Allowed values are FILE and KMS.
--kmsKeyOCID specifies KMS key OCID to use for TDE. This is applicable only if KMS is selected for TDE.
--sourceDBTdeConfigMethod specifies source database TDE configuration method. Allowed values are FILE and KMS.
--sourceDBKmsKeyOCID specifies source database KMS key OCID to use for TDE. This is applicable only if KMS is selected for TDE.
--executePrereqs specifies yes to run only the prereqs for this operation. Valid values: yes or no
--waitForCompletion specifies false to run the operation in background. Valid values: true or false
--skipPDBs specifies a comma-delimited list of source database PDB names, which needs to be excluded for the duplicate database operation. Example: pdb1,pdb2,...

Frequently Asked Questions:

Q: What is the purpose of the dbaascli database duplicate command?

A: The dbaascli database duplicate command is used to create a new Oracle AI Database by duplicating an existing active database.

Q: What are the prerequisites for using the dbaascli database duplicate command?

A: You must run the command as the root user.

Q: How do I specify the source database for duplication?

A: Use the --sourceDBConnectionString option to provide the source database connection string in the format <scan_name>:<scan_port>/<database_service_name>. For example:

--sourceDBConnectionString <scan_name>:<scan_port>/<database_service_name>

Q: How do I specify the location of the Oracle Home for the new database?

A: You can specify the Oracle Home location using the --oracleHome option or the Oracle Home name using the --oracleHomeName option. For example:

--oracleHome <value>

or

--oracleHomeName <value>

Q: What is the purpose of the –sourceDBWalletLocation option?

A: The --sourceDBWalletLocation option specifies the location of the source database TDE wallet file, which is required to duplicate the database from an active source database.

Q: Can I skip duplicating specific PDBs from the source database?

A: Yes, you can use the --skipPDBs option to specify a comma-delimited list of PDB names that should be excluded from the duplicate operation. For example:

--skipPDBs pdb1,pdb2

Q: How do I configure TDE for the new database?

A: Use the --tdeConfigMethod option to specify the TDE configuration method (FILE or KMS). If you choose KMS, you can provide the KMS key OCID using the --kmsKeyOCID option. For example:

--tdeConfigMethod FILE

or

--tdeConfigMethod KMS --kmsKeyOCID <value>

Q: What does the –executePrereqs option do?

A: The --executePrereqs option specifies whether to run only the prerequisite checks for the operation. Valid values are yes to run prereqs only, or no to proceed with the full operation.

Q: How can I resume a previously interrupted duplicate operation?

A: Use the --resume option along with the --sessionID option to resume a previously interrupted duplicate operation. For example:

--resume --sessionID <value>

Q: What does the –waitForCompletion option do?

A: The --waitForCompletion option specifies whether to wait for the operation to complete. Setting this to true waits for completion, while false runs the operation in the background. For example:

--waitForCompletion true

Q: What is the purpose of the –rmanParallelism option?

A: The --rmanParallelism option specifies the parallelism value for RMAN (Recovery Manager) during the duplication process. This can improve the speed of the duplication operation by using multiple parallel processes.

Q: How do I specify the size of the SGA and PGA for the new database?

A: Use the --sgaSizeInMB and --pgaSizeInMB options to specify the sizes of the SGA (System Global Area) and PGA (Program Global Area) in megabytes, respectively. For example:

--sgaSizeInMB <value>

--pgaSizeInMB <value>

Q: What does the –revert option do?

A: The --revert option is used to roll back a previous duplicate operation. You need to provide the --sessionID to specify which session to revert.

Example: dbaascli database duplicate

dbaascli database duplicate --sourceDBConnectionString test-user-scan.dbaastoolslrgsu.dbaastoolslrgvc.oraclevcn.com:1521/mynew.dbaastoolslrgsu.dbaastoolslrgvc.oraclevcn.com --oracleHome /u02/app/oracle/product/19.0.0.0/dbhome_2 --dbName newdup --sourceDBWalletLocation /var/opt/oracle/dbaas_acfs/tmp/prim_wallet

dbaascli database getDetails

This command shows the detailed information of a given database e.g. dbname, node information, pluggable databases information etc.

Prerequisites:

Run the command as the root user or the oracle user

Syntax:

dbaascli database getDetails --dbname <value>

Where :

Frequently Asked Questions:

Q: What is the purpose of the dbaascli database getDetails command?

A: The dbaascli database getDetails command shows detailed information about a specified Oracle AI Database, including the database name, node information, and pluggable database (PDB) details.

Q: Who can run the dbaascli database getDetails command?

A: The command can be run by the root user or the oracle user.

Q: What does the –dbname option specify in the dbaascli database getDetails command?

A: The --dbname option specifies the name of the Oracle AI Database for which detailed information is being retrieved.

Q: What kind of information does the dbaascli database getDetails command provide?

A: The command provides details such as the database name, node information, and information about pluggable databases (PDBs) associated with the container database.

dbaascli database getPDBs

To view the list of all pluggable databases in a container database, use the dbaascli database getPDBs command.

Run the command as the root or oracleuser.

Syntax:

dbaascli database getPDBs --dbname <value>

Parameters:

Parameter Description
--dbname specifies the name of the container database

Frequently Asked Questions:

Q: What is the purpose of the dbaascli database getPDBs command?

A: The dbaascli database getPDBs command is used to list all the pluggable databases (PDBs) within a specified container database (CDB).

Q: How do I specify the container database for the getPDBs command?

A: You use the --dbname option to specify the name of the container database. For example:

--dbname <value>

Q: Do I need to run the dbaascli database getPDBs command as a specific user?

A: Yes, you must run the command as either the root user or the oracle user.

Q: Can I view PDBs in a non-CDB database using the getPDBs command?

A: No, the getPDBs command is only applicable to container databases (CDBs). You cannot use this command for non-CDB databases.

Q: What is the format of the output from the dbaascli database getPDBs command?

A: The command returns a list of all PDBs within the specified container database. The output typically includes PDB names, statuses, and other relevant details about each pluggable database.

Q: Can this command be used for multiple databases at once?

A: No, the dbaascli database getPDBs command works with a single container database at a time, specified by the --dbname option.

Q: Is it necessary to shut down the database to use the getPDBs command?

A: No, the getPDBs command does not require the database to be shut down. It can be run while the container database is operational.

Example: dbaascli database getPDBs –dbname

dbaascli database getPDBs --dbname apr_db1

dbaascli database modifyParameters

To modify or reset initialization parameters for an Oracle AI Database, use the dbaascli database modifyParameters command.

Prerequisites:

Run the command as the root user.

Syntax:

dbaascli database modifyParameters --dbname <value>
{
--setParameters <values>[--instance <value>] [--backupPrepared] [--allowBounce]|
--resetParameters <values> [--instance <value>] [--backupPrepared] [--allowBounce]
}
--responseFile
[--backupPrepared]
[--instance]
[--allowBounce]
[--waitForCompletion]

Parameters:

Parameter Description
--dbname specifies the name of the database.
--setParameters specifies a comma-delimited list of parameters to modify with new values. For example: parameter1=valueA,parameter2=valueB, and so on. For blank values use parameter1=valueA,parameter2=’‘,etc.
--resetParameters specifies a comma-delimited list of parameters to be reset to their corresponding default values. For example, parameter1,parameter2, and so on.
--instance specifies the name of the instance on which the parameters will be processed. If not specified, then the operation will be performed at the database level.
--backupPrepared acknowledges that a proper database backup is in place prior to modifying critical or sensitive parameters.
--allowBounce grants permission to bounce the database in order to reflect the changes on applicable static parameters.
--waitForCompletion specify false to run the operation in background. Valid values: true or false.

Frequently Asked Questions:

Q: What is the purpose of the dbaascli database modifyParameters command?

A: The dbaascli database modifyParameters command is used to modify or reset Oracle AI Database initialization parameters.

Q: How do I specify the database for which I want to modify parameters?

A: You must use the --dbname option to specify the name of the database for which you want to modify or reset parameters.

Q: How can I modify database parameters using the modifyParameters command?

A: Use the --setParameters option followed by a comma-delimited list of parameters and their new values. For example:

--setParameters parameter1=valueA,parameter2=valueB

Q: How do I reset parameters to their default values using this command?

A: Use the --resetParameters option followed by a comma-delimited list of parameters to reset to their default values. For example:

--resetParameters parameter1,parameter2

Q: Can I modify parameters using a response file?

A: Yes, you can specify the absolute location of a response JSON file using the --responseFile option. The file should contain the parameters you want to modify.

Q: Is it necessary to take a backup before modifying parameters?

A: While not mandatory for all changes, if you are modifying critical or sensitive parameters, it’s recommended to have a backup in place. You can use the --backupPrepared option to acknowledge that a backup has been prepared.

Q: Can I apply changes only to a specific instance in a multi-instance database?

A: Yes, you can specify the instance name using the --instance option. If this option is not used, the changes will be applied at the database level.

Q: Will the database need to be bounced (restarted) after modifying parameters?

A: For some static parameters, a database bounce is required. You can use the --allowBounce option to grant permission for the database to bounce if necessary.

Q: What happens if I don’t allow the database to bounce when changing static parameters?

A: If you do not use the --allowBounce option when modifying static parameters, the changes will not take effect until the next manual database restart.

Q: Can I resume modifying parameters if an earlier session was interrupted?

A: No, this command does not support session resumption. You will need to re-run the command from the beginning.

Example: dbaascli database modifyParameters

dbaascli database modifyParameters --dbname dbname --setParameters "log_archive_dest_state_17=ENABLE"

dbaascli database recover

To recover a database, use the dbaascli database recover command.

Prerequisites:

Syntax:

dbaascli database recover --dbname <value>
        {
            --start
                {
                    --untilTime <value>
                    | --untilSCN <value>
                    | --latest
                }
            | --status --uuid <value>
        }

Parameters:

Parameter Attributes Description
--dbname - Oracle AI Database name.
--start | --status - -
--start - Begins database recovery.
--start --untilTime | --untilSCN | --latest -
--start --untilTime Recovers database until time. Input format: DD-MON-YYYY HH24:MI:SS.
--start --untilSCN Recovers database until SCN.
--start --latest Recovers database to last known state.
--status - -
--status --uuid <value> -

Frequently Asked Questions:

Q: What is the purpose of the dbaascli database recover command?

A: The dbaascli database recover command is used to recover an Oracle AI Database from backups stored in a backup storage destination.

Q: How do I specify which database to recover?

A: You can specify the database you want to recover using the --dbname option followed by the database name. For example:

--dbname <database_name>

Q: What are the recovery options available with the dbaascli database recover command?

A: The recovery options are:

Q: How do I recover the database to a specific time?

A: Use the --untilTime option followed by the time in the format DD-MON-YYYY HH24:MI:SS. For example:

--untilTime 05-SEP-2024 15:30:00

Q: How do I recover the database to a specific SCN?

A: Use the --untilSCN option followed by the SCN value. For example:

--untilSCN 123456789

Q: How can I recover the database to the latest known state?

A: Use the --latest option to recover the database to the most recent state possible. For example:

--latest

Q: How can I check the status of a recovery operation?

A: Use the --status option along with the --uuid value to check the status of an ongoing or previous recovery operation. For example:

--status --uuid <recovery_uuid>

Q: What does the –start option do in the recovery process?

A: The --start option initiates the recovery operation based on the selected recovery method (--untilTime, --untilSCN, --latest).

Q: Is there a way to recover the database without specifying a time or SCN?

A: Yes, you can recover the database to its last known state using the --latest option, which doesn’t require specifying a time or SCN.

Q: Can I perform a partial recovery?

A: Yes, you can recover the database to a specific point in time or SCN using the --untilTime or --untilSCN options, respectively.

Examples:

dbaascli database runDatapatch

To patch an Oracle AI Database, use the dbaascli database runDatapatch command.

Prerequisites:

Syntax:

dbaascli database runDatapatch --dbname
[--resume]
    [--sessionID]
[--skipPdbs | --pdbs]
[--executePrereqs]
[--patchList]
[--skipClosedPdbs]
[--rollback]

Parameters:

Parameter Description
--dbname specifies the name of the database
--resume resumes the previous run
--sessionID specifies to resume a specific session ID
--skipPdbs skips running the datapatch on a specified comma-delimited list of PDBs. For example: pdb1,pdb2,...
--pdbs runs the datapatch only on a specified comma-delimited list of PDBs. For example: pdb1,pdb2,...
--executePrereqs runs prerequisite checks
--patchList applies or rolls back the specified comma-delimited list of patches. For example: patch1,patch2,...
--skipClosedPdbs skips running the datapatch on closed PDBs
--rollback rolls back the patches applied

Frequently Asked Questions:

Q: What is the purpose of the dbaascli database runDatapatch command?

A: The dbaascli database runDatapatch command is used to apply patches to an Oracle AI Database.

Q: What must be ensured before running the dbaascli database runDatapatch command?

A: Before running the command, ensure that all instances of the database are up and running.

Q: How do I specify which database to patch?

A: Use the --dbname option followed by the name of the database. For example:

--dbname myDatabase

Q: How do I resume a previously interrupted runDatapatch operation?

A: Use the --resume option to resume the previous run or the --sessionID option to specify a specific session ID. For example:

--resume

--sessionID 12345

Q: How can I skip certain PDBs when running the patch?

A: Use the --skipPdbs option followed by a comma-delimited list of PDB names to skip. For example:

--skipPdbs pdb1,pdb2

Q: How can I run the patch only on certain PDBs?

A: Use the --pdbs option followed by a comma-delimited list of PDB names to include. For example:

--pdbs pdb1,pdb2

Q: How do I apply or roll back a specific set of patches?

A: Use the --patchList option followed by a comma-delimited list of patch names to apply or roll back. For example:

--patchList patch1,patch2

Q: What does the –rollback option do?

A: The --rollback option rolls back the patches that were applied during the patching operation.

Q: What happens if some PDBs are closed during the patching operation?

A: If some PDBs are closed, you can use the --skipClosedPdbs option to skip patching those closed PDBs.

Q: Can I run prerequisite checks before applying patches?

A: Yes, use the --executePrereqs option to run prerequisite checks before applying the patch.

Q: How do I find out which session ID to resume a patch?

A: After a runDatapatch operation, the session ID is typically logged. Use the --sessionID option to specify that ID when resuming a patch. For example:

--sessionID 67890

dbaascli database runDatapatch --dbname db19

dbaascli database start

To start an Oracle AI Database, use the dbaascli database start command.

Prerequisites:

Run the command as the root user.

Syntax:

dbaascli database start
[--dbname]
[--mode]

Parameters:

Parameter Description
--dbname specifies the name of the database
--mode specifies mount or nomount to start database in the corresponding mode

The command starts and opens the database. In Oracle Database 12c or later, all of the PDBs are also opened.

Frequently Asked Questions:

Q: What is the purpose of the dbaascli database start command?

A: The dbaascli database start command is used to start an Oracle AI Database.

Q: What must be done before running the dbaascli database start command?

A: The command must be run as the root user.

Q: How do I specify the database I want to start?

A: Use the --dbname option followed by the name of the database. For example:

--dbname myDatabase

Q: What are the possible modes in which I can start the database?

A: You can start the database in mount or nomount mode using the --mode option. For example:

--mode mount

Q: What is the default mode if I don’t specify one?

A: If you don’t specify a mode, the database will start in the default open mode.

Q: Will this command open all PDBs in Oracle Database 12c or later?

A: Yes, when starting the database in Oracle Database 12c or later, all pluggable databases (PDBs) will also be opened.

Q: How can I start a database in nomount mode?

A: Use the --mode option and set it to nomount. For example:

--mode nomount

Q: How can I start a database in mount mode?

A: Use the --mode option and set it to mount. For example:

--mode mount

Q: Is it mandatory to specify a database name when running the dbaascli database start command?

A: Yes, it is recommended to specify the database name using the --dbname option to ensure the correct database is started.

Example: dbaascli database start

dbaascli database start --dbname dbname --mode mount

dbaascli database stop

To stop an Oracle AI Database, use the dbaascli database stop command.

Prerequisites:

Run the command as the root user.

Syntax:

dbaascli database stop
[--dbname <value>]
[--mode <value>]

Parameters:

Parameter Description
--dbname specifies the name of the database that you want to stop
--mode specifies the mode of the database. Valid values: abort, immediate, normal, transactional

The command performs a database shutdown in immediate mode. No new connections or new transactions are permitted. Active transactions are rolled back, and all connected users are disconnected.

Frequently Asked Questions:

Q: What is the purpose of the dbaascli database stop command?

A: The dbaascli database stop command is used to stop an Oracle AI Database.

Q: What are the prerequisites for using the dbaascli database stop command?

A: You must run the command as the root user, and you must connect to an Oracle Base Database Cloud@Customer virtual machine using SSH.

Q: How do I specify which database to stop?

A: You can specify the database by using the --dbname option followed by the name of the database. For example:

--dbname myDatabase

Q: What are the valid shutdown modes for the dbaascli database stop command?

A: The valid shutdown modes are:

Q: What is the default shutdown mode if no mode is specified?

A: If no mode is specified, the database will be shut down in immediate mode by default.

Q: What happens in immediate shutdown mode?

A: In immediate mode, no new connections or transactions are permitted, active transactions are rolled back, and all connected users are disconnected.

Q: How can I stop the database in abort mode?

A: To stop the database in abort mode, use the --mode option with abort. For example:

--mode abort

Q: What does normal mode do when stopping the database?

A: In normal mode, the database allows current user sessions to complete and then stops without affecting active transactions.

Q: What is transactional mode used for in the dbaascli database stop command?

A: In transactional mode, the database stops only after all active transactions are completed, but no new transactions are allowed.

Q: Is it mandatory to specify the shutdown mode in the dbaascli database stop command?

A: No, specifying a shutdown mode is optional. If not provided, the default immediate mode will be used.

Example: dbaascli database stop

dbaascli database stop --dbname db19

dbaascli database upgrade

To upgrade an Oracle AI Database, use the dbaascli database upgrade command.

Prerequisites:

Run the command as the root user.

Syntax:

dbaascli database upgrade --dbname <value>
{--targetHome <value> | --targetHomeName <value>}
{ [--executePrereqs | --postUpgrade | --rollback]}
{[--standBy | --allStandbyPrepared]}
{[--upgradeOptions <value>]  | [--standBy]}
[--removeGRP]
[--increaseCompatibleParameter]
[--resume [--sessionID <value>]]
[--waitForCompletion <value>]

Parameters:

Parameter Attributes Description
--dbname - (mandatory) specifies the name of the database.
--targetHome - specifies the target Oracle home location
--targetHomeName - specifies the name of the target Oracle AI Database home
--standBy - use this option to upgrade standby databases in Data Guard configurations
--allStandbyPrepared - required for Data Guard configured primary databases. Flags to acknowledge that all the required operations are performed on the standby databases prior to upgrading primary database
--removeGRP - automatically removes the Guaranteed Restore Point (GRP) backup only if the database upgrade was successful
--increaseCompatibleParameter - automatically increases the compatible parameter as part of the database upgrade. The parameter will get increased only if the database upgrade was successful
--executePrereqs - runs only the preupgrade checks
--postUpgrade - use this option if postupgrade fails and needs to rerun the postupgrade steps
--rollback - reverts an Oracle AI Database to its original Oracle home
--upgradeOptions - use this option to pass DBUA-specific arguments to perform the Oracle AI Database upgrade. Refer to the corresponding Oracle documentation for the supported arguments and options.
--upgradeOptions --standby -
--resume - to resume the previous execution
--resume --sessionID to resume a specific session id.
--waitForCompletion - specify false to run the operation in background. Valid values: true or false.

Frequently Asked Questions:

Q: What is the purpose of the dbaascli database upgrade command?

A: The dbaascli database upgrade command is used to upgrade an Oracle AI Database to a new version.

Q: What are the prerequisites for using the dbaascli database upgrade command?

A: You must run the command as the root user and connect to an Oracle Base Database Cloud@Customer virtual machine using SSH.

Q: How do I specify the database that needs to be upgraded?

A: Use the --dbname option followed by the name of the database. For example:

--dbname myDatabase

Q: How can I specify the target Oracle home for the upgrade?

A: You can specify the target Oracle home location with the --targetHome option or the name of the target Oracle AI Database home with the --targetHomeName option.

Q: What does the –standBy option do?

A: The --standBy option is used to upgrade standby databases in Data Guard configurations.

Q: What is the purpose of the –allStandbyPrepared flag?

A: The --allStandbyPrepared flag acknowledges that all required operations on standby databases have been performed before upgrading the primary database in a Data Guard configuration.

Q: What does the –removeGRP option do?

A: The --removeGRP option automatically removes the Guaranteed Restore Point (GRP) backup if the database upgrade is successful.

Q: When should I use the –increaseCompatibleParameter option?

A: Use the --increaseCompatibleParameter option to automatically increase the compatible parameter during the database upgrade, provided the upgrade is successful.

Q: What does the –executePrereqs option do?

A: The --executePrereqs option runs only the pre-upgrade checks to ensure that the database is ready for the upgrade.

Q: How do I handle a failed post-upgrade step?

A: Use the --postUpgrade option to rerun the post-upgrade steps if the initial post-upgrade attempt fails.

Q: What is the purpose of the –revert option?

A: The --revert option reverts the Oracle AI Database to its original Oracle home, undoing the upgrade.

Q: How can I pass additional arguments specific to DBUA for the upgrade?

A: Use the --upgradeOptions option to pass DBUA-specific arguments for the Oracle AI Database upgrade. Refer to the Oracle documentation for supported arguments and options.

Q: Is it mandatory to specify the target Oracle home for the upgrade?

A: Yes, you must specify either the --targetHome or --targetHomeName to indicate the target Oracle home for the upgrade.

Q: What should I do if I need to perform a pre-upgrade check but not proceed with the upgrade?

A: Use the --executePrereqs option to perform only the pre-upgrade checks without proceeding with the actual upgrade.

Example: dbaascli database upgrade pre-upgrade requisite checks

dbaascli database upgrade --dbname dbname --targetHome Target Oracle home location --executePrereqs

dbaascli database move

To move the database from one home to another, use the dbaascli database move command.

Prerequisites:

Syntax:

dbaascli database move
{
  --oracleHome <value> | --oracleHomeName <value>
}
--dbname <value>
[--executePrereqs]
[--resume [--sessionID <value>]]
[--rollback [--sessionID <value>]]
[--skipDatapatch]
[--skipPDBs <value>]
[--skipClosedPDBs]
[--continueWithDbDowntime]
[--allowParallelDBMove]
[--waitForCompletion <value>]
[--nodeList <value>]

Parameters:

Parameter Description
--oracleHome specifies Oracle home path
--oracleHomeName specifies the name of Oracle home
--dbname specifies the name of the database
--executePrereqs runs the prerequisite checks and report the results
--resume resumes the previous run
--sessionID specifies to resume a specific session ID
--rollback rolls the database back to previous home
--sessionID specifies to resume a specific session ID
--skipDatapatch skips running the datapatch on the databases
--skipPdbs skips running the datapatch on a specified comma-delimited list of PDBs. For example: pdb1,pdb2,...
--skipClosedPDBs skips patching closed PDBs
--continueWithDbDowntime continues patching with database downtime. This option can be used in environments wherein there is only one active instance up and the patching operation can be continued even with a downtime.
--allowParallelDBMove allows database move in parallel.
--waitForCompletion specifies false to run the operation in the background. Valid values: true or false
--nodeList specifies a comma-delimited list of nodes if operation has to be performed on a subset of nodes

Frequently Asked Questions:

Q: What is the dbaascli database move command used for?

A: The dbaascli database move command is used to move a database from one Oracle home to another.

Q: What are the prerequisites for using the dbaascli database move command?

A: Before performing a move operation, ensure that all database instances associated with the database are up and running. Additionally, the command must be run as the root user.

Q: What does the –oracleHome parameter specify?

A: The --oracleHome parameter specifies the path of the Oracle home to which the database will be moved.

Q: What does the –oracleHomeName parameter specify?

A: The --oracleHomeName parameter specifies the name of the Oracle home to which the database will be moved.

Q: What is the purpose of the –dbname parameter?

A: The --dbname parameter specifies the name of the database that you want to move.

Q: What does the –executePrereqs option do?

A: The --executePrereqs option runs the prerequisite checks and reports the results.

Q: What is the –resume option used for?

A: The --resume option resumes a previously interrupted or incomplete move operation.

Q: How is –sessionID used in the command?

A: The --sessionID specifies the session ID to resume a previous run or rollback.

Q: What does the –rollback option do?

A: The --rollback option rolls the database back to its previous Oracle home.

Q: What does the –skipDatapatch option do?

A: The --skipDatapatch option skips running the datapatch on the databases during the move operation.

Q: What is the function of the –skipPDBs option?

A: The --skipPDBs option skips running the datapatch on a specified comma-delimited list of PDBs (e.g., pdb1, pdb2).

Q: What does the –skipClosedPDBs option do?

A: The --skipClosedPDBs option skips patching of closed PDBs.

Q: What does –continueWithDbDowntime mean?

A: The --continueWithDbDowntime option allows the move operation to proceed even if there is only one active instance up, allowing for downtime during the process.

Q: What is the purpose of the –allowParallelDBMove option?

A: The --allowParallelDBMove option allows the database move to be performed in parallel, potentially speeding up the process.

Q: What does –waitForCompletion specify?

A: The --waitForCompletion option specifies whether to wait for the operation to complete. Setting it to false runs the operation in the background.

Q: How do I use the –nodeList parameter?

A: The --nodeList parameter specifies a comma-delimited list of nodes on which the move operation will be performed, if it is not to be applied to all nodes.

Q: What should I do if I encounter issues with the dbaascli database move command?

A: Ensure all database instances are running and verify that you are running the command as the root user. If issues persist, consult the detailed command documentation or open a support ticket with Oracle.

Q: Can I perform a move operation if one of the database instances is down?

A: No, all associated database instances must be up and running before performing the move operation.

Q: What happens if the move operation is interrupted?

A: You can use the --resume option to continue the move operation from where it left off by using the same session or specifying the --sessionID.

Q: What does the –allowParallelDBMove option do?

A: It enables the database move to be performed in parallel, which can reduce the time it takes to complete the operation, especially on larger environments.

Q: How do I monitor the progress of a move operation that is running in the background?

A: When using --waitForCompletion false, the command does not wait for the operation to complete. You can check the status of the operation manually using appropriate Oracle logs or status commands.

Q: What is the significance of the –skipClosedPDBs option?

A: It skips patching for PDBs that are closed, reducing the operation time if there are PDBs that don’t need to be patched.

Q: Can the database move be rolled back at any time?

A: Yes, the move operation can be rolled back using the --rollback option, either by specifying the session ID or simply rolling back to the previous Oracle home.

Q: What is the role of –nodeList in a multi-node environment?

A: In a multi-node environment, you can restrict the move operation to specific nodes by providing a comma-delimited list of node names with --nodeList.

Q: Can I move the database to a new Oracle home while skipping specific nodes in a multi-node environment?

A: Yes, you can use the --nodeList option to specify which nodes to include in the move operation. Any nodes not listed will be skipped.

Q: What is the maximum number of nodes I can specify with the –nodeList parameter?

A: The --nodeList parameter allows you to specify a comma-delimited list of as many nodes as needed, limited only by your environment configuration. Ensure all nodes are valid and reachable.

Q: How do I know which PDBs are closed before using the –skipClosedPDBs option?

A: You can query the v$pdbs view to check the status of your PDBs. Any PDBs with a status of “MOUNTED” or “CLOSED” will be skipped when using --skipClosedPDBs.

Q: How do I verify if a rollback has completed successfully?

A: After running the rollback command, you can review the database logs or use the Oracle alert logs to verify that the database has been successfully rolled back to its previous Oracle home.

Q: Is there a way to force the move operation if some prerequisites fail?

A: The move command enforces prerequisite checks for system stability. You cannot bypass critical prerequisite failures. Address any issues reported by the --executePrereqs option before proceeding with the move.

Examples:

Example: Basic Database Move by Oracle Home Path

dbaascli database move --oracleHome /u01/app/oracle/product/19.0.0/dbhome_1 --dbname ORCL

Moves the database ORCL to the Oracle home located at /u01/app/oracle/product/19.0.0/dbhome_1.

Example: Database Move by Oracle Home Name

dbaascli database move --oracleHomeName DB_HOME_NAME --dbname ORCL

Moves the database ORCL to the Oracle home named DB_HOME_NAME.

Example: Running Prerequisite Checks Before Moving

dbaascli database move --oracleHome /u01/app/oracle/product/19.0.0/dbhome_1 --dbname ORCL --executePrereqs

Moves the database ORCL to the Oracle home while running the prerequisite checks beforehand.

Example: Resuming a Previous Move Operation

dbaascli database move --oracleHome /u01/app/oracle/product/19.0.0/dbhome_1 --dbname ORCL --resume

Resumes a previous move operation for the ORCL database.

Example: Resuming a Move Operation with a Specific Session ID

dbaascli database move --oracleHomeName DB_HOME_NAME --dbname ORCL --resume --sessionID 12345

Resumes the move operation for the ORCL database using session ID 12345.

Example: Rolling Back a Move Operation

dbaascli database move --oracleHome /u01/app/oracle/product/19.0.0/dbhome_1 --dbname ORCL --rollback

Rolls back the move operation for the ORCL database, restoring it to the previous Oracle home.

Example: Rolling Back a Move Operation with a Session ID

dbaascli database move --oracleHomeName DB_HOME_NAME --dbname ORCL --rollback --sessionID 67890

Rolls back the move operation for ORCL using session ID 67890.

Example: Skipping Datapatch

dbaascli database move --oracleHome /u01/app/oracle/product/19.0.0/dbhome_1 --dbname ORCL --skipDatapatch

Moves the database ORCL without running datapatch on the databases.

Example: Skipping Specific PDBs During Datapatch

dbaascli database move --oracleHome /u01/app/oracle/product/19.0.0/dbhome_1 --dbname ORCL --skipPDBs pdb1,pdb2

Moves the ORCL database to a new Oracle home but skips running datapatch on the specified PDBs (pdb1 and pdb2).

Example: Skipping Datapatch on Closed PDBs

dbaascli database move --oracleHome /u01/app/oracle/product/19.0.0/dbhome_1 --dbname ORCL --skipClosedPDBs

Moves the ORCL database and skips running datapatch on any closed PDBs.

Example: Allowing Database Downtime During Move

dbaascli database move --oracleHomeName DB_HOME_NAME --dbname ORCL --continueWithDbDowntime

Moves the ORCL database to the specified Oracle home while allowing downtime of the database during the move process.

Example: Moving Database in Parallel

dbaascli database move --oracleHome /u01/app/oracle/product/19.0.0/dbhome_1 --dbname ORCL --allowParallelDBMove

Moves the database ORCL to the specified Oracle home with the option to run the move in parallel for better performance.

Example: Running the Operation in the Background

dbaascli database move --oracleHome /u01/app/oracle/product/19.0.0/dbhome_1 --dbname ORCL --waitForCompletion false

Moves the database ORCL to a new Oracle home but runs the operation in the background.

Example: Specifying Nodes for the Move

dbaascli database move --oracleHome /u01/app/oracle/product/19.0.0/dbhome_1 --dbname ORCL --nodeList node1,node2

Moves the database ORCL to the specified Oracle home but performs the operation only on node1 and node2.

Example: Combination of Move with Prerequisite Checks, Skipping Specific PDBs, and Allowing Downtime

dbaascli database move --oracleHomeName DB_HOME_NAME --dbname ORCL --executePrereqs --skipPDBs pdb1 --continueWithDbDowntime

Moves the ORCL database to the specified Oracle home, runs prerequisite checks, skips running datapatch on pdb1, and allows database downtime during the operation.

Example: Combination of Move in Parallel and Running in the Background

dbaascli database move --oracleHome /u01/app/oracle/product/19.0.0/dbhome_1 --dbname ORCL --allowParallelDBMove --waitForCompletion false

Moves the ORCL database to a new Oracle home, runs the move in parallel, and executes the operation in the background.

Example: Combining Move with Parallel Execution and Skipping Closed PDBs

dbaascli database move --oracleHome /u02/app/oracle/product/19.0.0/dbhome_2 --dbname TESTDB --allowParallelDBMove --skipClosedPDBs

Moves the TESTDB database to the new Oracle home /u02/app/oracle/product/19.0.0/dbhome_2, while running the operation in parallel and skipping datapatch on closed PDBs.

Example: Running Prerequisites Check Only

dbaascli database move --oracleHome /u02/app/oracle/product/19.0.0/dbhome_2 --dbname PRODDB --executePrereqs

Checks the prerequisites for moving the PRODDB database to the Oracle home located at /u02/app/oracle/product/19.0.0/dbhome_2 without actually performing the move.

Example: Skipping Datapatch for Specific PDBs

dbaascli database move --oracleHome /u02/app/oracle/product/19.0.0/dbhome_2 --dbname HRDB --skipPDBs pdb1,pdb3

Moves the HRDB database to the new Oracle home, but skips running datapatch for pdb1 and pdb3.

Example: Running the Move on Specific Nodes

dbaascli database move --oracleHome /u02/app/oracle/product/19.0.0/dbhome_2 --dbname FINDB --nodeList node1,node3

Moves the FINDB database to the new Oracle home only on node1 and node3.

Example: Database Move with Downtime Allowed

dbaascli database move --oracleHome /u01/app/oracle/product/19.0.0/dbhome_1 --dbname ORCL --continueWithDbDowntime

Moves the ORCL database to the specified Oracle home while allowing downtime during the move operation.

Example: Combination of Parallel Move and Skipping Datapatch

dbaascli database move --oracleHome /u02/app/oracle/product/19.0.0/dbhome_2 --dbname CRMDB --allowParallelDBMove --skipDatapatch

Moves the CRMDB database in parallel, skipping the datapatch process.

Example: Move Operation in Background with a Node List

dbaascli database move --oracleHome /u02/app/oracle/product/19.0.0/dbhome_2 --dbname SALESDB --waitForCompletion false --nodeList node2,node3

Moves the SALESDB database to the specified Oracle home in the background, and the operation is applied only on node2 and node3.

Example: Database Move with Prerequisite Check and Allowing Parallel Move

dbaascli database move --oracleHome /u01/app/oracle/product/19.0.0/dbhome_2 --dbname ORCL --executePrereqs --allowParallelDBMove

Moves the ORCL database to the new Oracle home after performing the prerequisite checks and running the move operation in parallel.

Example: Rolling Back a Move Operation and Skipping Closed PDBs

dbaascli database move --oracleHome /u02/app/oracle/product/19.0.0/dbhome_2 --dbname DEVDB --rollback --skipClosedPDBs

Rolls back the move operation for the DEVDB database, skipping any closed PDBs.

Example: Moving the Database with Specific Downtime and Parallel Execution

dbaascli database move --oracleHome /u02/app/oracle/product/19.0.0/dbhome_2 --dbname FINDB --allowParallelDBMove --continueWithDbDowntime

Moves the FINDB database to the specified Oracle home while allowing database downtime and enabling parallel execution to speed up the process.

Example: Checking Database Move Prerequisites without Executing the Move

dbaascli database move --oracleHome /u01/app/oracle/product/19.0.0/dbhome_1 --dbname HRDB --executePrereqs

Runs prerequisite checks to validate that the HRDB database can be moved to the specified Oracle home without executing the move itself.

Example: Moving Database and Running the Command in the Background on Specific Nodes

dbaascli database move --oracleHome /u02/app/oracle/product/19.0.0/dbhome_3 --dbname PRODDB --waitForCompletion false --nodeList node1,node4

Moves the PRODDB database to a new Oracle home, executing the operation in the background, and applying it only on node1 and node4.

Example: Combining Prerequisite Checks, Skipping Closed PDBs, and Allowing Parallel Execution

dbaascli database move --oracleHome /u02/app/oracle/product/19.0.0/dbhome_2 --dbname CRMDB --executePrereqs --skipClosedPDBs --allowParallelDBMove

Performs prerequisite checks before moving the CRMDB database to the new Oracle home, skips patching closed PDBs, and allows the operation to run in parallel for faster execution.

Example: Database Move with Rollback on Specific Session ID and Skipping Datapatch

dbaascli database move --oracleHomeName DB_HOME_NAME --dbname DEVDB --rollback --sessionID 45678 --skipDatapatch

Rolls back a previously executed move operation for the DEVDB database to its prior Oracle home using session ID 45678, skipping the datapatch process during the rollback.

Example: Moving Database with Allow Parallel Execution and Specifying Datapatch Skipping for PDBs

dbaascli database move --oracleHome /u02/app/oracle/product/19.0.0/dbhome_3 --dbname ANALYTICDB --allowParallelDBMove --skipPDBs pdb2,pdb4

Moves the ANALYTICDB database in parallel to the specified Oracle home and skips the datapatch process for pdb2 and pdb4.