Re: Is there a limit of rows in V$ARCHIVED_LOG

"David Fitzjarrell" <oratune_at_aol.com> wrote in message news:94hkdi$ltq$1_at_nnrp1.deja.com...
> In article <94hfrs$n$1_at_oxygen.technet.net>,
> The V$ARCHIVED_LOGS view displays archived log information from the
> control file including archive log names. An archive log record is
> inserted after the online redo log is successfully archived or cleared
> (name column is NULL if the log was cleared). If the log is archived
> twice, there will be two archived log records with the same THREAD#,
> SEQUENCE#, and FIRST_CHANGE#, but with a different name. An archive log
> record is also inserted when an archive log is restored from a backup
> set or a copy and whenever a copy of a log is made with the RMAN copy
> command.
>
> An init<SID>.ora parameter that affects this is
> control_file_record_keep_time, which specifies the minimum number of
> days that must pass before a reusable record in the controlfile can be
> reused. I would imagine that the archive log records are reusable
> records, therefore any archive log over the
> control_file_record_keep_time will not appear in the controlfile.
> Check the dates on the 'missing' archive logs and determine if they
> coincide with the value set for control_file_record_keep_time. I
> expect that they will.
>

I may be hopelessly wrong about this, but I could almost swear that control_file_record_keep_time only becomes of relevance when using RMAN without a catalogue, and that the real problem is maxloghistory when creating the database.

Oh well: he has two possible solutions now, neither of which will kill him, and it will be interesting to find out which one was the real McCoy.

Regards
HJR
> --
> David Fitzjarrell
> Oracle Certified DBA
>
>
> Sent via Deja.com
> http://www.deja.com/
Received on Mon Jan 22 2001 - 20:03:46 CST