Database Installation and Operation Fails if RemoveIPC=yes Is Configured for systemd
If RemoveIPC=yes is configured for systemd, interprocess communication (IPC) is terminated for a non-system user’s processes when that user logs out. This setting, which is intended for laptops, can cause software problems on server systems. For example, if the user is a database software owner such as oracle for Oracle Database, this configuration can cause database installation to fail or database services to crash.
By default, Oracle Linux 7 Update 2 configures RemoveIPC=no in /etc/systemd/logind.conf to prevent systemd from terminating IPC. However, if you have touched this file before updating your system to Oracle Linux 7 Update 2, the update installs the new version of the file as /etc/systemd/logind.conf.rpmnew and does not set RemoveIPC=no in /etc/systemd/logind.conf.
To avoid database crashes, set RemoveIPC=no in /etc/systemd/logind.conf and run systemctl reboot to reboot the system. (Bug ID 22224874)
Reference Document: ORA-27300 ORA-27301 ORA-27302 ORA-27157 Database Crash (Doc ID 438205.1)
Master in Computer Science and Post-Graduation in MIS. EDRP (EC-Council Disaster Recovery Professional), Security+, OCP 7.3, 10, 11g, 12c, 11i, R12, OCE 11i System Administration, Linux and RAC 10g, 11g, and OCS in Performance Tuning. More than 18 years’ Information Technology consecutive hands-on experience, possess diversified business and technical background on a wide variety platforms, hardware and operating systems, in the Capacity of Sr. Team Lead Consultant, Sr. Database Administrator, Sr. Applications DBA, Sr. Resident Consultant and Manager Systems. Extensive experience in managing ERP environments and large Databases including Space Management, Backup and Recover, Performance Tuning, Routine Tasks Automation and Database/Applications Health Checks. Started Oracle related Career from Oracle 6. Worked on 7, 8, 9i, 10g, 11g, 12c & e-Business 11.0.3, 11.5.9, 18.104.22.168, R12 and R12.2. Distinct Technical Jobs such as installation, migration, implementation, upgrade, cloning, and maintenance were performed hundreds number of times. Database and Applications (Security & Performance) related Health Checks, RAC & Data Guard Implementation/Troubleshooting Switchover/Failover were also made during the tenure on the basis of As-When-Needed. Contact Me for Database/Applications Installation, Upgrade, Migration, Disaster Recovery, Troubleshooting and Health Checks.
Find Us On