ORA-00845: MEMORY_TARGET not supported on this system crs-2674 crs-2632

ORA-00845: MEMORY_TARGET not supported on this system crs-2674 crs-2632

PRCR-1079 : Failed to start resource ora.crsh**.db
CRS-5017: The resource action "ora.crsh**.db start" encountered the following error:
ORA-00845: MEMORY_TARGET not supported on this system
. For details refer to "(:CLSN00107:)" in "/u01/app/oracle/diag/crs/ol6-121-rac2/crs/trace/crsd_oraagent_oracle.trc".
CRS-2674: Start of 'ora.crsh**.db' on 'ol6-121-rac2' failed
CRS-2632: There are no more servers to try to place resource 'ora.crsh**.db' on that would satisfy its placement policy
CRS-5017: The resource action "ora.crsh**.db start" encountered the following error:
CRS-2674: Start of 'ora.crsh**.db' on 'ol6-121-rac2' failed

Database only failed on node 2 

CAUSE

The new ASM functionality uses /dev/shm on Linux for SGA and PGA management. The errors occur if either MEMORY_TARGET or MEMORY_MAX_TARGET is configured larger than the configured /dev/shm size, or if /dev/shm is mounted incorrectly.

SOLUTION

Update the  /etc/fstab as below to resize the /dev/shm to 4g and remount. Choose the size as per you requiment. If it is live environment, get it done by the UNIX Team.

FSTAB entry on node 2 before changes

tmpfs is 1.9 GB

FSTAB entry on node 2 after changes

Now the changes are made on Node2 and reboot is also done.

The problem is solved !!!

The same error was faced when the nodes rebooted and database doesn't comes up on node 1.