000013960 - Error code 601 when installing RSA Authentication Manager 7.1 DB patch on latest Sun hardware

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

Article Content

Article Number000013960
Applies ToRSA Authentication Manager 7.1.2 (7.1 SP2)
Solaris v10
RSA Oracle patch installation (
IssueSuccessful installation of RSA Authentication Manager 7.1 Oracle database patch on latest Sun hardware
Error message in patch_install.log :

Error 601 : failure executing /RSASecurity/RSAAuthenticationManager/DB/TMP/upgrade 10204.sh,written code =1
Error message in RSASecurity/RSAAuthenticationManager/db/cfgtoollogs/dbca/xxxxxxxx\xxxxxxxx.log :

File "/var/opt/oracle/oratab" is not accessible.
ORA-04031: unable to allocate 1048608 bytes of shared memory ("shared pool","unknown object","sga heap(1,0)","row cache")

Note : where 'xxxxxxxx' is the internal id tag of your internal Oracle instance.
ResolutionThere is a parameter within Oracle called SGA_MAX_SIZE. This is defined as the setting that controls the maximum memory used by the Oracle shared pool.

The default setting is approximately 35% of total memory, which is insufficient on some systems.

This adjustment can be made from directly within the in-built Oracle instance.

To adjust from Oracle's SQLPlus utility, first obtain the Oracle DB password :

1. From the commandline, cd to utils directory under RSA_HOME (typically, /RSASecurity/RSAAuthenticationManager/utils).

2. Execute the following command and note the output :

./rsautil manage-secrets -a get com.rsa.db.root.password

You'll be prompted for your system's master password. Enter in this password and you'll see the Oracle password returned as follows :

com.rsa.db.root.password: HIKyB0Eobm

3. Execute the following commands :

. ./rsaenv     (Please note the two dots, ie. "dot space dot slash rsaenv")

sqlplus sys/<value from step2> as sysdba

SQL>  sqlplus sys/HIKyB0Eobm as sysdba

4. You will now have root access to the Oracle instance using SQLPlus. Now execute the following command :

SQL > alter system set sga_max_size=900M scope = spfile;

Once complete, the DB installation should proceed normally.
Legacy Article IDa52020