Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2050123.1
Update Date:2015-09-01
Keywords:

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  


Related Items
  • Linux OS
  •  
  • Oracle Exalytics Software
  •  
  • Exalytics In-Memory Machine X2-4
  •  
Related Categories
  • PLA-Support>Eng Systems>Exalytics>Oracle Exalytics>DB: Exalytics_EST
  •  




In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-11246431731>

Applies to:

Exalytics In-Memory Machine X2-4 - Version All Versions and later
Linux 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.

Symptoms

Uninstalled 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.

While completing installation steps as described in  http://docs.oracle.com/cd/E35328_01/E35330/html/vmiug-manager-install.html

1. Select "custom" install type and use existing OVM repository (on existing Oracle DB).
2. Provide database host servername, SID and listener (step 1).
3. Automatically installs java and then prompts for schema name for OVS repository (entered ovmmeta/ ****** (password).
4. Step 4 prompts for "weblogic" username and password - default is auto selected, left as is and entered password.
Install proceeded automatically through next steps and then failed with error on Step 7, creating weblogic domain.

The ovm-manager-3-install-2015-08-18-213707.log shows errors:

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
           0 rows affected

           ORA-01920: user name 'OVMMETA' conflicts with another user or role name    <<<<<<<<<<<<<<
[...]

 

Cause

Found 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).
 

Solution

1. 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

2. Check to make sure that the original OVM manager install was completely uninstalled from the Linux server. Also work with DBA to drop the OVM repository schema (OVMMETA) in the existing Oracle database (i.e. "drop user cascade" command).

NOTE: If the schema is not dropped, you must use a new schema name when you do the reinstall. Otherwise, the install will fail with an error like: ...ORA-01920: user name 'OVM_Schema_name' conflicts with another user or role name.

3. After completing above steps, reinstall of OVM manager will succeed.
 

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
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback