000030121 - How to tell if the Oracle database on an appliance is Local or Remote in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support on Apr 19, 2020
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000030121
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle 
RSA Product/Service Type: Appliance 
RSA Version/Condition: All
 
IssueHow to tell if the Oracle database on an appliance is installed locally or remotely in RSA Identity Governance & Lifecycle
 
ResolutionThere are multiple ways to determine if the RSA Identity Governance & Lifecycle Oracle database appliance installation is local or remote. Below are some examples.
  • If there is an installation failure, use the /tmp/aveksa-install.log

Look for:


 


Use a remote Oracle server installation [N]? N
Use a remote Oracle server installation [N]? Y


 


or look for:


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

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

 


Installing Oracle Client indicates a remote database installation.

 

  • On a running system (successfully installed):

Look in the aveksaServerInfo.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServerInfo.log) for:


 


Database: DB_LOCAL
Database: DB_REMOTE


 


Look in the $AVEKSA_HOME/Aveksa_System.cfg file for:


 


REMOTE_ORACLE=N
REMOTE_ORACLE=Y


 

Attachments

    Outcomes