![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||
Solution Type Problem Resolution Sure Solution 2050123.1 : Exalytics: Re-install of OVM Manager 3.2.8 On Standalone Linux Machine Fails While Starting WLS or When Installing OVM Repository Schema
In this Document
Created from <SR 3-11246431731> Applies to:Exalytics In-Memory Machine X2-4 - Version All Versions and laterLinux OS - Version Oracle Linux 5.5 and later Oracle Exalytics Software - Version 1.0.0.5.0 and later Information in this document applies to any platform. SymptomsUninstalled Oracle Virtual Machine Manager (OVMM) 3.2.8 from existing Red Hat Linux 6 2.6.32-504.12.2.el6.x86_6 OVM server using the installer option. Left original Oracle Database OVM repository intact with intent of reinstalling OVMM using the same uuid. The OVMM database is an Oracle database and it only contains this one OVMM repository. 08-18 21:52 system.process DEBUG system.process.run stderr:
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is: java.net.ConnectException: Connection refused; No available router to destination] at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40) at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:788) at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:366) at weblogic.jndi.Environment.getContext(Environment.java:315) at weblogic.jndi.Environment.getContext(Environment.java:285)
Rechecked machine and ports and then re-attempted. This time the OVMM installer fails on Step 3 and the ovm-manager-3-install-2015-08-24-162053.log shows error: ... 08-24 16:22 ovm.installer.database ERROR Failed to add Oracle VM Manager schema to Oracle Database
CauseFound that a firewall was enabled and blocking port for WLS server which caused the first error. Disabled iptables and then found that the original OVM schema had not been dropped from the database when OVMM was originally de-installed. The OVMM will not allow you to install if the existing database contains an active schema with the same name (i.e. OVMMETA). Solution1. Turn off iptables: # service iptables stop
# service iptables save # setenforce 0 For additional information, see http://docs.oracle.com/cd/E35328_01/E35330/html/vmiug-manager-requirements.html#vmiug-manager-firewall References<NOTE:1351520.2> - Information Center: Certifications for Oracle VM Release 3.x for x86<NOTE:1351538.2> - Information Center: Oracle VM Release 3.x for x86 Attachments This solution has no attachment |
||||||||||||||||||
|