Memory_target cannot be started because of improper settings.

Today, I encountered another ldquo, strange rdquo, and problem during troubleshooting. The SGA Automatic Storage Management is disabled in the Test Library.

Today, I encountered another ldquo, strange rdquo, and problem during troubleshooting. The SGA Automatic Storage Management is disabled in the Test Library.

Today, I encountered another "strange" problem during troubleshooting.
The SGA Automatic Storage Management has been disabled in the Test Library. As a result, the shared_pool_size configuration is lost in the spfile file.
The parameters in the test environment are similar to the following:
Sga_max_size big integer 12000 M
Sga_target big integer 0
Shared_pool_size big integer 0
Db_cache_size big integer 6G
Pga_aggregate_target big integer 3147483648

This configuration should be faulty and the shared_pool_size part should be lost. The result shows the current test database. It is found that the shared_pool is more or less 2 GB.

COMPONENT CURRENT_M MIN_M MAX_M SPECCIFIED_M last_1_last_oper_typ GRANULE_M
--------------------------------------------------------------------------------------------------------
Shared pool 2000 992 2000 manual grow 16
Large pool 304 304 512 deferred shrink 16
Java pool 512 512 512 304 STATIC 16
Streams pool 0 0 0 STATIC 16
DEFAULT buffer cache 6224 6144 6352 6144 manual shrink 16
KEEP buffer cache 0 0 0 0 STATIC 16
RECYCLE buffer cache 0 0 0 0 STATIC 16
DEFAULT 2 K buffer cache 0 0 0 0 STATIC 16
DEFAULT 4 K buffer cache 0 0 0 0 STATIC 16
DEFAULT 8 K buffer cache 0 0 0 0 STATIC 16
DEFAULT 16 K buffer cache 0 0 0 0 STATIC 16
DEFAULT 32 K buffer cache 0 0 0 0 STATIC 16
Shared IO Pool 0 0 0 STATIC 16
If the problem persists, it may end up.
But I took a serious look and found that there was still a problem. SGA has around 12 GB, allocated to shared_pool 2 GB, buffer_cache 6 GB, plus large_pool, java_pool has less than 9 GB, where are the remaining parts?