and a list of the media used. For detailed syntax of the omnidb command, see
its man page.
• Ensure that the database is in the correct state.
If you are trying to restore a database item using the Data Protector GUI and the
GUI hangs try one of the following:
• If you are restoring the control file, the database should be in the NoMount
state.
Open a command window and enter the following:
sqlplus/nolog
SQL>connect user/password@service as sysdba
SQL>shutdown immediate
SQL>startup nomount
• If you are restoring datafiles, the database should be in the Mount state.
Open a command window and enter the following:
sqlplus/nolog
SQL>connect user/password@service as sysdba
SQL>shutdown immediate
SQL>startup mount
• If there is a problem you cannot resolve while you are trying to restore a database
item using the Data Protector GUI, try using the RMAN CLI to restore the database
items.
For information, see “Restoring Oracle using RMAN” on page 123.
• Try putting the database into the Open state manually after using the Data Protector
GUI to recover and restore a backup session.
If you have used the Data Protector GUI to recover and restore a backup session
and you see the following error message:
Oracle Error: ORA-1589: must use RESETLOGS or NORESETLOGS
option for database open.
Open a SQLplus window and use the following command:
sqlplus/nolog
SQL>connect user/password@service as sysdba
SQL>alter database open noresetlogs;
If this does not work, try using the following command:
SQL>alter database open resetlogs;
Zero downtime backup integration guide 153
To Next Page
Loading...
Need help?
General