000011569 - Authentication Manager SP4 upgrade installation fails on Solaris 10

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 Number000011569
Applies ToAuthentication Manager 7.1 SP4
Authentication Manager Service Pack 4 upgrade kit
Sun Solaris 10
IssueAuthentication Manager SP4 installation fails on Solaris 10
Oracle up and running

# ./setupSolaris.bin -console 

 

          Initializing Wizard........
          Launching InstallShield Wizard........
 


-------------------------------------------------------------------------------
RSA Authentication Manager 7.1 SP4 Installer

 

Welcome to the RSA Authentication Manager 7.1 SP4 Installer.

 

This installer will patch your existing RSA Authentication Manager 7.1
installation with the latest updates.

 

 To continue, select Next.

 


Press 1 for Next, 3 to Cancel or 5 to Redisplay [1]

 

-------------------------------------------------------------------------------
RSA Authentication Manager 7.1 SP4 Installer

 

The Installer will stop the RSA Authentication Manager services running on this
installation. To Restart RSA Authentication Manager services at the end of the
installation, select the Restart Services option below and then select Next.

 

Note: If the Restart Services option is left unchecked, please remember to
restart the services at your convenience.

 

[X] 1 - Restart Authentication Manager Services
[ ] 2 - Do not Restart Authentication Manager Services

 

To select an item enter its number, or 0 when you are finished: [0]

 


Press 1 for Next, 3 to Cancel or 5 to Redisplay [1]

 

Cannot upgrade database patch. Share memory size is insufficient for the
upgrade process. Use the Tune-System CLU to increase share memory size to at
least 900MB and try the upgrade again.

 

[OK]


from the <rsa_home>/logs/patch_install.log

(Dec 30, 2010 10:05:39 AM), Install, com.installshield.rsa.ippi.install.actions.wizard.PreReqChecks, msg1, Checking prerequisite for database share memory...
(Dec 30, 2010 10:05:40 AM), Install, com.installshield.rsa.ippi.install.actions.wizard.PreReqChecks, msg1, sga_max_size: 612368384 (584MB).
(Dec 30, 2010 10:05:40 AM), Install, com.installshield.rsa.ippi.install.actions.wizard.PreReqChecks, msg1, sga_target: 612368384 (584MB).
(Dec 30, 2010 10:05:40 AM), Install, com.installshield.rsa.ippi.install.actions.wizard.PreReqChecks, err, Cannot upgrade database patch. Share memory size is insufficient for the upgrade process. Use the Tune-System CLU to increase share memory size to at least 900MB and try the upgrade again.


Tune-System CLU
CauseShare memory size is insufficient
ResolutionHow to connect to sqlplus
1. Login to the solaris machine as the user you have installed AM under, it will not be root.  

If you do not know who that user is, do the following to obtain it using the ps -ef | grep command:

[root@badboy etc]# ps -ef | grep oracle
ammgr      918     1  0 Jul21 ?        00:00:00 oraclewxlw2law (LOCAL=NO)
ammgr      930     1  0 Jul21 ?        00:00:00 oraclewxlw2law (LOCAL=NO)
ammgr      938     1  0 Jul21 ?        00:00:00 oraclewxlw2law (LOCAL=NO)
<snip>
root     19763 19724  0 20:10 pts/0    00:00:00 grep oracle

Notice in this instance, I am running the software as ammgr, that is the user you need to log in as.

2) cd to the <install path>/utils, noting:

    -The default installation directory of the product is:
        /usr/local/RSASecurity/RSAAuthenticationManager/utils
    -Adjust this path if you have used a different installation path from the default

3) set the environment variables for sqlplus access by doing the following

    . ./rsaenv <hit return>

    -NOTE THE FORMAT ABOVE:     <period>[SPACE]<period>/rsaenv

4) obtain the password for your db instance by running the following command, noting in my example MY password is YMax1EZ3yG, yours will be different as each PW is unique per instance

    bash-3.00$ ./rsautil manage-secrets -a get com.rsa.db.root.password
    Enter Master password: ***********
    com.rsa.db.root.password: v2Nw95GsMU

Record that password, upper/lower sensitive.

5) connect to oracle as follows, using YOUR password from step 4 where I have noted mine here

    bash-3.00$ sqlplus sys/v2Nw95GsMU as sysdba

You will see the following and be presented with the SQL> prompt as such:

    SQL*Plus: Release 10.2.0.4.0 - Production on Thu Jul 28 16:07:10 2011

    Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.


    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
    With the Partitioning, Data Mining and Real Application Testing options

    SQL>

6) issue the following commands at the SQL prompt, noting you must terminate each with a ; then hit return

    SQL>shutdown immediate;
    SQL>startup nomount;
    SQL>create pfile='oldpfile.ora' from spfile;
    SQL>alter database mount;
    SQL>alter database open;


7) Open a second window to the solaris server and log in as root, NOTE: do not terminate the SQL session window, keep it open and active, do not close it!

8) In this second window from the command line, cd to the /usr/local/RSASecurity/RSAAuthenticationManager/db/dbs (or its equivalent if you did not use the default installation path)

9) vi the file we just created, oldpfile.ora

    [root@badboy dbs]# cd /usr/local/RSASecurity/RSAAuthenticationManager/db/dbs

    [root@badboy dbs]# ls
    hc_wxlw2law.dat  init.ora    oldpfile.ora   spfilewxlw2law.ora
    initdw.ora       lkWXLW2LAW  orapwwxlw2law

    [root@badboy dbs]# vi oldpfile.ora   

10) Search in the orapfile.ora for the string 'sga_target' in the file (this value is in bytes), it will look something like this:

    *.sga_target=1084227584

    (HINT: found on line 32 on a test system)

10) change the value of *.sga_target=943718400, then save the file, we are done with this window now

11) Return to the SQL> window and these sql commands:


    SQL> shutdown immediate;
    SQL>create spfile from pfile='oldpfile.ora';
    SQL>startup;

12) exit sql

    SQL>exit
NotesSample session demonstrating SQL steps:

[ammgr@badboy RSAAuthenticationManager]$ cd /usr/local/RSASecurity/RSAAuthenticationManager/utils
[ammgr@badboy utils]$ ./rsautil manage-secrets -a get com.rsa.db.root.password

Enter Master password:
You must enter the Master password: ********

[ammgr@badboy utils]$ ./rsautil manage-secrets -a get com.rsa.db.root.password
Enter Master password: ********
com.rsa.db.root.password: v2Nw95GsMU

[ammgr@badboy utils]$ . ./rsaenv

[ammgr@badboy utils]$ sqlplus sys/v2Nw95GsMU as sysdba

SQL*Plus: Release 10.2.0.4.0 - Production on Thu Jul 28 20:27:50 2011

Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.


Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, Data Mining and Real Application Testing options

SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup nomount;
ORACLE instance started.

Total System Global Area 1090519040 bytes
Fixed Size                  1266996 bytes
Variable Size             469764812 bytes
Database Buffers          603979776 bytes
Redo Buffers               15507456 bytes
SQL> create pfile='oldpfile.ora' from spfile;

File created.

SQL> alter database mount;

Database altered.

SQL> alter database open;

Database altered.

SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, Data Mining and Real Application Testing options
[ammgr@badboy utils]$

NOTE 1: Where RSA_AM_HOME is referenced in this solution, this refers to the top level of your installation directory, the default being /usr/local/RSASecurity/RSAAuthenticationManager.  If you have modified the installation path, change this path to reflect what prefixes RSASecurity/RSAAuthenticationManager, which are fixed values, for example, if you installed into /opt/applications, RSA_AM_HOME would then be /opt/applications/RSASecurity/RSAAuthenticationManager

NOTE 2:Connecting to sqlplus requires you to obtain the db password, that is not listed in these directions, with my apologies.

NOTE 3: You will need the master password to perform one of these steps, make sure you have it readily available.

NOTE 4: you should back up your database before this procedure, and also note you will be down on the primary server when this is being run.
Legacy Article IDa53448

Attachments

    Outcomes