这篇文章主要介绍RMAN如何恢复drop purge的表,文中介绍的非常详细,具有一定的参考价值,感兴趣的小伙伴们一定要看完!@ORA12C> alter s
这篇文章主要介绍RMAN如何恢复drop purge的表,文中介绍的非常详细,具有一定的参考价值,感兴趣的小伙伴们一定要看完!
@ORA12C> alter session set nls_date_fORMat='yyyy-mm-dd hh34:mi:ss';
Session altered.
SYS@ORA12C> create table t_0920 as select * from dba_objects;
Table created.
SYS@ORA12C> select count(*) from t_0920;
COUNT(*)
-----------------
91691
1 row selected.
SYS@ORA12C> select sysdate from dual;
SYSDATE
-------------------
2015-09-20 14:17:49
1 row selected.
SYS@ORA12C> drop table t_0920 purge;
Table dropped.
SYS@ORA12C> desc t_0920;
ERROR:
ORA-04043: object t_0920 does not exist
SYS@ORA12C> create table t_09201 as select * from dba_objects;
Table created.
SYS@ORA12C> select count(*) from t_09201;
COUNT(*)
-----------------
91691
1 row selected.
SYS@ORA12C> shutdown immediate;
Database closed.
Database dismounted.
oracle instance shut down.
SYS@ORA12C> startup mount;
ORACLE instance started.
Total System Global Area 729808896 bytes
Fixed Size 2928680 bytes
Variable Size 570429400 bytes
Database Buffers 150994944 bytes
Redo Buffers 5455872 bytes
Database mounted.
现在需要把t_0920表恢复过来:
run{
sql "alter session set nls_date_format=''yyyy-mm-dd hh34:mi:ss''";
set until time '2015-09-20 14:17:49';
restore database;
recover database;
6> }
using target database control file instead of recovery catalog
sql statement: alter session set nls_date_format=''yyyy-mm-dd hh34:mi:ss''
executing command: SET until clause
Starting restore at 20-SEP-15
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=355 device type=DISK
creating datafile file number=2 name=/u01/app/oracle/oradata/ORA12C/t2.dbf
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/ORA12C/system01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/ORA12C/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/ORA12C/undotbs01.dbf
channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/ORA12C/example01.dbf
channel ORA_DISK_1: restoring datafile 00006 to /u01/app/oracle/oradata/ORA12C/users01.dbf
channel ORA_DISK_1: reading from backup piece /u01/app/oracle/fast_recovery_area/ORA12C/backupset/2015_09_20/o1_mf_nnndf_TAG20150920T120820_bzwd9ntd_.bkp
channel ORA_DISK_1: piece handle=/u01/app/oracle/fast_recovery_area/ORA12C/backupset/2015_09_20/o1_mf_nnndf_TAG20150920T120820_bzwd9ntd_.bkp tag=TAG20150920T120820
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:56
Finished restore at 20-SEP-15
Starting recover at 20-SEP-15
using channel ORA_DISK_1
starting media recovery
arcHived log for thread 1 with sequence 18 is already on disk as file /u01/app/oracle/fast_recovery_area/ORA12C/archivelog/2015_09_20/o1_mf_1_18_bzwh058r_.arc
archived log for thread 1 with sequence 19 is already on disk as file /u01/app/oracle/fast_recovery_area/ORA12C/archivelog/2015_09_20/o1_mf_1_19_bzwhh60d_.arc
archived log for thread 1 with sequence 20 is already on disk as file /u01/app/oracle/fast_recovery_area/ORA12C/archivelog/2015_09_20/o1_mf_1_20_bzwhzsts_.arc
archived log for thread 1 with sequence 1 is already on disk as file /u01/app/oracle/fast_recovery_area/ORA12C/archivelog/2015_09_20/o1_mf_1_1_bzwmprks_.arc
archived log file name=/u01/app/oracle/fast_recovery_area/ORA12C/archivelog/2015_09_20/o1_mf_1_18_bzwh058r_.arc thread=1 sequence=18
archived log file name=/u01/app/oracle/fast_recovery_area/ORA12C/archivelog/2015_09_20/o1_mf_1_19_bzwhh60d_.arc thread=1 sequence=19
archived log file name=/u01/app/oracle/fast_recovery_area/ORA12C/archivelog/2015_09_20/o1_mf_1_20_bzwhzsts_.arc thread=1 sequence=20
archived log file name=/u01/app/oracle/fast_recovery_area/ORA12C/archivelog/2015_09_20/o1_mf_1_1_bzwm5k1c_.arc thread=1 sequence=1
archived log file name=/u01/app/oracle/fast_recovery_area/ORA12C/archivelog/2015_09_20/o1_mf_1_1_bzwmprks_.arc thread=1 sequence=1
media recovery complete, elapsed time: 00:00:07
Finished recover at 20-SEP-15
RMAN> alter database open resetlogs;
Statement processed
验证:t_0920 表已经恢复了,t_09201表不存在了。
SYS@ORA12C> select count(*) from t_0920;
COUNT(*)
-----------------
91691
1 row selected.
SYS@ORA12C> select count(*) from t_09201;
select count(*) from t_09201
*
ERROR at line 1:
ORA-00942: table or view does not exist
以上是“RMAN如何恢复drop purge的表”这篇文章的所有内容,感谢各位的阅读!希望分享的内容对大家有帮助,更多相关知识,欢迎关注编程网数据库频道!
--结束END--
本文标题: RMAN如何恢复drop purge的表
本文链接: https://www.lsjlt.com/news/65359.html(转载时请注明来源链接)
有问题或投稿请发送至: 邮箱/279061341@qq.com QQ/279061341
下载Word文档到电脑,方便收藏和打印~
2024-05-22
2024-05-22
2024-05-22
2024-05-22
2024-05-22
2024-05-22
2024-05-22
2024-05-21
2024-05-21
2024-05-21
回答
回答
回答
回答
回答
回答
回答
回答
回答
回答
一口价域名售卖能注册吗?域名是网站的标识,简短且易于记忆,为在线用户提供了访问我们网站的简单路径。一口价是在域名交易中一种常见的模式,而这种通常是针对已经被注册的域名转售给其他人的一种方式。
一口价域名买卖的过程通常包括以下几个步骤:
1.寻找:买家需要在域名售卖平台上找到心仪的一口价域名。平台通常会为每个可售的域名提供详细的描述,包括价格、年龄、流
443px" 443px) https://www.west.cn/docs/wp-content/uploads/2024/04/SEO图片294.jpg https://www.west.cn/docs/wp-content/uploads/2024/04/SEO图片294-768x413.jpg 域名售卖 域名一口价售卖 游戏音频 赋值/切片 框架优势 评估指南 项目规模
0