I’m not sure why it tries to start the database but this will set it to not
crsctl modify resource <db resource name> -init -attr AUTO_START=never
And to turn it back on
crsctl modify resource <db resource name> -init -attr AUTO_START=always
Another valid value is ‘restore’ that restores it the previous value.
To check the existing setting
crsctl stat res <db resource name> -p | grep AUTO_START
There is also an ENABLED property that would be set to 1 for the auto start to
On Sep 16, 2020, at 6:56 AM, Frank Gordon <frankagordon@xxxxxxxxx> wrote:
How did you tell Oracle Restart not to start this database automatically?
On Tue, Sep 15, 2020 at 10:50 AM Charlotte Hammond
<dmarc-noreply@xxxxxxxxxxxxx <mailto:dmarc-noreply@xxxxxxxxxxxxx>> wrote:
I'm running a manual 11g to 18c upgrade:
Oracle Restart 19.7
Source Home 184.108.40.206
Target Home 220.127.116.11
I have shutdown the database using srvctl from the 11g home.
I have started the database using sqlplus from the 18c home in upgrade mode.
I have started the upgrade using dbupgrade.
Then, a few minutes in and for no apparent reason, as can be seen in
ohasd.trc, Oracle Restart tries to restart the database from the old 11g
home, whilst dbupgrade is still running.
It seems to start (although an ORA-600[kccsbck_first] is logged), and
hilarity ensues. Ultimately the upgrade fails with CRS-5702 (resource
already running) at a point where it attempts to do a restart.
My question is: why does Oracle Restart attempt to bring up the database
which was cleanly shutdown before the upgrade?
I've used this approach on dozens of other databases without problems, and
running dbupgrade again on this one seems to work fine too.