Dears,
I have 2 servers in RAC mode via ASM (DB Version 12cR1, OS CentOS 7), each node has 32 GB or RAM.
I configured the database to use 14 GB of RAM during the installation (AMM is enabled too), yesterday the system admin decreased the RAM on all nodes from 32 GB to 16 GB, thus the database can't be started because of memory changes:
[oracle@db1 root]$ srvctl start database -d xxx
PRCR-1079 : Failed to start resource ora.xxx.db
CRS-5017: The resource action "ora.xxx.db start" encountered the following error:
ORA-01078: failure in processing system parameters
ORA-01565: error in identifying file '+DATA/xxx/spfilexxx.ora'
ORA-17503: ksfdopn:2 Failed to open file +DATA/xxx/spfilexxx.ora
ORA-01034: ORACLE not available
ORA-27123: unable to attach to shared memory segment
Linux-x86_64 Error: 2: No such file or directory
Additional information: 2667
Additional information: 229081089
Additional information: 1614807040
. For details refer to "(:CLSN00107:)" in "/u01/app/11.2.0/grid/diag/crs/xxx-db2/crs/trace/crsd_oraagent_oracle.trc".
CRS-2674: Start of 'ora.xxx.db' on 'xxx-db2' failed
CRS-5017: The resource action "ora.xxx.db start" encountered the following error:
ORA-01078: failure in processing system parameters
ORA-01565: error in identifying file '+DATA/xxx/spfilexxx.ora'
ORA-17503: ksfdopn:2 Failed to open file +DATA/xxx/spfilexxx.ora
ORA-01034: ORACLE not available
ORA-27123: unable to attach to shared memory segment
Linux-x86_64 Error: 2: No such file or directory
Additional information: 2667
Additional information: 233668609
Additional information: 1614807040
. For details refer to "(:CLSN00107:)" in "/u01/app/11.2.0/grid/diag/crs/xxx-db1/crs/trace/crsd_oraagent_oracle.trc".
CRS-2674: Start of 'ora.xxx.db' on 'xxx-db1' failed
CRS-2632: There are no more servers to try to place resource 'ora.xxx.db' on that would satisfy its placement policy
[oracle@db1 root]$
I increased the shm size by remounting it with 32 GB size (source: https://www.krenger.ch/blog/ora-00845-memory_target-not-supported-on-this-system/ ) but this did not work.
When try to reset the system variable MEMORY_TARGET to smaller value (7 GB) the database was stopped, thus this is normal I can't reset the parameter value, and I'm stuck where I can't start the database too:
SQL> alter system set MEMORY_TARGET=7G scope=spfile;
alter system set MEMORY_TARGET=7G scope=spfile
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0
I had a backup of PFILE because I used it when building the Data Guard for the cluster, I changed the MEMORY_TARGET and other memory related parameters into the half but still facing the following:
SQL> startup pfile='initprimary_backup.ora';
ORA-00449: background process 'RBAL' unexpectedly terminated with error 448
SQL>
Is there any other way to start the database (force option didn't work) in order to change the memory target, or to reset this parameter when database is down ?
Kindly advice,
Thanks and best regards ,,,