000030121 - How to quickly tell if an IMG installation is pointing to a local or remote database

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 Number000030121
Applies ToRSA Product Set: Identity Management and Governance
RSA Product/Service Type: Appliance and Software install
RSA Version/Condition: 6.9.1 (this applies to all versions)
Platform: Linux
O/S: RedHat, SuSE
 
Issue

A customer was doing an installation and unexpectedly saw 'tablespace missing' messages during the installation.
The customer was positive that the database existed and there should be no access problems.
Review of the /tmp/aveksa-install.log revealed no problems, other than these errors.    
The actual terminal session had been closed, so there was no way to determine the customer responses to the installation prompts, so a new session was initiated.  During this session,  it was noted that the cusotmer had select 'N' to 'is Oracle Remote',  when in fact, the database is remote and they should have input 'Y'.   
Once the correct pointers to the remote Oracle installation were entered, the installation completed without error.
 

ResolutionReview of the aveksa-install.log does clearly indicate if the database is local or remote, however, certain messages are only seen in the log, depending on where the database is located.
For example:
If the database is local, these messages wlll be seen:

--------------------------------------------------------------------------
Installing Oracle...

 

In addition, if the installation is on an appliance,  these messages will be seen:

--------------------------------------------------------------------------
Installing Oracle ASM drivers...
Red Hat EL 5 64-bit
warning: /tmp/asmlib/oracleasm-support-2.1.8-1.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Preparing...                ##################################################
oracleasm-support           ##################################################
warning: /tmp/asmlib/oracleasm-2.6.18-308.el5-2.0.5-1.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Preparing...                ##################################################
oracleasm-2.6.18-308.el5    ##################################################
warning: /tmp/asmlib/oracleasmlib-2.0.4-1.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Preparing...                ##################################################
oracleasmlib                ##################################################
Configuring the Oracle ASM library driver.
This will configure the on-boot properties of the Oracle ASM library
driver.  The following questions will determine whether the driver is
loaded on boot and what permissions it will have.  The current values
will be shown in brackets ('[]').  Hitting <ENTER> without typing an
answer will keep that current value.  Ctrl-C will abort.
Default user to own the driver interface [oracle]: Default group to own the driver interface [dba]: Start Oracle ASM library driver
on boot (y/n) [y]: Scan for Oracle ASM disks on boot (y/n) [y]: Writing Oracle ASM library driver configuration: done
Initializing the Oracle ASMLib driver: [  OK  ]
Scanning the system for Oracle ASMLib disks: [  OK  ]

 

However, if the database is remote, these messages will be seen:
 

--------------------------------------------------------------------------
Installing Oracle Client...

 

This is because when the database is remote,  only the Oracle client is installed locally.
NotesIt's still useful to capture the user command line session output, when possible,  to validate the installation type.

Attachments

    Outcomes