Are you using HAS? or RAC? When you configure the instance to be managed
by HAS or CRS, you can set the open mode under the startup options. If it
happens all the time, it suggests to me that restrict was added to the
startup options.
On Mon, Sep 27, 2021 at 1:12 PM Powell, Mark <mark.powell2@xxxxxxx> wrote:
Is this RAC, non-RAC, Exadata, etc...?
Are you just using sqlplus to start? If not, try
sqlplus /nolog
connect / as sysdba
startup
and see how it starts
Mark Powell
Database Administration
(313) 592-5148
------------------------------
*From:* oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> on
behalf of Jeff Chirco <backseatdba@xxxxxxxxx>
*Sent:* Monday, September 27, 2021 12:06 PM
*To:* oracle-l-freelist <oracle-l@xxxxxxxxxxxxx>
*Subject:* database starts in restricted mode automatically
We just noticed that since applying patch 19.11 our database automatically
starts in restricted mode even when issuing just a STARTUP and not
specifying restricted.
Anyone know why this is happening and how to fix it? I am able to
replicate it in a clone of the production database.
We think this contributed to some errors we got during 19.11 patch which
required us to run it twice. We checked with Oracle support on the
patching issues and they said everything was fine.
Jeff
