This example shows how you can set up a standby instance with the Database Manager CLI and activate it.
For detailed information about working with the Database Manager CLI and the meaning of the individual DBM commands, see the documentation for the Database Manager CLI.
You have created a database instance that you can use as a standby instance.
...
1. Transfer the standby instance to the ADMIN operational state:
db_offline
db_admin
2. Create a backup medium in the standby instance for importing the complete data backup from the original instance:
medium_put <medium_name_data> <path_data> <medium_type> DATA
3. Initialize the existing standby instance and import the last data backup from the original instance:
db_connect
db_activate RECOVER <medium_name_data>
4. Create a backup medium in the standby instance for importing the log backups from the original instance:
medium_put <medium_name_log> <path_log>\save.log FILE LOG
5. Identify the log backups to be imported (see Identifying Log Backups Since the Last Savepoint).
¡ Display the restart record for the standby instance:
db_restartinfo
¡ Log on to the original instance and display the log history (in a new command window):
dbmcli -d <database_name> -u <dbm_user,
dbm_user_password>
backup_history_open
backup_history_list
backup_history_close
6. Import the log backups:
db_offline
db_admin
db_connect
recover_start <medium_name_log> LOG 001
recover_replace <medium_name_log> <path_log>\save.log 002
recover_replace <medium_name_log> <path_log>\save.log 003
...
7. Activate the standby instance (cancel the import of the log backups and transfer the standby instance to the ONLINE operational state):
recover_ignore
Instead of the recover_ignore command, you can also use the recover_cancel command. If necessary, cancel importing the log backups, and transfer the standby instance to the OFFLINE operational state. To enter additional commands, transfer the standby instance to the ADMIN operational state again using the db_admin command.