Removeipc=yes's RHEL7.2 will crash Oracle ASM instances and Oracle database instances

Source: Internet
Author: User

An instance of the 11204 library on centos7.2 was crash, and the check alert was found as follows:

wed sep 21 00:00:11 2016errors in file /apps/oracle/diag/rdbms/xberp/xberp/ Trace/xberp_ckpt_17537.trc:ora-27157: os post/wait facility removedora-27300: os  system dependent operation:semop failed with status: 43ora-27301: os  failure message: Identifier removedORA-27302: failure occurred at:  sskgpwwait1wed sep 21 00:00:11 2016errors in file /apps/oracle/diag/rdbms/ XBERP/XBERP/TRACE/XBERP_DBRM_17523.TRC:ORA-27157: OS POST/WAIT FACILITY REMOVEDORA-27300:  os system dependent operation:semop failed with status: 43ora-27301:  os failure message: identifier removedora-27302: failure occurred at:  sskgpwwait1wed sep 21 00:00:11 2016errors in file /apps/oracle/diag/ Rdbms/xberp/xberp/trace/xberp_mman_17527.trc:ora-27157: os post/wait facility removedora-27300: os  system dependent operation:semop failed with status: 43ora-27301: os  failure message: identifier removedora-27302: failure occurred at:  sskgpwwait1wed sep 21 00:00:11 2016errors in file /apps/oracle/diag/rdbms/ XBERP/XBERP/TRACE/XBERP_J002_14570.TRC:ORA-27157: OS POST/WAIT FACILITY REMOVEDORA-27300:  os system dependent operation:semop failed with status: 43ora-27301:  os failure message: identifier removedora-27302: failure occurred at:  sskgpwwait1CKPT  (ospid: 17537): terminating the instance due to  error 27157wed sep 21 00:00:11 2016errors in file /apps/oracle/diag/ Rdbms/xberp/xberp/trace/xbeRp_j000_14566.trc:ora-27157: os post/wait facility removedora-27300: os system  dependent operation:semop failed with status: 43ora-27301: os failure  message: Identifier removedORA-27302: failure occurred at:  Sskgpwwait1instance terminated by ckpt, pid = 17537errors in file  /apps/oracle/diag/rdbms/xberp/xberp/trace/xberp_ckpt_17537.trc:ORA-27300: OS system  Dependent operation:semctl failed with status: 22ora-27301: os failure  message: Invalid argumentORA-27302: failure occurred at:  sskgpwrm1ora-27157: os post/wait facility removedora-27300: os system  dependent operation:semop failed with status: 43ora-27301: os failure  Message: identifier removedora-27302: failure occurred at: sskgpwwait1wed sep 21 10:20:34 2016 

Describe:

In centos7.2, the Systemd-logind service introduces a new feature that removes all IPC objects after a user exits the OS completely.

This attribute is controlled by the REMOVEIPC option in the/etc/systemd/logind.conf parameter file.

In centos7.2, the default value for REMOVEIPC is yes

Therefore, when the last Oracle or grid user exits, the operating system will remove the user's shared memory segments and semaphores

Because Oracle ASM and database use the shared memory segments, the Remove shared memory segments will crash the Oracle ASM and database instances.


Oracle Linux 7.2 Avoids this problem by explicitly setting REMOVEIPC as No,oracle Linux7.2 in the/etc/systemd/logind.conf configuration file.


Workaround:

1) Set Removeipc=no in/etc/systemd/logind.conf

2) Reboot the server or restart Systemd-logind as follows:

# Systemctl Daemon-reload

# systemctl Restart Systemd-logind


These errors are related to the OS and may be referenced in the documentation on MOS:

Alert:setting Removeipc=yes on Redhat 7.2 crashes ASM and Database Instances as well as any application that Uses a Share D Memory Segment (SHM) or semaphores (SEM) (document ID 2081410.1)



This article is from the "just out of the shell of the Birds" blog, please be sure to keep this source http://qhd2004.blog.51cto.com/629417/1854907

Removeipc=yes's RHEL7.2 will crash Oracle ASM instances and Oracle database instances

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.