Oracle uses Incomplete Database-level recovery to solve the logical errors caused by data loss or human error before 10 Gb. After 10 Gb, RMAN introduces a new feature called "tablespace point-in-time recovery", TSPITR for short, which can actually achieve Incomplete recovery at the tablespace level, of course we know that after 10 Gb, the flashback feature can also solve the above problems. Since I have nev
1. Introduction to the experimental environment 1.1 soa Original Database database name comsoa instance name COMSOADBID 4133565260 database version windows64bit10.2.0 data file directory H:\ORACLE\ORADATA\ Comsoapfilecomsoa.__db_cache_size=1291845632comsoa.__java_pool_size=16777216comsoa.__large_pool_size= 16777216comsoa.__shared_pool_size=805306368comsoa.__streams_pool_size=0*.audit_file_dest= ' H:\ora
1. display the current configuration information======================================1.01 RMAN> show all;1.02 check non-default values in RMAN settings:SQL> select name, value from v $ rman_configure; -- before 11gSQL> SELECT CONF #, NAME, VALUE FROM RC_RMAN_CONFIGURATION;CONF # NAME VALUE---------- ---------------------------------------- Success -----------------------------------------------------------
Case 3:
--All of the table space data files are lost, restore data files (open)
1) test environment
07:37:23 sql> INSERT INTO scott.test values (6);
1 row created.
07:39:18 sql> INSERT INTO scott.test values (7);
1 row created.
07:39:20 sql> INSERT INTO scott.test values (8);
1 row created.
07:39:21 sql> commit;
Commit complete.
07:39:23 sql> SELECT * from Scott.test;
Id
----------
6
7
8
1
2
3
4
5
8 rows selected.
07:40:06 sql>
----datafile is corrupted in open state
[
After 12.1.0.2, duplicate target database for standby from active database is always hang dead in restore Controlfile. This is caused by bug 19664695. (Bug22468652 and bug 20721271 can end up with bug 19664695.) )
The workaround is to set up Disable_oob=on in the Sqlnet.ora file of Oracle_home and Grid_home. Please refer to RMAN active duplicate hanging on restore control file (Doc ID 2073604.1)
RMAN acti
We know that in previous versions of ORACLE10GR2, temporary files for temporary tablespace are not automatically restored if you use Rman to recover the database.
This has caused a series of problems, many DBAs forget to add temporary files after the recovery is complete, often to the application error to discover.
Starting with ORACLE10GR2, Oracle will automatically re-create the temporary files after us
Oracle database bad blocks are repaired through the DBV and Rman Blockrecover.
(1) When the Rman backup, Alert.log reported the following error:
Fri 2 12:41:36 2010
Hex Dump of (file, block 2718618) in trace file/u01/app/oracle/admin/bi/udump/bi_ora_31213.trc
Corrupt block relative dba:0x03297b9a (file, block 27186
Rman is a physical-structured backup based on data block backup, supporting the recovery operation with online redolog and archive Redolog, and is Oracle's recommended backup recovery tool.
The data imp/exp is a logical structure based import export tool that is based on the Import export tool for data objects (such as tables, stored procedures, and so on) and does not support the use of online redolog and archive Redolog, if used as backup and resto
Enter the Rman interfaceRman target/rman>Modify control file backup mode for automatic backupRMAN > Configure Controlfile autobackup on;Check if the control file backup is an automatic backupRMAN > Show Controlfile autobackup;View Control file Automatic backup pathRman> show controlfile autobackup format;Modify control file Automatic backup pathRMAN > Configure Controlfile autobackup format for device type
(4, ' BLAKE ', 6700);
Commit
CREATE TABLE Scott.employee (ID int,name varchar2 ()) tablespace User01;
(5) The use of Rman for table Space 1 is based on point-in-time recovery.
--rman part of the recovery table space
Recover Tablespace User01
Until Time "To_timestamp (' 2010-03-11 21:44:52 ', ' yyyy-mm-dd hh24:mi:ss ')"
Auxiliary destination '/home/oracle/
Oracle Rman Cold Shell script (I am here full backup, created 2 channels C1, C2) can be changed on this basis650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M00/86/18/wKioL1e0fHyRO_TTAABgkcV8Mm0539.png-wh_500x0-wm_3 -wmp_4-s_2228178479.png "title=" capture. PNG "alt=" Wkiol1e0fhyro_ttaabgkcv8mm0539.png-wh_50 "/>Text:#!/bin/bash#Author: Wangergui email:[email protected] date:2016-08-17#Function: Oracl
First, the case description
After using Rman to back up the database, because the table space was accidentally deleted manually, it is now necessary to use the incomplete recovery to retrieve the tablespaces that were mistakenly deleted.
Ii. Environmental Preparedness
[ORACLE@ECP-UC-DB1 ~]$ Sqlplus/as SYSDBA
Sql*plus:release 10.2.0.4.0-production on Mon Nov 14 12:35:14 2011
Copyright (c) 1982, 2007,
Restore full backup of another machine on a new machine
1 to remember the various directory structure and dbid of the original machine
2 creating the corresponding directory structure on the new machine note user permissions/u01/oracle/admin/dbname/pfile bdump udump dpdump cdump/oradata/dbname/rman_backup Flash_recover_sea Archivelog
3 Put the backup set file in the original backup directory of the new machine
3 R
First, the relevant query command
1.List database backed up by the current Rman
rman> list incarnation;
Rollup Queries: – If you have more than one backup file, use these two list commands to have a general understanding of the backup files.
1.1. List backup summary; – Overview of available backups
B means backup
A indicates that Archivelog, F represents fu
The purpose of this test is to export the Rman backup from the production database and then restore it in the test database1, copy Backup to the appropriate directory2, enter RmanRman target \3. Close the databaseShutdown4, start the database in Nomount modeStartup Nomount5, Recovery control fileRestore Controlfile from '/home/oracle/rman_backup/cf_c-1383295282-20171102-00 ';6. Mount DatabaseALTER DATABASE
Oracle Study case--rman ORA-19921 errorSystem environment:Operating system: AIX5.3Oracle:oracle 10GR2Error phenomena:The following error occurred when the database was connected via Rman:[11:01:51 [email protected]: ~] $rman target/Recovery manager:release 10.2.0.1.0-production on Mon Jan 19 11:01:53 2015Copyright (c)
Oracle 11g backup-based rman duplicate, rmanduplicateBackup-based rman duplicate command to create standby databasePrerequisites: ensure the backup of the original database and archive is completely visible to the standby end,It is assumed that the storage structure of all files, such as the source database and the target database, and log files, are identical;Co
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.