Oracle11gR2RACORA00845MEMORY_TARGETnotsupportedonthissystem解决方法

公司刚上线一套Oracle 11gR2 的RAC。 将MEMORY_TARGET内存设置为12G后&＃xff0c;启动的时候报了错误&＃xff1a;

       ORA-00845: MEMORY_TARGET not supported on this system

00845, 00000, "MEMORY_TARGET not supported on this system"

// *Cause: The MEMORY_TARGET parameter was not supported on this operating system or /dev/shm was not sized correctly on Linux.

// *Action: Refer to documentation for a list of supported operating systems. Or, size /dev/shm to be at least the SGA_MAX_SIZE on each Oracle instance running on the system.

在Oracle 11g里&＃xff0c;通过MEMORY_TARGET参数自动管理SGA和PGA。 但是在Oracle 11gR2 里如果MEMORY_TARGET参数值设定的过大&＃xff0c;可能就会出现这个错误。

解决方法&＃xff1a;增加/dev/shm, /dev/shm通常用做共享内存。

 /dev/shm是一个临时文件系统&＃xff08;tmpfs) 。 从/etc/fstab中mount支持标准的参数"size"&＃xff0c;可以用size来增加或者减少在/dev/shm上的tmpfs大小.如果没有设置size&＃xff0c;它的大小大于MEMORY_TARGET。

如果想立即生效&＃xff0c;方法如下&＃xff1a;

# umount tmpfs

# mount -t tmpfs shmfs -o size&＃61;14G /dev/shm

让以后每次重启OS 都自动mount&＃xff0c;修改文件 /etc/fstab 将tmpfs 修改成以下值&＃xff1a;

 tmpfs            /dev/shm        tmpfs  defaults,size&＃61;14G        0 0

如果直接修改/etc/fstab&＃xff0c;通过重启OS 也可以让参数生效。

注意&＃xff1a;这个size 的大小需要设置为整数。

df -h 在查查修改后的/dev/shm的大小

文件系统              容量  已用 可用 已用% 挂载点

/dev/mapper/vg00-lv_root

                       20G   11G  7.7G  59% /

/dev/mapper/vg00-lv_home

                       97G  6.8G   86G   8% /home

/dev/sda1              97M   13M   80M  14% /boot

tmpfs                  14G     0   14G   0% /dev/shm

Oracle 官网的说明&＃xff1a;

In this Document
  Symptoms
  Changes
  Cause
  Solution
  References

Oracle Server - Enterprise Edition - Version: 11.1.0.6 to 11.2.0.2.0 - Release: 11.1 to 11.2
Linux x86
Linux x86-64

On a Linux system, trying to start up an 11g instance could fail with the following error:

ORA-845: MEMORY_TARGET not supported on this system

In the alert log, you could or could not see the below messages:

ORA-04031 errors

OR

Starting ORACLE instance (normal)
WARNING: You are trying to use the MEMORY_TARGET feature.
This feature requires the /dev/shm file system to be mounted for at
Least bytes.The /dev/shm is either not mounted or is mounted
With available space less than this size.
Please fix this so that MEMORY_TARGET can work as expected.
Current available is and used is bytes.memory_target needs larger /dev/shm

If ORA-04031 is seen in the alert log, sometimes you can not establish new connections due to this problem.

Installed 11g, or created a new database on 11g and is starting to use the AMM (Automatic Memory Management) feature.

This feature requires the /dev/shm file system to be mounted for at least %llu bytes.
/dev/shm is either not mounted or is mounted with available space less than this size.

Explanation:

AMM (Automatic Memory Management) is a new feature in 11 which manages both SGA and PGA.

MEMORY_TARGET is used instead of SGA_TARGET and MEMORY_MAX_TARGET is used instead of SGA_MAX_SIZE (defaults to MEMORY_TARGET ).

It uses /dev/shm on Linux. If max_target set over /dev/shm size, you get the error messages.

1. If you are installing Oracle 11g on a Linux system, note that Memory Size (SGA and PGA), which sets
the initialization parameter MEMORY_TARGET or MEMORY_MAX_TARGET, cannot be greater than the shared memory filesystem (/dev/shm) on your operating system. To resolve the current error, increase the /dev/shm file size. For example:

# mount -t tmpfs shmfs -o size&＃61;7g /dev/shm

Also, to make this change persistent across system restarts, add an entry in /etc/fstab similar to the following:

shmfs /dev/shm tmpfs size&＃61;7g 0

2. This error may also occur if /dev/shm is not properly mounted. Make sure your df output is similar to the following:

$ df -k
Filesystem 1K-blocks Used Available Use% Mounted on
...
shmfs 6291456 832356 5459100 14% /dev/shm

3. If configuring AMM is not possible due to lack of space on /dev/shm mount point, you can configure ASMM instead of AMM, i.e. set SGA_TARGET, SGA_MAX_SIZE and PGA_AGGREGATE_TARGET instead of MEMORY_TARGET.

In this Document
  Purpose
  Scope and Application
  HugePages and Oracle Database 11g Automatic Memory Management (AMM) on Linux
  References

Oracle Server - Enterprise Edition - Version: 11.1.0.6 and later   [Release: 11.1 and later ]
Linux OS - Version: 2.6 and later ]
Linux x86
IBM: Linux on System z
IBM: Linux on POWER Systems
IBM S/390 Based Linux (31-bit)
Linux x86-64
Linux Itanium

This document discusses the interoperability of the Automatic Memory Management (AMM) feature introduced by Oracle DB 11g and the HugePages (HugeTLB) feature of the Linux OS kernel.

This document is to be used by Linux system administrators and Oracle database administrators that work with Oracle Database Server 11g on Linux Operating System.

The 11g AMM feature is enabled by the MEMORY_TARGET / MEMORY_MAX_TARGET instance initialization parameters (see Note 460506.1 for further information). That is also the case with a default database instance created using Database Configuration Assistant (DBCA).

With AMM all SGA memory is allocated by creating files under /dev/shm. When Oracle DB does SGA allocations that way HugePages are not reserved/used. The use of AMM is absolutely incompatible with HugePages.

Please also note that ramfs (instead of tmpfs mount over /dev/shm) is not supported for AMM at all. With AMM the Oracle database needs to grow and reduce the size of SGA dynamically. This is not possible with ramfs where it possible and supported with tmpfs (which is the default for the OS installation).

If you want to use HugePages make sure that both MEMORY_TARGET / MEMORY_MAX_TARGET initialization parameters are disabled (set to 0) for the database instance.(See also Oracle&＃xfffd; Database Administrator&＃39;s Guide 11g)

NOTE:460506.1 - ORA-00845 When Starting Up An 11g Instance With AMM Configured.

------------------------------------------------------------------------------

Blog&＃xff1a; http://blog.csdn.net/tianlesoftware

网上资源&＃xff1a; http://tianlesoftware.download.csdn.net

相关视频&＃xff1a;http://blog.csdn.net/tianlesoftware/archive/2009/11/27/4886500.aspx

DBA1 群&＃xff1a;62697716(满); DBA2 群&＃xff1a;62697977(满)

DBA3 群&＃xff1a;62697850   DBA 超级群&＃xff1a;63306533;    

聊天 群&＃xff1a;40132017

--加群需要在备注说明Oracle表空间和数据文件的关系&＃xff0c;否则拒绝申请