Re: database starts in restricted mode automatically

Thanks Andrew I am glad I am not the only one. In your alert log during the start up process do you have the following message? Also how many records do you have in V$ENCRYPTION_KEYS?

ALTER DATABASE OPEN detects that an encrypted tablespace has been restored but the database key has not been activated, or the database has been flashback'ed prior to first set key of the master key (pdb 0). Database is open in RESTRICTED MODE only. Please select the latest master key from V$ENCRYPTION_KEYS and execute ADMINISTER KEY MANAGEMENT USE KEY <key_id> command, and restart the database

On Tue, Sep 28, 2021 at 5:47 AM Cohen, Andrew M. <Andrew.Cohen_at_tufts.edu> wrote:

> We have the same issue for only one of our many databases that we have
> applied the same patch to. All of the databases that have been cloned to
> other environments also have this same issue. I have opened an SR with
> Oracle and the best they can tell me is that it is a bug. I would
> definitely like to know if you find a solution. If I find one, I’ll post
> it as well.
>
>
>
> *From:* oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org> *On
> Behalf Of *Jeff Chirco
> *Sent:* Monday, September 27, 2021 3:43 PM
> *To:* Andrew Kerber <andrew.kerber_at_gmail.com>
> *Cc:* mark.powell2_at_dxc.com; oracle-l-freelist <oracle-l_at_freelists.org>
> *Subject:* Re: database starts in restricted mode automatically
>
>
>
> Somehow I have two records in V$ENCRYPTION_KEYS
>
>
>
> On Mon, Sep 27, 2021 at 12:31 PM Jeff Chirco <backseatdba_at_gmail.com>
> wrote:
>
> This non RAC, Simple EE database running on a small Dell server. No Grid,
> single instance (no CDB)
>
>
>
> I just checked the alert log during startup and noticed this. I have not
> restores any encrypted tablespaces nor has it been flashbacked.
>
>
>
> ALTER DATABASE OPEN detects that an encrypted tablespace has been restored
> but the database key has not been activated, or the database has been
> flashback'ed prior to first set key of the master key (pdb 0).
> Database is open in RESTRICTED MODE only.
> Please select the latest master key from V$ENCRYPTION_KEYS and execute
> ADMINISTER KEY MANAGEMENT USE KEY <key_id> command, and restart the database
>
>
>
> SQL>conn / as sysdba
> Connected to an idle instance.
> 12:25:45 idle>startup
> ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
> ORACLE instance started.
>
> Total System Global Area 6459226192 bytes
> Fixed Size 12449872 bytes
> Variable Size 2432696320 bytes
> Database Buffers 3992977408 bytes
> Redo Buffers 21102592 bytes
> Database mounted.
> Database opened.
>
>
> SQL>Select logins from v$instance;
>
> LOGINS
> ----------
> RESTRICTED
>
>
>
> On Mon, Sep 27, 2021 at 11:43 AM Andrew Kerber <andrew.kerber_at_gmail.com>
> wrote:
>
> 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_at_dxc.com> 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_at_freelists.org <oracle-l-bounce_at_freelists.org> on
> behalf of Jeff Chirco <backseatdba_at_gmail.com>
> *Sent:* Monday, September 27, 2021 12:06 PM
> *To:* oracle-l-freelist <oracle-l_at_freelists.org>
> *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
>
>
>
>
>
> --
>
> Andrew W. Kerber
>
> 'If at first you dont succeed, dont take up skydiving.'
>
>

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