Comments on: Nologging redo size

By: Riyaj Shamsudeen

Riyaj Shamsudeen — Fri, 10 Feb 2012 14:44:24 +0000

Yasir
I have added a script to get the redo size from v$archived_log if you don’t have AWR license.
Cheers
Riyaj

By: Anand

Anand — Thu, 26 Jan 2012 03:35:43 +0000

Good one..

Anand

By: Riyaj Shamsudeen

Riyaj Shamsudeen — Thu, 26 Jan 2012 03:22:02 +0000

Agreed.

By: Riyaj Shamsudeen

Riyaj Shamsudeen — Thu, 26 Jan 2012 03:20:59 +0000

Yes, You could potentially use v$archived_log (not gv$archived_log since the archive log files from all nodes are visible in v$archived_log itself). Following SQL can give you some idea, but I think, I should write it better since it might be useful for the Standard Edition customers without AWR data.

select to_char(first_time, ‘mm/dd’) ArchiveDate,
sum(BLOCKS*BLOCK_SIZE/1024/1024) LOGMB
from V$ARCHIVED_LOG
where first_time > sysdate – 7
and dest_id=1
group by to_char(first_time, ‘mm/dd’)
order by to_char(first_time, ‘mm/dd’)
/

Cheers
Riyaj

By: Vyacheslav Rasskazov

Vyacheslav Rasskazov — Thu, 26 Jan 2012 00:34:01 +0000

Quote: “Minimal redo(aka invalidation redo) is generated, if the database is not in force logging mode”
A think, more correctly, is “Minimal redo(aka invalidation redo) is generated, if the database is not in force logging mode AND segment have nologging attribute OR database in noarchivelog mode”.

By: Yasir

Yasir — Wed, 25 Jan 2012 23:10:43 +0000

Dear Sir,
Can we get the same from gv$archived_log?
It also has blocks and block_size column. So blocks*block_size would give redo rate based on first_time.