In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-16 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >
Share
Shulou(Shulou.com)06/01 Report--
one
SQL > recover database
This command is used to restore all data files and can only use archived logs and online logs saved on the file system. The premise of using such commands is that the control file cannot be restored or rebuilt.
SQL > recover database until sequence XX;--SQL is not written in this way, it will make an error ORA-00277: illegal option to the UNTIL recovery flag SEQUENCE
two
SQL > recover database using backup controlfile
This command is used to recover all data files and control files, and can only use archived logs and online logs saved on the file system.
three
RMAN > recover database
This command is used to restore all data files and control files, using incremental backups, archive logs in backups and on the file system, and online logs on the file system
The difference among three prompts about Specify log: {= suggested | filename | AUTO | CANCEL}
RMAN will not have such a prompt, so RMAN > recover database until cancel will report an error
SQL > recover database until cancel; will bring out the following Specify log: {= suggested | filename | AUTO | CANCEL} information
SQL > recover database using backup controlfile; automatically brings out Specify log: {= suggested | filename | AUTO | CANCEL} information
Enter filename to enter a specific archive log for recover (when the current redo log is lost, filename is the path of the corresponding current redo log). In case 85 below, the prompt is displayed as archive log, but current redo log, so enter / db/oracle/oradata/PROD1/redo01.log
Enter AUTO to indicate active recover until the last archive log
SQL > recover database until cancel
ORA-00279: change 2292679 generated at 07/31/2017 14:26:21 needed for thread 1
ORA-00289: suggestion:
/ db/oracle/fast_recovery_area/PROD1/archivelog/2017_07_31/o1_mf_1_85_%u_.arc
ORA-00280: change 2292679 for thread 1 is in sequence # 85
Specify log: {= suggested | filename | AUTO | CANCEL}
/ db/oracle/oradata/PROD1/redo01.log
ORA-00308: cannot open archived log' / db/oracle/oradata/PROD1/redo01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Specify log: {= suggested | filename | AUTO | CANCEL}
AUTO
ORA-00308: cannot open archived log
'/ db/oracle/fast_recovery_area/PROD1/archivelog/2017_07_31/o1_mf_1_85_%u_.arc'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.