What should I do if the RemoveIPC of RedHat7.2 sets the main yes to cause rac downtime?

Today, I will talk to you about what to do about the rac downtime caused by RedHat7.2 's RemoveIPC setting, the main yes. Many people may not know much about it. In order to make you understand better, the editor summarized the following content for you. I hope you can get something from this article.

Recently, we are going to build a database rac environment based on RedHat7.2. After reading the documents, we found that the new features of version 7.2 of RedHat, Centos and Oel will cause database downtime. The details are as follows:

In RedHat7.2, systemd-logind Services introduces a new feature: when a user exits os completely, remove loses all IPC objects.

This feature is controlled by the RemoveIPC option in the / etc/systemd/logind.conf parameter file.

In RedHat7.27.2, the default value for RemoveIPC is yes

Therefore, when the last oracle or Grid user exits, the operating system will remove the shared memory segments and semaphores of that user

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

Oracle Linux7.2 avoids this problem by explicitly setting RemoveIPC to no,Oracle Linux7.2 in the / etc/systemd/logind.conf configuration file

Solution:

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 os.

After reading the above, do you have any further understanding of what to do if the main yes of RedHat7.2 's RemoveIPC setting causes rac downtime? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.