image

Recovery from complete loss of all online redo log files using RMAN

Recovery from complete loss of all online redo log files using RMAN: Database name and version SQL> select instance_name,version from v$instance; INSTANCE_NAME VERSION —————- —————– opsdba 10.2.0.2.0 SQL> select member from v$Logfile; MEMBER ——————————- /u02/ORACLE/opsdba/redo03.log /u02/ORACLE/opsdba/redo02.log /u02/ORACLE/opsdba/redo01.log Lets delete all the redo log files , from the above specified location i.e /u02/ORACLE/ opsdba:/u02/ORACLE/opsdba>rm redo*.log If … continue reading

image

Incomplete Recovery (until log sequence)

Point in time recovery using RMAN (until a log sequence number) Recovery Objective SQL> conn scott/tiger Connected. SQL> select count(*) from myobjects; COUNT(*) ———- 249410 Switch a logfile SQL> conn / as sysdba Connected. SQL> alter system switch logfile; System altered. Note the current log sequence number (13) SQL> archive log list Database log mode … continue reading

image

Loss Of All Files – Disaster Recovery

RECOVERY SCENARIO: Complete loss of all database files including SPFILE using RMAN Database Details —————— Database Name=OPSDBA Machine Name=ITLINUXDEVBLADE07 DBID=1499754868 (select dbid from v$database) SIMULATING CRASH ———————— opsdba:/u01/ORACLE/opsdba>ls -l total 1948980 drwxr-x— 2 oracle dba 4096 Feb 12 13:35 arch -rw-r—– 1 oracle dba 7389184 Feb 12 13:57 control01.ctl -rw-r—– 1 oracle dba 7389184 Feb … continue reading

image

Recovery of a dropped tablespace

Recovery of a dropped tablespace To recover from a case of a dropped tablespace, the Tablespace Point In Time Recovery (TSPITR) method cannot be used. When you drop a tablespace, the controlfile will then no longer have any records of the tablespace which has been dropped. Attempts to use the RMAN RECOVER TABLESPACE command will … continue reading

Visit Us On FacebookVisit Us On Google PlusVisit Us On Youtube