000030859 - RSA VIA L&G / IMG / Aveksa - After increasing SGA_MAX and restarting datatabase ASM and database do not start due to 512M or small SGA_TARGET value

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000030859
Applies ToRSA Product Set: Identity Management and Governance
RSA Product/Service Type: Appliance
RSA Version/Condition: 6.9.1
Oracle 11.2
IssueAfter changing the SGA_MAX value to something large a restart of the database is required. 
When starting the database you receive the error:
Error on startup: ORA-00821: Specified value of sga_target 512M is too small, needs to be at least 768M
CauseThe newly increased SGA_MAX value results in Oracle allocating more RAM and more processes than it did prior.
The additional resources exhaust the 512M default sga_target that is set.
ResolutionFrom another host that is operational perform the following:
su - oracle
sqlplus / as sysdba
create pfile='/tmp/initFIX.ora' from spfile
Copy the /tmp/initFix.ora file from the remote host and edit the SGA_MAX and SGA_TARGET to values that are appropriate for your appliance / deployment.
copy this file to the failing host /tmp directory

Login or su to oracle on the failing host:
The control_files parameter references a file that will likely not match your system.  You will need to collect the correct filename and edit the initFIX.ora.
Here is how to collect your control filename
su - oracle
cd +DG01/avdb/controlfile/
ls -l
Record the value of name for "CONTROLFILE" it should resemble Current.260.873286311
Edit the initFIX,ora and update the control_files suffix to be the correct filename.
exit oracle to unset the 3 variables exported above before performing the below procedure.
su - oracle
acm startoracle  (which should fail with the memory error)
sqlplus / as sysdba
startup pfile='/tmp/initFIX.ora'
Database should start
create spfile='+DG01/avdb/spfileavdb.ora' from pfile='/tmp/initFIX.ora';
exit    (to exit sqlplus)
acm stoporacle
acm startoracle (system will come up with the RAM settings that were contained within the initFIX.ora from the other host.

In case you do not have another host available, attached to this KB is a initFIX.ora with 4GB set for sga_max and sga_target.  Edit to set SGA values that are appropriate for your appliance / deployment.

NotesThis issue has been noticed on appliances where the alert_AVDB.log showed that the ALTER command to increase SGA_TARGET was executed but subsequent restart parameter values still showed SGA_TARGET set to 512M.