My Oracle Support Banner

OCIC:Cannot Connect To The VM After Scale Down The Shape From OC3 To OC1 (Doc ID 2499362.1)

Last updated on NOVEMBER 06, 2019

Applies to:

Oracle Database Cloud Service - Version N/A to N/A [Release 1.0]
Information in this document applies to any platform.

Symptoms

Scaled down the DBCS from OC3 to OC1 or OC6 to OC4 and VM is failing to start which causes SSH connectivity failure. UI may shows service is up and running after it time out.

Error reported in Boot logs 

init: oracle-tfa main process (2026) terminated [  332.127497] audit: type=1701 audit(1547440820.621:15): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=system_u:system_r:initrc_t:s0 pid=2031 comm="stty" exe="/bin/stty" sig=11
with status 254

udevd-work[684]: fork of '/bin/sh' failed: Cannot allocate memory

udevd-work[2042]: fork of '/bin/sh' failed: Cannot allocate memory

init: oracle-tfa main process ended, respawning

init: start-ttys main process (2027) terminated with status 254

init: tty (/dev/tty5) main process (2040) killed by SEGV signal

init: tty (/dev/tty5) main process ended, respawning

init: Temporary process spawn error: Cannot allocate memory

init: serial_console (serial_console) main process (2028) terminated with status 254

init: serial_console (serial_console) main process ended, respawning

Changes

Scale down the shape

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.