RMAN下CROSSCHECK命令详解
CROSSCHECK命令用户核对备份文件,以确保RMAN资料库与备份文件保持同步。当执行该命令时,如果RMAN资料库记录的状态与实际备份文
在用DELETE OBSOLETE 命令删除废弃的备份文件,如果出现如下错误(RMAN-06207 & RMAN-06208),那么需要用CROSSCHECK命令来解决:
RMAN-06207: WARNING: 2 objects could not be deleted for DISK channel(s) due
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
CROSSCHECK命令用户核对备份文件,以确保RMAN资料库与备份文件保持同步。当执行该命令时,如果RMAN资料库记录的状态与实际备份文件不匹配,则会更新资料库里的状态使其与实际备份文件状态一致;若备份文件处于expired状态,那么说明该备份已失效,可以删除之;
推荐阅读:
RMAN 配置归档日志删除策略
Oracle基础教程之通过RMAN复制数据库
RMAN备份策略制定参考内容
RMAN备份学习笔记
Oracle数据库备份加密 RMAN加密
常用命令介绍:
1.CROSSCHECK BACKUP
用于核对数据库、表空间、数据文件、控制文件、归档日志、SPFILE的备份集。
CROSSCHECK BACKUP ; --核对所有备份(包括有效和失效的备份)
CROSSCHECK BACKUP of database; --核对除控制文件、归档文件外的备份文件
CROSSCHECK BACKUP of tablespace system;
CROSSCHECK BACKUP of datafile 1;
CROSSCHECK BACKUP of controlfile;
CROSSCHECK BACKUP of archivelog all;
CROSSCHECK BACKUP of archivelog sequence 3;
CROSSCHECK BACKUP of spfile;
2.CROSSCHECK BACKUPPIECE
用于 核对特定备份片,该命令需要制定备份片的BP值或备份片名称;
CROSSCHECK BACKUPPIECE 24;
CROSSCHECK BACKUPPIECE '/u01/app/oracle/rman_backup/OCPYJG_28';
3.CROSSCHECK BACKUPSET
用于核对特定的备份集,,该命令需要制定备份集的BP值;
CROSSCHECK BACKUPSET 24;
4.CROSSCHECK COPY
用于核对数据库、表空间、数据文件、控制文件、归档文件的映像副本(即备份是用COPY DATAFILE ...... 或BACKUP AS COPY ......DATAFILE......命令备份数据文件的映像)
CROSSCHECK COPY;
CROSSCHECK COPY of database;
CROSSCHECK COPY of tablespace system;
CROSSCHECK COPY of datafile 1;
CROSSCHECK COPY of controlfile;
CROSSCHECK COPY of archivelog all;
CROSSCHECK COPY of archivelog from sequence 24 until sequence 32;
5.CROSSCHECK DTAFILECOPY
用于核对特定的数据文件映像副本,该命令需要指定映像副本的文件名或KEY值;
CROSSCHECK DATAFILECOPY 2;
CROSSCHECK DATAFILECOPY '/u01/app/oracle/rman_backup/tp9.dbf';
6.CROSSCHECK CONTROLFILECOPY
用于核对特定的控制文件映像副本,该命令需要指定控制文件映像副本的文件名或KEY值;
CROSSCHECK CONTROLFILECOPY 3;
CROSSCHECK CONTROLFILECOPY '/u01/app/oracle/rman_backup/controlfile01.ctl;
7.CROSSCHECK ARCHIVELOG
用于核对特定的归档日志,该命令需要指定归档日志的文件名或KEY值或SEQUENCE值;
CROSSCHECK ARCHIVELOG 36;
CROSSCHECK ARCHIVELOG 'crosscheck archivelog '/u01/app/oracle/product/11g/dbs/arch1_6_813161833.dbf';
CROSSCHECK ARCHIVELOG sequence 7;
本文永久更新链接地址:

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

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











The main role of MySQL in web applications is to store and manage data. 1.MySQL efficiently processes user information, product catalogs, transaction records and other data. 2. Through SQL query, developers can extract information from the database to generate dynamic content. 3.MySQL works based on the client-server model to ensure acceptable query speed.

InnoDB uses redologs and undologs to ensure data consistency and reliability. 1.redologs record data page modification to ensure crash recovery and transaction persistence. 2.undologs records the original data value and supports transaction rollback and MVCC.

MySQL is an open source relational database management system, mainly used to store and retrieve data quickly and reliably. Its working principle includes client requests, query resolution, execution of queries and return results. Examples of usage include creating tables, inserting and querying data, and advanced features such as JOIN operations. Common errors involve SQL syntax, data types, and permissions, and optimization suggestions include the use of indexes, optimized queries, and partitioning of tables.

MySQL's position in databases and programming is very important. It is an open source relational database management system that is widely used in various application scenarios. 1) MySQL provides efficient data storage, organization and retrieval functions, supporting Web, mobile and enterprise-level systems. 2) It uses a client-server architecture, supports multiple storage engines and index optimization. 3) Basic usages include creating tables and inserting data, and advanced usages involve multi-table JOINs and complex queries. 4) Frequently asked questions such as SQL syntax errors and performance issues can be debugged through the EXPLAIN command and slow query log. 5) Performance optimization methods include rational use of indexes, optimized query and use of caches. Best practices include using transactions and PreparedStatemen

MySQL is chosen for its performance, reliability, ease of use, and community support. 1.MySQL provides efficient data storage and retrieval functions, supporting multiple data types and advanced query operations. 2. Adopt client-server architecture and multiple storage engines to support transaction and query optimization. 3. Easy to use, supports a variety of operating systems and programming languages. 4. Have strong community support and provide rich resources and solutions.

Compared with other programming languages, MySQL is mainly used to store and manage data, while other languages such as Python, Java, and C are used for logical processing and application development. MySQL is known for its high performance, scalability and cross-platform support, suitable for data management needs, while other languages have advantages in their respective fields such as data analytics, enterprise applications, and system programming.

MySQL is suitable for small and large enterprises. 1) Small businesses can use MySQL for basic data management, such as storing customer information. 2) Large enterprises can use MySQL to process massive data and complex business logic to optimize query performance and transaction processing.

MySQL index cardinality has a significant impact on query performance: 1. High cardinality index can more effectively narrow the data range and improve query efficiency; 2. Low cardinality index may lead to full table scanning and reduce query performance; 3. In joint index, high cardinality sequences should be placed in front to optimize query.
