如果光是INACTIVE状态的redo损坏,有三种方法可以恢复: 1.clear logfile 相关命令: alter database clear logfile
如果光是INACTIVE状态的redo损坏,有三种方法可以恢复:
1.clear logfile
相关命令:
alter database clear logfile '/database/oradata/skyread/redo04.log'; --已经归档的操作
alter database clear unarchived logfile '/database/oradata/skyread/redo04.log'; --inactive未归档的操作
2.不完全恢复until cancel
启动到mount状态运行recover database until cancel;
3.重建控制文件resetlogs方法
采用重建控制文件脚本resetlogs的方式重建,应用相关redo,完成介质恢复,resetlogs不检查日志文件,,所以不会报错
活动的在线日志损坏而且异常关闭的恢复:
SQL> alter database backup controlfile to trace as '/home/Oracle/ctl.sql' reuse resetlogs;
Database altered.
SQL> create table t1 as select * from dba_objects;
Table created.
SQL> select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIME
---------------- ---------------- ---------------- ---------------- ---------------- --- ---------------- ---------------- -------------------
1 1 31 536870912 1 YES INACTIVE 122695597193 2013-05-29 14:41:24
2 1 32 536870912 1 YES INACTIVE 122695676280 2013-05-31 13:38:04
3 1 29 536870912 1 YES INACTIVE 122695590894 2013-05-29 10:29:29
4 1 33 536870912 1 YES ACTIVE 122695698110 2013-05-31 14:15:47
5 1 34 536870912 1 NO CURRENT 122695861946 2013-06-04 13:48:31
破坏活动归档的日志文件,破坏控制文件,异常关机:
SQL> shutdown abort;
ORACLE instance shut down.
启动到mount状态时报错:
SQL> startup;
ORACLE instance started.
Total System Global Area 5049942016 bytes
Fixed Size 2090880 bytes
Variable Size 1375733888 bytes
Database Buffers 3657433088 bytes
Redo Buffers 14684160 bytes
ORA-00205: error in identifying control file, check alert log for more info
重建控制文件,注意如果是noresetlogs是不成功的,这里由于redo04.log损坏,只能采用resetlogs,不检查日志文件
SQL> CREATE CONTROLFILE REUSE DATABASE "SKYREAD" NORESETLOGS FORCE LOGGING ARCHIVELOG
2 MAXLOGFILES 20
3 MAXLOGMEMBERS 5
4 MAXDATAFILES 1000
5 MAXINSTANCES 8
6 MAXLOGHISTORY 2337
7 LOGFILE
8 GROUP 1 '/database/oradata/skyread/redo01.log' SIZE 512M,
9 GROUP 2 '/database/oradata/skyread/redo02.log' SIZE 512M,
10 GROUP 3 '/database/oradata/skyread/redo03.log' SIZE 512M,
11 GROUP 4 '/database/oradata/skyread/redo04.log' SIZE 512M,
12 GROUP 5 '/database/oradata/skyread/redo05.log' SIZE 512M
13 DATAFILE
14 '/database/oradata/skyread/system01.dbf',
15 '/database/oradata/skyread/tbs_test.dbf',
16 '/database/oradata/skyread/sysaux01.dbf',
17 '/database/oradata/skyread/users01.dbf',
18 '/database/oradata/skyread/system02.dbf',
19 '/database2/oradata/skyread/undotbs02.dbf',
20 '/database2/oradata/skyread/TBS_MRPMUSIC01.dbf',
21 '/database/oradata/skyread/sf01.dbf'
22 CHARACTER SET UTF8;
CREATE CONTROLFILE REUSE DATABASE "SKYREAD" NORESETLOGS FORCE LOGGING ARCHIVELOG
*
ERROR at line 1:
ORA-01503: CREATE CONTROLFILE failed
ORA-01565: error in identifying file '/database/oradata/skyread/redo04.log'
ORA-27046: file size is not a multiple of logical block size
Additional information: 1
SQL> CREATE CONTROLFILE REUSE DATABASE "SKYREAD" RESETLOGS FORCE LOGGING ARCHIVELOG
2 MAXLOGFILES 20
3 MAXLOGMEMBERS 5
4 MAXDATAFILES 1000
5 MAXINSTANCES 8
6 MAXLOGHISTORY 2337
7 LOGFILE
8 GROUP 1 '/database/oradata/skyread/redo01.log' SIZE 512M,
9 GROUP 2 '/database/oradata/skyread/redo02.log' SIZE 512M,
10 GROUP 3 '/database/oradata/skyread/redo03.log' SIZE 512M,
11 GROUP 4 '/database/oradata/skyread/redo04.log' SIZE 512M,
12 GROUP 5 '/database/oradata/skyread/redo05.log' SIZE 512M
13 DATAFILE
14 '/database/oradata/skyread/system01.dbf',
15 '/database/oradata/skyread/tbs_test.dbf',
16 '/database/oradata/skyread/sysaux01.dbf',
17 '/database/oradata/skyread/users01.dbf',
18 '/database/oradata/skyread/system02.dbf',
19 '/database2/oradata/skyread/undotbs02.dbf',
20 '/database2/oradata/skyread/TBS_MRPMUSIC01.dbf',
21 '/database/oradata/skyread/sf01.dbf'
22 CHARACTER SET UTF8;
Control file created.
下面是一系列的打开过程,由于redo04.log是活动的,所以需要恢复
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;
alter database open resetlogs
*
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/database/oradata/skyread/system01.dbf'
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 122695861946 generated at 06/04/2013 13:48:31 needed for thread 1
ORA-00289: suggestion : /database/oradata/arch/1_34_815416841.dbf
ORA-00280: change 122695861946 for thread 1 is in sequence #34
Specify log: {
/database/oradata/arch/1_34_815416841.dbf
ORA-00308: cannot open archived log '/database/oradata/arch/1_34_815416841.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
应用日志并打开数据库:
Specify log: {
/database/oradata/skyread/redo05.log
Log applied.
Media recovery complete.
SQL> alter database open resetlogs;
Database altered.
如果是未归档的活动在线日志文件损坏,那么需要有数据文件的备份才能恢复,这里不再详细介绍。

Stored procedures are precompiled SQL statements in MySQL for improving performance and simplifying complex operations. 1. Improve performance: After the first compilation, subsequent calls do not need to be recompiled. 2. Improve security: Restrict data table access through permission control. 3. Simplify complex operations: combine multiple SQL statements to simplify application layer logic.

The working principle of MySQL query cache is to store the results of SELECT query, and when the same query is executed again, the cached results are directly returned. 1) Query cache improves database reading performance and finds cached results through hash values. 2) Simple configuration, set query_cache_type and query_cache_size in MySQL configuration file. 3) Use the SQL_NO_CACHE keyword to disable the cache of specific queries. 4) In high-frequency update environments, query cache may cause performance bottlenecks and needs to be optimized for use through monitoring and adjustment of parameters.

The reasons why MySQL is widely used in various projects include: 1. High performance and scalability, supporting multiple storage engines; 2. Easy to use and maintain, simple configuration and rich tools; 3. Rich ecosystem, attracting a large number of community and third-party tool support; 4. Cross-platform support, suitable for multiple operating systems.

The steps for upgrading MySQL database include: 1. Backup the database, 2. Stop the current MySQL service, 3. Install the new version of MySQL, 4. Start the new version of MySQL service, 5. Recover the database. Compatibility issues are required during the upgrade process, and advanced tools such as PerconaToolkit can be used for testing and optimization.

MySQL backup policies include logical backup, physical backup, incremental backup, replication-based backup, and cloud backup. 1. Logical backup uses mysqldump to export database structure and data, which is suitable for small databases and version migrations. 2. Physical backups are fast and comprehensive by copying data files, but require database consistency. 3. Incremental backup uses binary logging to record changes, which is suitable for large databases. 4. Replication-based backup reduces the impact on the production system by backing up from the server. 5. Cloud backups such as AmazonRDS provide automation solutions, but costs and control need to be considered. When selecting a policy, database size, downtime tolerance, recovery time, and recovery point goals should be considered.

MySQLclusteringenhancesdatabaserobustnessandscalabilitybydistributingdataacrossmultiplenodes.ItusestheNDBenginefordatareplicationandfaulttolerance,ensuringhighavailability.Setupinvolvesconfiguringmanagement,data,andSQLnodes,withcarefulmonitoringandpe

Optimizing database schema design in MySQL can improve performance through the following steps: 1. Index optimization: Create indexes on common query columns, balancing the overhead of query and inserting updates. 2. Table structure optimization: Reduce data redundancy through normalization or anti-normalization and improve access efficiency. 3. Data type selection: Use appropriate data types, such as INT instead of VARCHAR, to reduce storage space. 4. Partitioning and sub-table: For large data volumes, use partitioning and sub-table to disperse data to improve query and maintenance efficiency.

TooptimizeMySQLperformance,followthesesteps:1)Implementproperindexingtospeedupqueries,2)UseEXPLAINtoanalyzeandoptimizequeryperformance,3)Adjustserverconfigurationsettingslikeinnodb_buffer_pool_sizeandmax_connections,4)Usepartitioningforlargetablestoi


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

mPDF
mPDF is a PHP library that can generate PDF files from UTF-8 encoded HTML. The original author, Ian Back, wrote mPDF to output PDF files "on the fly" from his website and handle different languages. It is slower than original scripts like HTML2FPDF and produces larger files when using Unicode fonts, but supports CSS styles etc. and has a lot of enhancements. Supports almost all languages, including RTL (Arabic and Hebrew) and CJK (Chinese, Japanese and Korean). Supports nested block-level elements (such as P, DIV),

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software

MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

MinGW - Minimalist GNU for Windows
This project is in the process of being migrated to osdn.net/projects/mingw, you can continue to follow us there. MinGW: A native Windows port of the GNU Compiler Collection (GCC), freely distributable import libraries and header files for building native Windows applications; includes extensions to the MSVC runtime to support C99 functionality. All MinGW software can run on 64-bit Windows platforms.

Dreamweaver CS6
Visual web development tools
