Restore Archivelog with Particular sequence

Restore Archivelog with Particular sequence

RMAN> run {
allocate channel dsk1 type disk;
restore archivelog logseq 11645;
release channel dsk1;
 }

RAC - Restore Archivelog with Particular sequence and thread

RMAN> run {
allocate channel ch01 type disk format '/ora_backup/u0006/FIPRD3/archivelog/';
restore archivelog logseq 24208 thread 3;
}

Restore Archivelog with Particular sequence at diff. location

RMAN> run{
set archivelog destination to '/ora_backup/u0001/cloning/';
 restore archivelog sequence 6232 thread 3;
 }

Redo log switch report from alert.log

Redo log file switch Report from alert.log using perl script

Redo log switch History

Redo log switch History

Find out  date  & time, SCN and other details about log switch

How Much Redo log is generated

Redo log Daily and Hourly volume calculated 

Find out how many MB of redo log is generated

Redo log Switch

Redo log Switch Rate by Date and Hour     

Find out how many log switches are taking place per hour

Redo Log Files and Sizing

 

Redo Log Files and Sizing         

set heading off;

select '******************************************************' from dual;

select '****           Redo Log Files and Sizing          ****' from dual;

select '******************************************************' from dual;

timing start 'Redo Sizing';

set heading on;

col "File Name" for a60;

col "Size in MB" format 999,999,999,999,990

select a.group#, thread#, substr(a.member,1,80) as "File Name",b.bytes/1024/1024 as "Size in MB" from v$logfile a,v$log b where a.group#=b.group#;

timing stop 'Redo Sizing';

Hope this helps. Regards Rupam

Find Sessions Generating Lots of Redo or Archive logs

Find Sessions Generating Lots of Redo or Archive logs

1. Login to a user with dba privilege

2. Execute the query

sql> SELECT s.sid, s.serial#, s.username, s.program,  i.block_changes

         FROM v$session s, v$sess_io i

       WHERE s.sid = i.sid 

       ORDER BY 5 asc, 1, 2, 3, 4;

3. Run the query multiple times and examine the delta between each occurrence of BLOCK_CHANGES. Large deltas indicate high redo generation by the session.

Hope this helps. Regards Rupam

Redo Log File - add and drop

Steps to add and drop redo log in database using ASM

1. Check redo log file destination

sql> show parameter db_create

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

db_create_file_dest                        string      +ORADATA001

db_create_online_log_dest_1          string      +ORADATA001

db_create_online_log_dest_2          string      +ORAFLASH001

db_create_online_log_dest_3          string

db_create_online_log_dest_4          string

db_create_online_log_dest_5          string