重建控制文件,并且不干净的关闭数据库测试

简介: 重建控制文件,并且不干净的关闭数据库测试: 数据库SHUTDOWN ABORT,删除CONTROLFILE SQL> startup nomount;ORACLE instance started.

重建控制文件,并且不干净的关闭数据库测试:

数据库SHUTDOWN ABORT,删除CONTROLFILE

SQL> startup nomount;
ORACLE instance started.

Total System Global Area  419430400 bytes
Fixed Size                  2021248 bytes
Variable Size             171968640 bytes
Database Buffers          243269632 bytes
Redo Buffers                2170880 bytes
SQL> CREATE CONTROLFILE REUSE DATABASE "XUEXI" RESETLOGS  ARCHIVELOG
  2      MAXLOGFILES 16
  3      MAXLOGMEMBERS 3
  4      MAXDATAFILES 100
  5      MAXINSTANCES 8
  6      MAXLOGHISTORY 292
  7  LOGFILE
  8    GROUP 1 '/oradata/xuexi/redo01.log'  SIZE 50M,
  9    GROUP 2 '/oradata/xuexi/redo02.log'  SIZE 50M,
 10    GROUP 3 '/oradata/xuexi/redo03.log'  SIZE 50M,
 11    GROUP 4 '/oradata/XUEXI/onlinelog/o1_mf_4_8yqwxqsh_.log'  SIZE 50M,
 12    GROUP 5 (
 13      '/oradata/XUEXI/onlinelog/o1_mf_5_8yqx1d59_.log',
 14      '/oradata/XUEXI/onlinelog/o1_mf_5_8yqx1gvx_.log'
 15    ) SIZE 50M,
 16    GROUP 7 (
 17      '/oradata/XUEXI/onlinelog/o1_mf_7_8zl9m1ro_.log',
 18      '/oradata/XUEXI/onlinelog/o1_mf_7_8zl9m3gj_.log',
 19      '/oradata/logfile07.log'
 20    ) SIZE 100M
 21  -- STANDBY LOGFILE
 22  DATAFILE
 23    '/oradata/xuexi/system01.dbf',
 24    '/oradata/xuexi/undotbs01.dbf',
 25    '/oradata/xuexi/sysaux01.dbf',
 26    '/oradata/xuexi/users01.dbf',
 27    '/oradata/xuexi/XUEXI/datafile/o1_mf_tomf_8yqwrdoj_.dbf',
 28    '/oradata/xuexi/omf2.dbf',
 29    '/oradata/xuexi/XUEXI/datafile/testimp01.dbf',
 30    '/oradata/xuexi/XUEXI/datafile/testimp011.dbf',
 31    '/oradata/xuexi/XUEXI/datafile/testo1.dbf',
 32    '/oradata/xuexi/XUEXI/datafile/testo2.dbf'
 33  CHARACTER SET AL32UTF8
 34  ;

Control file created.

SQL> alter database mount;
alter database mount
*
ERROR at line 1:
ORA-01100: database already mounted


SQL> recover database ;
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done

 

SQL> RECOVER DATABASE USING BACKUP CONTROLFILE;
ORA-00279: change 1917689 generated at 10/04/2013 21:15:57 needed for thread 1
ORA-00289: suggestion : /archive/1_102_822387818.dbf
ORA-00280: change 1917689 for thread 1 is in sequence #102


Specify log: {=suggested | filename | AUTO | CANCEL}
auto
ORA-00308: cannot open archived log '/archive/1_102_822387818.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3


ORA-00308: cannot open archived log '/archive/1_102_822387818.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory

显然这里缺少102这个归档,因为他是当前日志文件,所以我们需要把日志复制到归档目录下,但是那个日志是102呢,这样就可以确定
[oracle@localhost bdump]$ tail -n 4000 alert_xuexi.log |grep Current
  Current log# 4 seq# 100 mem# 0: /oradata/XUEXI/onlinelog/o1_mf_4_8yqwxqsh_.log
  Current log# 4 seq# 100 mem# 0: /oradata/XUEXI/onlinelog/o1_mf_4_8yqwxqsh_.log
  Current log# 5 seq# 101 mem# 0: /oradata/XUEXI/onlinelog/o1_mf_5_8yqx1d59_.log
  Current log# 5 seq# 101 mem# 1: /oradata/XUEXI/onlinelog/o1_mf_5_8yqx1gvx_.log
  Current log# 7 seq# 102 mem# 0: /oradata/XUEXI/onlinelog/o1_mf_7_8zl9m1ro_.log
  Current log# 7 seq# 102 mem# 1: /oradata/XUEXI/onlinelog/o1_mf_7_8zl9m3gj_.log
  Current log# 7 seq# 102 mem# 2: /oradata/logfile07.log
  可以确认/oradata/logfile07.log就是需要的归档
cp /oradata/logfile07.log /archive/1_102_822387818.dbf

SQL> recover database using backup controlfile
ORA-00279: change 1917689 generated at 10/04/2013 21:15:57 needed for thread 1
ORA-00289: suggestion : /archive/1_102_822387818.dbf
ORA-00280: change 1917689 for thread 1 is in sequence #102

Specify log: {=suggested | filename | AUTO | CANCEL}
AUTO
完成后即可
当然也快手动输入你确认的当前归档如下:
SQL> recover database using backup controlfile
ORA-00279: change 1917689 generated at 10/04/2013 21:15:57 needed for thread 1
ORA-00289: suggestion : /archive/1_102_822387818.dbf
ORA-00280: change 1917689 for thread 1 is in sequence #102

Specify log: {=suggested | filename | AUTO | CANCEL}
/oradata/logfile07.log
Log applied.
Media recovery complete.
SQL> alter database open resetlogs;

SQL> alter database open resetlogs;

Database altered.
Log applied.
Media recovery complete.


alter database backup controlfile to trace 全文
/opt/oracle/admin/xuexi/udump/xuexi_ora_5686.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /opt/oracle/product/10.2.0/db_1
System name:    Linux
Node name:      localhost.localdomain
Release:        2.6.18-164.el5
Version:        #1 SMP Tue Aug 18 15:51:48 EDT 2009
Machine:        x86_64
Instance name: xuexi
Redo thread mounted by this instance: 1
Oracle process number: 18
Unix process pid: 5686, image: oracle@localhost.localdomain (TNS V1-V3)

*** SERVICE NAME:(SYS$USERS) 2013-10-04 21:38:20.304
*** SESSION ID:(146.91) 2013-10-04 21:38:20.304
*** 2013-10-04 21:38:20.304
-- The following are current System-scope REDO Log Archival related
-- parameters and can be included in the database initialization file.
--
-- LOG_ARCHIVE_DEST=''
-- LOG_ARCHIVE_DUPLEX_DEST=''
--
-- LOG_ARCHIVE_FORMAT=%t_%s_%r.dbf
--
-- DB_UNIQUE_NAME="xuexi"
--
-- LOG_ARCHIVE_CONFIG='SEND, RECEIVE, NODG_CONFIG'
-- LOG_ARCHIVE_MAX_PROCESSES=2
-- STANDBY_FILE_MANAGEMENT=MANUAL
-- STANDBY_ARCHIVE_DEST=?/dbs/arch
-- FAL_CLIENT=''
-- FAL_SERVER=''
--
-- LOG_ARCHIVE_DEST_1='LOCATION=/archive'
-- LOG_ARCHIVE_DEST_1='OPTIONAL REOPEN=300 NODELAY'
-- LOG_ARCHIVE_DEST_1='ARCH NOAFFIRM NOEXPEDITE NOVERIFY SYNC'
-- LOG_ARCHIVE_DEST_1='REGISTER NOALTERNATE NODEPENDENCY'
-- LOG_ARCHIVE_DEST_1='NOMAX_FAILURE NOQUOTA_SIZE NOQUOTA_USED NODB_UNIQUE_NAME'
-- LOG_ARCHIVE_DEST_1='VALID_FOR=(PRIMARY_ROLE,ONLINE_LOGFILES)'
-- LOG_ARCHIVE_DEST_STATE_1=ENABLE
--
-- Below are two sets of SQL statements, each of which creates a new
-- control file and uses it to open the database. The first set opens
-- the database with the NORESETLOGS option and should be used only if
-- the current versions of all online logs are available. The second
-- set opens the database with the RESETLOGS option and should be used
-- if online logs are unavailable.
-- The appropriate set of statements can be copied from the trace into
-- a script. file, edited as necessary, and executed when there is a
-- need to re-create the control file.
--
--     Set #1. NORESETLOGS case
--
-- The following commands will create a new control file and use it
-- to open the database.
-- Data used by Recovery Manager will be lost.
-- Additional logs may be required for media recovery of offline
-- Use this only if the current versions of all online logs are
-- available.
-- After mounting the created controlfile, the following SQL
-- statement will place the database in the appropriate
-- protection mode:
--  ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "XUEXI" NORESETLOGS  ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 292
LOGFILE
  GROUP 1 '/oradata/xuexi/redo01.log'  SIZE 50M,
  GROUP 2 '/oradata/xuexi/redo02.log'  SIZE 50M,
  GROUP 3 '/oradata/xuexi/redo03.log'  SIZE 50M,
  GROUP 4 '/oradata/XUEXI/onlinelog/o1_mf_4_8yqwxqsh_.log'  SIZE 50M,
  GROUP 5 (
    '/oradata/XUEXI/onlinelog/o1_mf_5_8yqx1d59_.log',
    '/oradata/XUEXI/onlinelog/o1_mf_5_8yqx1gvx_.log'
  ) SIZE 50M,
  GROUP 7 (
    '/oradata/XUEXI/onlinelog/o1_mf_7_8zl9m1ro_.log',
    '/oradata/XUEXI/onlinelog/o1_mf_7_8zl9m3gj_.log',
    '/oradata/logfile07.log'
  ) SIZE 100M
-- STANDBY LOGFILE
DATAFILE
  '/oradata/xuexi/system01.dbf',
  '/oradata/xuexi/undotbs01.dbf',
  '/oradata/xuexi/sysaux01.dbf',
  '/oradata/xuexi/users01.dbf',
  '/oradata/xuexi/XUEXI/datafile/o1_mf_tomf_8yqwrdoj_.dbf',
  '/oradata/xuexi/omf2.dbf',
  '/oradata/xuexi/XUEXI/datafile/testimp01.dbf',
  '/oradata/xuexi/XUEXI/datafile/testimp011.dbf',
  '/oradata/xuexi/XUEXI/datafile/testo1.dbf',
  '/oradata/xuexi/XUEXI/datafile/testo2.dbf'
CHARACTER SET AL32UTF8
;
-- Commands to re-create incarnation table
-- Below log names MUST be changed to existing filenames on
-- disk. Any one log file from each branch can be used to
-- re-create incarnation records.
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822350387.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822350760.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822330757.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822350003.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822349246.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822350252.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822374325.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822387818.dbf';
-- Recovery is required if any of the datafiles are restored backups,
-- or if the last shutdown was not normal or immediate.
RECOVER DATABASE
-- All logs need archiving and a log switch is needed.
ALTER SYSTEM ARCHIVE LOG ALL;
-- Database can now be opened normally.
ALTER DATABASE OPEN;
-- Commands to add tempfiles to temporary tablespaces.
-- Online tempfiles have complete space information.
-- Other tempfiles may require adjustment.
ALTER TABLESPACE TEMP1 ADD TEMPFILE '/oradata/xuexi/temp011.dbf'
     SIZE 19922944  REUSE AUTOEXTEND ON NEXT 8192  MAXSIZE 5120M;
-- End of tempfile additions.
--
--     Set #2. RESETLOGS case
--
-- The following commands will create a new control file and use it
-- to open the database.
-- Data used by Recovery Manager will be lost.
-- The contents of online logs will be lost and all backups will
-- be invalidated. Use this only if online logs are damaged.
-- After mounting the created controlfile, the following SQL
-- statement will place the database in the appropriate
-- protection mode:
--  ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "XUEXI" RESETLOGS  ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 292
LOGFILE
  GROUP 1 '/oradata/xuexi/redo01.log'  SIZE 50M,
  GROUP 2 '/oradata/xuexi/redo02.log'  SIZE 50M,
  GROUP 3 '/oradata/xuexi/redo03.log'  SIZE 50M,
  GROUP 4 '/oradata/XUEXI/onlinelog/o1_mf_4_8yqwxqsh_.log'  SIZE 50M,
  GROUP 5 (
    '/oradata/XUEXI/onlinelog/o1_mf_5_8yqx1d59_.log',
    '/oradata/XUEXI/onlinelog/o1_mf_5_8yqx1gvx_.log'
  ) SIZE 50M,
  GROUP 7 (
    '/oradata/XUEXI/onlinelog/o1_mf_7_8zl9m1ro_.log',
    '/oradata/XUEXI/onlinelog/o1_mf_7_8zl9m3gj_.log',
    '/oradata/logfile07.log'
  ) SIZE 100M
-- STANDBY LOGFILE
DATAFILE
  '/oradata/xuexi/system01.dbf',
  '/oradata/xuexi/undotbs01.dbf',
  '/oradata/xuexi/sysaux01.dbf',
  '/oradata/xuexi/users01.dbf',
  '/oradata/xuexi/XUEXI/datafile/o1_mf_tomf_8yqwrdoj_.dbf',
  '/oradata/xuexi/omf2.dbf',
  '/oradata/xuexi/XUEXI/datafile/testimp01.dbf',
  '/oradata/xuexi/XUEXI/datafile/testimp011.dbf',
  '/oradata/xuexi/XUEXI/datafile/testo1.dbf',
  '/oradata/xuexi/XUEXI/datafile/testo2.dbf'
CHARACTER SET AL32UTF8
;
-- Commands to re-create incarnation table
-- Below log names MUST be changed to existing filenames on
-- disk. Any one log file from each branch can be used to
-- re-create incarnation records.
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822350387.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822350760.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822330757.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822350003.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822349246.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822350252.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822374325.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822387818.dbf';
-- Recovery is required if any of the datafiles are restored backups,
-- or if the last shutdown was not normal or immediate.
RECOVER DATABASE USING BACKUP CONTROLFILE
-- Database can now be opened zeroing the online logs.
ALTER DATABASE OPEN RESETLOGS;
-- Commands to add tempfiles to temporary tablespaces.
-- Online tempfiles have complete space information.
-- Other tempfiles may require adjustment.
ALTER TABLESPACE TEMP1 ADD TEMPFILE '/oradata/xuexi/temp011.dbf'
     SIZE 19922944  REUSE AUTOEXTEND ON NEXT 8192  MAXSIZE 5120M;
-- End of tempfile additions.
--

相关文章
|
19天前
|
机器学习/深度学习 算法 异构计算
m基于FPGA的多通道FIR滤波器verilog实现,包含testbench测试文件
本文介绍了使用VIVADO 2019.2仿真的多通道FIR滤波器设计。展示了系统RTL结构图,并简述了FIR滤波器的基本理论,包括单通道和多通道的概念、常见结构及设计方法,如窗函数法、频率采样法、优化算法和机器学习方法。此外,还提供了Verilog核心程序代码,用于实现4通道滤波器模块,包含时钟、复位信号及输入输出接口的定义。
38 7
|
2月前
|
Kubernetes 关系型数据库 MySQL
ChaosBlade常见问题之数据库进行故障注入报错ibdata1文件异常如何解决
ChaosBlade 是一个开源的混沌工程实验工具,旨在通过模拟各种常见的硬件、软件、网络、应用等故障,帮助开发者在测试环境中验证系统的容错和自动恢复能力。以下是关于ChaosBlade的一些常见问题合集:
27 1
|
2月前
|
监控 关系型数据库 数据库
OceanBase数据库常见问题之文件存在但是数据库提示文件不存在如何解决
OceanBase 是一款由阿里巴巴集团研发的企业级分布式关系型数据库,它具有高可用、高性能、可水平扩展等特点。以下是OceanBase 数据库使用过程中可能遇到的一些常见问题及其解答的汇总,以帮助用户更好地理解和使用这款数据库产品。
|
2月前
|
XML 关系型数据库 MySQL
【Mysql】有关数据库中一对多/一对一,多对一xml中文件映射问题
【Mysql】有关数据库中一对多/一对一,多对一xml中文件映射问题
19 0
|
1月前
|
JSON 关系型数据库 数据库
【python】Python将100个PDF文件对应的json文件存储到MySql数据库(源码)【独一无二】
【python】Python将100个PDF文件对应的json文件存储到MySql数据库(源码)【独一无二】
【python】Python将100个PDF文件对应的json文件存储到MySql数据库(源码)【独一无二】
|
1月前
|
JSON 关系型数据库 数据库
【python】Python将100个PDF文件对应的json文件存储到MySql数据库(源码)【独一无二】
【python】Python将100个PDF文件对应的json文件存储到MySql数据库(源码)【独一无二】
|
2月前
|
传感器 算法 计算机视觉
基于肤色模型和中值滤波的手部检测算法FPGA实现,包括tb测试文件和MATLAB辅助验证
该内容是关于一个基于肤色模型和中值滤波的手部检测算法的描述,包括算法的运行效果图和所使用的软件版本(matlab2022a, vivado2019.2)。算法分为肤色分割和中值滤波两步,其中肤色模型在YCbCr色彩空间定义,中值滤波用于去除噪声。提供了一段核心程序代码,用于处理图像数据并在FPGA上实现。最终,检测结果输出到"hand.txt"文件。
|
3天前
|
SQL 存储 小程序
数据库数据恢复—Sql Server数据库文件丢失的数据恢复案例
数据库数据恢复环境: 5块硬盘组建一组RAID5阵列,划分LUN供windows系统服务器使用。windows系统服务器内运行了Sql Server数据库,存储空间在操作系统层面划分了三个逻辑分区。 数据库故障: 数据库文件丢失,主要涉及3个数据库,数千张表。数据库文件丢失原因未知,不能确定丢失的数据库文件的存放位置。数据库文件丢失后,服务器仍处于开机状态,所幸未写入大量数据。
数据库数据恢复—Sql Server数据库文件丢失的数据恢复案例
|
8天前
|
算法 异构计算
基于直方图的图像曝光量分析FPGA实现,包含tb测试文件和MATLAB辅助验证
该内容包括了算法的运行效果展示、软件版本信息、理论概述和核心程序代码。在正常图像中,`checkb`位于`f192b`和`f250b`之间,而多度曝光图像中`checkb`超出此范围,判断为曝光过度。使用的软件为Vivado 2019.2和MATLAB 2022a。理论依据未详细给出,但提及主要方法。提供的Verilog代码段用于处理图像数据,包括读取文件、时钟控制及图像histogram计算等,其中模块`im_hist`似乎是关键部分。
|
10天前
|
存储 大数据 测试技术
矢量数据库的性能测试与评估方法
【4月更文挑战第30天】本文探讨了矢量数据库的性能测试与评估方法,强调其在大数据和AI时代的重要性。文中介绍了负载测试、压力测试、容量测试、功能测试和稳定性测试五大评估方法,以及实施步骤,包括确定测试目标、设计用例、准备环境、执行测试和分析结果。这些方法有助于确保数据库的稳定性和高效性,推动技术发展。