Re: read_only_open_delayed

I think the last time I used this feature was on an Oracle 10g system, and I don't recall seeing (or hearing later) any problems with it. It was part of handling some very large range-partitioned tables where each tablespace held the partitions for a given date (can't remember if it was daily or weekly now) and I think the point was that the oldest partitions /tablespaces were read-only and not queried very much hence the obvious choice of strategy.

Regards
Jonathan Lewis

On Tue, 5 Apr 2022 at 00:54, Fairlie Rego <fairlie.rego_at_gmail.com> wrote:

> Hi all,
>
> I have a 19.10 database with a large number of read only files which takes
> 21 minutes to open in production when a database switchover happens.
> Unfortunately this does not meet our RTO and we have tested the
> switchover/open with the read_only_open_delayed parameter in a test
> environment which is not an exact prod replica but as close to it as
> possible.
>
> So in the test environment the open time reduces from 8 minutes to 22
> seconds.
>
> SQL> select enabled,count(*) from v$datafile group by enabled;
>
> ENABLED COUNT(*)
> ---------- ----------
> READ ONLY 1091
> READ WRITE 496
>
> Keen to understand if anyone else is using this since this parameter has
> been around since 10.1
>
> Cheers
>
> --
> Fairlie Rego
> Executive Database Architect
> www.technoconsulting.com.au
> http://www.linkedin.com/in/fairlierego
> https://fairlierego.wordpress.com/
>
> Twitter _at_fairlierego
>

--
http://www.freelists.org/webpage/oracle-l