resetlogs打开数据库后备份、归档日志是否可用的测试 RMAN-06054

最新推荐文章于 2024-08-09 21:25:57 发布
最新推荐文章于 2024-08-09 21:25:57 发布
阅读量213 收藏
点赞数
文章标签： 数据库 操作系统
本测试验证数据库在resetlogs打开后，之前的备份、日志是否可用。

--首先测试备份是否可用
--查看数据库版本
SQL> select * from v$version where rownum<5;
BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
PL/SQL Release 11.2.0.1.0 - Production
CORE    11.2.0.1.0      Production
TNS for Linux: Version 11.2.0.1.0 - Production
--插入测试数据
SQL> insert into test values(1,'before');
1 row created.
SQL> commit;
Commit complete.
SQL> select * from test;
        ID NAME
---------- --------------------
         1 before
--查看当前scn
SQL> select current_scn from v$database;
CURRENT_SCN
-----------
2912936147
--清空所有备份
RMAN> list backup of database summary;
specification does not match any backup in the repository
RMAN> list backup of archivelog all;
specification does not match any backup in the repository
--进行数据库全备
RMAN> backup database;
Starting backup at 09-APR-12
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4
using channel ORA_DISK_5
using channel ORA_DISK_6
... ...
rdn_.bkp tag=TAG20120409T231116 comment=NONE
channel ORA_DISK_3: backup set complete, elapsed time: 00:01:50
Finished backup at 09-APR-12
RMAN> list backup of database summary;

List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
119     B  F  A DISK        09-APR-12       1       1       YES        TAG20120409T231116
120     B  F  A DISK        09-APR-12       1       1       YES        TAG20120409T231116
123     B  F  A DISK        09-APR-12       1       1       YES        TAG20120409T231116
124     B  F  A DISK        09-APR-12       1       1       YES        TAG20120409T231116
125     B  F  A DISK        09-APR-12       1       1       YES        TAG20120409T231116
--查看当前数据库日志序列
SQL> select SEQUENCE#,STATUS from v$log;
SEQUENCE# STATUS
---------- ----------------
        10 INACTIVE
        11 INACTIVE
        12 CURRENT
SQL> archive log list;
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     10
Next log sequence to archive   12
Current log sequence           12
SQL> select flashback_on from v$database;
FLASHBACK_ON
------------------
YES
--插入备份后的测试数据2
SQL> insert into test values(2,'yallonking');
1 row created.
SQL> commit;
Commit complete.
SQL> select current_scn from v$database;
CURRENT_SCN
-----------
2912937359
--建数据库闪回到记录1的状态，并以restlogs打开数据库（模拟不完全恢复）
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area  422670336 bytes
Fixed Size                  1336960 bytes
Variable Size             331352448 bytes
Database Buffers           83886080 bytes
Redo Buffers                6094848 bytes
Database mounted.
SQL> flashback database to scn 2912936147;
Flashback complete.
SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

SQL> alter database open resetlogs;
Database altered.
--查看测试数据
SQL> conn test/test
Connected.
SQL> select * from test;
        ID NAME
---------- --------------------
         1 before
--查看当前日志序列
SQL> select SEQUENCE#,STATUS from v$log;
SEQUENCE# STATUS
---------- ----------------
         1 CURRENT
         0 UNUSED
         0 UNUSED
SQL> archive log list;
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     1
Next log sequence to archive   1
Current log sequence           1
--查看当前归档日志中的序列号变化
[oracle@test 2012_04_09]$ ll
total 16304
-rw-r----- 1 oracle oinstall 14886912 Apr  9 23:59 o1_mf_1_10_7r61vk5f_.arc
-rw-r----- 1 oracle oinstall   487936 Apr  9 23:47 o1_mf_1_11_7r614lr5_.arc
-rw-r----- 1 oracle oinstall   487936 Apr  9 23:59 o1_mf_1_11_7r61vl56_.arc
-rw-r----- 1 oracle oinstall   819712 Apr  9 23:59 o1_mf_1_12_7r61vl79_.arc
[oracle@test 2012_04_09]$ cd -
/tmp/TEST/archivelog/2012_04_10
[oracle@test 2012_04_10]$ ll
total 1532
-rw-r----- 1 oracle oinstall 1040384 Apr 10 00:07 o1_mf_1_1_7r6299vp_.arc
-rw-r----- 1 oracle oinstall  250368 Apr 10 00:08 o1_mf_1_1_7r62cx25_.arc
-rw-r----- 1 oracle oinstall  271872 Apr 10 00:10 o1_mf_1_1_7r62j5bk_.arc

--插入闪回后的测试数据3
SQL> insert into test values(3,'after');
1 row created.
SQL> commit;
Commit complete.
SQL> select current_scn from v$database;
CURRENT_SCN
-----------
2912937130
--尝试闪回到备份后的记录2，但数据库已经闪回到备份时的1，且将日志序列重置，故此处无法获得记录2 的相关日志信息，故闪回不到记录2。
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area  422670336 bytes
Fixed Size                  1336960 bytes
Variable Size             331352448 bytes
Database Buffers           83886080 bytes
Redo Buffers                6094848 bytes
Database mounted.
SQL>  flashback database to scn 2912937359;
flashback database to scn 2912937359
*
ERROR at line 1:
ORA-38743: Time/SCN is in the future of the database.
--尝试闪回到数据库已经闪回到1且在之后又进行了3的插入，因为闪回到1后，记录3的日志信息还在没有被重置，故此刻是可以闪回到3的。
SQL>  flashback database to scn 2912937130;
Flashback complete.
SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

SQL> alter database open resetlogs;
Database altered.
SQL> select * from test.test;
        ID NAME
---------- --------------------
         1 before
         3 after
--再次尝试闪回到备份记录1成功。
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area  422670336 bytes
Fixed Size                  1336960 bytes
Variable Size             331352448 bytes
Database Buffers           83886080 bytes
Redo Buffers                6094848 bytes
Database mounted.
SQL>  flashback database to scn 2912936147;
Flashback complete.
SQL> alter database open resetlogs;
Database altered.
SQL> select * from test.test;
        ID NAME
---------- --------------------
         1 before

--下面是2种情况进行分析resetlogs后的和前的日志是否可用的测试
--情况一
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area  422670336 bytes
Fixed Size                  1336960 bytes
Variable Size             331352448 bytes
Database Buffers           83886080 bytes
Redo Buffers                6094848 bytes
Database mounted.
RMAN> run{
2> set until sequence 12 thread 1;
3> recover database;
4> }
executing command: SET until clause
Starting recover at 10-APR-12
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4
using channel ORA_DISK_5
using channel ORA_DISK_6
starting media recovery
media recovery complete, elapsed time: 00:00:00
Finished recover at 10-APR-12
SQL> alter database open resetlogs;
Database altered.
SQL> select * from test.test;
        ID NAME
---------- --------------------
         1 before
--此处发现resetlogs以前的归档日志是可以使用的，但记录2还是没有恢复过来，初步断定是当时日志还是在redo中，没有写到归档中。
--下面重新进行测试
SQL> truncate table test.test;
Table truncated.
SQL> select current_scn from v$database;
CURRENT_SCN
-----------
2912941477
SQL> select sequence#,status from v$log;
SEQUENCE# STATUS
---------- ----------------
         1 CURRENT
         0 UNUSED
         0 UNUSED
SQL> insert into test.test values(1,'oraking');
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> /
System altered.
SQL> /
System altered.
SQL> /
System altered.
SQL> alter system archive log current;
System altered.
SQL> select sequence#,status from v$log;
SEQUENCE# STATUS
---------- ----------------
         4 INACTIVE
         5 INACTIVE
         6 CURRENT
SQL> select current_scn from v$database;
CURRENT_SCN
-----------
2912941587
SQL> insert into test.test values(2,'yallonking');
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> /
System altered.
SQL> /
System altered.
SQL> /
System altered.
SQL> alter system archive log current;
System altered.
SQL> select sequence#,status from v$log;
SEQUENCE# STATUS
---------- ----------------
        10 INACTIVE
        11 CURRENT
         9 INACTIVE
SQL> select current_scn from v$database;
CURRENT_SCN
-----------
2912942137
SQL> insert into test.test values(3,'yallonking');
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> /
System altered.
SQL> /
System altered.
SQL> /
System altered.
SQL> alter system archive log current;
System altered.
SQL> select sequence#,status from v$log;
SEQUENCE# STATUS
---------- ----------------
        16 CURRENT
        14 INACTIVE
        15 ACTIVE
SQL> select current_scn from v$database;
CURRENT_SCN
-----------
2912942252
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area  422670336 bytes
Fixed Size                  1336960 bytes
Variable Size             343935360 bytes
Database Buffers           71303168 bytes
Redo Buffers                6094848 bytes
Database mounted.
SQL> flashback database to scn 2912942252;
Flashback complete.
SQL> alter database open resetlogs;
Database altered.
SQL> select sequence#,status from v$log;
SEQUENCE# STATUS
---------- ----------------
         1 CURRENT
         0 UNUSED
         0 UNUSED
SQL> select * from test.test;
        ID NAME
---------- --------------------
         1 oraking
         2 yallonking
         3 yallonking

SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area  422670336 bytes
Fixed Size                  1336960 bytes
Variable Size             343935360 bytes
Database Buffers           71303168 bytes
Redo Buffers                6094848 bytes
Database mounted.
SQL> !
[oracle@test ~]$ rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Apr 10 02:30:34 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
connected to target database: TEST (DBID=2055832488, not open)
RMAN> run{
2> set until sequence 10 thread 1;
3> recover database;
4> }
executing command: SET until clause
Starting recover at 10-APR-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=21 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=22 device type=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: SID=23 device type=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: SID=24 device type=DISK
allocated channel: ORA_DISK_5
channel ORA_DISK_5: SID=25 device type=DISK
allocated channel: ORA_DISK_6
channel ORA_DISK_6: SID=26 device type=DISK
starting media recovery
media recovery complete, elapsed time: 00:00:00
Finished recover at 10-APR-12
SQL> alter database open resetlogs;
Database altered.
SQL> select * from test.test;
        ID NAME
---------- --------------------
         1 oraking
         2 yallonking
         3 yallonking
SQL> flashback database to scn 2912941587;
Flashback complete.
SQL> !
[oracle@test ~]$ rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Apr 10 02:37:20 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
connected to target database: TEST (DBID=2055832488, not open)
RMAN> run{
2> set until sequence 10 thread 1;
3> recover database;}
executing command: SET until clause
Starting recover at 10-APR-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=21 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=22 device type=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: SID=23 device type=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: SID=24 device type=DISK
allocated channel: ORA_DISK_5
channel ORA_DISK_5: SID=25 device type=DISK
allocated channel: ORA_DISK_6
channel ORA_DISK_6: SID=26 device type=DISK
starting media recovery
archived log for thread 1 with sequence 6 is already on disk as file /tmp/TEST/archivelog/2012_04_10/o1_mf_1_6_7r6bcs7b_.arc
archived log for thread 1 with sequence 7 is already on disk as file /tmp/TEST/archivelog/2012_04_10/o1_mf_1_7_7r6bctbj_.arc
archived log for thread 1 with sequence 8 is already on disk as file /tmp/TEST/archivelog/2012_04_10/o1_mf_1_8_7r6bcx9t_.arc
archived log for thread 1 with sequence 9 is already on disk as file /tmp/TEST/archivelog/2012_04_10/o1_mf_1_9_7r6bcy2w_.arc
archived log for thread 1 with sequence 10 is already on disk as file /tmp/TEST/archivelog/2012_04_10/o1_mf_1_10_7r6bd34t_.arc
archived log for thread 1 with sequence 11 is already on disk as file /tmp/TEST/archivelog/2012_04_10/o1_mf_1_11_7r6bg47x_.arc
archived log for thread 1 with sequence 12 is already on disk as file /tmp/TEST/archivelog/2012_04_10/o1_mf_1_12_7r6bg58h_.arc
archived log for thread 1 with sequence 13 is already on disk as file /tmp/TEST/archivelog/2012_04_10/o1_mf_1_13_7r6bg8fs_.arc
archived log for thread 1 with sequence 14 is already on disk as file /tmp/TEST/archivelog/2012_04_10/o1_mf_1_14_7r6bmpom_.arc
archived log for thread 1 with sequence 15 is already on disk as file /tmp/TEST/archivelog/2012_04_10/o1_mf_1_15_7r6bmppk_.arc
archived log for thread 1 with sequence 16 is already on disk as file /tmp/TEST/archivelog/2012_04_10/o1_mf_1_16_7r6bmpnf_.arc
archived log for thread 1 with sequence 1 is already on disk as file /tmp/TEST/archivelog/2012_04_10/o1_mf_1_1_7r6bthx9_.arc
archived log file name=/tmp/TEST/archivelog/2012_04_10/o1_mf_1_6_7r6bcs7b_.arc thread=1 sequence=6
archived log file name=/tmp/TEST/archivelog/2012_04_10/o1_mf_1_7_7r6bctbj_.arc thread=1 sequence=7
archived log file name=/tmp/TEST/archivelog/2012_04_10/o1_mf_1_8_7r6bcx9t_.arc thread=1 sequence=8
archived log file name=/tmp/TEST/archivelog/2012_04_10/o1_mf_1_9_7r6bcy2w_.arc thread=1 sequence=9
archived log file name=/tmp/TEST/archivelog/2012_04_10/o1_mf_1_10_7r6bd34t_.arc thread=1 sequence=10
archived log file name=/tmp/TEST/archivelog/2012_04_10/o1_mf_1_11_7r6bg47x_.arc thread=1 sequence=11
archived log file name=/tmp/TEST/archivelog/2012_04_10/o1_mf_1_12_7r6bg58h_.arc thread=1 sequence=12
archived log file name=/tmp/TEST/archivelog/2012_04_10/o1_mf_1_13_7r6bg8fs_.arc thread=1 sequence=13
archived log file name=/tmp/TEST/archivelog/2012_04_10/o1_mf_1_14_7r6bmpom_.arc thread=1 sequence=14
archived log file name=/tmp/TEST/archivelog/2012_04_10/o1_mf_1_15_7r6bmppk_.arc thread=1 sequence=15
archived log file name=/tmp/TEST/archivelog/2012_04_10/o1_mf_1_16_7r6bmpnf_.arc thread=1 sequence=16
archived log file name=/tmp/TEST/archivelog/2012_04_10/o1_mf_1_1_7r6bthx9_.arc thread=1 sequence=1
unable to find archived log
archived log thread=1 sequence=1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/10/2012 02:37:59
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1 and starting SCN of 2912942650
RMAN> quit
以上说明:时刻A插入数据，进行到时刻C，闪回至时刻B，则A->B间的日志不可用，也就是不能进行不完全恢复到A和B之间的某个时刻。

--情况二
SQL> truncate table test.test;
Table truncated.
SQL> select current_scn from v$database;
CURRENT_SCN
-----------
2912943400
SQL> select sequence#,status from v$log;
SEQUENCE# STATUS
---------- ----------------
         1 CURRENT
         0 UNUSED
         0 UNUSED
SQL> insert into test.test values(1,'oraking');
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> /
System altered.
SQL> /
System altered.
SQL> /
System altered.
SQL> alter system archive log current;
System altered.
SQL> select sequence#,status from v$log;
SEQUENCE# STATUS
---------- ----------------
         4 INACTIVE
         5 INACTIVE
         6 CURRENT
SQL> select current_scn from v$database;
CURRENT_SCN
-----------
2912943445
SQL> insert into test.test values(2,'yallonking');
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> /
System altered.
SQL> /
System altered.
SQL> /
System altered.
SQL> alter system archive log current;
System altered.
SQL> select sequence#,status from v$log;
SEQUENCE# STATUS
---------- ----------------
        10 INACTIVE
        11 CURRENT
         9 INACTIVE
SQL> select current_scn from v$database;
CURRENT_SCN
-----------
2912943484

SQL> insert into test.test values(3,'king');
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> /
System altered.
SQL> /
System altered.
SQL> /
System altered.
SQL> /
System altered.
SQL> /
System altered.
SQL> alter system archive log current;
System altered.
SQL> select sequence#,status from v$log;
SEQUENCE# STATUS
---------- ----------------
        16 INACTIVE
        17 INACTIVE
        18 CURRENT
SQL> select current_scn from v$database;
CURRENT_SCN
-----------
2912943534
SQL> select * from test.test;
        ID NAME
---------- --------------------
         1 oraking
         2 yallonking
         3 king
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area  422670336 bytes
Fixed Size                  1336960 bytes
Variable Size             356518272 bytes
Database Buffers           58720256 bytes
Redo Buffers                6094848 bytes
Database mounted.
SQL> flashback database to scn 2912943445;
Flashback complete.
SQL> !
[oracle@test ~]$ rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Apr 10 03:01:36 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
connected to target database: TEST (DBID=2055832488, not open)RMAN> run{
2> set until sequence 10 thread 1;
3> recover database;
4> }
executing command: SET until clause
Starting recover at 10-APR-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=21 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=22 device type=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: SID=23 device type=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: SID=24 device type=DISK
allocated channel: ORA_DISK_5
channel ORA_DISK_5: SID=25 device type=DISK
allocated channel: ORA_DISK_6
channel ORA_DISK_6: SID=26 device type=DISK
starting media recovery
archived log for thread 1 with sequence 6 is already on disk as file /tmp/TEST/archivelog/2012_04_10/o1_mf_1_6_7r6dcdn2_.arc
archived log for thread 1 with sequence 7 is already on disk as file /tmp/TEST/archivelog/2012_04_10/o1_mf_1_7_7r6dcfgs_.arc
archived log for thread 1 with sequence 8 is already on disk as file /tmp/TEST/archivelog/2012_04_10/o1_mf_1_8_7r6dcgko_.arc
archived log for thread 1 with sequence 9 is already on disk as file /tmp/TEST/archivelog/2012_04_10/o1_mf_1_9_7r6dcjdd_.arc
archived log file name=/tmp/TEST/archivelog/2012_04_10/o1_mf_1_6_7r6dcdn2_.arc thread=1 sequence=6
archived log file name=/tmp/TEST/archivelog/2012_04_10/o1_mf_1_7_7r6dcfgs_.arc thread=1 sequence=7
archived log file name=/tmp/TEST/archivelog/2012_04_10/o1_mf_1_8_7r6dcgko_.arc thread=1 sequence=8
archived log file name=/tmp/TEST/archivelog/2012_04_10/o1_mf_1_9_7r6dcjdd_.arc thread=1 sequence=9
media recovery complete, elapsed time: 00:00:00
Finished recover at 10-APR-12
RMAN> quit

Recovery Manager complete.
[oracle@test ~]$ exit
exit
SQL> alter database open resetlogs;
Database altered.
SQL> select * from test.test;
        ID NAME
---------- --------------------
         1 oraking
         2 yallonking
--以上说明当数据库闪回到之前的A时刻后，A之后的日志也是可以继续使用的。
总结：当数据库以resetlogs打开数据库后，日志序列重置，之前的备份仍然可用，但备份之后的日志需要分情况讨论。
 

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/26143577/viewspace-720847/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/26143577/viewspace-720847/

cuiqu7295
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
ORACLE 12c rac备份异机单实例恢复(RMAN recover database出现RMAN-06054)
Lucis_tomato的博客
11-26 2738
1.首先在源rac 环境创造 数据，任何能体现与恢复环境不同的情况都可以。 本次模拟环境的目标机器上有一个db名与rac库一致的单实例db简略部分步骤 insert into test.table1 values('2','B'); insert into test.table1 values('3','C'); commit; 2.对源库rac环境进行备份 #!/bin/sh export BACKUP_DATE=`date +%d` RMAN_LOG_FILE=/backup/backu.
RMAN恢复复制数据库报错RMAN-06054的分析
热门推荐
cloud952788的专栏
08-15 1万+
在使用recovery还原数据库或者rman复制数据库时，在备份中无法找到sequence就会报错RMAN-06054。解决方法： 说明:此处的sequence和thread概念 sequence是数据库日志递增的序列号，日志切换时会顺序递增 thread是instance id。单实例是1，rac环境中的话有1,2。。。 SCN是system change number 是跟随事务递
Oracle 12c-备份恢复学习实践手册合集
06-24
Oracle 12c 闪回技术 Flashback Database.pdf Oracle 12c 闪回技术 Oracle Flashback技术.pdf Oracle 12c 管理UNDO.pdf Oracle 12c 数据库备份和恢复概述.pdf Oracle 12c 用户管理的备份和恢复.pdf Oracle 12c SCN详解.pdf Oracle 12c RMAN备份与恢复数据库.pdf Oracle 12c EXPDP和IMPDP指令详解.pdf Oracle 12c EXP和IMP指令详解.pdf
RMAN-06054: 介质恢复正在请求未知的线程 1 序列 105776 的归档日志以及起始 SCN 62897768726
鲨鱼胃的博客
10-10 5438
问题描述 在做异机恢复（RAC->单实例）的时候，recover database时遇到如下报错： RMAN-03002: recover 命令 (在 09/30/2019 08:36:48 上) 失败 RMAN-06054: 介质恢复正在请求未知的线程 1 序列 105776 的归档日志以及起始 SCN 62897768726 在11g官方文档error messages中对错误描述如下：...
RMAN duplicate恢复数据库报错RMAN-06054问题处理
weixin_33701564的博客
12-23 386
最近生产上要搞大动作，需要把生产库备份每天都恢复到另外一台机器上，进行测试。于是想到了用DUPLIDATE的方式，简单方便，前期配置好目录，然后一条命令就可以把库恢复出来。于是写了恢复脚本，也通过了测试，而且生产上使用一切正常。但一次需要在测试环境恢复数据库时，使用该脚本却报错RMAN-06054。奇怪的是同样的备份在生产上的另一个环境已经成功恢复了。下面来看...
rman之resetlogs及恢复备份控制文件的一点理解
t0nsha's Blog
06-04 2329
版本:SQL> select * from v$version;BANNER--------------------------------------------------------------------------------Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit ProductionPL/SQL
RMAN备份整个数据库和归档日志时报错
linghao00的专栏
05-18 1169
Hi. I lost few previous archivelogs, and can't run "backup database plus archivelog;". That's what I got from rman: RMAN> backup database plus archivelog; Starting backup at 12-APR-09 current l
数据库ORA-01196故障-归档日志丢失恢复详解
09-09
4. **完成介质恢复**：使用`ALTER DATABASE OPEN RESETLOGS`命令打开数据库，这将创建新的重做日志组，并删除未应用的归档日志。 5. **验证一致性**：打开数据库后，使用`DBVERIFY`或`UTL_FILE`包进行数据文件一致...
Oracle数据库恢复教程之resetlogs操作
09-09
resetlogs选项在完成恢复后打开数据库，创建新的重做日志序列，这将导致数据库变为非当前版本。 首先，resetlogs操作应当谨慎处理。如果不确定操作的必要性，最好寻求资深DBA的帮助，避免因误操作导致数据丢失。在...
Oracle数据库备份整库
11-09
` 这会备份所有数据文件、控制文件和归档日志。 4. **备份初始化参数文件**：`backup spfile;` 5. **验证备份**：`validate backupset;` 确保备份文件的完整性和可恢复性。 6. **退出RMAN**：`exit;` 五、备份存储...
RMAN 关于恢复到过去的时间点
11-19
一、概述，RMAN基于SCN，TIMESTAMP的恢复，是作用于redo.log日志上面的。
RMAN技术在ORACLE 10g数据库中的应用.pdf
10-10
RMAN主要负责数据库的备份和恢复任务，能够有效地处理数据库文件、归档日志和控制文件的备份，同时也支持全面或部分的数据库恢复操作。 在Oracle 10g之前，虽然RMAN已经具备一定的功能，但在某些方面仍不能满足DBA...
Oracle 11g 基于RMAN的备份与恢复.docx
02-07
Oracle 11g 的备份与恢复是数据库管理中的关键环节，确保数据的安全性和可用性。在Oracle数据库中，恢复管理器（RMAN）是进行备份和恢复的主要工具。以下是对Oracle 11g基于RMAN的备份与恢复的详细说明： 1. 备份...
RMAN-06054错误解决办法
zuixinnet的专栏
04-08 1万+
RMAN> recover database;#会报错，但不要紧，我们只需要得到thread和sequence号就行 Starting recover at 20-JUL-11 using channel ORA_DISK_1 starting media recovery unable to find archive log archive log thread=1 sequence=
RMAN-06054 report duri…
babymouse1212的博客
05-02 1119
Symptoms: RMAN恢复时出现    RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 22488 and starting SCN of 10242830716955   RMAN> recover database; Starting recover at 02-O
Oracle rman恢复一
Allen_xiaofei的博客
05-29 432
当归档日志已开启，系统表空间以及控制文件被误删以后的处理，以下恢复只能恢复至归档文件的内容，已提交但还未写入归档文件的内容不会恢复（慎用）。处理：1、从归档目录下的控制文件恢复            restore controlfile from 'D:\oracle\rman\C-1504057855-20180529-02';         2、恢复数据库文件以及恢复介质         ...
oracle rman同时写入不同位置,Oracle RMAN 恢复数据库到不同主机（二）
weixin_36025345的博客
04-05 391
我们在recover database时报一个错误：RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 149 and starting SCN of 3507749这里是提醒恢复到一个未知的scn号。我们在备份时只有148号归档，149号还是online redo，所以没有co...
resetlogs后使用rman备份全库提示nas路径找不到
ckml77559的博客
07-27 200
由于开发需求要将测试库不完全恢复到某一个时间点，由于恢复时间较长于是脚本中只执行到recover这一步，等第二天上班在执行最后一步alter database open resetlogs。resetlogs成功后...
JDBC详细使用
最新发布
m0_73627305的博客
08-09 515
​ JDBC是一种标准,一种规则,主要作用是使用java语言操作数据库的​ JDBC这个标准中有很多的接口,接口中有很多方法。
DM8数据库误操作恢复：归档、备份与日志分析
确定了误操作的时间点后，可以根据备份和归档日志进行恢复。基本步骤如下： 1. 用备份文件还原数据库到误操作之前的一个时间点： ```sql RESTOREDATABASEFROM'/dm8/backup/fullback_DAMENG_0325'; ``` 2. 使用redo...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值