Restoring System and Database Configuration Files
You can
use the download_cfg command of the bkup_api utility to
restore system and database configuration files from an automatic database
backup.
-
Connect to the compute node as the
opcuser.For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).
-
Start a root-user command shell:
$ sudo -s # -
Use the
download_cfgsubcommand to retrieve the system and database configuration files from an automatic database backup:# /var/opt/oracle/bkup_api/bkup_api download_cfg --dbname=dbnamewhere
dbnamespecifies the database name for the database that is associated with the backup.By default, the system and database configuration files are retrieved from the most recent backup. If you would like to specify differently, you can add one of the following options:
-
Use
--date=backupdateto identify a specific backup date that you want to retrieve the system and database configuration files from. The expected format forbackupdateisMM/DD/YYYY. -
Use
--file=filenameto identify a specific backup file containing system or database configuration files. Thefilenamethat you specify must be the complete name for the file as shown in the object store.
You can view a list of system and database configuration file backups by using the following command:
# /var/opt/oracle/bkup_api/bkup_api list_cfgfiles --dbname=dbnameYou can use the output from this command to identify a specific
backupdateorfilenameto target for retrieval.By default, the compressed tar files that contain the system and database configuration files are downloaded to
/var/opt/oracle/log/dbname/cfgfiles. To specify a different location where you would like to download the system and database configuration files, add the--location=locationoption. -
-
After you retrieve the system and database configuration files from an automatic database backup, you must manually extract the required files from the compressed tar files and copy them to their original locations.
-
Exit the root-user command shell and disconnect from the compute node:
# exit $ exit