Showing results for 
Search instead for 
Did you mean: 

IMC Standard 5.2/5.1 Fail to Install on RHEL6.1

Go to solution
Occasional Advisor

IMC Standard 5.2/5.1 Fail to Install on RHEL6.1

I'm trying to install IMC Standard on Red Hat EL 6.1 x64 as the Oracle 11 R2 Linux x64 is the only database that we could use in this environment, but even after a double check on packages requirements (some was missing on RHEL6.1 initial setup and I installed through "yum groupinstall" or rpm -ivh) I still have the error below on "" or on "":


Althrough I'm using the "sys" user on database (I'm able to connect to database with "sqlplus sys/password@hp as sysdba)I got the error below (font in red) on of IMC 5.2 installation files or when I try to use the IMC 5.1 installation files I got a "Connecting to the database failed".


What should I correct or check to be able to install it ?




Felicio Santos.


My environment variables:



My tnsnames.ora:


# Generated by Oracle configuration tools.

HP =
      (ADDRESS = (PROTOCOL = TCP)(HOST = = 1521))
      (SERVICE_NAME = hp)


Attached are my rpm -qa result. stdout:


Some required packages were not found on your operating system. Please install them by following the instructions in the Red Hat Enterprise Linux Server 6.x Installation Guide.

Can not find instInfoFile - /etc/iMC-Reserved/instinfo.txt
Change LD_LIBRARY_PATH=./:/usr/lib/jvm/java-1.6.0-openjdk-
Execute 'conntest' failed Cannot run program "/tmp/1362775250851/common/lib/conntest_linux" (in directory "/tmp/1362775250851/common/lib"): error=2, No such file or directory
        at java.lang.ProcessBuilder.start(
        at java.lang.Runtime.exec(
        at com.h3c.imc.deploy.Util.executeCommand(
        at com.h3c.imc.deploy.dma.wizard.DatabaseSelectPanelDescriptor$DbConnectCheckingWorkingDialog.doConntest(
        at com.h3c.imc.deploy.dma.wizard.DatabaseSelectPanelDescriptor$DbConnectCheckingWorkingDialog.doWork(
        at com.h3c.imc.deploy.dma.wizard.DatabaseSelectPanelDescriptor$DbConnectCheckingWorkingDialog.doWork(
        at com.h3c.imc.deploy.wizard.WorkingDialog$ProgressWorker.doInBackground(
        at javax.swing.SwingWorker$
        at java.util.concurrent.FutureTask$Sync.innerRun(
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$
Caused by: error=2, No such file or directory
        at java.lang.UNIXProcess.<init>(
        at java.lang.ProcessImpl.start(
        at java.lang.ProcessBuilder.start(
        ... 13 more

Honored Contributor

Re: IMC Standard 5.2/5.1 Fail to Install on RHEL6.1

Looking at the install guide, these are the required packages:

  • glibc-2.12-1.25.el6.i686.rpm

  • libaio-0.3.107-10.el6.i686.rpm

  • libgcc-4.4.5-6.el6.i686.rpm

  • libstdc++-4.4.5-6.el6.i686.rpm 



Looking at your list of RPMs, you seem to have all of those, but you may need the 32-bit versions (i686) as well as the 64-bit version (x86_64). I'm not certain on this for IMC, as all of my IMC installs have been on Windows. However, I have run into a very similar problem with some other HP Software, where some 32-bit libraries were required, in addition to the 64-bit libraries. 


Actually, check out this thread here:


Peter's saying you do need the 32-bit versions of those libraries. Give that a go, hopefully it works!



Occasional Advisor

Re: IMC Standard 5.2/5.1 Fail to Install on RHEL6.1

That's right ! Just installed the 32bit version of libraries and the check passed as also the setup. Thanks for your assistance and quicker answer !

Esteemed Contributor

Re: IMC Standard 5.2/5.1 Fail to Install on RHEL6.1

Thanks for the pointer to the other thread, Lindsay. That was exactly the issue for me in an install of IMC 7.0. What's the bet if I remove the 32-bit libraries after the installation is done, things will still work perfectly? ;-)
Honored Contributor

Re: IMC Standard 5.2/5.1 Fail to Install on RHEL6.1

Yeah, wouldn't surprise me. Maybe I should investigate further using lsof on a CentOS IMC server I've got running these days? I've seen some other apps where either it was just a leftover requirement in the installer, or the 32-bit libraries were only used by the installer, and not the actual app.