Unassign Server from a Corrupted Oracle VM Manage 3.1.1 instance
My problem is that the Oracle Database holding the metadata of the VM Manager that currently owns my VM Server died completely and I'm unable to log in to the VM Manager to manage the VMs living in the Server.
I have no (explicit) backup from the Manager Database so I'm unable to recreate the schema to bring the Manager up again.
I have an alternate Manager instance in a different server but cannot tke the ownership of the Server because is already owned by another VM Manager (the corrupted one). The error shown is OVMRU_000009E Server <my OVM server> is already owned by an Oracle VM Manager.
What is the best option to unassign the VM Server from the old VM Manager?
These are my options so far, haven't tried them yet, though:
1) As per the an alternate thread (https://forums.oracle.com/forums/thread.jspa?messageID=10633203#10633203)
# service ovs-agent stop
# rm /etc/ovs-agent/db/server
# service ovs-agent start
2) Uninstall the corrupted VM Manager using the runInslatter.sh script from the Manager installation media.
I appreciate your help a lot!
I had to improvise a little bit before you answer came so I went ahead and reinstalled the Manager without taking note of the current UUID, the new Manager installation was installed using the same old UUID, though.
My next issue was that the new Manager was not able to recognize the existen Physical Repository, this might be due the SATA Disk was not empty (of course, it was holding all my VMs). I couldn't find a way for the new Manager to mount and recognize the existen Repo so I went ahead and backed the Repository Up to an alternate partition so was able to clean the disk.
After the backup, I wiped the SATA disk out using the command:
+# dd if=/dev/zero of=/dev/sda bs=1M+
But my surprise was that the Manager, under Storage > Local Storage, was still showing the SATA disk as used, as if the content was still there, so I couldn't create a new Repository on it. Not sure how the mapper/ocfs2/SATA stuff combines to provide Physical devices for the VM Server.. I'm going to have to learn more about these stuff.
Current Status, I decided to re-install the whole VM Server and the VM Manager (in the same box) and hopefully the new manager will recognize the SATA Disk as empty and will be able to create a new Repository on it, then I'll copy the VMs from the Backup and "hopefully" the VMs will be displayed.
Am I walking the right way?
Similar Messages
-
How to Migrate VM Server pool to Other Oracle VM Manager
Hi,
I want to move oracle server pool from One Oracle VM Manager to other VM manager.
Can any one help me on how to migrate vm server pool to other VM Manager.
Thanks & Regards
YJRHi,
unfortunately I don't know of an easy supported way.
The process itself is pretty similar to migrating serverpools to Enterprise Manager as described in this note:
Migrating from Oracle VM Manager to Enterprise Manager Grid Control (Doc ID 807091.1)
With the exception that you simply register the new pool in a new manager and then have to rediscover all VMs.
So overall it is a simple "delete serverpool" and "create serverpool" with additional import of virtual machines.
If during this steps a problem arise, you still can deconfigure everything and reregister with the new manager (with the help of cleanup.py).
Regards
Sebastian -
Upgrading SQL Server from 2008 to 2012 doesn't respect existing install / instance paths
Basic Information : Running Microsoft Windows Server 2008 with MS SQL Server 2008 (version 10.0.5869), trying to upgrade to SQL Server 2012. Currently working in a cloned
VM of our production server (so I can try things and not worry about affecting our production system).
Current server setup:
C Drive: Operating System (About 7 GB of 50 GB free)
J Drive: Program Files (About 65 GB of 78 GB free)
F Drive: SQL Databases (About 120 GB of 195 GB free)
Issue: I am trying to do an upgrade of our existing MS SQL Server 2008 install. I am using the GUI method, and choosing "Upgrade from SQL Server, 2005, SQL Server
2008, or SQL Server 2008 R2" in the Setup GUI:
All the checks & rules run with no issues. When I get to the "Instance Configuration" screen in the setup GUI, it is not respecting where my SQL Server instance is already installed (which is on the J drive). Instead it wants to install EVERYTHING
(including Instance Directory, which should be on the F drive, and the install folder, which should be on the J drive) on the C drive under C:\Program Files\ and there is no option in the GUI to change that, as it's grayed out.
I tried using a Configuration File to do the upgrade, but when I tried to specify the specific paths, it says those variables are not allowed to be used in an upgrade. If I allow the install to go through, it seems to install fine, but only leaves me with about
1.5 GB free on the OS drive (Drive C) and all of SQL Server is now installed on Drive C, which is not what I want or need.
Looking in the Registry Editor, I can see that under HKLM\SOFTWARE\Microsoft\Microsoft
SQL Server\MSQL11.MSSQLSERVER\ that the SqlProgramDir key
has changed from "F:\" to "C:\Program Files\Microsoft SQL Server\" and that the SQLPath and SQLDataRoot have
changed from "F:\MSSQL10.MSSQLSERVER\MSSQL" to "C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL". SQLBinRoot has
also been changed "F:\MSSQL10.MSSQLSERVER\MSSQL\Binn" to "C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn".
It doesn't seem to want to follow where the existing Install and Instance Directories are. Am I missing something here? I've done a decent amount of research, but can't find anything that talks about this. So I'm at a loss as to what to do from here.I haven't touched the registry. Here is the ConfigurationFile.ini from the original install (I've scrubbed sensitive info out of it) showing the paths:
;SQLSERVER2008 Configuration File
[SQLSERVER2008]
; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will reflect the instance ID of the SQL Server instance.
INSTANCEID="MSSQLSERVER"
; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.
ACTION="Install"
; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, and Tools. The SQL feature will install the database engine, replication, and full-text. The Tools feature will install Management Tools, Books online, Business Intelligence Development Studio, and other shared components.
FEATURES=SQLENGINE,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
; Displays the command line parameters usage
HELP="False"
; Specifies that the detailed Setup log should be piped to the console.
INDICATEPROGRESS="False"
; Setup will not display any user interface.
QUIET="False"
; Setup will display progress only without any user interaction.
QUIETSIMPLE="False"
; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system.
X86="False"
; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature.
ERRORREPORTING="False"
; Specify the root installation directory for native shared components.
INSTALLSHAREDDIR="J:\Program Files\Microsoft SQL Server"
; Specify the root installation directory for the WOW64 shared components.
INSTALLSHAREDWOWDIR="J:\Program Files (x86)\Microsoft SQL Server"
; Specify the installation directory.
INSTANCEDIR="F:"
; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature.
SQMREPORTING="False"
; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services (RS).
INSTANCENAME="MSSQLSERVER"
; Agent account name
AGTSVCACCOUNT="NT AUTHORITY\SYSTEM"
; Auto-start service after installation.
AGTSVCSTARTUPTYPE="Automatic"
; Startup type for Integration Services.
ISSVCSTARTUPTYPE="Automatic"
; Account for Integration Services: Domain\User or system account.
ISSVCACCOUNT="NT AUTHORITY\SYSTEM"
; The name of the account that the Analysis Services service runs under.
ASSVCACCOUNT="NT AUTHORITY\SYSTEM"
; Controls the service startup type setting after the service has been created.
ASSVCSTARTUPTYPE="Automatic"
; The collation to be used by Analysis Services.
ASCOLLATION="Latin1_General_CI_AS"
; The location for the Analysis Services data files.
ASDATADIR="F:\MSAS10.MSSQLSERVER\OLAP\Data"
; The location for the Analysis Services log files.
ASLOGDIR="F:\MSAS10.MSSQLSERVER\OLAP\Log"
; The location for the Analysis Services backup files.
ASBACKUPDIR="F:\MSAS10.MSSQLSERVER\OLAP\Backup"
; The location for the Analysis Services temporary files.
ASTEMPDIR="F:\MSAS10.MSSQLSERVER\OLAP\Temp"
; The location for the Analysis Services configuration files.
ASCONFIGDIR="F:\MSAS10.MSSQLSERVER\OLAP\Config"
; Specifies whether or not the MSOLAP provider is allowed to run in process.
ASPROVIDERMSOLAP="1"
; Specifies the list of administrator accounts that need to be provisioned.
ASSYSADMINACCOUNTS=""
; Startup type for the SQL Server service.
SQLSVCSTARTUPTYPE="Automatic"
; Level to enable FILESTREAM feature at (0, 1, 2 or 3).
FILESTREAMLEVEL="0"
; Set to "1" to enable RANU for SQL Server Express.
ENABLERANU="False"
; Specifies a Windows collation or an SQL collation to use for the Database Engine.
SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS"
; Account for SQL Server service: Domain\User or system account.
SQLSVCACCOUNT="NT AUTHORITY\SYSTEM"
; Windows account(s) to provision as SQL Server system administrators.
SQLSYSADMINACCOUNTS=""
; The default is Windows Authentication. Use "SQL" for Mixed Mode Authentication.
SECURITYMODE="SQL"
; Provision current user as a Database Engine system administrator for SQL Server 2008 Express.
ADDCURRENTUSERASSQLADMIN="False"
; Specify 0 to disable or 1 to enable the TCP/IP protocol.
TCPENABLED="1"
; Specify 0 to disable or 1 to enable the Named Pipes protocol.
NPENABLED="0"
; Startup type for Browser Service.
BROWSERSVCSTARTUPTYPE="Disabled"
; Specifies which account the report server NT service should execute under. When omitted or when the value is empty string, the default built-in account for the current operating system.
; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
; The domain part of RSSVCACCOUNT is a maximum of 254 characters long.
RSSVCACCOUNT="NT AUTHORITY\SYSTEM"
; Specifies how the startup mode of the report server NT service. When
; Manual - Service startup is manual mode (default).
; Automatic - Service startup is automatic mode.
; Disabled - Service is disabled
RSSVCSTARTUPTYPE="Automatic"
; Specifies which mode report server is installed in.
; Default value: “FilesOnly”
RSINSTALLMODE="DefaultNativeMode" -
Updating Oracle VM Manager from 3.1.1 to 3.2.1 where server is yum repo
I have a server running Oracle Enterprise Linux 6.3. Upon which is running Oracle VM Manager 3.1.1 ("BUILDID=3.1.1.305" from /u01/app/oracle/ovm-manager-3/.config).
This server is also my Oracle Enterprise Linux yum repo. This means its subscribed channels are (on ULN):
- Latest Unbreakable Enterprise Linux Kernel for Oracle Linux (x86_64)
- Oracle Linux 6 Add ons (x86_64)
- Oracle Linus 6 Latest (x86_64)
- Oracle VM 3 latest
- Oracle VM 3.2.1 Server Patches
Note that the last one was "Oracle VM 3.1.1 Server Patches" until this attempt to update. The "Yum Server" button is also ticked on ULN and I've followed the instructions on http://www.oracle.com/technetwork/articles/servers-storage-admin/yum-repo-setup-1659167.html.
Now, when I attempt a "yum update" on this server I get the following:
--> Finished Dependency Resolution
Error: Package: kernel-uek-2.6.39-300.28.1.el5uek.x86_64 (ovm3_3.2.1_x86_64_patch)
Requires: mkinitrd >= 5.1.19.6-71.0.10
Available: mkinitrd-5.1.19.6-61.100.1.el5_5.5.x86_64 (ovm3_x86_64_latest)
mkinitrd = 5.1.19.6-61.100.1.el5_5.5
Available: mkinitrd-5.1.19.6-61.100.1.el5_5.8.x86_64 (ovm3_x86_64_latest)
mkinitrd = 5.1.19.6-61.100.1.el5_5.8
Available: mkinitrd-5.1.19.6-61.100.1.el5_5.11.x86_64 (ovm3_x86_64_latest)
mkinitrd = 5.1.19.6-61.100.1.el5_5.11
Available: mkinitrd-5.1.19.6-71.100.1.el5_7.3.x86_64 (ovm3_x86_64_latest)
mkinitrd = 5.1.19.6-71.100.1.el5_7.3
Available: mkinitrd-5.1.19.6-71.100.1.el5_7.3.1.x86_64 (ovm3_x86_64_latest)
mkinitrd = 5.1.19.6-71.100.1.el5_7.3.1
Available: mkinitrd-5.1.19.6-71.100.1.el5_7.5.x86_64 (ovm3_x86_64_latest)
mkinitrd = 5.1.19.6-71.100.1.el5_7.5
Error: Package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64 (ol6_x86_64_latest)
Requires: libgnutls.so.26()(64bit)
Removing: gnutls-2.8.5-4.el6_2.2.x86_64 (@anaconda-OracleLinuxServer-201206261930.x86_64/6.3)
libgnutls.so.26()(64bit)
Obsoleted By: ovs-release-3.2-5.208.x86_64 (ovm3_x86_64_latest)
Not found
Available: gnutls-2.8.5-4.el6.x86_64 (ol6_x86_64_latest)
libgnutls.so.26()(64bit)
Available: gnutls-1.4.1-3.el5_3.5.x86_64 (ovm3_x86_64_latest)
Not found
Error: Package: system-config-network-tui-1.6.0.el6.2-1.0.3.el6.noarch (@anaconda-OracleLinuxServer-201206261930.x86_64/6.3)
Requires: dbus-python
Removing: dbus-python-0.83.0-6.1.el6.x86_64 (@anaconda-OracleLinuxServer-201206261930.x86_64/6.3)
dbus-python = 0.83.0-6.1.el6
Obsoleted By: ovs-release-3.2-5.208.x86_64 (ovm3_x86_64_latest)
Not found
Available: dbus-python-0.70-9.el5_4.x86_64 (ovm3_x86_64_latest)
dbus-python = 0.70-9.el5_4
Error: Package: python-urlgrabber-3.9.1-9.100.3.el5.noarch (ovm3_x86_64_latest)
Requires: python(abi) = 2.4
Installed: python-2.6.6-29.el6_3.3.x86_64 (@ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.4.3-27.100.1.el5_5.6.x86_64 (ovm3_x86_64_latest)
python(abi) = 2.4
Available: python-2.6.5-3.el6.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.6.5-3.el6_0.2.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.6.6-20.el6.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.6.6-29.el6.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.6.6-29.el6_2.2.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Error: Package: ovs-agent-3.2.1-183.x86_64 (ovm3_x86_64_latest)
Requires: python(abi) = 2.4
Installed: python-2.6.6-29.el6_3.3.x86_64 (@ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.4.3-27.100.1.el5_5.6.x86_64 (ovm3_x86_64_latest)
python(abi) = 2.4
Available: python-2.6.5-3.el6.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.6.5-3.el6_0.2.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.6.6-20.el6.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.6.6-29.el6.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.6.6-29.el6_2.2.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Error: Package: neon-0.29.3-2.el6.x86_64 (@anaconda-OracleLinuxServer-201206261930.x86_64/6.3)
Requires: libgnutls.so.26()(64bit)
Removing: gnutls-2.8.5-4.el6_2.2.x86_64 (@anaconda-OracleLinuxServer-201206261930.x86_64/6.3)
libgnutls.so.26()(64bit)
Obsoleted By: ovs-release-3.2-5.208.x86_64 (ovm3_x86_64_latest)
Not found
Available: gnutls-2.8.5-4.el6.x86_64 (ol6_x86_64_latest)
libgnutls.so.26()(64bit)
Available: gnutls-1.4.1-3.el5_3.5.x86_64 (ovm3_x86_64_latest)
Not found
Error: Package: rhn-client-tools-1.0.0-87.0.6.el6.noarch (ol6_x86_64_latest)
Requires: dbus-python
Removing: dbus-python-0.83.0-6.1.el6.x86_64 (@anaconda-OracleLinuxServer-201206261930.x86_64/6.3)
dbus-python = 0.83.0-6.1.el6
Obsoleted By: ovs-release-3.2-5.208.x86_64 (ovm3_x86_64_latest)
Not found
Available: dbus-python-0.70-9.el5_4.x86_64 (ovm3_x86_64_latest)
dbus-python = 0.70-9.el5_4
Error: Package: xen-tools-4.1.3-25.el5.3.x86_64 (ovm3_3.2.1_x86_64_patch)
Requires: python(abi) = 2.4
Installed: python-2.6.6-29.el6_3.3.x86_64 (@ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.4.3-27.100.1.el5_5.6.x86_64 (ovm3_x86_64_latest)
python(abi) = 2.4
Available: python-2.6.5-3.el6.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.6.5-3.el6_0.2.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.6.6-20.el6.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.6.6-29.el6.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.6.6-29.el6_2.2.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Error: Package: multiprocessing-2.6.1.1-1.x86_64 (ovm3_x86_64_latest)
Requires: python(abi) = 2.4
Installed: python-2.6.6-29.el6_3.3.x86_64 (@ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.4.3-27.100.1.el5_5.6.x86_64 (ovm3_x86_64_latest)
python(abi) = 2.4
Available: python-2.6.5-3.el6.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.6.5-3.el6_0.2.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.6.6-20.el6.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.6.6-29.el6.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Available: python-2.6.6-29.el6_2.2.i686 (ol6_x86_64_latest)
python(abi) = 2.6
Error: Package: neon-0.29.3-2.el6.x86_64 (@anaconda-OracleLinuxServer-201206261930.x86_64/6.3)
Requires: libgnutls.so.26(GNUTLS_1_4)(64bit)
Removing: gnutls-2.8.5-4.el6_2.2.x86_64 (@anaconda-OracleLinuxServer-201206261930.x86_64/6.3)
libgnutls.so.26(GNUTLS_1_4)(64bit)
Obsoleted By: ovs-release-3.2-5.208.x86_64 (ovm3_x86_64_latest)
Not found
Available: gnutls-2.8.5-4.el6.x86_64 (ol6_x86_64_latest)
libgnutls.so.26(GNUTLS_1_4)(64bit)
Available: gnutls-1.4.1-3.el5_3.5.x86_64 (ovm3_x86_64_latest)
Not found
Error: Package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64 (ol6_x86_64_latest)
Requires: libgnutls.so.26(GNUTLS_1_4)(64bit)
Removing: gnutls-2.8.5-4.el6_2.2.x86_64 (@anaconda-OracleLinuxServer-201206261930.x86_64/6.3)
libgnutls.so.26(GNUTLS_1_4)(64bit)
Obsoleted By: ovs-release-3.2-5.208.x86_64 (ovm3_x86_64_latest)
Not found
Available: gnutls-2.8.5-4.el6.x86_64 (ol6_x86_64_latest)
libgnutls.so.26(GNUTLS_1_4)(64bit)
Available: gnutls-1.4.1-3.el5_3.5.x86_64 (ovm3_x86_64_latest)
Not found
Error: Package: avahi-0.6.25-11.el6.x86_64 (@ol6_latest)
Requires: libdaemon.so.0()(64bit)
Removing: libdaemon-0.14-1.el6.x86_64 (@ol6_latest)
libdaemon.so.0()(64bit)
Obsoleted By: ovs-release-3.2-5.208.x86_64 (ovm3_x86_64_latest)
Not found
Available: libdaemon-0.10-5.el5.x86_64 (ovm3_x86_64_latest)
libdaemon.so.0()(64bit)
Error: Package: avahi-0.6.25-11.el6.x86_64 (@ol6_latest)
Requires: libdaemon >= 0.11
Removing: libdaemon-0.14-1.el6.x86_64 (@ol6_latest)
libdaemon = 0.14-1.el6
Obsoleted By: ovs-release-3.2-5.208.x86_64 (ovm3_x86_64_latest)
Not found
Available: libdaemon-0.10-5.el5.x86_64 (ovm3_x86_64_latest)
libdaemon = 0.10-5.el5
You could try using --skip-broken to work around the problem
You could try running: rpm -Va nofiles nodigest
Can someone please explain what mistakes I've made so I can get this box updated (both OS and Oracle VM Manager), please? Do I simply need to exclude some channels for the duration of the update of the local box, then add them back in for the repo mirroring to continue working?
With thanks,
BenIt appears that for the most part the package ovs-release is the problem. To judge from the first half of a failed yum update. Why isn't there an ovs-release package that references el6 packages? Really, did I make a mistake installing Oracle VM Manager on OL6 given that http://public-yum.oracle.com/repo/OracleVM/OVM3/latest/x86_64/ contains only "el5"-tagged packages?
Resolving Dependencies
--> Running transaction check
---> Package dbus-python.x86_64 0:0.83.0-6.1.el6 will be obsoleted
--> Processing Dependency: dbus-python for package: system-config-network-tui-1.6.0.el6.2-1.0.3.el6.noarch
--> Processing Dependency: dbus-python for package: rhn-client-tools-1.0.0-87.0.6.el6.noarch
---> Package gnutls.x86_64 0:2.8.5-4.el6_2.2 will be obsoleted
--> Processing Dependency: libgnutls.so.26()(64bit) for package: neon-0.29.3-2.el6.x86_64
--> Processing Dependency: libgnutls.so.26()(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
--> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: neon-0.29.3-2.el6.x86_64
--> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
---> Package kexec-tools.x86_64 0:2.0.3-3.0.1.el6 will be updated
---> Package kexec-tools.x86_64 0:2.0.3-4.0.7.*el5* will be an update
--> Processing Dependency: libxenctrl.so.4.0()(64bit) for package: kexec-tools-2.0.3-4.0.7.*el5*.x86_64
---> Package libdaemon.x86_64 0:0.14-1.el6 will be obsoleted
--> Processing Dependency: libdaemon.so.0()(64bit) for package: avahi-0.6.25-11.el6.x86_64
--> Processing Dependency: libdaemon >= 0.11 for package: avahi-0.6.25-11.el6.x86_64
Package libdaemon is obsoleted by ovs-release, but obsoleting package does not provide for requirements
---> Package ovs-release.x86_64 0:3.2-5.208 will be obsoleting
--> Processing Dependency: openvswitch for package: ovs-release-3.2-5.208.x86_64
--> Processing Dependency: kmod-openvswitch-uek for package: ovs-release-3.2-5.208.x86_64
--> Processing Dependency: net-snmp-utils for package: ovs-release-3.2-5.208.x86_64
--> Processing Dependency: lm_sensors for package: ovs-release-3.2-5.208.x86_64
--> Processing Dependency: ovs-agent for package: ovs-release-3.2-5.208.x86_64
---> Package smartmontools.x86_64 1:5.42-2.el6 will be updated
---> Package smartmontools.x86_64 1:5.42-2.100.2.*el5* will be an update
--> Running transaction check
---> Package dbus-python.x86_64 0:0.83.0-6.1.el6 will be obsoleted
--> Processing Dependency: dbus-python for package: system-config-network-tui-1.6.0.el6.2-1.0.3.el6.noarch
--> Processing Dependency: dbus-python for package: rhn-client-tools-1.0.0-87.0.6.el6.noarch
---> Package gnutls.x86_64 0:2.8.5-4.el6_2.2 will be obsoleted
--> Processing Dependency: libgnutls.so.26()(64bit) for package: neon-0.29.3-2.el6.x86_64
--> Processing Dependency: libgnutls.so.26()(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
--> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: neon-0.29.3-2.el6.x86_64
--> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
---> Package kmod-openvswitch-uek.x86_64 0:1.6.90-2 will be installed
--> Processing Dependency: kernel(memcpy) = 0x6067a146 for package: kmod-openvswitch-uek-1.6.90-2.x86_64
Package kernel-ovs is obsoleted by ovs-release, but obsoleting package does not provide for requirements
--> Processing Dependency: kernel(printk) = 0x985558a1 for package: kmod-openvswitch-uek-1.6.90-2.x86_64
---> Package libdaemon.x86_64 0:0.14-1.el6 will be obsoleted
--> Processing Dependency: libdaemon.so.0()(64bit) for package: avahi-0.6.25-11.el6.x86_64
--> Processing Dependency: libdaemon >= 0.11 for package: avahi-0.6.25-11.el6.x86_64
Package libdaemon is obsoleted by ovs-release, but obsoleting package does not provide for requirements
---> Package lm_sensors.x86_64 0:3.1.1-10.el6 will be installed
--> Processing Dependency: libsensors.so.4()(64bit) for package: lm_sensors-3.1.1-10.el6.x86_64
---> Package net-snmp-utils.x86_64 1:5.5-41.el6_3.1 will be installed
--> Processing Dependency: net-snmp-libs = 1:5.5-41.el6_3.1 for package: 1:net-snmp-utils-5.5-41.el6_3.1.x86_64
--> Processing Dependency: libnetsnmp.so.20()(64bit) for package: 1:net-snmp-utils-5.5-41.el6_3.1.x86_64
---> Package openvswitch.x86_64 0:1.6.90-7 will be installed
--> Processing Dependency: libcrypto.so.6()(64bit) for package: openvswitch-1.6.90-7.x86_64
--> Processing Dependency: libssl.so.6()(64bit) for package: openvswitch-1.6.90-7.x86_64
---> Package ovs-agent.x86_64 0:3.2.1-183 will be installed
--> Processing Dependency: python(abi) = 2.4 for package: ovs-agent-3.2.1-183.x86_64
--> Processing Dependency: multiprocessing >= 2.6.1.1 for package: ovs-agent-3.2.1-183.x86_64
--> Processing Dependency: python-simplejson >= 2.0.7 for package: ovs-agent-3.2.1-183.x86_64
---> Package xen-tools.x86_64 0:4.1.3-25.*el5.3* will be installed
--> Processing Dependency: python(abi) = 2.4 for package: xen-tools-4.1.3-25.*el5.3*.x86_64
--> Running transaction check
---> Package dbus-python.x86_64 0:0.83.0-6.1.el6 will be obsoleted
--> Processing Dependency: dbus-python for package: system-config-network-tui-1.6.0.el6.2-1.0.3.el6.noarch
--> Processing Dependency: dbus-python for package: rhn-client-tools-1.0.0-87.0.6.el6.noarch
---> Package gnutls.x86_64 0:2.8.5-4.el6_2.2 will be obsoleted
--> Processing Dependency: libgnutls.so.26()(64bit) for package: neon-0.29.3-2.el6.x86_64
--> Processing Dependency: libgnutls.so.26()(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
--> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: neon-0.29.3-2.el6.x86_64
--> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
---> Package kernel-uek.x86_64 0:2.6.39-300.28.1.*el5uek* will be installed
--> Processing Dependency: kernel-firmware = 2.6.39-300.28.1.*el5uek* for package: kernel-uek-2.6.39-300.28.1.*el5uek*.x86_64
--> Processing Dependency: device-mapper-multipath >= 0.4.9-23.0.1.*el5* for package: kernel-uek-2.6.39-300.28.1.*el5uek*.x86_64
--> Processing Dependency: mkinitrd >= 5.1.19.6-71.0.10 for package: kernel-uek-2.6.39-300.28.1.*el5uek*.x86_64
--> Processing Dependency: ql2xxx-firmware for package: kernel-uek-2.6.39-300.28.1.*el5uek*.x86_64
---> Package kmod-openvswitch-uek.x86_64 0:1.6.90-2 will be installed
---> Package libdaemon.x86_64 0:0.14-1.el6 will be obsoleted
--> Processing Dependency: libdaemon.so.0()(64bit) for package: avahi-0.6.25-11.el6.x86_64
--> Processing Dependency: libdaemon >= 0.11 for package: avahi-0.6.25-11.el6.x86_64
Package libdaemon is obsoleted by ovs-release, but obsoleting package does not provide for requirements
---> Package lm_sensors-libs.x86_64 0:3.1.1-10.el6 will be installed
---> Package multiprocessing.x86_64 0:2.6.1.1-1 will be installed
--> Processing Dependency: python(abi) = 2.4 for package: multiprocessing-2.6.1.1-1.x86_64
---> Package net-snmp-libs.x86_64 1:5.5-41.el6_3.1 will be installed
---> Package openssl098e.x86_64 0:0.9.8e-17.0.1.el6_2.2 will be installed
---> Package ovs-agent.x86_64 0:3.2.1-183 will be installed
--> Processing Dependency: python(abi) = 2.4 for package: ovs-agent-3.2.1-183.x86_64
---> Package python-simplejson.x86_64 0:2.0.9-3.1.el6 will be installed
---> Package xen-tools.x86_64 0:4.1.3-25.*el5.3* will be installed
--> Processing Dependency: python(abi) = 2.4 for package: xen-tools-4.1.3-25.*el5.3*.x86_64
--> Running transaction check
---> Package dbus-python.x86_64 0:0.83.0-6.1.el6 will be obsoleted
--> Processing Dependency: dbus-python for package: system-config-network-tui-1.6.0.el6.2-1.0.3.el6.noarch
--> Processing Dependency: dbus-python for package: rhn-client-tools-1.0.0-87.0.6.el6.noarch
---> Package device-mapper-multipath.x86_64 0:0.4.9-56.el6_3.1 will be installed
--> Processing Dependency: device-mapper-multipath-libs = 0.4.9-56.el6_3.1 for package: device-mapper-multipath-0.4.9-56.el6_3.1.x86_64
--> Processing Dependency: libmultipath.so()(64bit) for package: device-mapper-multipath-0.4.9-56.el6_3.1.x86_64
---> Package gnutls.x86_64 0:2.8.5-4.el6_2.2 will be obsoleted
--> Processing Dependency: libgnutls.so.26()(64bit) for package: neon-0.29.3-2.el6.x86_64
--> Processing Dependency: libgnutls.so.26()(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
--> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: neon-0.29.3-2.el6.x86_64
--> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
---> Package kernel-uek.x86_64 0:2.6.39-300.28.1.*el5uek* will be installed
--> Processing Dependency: mkinitrd >= 5.1.19.6-71.0.10 for package: kernel-uek-2.6.39-300.28.1.*el5uek*.x86_64
---> Package kernel-uek-firmware.noarch 0:2.6.39-300.28.1.*el5uek* will be installed
---> Package libdaemon.x86_64 0:0.14-1.el6 will be obsoleted
--> Processing Dependency: libdaemon.so.0()(64bit) for package: avahi-0.6.25-11.el6.x86_64
--> Processing Dependency: libdaemon >= 0.11 for package: avahi-0.6.25-11.el6.x86_64
Package libdaemon is obsoleted by ovs-release, but obsoleting package does not provide for requirements
---> Package multiprocessing.x86_64 0:2.6.1.1-1 will be installed
--> Processing Dependency: python(abi) = 2.4 for package: multiprocessing-2.6.1.1-1.x86_64
---> Package ovs-agent.x86_64 0:3.2.1-183 will be installed
--> Processing Dependency: python(abi) = 2.4 for package: ovs-agent-3.2.1-183.x86_64
---> Package ql2xxx-firmware.noarch 0:1.01.01-0.1.*el5* will be installed
---> Package xen-tools.x86_64 0:4.1.3-25.*el5.3* will be installed
--> Processing Dependency: python(abi) = 2.4 for package: xen-tools-4.1.3-25.*el5.3*.x86_64
--> Running transaction check
---> Package dbus-python.x86_64 0:0.83.0-6.1.el6 will be obsoleted
--> Processing Dependency: dbus-python for package: system-config-network-tui-1.6.0.el6.2-1.0.3.el6.noarch
--> Processing Dependency: dbus-python for package: rhn-client-tools-1.0.0-87.0.6.el6.noarch
---> Package device-mapper-multipath-libs.x86_64 0:0.4.9-56.el6_3.1 will be installed
---> Package gnutls.x86_64 0:2.8.5-4.el6_2.2 will be obsoleted
--> Processing Dependency: libgnutls.so.26()(64bit) for package: neon-0.29.3-2.el6.x86_64
--> Processing Dependency: libgnutls.so.26()(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
--> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: neon-0.29.3-2.el6.x86_64
--> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
---> Package kernel-uek.x86_64 0:2.6.39-300.28.1.*el5uek* will be installed
--> Processing Dependency: mkinitrd >= 5.1.19.6-71.0.10 for package: kernel-uek-2.6.39-300.28.1.*el5uek*.x86_64
---> Package libdaemon.x86_64 0:0.14-1.el6 will be obsoleted
--> Processing Dependency: libdaemon.so.0()(64bit) for package: avahi-0.6.25-11.el6.x86_64
--> Processing Dependency: libdaemon >= 0.11 for package: avahi-0.6.25-11.el6.x86_64
Package libdaemon is obsoleted by ovs-release, but obsoleting package does not provide for requirements
---> Package multiprocessing.x86_64 0:2.6.1.1-1 will be installed
--> Processing Dependency: python(abi) = 2.4 for package: multiprocessing-2.6.1.1-1.x86_64
---> Package ovs-agent.x86_64 0:3.2.1-183 will be installed
--> Processing Dependency: python(abi) = 2.4 for package: ovs-agent-3.2.1-183.x86_64
---> Package xen-tools.x86_64 0:4.1.3-25.*el5.3* will be installed
--> Processing Dependency: python(abi) = 2.4 for package: xen-tools-4.1.3-25.*el5.3*.x86_64
Edited by: user7586670 on 20-Feb-2013 06:20 -
Fresh install of Oracle VM Manager Template into Oracle VM Server
Hi,
I am trying to install the Oracle VM Manager template and then
create an Oracle VM Manager client.
I have already done a 'fresh install' of Oracle VM Server.
I do not have another machine available to use to contain the
'Oracle VM Manager', therefore, I am attempting to install the
Oracle VM Manager template directly into an Oracle VM Manager Server and
run the client.
I am following the instructions of the Oracle VM Server Users Guide
in section 4.3.
When I extract the zip file contents into the
/OVS/seed_pool directory, I get the following files.
Deploy_Manager_Template.sh
OVM_EL5U3_X86_OVM_MANAGER_PVM.tgz
So far, so good.
Next, I used 'tar' to help me extract the directories of the .tgz file.
So far, so good.
Next, as instructed, I used 'python' and 'print randomMAC()' to create a new MAC address.
Inside the /OVS/seed_pool/OVM_EL5U3_X86_OVM_MANAGER_PVM/vm.cfg file
I modified the vif MAC address. I replaced the
xx:xx:xx with the 'last three' that were generated by the python randomMAC
function from above.
vif = [ 'mac=00:16:3E:<my generated numbers>', ]
So far, so good?
In the Oracle VM Server Users Guide in section 4.3.,
The next step, expains that I should run
xm create mv.cfg
I did this. When I ran this I received back the error.
Using config file "./vm.cfg"
Error disk is not accessible.
When I peek inside my vm.cfg file.
I see file references starting with the following
file:/OVS/running_pool/ ...
Of, course my running_pool directory is empty.
(Again, this is a fresh install of Oracle VM Server).
My first question is the following.
Sometime in this process was I supposed to run
the the following executable?
./Deploy_Manager_Template.sh
If so, should I have done this early?
Was the modification of the vif (of adding the MAC address
into the vm.cfg file, something I 'should have not done'
or 'something that could be ignored' because the
'./Deploy_Manager_Template.sh' would have done this for me?
My second question is the following.
Would the following process be 'more correct?'
..1 Not modify the vm.cfg' file.
..2 run ./Deploy_Manager_Template.sh.
..3 In the /OVS/running_pool/ directory find my
vm.cfg file of interest, then modify the vif with a new MAC address.
..4 In /OVS/running_pool/Change my current location to my directory of interest
run xm create vm.cfg (to run my Oracle VM Manager)?
Any help or ideas whould be appreciated.
Thank you very much,
AIMHi,
This is the README file for Oracle VM Manager 2.2.0
Readme for Media Pack B57738-01
Print: Access key=P Close: Access key=C
Oracle VM Templates for Oracle VM Manager 2.2.0 Media Pack v1 for x86 (32 bit)
=====================================================================
Template Version 2.3
Oracle VM Manager Version 2.2.0
This document contains:
1. Prerequisites for Oracle VM Manager virtual machine (VM) deployment
2. Oracle VM Manager Template description
3. Creating an Oracle VM Manager Virtual Machine from
Oracle VM Manager Template
4. Deployment Interview
5. Known Issues
For more information on Oracle VM Manager, please refer to
the "Oracle VM Manager Installation Guide" and the "Oracle VM Manager
User's Guide" available at:
http://download.oracle.com/docs/cd/E15458_01/index.htm
1. Prerequisites
================
- A new install of Oracle VM Server 2.2 that has NOT been managed by another
Oracle VM Manager. Manager Template 2.2 is intended to be installed on Oracle
VM 2.2 server. If you have a new Oracle VM 2.1.5 server and want to deploy
Oracle VM Manager template, please use the Oracle VM 2.1.5 Manager template.
Note: root access to the server's dom0 is required.
- It's highly recommended that you upgrade the default agent (ovs-agent-2.3-19)
to ovs-agent-2.3-27 or later. You can get the latest Oracle VM 2.2 packages
from Oracle's Unbreakable Linux Network (http://linux.oracle.com).
Note: Alternate location to get Oracle VM agent 2.3-27 is
http://oss.oracle.com/oraclevm/server/2.2/RPMS/ovs-agent-2.3-27.noarch.rpm
- A working directory of the Oracle VM Server 2.2 has at least 4GB free space
for downloading and installing the template. The working directory can be any
directory on the Oracle VM server except /OVS/running_pool.
Note: The /root partition of the default Oracle VM server install may not have
enough space to temporarily host the template installation. Please use other
directory that has sufficient free space.
- At least 15GB of free space in the cluster root storage repository. For storage
and repository configuration, please refer to Oracle VM 2.2 Server User Guide:
http://download.oracle.com/docs/cd/E15458_01/doc.22/e15444/storage.htm
and
http://download.oracle.com/docs/cd/E15458_01/doc.22/e15444/repository.htm
- At least 2GB of free memory on the Oracle VM Server
- A static IP address for the Oracle VM Manager
- If enabling HA (high availability) for the Oracle VM Manager,
mount a clustered OCFS2 or NFS filesystem on /OVS. If ext3 or a
local OCFS2 filesystem is used, enabling HA will cause the high availability
prerequisite checking to fail. The Oracle VM Manager configuration
process will exit without completing the configuration.
- The Oracle VM Manager will register the first VM that it detects.
To have Oracle VM Manager be the first VM registered,
make sure there are no virtual machine images besides the Oracle VM Manager
virtual machine in the /OVS/running_pool directory on the Oracle VM Server.
- A desktop or other system with a VNC Viewer installed
The steps below assume that the Oracle VM Server used is not currently
or was not previously managed by another Oracle VM Manager. If this is not
the case, the instructions below will ask user clean up Oracle VM Agent DB
before running the Oracle VM Manager.
2. Oracle VM Manager Template Description
=========================================
The Oracle VM Manager Template is distributed as one archive file which
includes:
File Version
OVM_EL5U3_X86_OVM_MANAGER_PVM.tgz 2.3
Deploy_Manager_Template.sh 2.3
The OVM_EL5U3_X86_OVM_MANAGER_PVM.tgz archive contains two disk images,
a VM configuration file and a readme file:
- Oracle Enterprise Linux 5.3 x86 system disk image
- Oracle VM Manager 2.2 disk image
- vm.cfg
- README
The system image is a JeOS (Just enough OS) installation of Oracle
Enterprise Linux 5.3. It is a smaller footprint install that contains
the only packages needed by Oracle VM Manager.
Oracle VM Manager is configured to use Oracle Database 10g
Express Edition (included).
Deploy_Manager_Template.sh is used to check the prerequisite and
create virtual machine.
During the first boot of the Oracle VM Manager virtual machine,
the Oracle VM Manager configuration process will create server pool
and import the Oracle VM Manager virtual machine.
Two OS user accounts are created by default:
user: root password: ovsroot
user: oracle password: oracle
The user 'oracle' belongs to the 'oinstall' and 'dba' groups.
The default vnc console password is 'oracle'
3. Creating the Oracle VM Manager virtual machine
=================================================
1) Download the Oracle VM Manager Template (V19215-01.zip)
from http://edelivery.oracle.com/oraclevm
2) Login to the Oracle VM Server's dom0 as 'root'
Copy V19215-01.zip to your working directory with at least 4GB free space.
You can choose any directory on OVM Server except /OVS/running_pool.
This zip file contains the archive file OVM_EL5U3_X86_OVM_MANAGER_PVM.tgz
and a deploy script Deploy_Manager_Template.sh
3) As root, run
# unzip V19215-01.zip
4) As 'root', run the deployment script:
# chmod 755 Deploy_Manager_Template.sh
# ./Deploy_Manager_Template.sh
The deployment script Deploy_Manager_Template.sh will complete the following
tasks:
a) prerequisite checking
b) uncompress OVM_EL5U3_X86_OVM_MANAGER_PVM.tgz file to directory
/OVS/running_pool. This directory will contain the files following files:
/OVS/running_pool/OVM_EL5U3_X86_OVM_MANAGER_PVM
|- System.img (OS image file)
|- Manager.img (Manager image file)
|- vm.cfg (VM configuration file)
|- README (Readme file)
c) generate and assign new MAC address to the virtual machine
d) interview the user for VM and VM Manager configuration parameters
(next section 'Deployment interview' provides the list of questions)
e) create and boot the virtual machine from the Oracle VM Server
command line
f) display the access information for Oracle VM Manager and Oracle VM
Manager VM
4. Deployment Interview
=======================
The deployment script will prompt a user to enter
a) Agent password
The agent password is required for the prerequisites check.
b) Storage configuration
Storage Source: NFS address, OCFS2 partition path
The script will automatically detect your cluster root storage repository
if you have configured it. Or it prompts users to input their storage source
and the script tries to set it up as cluster root.
NOTE: how to manually create your own storage repository in OracleVM server 2.2.x
1) Register your storage source. Example:
/opt/ovs-agent-2.3/utils/repos.py -n myhost:/mynfslocation
/opt/ovs-agent-2.3/utils/repos.py -n /dev/sdb3
Note that the storage source should have at least 15GB free space.
If the storage source is successfully registered, note down the uuid genereated
by the command above, such as:
51d4c69b-e439-41ac-8b31-3cc485c993b0 => /dev/sdb3
2) Mount your storage repository.
If the agent version is 2.3-27 or higher, execute:
/opt/ovs-agent-2.3/utils/repos.py -i
otherwise, complete the following commands:
[1] mkdir -p /var/ovs/mount/$(echo <uuid> | sed s/-//g | tr '[:lower:]' \
'[:upper:]')"
where '<uuid>' is the uuid noted down in step 2)
[2] mount your storage source to the directory made in step [1].
3) If /OVS exists, delete or move /OVS
mv /OVS "/OVS.$(date '+%Y%m%d-%H%M%S').orig"
create a symbolic link from storage repository to /OVS
ln -nsf /var/ovs/mount/<UUID>/ /OVS
c) Network configuration
Static IP address
Netmask
Default Gateway IP address
DNS Server IP address
Hostname
d) Password for database accounts:
'SYS' and 'SYSTEM' (the same password the same password is used)
'OVS'
'oc4jadmin'
'admin'
e) Web Service configuration (supported in template in version 1.2)
Web Service password (at least 6 characters)
Enable HTTPS or not
f) SMTP server (outgoing mail server SMTP hostname)
E-mail Address for account 'admin'
g) Data for the manager services configuration:
Oracle VM Server Pool Name
Oracle VM Server login user name
Oracle VM Server login password
Note that Oracle VM Manager is critical for managing Oracle VM Server Pools.
Do not pause, suspend or shutdown this virtual machine! Configuring
HA is recommended for this virtual machine so that Oracle VM will
automatically restart the Oracle VM Manager virtual machine if there
is a server crash.
5. Known Issues
===============
1) You may see messages on a virtual machine's console similar to these
when the virtual machine is booting up:
Fatal: No PCI config space access function found
rtc: IRQ 8 is not free.
i8042.c: No controller found.
These messages can be ignored.
2) Mail server check fails.
Bug #7140 in bugzilla.oracle.com
Oracle VM Manager installer only checks the default SMTP port 25 for the
mail server. If the SMTP port is not 25, the check fails, and you will
see the following message:
Mail server '<mail server hostname>' check failed, want to re-enter it(Y|n)?
You can enter 'n' to skip the mail server checking. You will also see the
send mail checking fails with following message:
Failed to send mail to '<Admin e-mail address>'
want to re-enter the e-mail address(Y|n)?
You can enter 'n' to skip the send mail checking.
3) OEL VM console may display error messages similar to those below:
BUG: warning at drivers/xen/fbfront/xenfb.c:143/xenfb_update_screen() (Not
tainted)
Call Trace:
[<ffffffff803aa461>] xenfb_thread+0x135/0x2c5
[<ffffffff8024874b>] try_to_wake_up+0x365/0x376
[<ffffffff8029ba6e>] autoremove_wake_function+0x0/0x2e
[<ffffffff8029b856>] keventd_create_kthread+0x0/0xc4
[<ffffffff803aa32c>] xenfb_thread+0x0/0x2c5
[<ffffffff8029b856>] keventd_create_kthread+0x0/0xc4
[<ffffffff802339c8>] kthread+0xfe/0x132
[<ffffffff80260b24>] child_rip+0xa/0x12
[<ffffffff8029b856>] keventd_create_kthread+0x0/0xc4
[<ffffffff802338ca>] kthread+0x0/0x132
[<ffffffff80260b1a>] child_rip+0x0/0x12
This will not cause any problems.
4) If you accidentally power off Oracle VM Manager virtual machine through
Oracle Manager UI, and restart the virtual machine from OVM server command
line, although Oracle VM Manager virtual machine is running normally,
the virtual machine status in Manager UI will stay in 'Shutting Down'.
This is expected, as the virtual machine status sync will only happen when
the virtual machine status is "Error" or "Powered Off".
To re-sync the virtual machine status, please complete the following steps:
1. Log on the Manager UI;
2. Navigate to the 'Virtual Machines' tab;
3. Select Oracle VM Manager virtual machine, "OVM_EL5U3_X86_OVM_MANAGER_PVM";
4. Choose 'Reset' from 'More Actions' dropdown list;
5. Click 'Go' button, the status will become "Running" after a while.
5) (Bug 9191053) For OVS agent version 2.3-19, the following High
Availability scenario will not work.
"If a Virtual Machine Server fails, all running virtual machines are
restarted automatically on another available Virtual Machine Server."
For OVS agent 2.3-19, Oracle VM Manager virtual machine will not be
automatically restarted on any other available Virtual Machine Server,
but on the original Virtual Machine Server when it becomes available again.
To fix the issue, please upgrade OVS agent to 2.3-27 or the latest version. -
Connect to SQL Server from Oracle
Does Oracle offer any connectivity to NON-Oracle databases such as SQL Server from within the Oracle database itself, similar to a database link ?
Yes, it's called Heterogeneous Connectivity. Basically how it works is you set up an ODBC data source on the Oracle server
and need to modify the tnsnames.ora and listener.ora files. Once you get it set up it works exactly like a dblink. You should be
able to find information on it in the Oracle manuals or from Metalink. There's also a Heterogenous Connectivity forum on OTN. If
you can't find anything let me know and I can send you some documents on how to set it up. I think the hardest part for you might
be finding a SQL Server ODBC driver for HP-UX. -
Oracle DB: How to read data from a corrupted database table.
Hi All,
Wanted to know if there is a way I could read data from a corrupted Oracle database table?
Are there any tools that I can use? Or does Oracle provides any mechanism to do that?
Any pointers in this regard would be helpful.
Thanks in Advance.user10600611 wrote:
Table shows inconsistent data.You are going to have to be more specific. Inconsistent in what sense? A correct data model should not allow for inconsistencies to crop up.
However, you may be able to use one of the many FLASHBACK features of Oracle to look at the table at a prior point in time before the corruption.
HTH! -
Oracle VM Linux Os (Oracle VM server 2.1 + Oracle VM manager 2.1)
All experts
What is Oracle VM Linux Os and what difference between
Oracle VM server 2.1
and
Oracle VM manager 2.1
Thanks in advanceWhy is it easier for you to use two separate postings to ask us to read the docs for you rather than reading them yourself?
http://www.oracle.com/technology/tech/virtualization/index.html -
Problem with console in Oracle VM Manager
I have installed Oracle VM 3.0.3 and Oracle VM Manager 3.0.3 is install on Oracle LINUX 5.6. I cannot get the console to work from either the Oracle VM Manager server itself using firefox or remotely from Windows running IE or Chrome. After looking at version posts I have installed tightvnc-java-1.3.9 and ovm-console-1.0.0. The symptoms are different locally and remotely. First locally on the OVM Manager server with firefox. I click on console and a pop up asks if I want to run ovm_rasproxy-ws.jnlp click OK and things go crazy, multiple tabs open and keeps going until I kill firefox or the server runs out of resources. On the remote PC I click console and things just hang and nothing happens. Checked firewall settings, iptables is not running, I can telnet to port 15901.
Any ideas
Richardmaybe this will help
local ( oracle vm manager )
ovm_rasproxy-ws.jnlp --> need open by javaws . search the javaws path . or maybe you can install sun java version 7 1st . remote pc
need install realvnc and java jre ( try install java version 7 )
version 3.0.3 - for IE need IE 9 and above. -
Oracle Identity Manager looking for OracleAS 10.1.3.x
Hi,
I need to install the following products on 2 servers
Oracle Identity Management Suite (OID, DAS, SSO) as a OracleAS Active-Active Cluster.
Oracle Identity Manager in Cluster
Oracle Access Manager in Cluster
Oracle Virtual Directory in Cluster
with F5 load balancers
A bit complex configuration, but think i can achieve it. I completed the first task successfully but now I am facing a problem when i wanted to install the Oracle Identity Manager 9.1 on the existing OracleAS cluster. OIM is looking for a 10.1.3.x version of OracleAS where as the Oracle Identity Management suite is shipped with OracleAS 10.1.0.2 version. we went ahead with the installation process as there was no reference of application server version in the Oracle Identity Management Certification matrix and the OracleAS 10.1.3.4 certification document below mentioned that IM 10.1.4.0.1 is shipped with 10.1.3.x version.
http://www.oracle.com/technology/software/products/ias/files/oracle_soa_certification_101310.html
Can anyone guided me how should i go ahead with this.
Thanks & Regards
Ramesh GKCheck this OIM on OAS issues
SOA suite is using jdk 1.5.x , Identity Management Suite is using jdk 1.4.x. My advice is to use OC4J from SOA Suite. Open a SR to confirm this. Some OIM required patch for OC4J are only for 10.1.3.x and can't be applied to OC4J from Identity Management Suite, also you can't not use the same database for OIM and IDM repository if you are using multilanguage installation. -
Isolate app server from external RFC's, idocs
There is a server in our SAP R3 landscape that needs to be isolated both from user logon, external communiction like idocs and also load balancing of batch jobs to this server.
The user logon is no issue, config via SMLG by not including the server in the logon groups.
The external idoc coming in is still an issue to be addressed.
So is the batch job issue. This server requires background processes. But we don't want general batch jobs load balanaced to this server.
If idocs were balanced to that server, potentially they would wait (because of heavy procesing occuring on this server) and could processes to backup.
Can these be eliminated via usage of RZ12? By default a server in the environment will be in that group.
Could the server effectively be isolated by creating some bogus server logon group and assigning the server to it?
So 2 issues:
1. isolate server from idocs
2. isolate server from having batch jobs load balanced to it.
Any thoughts appreciated on this matter of isolating a server from the rest of the landscape so that it can be dedicated to a specific process.We understand the issues of you as below.
1. isolate server from idocs (The external idoc coming in is still an issue to be addressed)
- As u already eliminated the target server from SMLG, User login are managed but why external IDOC's are coming.
View-1) if the IDOC's are coming from other ABAP System, Check the RFC Connections of Source ABAP System to This Target ABAP System, Are they using by any chance LOGON group "SPACE". if yes...pl assign it to a Custom LOGON GROUP of Source which does not include the application server you desire.
View-2) if the IDOC's are coming directly from an external NON-ABAP System, Analyze where the external RFC server is registered..Secondly.....How the Inbound IDOCS are processed by Function Module....Select " TRIGGER BY BACK GROUND PROGRAM" instead "TRIGGER IMMEDIATELY" to build a control thru which BATCH Server the INBOUND IDOCS are processed.
2. isolate server from having batch jobs load balanced to it.
This you can acheive it as Mr.Sunil Bujade said thru SM61 in this thread.
3. HTTP Logins to thru that application server
If your ECC System connected to a Portal , and you are experience some WEB logins (IC) login on this application server ,
Do not activate the parameters on the application server where you do not desire HTTP Connections, which will stop HTTP Logins.
icm/server_port_0
icm/host_name_full
login/accept_sso2_ticket
login/create_sso2_ticket
(or)
You should Disable / Deactivate ICM of application server said by Mr.Khaiser in this thread ( I think after every restart ).
If time allows have a look of these Notes.
SAP Note 0001385751 Deactivating background processing
SAP Note 0000786412 Determining execution server of jobs w/o target server
SAP Note 0001359508 Background server groups: Blank server name in server group
SAP Note 0000519059 FAQ: Background processing system
A Final Question,
In which scenario, A server is not for GUI LOGINS, not for Specific BATCH Jobs, not for HTTP Logins, is required.. May we request a Technical Scenario was required such application server which may be useful to connect to the requirement when similar demand in our landscape.
Rgds -
Oracle VM Manager 3.1.1 will not delete a malfunctioning OVS server
We have a Oracle VM 3.1.1 environment up and running. We were able to add 4 servers to a clustered pool without issue. But when we got to the 5th box we ran into an issue. We got it up all the ports bonded but realized we had a SAN level issue. Since then we have been trying to delete the server that is now offline due to that issue. It appears I can not remove the server from VM Manager because it can no longer communicate with the ovs-agent. How do I delete a server that's already defined in the environment but no longer exists?
We have attempted to recreate and readd the host with the same name and IP address but cant control the server. It shows up but is in a constant "starting" state. We can not delete, edit, or modify any aspect of the server from bonded ports.
The server is current stuck in Unassigned Servers. It's prevent us from modifying or using several of our VLANs to due assigned ports that no longer exist. No VM's exist on any server.
We have rebooted the OVM Manager, we have restarted the OVS servers, acknowledged, we have stopped the services & cleared the /etc/ovs-agent/db folder, and just about anything we can think of.
Can anyone assist us? We have logged an SR but havent heard back from them. This is a major issue for us as we have a dozen people waiting on this environment standup and are currently completely dead in the water.
When we try and delete the server we receive the following error.
Job Construction Phase
begin()
com.oracle.odof.exception.ObjectException: Caught during invoke method: java.lang.NullPointerException
at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:151)
at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:773)
at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.NullPointerException
at com.oracle.ovm.mgr.api.manager.Page83Map.removeServerReservedLunFromPage83Map(Page83Map.java:212)
at com.oracle.ovm.mgr.api.physical.ServerDbImpl.onPersistableClean(ServerDbImpl.java:565)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:822)
at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:245)
at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:219)
at com.oracle.ovm.mgr.api.job.JobEngine.invokeMethod(JobEngine.java:744)
at com.oracle.ovm.mgr.api.manager.ModelManagerDbImpl.deleteObject(ModelManagerDbImpl.java:868)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:822)
at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:245)
at com.oracle.ovm.mgr.api.manager.ModelManagerProxy.deleteObject(Unknown Source)
at com.oracle.ovm.mgr.api.manager.OvmManagerImpl.deleteObjectInternal(OvmManagerImpl.java:386)
at com.oracle.ovm.mgr.api.manager.OvmManagerImpl.deleteObject(OvmManagerImpl.java:409)
at com.oracle.ovm.mgr.api.manager.OvmManagerImpl.deleteObject(OvmManagerImpl.java:391)
at com.oracle.ovm.mgr.api.system.FoundryDbImpl.deleteServer(FoundryDbImpl.java:1007)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
... 7 more
Job Aborted from server, cleaning up client.
Description:
(10/03/2012 06:27:31:178 PM) Due to Abort by user: admin
https://dl.dropbox.com/u/55193042/OracleVMManager_Issue1.pngDid you unpresent the repository from the OVS server? Try to remove the OVS server from the serverpool AFTER unpresenting the repository.
If this is successful, you may be able to delete the problem server.
There is a more drastic solution that worked with OVM 3.0.1 which involved reinstalling OVM Manager with the repository uuid. This rebuilt the database cleanly but dropped the friendly names leaving only uuids. Perhaps you may not have to do this if unpresenting the repository works. -
Oracle Identity Manager 9.1.0.2 and Oracle Weblogic server 11g R1 b(10.3.1)
Hi,
can we Install Oracle Identity Manager 9.1.0.2 version on Oracle Weblogic server 11h R1 b(10.3.1)?
Is it OIM 9.1.0.2 compatible to install on Oracle Weblogic server 11h R1 b(10.3.1).
Early response is appreciatedCheck this
http://www.oracle.com/technology/software/products/ias/files/idm_certification_101401.html#BABGBGHI
And Oracle has mentioned that
*2.1 Certified Application Servers*
Note: There is no change in application server certification from
release 9.1.0.1 to release 9.1.0.2.
Oracle WebLogic Server 10.3
But you can try with new version of Weblogic. It shouldn't create any problem. -
Facing error in starting managed server from nodemanager
Hi All,
I have installed WebLogic server 10.3.4 and installed OSB 11.1.1.4.0. I created domain with one admin server and one managed server for osb. When I started managed server with the startManagedWebLogic command it got started successfully but when I am trying tp start the managed server from nodemanager I am getting the following error
starting weblogic with Java version:
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
Starting WLS with line:
D:\JDK\JROCKI~1.0\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx512m -Dweblogic.Name=osb_server1 -Djava.security.policy=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=D:\Oracle_OSB\Middleware\user_projects\domains\osb_domain\servers\osb_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=D:\ORACLE~1\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1 -Djrockit.optfile=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\servers\osb_server1 -Doracle.domain.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\servers\osb_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dem.oracle.home=D:\Oracle_OSB\Middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://soaspt-app01.scotwat.net:7010 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\ORACLE~1\MIDDLE~1\patch_wls1034\profiles\default\sysext_manifest_classpath;D:\ORACLE~1\MIDDLE~1\patch_ocp360\profiles\default\sysext_manifest_classpath weblogic.Server
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
<11-Mar-2013 13:22:17> <FINEST> <NodeManager> <Waiting for the process to die: 5916>
<11-Mar-2013 13:22:17> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<11-Mar-2013 13:22:17> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
My nodemanager is started and reachable. The error above says "Address already in use" but I am able to start my managed server through startManagedWebLogic.cmd command.
Can anyone please tell me what could be the issue. It is really urgent. Please help!!Hi Roshni,
It is likely that a configuration is missing or not set properly in the Node Manager properties file (nodemanager.properties) since the managed server can be started up using startManagedWebLogic.cmd but not with Node Manager. I would complete the following steps to fix the problem:
1. Go to %WLS_HOME%\common\nodemanager and open up nodemanager.properties (Make a backup of the file first). NOTE: WLS_HOME is your WebLogic Server home.
2. Look for the parameters "StartScriptEnabled" and "StopScriptEnabled". They should be set to true. If not, please set them to true.
3. Save and close the file.
4. Restart the Node Manager
If you are still unable to start the manager server using Node Manager, you may need to update the DEBUG_PORT parameter in setDomainEnv.cmd located in %MIDDLEWARE_HOME%\user_projects\domains\%DOMAIN_HOME%\bin (always make a backup before changing a configuration file). You may refer to Oracle Support note 1272642.1 for more information about the nodemanager.properties file and how to configure the DEBUG_PORT parameter in setDomainEnv.cmd if needed.
Thanks,
Scott (PITSS)
http://pitss.com/us -
Starting Managed Server from Administration Console
Hi
I am new for SOA and fusion. Can anyone share the brief steps that are needed to start/stop a Managed Server from Admin Console.
I did a fresh install on RHEL5 and configure a domain. i was able to start the services from script which are created when creating a domain.
But when i assigned a Managed Server to a Node Manager and try starting the Managed server. It does not start and in the log i can see exceptions like below
Failed to invoke startup class "JPS Startup Class", java.lang.ClassNotFoundException: oracle.security.jps.wls.JpsWlsStartupClass
java.lang.ClassNotFoundException
Failed to invoke startup class "ODL-Startup", java.lang.ClassNotFoundException: oracle.core.ojdl.weblogic.ODLConfiguration
java.lang.ClassNotFoundException
I start the services in below order
Weblogic Server
node Manager
and
soa_server
Thanks
Hariyou must set to true the StartScriptEnabled property in nodemanager.properties
Maybe you are looking for
-
I recently had a problem with my iPhone 3G. I upgraded to OS 5.1.1. The thing crashed. I took it to the AT&T store and they cleared it of everything. So I re-installed all of my personal stuff and apps. All is again OK with the exception of the
-
Captivate 6 - Cannot copy and paste to different slides
Hello, I have recently spent some time creating an Captivate template to use for my company' s eLearnings. I noticed when I created a project from this template, I am not able to copy and paste objects (eg buttons) from one slide to the next in the n
-
Everytime i boot up my computer what ever was in my itunes is gone and i have to re up load everything. if i upload all the music and close itunes and bring it back up its all still there its just when i turn of my computer and boot it back up is whe
-
I f I type a sentence with uppercase clicked on and then decide I do not want it in upper case but in lower case, so I go <Format> <Capitalization> <no Caps> nothing happens. I can't seem to be able to change to lower case except by re-typing the who
-
Can i install 'extra audio content' after i have installed the main program?
hello all! i need to install the 'extra audio content' that comes with Logic, as i didnt include them when installing in the first place. how do i go about doing this? i mainly need all the different presents and chanel strips, not so bothered about