Code:
2021-06-19 23:43:21.362 : [ default][ default]ut_read_reg:2:ocr registry key SOFTWARE\Oracle\olr cannot be opened. error 2
2021-06-19 23:43:21.362 : [ default][ default]ut_read_reg:2:ocr registry key SOFTWARE\Oracle\ocr cannot be opened. error 2
*** 2021-06-19T23:43:58.116229+03:00
ksacl_Update: caught error 604
*** 2021-06-19T23:44:01.127029+03:00
ksacl_Update: caught error 604
*** 2021-06-19T23:44:04.137829+03:00
ksacl_Update: caught error 604
и до бесконечности

Code:
kstmmainvktm: succeeded in setting elevated priority
highres_enabled
VKTM running at (5)millisec precision with DBRM quantum (100)ms
[Start] HighResTick = 2206690212
kstmrmtickcnt = 0 : ksudbrmseccnt[0] = 1624135393
*** 2021-06-19T23:52:17.503429+03:00
kstmchkdrift (kstmhighrestimecntkeeper:highres): Time jumped forward by (1528772)usec at (2750448661) whereas (1000000) is allowed

Code:
dbkrfssm: mmon not open
*** 2021-06-19T23:48:26.763829+03:00
dbkrfssm: mmon not open
*** 2021-06-19T23:53:27.906229+03:00
dbkrfssm: mmon not open
*** 2021-06-19T23:58:29.017429+03:00
dbkrfssm: mmon not open
dbkrfssm: mmon not open
*** 2021-06-20T00:08:31.364629+03:00
dbkrfssm: mmon not open
и так до бесконечности

Code:
Caching undo dictionary info: used hint for object index=3
Caching undo dictionary info: used hint for object index=4
*** 2021-06-19T23:43:55.121029+03:00
kjznppl0: database in migration or not writable
*** 2021-06-19T23:43:57.055429+03:00
06/19/2021 23:43:562021-06-19 23:43:57.055 : [ default][ default]ut_read_reg:2:ocr registry key SOFTWARE\Oracle\olr cannot be opened. error 2
2021-06-19 23:43:57.055 : [ default][ default]ut_read_reg:2:ocr registry key SOFTWARE\Oracle\ocr cannot be opened. error 2
2021-06-19 23:43:57.055 : [ default][ default]ut_read_reg:2:ocr registry key SOFTWARE\Oracle\olr cannot be opened. error 2
2021-06-19 23:43:57.055 : [ default][ default]ut_read_reg:2:ocr registry key SOFTWARE\Oracle\ocr cannot be opened. error 2

Code:
krsy_rtw_primary_loop: Sleep 5 seconds and then try to clear SRLs in 2 time(s)
*** 2021-06-19T23:43:40.051429+03:00
krsy_rtw_primary_loop: Sleep 10 seconds and then try to clear SRLs in 3 time(s)
*** 2021-06-19T23:43:50.129029+03:00
krsy_rtw_primary_loop: Sleep 20 seconds and then try to clear SRLs in 4 time(s)
*** 2021-06-19T23:44:10.143829+03:00
RT_STATE: Changing deferred archival state from 0 to 1 [krsy.c:2864]
krse_srl_archive_int: Database is not in archivelog mode
RT_STATE: Changing deferred archival state from 1 to 0 [krsy.c:2867]
*** 2021-06-19 23:44:10.190629 1149 krsh.c
INFO: krsh_tmi_update: Time Measurement Interface event set to: 0 (0x0) [krsy.c:2213]

Code:
[Thread-182] [ 2021-06-19 23:43:58.537 MSK ] [PerlEngine.execute:229]  Execing PERL process...
[Thread-182] [ 2021-06-19 23:43:58.599 MSK ] [PerlEngine.execute:267]  m_bReaderStarted: false
[Thread-182] [ 2021-06-19 23:43:58.599 MSK ] [PerlEngine.execute:271]  Starting Reader Thread...

Code:
2021-06-19T23:43:57.398629+03:00
db_recovery_file_dest_size of 30000 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
2021-06-19T23:43:58.397029+03:00
Completed: ALTER DATABASE OPEN MIGRATE

Current Release/Source Release
Direct Upgrade 
12.1.0.2, 11.2.0.4, 11.2.0.3
Direct upgrade to 12.2.0.1 is supported. 

...\perl\bin\perl catctl.pl -n 4 catupgrd.sql

Unexpected error encountered in catctlMain; Error Stack Below; exiting
Died at catctl.pl line 7898.
 at catctl.pl line 7898.
   main::catctlDie("\x{a}Unexpected error encountered in catconExec; exiting\x{a} No such"...) called at catctl.pl line 4621
   main::catctlExecutePhaseFiles(0, 1, undef, undef, undef) called at catctl.pl line 1912
   main::catctlRunPhase(0, 1, undef, undef, undef) called at catctl.pl line 2056
   main::catctlRunPhases(0, 116, 116, undef, undef, undef) called at catctl.pl line 2229
   main::catctlRunMainPhases() called at catctl.pl line 1386
   main::catctlMain() called at catctl.pl line 1301
   eval {...} called at catctl.pl line 1299

 Symptom 
When running VMware snapshot for Linux server running Oracle database, you get a warning in alert.log:
Warning: VKTM detected a forward time drift.
Time drifts can result in unexpected behavior such as time-outs.
Please see the VKTM trace file for more details:
/oracle/SID/saptrace/diag/rdbms/sid/SID/trace/SID_vktm_nnnn.trc
 Environment 
• VMware virtualization
•Windows server (any release)
•Oracle DB (11g or higher)
 Cause 
During a VMware snapshot, the VM is stunned, and time is not kept in sync.
VMware KBA: Time drift in guest operating system during snapshot removal
After the snapshot is finished and the VM is resumed, and the time will be synchronized from the ESX by the VMware tools. This will happen even if tools.syncTime is already disabled.
VMware KBA: Disabling Time Synchronization
 Resolution 
 The alert can be ignored , as it should not cause any problems in the system. If the time would not be synchronized after a snapshot, the OS clock would be significantly off.
It is recommended to keep the time of the ESX and the VM synchronized to external sources, for example through NTP.