CA eHealth 6.3.2.05: Install / Update Tips & Tricks

Document created by Rich_V Employee on Jul 1, 2014Last modified by SamCreek on Dec 17, 2016
Version 3Show Document
  • View in full screen mode

CA eHealth 6.3.2.05: Install / Update Tips & Tricks

 

This article is written to help customers with an install or update of eHealth 6.3.2.05.  The content is based on our internal release testing of 6.3.2.05.

 

Q-1:  What are the main new features included with 6.3.205?

A-1: New features include:

0.      Support for RHEL 6.5

1.      Support for IE 10 and IE 11

2.      Apache Upgraded to 2.4.9

3.      OpenSSL Upgraded to 1.0.1g

4.      Java upgraded to 1.7.0_55

5.      April Oracle CPU

6.      137  new certifications delivered

 

Q-2:  Where is the sizing wizard link a customer can use for 6.3.2.0X?

A-2:  The latest sizing wizard for eHealth 6.3 is available on support.ca.com, search for sizing ehealth. Alternatively, you can get it here:

ftp://ftp.ca.com/pub/ehealthkits/ehealth_maint/63004/InstallSWIZ.exe

 

Q-3:  Do I need to create a new $NH_HOME (the location where the eHealth is installed) for 6.3.2.05 and NH_ORACLE_HOME for 11g when upgrading from 6.3.1.06 to 6.3.2.05?

A-3: The install program can recognize $NH_HOME for 6.3.1.06 during an upgrade from 6.3.1.06 to 6.3.2.05, thus a new $NH_HOME will not be created. However, a new Oracle 11G home will be created during the upgrade, under the existing $NH_ORACLE_HOME.

 

Q-4:  How to deal with a popup error of ‘An error occurred while ejecting 'DVD' Drive’ during ehealth upgrade?

A-4:  You may see above error when prompted for the Oracle location, you can ignore the error, just click the OK button to continue.

 

      * this question has been updated on 7.10.14*

Q-5:  What are the steps for updating ehealth 6.3.1.06 running on Linux 5.8 to ehealth 6.3.2.05 running on Linux 6.5?

 

You can follow the steps below for the update. Please note that that RHEL does NOT support in-place upgrade from RHEL 5.8 to RHEL 6.5.

  1. 1.      Update ehealth to 6.3.1.05 on Linux 5.8 if it is below 6.3.1.05
  2. 2.      Complete an in place update from ehealth 6.3.1.06 to 6.3.2.05 on Linux 5.8
  3. 3.   Stay on Linux 5.8, then do the following steps until you have to move to Linux 6.5
  4. 4.      Do an ascii database save  for 6.3.2.05 on Linux 5.8
  5. 5.      Remove ehealth and Oracle from Linux 5.8
  6. 6.      Upgrade Linux from 5.8 to 6.5
  7. 7.      Complete a fresh 6.3.2.05 installation on Linux 6.5
  8. 8.      Load the ascii database save (from step 3 above) to the freshly installed 6.3.2.05

 

Other alternatives are to do ASCII  save the DB at 6.3.1.06 on Linux 5.8 and then load the save into a new 6.3.2 system on Linux 6.5

 

Q-6:  Is activation required when updating ehealth 6.3.1.06 cluster to 6.3.2.05?

A-6:  There is no activation required when updating an ehealth 6.3.1.06 cluster to 6.3.2.05 because there is no new $NH_HOME generated during the upgrade. We will treat the cluster update as updating the cluster members one by one. We recommend updating the front-end system first before updating the back-end systems. Please be aware that a rollback from 6.3.2.05 to 6.3.1.06 is unavailable.

 

Q-7:  When was support for Linux 6.5 introduced?

A-7:  Support for RHEL 6.5 was introduced with eHealth 6.3.2.05

 

Q-8:  What do I need to do during the ehealth upgrade if I receive the error:

·         ‘The database must be converted before performing an update. Run nhUpgradeOracleDb as specified in the installation documentation’

 

A-8:  Ensure that you have placed the ehealth and Oracle kit on the local drive, ideally it should be placed in the same local drive/partition where $NH_HOME is located. Then make sure you can run sqlplus $NH_USER/$NH_USER @NH_DB_CONNECT_STRING on Linux and Solaris (sqlplus %NH_USER%/%NH_USER% @%NH_DB_CONNECT_STRING% on window).  Ensure running the command nhiCheckOracle –oracleMajorRev returns no error. If those do not resolve the issue, you can make following code change in INSTALL.NH for Solaris and Linux.

CHANGE FROM

            ${SU} ${NH_USER} -c ${f}

                        if [[ $? -ne 0 ]]

                        then

                                display "The database must be converted before performing an update. Run             nhUpgradeOracleDb as specified in the installation documentation."

                           exitInstall

 

TO

            ${SU} ${NH_USER} -c ${f}

                        if [[ $? -ne 0 ]]

                        then

                                display "The database must be converted before performing an update. Run             nhUpgradeOracleDb as specified in the installation documentation."

                           Return 0

 

Q-9:  How long should it take to complete a fresh 6.3.2.05 installation?

A-9:  It can take up to eight hours, we noticed from our testing that it may take about three hours for installing the Oracle base and one hour to install the Oracle update. The Oracle installation is where most of time will be spent.

 

Q-10:  What may cause an 6.3.2.05 installation failure on Linux 6.5 with the error of:

·         ‘a shared lib is missing’?

A-10:  When installing eHealth 6.3.2.05 on RHEL 6.5 system without the "gcc" library installed, the nhCheckInstallPreReqs script does not provide a warning about the GCC library being missing and the install fails with the error listed above. The solution is to install the GCC library, followed by re-installing eHealth. This is called out in the readme:

          Make sure that 32 bit glibc-2.12-1.107.el6.i686 is installed on the RHEL 6.5 system before starting installation. In absence of this library the install package will not open.

 

Q-11:  What are the download and installation procedures for a fresh 6.3.2.05 installation on Windows 2008, Linux 6.5 and Solaris 10?

A-11:  go to https://support.ca.com/irj/portal/SolutionCDNResults

Clicks Download Center on the left

Then click published solution

Select product CA eHealth E2E Console - MULTI-PLATFORM

Select 6.32 as a release, then click “Go” at the bottom; download the following  media depending on your OS types.  Go to next page if you don’t see the items.

Download the following for a fresh 6.3.2.05 installation on Windows 2008

            CA EHEALTH 6.3.2.05 MAINTENANCE RELEASE   - Fix #RO71153 

            CA EHEALTH 6.3.2 ORACLE 11.2.0.3 BASE  - Fix #RO63506 

            CA EHEALTH 6.3.2 ORACLE 11.2.0.03 UPDATE  - Fix #RO63481

Follow this procedure for a fresh 6.3.2.05 installation on Windows 2008

            1. Create a directory named 6.3.2.05_download and three subdirectories each named as            eh63205, OracleBase, and OracleUpdate on the disk where ehealth 6.3.2.05 will be             installed
            2. Copy CA EHEALTH 6.3.2.05 MAINTENANCE RELEASE into directory named eh63205,     then unzip it
            3. Copy CA EHEALTH 6.3.2 ORACLE 11.2.0.3 BASE into directory named OracleBase, then            unzip it
            4. Copy CA EHEALTH 6.3.2 ORACLE 11.2.0.03 UPDATE  into directory named         OracleUpdate, then unzip it
            5. Go to eh63205 on Window Explorer, and click ENU_632_WIN_0X_PLUS.exe to extract InstallPLus setup.exe
            6. Click  setup.exe created from step 5 to start the 6.3.2.05 fresh installation
            7. When prompted, enter the location of the OracleBase (full path for OracleBase directory)      and then the location of oracleUpdate (full path for OracleUpdate directory)
            8. Follow online interactive instruction to complete the fresh installation

 

Download the following for a fresh 6.3.2.05 installation on Linux 5.8 or Linux 6.5

            CA EHEALTH 6.3.2.05 MAINTENANCE RELEASE  -  Fix #RO71154

            CA EHEALTH 6.3.2 ORACLE 11.2.0.3 BASE - Fix #RO 63507 

            CA EHEALTH 6.3.2 ORACLE 11.2.0.03 UPDATE - Fix #RO63479 

Follow this procedure for a fresh 6.3.2.05 installation on Linux 5.8 or Linux 6.5

            1. Create a directory named 6.3.2.05_download and three subdirectories each named as            eh63205, OracleBase and OracleUpdate on the disk where ehealth 6.3.2.05 will be installed
            2. Copy CA EHEALTH 6.3.2.05 MAINTENANCE RELEASE into directory named eh63205,     then unzip it
            3. Copy CA EHEALTH 6.3.2 ORACLE 11.2.0.3 BASE into directory named OracleBase, then            unzip it
            4. Copy CA EHEALTH 6.3.2 ORACLE 11.2.0.03 UPDATE into directory named          OracleUpdate, then unzip it
            5. cd to eh63205, and run ENU_632_LIU_0X_PLUS.sh to extract INSTALL.NH
            6. Run INSTALL.NH created from step 5 to start 6.3.2.05 fresh installation
            7. When prompted, enter location of the OracleBase (full path for OracleBase directory)            and then location of oracleUpdate (full path for  OracleUpdate directory)
            8. Follow online interactive instruction to complete the fresh installation

 

Download the following for a fresh 6.3.2.05 installation on Solaris 10

            CA EHEALTH 6.3.2.05 MAINTENANCE RELEASE - Fix #RO71151 

            CA EHEALTH 6.3.2 ORACLE 11.2.0.3 BASE - Fix #RO63505 

            CA EHEALTH 6.3.2 ORACLE 11.2.0.03 UPDATE - Fix #RO63480 

Follow this procedure below to do a fresh 6.3.2.05 installation on Solaris 10, please note that the procedure is the same as the one used for Linux.

            1. Create a directory named 6.3.2.05_download and three subdirectories each named as            eh63205, OracleBase and OracleUpdate on the disk where ehealth 6.3.2.05 will be installed
            2. Copy CA EHEALTH 6.3.2.05 MAINTENANCE RELEASE into directory named eh63205,     then unzip it
            3. Copy CA EHEALTH 6.3.2 ORACLE 11.2.0.3 BASE into directory named OracleBase, then            unzip it
            4. Copy CA EHEALTH 6.3.2 ORACLE 11.2.0.03 UPDATE  into directory named         OracleUpdate, then unzip it
            5. cd to eh63205, and run ENU_632_SOL_0X_PLUS.sh to extract INSTALL.NH
            6. Run INSTALL.NH created from step 5 to start 6.3.2.05 fresh installation
            7. When prompted, enter location of the OracleBase (full path for OracleBase directory)            and then location of oracleUpdate (full path for  OracleUpdate directory)
            8. Follow online interactive instruction to complete the fresh installation

 

Q-12:  What is the download and update procedure for updating from ehealth 6.3.1.06 to 6.3.2.05 on Windows 2008, Linux and Solaris 10

A-12:  Updating from6.3.1.06 to 6.3.2.05 requires the same ehealth and oracle kits, and uses the same procedure as 6.3.2.05 fresh installation, therefore, you can follow Q-10/A-10 described above for doing the update.  Only difference is that during a fresh installation you will be prompted for entering CA eHealth home directory, whereas during the update the installation program recognizes the prior installation of 6.3.1.06 on your system and uses it as the ehealth 6.3.2.05 home, thus it does not prompt you for eHealth home directory.

 

Q-13:  What is the general update path for upgrade from ehealth 6.2.X, through 6.3.0.0X to 6.3.2.0X?

A-13:  You can only do an in place update to release 6.3.2.0X  from a CA eHealth installation that is at release 6.3.1.06 or higher.  Any update from ehealth 6.3.1.05 or lower to 6.3.2.0X requires that you either upgrade in place to ehealth 6.3.1.06 first, or do a two machine migration from ehealth 6.3.1.05 or lower to 6.3.2.0X.

 

Q-14:  What is the two-machine migration procedure?

A-14:  Two machine update consists of three steps:

            1. Install ehealth on the target machine

            2. Do an ascii database save on the source machine

            3. Transfer the ascii database from source to target machine and load it into the newly   installed ehealth.

 

Q-15 When installing on Linux rh 6.5, the nhCheckInstallPreReqs complains that I am missing uudecode. Where can I get this?

A-15 the uudecode utility is part of the sharutils rpm. It has always been required by ehealth. In rh 6.5, sharutils is not shipped on the default install media. You will need to logon to rh and download it using yum. Or contact your Linux admin for assistance.

 

Q-16 does ehealth support SNMP v3?

A-16 Yes, ehealth does support discovery and polling of v3 elements. You need to use a third party product called Distributed SNMP security Pack.

As of 6.3.2.05, For CA eHealth to poll devices by using the SNMPv3 protocol, you must use the DSSP 17.2 product from SNMP Research International, Inc.

If you are using v3 polling, the number of managed elements is greatly reduced, please see the admin guide and readme.

You must override the default start-up parameters of DSSP:

■      Default values: -unm -subagent -wbufnum 4096

■      Modified values: -unm -subagent -wbufnum 4096 -sndsocksize 32768 -rcvsocksize 174760

These are command line arguments, see the DSSP quick start guide.

 

Q-17 Have there been any changes to the time zone problems caused by eHealth needing the EST time zone?

A-17 yes, there have been changes to the way eHealth handles time zones:

Updates to Time Zones

Many changes were made to the CA eHealth time zone support in this release. In general, the changes included:

■      Modifications to internal time zone mapping files.

Aliases were added to support more local country mappings.

Time zones with the wrong operating system mapping that caused incorrect mapping to DST and non-DST time zones were fixed.

Missing time zone definitions for either a DST or a non-DST instance were added. In particular Brasilia, Brazil/east was added to support GMT-3 with DST support.

Other changes are brought on by countries or regions changing their DST rules over time. For example, most of Russia changed their DST rules, and cities such as Moscow no longer use DST.

■      Updates to 3rd party libraries used in time zone support code. CA eHealth now follows the Olson time zone database. This means that time zone and DST support changes can be more quickly rolled out to the customer base.

■      Oracle 11g has built in support for Africa/Harare time zone (once it has been enabled).

■      A number of other time zone related bugs were fixed, especially in the reporting and user interface areas (both OCE and Web UI).

These changes can highlight other time-related problems on your systems. For example, setting the wrong time zone or setting the wrong DST setting, due to either an error or due to implementing your own fixes to the CA eHealth time zone files. In either case, you may notice different behavior once these time zone changes are installed with this release. Even with the updated time zone support, you can still have issues that require you to modify your time zone settings

 

Q-18 can I use EEM as a single sign-on solution in eHealth?

A-18 EEM is only configured out-of-the-box for sso between Spectrum and ehealth when launching reports in context.

Any other configuration of EEM and eHealth as an sso option requires a CA services engagement.

 

Q-19 have there been any changes to the Spectrum integration in 6.3.2.05?

A-19 yes, as of 6.3.2.05, CA Spectrum r8.x or r9.0.x is not supported with the present version of CA eHealth.

 

 

**************************************************************************

Attachments

    Outcomes