Create Database from existing database backup
Note:
This command is applicable only to ExaDB-D.
Create Database from existing database backup.
The create_db_frombackup command supports the following options:
Syntax
exacloudmigration create_db_frombackup [-ahV] -i <inputFile> [-w <walletFile>] [-a|-l <dbNames>] [--dry-run]Table 2-37 exacloudmigration create_db_frombackup Commands
| Command | Description |
|---|---|
-a, --all |
Creates new databases from the backups of all existing databases. |
-i, --inputFile |
Specifies the database input file name with complete path. |
-l, --dbNames |
Specifies a comma-delimited list of databases to create databases from the existing backup.
Examples:
|
-w, --walletFile |
Specifies the wallet file name with the path. |
--dry-run |
Performs dry run without creating databases. |
-h, --help |
Displays help information about the command and its options. |
-V, --version |
Displays the version of the utility. |
Examples:
- To validate the database input template file and perform a
--dry-run:/home/opc>./exacloudmigration create_db_frombackup -a -i inputs/infra_phxref/vmcluster_vmcluster1/database_inputs -w ewallet.p12 --dry-run - To validate a comma-delimited list of dbnames to verify the database input template file and perform a
--dry-run:/home/opc>./exacloudmigration create_db_frombackup -i inputs/infra_phxref/vmcluster_vmcluster1/database_inputs -l dbname1,dbname2 -w ewallet.p12 --dry-run - To create databases from the existing backups, following successful validation and dry run:
/home/opc>./exacloudmigration create_db_frombackup -a -i inputs/infra_phxref/vmcluster_vmcluster1/database_inputs -w ewallet.p12 - To create databases from the existing backups for a comma-delimited list of databases, following successful validation and dry run:
/home/opc>./exacloudmigration create_db_frombackup -i inputs/infra_phxref/vmcluster_vmcluster1/database_inputs -l dbname1,dbname2 -w ewallet.p12
Note:
- If the database wallet file is not used, the command prompts for the SYS and TDE passwords for each database.
- If the database wallet file is used, but a password entry for any database is missing, the utility stops execution and displays an error indicating that the password does not exist in the wallet.
- All the PDBs will be restored.
- If the source database is created using Customer-Managed Keys, creating the database requires only the SYS password for the new database.
- If the source database is created using Oracle-Managed Keys, creating the database requires two passwords: the TDE password and the SYS password for the new database. By default, the utility uses the password stored in the wallet for both.
- If the TDE password and the new database SYS password need to be different, the recommended approach is to create the new database using the same password and then update the SYS password of the database afterward.