Is there an issue on the standby database not able to allocate SGA more than 193?
edited Oct 12, 2010 10:20PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 1 commentAnswered
We have 10.2.0.4 on Linux x86-64.
We have managed to start the production database using a 200Gb SGA but we have a problem on the standby server.
ORA-27123: unable to attach to shared memory segment
Linux-x86_64 Error: 22: Invalid argument
Additional information: 1
Additional information: 819212
The standby server is of the same hardware, same OS level, same RDBMS version, sames patches etc. There is no difference between the production server and the standby one.
The kernel settings are:
kernel.shmmni = 4096
kernel.shmall = 57671680
kernel.shmmax = 236223201280
Kernel Version: 2.6.18-128.2.1.el5
We have also tried a C program (see below) that ran as "oracle" to grab 200Gb of memory and it worked fine. It is only Oracle that cannot allocate more than circa 193Gb.
We have managed to start the production database using a 200Gb SGA but we have a problem on the standby server.
ORA-27123: unable to attach to shared memory segment
Linux-x86_64 Error: 22: Invalid argument
Additional information: 1
Additional information: 819212
The standby server is of the same hardware, same OS level, same RDBMS version, sames patches etc. There is no difference between the production server and the standby one.
The kernel settings are:
kernel.shmmni = 4096
kernel.shmall = 57671680
kernel.shmmax = 236223201280
Kernel Version: 2.6.18-128.2.1.el5
We have also tried a C program (see below) that ran as "oracle" to grab 200Gb of memory and it worked fine. It is only Oracle that cannot allocate more than circa 193Gb.
0