Professional Documents
Culture Documents
How big is our SGA? In this example about 40 GB. Important: In the following query we directly convert into kB (value/1024). With that we can continue to calculate directly:
VALUE
---------------------------
TRUE
3. Check Hugepagesize
In our example we use a x86_64 Red Hat Enterprise Linux Server. So by default hugepagesize should be set to 2 MB:
4. Calculate Hugepages
For the calculation of the number of hugepages there is a easy way:
If you run more than one database on your server, you should include the SGA of all of your instances into the calculation:
vi /etc/sysctl.conf
vm.nr_hugepages=20480
The next parameter is hard and soft memlock in /etc/security/limits.conf for our oracle user. This value should be smaller than our available memory but minor to our SGA. Our
hugepages should fit into that by 100 percent. For that following calculation:
vi /etc/security/limits.conf
oracle soft memlock 41943040
oracle hard memlock 41943040
grep oracle /etc/security/limits.conf
...
oracle soft memlock 41943040
oracle hard memlock 41943040
As mentioned before we have to disable transparent hugepages from Red Hat Linux version 6 ongoing:
cat /sys/kernel/mm/redhat_transparent_hugepage/enabled
[always] madvise never
cat /sys/kernel/mm/redhat_transparent_hugepage/enabled
always madvise [never]
6. Server Reboot
If all parameter are set, make a complete reboot your server. As an alternative you can reload the parameters with sysctl -p.
7. Check Configuration
Memlock correct?
ulimit -l
41943040
cat /sys/kernel/mm/redhat_transparent_hugepage/enabled
always madvise [never]
Did the database uses HugePages? For that we take a look into the alert log. After „Starting ORACLE instance (normal)“ following entry „Large Pages Information“ gives us advise:
If your configuration is incorrect Oracle delivers recommendation here for the right setting. In the following example exactly one Page is missing, so 2048 kB memlock to come to 100
of SGA use of hugepages: