1. 程式人生 > >12C-PDB基於時間點恢復

12C-PDB基於時間點恢復

RMAN>alter  pluggable database zaki1 close immediate;

RMAN> run{

2> set until time "TO_DATE('2016-10-31 12:03:08','yyyy-mm-dd hh24:mi:ss')";
3> restore pluggable database zaki1;
4> recover pluggable database zaki1 ;
5> }
executing command: SET until clause
Starting restore at 31-OCT-16
using channel ORA_DISK_1

skipping datafile 9; already restored to file /oracle/db/oradata/orcl/zaki1/zaki1_users01.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 00007 to /oracle/db/oradata/orcl/zaki1/system01.dbf
channel ORA_DISK_1: restoring datafile 00008 to /oracle/db/oradata/orcl/zaki1/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00018 to /oracle/db/oradata/orcl/zaki1/gdb_data02.dbf
channel ORA_DISK_1: reading from backup piece /app/backup/zaki1_02rjglc9_1_120161028
channel ORA_DISK_1: piece handle=/app/backup/zaki1_02rjglc9_1_120161028 tag=TAG20161028T160437
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:45
Finished restore at 31-OCT-16

Starting recover at 31-OCT-16
using channel ORA_DISK_1
RMAN-05026: WARNING: presuming following set of tablespaces applies to specified Point-in-Time

List of tablespaces expected to have UNDO segments
Tablespace SYSTEM
Tablespace UNDOTBS1

Creating automatic instance, with SID='vsfu'

initialization parameters used for automatic instance:
db_name=ORCL
db_unique_name=vsfu_pitr_zaki1_ORCL
compatible=12.1.0.2.0
db_block_size=8192
db_files=200
diagnostic_dest=/oracle/db
_system_trig_enabled=FALSE
sga_target=2352M
processes=200
#No auxiliary destination in use
enable_pluggable_database=true
_clone_one_pdb_recovery=true
control_files=/oracle/db/fast_recovery_area/ORCL/controlfile/o1_mf_d1fmv34p_.ctl
#No auxiliary parameter file used

starting up automatic instance ORCL

Oracle instance started

Total System Global Area    2466250752 bytes

Fixed Size                     2927384 bytes
Variable Size                553649384 bytes
Database Buffers            1895825408 bytes
Redo Buffers                  13848576 bytes
Automatic instance created

contents of Memory Script:
{
# set requested point in time
set until  time "TO_DATE('2016-10-31 12:03:08','yyyy-mm-dd hh24:mi:ss')";
# restore the controlfile
restore clone controlfile;
 
# mount the controlfile
sql clone 'alter database mount clone database';
}
executing Memory Script

executing command: SET until clause

Starting restore at 31-OCT-16
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=12 device type=DISK

channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /oracle/db/fast_recovery_area/ORCL/autobackup/2016_10_28/o1_mf_s_926440264_d16369h7_.bkp
channel ORA_AUX_DISK_1: piece handle=/oracle/db/fast_recovery_area/ORCL/autobackup/2016_10_28/o1_mf_s_926440264_d16369h7_.bkp tag=TAG20161028T163104
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/oracle/db/fast_recovery_area/ORCL/controlfile/o1_mf_d1fmv34p_.ctl
Finished restore at 31-OCT-16

sql statement: alter database mount clone database

Removing automatic instance
shutting down automatic instance 
Oracle instance shut down
Automatic instance removed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 10/31/2016 12:58:59
ORA-19809: limit exceeded for recovery files

ORA-19804: cannot reclaim 10737418240 bytes disk space from 5048893440 limit 

--進行recover操作時會啟動輔助例項,輔助例項則會使用到fast recovery area,如果fast recovery area的空間不夠了,recover時會報錯。後來手動使用AUXILIARY DESTINATION子句來為輔助例項指定一個臨時的位置,就沒有問題了。

RMAN> 

RMAN> run{
2>  set until time "TO_DATE('2016-10-31 12:03:08','yyyy-mm-dd hh24:mi:ss')";
3>  restore pluggable database zaki1;
4>  recover pluggable database zaki1 auxiliary destination '/app/backup/tmp';
5>  }

executing command: SET until clause

Starting restore at 31-OCT-16
using channel ORA_DISK_1

skipping datafile 7; already restored to file /oracle/db/oradata/orcl/zaki1/system01.dbf
skipping datafile 8; already restored to file /oracle/db/oradata/orcl/zaki1/sysaux01.dbf
skipping datafile 9; already restored to file /oracle/db/oradata/orcl/zaki1/zaki1_users01.dbf
skipping datafile 18; already restored to file /oracle/db/oradata/orcl/zaki1/gdb_data02.dbf
restore not done; all files read only, offline, or already restored
Finished restore at 31-OCT-16

Starting recover at 31-OCT-16
using channel ORA_DISK_1
RMAN-05026: WARNING: presuming following set of tablespaces applies to specified Point-in-Time

List of tablespaces expected to have UNDO segments
Tablespace SYSTEM
Tablespace UNDOTBS1

Creating automatic instance, with SID='Bckv'

initialization parameters used for automatic instance:
db_name=ORCL
db_unique_name=Bckv_pitr_zaki1_ORCL
compatible=12.1.0.2.0
db_block_size=8192
db_files=200
diagnostic_dest=/oracle/db
_system_trig_enabled=FALSE
sga_target=2352M
processes=200
db_create_file_dest=/app/backup/tmp
log_archive_dest_1='location=/app/backup/tmp'
enable_pluggable_database=true
_clone_one_pdb_recovery=true
#No auxiliary parameter file used

starting up automatic instance ORCL

Oracle instance started

Total System Global Area    2466250752 bytes

Fixed Size                     2927384 bytes
Variable Size                553649384 bytes
Database Buffers            1895825408 bytes
Redo Buffers                  13848576 bytes
Automatic instance created

contents of Memory Script:
{
# set requested point in time
set until  time "TO_DATE('2016-10-31 12:03:08','yyyy-mm-dd hh24:mi:ss')";
# restore the controlfile
restore clone controlfile;
 
# mount the controlfile
sql clone 'alter database mount clone database';
}
executing Memory Script

executing command: SET until clause

Starting restore at 31-OCT-16
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=173 device type=DISK

channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /oracle/db/fast_recovery_area/ORCL/autobackup/2016_10_28/o1_mf_s_926440264_d16369h7_.bkp
channel ORA_AUX_DISK_1: piece handle=/oracle/db/fast_recovery_area/ORCL/autobackup/2016_10_28/o1_mf_s_926440264_d16369h7_.bkp tag=TAG20161028T163104
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03
output file name=/app/backup/tmp/ORCL/controlfile/o1_mf_d1fpyqvq_.ctl
Finished restore at 31-OCT-16

sql statement: alter database mount clone database

contents of Memory Script:
{
# set requested point in time
set until  time "TO_DATE('2016-10-31 12:03:08','yyyy-mm-dd hh24:mi:ss')";
# switch to valid datafilecopies
switch clone datafile  7 to datafilecopy 
 "/oracle/db/oradata/orcl/zaki1/system01.dbf";
switch clone datafile  8 to datafilecopy 
 "/oracle/db/oradata/orcl/zaki1/sysaux01.dbf";
switch clone datafile  9 to datafilecopy 
 "/oracle/db/oradata/orcl/zaki1/zaki1_users01.dbf";
switch clone datafile  18 to datafilecopy 
 "/oracle/db/oradata/orcl/zaki1/gdb_data02.dbf";
# set destinations for recovery set and auxiliary set datafiles
set newname for clone datafile  1 to new;
set newname for clone datafile  5 to new;
set newname for clone datafile  3 to new;
set newname for clone datafile  6 to new;
set newname for clone datafile  17 to new;
# restore the tablespaces in the recovery set and the auxiliary set
restore clone datafile  1, 5, 3, 6, 17;
 
switch clone datafile all;
}
executing Memory Script

executing command: SET until clause

datafile 7 switched to datafile copy
input datafile copy RECID=1 STAMP=926689888 file name=/oracle/db/oradata/orcl/zaki1/system01.dbf

datafile 8 switched to datafile copy
input datafile copy RECID=2 STAMP=926689888 file name=/oracle/db/oradata/orcl/zaki1/sysaux01.dbf

datafile 9 switched to datafile copy
input datafile copy RECID=3 STAMP=926689888 file name=/oracle/db/oradata/orcl/zaki1/zaki1_users01.dbf

datafile 18 switched to datafile copy
input datafile copy RECID=4 STAMP=926689888 file name=/oracle/db/oradata/orcl/zaki1/gdb_data02.dbf

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

Starting restore at 31-OCT-16
using channel ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00001 to /app/backup/tmp/ORCL/datafile/o1_mf_system_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00005 to /app/backup/tmp/ORCL/datafile/o1_mf_undotbs1_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00003 to /app/backup/tmp/ORCL/datafile/o1_mf_sysaux_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00006 to /app/backup/tmp/ORCL/datafile/o1_mf_users_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00017 to /app/backup/tmp/ORCL/datafile/o1_mf_gdb_data_%u_.dbf
channel ORA_AUX_DISK_1: reading from backup piece /app/backup/zaki1_01rjgl8l_1_120161028
channel ORA_AUX_DISK_1: piece handle=/app/backup/zaki1_01rjgl8l_1_120161028 tag=TAG20161028T160437
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:12:45
Finished restore at 31-OCT-16

datafile 1 switched to datafile copy
input datafile copy RECID=10 STAMP=926690655 file name=/app/backup/tmp/ORCL/datafile/o1_mf_system_d1fpz1nr_.dbf
datafile 5 switched to datafile copy
input datafile copy RECID=11 STAMP=926690655 file name=/app/backup/tmp/ORCL/datafile/o1_mf_undotbs1_d1fpz1mz_.dbf
datafile 3 switched to datafile copy
input datafile copy RECID=12 STAMP=926690655 file name=/app/backup/tmp/ORCL/datafile/o1_mf_sysaux_d1fpz1m9_.dbf
datafile 6 switched to datafile copy
input datafile copy RECID=13 STAMP=926690655 file name=/app/backup/tmp/ORCL/datafile/o1_mf_users_d1fpz1om_.dbf
datafile 17 switched to datafile copy
input datafile copy RECID=14 STAMP=926690655 file name=/app/backup/tmp/ORCL/datafile/o1_mf_gdb_data_d1fpz1lg_.dbf

contents of Memory Script:
{
# set requested point in time
set until  time "TO_DATE('2016-10-31 12:03:08','yyyy-mm-dd hh24:mi:ss')";
# online the datafiles restored or switched
sql clone "alter database datafile  1 online";
sql clone "alter database datafile  5 online";
sql clone "alter database datafile  3 online";
sql clone 'ZAKI1' "alter database datafile 
 7 online";
sql clone 'ZAKI1' "alter database datafile 
 8 online";
sql clone 'ZAKI1' "alter database datafile 
 9 online";
sql clone 'ZAKI1' "alter database datafile 
 18 online";
sql clone "alter database datafile  6 online";
sql clone "alter database datafile  17 online";
# recover pdb
recover clone database tablespace  "SYSTEM", "UNDOTBS1", "SYSAUX", "USERS", "GDB_DATA" pluggable database 
 'ZAKI1'   delete archivelog;
sql clone 'alter database open read only';
plsql <<<begin
   add_dropped_ts;
end; >>>;
plsql <<<begin
   save_pdb_clean_scn;
end; >>>;
# shutdown clone before import
shutdown clone abort
plsql <<<begin
   pdbpitr_inspect(pdbname =>  'ZAKI1');
end; >>>;
}
executing Memory Script

executing command: SET until clause

sql statement: alter database datafile  1 online

sql statement: alter database datafile  5 online

sql statement: alter database datafile  3 online

sql statement: alter database datafile  7 online

sql statement: alter database datafile  8 online

sql statement: alter database datafile  9 online

sql statement: alter database datafile  18 online

sql statement: alter database datafile  6 online

sql statement: alter database datafile  17 online

Starting recover at 31-OCT-16
using channel ORA_AUX_DISK_1

starting media recovery

archived log for thread 1 with sequence 814 is already on disk as file /app/archivelog/1_814_918752760.dbf
archived log for thread 1 with sequence 815 is already on disk as file /app/archivelog/1_815_918752760.dbf
archived log for thread 1 with sequence 816 is already on disk as file /app/archivelog/1_816_918752760.dbf
archived log for thread 1 with sequence 817 is already on disk as file /app/archivelog/1_817_918752760.dbf
archived log for thread 1 with sequence 818 is already on disk as file /app/archivelog/1_818_918752760.dbf
archived log for thread 1 with sequence 819 is already on disk as file /app/archivelog/1_819_918752760.dbf
archived log for thread 1 with sequence 820 is already on disk as file /app/archivelog/1_820_918752760.dbf
archived log for thread 1 with sequence 821 is already on disk as file /app/archivelog/1_821_918752760.dbf
archived log for thread 1 with sequence 822 is already on disk as file /app/archivelog/1_822_918752760.dbf
archived log for thread 1 with sequence 823 is already on disk as file /app/archivelog/1_823_918752760.dbf
archived log for thread 1 with sequence 824 is already on disk as file /app/archivelog/1_824_918752760.dbf
archived log for thread 1 with sequence 825 is already on disk as file /app/archivelog/1_825_918752760.dbf
archived log for thread 1 with sequence 826 is already on disk as file /app/archivelog/1_826_918752760.dbf
archived log for thread 1 with sequence 827 is already on disk as file /app/archivelog/1_827_918752760.dbf
archived log for thread 1 with sequence 828 is already on disk as file /app/archivelog/1_828_918752760.dbf
archived log for thread 1 with sequence 829 is already on disk as file /app/archivelog/1_829_918752760.dbf
archived log for thread 1 with sequence 830 is already on disk as file /app/archivelog/1_830_918752760.dbf
archived log for thread 1 with sequence 831 is already on disk as file /app/archivelog/1_831_918752760.dbf
archived log for thread 1 with sequence 832 is already on disk as file /app/archivelog/1_832_918752760.dbf
archived log for thread 1 with sequence 833 is already on disk as file /app/archivelog/1_833_918752760.dbf
archived log for thread 1 with sequence 834 is already on disk as file /app/archivelog/1_834_918752760.dbf
archived log for thread 1 with sequence 835 is already on disk as file /app/archivelog/1_835_918752760.dbf
archived log for thread 1 with sequence 836 is already on disk as file /app/archivelog/1_836_918752760.dbf
archived log for thread 1 with sequence 837 is already on disk as file /app/archivelog/1_837_918752760.dbf
archived log for thread 1 with sequence 838 is already on disk as file /app/archivelog/1_838_918752760.dbf
archived log for thread 1 with sequence 839 is already on disk as file /app/archivelog/1_839_918752760.dbf
archived log for thread 1 with sequence 840 is already on disk as file /app/archivelog/1_840_918752760.dbf
archived log file name=/app/archivelog/1_814_918752760.dbf thread=1 sequence=814
archived log file name=/app/archivelog/1_815_918752760.dbf thread=1 sequence=815
archived log file name=/app/archivelog/1_816_918752760.dbf thread=1 sequence=816
archived log file name=/app/archivelog/1_817_918752760.dbf thread=1 sequence=817
archived log file name=/app/archivelog/1_818_918752760.dbf thread=1 sequence=818
archived log file name=/app/archivelog/1_819_918752760.dbf thread=1 sequence=819
archived log file name=/app/archivelog/1_820_918752760.dbf thread=1 sequence=820
archived log file name=/app/archivelog/1_821_918752760.dbf thread=1 sequence=821
archived log file name=/app/archivelog/1_822_918752760.dbf thread=1 sequence=822
archived log file name=/app/archivelog/1_823_918752760.dbf thread=1 sequence=823
archived log file name=/app/archivelog/1_824_918752760.dbf thread=1 sequence=824
archived log file name=/app/archivelog/1_825_918752760.dbf thread=1 sequence=825
archived log file name=/app/archivelog/1_826_918752760.dbf thread=1 sequence=826
archived log file name=/app/archivelog/1_827_918752760.dbf thread=1 sequence=827
archived log file name=/app/archivelog/1_828_918752760.dbf thread=1 sequence=828
archived log file name=/app/archivelog/1_829_918752760.dbf thread=1 sequence=829
archived log file name=/app/archivelog/1_830_918752760.dbf thread=1 sequence=830
archived log file name=/app/archivelog/1_831_918752760.dbf thread=1 sequence=831
archived log file name=/app/archivelog/1_832_918752760.dbf thread=1 sequence=832
archived log file name=/app/archivelog/1_833_918752760.dbf thread=1 sequence=833
archived log file name=/app/archivelog/1_834_918752760.dbf thread=1 sequence=834
archived log file name=/app/archivelog/1_835_918752760.dbf thread=1 sequence=835
archived log file name=/app/archivelog/1_836_918752760.dbf thread=1 sequence=836
archived log file name=/app/archivelog/1_837_918752760.dbf thread=1 sequence=837
archived log file name=/app/archivelog/1_838_918752760.dbf thread=1 sequence=838
archived log file name=/app/archivelog/1_839_918752760.dbf thread=1 sequence=839
archived log file name=/app/archivelog/1_840_918752760.dbf thread=1 sequence=840
media recovery complete, elapsed time: 00:06:19
Finished recover at 31-OCT-16
sql statement: alter database open read only
Oracle instance shut down

Removing automatic instance
Automatic instance removed
auxiliary instance file /app/backup/tmp/ORCL/datafile/o1_mf_sysaux_d1fpz1m9_.dbf deleted
auxiliary instance file /app/backup/tmp/ORCL/controlfile/o1_mf_d1fpyqvq_.ctl deleted
Finished recover at 31-OCT-16

RMAN> alter pluggable database zaki1 open resetlogs;

Statement processed


相關推薦

12C-PDB基於時間恢復

RMAN>alter  pluggable database zaki1 close immediate; RMAN> run{ 2> set until time "TO_DATE('2016-10-31 12:03:08','yyyy-mm-dd hh

binlog-rollback.pl基於binlog位置時間恢復delete誤刪語句

基於位置點和時間點恢復delete誤刪一、基於binlog位置點的恢復 為了演示,刷新一個新的binlog文件,讓它單獨記錄delete刪除語句: MySQL [zhangyou]> flush logs Query OK, 0 rows affected (0.09 sec) MySQL [zhan

Mysql的增量備份 及基於時間與位置的恢復

pre school 主從架構 http 二進制 全備 etc 復數 根據 增量備份的優點是沒有重復數據,備份量不大,時間短。缺點也很明顯,需要上次完全備份及完全備份之後所有的增量備份才能恢復,反推恢復,操作較為繁瑣。 Mysql沒有提供增量備份的方法,但是可以通過二進制日

MySQL增量備份恢復基於時間與位置的恢復

local 間接 恢復 efault posit 創建 val etc 節點 為什麽使用增量備份? 完全備份有兩種方式,一種是使用tar打包數據文件,另一種是使用mysqldump進行完全備份。完全備份存在的問題很容易看到,每次都是把所有的數據內容進行備份,備份數據中有大量

MySQL 基於時間與位置恢復

開始 mark 文本 zhang map bin 完全 slave -o 基於時間點與位置恢復 利用二進制日誌可以實現基於時間與位置的恢復,例如由於誤操作刪除了一張表,這時候完全恢復是沒用的,因為日誌裏面還是存在錯誤語句,我們需要的是恢復到誤操作之前的狀態,然後跳過誤操作數

使用 mysqldump 實現 MySQL 5.7 基於時間恢復

trigger result c89 ade cto ima RoCE out a10 創建測試數據全備數據庫 mysqldump --single-transaction --flush-logs --master-data=2 --all-databases --tri

13.基於時間恢復

介紹 恢復完整備份後,您需要還原二進位制日誌以獲取時間點恢復。 備份提供備份可用的二進位制日誌位置。 操作 1 mysqldump or mysqlpump binary log資訊根據傳遞給mysqldump/mysqlpump的選項作為CHANGE MASTER TO命令

ARCHIVELOG模式下使用者管理的不完全恢復基於時間的不完全恢復

基於時間點的恢復主要使用於以下情況:誤刪除表、誤截斷表、提交了錯誤的資料。(從oracle 10g利用閃回更easy!)   首先關閉資料庫執行一個冷全備份(冷備份的時候使用者u1的t表中是有3條記錄的。) [sql] view plai

基於時間RMAN恢復

二. 恢復步驟: 1. 引數檔案恢復 [[email protected] ~]$ rman target / Recovery Manager: Release 11.2.0.4.0 - Production on Tue Sep 5 05:50:45 2017 Copyright

RMAN備份與恢復基於時間的不完全恢復

一 不完全恢復講解         在上一篇文章(RMAN備份與恢復之UNDO表空間丟失)中,我們講到UNDO表空間丟失怎麼處理。UNDO表空間是不可離線的,同樣,SYSTEM表空間也是不可離線的,所以SYSTEM表空間丟失的處理辦法和UNDO表空間丟失的處理辦法類似,在

MySQL中基於mysqldump和二進制日誌log-bin二進制日誌進行邏輯備份以及基於時間的還原

總結 mysql-bin lin .sql bin -h eat log-bin 之前 本文出處:http://www.cnblogs.com/wy123/p/6956464.html 本文僅模擬使用mysqldump和log-bin二進制日誌進行簡單

RMAN基於時間回複數據

1、檢視資料庫是否歸檔 [[email protected] ~]$sqlplus / as sysdba SQL> archive log list 2、實驗過程 2.1建立測試使用者 CREATE TABLESPACE qqqDATAFILE'/u0

數據庫恢復至某個時間

fast ott acl ring rod 宋體 ice reset iat 實例詳解: 數據庫恢復到某個時間點 [oracle@lyo1 ~]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.4.0 Production o

使用xtrbackup/mysqldump全量備份+binlog備份恢復到最近一個時間

先用xtrabackup做全備: innobackupex --defaults-file=/usr/local/mysql/my.cnf --user=root --password=123 /home/backup/xtrabackup/ 全備完成之後新建sanguoyanyi表,並插入

mysql 開發進階篇系列 43 邏輯備份與恢復(基於時間和位置的不完全恢復)

一. 概述          在上篇講到了邏輯備份,使用mysqldump工具來備份一個庫,並使用完全恢復還原了資料庫。在結尾也講到了誤操作是不能用完全恢復的。解決辦法是:我們需要恢復到誤操作之前的狀態,然後跳過誤操作語句。再恢復後面執行的語句,完成我們的恢復,這種恢復叫“不完全恢復”。在mysql 中,不完

oracle通過快照恢復資料到某個時間

1、如果是第一次對錶操作,先執行這sql ALTER TABLE TB_YOFISHDK_ORDER_LOAN_INFO ENABLE ROW MOVEMENT; --注:如果報錯ORA-08189: cannot flashback the table because ro

一步一步告訴你DB2關於指定時間前滾恢復方法

(1)備份資料庫 [[email protected] ~ 22]$db2 backup db sample online include logs Backup successful. The timestamp for this backup image

恢復到特定時間、scn、日誌序列號),rman不完全恢復

將資料庫、表空間、資料檔案等恢復至恢復備份集儲存時間中的任何一個時間點/SCN/日誌序列(一般是日誌挖掘找到誤操作點),但須謹慎,操作前一定需要做好備份,具備條件的情況下最好先恢復到異機,避免業務停機時間。 前提:已經有資料庫備份 (作者已經提前準備了備份,這裡不進行備

DB2關於指定時間前滾恢復方法

其中,End Time: 20051223120902為備份的結束時間,同時它也是前滾時的最小恢復時間點(PIT),也就是說,如果按照指定時間點恢復,最小要恢復到這個時間點,如果用提前於這個時間的時間來前滾,將會返回資訊提示:[[email protected] ~ 31]$db2 ”rollfor

[RMAN]使用RMAN備份將資料庫不完全恢復到指定時間

RMAN作為Oracle強大的備份恢復工具,可以協助我們恢復資料庫到指定時間點,這便是Oracle不完全恢復的一種體現,通過這種方法可以找回我們曾經丟失的資料。這裡以找回誤TRUNCATE表資料為例給大家演示一下RMAN的不完全恢復功能。 1.調整資料庫為歸檔模式[emai