USE_LARGE_PAGES is used to manage the database's use of large pages for SGA memory.


This parameter is applicable only on the Linux operating system. However, setting this parameter to FALSE can cause performance degradation on any platform.

Property Description

Parameter type




Default value




Modifiable in a PDB




Oracle RAC

Multiple instances can use different values

This parameter does not affect process-private memory allocations.


These values can be specified for USE_LARGE_PAGES:

  • TRUE

    Specifies that the instance can use large pages if large pages are configured on the system.

    In Oracle Database 11g Release 2 (, if there are not enough large pages configured on the system, then regular sized pages will be used to allocate SGA memory. This can cause the free large pages to go unused, and the operating system can allocate a huge amount of memory to create page tables to map SGA into physical pages for the Oracle processes. This may lead to ORA-04030 errors and severe performance degradation on an instance.

    In Oracle Database 11g Release 2 ( and later releases, Oracle allocates as much of the SGA as it can in large pages, and if it runs out, it will allocate the rest of the SGA using regular sized pages. This can cause the instance to create additional shared memory segments for the SGA, but the total SGA size will be unchanged. In this supported mixed page mode allocation, the database will exhaust the available large pages before switching to regular sized pages.


    Specifies that the instance will not use large pages. This setting is not recommended because it can cause severe performance degradation for the instance. Although the USE_LARGE_PAGES initialization parameter applies only to Linux systems, setting this parameter to FALSE can cause performance degradation on any platform.

  • ONLY

    Specifies that the instance will fail to start if large pages cannot be used for the entire SGA memory. Oracle recommends this setting for consistent performance.


USE_LARGE_PAGES is set to FALSE automatically in an Oracle ASM instance when MEMORY_TARGET is enabled. In this case, the FALSE setting does not cause performance degradation.

See Also: