RMAN的crosscheck和obsolete的用法
一直对rman的crosschcek和obsolete的用法理解的不清楚,而且有点混乱,这样对rman的备份集甚至备份的管理造成很大的影响,今天还
一直对rman的crosschcek和obsolete的用法理解的不清楚,而且有点混乱,这样对rman的备份集甚至备份的管理造成很大的影响,今天还是及时测试一下,及时弥补这个重要环节
--------------------------------------分割线 --------------------------------------
推荐阅读:
RMAN 配置归档日志删除策略
Oracle基础教程之通过RMAN复制数据库
RMAN备份策略制定参考内容
RMAN备份学习笔记
Oracle数据库备份加密 RMAN加密
--------------------------------------分割线 --------------------------------------
RMAN> show all;
RMAN configuration parameters for database with db_unique_name XUPENG are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0.3/db_1/dbs/snapcf_xupeng.f'; # default
---默认策略就保留一份
---当前数据库无备份集备份
RMAN> list backup summary;
specification does not match any backup in the repository
做一次全备!
RMAN> backup database format '/u01/backup/ora_full_%U';
Starting backup at 10-MAR-14
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=38 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00004 name=/u01/app/oracle/oradata/XUPENG/users01.dbf
input datafile file number=00001 name=/u01/app/oracle/oradata/XUPENG/system01.dbf
input datafile file number=00002 name=/u01/app/oracle/oradata/XUPENG/sysaux01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/XUPENG/undotbs01.dbf
input datafile file number=00005 name=/u01/app/oracle/oradata/XUPENG/tools.dbf
input datafile file number=00006 name=/u01/app/oracle/oradata/XUPENG/test.dbf
input datafile file number=00008 name=/u01/app/oracle/oradata/XUPENG/xupeng.dbf
channel ORA_DISK_1: starting piece 1 at 10-MAR-14
channel ORA_DISK_1: finished piece 1 at 10-MAR-14
piece handle=/u01/backup/ora_full_01p2qnrf_1_1 tag=TAG20140310T105231 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00007 name=/u01/app/oracle/oradata/XUPENG/fuck.dbf
channel ORA_DISK_1: starting piece 1 at 10-MAR-14
channel ORA_DISK_1: finished piece 1 at 10-MAR-14
piece handle=/u01/backup/ora_full_02p2qnrm_1_1 tag=TAG20140310T105231 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 10-MAR-14
channel ORA_DISK_1: finished piece 1 at 10-MAR-14
piece handle=/u01/backup/ora_full_03p2qnrn_1_1 tag=TAG20140310T105231 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 10-MAR-14
--备份数据文件system
RMAN> backup datafile 1 format '/u01/backup/ora_system_%U';
Starting backup at 10-MAR-14
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/XUPENG/system01.dbf
channel ORA_DISK_1: starting piece 1 at 10-MAR-14
channel ORA_DISK_1: finished piece 1 at 10-MAR-14
piece handle=/u01/backup/ora_system_04p2qnuc_1_1 tag=TAG20140310T105404 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 10-MAR-14
channel ORA_DISK_1: finished piece 1 at 10-MAR-14
piece handle=/u01/backup/ora_system_05p2qnuf_1_1 tag=TAG20140310T105404 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 10-MAR-14
----所有的备份都会包括控制文件和spfile
更多详情见请继续阅读下一页的精彩内容:

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

AI Hentai Generator
Generate AI Hentai for free.

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



InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.

The article discusses using MySQL's ALTER TABLE statement to modify tables, including adding/dropping columns, renaming tables/columns, and changing column data types.

Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.

Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.

Article discusses configuring SSL/TLS encryption for MySQL, including certificate generation and verification. Main issue is using self-signed certificates' security implications.[Character count: 159]

Article discusses popular MySQL GUI tools like MySQL Workbench and phpMyAdmin, comparing their features and suitability for beginners and advanced users.[159 characters]

The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values and pointers to data rows, and is suitable for non-primary key column queries.

Article discusses strategies for handling large datasets in MySQL, including partitioning, sharding, indexing, and query optimization.
