I'm trying to understand the behaviour of the Lifecycle status of the 19c database that I have created on the OCI Oracle Base Database service.
I have my database created as a single node DB (since I'm on Free tier account and in trial). I don't see the database life cycle state changes to either STOPPED or UNVAILABLE even after I shut down the entire oracle stack (Grid + DB) or even after I shut down the entire node.
See below:
[root@mj ~]# /u01/app/19.0.0.0/grid/bin/crsctl stop has
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'mj'
CRS-2673: Attempting to stop 'ora.crsd' on 'mj'
CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on server 'mj'
..
..
..
CRS-2677: Stop of 'ora.gipcd' on 'mj' succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'mj' has completed
CRS-4133: Oracle High Availability Services has been stopped.
[root@mj ~]#
[root@mj ~]# ps -ef|grep pmon
root 35887 34476 0 20:34 pts/0 00:00:00 grep --color=auto pmon
[root@mj ~]#
I can still see the status of the database as AVAILABLE in the console. Is this correct or should I raise it with Oracle support?
Thanks
Selvakumar Nagulan