000030555 - RSA Identity Management and Governance 6.9.1 install fails with Oracle CRS-2728  A resource type with the name is already registered.

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support on Jan 29, 2018
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000030555
Applies ToRSA Product Set: Identity Management and Governance
RSA Product/Service Type: Appliance
RSA Version/Condition: 6.9.1
Platform: Linux
O/S Version: Red Hat Enterprise Linux 5.x
IssueAfter having problems upgrading to RSA Identity Management and Governance 6.9.1 (IMG), a customer uninstalled IMG and then tried to re-install, but the Oracle portion of the install would not complete.  The following error was seen in the /tmp/aveksa-install.log:
 

CRS-2728: A resource type with the name 'ora.daemon.type' is already registered
CRS-4000: Command Add failed, or completed with errors.
CRS-2728: A resource type with the name 'ora.cssd.type' is already registered
CRS-4000: Command Add failed, or completed with errors.
CauseThe Oracle error that a resource type already existed is a result of an existing installation process running but not completing.

Review of the system processes  (ps -ef) shows the following.  Note that this is not a list of all processes, but a subset selected to highlight this issue:
 

root     11475     1  0 09:59 pts/2    00:00:00 tail -f /tmp/OraInstall2015-06-11_09-59-09AM/installActions2015-06-11_09-59-09AM.log
root     16001   308  0 10:21 pts/2    00:00:00 su - oracle
oracle   16002 16001  0 10:21 pts/2    00:00:00 -bash
root     16292 16002  0 10:29 pts/2    00:00:00 su
root     16294 16292  0 10:30 pts/2    00:00:00 bash
root     17273     1  0 09:31 ?        00:00:00 tail -f /tmp/OraInstall2015-06-11_09-31-47AM/installActions2015-06-11_09-31-47AM.log
root     21225     1  0 10:38 pts/2    00:00:00 tail -f /tmp/OraInstall2015-06-11_10-38-35AM/installActions2015-06-11_10-38-35AM.log
root     25872     1  0 09:37 ?        00:00:00 tail -f /tmp/OraInstall2015-06-11_09-37-18AM/installActions2015-06-11_09-37-18AM.log
root     28974  3960  0 11:09 ?        00:00:00 sshd: oracle [priv]
oracle   28979 28974  0 11:09 ?        00:00:00 sshd: oracle@pts/4
oracle   29025     1  0 05:12 ?        00:00:01 /u01/app/11.2.0/grid/bin/ohasd.bin reboot
oracle   29185     1  0 05:13 ?        00:00:00 /u01/app/11.2.0/grid/bin/evmd.bin
oracle   29240 29185  0 05:13 ?        00:00:00 /u01/app/11.2.0/grid/bin/evmlogger.bin -o /u01/app/11.2.0/grid/evm/log/evmlogger.inf
oracle   29607     1  0 09:39 ?        00:00:00 /u01/app/11.2.0/grid/bin/oraagent.bin
oracle   30218     1  0 05:13 ?        00:00:05 /u01/app/oracle/product/11.2.0/db_1/bin/emagent
root     30552     1  0 11:12 pts/2    00:00:00 /bin/sh ./captureoraclelog.sh
root     30624 30552  0 11:12 pts/2    00:00:00 tail -f /tmp/OraInstall2015-06-11_11-12-37AM/installActions2015-06-11_11-12-37AM.log


  • Notice that in this list there are five iterations of tailing an OraInstall log.  
  • There are several terminal sessions for Linux users root and oracle. 
  • And finally there are several /u01/app/11.2.0/grid/bin processes.

A correct installation will have only one tail -f  command of the OraInstall log file;  it will have only one root or admin login (as installations can only be done by the Linux root or admin users); and finally, there will not be any /u01/app/11.2.0/grid/bin.../..   processes, since the Oracle instance has not yet successfully completed.
 
ResolutionIt is thought that these extraneous processes were a result of the failed installation(s) mentioned.

There are two possible resolutions to this situation, both resulting in these unnecessary processes being removed:
  • Reboot the physical hardware appliance and after logging in as root, confirm that none of these processes exist.  Repeat if necessary.  
  • Alternatively, if it's not 100% sure that the console can be accessed in the very unexpected event of the server not coming back online, an alternative to a reboot would be to individually terminate the extraneous processes, via the kill -9 command..  Care must be taking to only terminate those processes associated with the installation.

In the process list shown above, examples would be:

# kill -9 30624
# kill -9 29607

Attachments

    Outcomes