Dbvisit create Standby database fails with error RMAN-04014: startup failed: ORA-27125: unable to create shared memory segment
Problem Details
Problem Statement
Creating a Standby database fails with below mentioned error in some cases when Standby server memory is not configured correctly or sometimes it could be due to dbvagentmanager running as systemctl that does not inherit the system limits /etc/security/limits.conf.
Applicable Error Code
RMAN-03002: failure of startup command at 01/25/2023 00:12:29
RMAN-04014: startup failed: ORA-27125: unable to create shared memory segment
Linux-x86_64 Error: 1: Operation not permitted
Affected Versions
v11
Affected Platforms
Linux
Description
A. If the problem is due to misconfigured memory in the standby server then refer to the below support article from oracle
Not Able To Start The Database, fails with ORA-27125: unable to create shared memory segment (Doc ID 2242978.1)
B. If this is caused due to dbvagentmanager running as systemctl then follow the below steps to resolve the error
1. Stop and disable dbvagentmanager service:
sudo systemctl stop dbvagentmanager
sudo systemctl disable dbvagentmanager...
[Service]
LimitNOFILE=65536
LimitNPROC=16384
LimitMEMLOCK=infinity
...3. Enable and start the service again
sudo systemctl daemon-reload
sudo systemctl enable dbvagentmanager
sudo systemctl start dbvagentmanager
We have executed the steps in the article and we no longer get ORA-27125: unable to create shared memory segment.
We now get: RMAN-04014: startup failed: ORA-16026: parameter LOG_ARCHIVE_DEST_1 contains an invalid attribute value
Which is more in line with what we saw and tested.