Shulou(Shulou.com)06/01 Report--

Phenomenon:

When oracle executes job:expdp, the database instance directly crashes. The error report is as follows: 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 man logind.conf (5) for details.

In the RHEL 7.x version, the systemd-logind service controls the user's behavior, and when the user exits, it cleans up all segments of the user's memory. Then there is a problem with the data pump of the scheduled task, and the memory segment called is oracle.

View the description of 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.

The default value is yes;, so when there are scheduled 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 will crash the Oracle ASM and database instances.

Solution:

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

2) restart the service

Systemctl daemon-reload

Systemctl restart systemd-logind

Refer to 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)

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.