1. 程式人生 > >基於時間不完全恢復之rman篇

基於時間不完全恢復之rman篇

SQL> select sysdate from dual; SYSDATE
-------------------
2013-07-31 22:36:51
run{
sql 'alter session nls_date_format="yyyy-mm-dd hh24:mi:ss"'
set until time '2013-07-31 22:45:51'
restore database;
recover database;
alter database open resetlogs;
} --命令要點,虛擬機器時間關了就不動了,還是7.31號的時間
restore database;
recover database until time '2013-07-31 22:46:51';

alter database open resetlogs;
SSH Secure Shell 3.2.9 (Build 283)
Copyright (c) 2000-2003 SSH Communications Security Corp - http://www.ssh.com/ This copy of SSH Secure Shell is a non-commercial version.
This version does not include PKI and PKCS #11 functionality.
Last login: Wed Jul 31 15:50:34 2013 from 192.168.1.100
[
[email protected]
~]# su - oracle
[[email protected] ~]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.1.0 Production on Wed Jul 31 22:30:03 2013 Copyright (c) 1982, 2009, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
--確認資料庫已經處於歸檔狀態下

SQL> archive log list
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /home/oracle/archivelog
Oldest online log sequence     1
Next log sequence to archive   2
Current log sequence           2
SQL> !clear SQL> create user u1 identified by u1; User created. SQL> create user u2 identified by u2; User created. SQL> grant resource,connect to u1,u2; Grant succeeded. SQL> conn u1/u1
Connected.
SQL> create table cj(id number,name varchar2(50)); Table created. SQL> insert into cj values(1,'cj'); 1 row created. SQL> insert into cj values (8,'cj888'); 1 row created. SQL> select sysdate from dual; SYSDATE
---------
31-JUL-13 --設定時間格式,以便後面基於時間恢復時能識別到時間點的格式
SQL>  alter session set nls_date_format='yyyy-mm-dd hh24:mi:ss'; Session altered. SQL> select sysdate from dual; SYSDATE
-------------------
2013-07-31 22:36:51 SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options [[email protected] ~]$ cd /u01/app/oracle/flash_recovery_area/MDNSS/
[[email protected] MDNSS]$ ll
total 16
drwxr-x--- 2 oracle oinstall 4096 Jul 31 22:41 archivelog
drwxr-x--- 3 oracle oinstall 4096 Jul 31 18:46 backupset
drwxr-x--- 2 oracle oinstall 4096 Jul 31 22:31 flashback
drwxr-x--- 2 oracle oinstall 4096 May 26 01:41 onlinelog
[[email protected] MDNSS]$ cd backupset/
[[email protected] backupset]$ ll
total 4
drwxr-x--- 2 oracle oinstall 4096 Jul 31 22:41 2013_07_31
[[email protected] backupset]$ date
Wed Jul 31 22:43:29 CST 2013
--設定日期環境
[[email protected] backupset]$ export NLS_DATE_FORMAT="yyyy-mm-dd hh24:mi:ss"
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Jul 31 22:38:12 2013 Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved. connected to target database: MDNSS (DBID=3864238845)
--下面開始RMAN全庫備份了,包括歸檔日誌,之後刪除INPUT在記憶體中的載入  RMAN> backup database plus archivelog delete input;
Starting backup at 31-JUL-13
current log archived
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=46 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=24 RECID=1 STAMP=816470585
input archived log thread=1 sequence=25 RECID=2 STAMP=816470822
input archived log thread=1 sequence=26 RECID=3 STAMP=816486445
input archived log thread=1 sequence=27 RECID=4 STAMP=822198990
input archived log thread=1 sequence=28 RECID=7 STAMP=822208660
input archived log thread=1 sequence=29 RECID=11 STAMP=822209838
input archived log thread=1 sequence=30 RECID=9 STAMP=822209838
input archived log thread=1 sequence=31 RECID=10 STAMP=822209838
input archived log thread=1 sequence=32 RECID=12 STAMP=822209838
channel ORA_DISK_1: starting piece 1 at 31-JUL-13
channel ORA_DISK_1: finished piece 1 at 31-JUL-13
piece handle=/u01/app/oracle/flash_recovery_area/MDNSS/backupset/2013_07_31/o1_mf_annnn_TAG20130731T223852_8zl8cxq2_.bkp tag=TAG20130731T223852 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/u01/app/oracle/flash_recovery_area/MDNSS/archivelog/2013_05_26/o1_mf_1_24_8t435s00_.arc RECID=1 STAMP=816470585
archived log file name=/home/oracle/archivelog/1_25_816399680.dbf RECID=2 STAMP=816470822
archived log file name=/home/oracle/archivelog/1_26_816399680.dbf RECID=3 STAMP=816486445
archived log file name=/home/oracle/archivelog/1_27_816399680.dbf RECID=4 STAMP=822198990
archived log file name=/home/oracle/archivelog/1_28_816399680.dbf RECID=7 STAMP=822208660
archived log file name=/home/oracle/archivelog/1_29_816399680.dbf RECID=11 STAMP=822209838
archived log file name=/home/oracle/archivelog/1_30_816399680.dbf RECID=9 STAMP=822209838
archived log file name=/home/oracle/archivelog/1_31_816399680.dbf RECID=10 STAMP=822209838
archived log file name=/home/oracle/archivelog/1_32_816399680.dbf RECID=12 STAMP=822209838
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=1 RECID=13 STAMP=822223538
input archived log thread=1 sequence=2 RECID=14 STAMP=822224196
input archived log thread=1 sequence=7 RECID=17 STAMP=822243364
input archived log thread=1 sequence=8 RECID=18 STAMP=822243364
input archived log thread=1 sequence=9 RECID=15 STAMP=822243364
input archived log thread=1 sequence=10 RECID=16 STAMP=822243364
channel ORA_DISK_1: starting piece 1 at 31-JUL-13
channel ORA_DISK_1: finished piece 1 at 31-JUL-13
piece handle=/u01/app/oracle/flash_recovery_area/MDNSS/backupset/2013_07_31/o1_mf_annnn_TAG20130731T223852_8zl8dgfj_.bkp tag=TAG20130731T223852 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/home/oracle/archivelog/1_1_822209838.dbf RECID=13 STAMP=822223538
archived log file name=/home/oracle/archivelog/1_2_822209838.dbf RECID=14 STAMP=822224196
archived log file name=/home/oracle/archivelog/1_7_822209838.dbf RECID=17 STAMP=822243364
archived log file name=/home/oracle/archivelog/1_8_822209838.dbf RECID=18 STAMP=822243364
archived log file name=/home/oracle/archivelog/1_9_822209838.dbf RECID=15 STAMP=822243364
archived log file name=/home/oracle/archivelog/1_10_822209838.dbf RECID=16 STAMP=822243364
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=1 RECID=19 STAMP=822249980
input archived log thread=1 sequence=2 RECID=20 STAMP=822263931
channel ORA_DISK_1: starting piece 1 at 31-JUL-13
channel ORA_DISK_1: finished piece 1 at 31-JUL-13
piece handle=/u01/app/oracle/flash_recovery_area/MDNSS/backupset/2013_07_31/o1_mf_annnn_TAG20130731T223852_8zl8dkt6_.bkp tag=TAG20130731T223852 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/home/oracle/archivelog/1_1_822243364.dbf RECID=19 STAMP=822249980
archived log file name=/home/oracle/archivelog/1_2_822243364.dbf RECID=20 STAMP=822263931
Finished backup at 31-JUL-13 Starting backup at 31-JUL-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/mdnss/system01.dbf
input datafile file number=00002 name=/u01/app/oracle/oradata/mdnss/sysaux01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/mdnss/undotbs01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/mdnss/users01.dbf
input datafile file number=00007 name=/u01/app/oracle/oradata/mdnss/t2a.dbf
input datafile file number=00006 name=/u01/app/oracle/oradata/mdnss/jf_data02.dbf
input datafile file number=00005 name=/u01/app/oracle/oradata/mdnss/jf_data01.dbf
channel ORA_DISK_1: starting piece 1 at 31-JUL-13
channel ORA_DISK_1: finished piece 1 at 31-JUL-13
piece handle=/u01/app/oracle/flash_recovery_area/MDNSS/backupset/2013_07_31/o1_mf_nnndf_TAG20130731T223917_8zl8dpg6_.bkp tag=TAG20130731T223917 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:38
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 31-JUL-13
channel ORA_DISK_1: finished piece 1 at 31-JUL-13
piece handle=/u01/app/oracle/flash_recovery_area/MDNSS/backupset/2013_07_31/o1_mf_ncsnf_TAG20130731T223917_8zl8hvz0_.bkp tag=TAG20130731T223917 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 31-JUL-13 Starting backup at 31-JUL-13
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=3 RECID=21 STAMP=822264061
channel ORA_DISK_1: starting piece 1 at 31-JUL-13
channel ORA_DISK_1: finished piece 1 at 31-JUL-13
piece handle=/u01/app/oracle/flash_recovery_area/MDNSS/backupset/2013_07_31/o1_mf_annnn_TAG20130731T224101_8zl8hxw0_.bkp tag=TAG20130731T224101 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/home/oracle/archivelog/1_3_822243364.dbf RECID=21 STAMP=822264061
Finished backup at 31-JUL-13
[[email protected] backupset]$ cd 2013_07_31/
[[email protected] 2013_07_31]$ ls
o1_mf_annnn_TAG20130731T184620_8zktqws5_.bkp
o1_mf_annnn_TAG20130731T223852_8zl8cxq2_.bkp
o1_mf_annnn_TAG20130731T223852_8zl8dgfj_.bkp
o1_mf_annnn_TAG20130731T223852_8zl8dkt6_.bkp
o1_mf_annnn_TAG20130731T224101_8zl8hxw0_.bkp
o1_mf_ncsnf_TAG20130731T223917_8zl8hvz0_.bkp
o1_mf_nnndf_TAG20130731T223917_8zl8dpg6_.bkp
[[email protected] 2013_07_31]$ ls -tl
total 1224012
-rw-r----- 1 oracle oinstall       3072 Jul 31 22:41 o1_mf_annnn_TAG20130731T224101_8zl8hxw0_.bkp
-rw-r----- 1 oracle oinstall    9830400 Jul 31 22:41 o1_mf_ncsnf_TAG20130731T223917_8zl8hvz0_.bkp
-rw-r----- 1 oracle oinstall 1080147968 Jul 31 22:40 o1_mf_nnndf_TAG20130731T223917_8zl8dpg6_.bkp--這個是資料檔案的備份檔案集
-rw-r----- 1 oracle oinstall   31120384 Jul 31 22:39 o1_mf_annnn_TAG20130731T223852_8zl8dkt6_.bkp
-rw-r----- 1 oracle oinstall   25585664 Jul 31 22:39 o1_mf_annnn_TAG20130731T223852_8zl8dgfj_.bkp
-rw-r----- 1 oracle oinstall  102524928 Jul 31 22:39 o1_mf_annnn_TAG20130731T223852_8zl8cxq2_.bkp
-rw-r----- 1 oracle oinstall    2908672 Jul 31 18:46 o1_mf_annnn_TAG20130731T184620_8zktqws5_.bkp
SQL> create table u2_table(id number,name varchar2(50),password varchar2(50)); Table created. SQL> insert into u2_table(88,'cunxm','chenjian');
insert into u2_table(88,'cunxm','chenjian')
                     *
ERROR at line 1:
ORA-00928: missing SELECT keyword

SQL> c/table/table values;--SQL寫錯了,可以這樣替換喔
  1* insert into u2_table values(88,'cunxm','chenjian')
SQL> / 1 row created. SQL> / 1 row created. SQL> commit; Commit complete. SQL> commit; Commit complete. SQL> select table_name from user_tables; TABLE_NAME
------------------------------
CJ
U2_TABLE
SQL> select * from cj;         ID NAME
---------- --------------------------------------------------
         1 cj
         8 cj888
SQL> drop user u2 cascade;
drop user u2 cascade
*
ERROR at line 1:
ORA-01031: insufficient privileges--許可權不夠,切換管理員使用者操作
SQL> conn / as sysdba
Connected.
SQL> dropt user u2 cascade;--關聯刪除
SP2-0734: unknown command beginning "dropt user..." - rest of line ignored.
SQL> drop user u2 cascade; User dropped. SQL> conn u1/u1;
Connected.
SQL> drop table cj purge;--乾淨刪除,學過閃回表之前必作的動作 Table dropped.
SQL> purge recyclebin; --清除回收站,以免誤解 SQL> shutdown immediate
ORA-01031: insufficient privileges
SQL> conn / as sysdba
Connected.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> exit [[email protected] 2013_07_31]$ export NLS_DATE_FORMAT='yyyy-mm-dd hh24:mi:ss';
[[email protected] 2013_07_31]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.1.0 Production on Wed Jul 31 22:57:25 2013 Copyright (c) 1982, 2009, Oracle.  All rights reserved. Connected to an idle instance.
--在準備恢復之前,在刪除u2使用者,以及刪除u1表CJ;以便認識這些不完全恢復的時間點,是不是刪除的表與使用者都可以,但後來u2建立的表u2_table是無法重現了,但刪除使用者與表能找回來
SQL> startup mount;
ORACLE instance started. Total System Global Area  517763072 bytes
Fixed Size                  2214896 bytes
Variable Size             394265616 bytes
Database Buffers          117440512 bytes
Redo Buffers                3842048 bytes
Database mounted.
SQL> restore database;  --注意這是SQLPLUS下面的環境,回到RMAN命令列操作
SP2-0734: unknown command beginning "restore da..." - rest of line ignored.
SQL> alert session nls_date_format='yyyy-mm-dd hh24:mi:ss';
SP2-0734: unknown command beginning "alert sess..." - rest of line ignored.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[[email protected] 2013_07_31]$  export NLS_DATE_FORMAT="yyyy-mm-dd hh24:mi:ss"
[[email protected] 2013_07_31]$ rman target / Recovery Manager: Release 11.2.0.1.0 - Production on Wed Jul 31 23:01:09 2013 Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved. connected to target database: MDNSS (DBID=3864238845, not open) --為了安全不會出差錯,第二次進行設定時間格式
RMAN>  sql 'alter session set nls_date_format="yyyy-mm-dd hh24:mi:ss"'; sql statement: alter session set nls_date_format="yyyy-mm-dd hh24:mi:ss" RMAN> restore database; Starting restore at 2013-07-31 23:02:48
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=20 device type=DISK 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/mdnss/system01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/mdnss/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/mdnss/undotbs01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/mdnss/users01.dbf
channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/mdnss/jf_data01.dbf
channel ORA_DISK_1: restoring datafile 00006 to /u01/app/oracle/oradata/mdnss/jf_data02.dbf
channel ORA_DISK_1: restoring datafile 00007 to /u01/app/oracle/oradata/mdnss/t2a.dbf
channel ORA_DISK_1: reading from backup piece /u01/app/oracle/flash_recovery_area/MDNSS/backupset/2013_07_31/o1_mf_nnndf_TAG20130731T223917_8zl8dpg6_.bkp
channel ORA_DISK_1: piece handle=/u01/app/oracle/flash_recovery_area/MDNSS/backupset/2013_07_31/o1_mf_nnndf_TAG20130731T223917_8zl8dpg6_.bkp tag=TAG20130731T223917
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:25
Finished restore at 2013-07-31 23:04:15 --一定理解時間點的概念,因為上面2013-07-31 22:36:51是我建立二個使用者,以及在u1建立一張表後的動作,由於不太熟練,所以
--時間老以為可以恢復到記錄這個時間之前是不對的,因為備份完全後起碼在十分種左右,這一次是一致性關閉資料庫,所以在這個時間上加十分鐘就剛好了
RMAN> recover database until time '2013-07-31 22:36:51'; Starting recover at 2013-07-31 23:05:31
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 07/31/2013 23:05:32
RMAN-06555: datafile 1 must be restored from backup created before 2013-07-31 22:36:51 RMAN>  recover database until time '2013-07-31 22:34:51';--往前調是不認的 Starting recover at 2013-07-31 23:06:22
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 07/31/2013 23:06:22
RMAN-06555: datafile 1 must be restored from backup created before 2013-07-31 22:34:51 RMAN> recover database until time '2013-07-31 22:36:51'; Starting recover at 2013-07-31 23:08:36
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 07/31/2013 23:08:36
RMAN-06555: datafile 1 must be restored from backup created before 2013-07-31 22:36:51 RMAN> recover database until time '2013-07-31 22:46:51';--只有往後調時間點點才能恢復 Starting recover at 2013-07-31 23:09:31
using channel ORA_DISK_1 starting media recovery
media recovery complete, elapsed time: 00:00:03 Finished recover at 2013-07-31 23:09:34 RMAN> alter database open resetlogs; database opened

相關推薦

基於時間完全恢復rman

SQL> select sysdate from dual; SYSDATE ------------------- 2013-07-31 22:36:51 run{ sql 'alter session nls_date_format="yyyy-mm-dd hh

20121225_完全恢復記錄(rman)

restore controlfile from '/orabak/AutoCtl_SGERP5_20121222_c-3580899532-20121222-00'; oracle:srvctl add database -d sgerp5 -o /u01/app/pro

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

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

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

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

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

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

Oracle 基於 RMAN完全恢復(incomplete recovery by RMAN)

引用自:https://blog.csdn.net/leshami/article/details/9253867 Oracle 資料庫可以實現資料庫不完全恢復與完全恢復。完全恢復是將資料庫恢復到最新時刻,也就是無損恢復,保證資料庫無丟失的恢復。而不完全恢復則是根據需要特意將資料庫恢復到某個過去

RMAN備份恢復完全恢復

ORACLE不完全恢復 基於時間的不完全恢復 恢復要求:a、資料庫開啟歸檔切要有最近的有效rman全備。b、要有需要恢復到的準確時間點。 1、 做一個rman全備 RMAN>backup database; 2、 構建幾個狀態 在資料庫裡建立scott.t1並插入資料記錄狀態為a,記錄時間t1。 在資料

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

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

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

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

ARCHIVELOG模式下使用者管理的完全恢復基於備份控制檔案的完全恢復

基於備份控制檔案的恢復只要適用於以下情況:表空間被意外刪除;所有控制檔案全部損壞。   先關閉資料庫,執行一次全庫冷備份。 [sql] view plain copy print ?

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

當用戶執行不完全恢復時,如果能夠確定恢復點所對應的SCN值,那麼可以使用這種方法恢復!   首先關閉資料庫執行一個冷全備份 [sql] view plain copy print ?

ARCHIVELOG模式下使用者管理的完全恢復基於取消的完全恢復

 基於取消的恢復只要適用於以下情況: 歸檔日誌丟失導致完全恢復失敗; 丟失了資料檔案和未歸檔的重做日誌(聯機重做日誌);   先關閉資料庫,執行一次全庫冷備份。 [sql] view plain copy pri

木浪雲融合資料管理免費版完全體驗極速恢復

上次和大家分享了木浪雲資料管理免費的初步體驗,只給大家介紹了產品的獲取、部署、初始化以及虛擬機器備份的初步體驗,總的體驗上還是非常簡潔和容易上手的,介面上也比較清爽,這個個人比較喜歡。在開始之前我們還是簡單的回顧一下。 免費版的木浪雲融合資料管理免費版主要支援如下功能: 全中文HT

RMAN全庫【完全恢復/完全恢復】brief版

一 完全恢復 1.資料庫全庫【完全恢復】 $ rman target / 登入rman工具,如果使用了catalog,則登陸方法rman target sys/[email protected

RMAN完全恢復方法(恢復到資料庫某一時間點)

RMAN不完全恢復方法 試驗目的:利用RMAN完成對資料庫的不完全恢復(將資料庫恢復到某個時間點) 試驗步驟:         1.RMAN備份資料庫:backup database;   2. 記錄當前時間: SQL> select to_c

實現多次完全恢復(RAC環境需要將另一節點關閉)

chang hang startup 節點 lec star med immediate 關閉 #查看以resetlogs打開的歷史SQL> SELECT a.INCARNATION#,a.RESETLOGS_CHANGE#,to_char(a.RESETLOGS_T

Oracle備份和恢復RMAN

RMAN ORACLE 張晨 前言:歡迎加QQ交流1445696451微博地址http://blog.51cto.com/13434336~~~~~~~分割~~~~~~數據庫備份與恢復是數據庫管理員必須掌握的。沒有任何系統能免遭硬盤物理損壞、粗心用戶的錯誤操作、或一些可能會威脅到存儲數據的潛在災難

oracle 歸檔模式下刪除current日誌完全恢復

com variable file end mounted 啟動數據庫 lte status archive 歸檔模式 SYS@orcl> archive log list Database log mode Archive Mode Automat

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

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

在異機實現 Oracle 完全恢復

otg art set med resetlogs 和數 to_date 數據庫 over 1、將數據庫完全備份集和歸檔日誌備份集傳到執行恢復的 Oracle 服務器# 傳到中轉服務器 scp -P 2222 database.20181030.5* 218.17.56.5