恢复控制文件后如何避免resetlogs打开数据库？-益强IT技术网

当前位置：当前位置：首页 >域名 >恢复控制文件后如何避免resetlogs打开数据库？正文

恢复控制文件后如何避免resetlogs打开数据库？

[域名] 时间：2025-11-05 11:47:36 来源：益强IT技术网作者：应用开发点击：75次

恢复控制文件后，恢复后何数据库使用resetlogs方式打开，控制开数在线日志的文件序列被重置。

SYS@practice >select group#,避免sequence#,archived,status,first_change#,next_change# from v$log; GROUP# SEQUENCE# ARC STATUS FIRST_CHANGE# NEXT_CHANGE# ---------- ---------- --- ---------------- ------------- ------------ 1 1 NO CURRENT 1014415 2.8147E+14 2 0 YES UNUSED 0 0 3 0 YES UNUSED 0 0

如果没有被resetlog截断的话当前日志的序列号应该是7，8，据库9

SYS@practice >select recid,恢复后何sequence#,first_change#,next_change# from v$log_history; RECID SEQUENCE# FIRST_CHANGE# NEXT_CHANGE# ---------- ---------- ------------- ------------ 1 1 925702 955284 2 2 955284 955847 3 3 955847 971151 4 4 971151 987800 5 5 987800 997957 6 6 997957 1010981 7 1 1010981 1013463 8 2 1013463 1013471 9 3 1013471 1014415

如果恢复完控制文件，不使用resetlogs是控制开数打不开数据库的。

我们可以采取手工创建控制文件的文件方法打开数据库，免费信息发布网保持联机日志的避免sequence#连续。下面的据库实验来演示具体操作过程。

在实验之前先手工切换3次日志，恢复后何使得在线日志的控制开数序列号产生变化。在恢复结束后作为参考。文件

SYS@practice >alter system archive log current; SYS@practice >alter system archive log current; SYS@practice >alter system archive log current;

切换后当前连接日志状态如下

SYS@practice >select group#,避免sequence#,archived,status,first_change#,next_change# from v$log; GROUP# SEQUENCE# ARC STATUS FIRST_CHANGE# NEXT_CHANGE# ---------- ---------- --- ---------------- ------------- ------------ 1 4 NO CURRENT 1030130 2.8147E+14 2 2 YES INACTIVE 1030109 1030117 3 3 YES ACTIVE 1030117 1030130

1、恢复控制文件

RMAN> startup force nomount; Oracle instance started Total System Global Area 580395008 bytes Fixed Size 2255392 bytes Variable Size 402654688 bytes Database Buffers 171966464 bytes Redo Buffers 3518464 bytes RMAN> restore controlfile from autobackup; Starting restore at 06-OCT-14 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=19 device type=DISK recovery area destination: /u01/fast_recovery_area database name (or database unique name) used for search: PRACTICE channel ORA_DISK_1: AUTOBACKUP /u01/fast_recovery_area/PRACTICE/autobackup/2014_10_06/o1_mf_s_860251717_b35s05gm_.bkp found in the recovery area channel ORA_DISK_1: looking for AUTOBACKUP on day: 20141006 channel ORA_DISK_1: restoring control file from AUTOBACKUP /u01/fast_recovery_area/PRACTICE/autobackup/2014_10_06/o1_mf_s_860251717_b35s05gm_.bkp channel ORA_DISK_1: control file restore from AUTOBACKUP complete output file name=/u01/oradata/practice/control01.ctl output file name=/u01/fast_recovery_area/practice/control02.ctl Finished restore at 06-OCT-14

2、据库启动数据库到mount状态

RMAN> mount database; database mounted released channel: ORA_DISK_1

3、恢复数据库

RMAN> recover database; Starting recover at 06-OCT-14 Starting implicit crosscheck backup at 06-OCT-14 allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=20 device type=DISK Crosschecked 6 objects Finished implicit crosscheck backup at 06-OCT-14 Starting implicit crosscheck copy at 06-OCT-14 using channel ORA_DISK_1 Finished implicit crosscheck copy at 06-OCT-14 searching for all files in the recovery area cataloging files... cataloging done List of Cataloged Files ======================= File Name: /u01/fast_recovery_area/PRACTICE/archivelog/2014_10_06/o1_mf_1_1_b362kndr_.arc File Name: /u01/fast_recovery_area/PRACTICE/archivelog/2014_10_06/o1_mf_1_3_b362lc83_.arc File Name: /u01/fast_recovery_area/PRACTICE/archivelog/2014_10_06/o1_mf_1_2_b362l34q_.arc File Name: /u01/fast_recovery_area/PRACTICE/autobackup/2014_10_06/o1_mf_s_860251717_b35s05gm_.bkp File Name: /u01/fast_recovery_area/PRACTICE/autobackup/2014_10_06/o1_mf_s_860251162_b35rgt84_.bkp File Name: /u01/fast_recovery_area/PRACTICE/autobackup/2014_10_06/o1_mf_s_860251158_b35rgpms_.bkp File Name: /u01/fast_recovery_area/PRACTICE/autobackup/2014_10_06/o1_mf_s_860246909_b35n9x55_.bkp using channel ORA_DISK_1 starting media recovery archived log for thread 1 with sequence 1 is already on disk as file /u01/fast_recovery_area/PRACTICE/archivelog/2014_10_06/o1_mf_1_1_b362kndr_.arc archived log for thread 1 with sequence 2 is already on disk as file /u01/fast_recovery_area/PRACTICE/archivelog/2014_10_06/o1_mf_1_2_b362l34q_.arc archived log for thread 1 with sequence 3 is already on disk as file /u01/fast_recovery_area/PRACTICE/archivelog/2014_10_06/o1_mf_1_3_b362lc83_.arc archived log for thread 1 with sequence 4 is already on disk as file /u01/oradata/practice/redo01.log archived log file name=/u01/fast_recovery_area/PRACTICE/archivelog/2014_10_06/o1_mf_1_1_b362kndr_.arc thread=1 sequence=1 archived log file name=/u01/fast_recovery_area/PRACTICE/archivelog/2014_10_06/o1_mf_1_2_b362l34q_.arc thread=1 sequence=2 archived log file name=/u01/fast_recovery_area/PRACTICE/archivelog/2014_10_06/o1_mf_1_3_b362lc83_.arc thread=1 sequence=3 archived log file name=/u01/oradata/practice/redo01.log thread=1 sequence=4 media recovery complete, elapsed time: 00:00:00 Finished recover at 06-OCT-14

4，备份控制文件到trace

SYS@practice >select open_mode from v$database; OPEN_MODE -------------------- MOUNTED SYS@practice >alter database backup controlfile to trace; SYS@practice >select value from v$diag_info where name=Default Trace File; VALUE -------------------------------------------------------------------------------- /u01/diag/rdbms/practice/practice/trace/practice_ora_1185.trc

5、重启实例到nomount状态

6、云服务器执行重建控制文件命令进入到mount状态

vi /home/oracle/create_controlfile.sql STARTUP NOMOUNT CREATE CONTROLFILE REUSE DATABASE "PRACTICE" NORESETLOGS ARCHIVELOG MAXLOGFILES 16 MAXLOGMEMBERS 3 MAXDATAFILES 100 MAXINSTANCES 8 MAXLOGHISTORY 292 LOGFILE GROUP 1 /u01/oradata/practice/redo01.log SIZE 50M BLOCKSIZE 512, GROUP 2 /u01/oradata/practice/redo02.log SIZE 50M BLOCKSIZE 512, GROUP 3 /u01/oradata/practice/redo03.log SIZE 50M BLOCKSIZE 512 DATAFILE /u01/oradata/practice/system01.dbf, /u01/oradata/practice/sysaux01.dbf, /u01/oradata/practice/undotbs01.dbf, /u01/oradata/practice/users01.dbf, /u01/oradata/practice/example01.dbf CHARACTER SET AL32UTF8 ; VARIABLE RECNO NUMBER; EXECUTE :RECNO := SYS.DBMS_BACKUP_RESTORE.SETCONFIG(CONTROLFILE AUTOBACKUP,ON); RECOVER DATABASE ALTER SYSTEM ARCHIVE LOG ALL; ALTER DATABASE OPEN; ALTER TABLESPACE TEMP ADD TEMPFILE /u01/oradata/practice/temp01.dbf REUSE;

在sqlplus下执行创建控制文件脚本，数据库会启动到open状态并添加临时表空间文件。

SYS@practice >@create_controlfile.sql Control file created. PL/SQL procedure successfully completed. Media recovery complete. System altered. Database altered. Tablespace altered.

此时数据库已经处于read write状态也就是open状态了

SYS@practice >select open_mode from v$database; OPEN_MODE -------------------- READ WRITE

查看当前日志的序列号，没有被重置。

SYS@practice >select group#,sequence#,archived,status,first_change#,next_change# from v$log; GROUP# SEQUENCE# ARC STATUS FIRST_CHANGE# NEXT_CHANGE# ---------- ---------- --- ---------------- ------------- ------------ 1 4 YES INACTIVE 1030130 1050296 2 5 NO CURRENT 1050296 2.8147E+14 3 3 YES INACTIVE 1030117 1030130

查看临时表数据文件也被创建出来了。

SYS@practice >select name from v$tempfile; NAME -------------------------------------------------------------------------------- /u01/oradata/practice/temp01.dbf

7，重新识别控制文件的备份信息和配置信息

此时的控制文件中没有之前备份过控制文件的信息

RMAN> list backup of controlfile; using target database control file instead of recovery catalog specification does not match any backup in the repository

从闪回恢复区重新注册备份信息

RMAN> catalog db_recovery_file_dest;

从执行过数据库全备份的地址注册备份信息

RMAN> catalog start with /home/oracle/;

再次列出备份过的控制文件，亿华云可以看到已经全部注册成功

RMAN> list backup of controlfile; List of Backup Sets =================== BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 1 Full 9.67M DISK 00:00:00 06-OCT-14 BP Key: 1 Status: AVAILABLE Compressed: NO Tag: TAG20141006T175610 Piece Name: /u01/fast_recovery_area/PRACTICE/autobackup/2014_10_06/o1_mf_s_860262970_b363zt2x_.bkp Control File Included: Ckp SCN: 1051644 Ckp time: 06-OCT-14 BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 3 Full 9.33M DISK 00:00:00 06-OCT-14 BP Key: 3 Status: AVAILABLE Compressed: NO Tag: TAG20141006T132827 Piece Name: /u01/fast_recovery_area/PRACTICE/backupset/2014_10_06/o1_mf_ncnnf_TAG20141006T132827_b35n9w39_.bkp Control File Included: Ckp SCN: 1005439 Ckp time: 06-OCT-14 BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 7 Full 9.33M DISK 00:00:00 06-OCT-14 BP Key: 7 Status: AVAILABLE Compressed: NO Tag: TAG20141006T143909 Piece Name: /home/oracle/full_PRACTICE_9_20141006_1.bak Control File Included: Ckp SCN: 1013438 Ckp time: 06-OCT-14

(责任编辑：IT科技类资讯)

解决电脑开机问题之CMOS信息错误（排查和修复CMOS信息错误导致的无法开机故障）当你想重装Ubuntu或者仅仅是想安装它的一个新版本的时候，假如有个便捷的方法来重新安装之前的应用并且重置其设置会很方便的。此时 Aptik 粉墨登场，它可以帮助你轻松实现。Aptik（自动包备份和恢复）是一个可以用在Ubuntu，Linux Mint 和其他基于Debian以及Ubuntu的Linux发行版上的应用，它允许你将已经安装过的包括软件库、下载包、安装的应用和主题、用户设置在内的PPAs(个人软件包存档)备份到外部的U盘、网络存储或者类似于Dropbox的云服务上。注意：当我们在此文章中说到输入某些东西的时候，假如被输入的内容被引号包裹，请不要将引号一起输入进去，除非我们有特殊说明。想要安装Aptik，需要先添加其PPA。使用Ctrl + Alt + T快捷键打开一个新的终端窗口。输入以下文字，并按回车执行。复制代码代码如下:sudo apt-get update更新完毕后，你就完成了安装Aptik的准备工作。接下来输入以下命令并按回车：复制代码代码如下:sudo apt-get install aptik注意：你可能会看到一些有关于获取不到包更新的错误提示。不过别担心，假如这些提示看起来跟下边图片中类似的话，你的Aptik的安装就没有任何问题。安装过程会被显示出来。其中一个被显示出来的消息会提到此次安装会使用掉多少磁盘空间，然后提示你是否要继续，按下“y”再按回车，继续安装。当安装完成后，输入“Exit”并按回车或者按下左上角的“X”按钮，关闭终端窗口。在正式运行Aptik前，你需要设置好备份目录到一个U盘、网络驱动器或者类似于Dropbox和Google Drive的云帐号上。这儿的例子中，我们使用的是Dropbox。一旦设置好备份目录，点击启动栏上方的“Search”按钮。在搜索框中键入 “aptik”。结果会随着你的输入显示出来。当Aptik图标显示出来的时候，点击它打开应用。此时一个对话框会显示出来要求你输入密码。输入你的密码并按“OK”按钮。Aptik的主窗口显示出来了。从“Backup Directory”下拉列表中选择“Other…”。这个操作允许你选择你已经建立好的备份目录。注意：在下拉列表的右侧的 “Open” 按钮会在一个文件管理窗口中打开选择目录功能。在 “Backup Directory” 对话窗口中，定位到你的备份目录，然后按“Open”。注意：假如此时你尚未建立备份目录或者想在备份目录中新建个子目录，你可以点“Create Folder”来新建目录。点击“Software Sources (PPAs).”右侧的 “Backup”来备份已安装的PPAs。然后“Backup Software Sources”对话窗口显示出来。已安装的包和对应的源（PPA）同时也显示出来了。选择你需要备份的源（PPAs），或者点“Select All”按钮选择所有源。点击 “Backup” 开始备份。备份完成后，一个提示你备份完成的对话窗口会蹦出来。点击 “OK” 关掉。一个名为“ppa.list”的文件出现在了备份目录中。