11G RAC 使用 srvctl start database -d psdb 节点2 起不来

[oracle@psdb1 ~]$ srvctl stop database -d psdb

[oracle@psdb1 ~]$ srvctl start database -d psdb
PRCR-1079 : Failed to start resource ora.psdb.db
CRS-5017: The resource action "ora.psdb.db start" encountered the following error:
ORA-00603: ORACLE server session terminated by fatal error
ORA-27544: Failed to map memory region for export
ORA-27300: OS system dependent operation:skgxpmmap failed with status: 0
ORA-27301: OS failure message: Error 0
ORA-27302: failure occurred at: skgxpmap1
ORA-27303: additional information: maximum(512) number of regions/context exeeded 512
Process ID: 0
Session ID: 0 Serial number: 0
. For details refer to "(:CLSN00107:)" in "/u01/11.2.0/grid/log/psdb2/agent/crsd/oraagent_oracle//oraagent_oracle.log".

CRS-2674: Start of 'ora.psdb.db' on 'psdb2' failed
CRS-2632: There are no more servers to try to place resource 'ora.psdb.db' on that would satisfy its placement policy

 --alter 日志

Cluster communication is configured to use the following interface(s) for this instance
169.254.12.215
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
Errors in file /u01/app/oracle/diag/rdbms/psdb/psdb/trace/psdb_ora_67269.trc (incident=320003):
ORA-00603: ORACLE server session terminated by fatal error
ORA-27544: Failed to map memory region for export
ORA-27300: OS system dependent operation:skgxpmmap failed with status: 0
ORA-27301: OS failure message: Error 0
ORA-27302: failure occurred at: skgxpmap1
ORA-27303: additional information: maximum(512) number of regions/context exeeded 512
Incident details in: /u01/app/oracle/diag/rdbms/psdb/psdb/incident/incdir_320003/psdb_ora_67269_i320003.trc
opiodr aborting process unknown ospid (67269) as a result of ORA-603
Tue May 21 20:23:10 2019
Errors in file /u01/app/oracle/diag/rdbms/psdb/psdb/trace/psdb_ora_68826.trc (incident=320004):
ORA-00600: internal error code, arguments: [ksxp_open: ref2], [0], [0x5043AD6390], [1], [1], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/psdb/psdb/incident/incdir_320004/psdb_ora_68826_i320004.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.

---trace 文件内容

*** 2019-05-21 20:22:58.861
Large Pages segment allocation succeed, size = 2147483648, shmid = 21430275, target_node = 129, large page used 1024
Allocation of segment with Large pages failed, size = 2147483648. Trying smaller size segments

 

--现象：节点1 和节点2 的 系统参数一致；但是节点1可以通过上面的命令正常启动数据库；节点2 启动报错

 

 

--解决办法

把节点2大页禁用　　 vm.nr_hugepages = 0

---此次只针对 /sys/kernel/mm/transparent_hugepage/enabled 是否禁用；

---另一个参数可以不禁用/sys/kernel/mm/transparent_hugepage/defrag

 

方案1
在rc.local中增加如下内容

if test -f /sys/kernel/mm/transparent_hugepage/enabled; then
echo never > /sys/kernel/mm/transparent_hugepage/enabled
fi
if test -f /sys/kernel/mm/transparent_hugepage/defrag; then
echo never > /sys/kernel/mm/transparent_hugepage/defrag
fi

方案2
通过修改grub启动参数来实现

[root@middle ~]# cat /etc/default/grub
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="crashkernel=auto rd.lvm.lv=cl/root rd.lvm.lv=cl/swap rhgb quiet"
GRUB_DISABLE_RECOVERY="true"
将 GRUB_CMDLINE_LINUX="crashkernel=auto rd.lvm.lv=cl/root rd.lvm.lv=cl/swap rhgb quiet" 这一行修改为

GRUB_CMDLINE_LINUX="crashkernel=auto rd.lvm.lv=cl/root rd.lvm.lv=cl/swap rhgb quiet transparent_hugepage=never"

并执行

[root@middle ~]# grub2-mkconfig -o /boot/grub2/grub.cfg

方案3
以上两个方案不是能实时生效，需要重启系统。如果需要实时生效需要

echo never >> /sys/kernel/mm/transparent_hugepage/enabled
echo never >> /sys/kernel/mm/transparent_hugepage/defrag

 

转载于:https://www.cnblogs.com/ss-33/p/10913279.html