Beruflich Dokumente
Kultur Dokumente
Standby Scn :
------------
[oracle@db32 ~]$ export ORACLE_SID=standby
CURRENT_SCN
-----------
871723
Prod Scn :
----------
[oracle@db31 ~]$ export ORACLE_SID=prod
CURRENT_SCN
-----------
899820
2) TAKE INCREMENTAL BACKUP FROM LAST SEQUENCE CHANGE AT STANDBY USING RMAN AT
PRIMARY DATABASE
-----------------------------------------------------------------------------------
-----------
Database altered.
6) SHUTDOWN STANDBY DATABASE AND REPLACE ALL CONTROLFILES WITH BACKUPED BEFORE)
WHEN PRIMARY SIDE ARCHIVELOG MISSING
-----------------------------------------------------------------------------------
---------------------------------
Do you really want to catalog the above files (enter YES or NO)? yes
cataloging files...
cataloging done
9) ONCE REGISTER WITH STANDBY CONTROLFILE RECOVER DATABASE FROM THE INREMENTAL
BACKUP USING RMAN WITH
'NOREDO' ( NOREDO NEED OPTION RECOVERY PROCESS WILL RECOVER FROM INCREMENTAL
BACKUP INSTEAD OF REDOLOG AND ARCHIVELOG)
-----------------------------------------------------------------------------------
--------------------------------------
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
Database altered.
NAME OPEN_MODE
--------- --------------------
PROD READ ONLY WITH APPLY
CURRENT_SCN
-----------
899825
=================================================================================TH
E END==============================================================================
When attempting to restore archive logs that are already located on disk using RMAN
you�ll receive an error if the archivelogs are stored within ASM because until
Oracle 11g shipped you could not use the OS copy or move command to retrieve them.
You would have to repeat this command for each archive log to be copied or try the
following solution:
Once the archivelos have been successfully uncataloged you are now able to
successfully restore the archive logs to a new location.
RMAN> run {
set archivelog destination to �/tmp�;
restore archivelog from logseq=60 until logseq=70;
}
Following the successful restore of the archivelogs you can then continue to
recatalog the archivelogs back into the ASM diskgroup.
Example:
-- Back up all archived logs from sequence # 250 to sequence # 301 and deletes the
archived redo logs after the backup is complete.
run {
allocate channel ch1 type disk format '/tmp/arc_%U';
backup
archivelog from logseq 250 until logseq 301 thread 1
}
In FORMAT clause, %U is replaced with unique file names when creating archivelog
backups.
The above RMAN statements create a file in the following format in the destination
directory (/etc).
Then, one can restore archive logs that are already located on a filesystem using
restore command:
run {
set archivelog destination to '/tmp';
restore archivelog all;
}