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

> 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.

Actually, I thought that it was somewhere in the middle....

I believe that the MAXLOGHISTORY is as you say it to be. But the CONTROL_FILE_RECORD_KEEP_TIME does *not only* apply to RMAN. I've never used RMAN on any of my databases. But when I migrate a database, I will see my control file expand for the number of days specified in the above parameter. This is due to the control file having to capture more information than the previous db version. So the control file expands in size. Once the CONTROL_FILE_RECORD_KEEP_TIME number of days has passed,the control file doesn't have to expand since it can write over previous information. If one uses RMAN, then RMAN gets information from the control file and it can go back the number of days specified in this parameter. So this parameter must be adjusted if you want RMAN to go back far enough. IIRC, I believe the default for this parameter is 7 days (Oracle 8i on Solaris).

Of course, this is just my experiences with a not so obviously documented parameter and I could be wrong......

Brian

-- 
========================================
Brian Peasland
Raytheons Systems at
  USGS EROS Data Center
These opinions are my own and do not
necessarily reflect the opinions of my 
company!
========================================