Shulou(Shulou.com)06/01 Report--

Rman can be used for database replication: for testing or development

Methods: one is to copy manually, the other is to use Rman duplicate; to manually copy, first shut down the database, then package the relevant files and copy them to another server, and start with startup; the other is to use the Rman duplicate command, but with restrictions, it must be on the same platform.

Abbreviation for RMAN:Recovery Manager

Connectable database types: Target database (database that needs to be backed up or restored, requires SYSDBA permission), Recovery Catalog Database (optional, the information during the backup process is stored in this database, by default, RMAN runs in non-catalog mode, so the information generated by the backup process is stored in the control file), Auxiliary database;, in practice, these three databases should be deployed on different nodes

Non-Catalog mode: 1. Full backup level 2, level 0 incremental backup level 3, level 1 incremental backup; in addition, there are secondary and tertiary incremental backups

Condition for using RMAN backup: the database runs in ArchiveLog mode and the rman path is added to the PATH environment variant

Usage (in non-catalog mode): enter rman at the command line to enter the command prompt; connect to the target database (connect target /) first; check whether there is a backup (list backupset); the backup command (backup database), which is a full backup, produces a backup set with multiple backup slices, which are essential for recovery, and the tag of the backup slices in the same backup set is the same.

Zero-level incremental backup: backup incremental level 0 database, which means that it is not much different from a full backup. The difference is that a first-level incremental backup can be performed after a zero-level incremental backup, but not a first-level incremental backup after a full backup.

Backup contents: database files, parameter files, control files, password files (optional), archive log files (cannot be backed up), archive log files (backup database plus archivelog delete input); you can also back up tablespaces or control files separately

Backup method: 1. Backup set: 2. Mirror backup:

Backup command mode: 1. A single command, ending with a semicolon; 2. Batch command, run {}, commonly used parameters include format, channe (a connection between RMAN and target database), etc.

Automatic backup: scheduled tasks + scripts; scheduled tasks can set periodic tasks based on crontab, and execute similar commands in tasks: rman target / logfile=... Cmdfile=... Where cmdfile can be a batch command

Missing password file: it is not part of RMAN backup and recovery, and can be regenerated using the command orapwd

SPFILE loss recovery: in the RMAN command line: 1. Startup nomount 2. Set dbid 3. Restore spfile from autobackup 4. Shutdown immediate 5. Startup

Control file loss recovery: in the RMAN command line: 1. Startup nomount 2. Restore controlfile from autobackup 3. Alter database mount 4. Recover database 5. Alter database open resetlogs

Redolog file lost: 1. Shutdown immediate 2. Startup mount 3. Restore database until cancel 4. Alter database open resetlogs; Note to execute in sqlplus

Data file lost recovery: in the RMAN command line: 1. Sql "alter database datafile XX offline" 2. Restore datafile XX; 3. Recover datafile XX 4. Sql "alter database datafile XX online"

Table space recovery: in the RMAN command line: 1. Sql "alter tablespace XX offline" 2. Restore tablespace XX; 3. Recover tablespace XX 4. Sql "alter tablespace XX online"

Recovery based on point in time, recovery based on SCN, recovery based on log sequence

Backup and restore in Catalog mode: it is basically the same as non-catalog, except that some content needs to be created in advance.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.