ORA-27300 on RHEL 7 on Oracle's inexplicable outage

Source: Internet
Author: User
Tags posix system log

phenomena:

oracle 执行job:expdp,数据库实例直接宕掉,报错如下: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: 36ORA-27301: OS failure message: Identifier removedORA-27302: failure occurred at: sskgpwwait1

Database version 11.2.0.4, operating system version: Rhel 7
Check the operating system log, the scheduled task log is not abnormal;
Reason:
On Redhat 7.x, Systemd-logind Service introduced a new feature to remove all IPC objects when a user fully logs out.
The feature is controled by the option REMOVEIPC in the/etc/systemd/logind.conf configuration file,
See Mans Logind.conf (5) for details.
In the RHEL 7.x version, the Systemd-logind service controls the behavior of the user and, when the user exits, cleans up all of the user's memory segments. Then the data pump for the scheduled task is problematic, and the memory segment of the call is Oracle;
See instructions for REMOVEIPC:
Removeipc=
Controls whether System V and POSIX IPC objects belonging to the user shall is removed when the user fully logs out. Takes a Boolean argument. If enabled, the user
May isn't consume IPC resources after the last of the user's sessions terminated. This covers System V semaphores, shared memory and message queues, as well as POSIX
Shared memory and message queues. Note that IPC objects of the root user is excluded from the effect of this setting. Defaults to "yes".
The default value for REMOVEIPC in RHEL7.2 is yes.
The default value is yes; So when you have timed tasks:
As a result, when the last Oracle or grid user disconnects, the OS removes shared memory segments and semaphores for those Users.
As Oracle ASM and Databases use shared memory segments for SGA, removing shared memory segments would crash the Oracle ASM and database instances.
Workaround:
1) Set Removeipc=no in/etc/systemd/logind.conf
2) Restart Service
Systemctl Daemon-reload
Systemctl Restart Systemd-logind

Reference MOS:
ORA-27300 ORA-27301 ORA-27302 ORA-27157 Database Crash (Doc ID 438205.1)
Failed Install of RAC with asm:ora-27300 ORA-27302 ORA-27300 ORA-27301 ORA-27302 (Doc ID 2099563.1)

ORA-27300 on RHEL 7 on Oracle's inexplicable outage

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.