Oracle adjusts the lock_sga parameter without using virtual memory

Because almost all operating systems support virtual memory, even if the memory we use is smaller than the physical memory, the OS cannot switch SGA to the virtual memory (SWAp ). Therefore, we can try to make the SGA lock in the physical memory not to be switched to the virtual memory, so as to reduce the Page Swap and swap, thus improving the performance. However, it is a pity that Windows cannot avoid this situation. Next we will refer to how to implement lock_sga in different systems
AIX 5l (Aix 4.3.3 or later)
Logon AIX as root
CD/usr/samples/kernel
. /Vmtune (information below) v_pingshm is already 1
. /Vmtune-S 1
Then the Oracle user modifies lock_sga = true in initsid. ora.
Restart the database
HP UNIX
Root Login
Create the file "/etc/privgroup": VI/etc/privgroup
Add line "dba mlock" To File
As root, run the command "/etc/setprivgrp-F/etc/privgroup ":
$/Etc/setprivgrp-F/etc/privgroup
Oracle user lock_sga = true in initsid. ora
Restart the database
Solaris (solaris2.6 or above)
By default, the hidden parameter use_ism = true is used for databases later than 8i. The system automatically locks the SGA in the memory and does not need to set lock_sga. If lock_sga = true is set, an error is returned when a non-root user starts the database.
Windows
Lock_sga = true cannot be set. You can set pre_page_sga = true to load all memory pages when the database is started. This may play a role.