RHEL 7上oracle 莫名宕機 ORA-27300

現象:

oracle 執行job:expdp,數據庫實例直接宕掉,報錯以下:
ORA-27300: OS system dependent operation:semctl failed with status: 22
ORA-27301: OS failure message: Invalid argument
ORA-27302: failure occurred at: sskgpwrm1
ORA-27157: OS post/wait facility removed
ORA-27300: OS system dependent operation:semop failed with status: 36
ORA-27301: OS failure message: Identifier removed
ORA-27302: failure occurred at: sskgpwwait1

數據庫版本11.2.0.4,操做系統版本:rhel 7
檢查操做系統日誌,定時任務日誌並沒有異常;
緣由:
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 man logind.conf(5) for details.
在 RHEL 7.x的版本里,systemd-logind 服務控制着用戶的行爲,當用戶退出,會清理該用戶的全部內存段.那麼定時任務的數據泵就有問題了,調用的內存段是oracle的;
查看removeipc的說明:
RemoveIPC=
Controls whether System V and POSIX IPC objects belonging to the user shall be removed when the user fully logs out. Takes a boolean argument. If enabled, the user
may not 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 are excluded from the effect of this setting. Defaults to "yes".
The default value for RemoveIPC in RHEL7.2 is yes.
默認值爲yes; 因此當有定時任務時:
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 will crash the Oracle ASM and database instances.
解決辦法:
1) Set RemoveIPC=no in /etc/systemd/logind.conf
2) 重啓服務
systemctl daemon-reload
systemctl restart systemd-logind

參考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)