Article Content
Article Number | 000031254 |
Applies To | RSA Product Set: Via Lifecycle and Governance (L&G), Identity Management and Governance (IMG) RSA Product/Service Type: Hardware and Software Appliance RSA Version/Condition: 6.9.1 Platform: Oracle 11g |
Issue | When RSA Via L&G is installed on an appliance, the values that are configured during the installation for the Oracle Instance for the Oracle SGA and PGA settings are based on how much physical memory is available on the appliance. Typically on systems which have upwards of 32gb of Memory, 1/2 of the memory is allocated for Oracle, and that is evenly divided between the SGA and PGA. This means that the largest default value that is set during installation is 8gb for the SGA and 8gb for the PGA. |
Cause | There is a configuration issue specific to Version 6.9.1 for a new installation on a system that is not upgraded from an earlier version. In a new V6.9.1 installation, values for sga_max_size and pga_aggregate_target are correctly calculated, but the value for sga_target is left at the default Oracle 11g installation value of 512M. In this situation, following the instructions from the older knowledgebase article mentioned above can result in database startup problem and an ORA-00821 error. Note: If an ORA-00821 error is occurring, knowledge base article 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 can be used to resolve the error. |
Resolution | The correct sequence of steps depends on the current settings. Determine the existing Oracle SGA and PGA values and then follow the guidelines noted below. acm stop OR service aveksa_server stop
$ sqlplus "/as sysdba"
$ sqlplus "/as sysdba"
sql> sho parameter sga_
sql> alter system set sga_target = 2000M comment='internally adjusted' scope=spfile;
SQL> sho parameter sga_
sql> alter system set sga_target = 8g comment='internally adjusted' scope=spfile;
$ acm stopdb
$ sqlplus "/as sysdba"
$ acm stopdb
$ sqlplus "/as sysdba"
$ acm start
$ sqlplus "/as sysdba" If you are unsure of any of the steps above or experience any issues, contact RSA Support and quote this article number for further assistance. |