I tried to install Oracle 19.7 Std. on an Grid 19.7
First off all: Thanks for the feature!
Installation runs fine, relocate works perfectly.
However when I run an shut down (shutdown -h now) the shutdown of the database is started:
2020-06-28T16:48:47.773075+02:00
Shutting down ORACLE instance (abort) (OS id: 4553)
2020-06-28T16:48:47.774325+02:00
Shutdown is initiated by oraagent.bin@failo1.darkwing.net (TNS V1-V3).
License high water mark = 7
USER (ospid: 4553): terminating the instance
2020-06-28T16:48:47.796910+02:00
opiodr aborting process unknown ospid (5289) as a result of ORA-1092
2020-06-28T16:48:47.854820+02:00
ORA-1092 : opitsk aborting process
2020-06-28T16:48:48.850488+02:00
Instance terminated by USER, pid = 4553
2020-06-28T16:48:49.094328+02:00
Instance shutdown complete (OS id: 4553)
As You see,the shutdown procedure is aborted. As far as I know ORA-1092 shows that the database has
lost contact to the datafiles?
On target crash recovery is needed:
2020-06-28T16:49:26.444565+02:00
Beginning crash recovery of 1 threads
Thread 1: Recovery starting at checkpoint rba (logseq 21 block 3769), scn 0
2020-06-28T16:49:26.520665+02:00
Started redo scan
2020-06-28T16:49:27.243715+02:00
Completed redo scan
read 1683 KB redo, 371 data blocks need recovery
I guess, that the ASM System shutdown to fast.
Is there any way to make sure that the ASM System waits for database shutdown?
Update:
If I issue "crsctl stop crs" the same error comes up.
I worried this was caused by the fact, my testsystem is running in Oracle Virtual Boxes and these just wher shutdown to fast.