Ora-00821:specified value of Sga_target 3072M is too small, needs to being at least 12896M

When testing Platespine cloned database server, due to limited resources, the cloned database server only gave 9G of memory, the results in the test, will always appear oomkiller lead to downtime, that is, out of memory killer, is a processing mechanism under Linux when memory is exhausted. When memory is low, oom traverses the entire list of processes and then, based on the memory usage of the process and its Oom score value, eventually finds a higher-scoring process and then sends a kill signal to kill it. So adjust the Sga_target and sga_max_size These two parameters, the results of the time to restart the tragedy:

 as Sysdba

SQL  on Dec 15 09:28:11 2016

 All Rights Reserved.

 to an idle instance.

SQL> Startup

value  of  is  to  at least 12896M

SQL> Startup nomount

between  and 0

SQL>

This error occurred, suddenly remembered that the server set the Shared_pool_size parameter, so generate Pfile, check Initgsp.ora, as shown below,

sql> create pfile= '/u01/app/oracle/product/10.2.0/db_1/dbs/initgsp.ora ' from SPFile;

File created.

Manually set the. shared_pool_size to 0, and then start the DB instance to resolve the problem. As shown below:

SQL> Startup pfile='/u01/app/oracle/product/10.2.0/db_1/dbs/initgsp.ora '

ORACLE instance started.

Global Area 3221225472 bytes

Size 2099752 bytes

Variable Size 637535704 bytes

Database Buffers 2533359616 bytes

Redo buffers 48230400 bytes

Database mounted.

Database opened.

SQL> Exit

Ora-00821:specified value of Sga_target 3072M is too small, needs to being at least 12896M