The final solution to how SGA breaks through the 2 GB memory limit in a 32-bit Linux environment of Oracle

The 32-bit memory does not support the statement of 4 GB or more. For example, win2003server can recognize 8 GB memory on 32-bit machines. Therefore, Oracle's SGA can be abrupt on a 32-bit host.

The 32-bit memory does not support the statement of 4 GB or more. For example, win2003 server can recognize 8 GB memory on 32-bit machines. Therefore, Oracle's SGA can be abrupt on a 32-bit host.

The 32-bit memory does not support the statement of 4 GB or more. For example, win2003 server can recognize 8 GB memory on 32-bit machines.

Therefore, Oracle's SGA can break the limit of 2 GB on 32-bit machines. However, the order of generation is that the ASM function cannot be used. The values of SGA, LargePool, and memory pool must be set manually.

The software version of my experiment is:

Oracle version 10

The Linux version is RedHatAs4 or RedHatAs5.

Other versions of Linux support large page with kernel higher than 2.4. The following are the specific steps:

Step 1:
In the/boot/grub. conf file, add bigpages = xMB to the related kernel entries and then enable large page support. Here, x is calculated as follows:
Total SGA size (unit: G) x 1024
Then we take a whole hundred places around this value, so a 32 gb sga, we do the following calculation:
32*1024 = 4096 = 32768
Therefore, the/boot/grub. conf file entry looks like:
Kernel/vmlinuz-2.4.9-e.40enterprise ro root =/dev/cciss/c0d0p2 bigpages = 32768 MB

Step 2:

ROOT User:
Umount/dev/shm
Mount-t ramfs/dev/shm
Chown oracle: dba/dev/shm

And put the above steps in the/etc/rc. local file, located in front of the script to start ORACLE, so that it is limited at startup

These three commands enable LINUX to use the RAMFS (bigpages) feature, which is available in LINUX AS4 or later versions.