DBCS: Scale Down activity failed when database was started using pfile as memory parameters did not get update

(Doc ID 2387771.1)

Last updated on MAY 06, 2018

Applies to:

Oracle Database Cloud Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

- The database was earlier running with SGA_TARGET of 5296M and then was increased to 10624M when the VM was scaled up.
- The database was running fine when the SGA_TARGET was 10624M
- After scaling down with expected SGA_TARGET=2640M, the database failed to start up even with lower expected SGA and gave the error.
- The OSW logs showed swapping happening and the free memory very low as compared to the total system memory.

 


The timeline of the operation was as below:

By 2018-04-10_15:51:09, image was updated to OC5 and SGA was updated successfully to 10.3 G from 5.1 GB, no swapping was there

 

Changes

The database was started using pfile instead of spfile as observed from logs. 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms