详细解决方案
map size mismatch; abort
热度：45 发布时间：2023-12-20 09:28:56.0
数据库启动时有莫名的提示map size mismatch; abort
原帖在这里：http://t.askmaclean.com/thread-1397-1-1.html
今天帮网友（centos 6.3 ora 10g）处理一个问题，处理方法如下，另外再多说一句不要违反官方的认证要求，否者就会出现一些奇怪的问题。低于11203的db 不能安装在rhel 6 and ol6上（可以强制安装，但是官方不支持，也不认证）
1#
发表于 2012-7-10 12:27:05
| 查看: 1360
| 回复: 11
系统环境：DELL的机器，安装的是linux6.2版本。需要在上面安装oracle 10g数据库。安装好包后，在启动数据库时，有如下提示：
SQL> startup nomount
map size mismatch; abort
: Success
map size mismatch; abort
: Success
map size mismatch; abort
: Success
map size mismatch; abort
: Success
ORACLE instance started.
Total System Global Area 2.1139E+10 bytes
Fixed Size 2220024 bytes
Variable Size 3296403464 bytes
Database Buffers 1.7834E+10 bytes
Redo Buffers 6488064 bytes
---------------------------------------------------------------------------------------下面附上sysctl的参数配置------------------------------------------------------
kernel.shmall = 4294967296
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default=262144
net.core.wmem_default=262144
net.core.rmem_max=262144
net.core.wmem_max=262144
在线等待，请大师分析分析。 |
回复
分享0
|
| |
|
最后登录
-
2013-8-24
在线时间
-
1149 小时
威望
-
2135
金钱
-
37288
注册时间
-
2011-10-12
阅读权限
-
200
帖子
-
3851
精华
-
27
积分
-
2135
UID
-
2
IP卡 狗仔卡
|
|
| |
|
最后登录
-
2013-8-19
在线时间
-
29 小时
威望
-
73
金钱
-
556
注册时间
-
2012-6-26
阅读权限
-
50
帖子
-
41
精华
-
1
积分
-
73
UID
-
534
IP卡 狗仔卡
|
回复2#
| 目前，我只需要利用参数文件启动到nomount状态。，现在倒是能启动到nomount,但就是搞不懂那些提示会不会有什么影响。 |
-
alert_db1.txt
3.43 KB, 下载次数: 106
|
| |
|
最后登录
-
2013-8-19
在线时间
-
29 小时
威望
-
73
金钱
-
556
注册时间
-
2012-6-26
阅读权限
-
50
帖子
-
41
精华
-
1
积分
-
73
UID
-
534
IP卡 狗仔卡
|
|
| |
|
最后登录
-
2013-8-24
在线时间
-
1149 小时
威望
-
2135
金钱
-
37288
注册时间
-
2011-10-12
阅读权限
-
200
帖子
-
3851
精华
-
27
积分
-
2135
UID
-
2
IP卡 狗仔卡
|
startup nomount 之后查一下以下信息 并贴出来
col name for a40
col value for a40
col describ for a40
set linesize 130
SELECT x.ksppinm NAME, y.ksppstvl VALUE, x.ksppdesc describ
FROM SYS.x$ksppi x, SYS.x$ksppcv y
WHERE x.inst_id = USERENV ('Instance')
AND y.inst_id = USERENV ('Instance')
AND x.indx = y.indx
AND upper(x.ksppinm) like '%NUMA%'; |
|
| |
|
最后登录
-
2013-8-19
在线时间
-
29 小时
威望
-
73
金钱
-
556
注册时间
-
2012-6-26
阅读权限
-
50
帖子
-
41
精华
-
1
积分
-
73
UID
-
534
IP卡 狗仔卡
|
回复 5# 的帖子
SQL> set pages 9999;
SQL> SELECT x.ksppinm NAME, y.ksppstvl VALUE, x.ksppdesc describ
FROM SYS.x$ksppi x, SYS.x$ksppcv y
WHERE x.inst_id = USERENV ('Instance')
AND y.inst_id = USERENV ('Instance')
AND x.indx = y.indx
AND upper(x.ksppinm) like '%NUMA%'; 2 3 4 5 6
NAME VALUE DESCRIB
---------------------------------------- ---------------------------------------- ----------------------------------------
_rm_numa_sched_enable FALSE Is Resource Manager (RM) related NUMA sc
heduled policy enabled
_NUMA_pool_size Not specified aggregate size in bytes of NUMA pool
_enable_NUMA_optimization TRUE Enable NUMA specific optimizations
_NUMA_instance_mapping Not specified Set of nodes that this instance should r
un on
_rm_numa_simulation_pgs 0 number of PGs for numa simulation in res
ource manager
_rm_numa_simulation_cpus 0 number of cpus per PG for numa simulatio
n in resource manager
_db_block_numa 2 Number of NUMA nodes
7 rows selected. |
|
| |
|
最后登录
-
2013-8-24
在线时间
-
1149 小时
威望
-
2135
金钱
-
37288
注册时间
-
2011-10-12
阅读权限
-
200
帖子
-
3851
精华
-
27
积分
-
2135
UID
-
2
IP卡 狗仔卡
|
alter system set "_enable_NUMA_optimization"= false scope=spfile;
alter system set "_db_block_numa"=1 scope=spfile;
startup force nomount; |
|
| |
|
最后登录
-
2013-8-19
在线时间
-
29 小时
威望
-
73
金钱
-
556
注册时间
-
2012-6-26
阅读权限
-
50
帖子
-
41
精华
-
1
积分
-
73
UID
-
534
IP卡 狗仔卡
|
回复 7# 的帖子
| 太牛了，没有那个提示了。对了，这是准备上线的库。不知道这样改会不会有什么影响。 |
|
| |
|
最后登录
-
2013-8-19
在线时间
-
29 小时
威望
-
73
金钱
-
556
注册时间
-
2012-6-26
阅读权限
-
50
帖子
-
41
精华
-
1
积分
-
73
UID
-
534
IP卡 狗仔卡
|
|
| |
|
最后登录
-
2013-8-24
在线时间
-
1149 小时
威望
-
2135
金钱
-
37288
注册时间
-
2011-10-12
阅读权限
-
200
帖子
-
3851
精华
-
27
积分
-
2135
UID
-
2
IP卡 狗仔卡
|
Description
Oracle NUMA (Non Uniform Memory Architecture) support can be used with large SMP multiprocessor environments with NUMA hardware. When enabled Oracle NUMA support facilitates efficient use of underlying NUMA hardware and may improve database performance.
Oracle NUMA support needs the right combination of hardware, operating system and Oracle version.
With 10.2.0.4 and 11.1.0.7 patchsets, Oracle NUMA support can be enabled on common Operating Systems like AIX, HP-UX, Solaris, Linux and Windows if the underlying hardware characteristic is NUMA.
When running an Oracle database with NUMA support in a NUMA capable environment, Oracle will by default detect if the hardware and operating system are NUMA capable and enable Oracle NUMA support.
Some OS upgrades/patches may enable NUMA (For example on Linux NUMA is enabled with kernel release 2.6.9-67). Care should be taken before enabling NUMA support or leaving it on by default. Please see below under the ???Recommendation??? section. Contact your hardware vendor for recommendation and information on your system and operating system NUMA capabilities
Likelihood of Occurrence
The symptoms described in the following section generally occur when:
Oracle database NUMA support is enabled
Both operating system and hardware are NUMA capable.
And :
Database workload is memory constrained (or apply too much memory pressure on a given NUMA memory pool)
Dynamic reconfiguration events change the characteristics of the hardware or partition (e.g number of CPUs, memory available).
Some issues are OS/hardware specific. See bugs caused by NUMA section below.
Dynamic reconfiguration events removing resources from NUMA system such as an entire cell and all its processors are not supported (Please review Note:761065.1)
Possible Symptoms
The problems manifest usually with crashes with internal errors including:
ORA-4031
ORA-600 with argument KSKRECONFIGNUMA2
ORA-600 with argument KSBASEND_INTERNAL
ORA-600 with argument KSMHEAP_ALLOC1
ORA-27302: FAILURE OCCURRED AT: SSKGXPCRE3
Workaround or Resolution
Recommendation
Customers who have their SLA???s unaffected with NUMA enabled can continue to run with no changes.
It is strongly recommended to customers who want to enable NUMA do sufficient testing before going into production.
Apply all the bug fixes or patchset required for your Oracle database version. Fixes for all known NUMA issues in the Oracle database is available for download. Please review the known bugs section.
To disable NUMA consult the section "Steps to disable NUMA" covering the instructions to disable NUMA at the Oracle database level. To disable NUMA at the operating system or hardware level contact your hardware vendor.
Please review the "Caution" section below when disabling NUMA.
Caution
Disabling or enabling NUMA can change application performance.
It is strongly recommended to evaluate the performance after disabling or before enabling NUMA in a test environment.
Operating system and/or hardware configuration may need to be tuned or reconfigured when disabling Oracle NUMA support. Consult your hardware vendor for more information or recommendation
Steps to disable NUMA
Customers can download and apply patch for Bug 8199533 to disable NUMA support. This is a database patch and should be applied to the Database home. This patch is available for common platforms on 10.2.0.4 and 11.1.0.7 releases.
If you apply patch for Bug 8199533 then Oracle will no longer enabled NUMA support by default even if it detects a NUMA capable environment.
Oracle support does not recommended using init.ora parameter "_enable_NUMA_optimization" to disable NUMA. Customers should apply fix for Patch 8199533 to disable NUMA . The patch is rolling upgradeable.
This patch does not need to be applied to the ASM home. However if the same Oracle home is used for both RDBMS and ASM instances then this patch can be applied to the Oracle home.
To enable NUMA optimization after applying patch 8199533, set init.ora parameter _enable_NUMA_optimization=TRUE
上面的参数禁用了 NUMA ， NUMA的介绍可以参考 上面的文档， 不推荐 使用 Linux 6.2 + 10gR2这样的组合， 如果使用的话 本质上我也建议禁用NUMA |
|
