Upgrade to RSA Identity Governance & Lifecycle 7.0.2 fails with message "Error occurred when determining the version of the remote Oracle server"
2 years ago
Originally Published: 2018-01-30
Article Number
000041402
Applies To
RSA Product Set: Identity Governance & Lifecycle
RSA Product/Service Type: Enterprise Software
RSA Version/Condition: 7.0.2
 
Issue
  • During the upgrade process, the script errors out with the following message:
Error occurred when determining the version of the remote Oracle server. Please bring Oracle online and restart installation.
  • The environment utilizes a remote database and it is currently on 12c
Starting installation of RSA Identity Governance and Lifecycle 
Installation started on Mon Jan 22 10:20:27 EST 2018 
Install Options: 
-------------------------------------------------------------------------- 

Existing 6.x install detected 
The cacerts keystore is backed up into /home/oracle/backupcacerts folder. Prior to upgrade if you have any certificates imported, you will have to re-import them from the backup keystore. 
install configuration setup complete. Mon Jan 22 10:20:39 EST 2018 

Starting installation of RSA Identity Governance and Lifecycle version=7.0.2 build=126845 

[Mon Jan 22 10:20:40 EST 2018] Performing pre-requisite checks 
osType : RHEL5 
Running test : checkEtcHosts 
Test passed 
Running test : checkFqdnHasDomainFormat 
Test passed 
Running test : checkMinDiskSizes 
Test passed 
Skip test : checkEntitlementPrereqs passwd oracle 500 
Running test : checkEntitlementMatchingId passwd oracle 500 1 
Test passed 
Skip test : checkEntitlementPrereqs group oinstall 500 
Skip test : checkEntitlementPrereqs group dba 501 
Running test : checkEtcSecurityLimits oracle hard nofile 65536 
Test passed 
Running test : checkEtcSecurityLimits oracle soft nofile 1024 
Test passed 
Running test : checkEtcSecurityLimits oracle hard nproc 16384 
Test passed 
Running test : checkEtcSecurityLimits oracle soft nproc 2047 
Test passed 
Running test : checkEntitlementMatchingId passwd root 0 1 
Test passed 
Running test : checkNtp 
Test passed 
Running test : checkUserNotInGroup oracle root 
Test passed 
Running test : checkUMASK 0022 
Test passed 
Running test : checkDNSResolution 
Test passed 
Running test : checkShmMount 
Test passed 
Running test : checkBootMount 
Test passed 
Running test : checkAFXPermissions oracle /home/oracle/AFX 
Test passed 
Pass ... requirements defined by Inspect System 
[Mon Jan 22 10:20:41 EST 2018] Pre-requisite checks completed 

-------------------------------------------------------------------------- 
Uninstalling previous version JDK 1.6.0... 
No JDK 1.6.0 packages found 
No needs to cleanup java directory 

-------------------------------------------------------------------------- 
Installing JDK 1.7.0... 
Preparing packages for installation... 
tzdata-java-2014b-1.el5 
jpackage-utils-1.7.3-1jpp.3.el5 
tzdata-2015a-1.el5 
Installing JDK completed 

-------------------------------------------------------------------------- 
[Mon Jan 22 10:22:32 EST 2018] Checking environment... 
Install Summary 
System Information: Linux vm-dev-aveksa-app01 2.6.18-419.el5 #1 SMP Wed Feb 22 22:40:57 EST 2017 x86_64 x86_64 x86_64 GNU/Linux 
OS Version 
IS64BIT Y 
AVEKSA_OWNER oracle 
AVEKSA_OWNER_ID 500 
AVEKSA_ADMIN admin 
AVEKSA_ADMIN_ID 501 
AVEKSA_GROUP oinstall 
AVEKSA_GROUP_ID 500 
AVEKSA_ADMIN_GROUP oinstall 
AVEKSA_ADMIN_GROUP_ID 500 
DBA_GROUP dba 
DBA_GROUP_ID 501 
DATA_DIR_GROUP datadir 
DATA_DIR_GROUP_ID 502 
AVEKSA_HOME /home/oracle 
USR_BIN /usr/bin 
ORACLE_HOME 
JAVA_HOME /etc/alternatives/java_sdk_1.7.0 
AVEKSA_WILDFLY_HOME /home/oracle/wildfly 
ASM_SID +ASM 
USE_ASM 
ORACLE_SID avop1 
ORACLE_SERVICE_NAME avop1 
ORACLE_CONNECTION_ID avop1 
AVEKSA_ORACLE_DB_USER AVUSER 
STAGING_DIR /tmp/aveksa/staging 
PACKAGES_DIR /tmp/aveksa/packages 
ASMLIB_BASENAME asmlib-008 
ASMLIB_PACKAGE asmlib-008_x64.tar.bz2 
ORACLE_BASENAME Oracle.12.1.0.2.0 
ORACLE_PACKAGE1 linuxamd64_12102_database_1of2.zip 
ORACLE_PACKAGE2 linuxamd64_12102_database_2of2.zip 
ORACLE_PACKAGE3 linuxamd64_12102_grid_1of2.zip 
ORACLE_PACKAGE4 linuxamd64_12102_grid_2of2.zip 
AVEKSA_USER avuser 
AVEKSA_REPORTS_USER avdwuser 
AVEKSA_PUBLIC_DB_USER ACMDB 
AVEKSA_AVPERF_USER perfstat 
JAVA_BASENAME openjdk17 
JAVA_PACKAGE openjdk17_v002.tar.bz2 
WILDFLY_BASENAME wildfly-8.2.0.Final 
WILDFLY_PACKAGE wildfly-8.2.0.Final.tar 
AGENT_HOME /home/oracle/AveksaAgent 
DEPLOY_DIR /tmp/aveksa/staging/deploy 
APPLIANCE N 
AS_AVEKSA_OWNER su - oracle -c 
FRESH_INSTALL N 
NEW_IMG_VER 7.0.2 
NEW_IMG_BLD 126845 
[Mon Jan 22 10:22:33 EST 2018] Checking environment completed 
You will need to import a backup after completion of this install to restore your environment. 
Before proceeding, please verify that you have a current backup off of this system. 
See the Upgrade and Migration guide for details on how to generate a database backup. 

Type 'BACKUP-OFFSITE-VERIFIED' to verify backup of the database exists off of this system 
before upgrading the software [ ]? 
Response was : BACKUP-OFFSITE-VERIFIED 

-------------------------------------------------------------------------- 
Checking for supported database version... 

Error occurred when determining the version of the remote Oracle server. 
Please bring Oracle online and restart installation. 

Exit installation.


 
Cause
This is a file permission issue.  The staging directory (/tmp/aveksa/staging) files and subdirectories inside staging are owned by the wrong user and group.  They need to be owned by oracle:oinstall, as shown:
[root@acm-staging]# ls -l
total 1127788
-rw-r--r--.  1 oracle oinstall 277776629 Sep  7  2016 AFXServer.zip
drwxr-xr-x.  9 oracle oinstall      4096 Sep  7  2016 AveksaAgent
-rw-r--r--.  1 oracle oinstall 802355842 Sep  7  2016 aveksa.ear
-rw-r--r--.  1 oracle oinstall  74688183 Sep  7  2016 aveksaWFArchitect.ear
-rw-r--r--.  1 oracle oinstall        13 Sep  7  2016 changesetinfo.txt
drwxr-xr-x. 19 oracle oinstall      4096 Mar  3  2017 database
drwxr-xr-x. 14 oracle oinstall      4096 Mar  3  2017 deploy
-rwxr-xr--.  1 oracle oinstall        50 Sep  7  2016 install.sh
-rw-r--r--.  1 oracle oinstall        13 Sep  7  2016 version.txt
Resolution
To fix the issue,
  1. Log in to the host as root.
  2. Navigate to the /tmp/aveksa directory:
cd tmp/aveksa
  1. Execute command below to remove staging/:
rm -rf staging/
  1. Make sure the staging directory was removed from /tmp/aveksa:
[root@acm-aveksa]# ls -l 
total 220 
-rw-r--r--. 1 root root 219755 Mar  3  2017 oracle.log 
drwxr-xr-x. 4 root root   4096 Mar  3  2017 packages
  1. Create the new staging directory as shown below.  First make sure you are inside /tmp/eveksa:
[root@acm-aveksa]# pwd
/tmp/aveksa
  1. Create the staging directory:
mkdir staging
  1. Confirm that the directory is owned by root:root:
[root@acm-aveksa]# ls -l

drwxr-xr-x. 4 root root   4096 Mar  3  2017 packages
drwxr-xr-x. 2 root root   4096 Feb  8 10:40 staging
  1. Expand the Aveksa package/tar to the new staging directory:
cd /tmp/aveksa/staging
tar -jxvf /tmp/aveksa/packages/aveksa-<product-version>.tar.bz2
  1. Verify the file permissions. Make sure the extracted files and subdirectories inside /tmp/aveksa/staging now have the user and group owners of oracle:oninstall:
[root@acm-staging]# ls -l
total 1127788
-rw-r--r--.  1 oracle oinstall 277776629 Sep  7  2016 AFXServer.zip
drwxr-xr-x.  9 oracle oinstall      4096 Sep  7  2016 AveksaAgent
-rw-r--r--.  1 oracle oinstall 802355842 Sep  7  2016 aveksa.ear
-rw-r--r--.  1 oracle oinstall  74688183 Sep  7  2016 aveksaWFArchitect.ear
-rw-r--r--.  1 oracle oinstall        13 Sep  7  2016 changesetinfo.txt
drwxr-xr-x. 19 oracle oinstall      4096 Mar  3  2017 database
drwxr-xr-x. 14 oracle oinstall      4096 Mar  3  2017 deploy
-rwxr-xr--.  1 oracle oinstall        50 Sep  7  2016 install.sh
-rw-r--r--.  1 oracle oinstall        13 Sep  7  2016 version.txt
  1. Perform the installation.
Notes
The initial cause of the file permissions change was a UID/GID issue. 

The required UIDs and GIDs are listed below:

oracle         500
admin         501
oinstall        500
dba             501
datadir        502

Verify that the required IDs for the users and groups listed above are set correctly before initiating installation script.