SGA_MAX_SIZE>MEMORY_TARGET???

关于 SGA_MAX_SIZE >MEMORY_TARGET的测试： SQL> alter system set memory_target=2G scope=spfile; 系统已更改。 SQL> shutdown immediate 数据库已经关闭。 已经卸载数据库。 ORACLE 例程已经关闭。 SQL> startup ORACLE 例程已经启动。 Total System Global Area 2137886720 bytes Fixed Size 2177456 bytes Variable Size 671090256 bytes Database Buffers 1459617792 bytes Redo Buffers 5001216 bytes 数据库装载完毕。 数据库已经打开。 SQL> show parameter mem NAME TYPE VALUE ------------------------------------ ------------ --------- hi_shared_memory_address integer 0 memory_max_target big integer 2G memory_target big integer 2G shared_memory_address integer 0 SQL> show parameter sga NAME TYPE VALUE ------------------------------------ ------------ --------- lock_sga boolean FALSE pre_page_sga boolean FALSE sga_max_size big integer 2G sga_target big integer 0 SQL> alter system set memory_max_target=3G scope=spfile; 系统已更改。 SQL> shutdown immediate 数据库已经关闭。 已经卸载数据库。 ORACLE 例程已经关闭。 SQL> startup ORACLE 例程已经启动。 Total System Global Area 3206836224 bytes Fixed Size 2180024 bytes Variable Size 1744833608 bytes Database Buffers 1442840576 bytes Redo Buffers 16982016 bytes 数据库装载完毕。 数据库已经打开。 SQL> show parameter mem NAME TYPE VALUE ------------------------------------ ------------ --------- hi_shared_memory_address integer 0 memory_max_target big integer 3G memory_target big integer 2G shared_memory_address integer 0 SQL> show parameter sga NAME TYPE VALUE ------------------------------------ ------------ --------- lock_sga boolean FALSE pre_page_sga boolean FALSE sga_max_size big integer 3G sga_target big integer 0 SQL>

测试总结：

From below test case, I set the sga_max_size large than memory_targe successfully.

Step:
1. Set the memory_target to 2G, and then restart db.
2. Set the memory_max_target to 3G, and then restart db.

I found the sga_max_size also change to 3G after step 2.

It means that you can set the size of the parameters memory_target and memory_max_target. After restarting db, The sga_max_size will change to memory_max_target size automatically.
But you can not set the SGA_MAX_SIZE more than MEMORY_TARGET alone.

About shmmax in solaris 10, the older "shminfo_shmmax" (set in /etc/system) is replaced by project.max-shm-memory parameter (set in /etc/project).
As per 'Solaris Tunable Parameters Reference Manual'
project.max-shm-memory resource control limits the total amount of shared memory of one project, whereas previously, the shmsys:shminfo_shmmax parameter limited the size of a single shared memory segment.

Set the value of project.max-shm-memory greater than sum of all the SGAs required to run on your server. If you want to set the memory_target as 80GB, you need to change the kernel parameter shmsys:shminfo_shmmax large than 80GB.
After the kernel parameter changed, you need to reboot the OS system to take effect.

I suggest you also running the Health Check script as described in the following note:
Note 250262.1 - RDA 4 - Health Check / Validation Engine Guide