Embed Size (px)
Citation preview
The Oracle Cloud Cookbook
Show a printer friendly, save as PDF version of the Oracle Cloud Cookbook
Distribution of the Oracle Cloud Cookbook or derivative of the work in any form for
commercial purposes is prohibited unless prior permission is obtained from the copyright
holder.
Author: Roddy Rodstein
Change Log
Revision Change Description Updated By Date
1.0 First Release Roddy Rodstein 09/10/11
1.0 Oracle Cloud Reference Design Roddy Rodstein 11/21/11
1.0 Oracle VM Licensing, Support and Packaging Roddy Rodstein 09/17/11
1.0 Oracle VM for x86 Server Sizing Advisor Roddy Rodstein 10/10/11
1.0 Oracle VM Server CD-ROM Installation Roddy Rodstein 09/10/11
1.6 Oracle VM Manager Installation Roddy Rodstein 04/06/12
1.0 Oracle VM Patch Updates Roddy Rodstein 10/05/11
1.1 Oracle Linux 6 Installation with Oracle VM Manager Roddy Rodstein 04/29/12
1.0 Oracle Enterprise Manager 12c Architecture, System Design and Sizing Roddy Rodstein 10/22/11
1.0 Oracle Enterprise Manager 12c Installation Roddy Rodstein 12/02/11
1.0 Oracle Enterprise Manager 12c Upgrade Roddy Rodstein 10/29/11
1.0 Register Oracle VM Manager 3.0 in Oracle Enterprise Manager 12c Roddy Rodstein 09/20/11
1.0 Oracle Enterprise Manager 12c Architecture, System Design and Sizing Roddy Rodstein 06/13/11
1.1 Oracle Linux 5 Installation Roddy Rodstein 04/29/12
1.1 Oracle Linux 6 Installation Roddy Rodstein 04/29/12
Table of Contents Audience
Objectives
About the Author
The Oracle Cloud Cookbook Introduction
Audience The Oracle Cloud Cookbook is an on-line resource to assist our customers, prospects and
partners to plan, design, deploy and support internal and external Oracle clouds using
Oracle VM for x86 managed by Oracle VM Manager, Oracle Enterprise Manager and Open
Source solutions. This book assumes that the reader has an architectural understanding of
cloud computing, Oracle technologies, storage and network systems, and related software.
Objectives The Oracle Cloud Cookbook intends to articulate the design considerations and validation
efforts required to design, install, deploy and support Oracle VM for x86 with Oracle
Linux, Solaris x86, JRockit Virtual Edition, and Microsoft virtual machines hosting Oracle
Database, Oracle Fusion Middleware technologies and Oracle Applications managed by
Oracle VM Manager, Oracle Enterprise Manager and Open Source solutions in internal
and/or external clouds.
About the Author Roddy Rodstein is an avid technologist, entrepreneur and author with a long history with
virtualization technologies and cloud computing. After ten years supporting virtualization,
cloud computing and application delivery technologies at Citrix and Oracle, Roddy
established Mokum Solutions, Inc.. Mokum Solutions, Inc. is a consultant and integrator of
Oracle technologies in private and public clouds. Earlier in his career Roddy successfully
established, owned, and operated a consulting business that specialized in server and
desktop virtualization solutions.
Roddy's professional achievements also extend to blogging, writing and self-publishing
industry reference guides currently available on Amazon, Securing Microsoft Terminal
Services (ISBN: 061514330X), Citrix CCA MetaFrame 1.8 for Windows Exam Cram
(ISBN: 1576109453) and web publications like The Underground Oracle VM Manual as
well as the development and ongoing management of the number one independent Oracle
social media website, ITNewsCast.com.
The Oracle Cloud Cookbook Introduction Welcome to the first edition of the Oracle Cloud Cookbook. Our goal with the Oracle
Cloud Cookbook is to create a comprehensive resource to assist our customers, prospects
and partners to plan, design, deploy and support internal and external Oracle clouds using
Oracle VM for x86 with Oracle Linux, Solaris x86, and Microsoft virtual machines hosting
Oracle Database, Oracle Fusion Middleware technologies and Oracle Applications
managed by Oracle VM Manager, Oracle Enterprise Manager and Open Source solutions.
The Oracle Cloud Cookbook will cover each of the three cloud layers; Infrastructure as a
Service (IaaS), Platform as a Service (PaaS) and Software as a Service (SaaS).
The Infrastructure as a Service (IaaS) chapters review how to plan, design, deploy and
support Oracle VM for x86 with Oracle Linux, Solaris, and Windows virtual machines
Managed by Oracle VM Manager and Oracle Enterprise Manager. The Platform as a
Service (PaaS) chapters review how to plan, deploy and support Oracle Database and
Oracle Fusion Middleware technologies on the aforementioned IaaS platform. The
Software as a Service (SaaS) chapters review how to plan, deploy, support and deliver
Oracle Applications in internal and external clouds.
Table 1 shows the Oracle cloud stack that will be covered in the Oracle Cloud Cookbook.
Software as a
Service SaaS Oracle Applications
Oracle
Enterprise
Manager
Oracle
VM
Manager
Open
Source
Solutions
Platform as a
Service
PaaS
Oracle Fusion Middleware
Oracle Database
Infrastructure as
a Service IaaS
Virtual Machines
Oracle VM for x86
x86 64 Servers
Storage
Oracle Desktop Virtualization Security Solution at DISA Mission Partner Conference 2012
building an appliance? physical ? virtual? production quality? use Oracle Linux
understanding memory allocation in oracle vm / xen
Oracle VM Administration: Oracle VM Server for x86 course schedule
figuring out cpu topology in oracle vm
Collaborate12 Starts Today!
Oracle VM Administration: Oracle VM Server for x86 - new Training
More Oracle VM templates for PeopleSoft and Oracle Enteprise Manager
Oracle Ebusiness Suite 12.1.3 Oracle VM templates
Eight New Oracle Database Assemblies Ready to Run In Your Oracle VM Cloud with
Oracle Enterprise Manager 12c
Oracle Cloud Reference Design
Show a printer friendly, save as PDF version of the Oracle Cloud Cookbook
Copyright © 2012 Mokum Solutions, Inc. All rights reserved.
Distribution of the Oracle Cloud Cookbook or derivative of the work in any form for
commercial purposes is prohibited unless prior permission is obtained from the copyright
holder.
Author: Roddy Rodstein
Change Log
Revision Change Description Updated By Date
1.0 First Release Roddy Rodstein 11/21/11
1.1 Content Refresh Roddy Rodstein 04/15/12
1.2 Oracle VM for x86 Disaster Recovery Roddy Rodstein 04/16/12
1.3 Oracle VM Servers backup and restoration Roddy Rodstein 04/20/12
Table of Contents The Oracle Cloud Reference Design Introduction
The Oracle Cloud Reference Design Implementation Overview
The Oracle Cloud Reference Design Support Infrastructure
Cloud Infrastructure Architecture
...Oracle VM for x86 Hardware Architecture
...Oracle VM for x86 Server Pool Design
...Oracle VM for x86 Disaster Recovery
...Oracle VM for x86 Security Standards
...Oracle VM for x86 Administration and Monitoring Standards
...Virtual Machine Operating System Standards
...Support Service Standards
The Oracle Cloud Reference Design Introduction This chapter of the Oracle Cloud Cookbook presents the Oracle Cloud reference design.
The Oracle Cloud reference designs encompass the software, hardware, storage, and
network components required to deploy a scalable, secure, and supportable internal or
external Oracle cloud.
The Oracle Cloud reference design is a field-tested best-practice standard, designed with
simplicity, reproducibility, usability, scalability, supportability and security. The Oracle
Cloud reference designs represent a complete Oracle Cloud standard that can be leveraged
as a vanilla solution or modified to more accurately reflect organization-specific needs. The
Oracle Cloud reference design includes the following categories and solutions:
Software as a
Service SaaS Oracle Applications
Oracle
Enterprise
Manager
Oracle
VM
Manager
Open
Source
Solutions
Platform as a
Service
PaaS
Oracle Fusion Middleware
Oracle Database
Infrastructure as
a Service IaaS
Virtual Machines
Oracle VM for x86
x86 64 Servers
Storage
Note: A detailed explanation of each category and solution in the Oracle Cloud reference
design is presented in the architectural overview section.
The Oracle Cloud Reference Design Implementation Overview The Oracle Cloud reference design provides a well defined starting point for each Oracle
Cloud implementation. It also serves as a baseline upon which all solution additions,
revisions, and tools will be based. As such, there is an increasing value to Oracle Cloud
reference design in keeping implementations as close to the reference design as possible.
Prior to implementing an Oracle Cloud, it’s important that an infrastructure assessment (IA)
and gap analysis (GA) be performed. During the IA/GA, the architecture of the solution
will match the customer’s business needs while maintaining the integrity of the Oracle
Cloud reference design. Implementation and support will follow the analysis phase after
careful consideration has been given to any specific design modifications that deviate from
the Oracle Cloud reference design.
This document outlines the decision points necessary for implementing the Oracle Cloud
reference design. For decisions that rely on preexisting factors or specific organizational
needs, the appropriate best practice will be discovered in the infrastructure assessment (IA)
and gap analysis (GA). The best practices should be analyzed carefully and decisions
should be made based on organizational needs, existing architecture, and budget resource
availability.
The Oracle Cloud reference design is designed to be scalable and resilient for ease of
implementation, high availability, and ease of maintenance for internal and external Oracle
clouds. The complete solution is made up of three architectural components that work
together to provide flexibility and options with respect to on-demand self-service, broad
network access, resource pooling, elasticity, measured service, high availability, security
and ease of maintenance. The design breaks down into the following three components:
Software as a Service (SaaS). Software as a Service is the capability to host and
deliver applications over the Internet, accessible from various client devices. The
provider manages the cloud infrastructure and application portfolio that is
accessed by the consumer. The Oracle Cloud reference design outlines the
decision points necessary for implementing an Oracle cloud infrastructure and
Oracle Software as a Service delivery model.
Platform as a Service (PaaS). Platform as a Service is the capability to host and
allow access to a computing platform and software stack for application
development. The provider hosts the computing platform and software stack on
the cloud infrastructure that is accessed by the consumer. The consumer manages
the computing platform and software stack used for application development. The
Oracle Cloud reference design outlines the decision points necessary for
implementing the cloud infrastructure and the Oracle Platform as a Service
delivery model.
Infrastructure as a Service (IaaS). Infrastructure as a Service is the capability to
provision and deliver fundamental computing resources as a service to the
consumer. The Oracle Cloud reference design outlines the decision points
necessary for implementing the cloud infrastructure to deliver Oracle Software as
a Service and Oracle Infrastructure as a Service.
Figure 1 shows a high-level overview of the Oracle Cloud reference design components.
The Oracle Cloud reference design isolates Oracle VM server pools into the following four
security domains:
Controlled: A controlled security domain is used to restrict access between security
domains. A controlled security domain could contain groups of users with their
network equipment or a demilitarized zone (DMZ).
Uncontrolled: An uncontrolled security domain refers to any network not in control
of an organization, such as the Internet.
Restricted: A restricted security domain can represent an organization’s
production, test and development networks. Access is restricted to authorized
personnel, and there is no direct access from the Internet.
Secured: A secured security domain is a network that is only accessible to a small
group of highly trusted users, such as administrators and auditors.
Note: The classification of security domains is very similar to data classifications. FIPS
PUB 199 is the Standards for Security Categorization of Federal Information and
Information Systems. FIPS PUB 199 can be used to determine the security category of
systems and within which security domain systems should reside.
The Oracle Cloud Reference Design Support Infrastructure Support is an integral part of the Oracle Cloud reference design and includes a combination
of Oracle support agreements and on-site and off-site support from the implementing party.
Administrators will have several options for support, including live assistance, phone
support, and forums.
Cloud Infrastructure Architecture This section provides a decision matrix for the Oracle Cloud reference design.
Implementers of the Oracle Cloud reference design can use the decision matrix as quick
reference guide to identify settings and configuration decisions to be implemented in the
environment. These decisions should be carefully analyzed during a gap analysis phase.
Oracle VM for x86 Hardware Architecture Selecting the right hardware for your Oracle VM environment is a critical component in the
success of your Oracle Cloud project. The resource requirements of all the virtual machines
provides the aggregate CPU, RAM and storage requirements necessary to calculate the
Oracle VM Servers hardware requirements. For example, a single Oracle VM Server
supports up to 160 CPU cores or threads, 2TB of memory and a maximum of 128 virtual
disks.
Tip: Please use our Oracle VM for x86 Server Sizing Advisor to accurately calculate the
number of servers you will need for your environment.
Decision
Point
Decision Justification
Certificati
on
The server hardware must be jointly supported
by the hardware vendor and Oracle.
Note: The following link is the Oracle'
hardware certification page.
http://linux.oracle.com/pls/apex/f?p=117:1:57
73793518142288::NO:RP::
Only jointly supported
hardware product receive
vendor support when
problems occur and service
tickets are created. The server
hardware must be jointly
supported by the hardware
vendor and Oracle.
CPU Server hardware will be ordered with two
socket Intel or AMD multiple-core CPUs for
small and medium workloads and four socket
multiple-core CPUs for large CPU-bound
workloads.
The Maximum Number of
CPU cores or threads an
Oracle VM server can
support is 160. Oracle VM
server maps a virtual CPU to
a hardware thread on a CPU
core in a CPU socket.
Oracle VM Server supports
CPU oversubscription, which
means that an Oracle VM
Server with 160 CPU cores
could overallocate the total
number of CPU cores to
virtual machines. For
example, a server with an
Intel Xeon processor 5600-
series CPU with
hyperthreading can have up
to six cores and twelve
threads per socket. A two
socket server with an Intel
Xeon processor 5600-series
CPU could allocate twenty
four virtual CPUs without
oversubscribing the physical
CPUs.
CPU-bound workloads
should not be on servers with
oversubscribed CPUs.
RAM Server hardware will be ordered with the
maximum amount of physical memory.
Note: Oracle VM Server supports up to 2TB
of RAM.
Oracle VM server does not
support memory
oversubscription, which
means that an Oracle VM
server cannot accept a Live
Migration or HA request
unless the server has
available RAM for the virtual
machines. Having available
RAM on each server provides
flexibility in terms of adding
new virtual machines to the
server pool, and to allow Live
Migration and HA within a
server pool.
By default, each Oracle VM
server reserves 512MB of
memory for dom0. The
average memory overhead for
each running guest on a dom0
is approximately 20MB plus
1% of the guest’s memory
size. The remaining physical
memory can be allocated to
guests.
Storage Unless the Oracle VM server is booting from
SAN, redundant SSD internal hard drives are
recomended.
Oracle VM Server requires
“only” 4 GB of local storage
for the entire Oracle VM
Virtual machine image and configuration files
are hosted on shared SAN, iSCSI, or NFS
repositories.
Server installation. The
design goal for Oracle VM is
to support multiple node
Oracle VM Server pools with
shared fibre channel SAN,
iSCSI and/or NFS storage.
Note: Oracle VM 3 supports
single server local storage
without HA or Live
Migration. With local
storage, the OCFS2 virtual
machine file system must be
on a dedicated hard dirve, i.e.
a partition on same disk as
Oracle VM server is not
supported. An Oracle VM
server with local storage is
limited to a server pool with
only one server, without high
availability (HA) or Live
Migration.
Network
Interface
Cards
802.1Q tag-based VLANs a) 802.1Q tag-based VLANs can have a 10G
two NIC mode 1 802.3AD bond for server
management and virtual machines, or one two
NIC mode 1 802.3AD bond for server
management and a second mode 4 or 6
802.3AD bond for virtual machines.
Port-based VLANs b) Port-based VLANs can have up to four
dedicated 802.3AD bonds and VLANs for
server management and one or more 802.3AD
bonds and VLANs for virtual machines.
NAME Rate(bit/s) Rate(byte/s)
Gigabit Ethernet 1 Gbit/s 125 MB/s
10 Gigabit Ethernet 10 Gbit/s 1.25 GB/s
Infiniband DDR 16 Gbit/s 2 GB/
For network-interface high
availability 802.3AD bonds
are used for each pair of
network interfaces. Oracle
VM supports two NICs ports
per 802.3AD bond and a total
of five 802.3AD bonds per
Oracle VM Server.
Both 802.3AD NIC bonds,
port-based VLANs and/or
802.1Q tag-based VLANs are
supported and configured
post Oracle VM Server
installation with Oracle VM
Manager. Network
redundancy, i.e. 802.3AD
NIC bonding doubles the
number of required NICs.
Oracle VM uses a total of
five discrete networks; Server
Management, Cluster
Heartbeat, live Migration,
Storage and Virtual
Oracle VM for x86 Server Pool Design
Oracle VM uses the concept of a "server pool" to group together and centrally manage one
or more server pools with up to 32 Oracle VM servers. If more than one location exists,
Oracle VM server pools may be dispersed to different locations. Oracle VM Manager with
Oracle Enterprise Manager 12c provide a single point of administration for one or more
dispersed Oracle VM server pools.
Oracle VM server pools can accommodates organization-specific needs, i.e., Oracle
technology license management (hard and soft partitioning) , defense in depth, the principle
of least privilege, compartmentalization of information, security domains and different
applications and their performance, authentication, and security requirements.
Machines. All five networks
can be supported using one
mode 2 10G bond with
802.1Q tag-based VLANs (2
NICs) or using up to five
802.3AD bond (10 NICs).
Each Oracle VM server pool
should have a discrete
network for the Server
Management, Cluster
Heartbeat, live Migration,
Storage and Virtual
Machines. Isolating the
Server Management, Cluster
Heartbeat, live Migration and
Storage networks protect the
server pool from unexpected
server reboots by eliminating
OCSF2 heartbeat
interruptions that could cause
a pool member to loose
network connectivity, fence
from the pool and reboot.
Host Bus
Adapter
Cards
SAN Storage: 2 Host Bus Adapter Cards
(HBAs).
NAME Line-Rate Throughput MBps
4GFC 4.25 800
8GFC 8.5 1600
10GFC 10.52 2550
16GFC 14.025 3200
20GFC 21.04 5100
2 HBAs are used to eliminate
a single point of failure.
Figure 2 shows a high-level overview of how server pools can be used to implement
security domains, defense in depth, the principle of least privilege and
compartmentalization of information.
Decision Point Decision Justification
Pool Design Prior to implementing an Oracle
Cloud, it’s important that an
infrastructure assessment (IA) and
gap analysis (GA) be performed.
During the IA/GA, the architecture
of the solution will be matched to
the customer’s business needs.
Server pool design is a strategic,
architectural security decision.
Server pools can be used to
controle Oracle licensing costs
(hard and soft partitioning) and as
a way to implement security
domains, defense in depth, the
principle of least privilege and
compartmentalization of
information.
Oracle VM
Manager
Oracle VM Manager will be
installed in Production mode on a
dedicated physical server using an
external Oracle 11g Standard,
Enterprise or RAC database on a
dedicated physical or virtual
server.
The Oracle VM Manager Database
repository will not be shared with
other production or test databases
on the same server.
The Oracle Enterprise Manager
Agent and the Virtualization plug-
The Oracle VM Manager Database repository, WebLogic and Oracle VM Manager can be installed in an “unsupported” all-in-one configuration for evaluations (Demo Mode) or in a multi-tier architecture for production (Production Mode). A Production Oracle VM Manager installation should not be placed on a single server, nor should the Oracle VM Manager Database repository be shared with production or test databases on the same server. For production, the Oracle VM Manager Database repository as well as the WebLogic hosts should be on
in will be installed to enable Oracle
Enterprise Manager integration.
dedicated virtual or physical servers. If your Oracle VM environment starts out small, make sure to have a plan to scale out your Oracle VM Manager infrastructure. For the Oracle VM Manager Database repository, scaling out means moving from a single server Database to a multi node RAC cluster. An important consideration when scaling out an Oracle VM Manager environment is to determine if the underlying hardware where the Oracle VM Manager Database repository runs is capable to transition to RAC. If the hardware is not capable to transition to RAC, it is possible to move and/or export the Oracle VM Manager Database repository to a different system with more resources.
Oracle VM
Server Agent
Roles
Each Oracle VM server pool will
have one server pool master with a
VIP for failover. The Virtual IP
address is a unique IP address on
the Server Management network.
There are a total of three Oracle
VM agent roles; 1) the Server Pool
Master, 2) the Utility Server and 3)
the Virtual Machine Server. By
default each Oracle VM server in a
pool has all three of the agent roles
enabled.
The server pool "Virtual IP"
feature is a mandatory server pool
property and feature that detect the
loss of the server pool master and
automatically will failover the pool
master server role to the first pool
member that can lock the pool file
systsm.
Storage Back-end storage Each Oracle VM server pool uses
one dedicated OCFS2 12G mount
point for the server pool's OCFS2
cluster configurations (the pool file
system) and one or more shared
OCFS2 or NFS repositories to host
virtual machine configuration files
and images.
Front-end storage The virtual machine layer is where
the storage is presented to virtual
machines as either a flat file
(UUID.img), as RAW disks
(LUN), or as a combination of flat
An Oracle VM storage solution
consists of three distinct layers.
Each layer has its own unique
requirements, configurations,
dependencies and features. The
first layer is the storage array,
which is referred to as back-end
storage. Oracle VM supports Fibre
Channel and iSCSI SANs and NFS
back-end storage. The second layer
is the server layer consisting of the
Oracle VM server storage
configurations and the shared
Oracle Cluster File System 2
(OCFS2) or NFS virtual machine
files and RAW disks. file system. The third layer is the
guest front-end storage consisting
of multiple guest storage and
driver options.
RAW disks have the best
performance of the two
front-end storage storage options.
In most cases, RAW disks are the
best option for hight I/O workloads
like Oracle Databases.
Networks Each Oracle VM server pool will
have isolated Oracle VM
management and virtual machine
networks.
Oracle VM uses a total of five
discrete networks; Server
Management, Cluster Heartbeat,
live Migration, Storage and Virtual
Machines. All five networks can be
supported using one mode 2 10G
bond with 802.1Q tag-based
VLANs (2 NICs) or using up to
five 802.3AD bond (10 NICs).
Each Oracle VM server pool
should have a discrete network for
the Server Management, Cluster
Heartbeat, live Migration, Storage
and Virtual Machines. Isolating the
Server Management, Cluster
Heartbeat, live Migration and
Storage networks protect the server
pool from unexpected server
reboots by eliminating OCSF2
heartbeat interruptions that cause
pool members to fence from the
pool and reboot.
Note: The heartbeat traffic is TCP
on port 7777. Each Oracle VM
server in a pool must be able to
communicate to all of the pool
members over TCP on port 7777.
RAM The server pool must be designed
with excess memory capacity to
accommodate the memory
requirements of virtual machines
that could migrate or start on any
pool member.
Oracle VM server does not support
memory oversubscription, which
means that an Oracle VM server
cannot accept a DRS, Live
Migration or HA requests unless
the server has available RAM for
the virtual machines. Having
Oracle VM for x86 Disaster Recovery
An Oracle VM disaster recovery architecture includes the design and process to maintain
business continuity following a disastrous event affecting the availability of an
organization's primary site. Failover to a disaster recovery site is prompted by the results of
a disaster assessment. The failover process is the restoration of the primary site's services at
the disaster recovery site.
Note: Disaster recovery requirements are calculated using SLA, Recovery Time Objectives
(RTOs) and Recovery Point Objectives (RPOs) objectives. SLA, RPO and RTO objectives
and budget influence the disaster recovery architecture and design.
Oracle VM uses the concept of a server pool to group together and manage one or more
clustered Oracle VM servers. Once an Oracle VM server pool is created, the physical and
virtual resources are managed within the boundary of the server pool. Physical resources
include server hardware, networks, storage, infrastructure services (DNS, NTP, LDAP,
HTTP, etc..), operating system installation media and administrative accounts. The virtual
resources include virtual disks, virtual network interfaces, and virtual machine
configuration files. For example, an Oracle VM environment with multiple server pools
located in one or more sites could be managed from a single Oracle VM Manager instance
with each server pool's resources isolated to their respected server pool. An Oracle VM
server pool's resources from one site can be replicated and restored to another site for
disaster recovery.
Restoration of the primary site's services at a disaster recovery site requires a replica of the
primary site's physical and virtual resources at the disaster recovery site. A disaster
recovery site hosts a replica of the primary site's Oracle VM physical and virtual resources,
i.e. server hardware, networks, storage, infrastructure services, virtual disks, and virtual
machine configuration files. The failover process involves restoring the primary sites
Oracle VM server pools at the disaster recovery site, then systematically starting the virtual
machines and services.
Note: Oracle VM Servers are not backed up and restored at the DR site. The time required
to backup and restore an Oracle VM Server is significantly greater then a PXE boot
kickstart installation.
A disaster recovery site can be a warm failover site waiting idle to respond to a disastrous
occurrence, or part of a multi-site high availability design. A multi-site design uses excess
capacity with application high availability to mirror services across sites to handle the lose
excess RAM on each Oracle VM
server provides flexibility in terms
of adding new virtual machines to
the server pool, and to allow DRS,
Live Migration and HA to operate
within a server pool.
of one or more sites.
Figure 3 shows a warm failover site waiting idle to respond to a disastrous occurrence.
Figure 4 shows a warm failover site responding to a disastrous occurrence and running the
primary sites services.
Figure 5 shows a multi-site design with application high availability solutions to mirror
services across sites as well as excess capacity to handle the lose of one or more sites.
Virtual machines that are restored at a disaster recovery site expect the same networks,
storage, and infrastructure services as in the primary site. In the event that the disaster
recovery site has different networks, storage, and infrastructure services, the properties of
each virtual machines would need to be edited to use the new networks, storage and
infrastructure services before services can be restored.
The virtual machine operating systems are typically installed in virtual disks that are
actually flat files hosted on shared OCFS2 or NFS repositories. RAW disks such as ASM
Disks, Log and Archive Files, etcetera are presented to the virtual machines from the
Oracle VM Servers as local devices. Each virtual machine's virtual network interface
card(s) (vNIC) are connected to one or more discrete networks using Xen bridges that are
managed and presented to the virtual machines by the Oracle VM pool members. Virtual
disks and virtual network interface card(s) allocations are managed using Oracle VM
Manager and/or Oracle Enterprise Manager with the configurations saved in each virtual
machines vm.cfg file.
The virtual machine vm.cfg files, virtual disk images and RAW disks (ASM disks) can be
replicated between sites using storage array replication and/or mirroring solutions. Rsync is
an option if an array does not have replication and/or mirroring functionality.
As soon as the replicated storage repositories are available, the failover process for a warm
recovery site starts with the installation of Oracle VM Manager with the runInstall.sh --uuid
option using the primary sites Oracle VM Manager UUID. An Oracle VM Manager --uuid
installation allows Oracle VM Manager to use the primary site' replicated repositories and
virtual machines.
Tip: The Oracle VM Manager UUID is listed in the “.config ” file on the Oracle VM
Manager host in the /u01/app/oracle/ovm-manager-3/ directory as well as in each server
pool' .ovsrepo file in the pool file system.
The next example shows the content of the .config file with the UUID in bold.
# cat /u01/app/oracle/ovm-manager-3/.config
DBHOST=localhost
SID=orcl
LSNR=1521
APEX=None
OVSSCHEMA=ovs
WLSADMIN=weblogic
OVSADMIN=admin
COREPORT=54321
UUID=0004fb00000100009edfaa0f93184f44 BUILDID=3.0.3.126
The next example shows the content of the .ovsrepo file with the UUID in bold.
# cat .ovsrepo
OVS_REPO_UUID=0004fb0000030000554308a6997a6b2f
OVS_REPO_MGR_UUID=0004fb00000100009edfaa0f93184f44
OVS_REPO_VERSION=3.0
Decision Point Decision Justification
Disaster
Recovery
Design
Prior to implementing an Oracle
VM Disaster Recovery solution,
it’s important that an infrastructure
assessment (IA) and gap analysis
(GA) be performed. During the
IA/GA, the architecture of the
solution will be matched to the
customer’s SLA, Recovery Time
Objectives (RTOs) and Recovery
Point Objectives (RPOs)
objectives.
Implementing a Disaster Recovery
is a strategic decision. Disaster
recovery requirements are
calculated using SLA, Recovery
Time Objectives (RTOs) and
Recovery Point Objectives (RPOs)
objectives. SLA, RPO and RTO
objectives and budget influence the
disaster recovery architecture and
design.
Oracle VM
Manager
Oracle VM Manager will be
installed in Production mode using
the runInstall.sh --uuid option with
the primary site's Oracle VM
Manager UUID.
Oracle VM Manager will be hosted
on a dedicated physical server
using an external or local Oracle
11g Standard, Enterprise or RAC
database.
Once Oracle Enterprise Manager is
restored, the Oracle Enterprise
Manager Agent and Virtualization
plug-in will be installed to enable
Oracle Enterprise Manager
integration.
As soon as the replicated storage
repositories are available, the
failover process for a warm
recovery site starts with the
installation of Oracle VM Manager
with the runInstall.sh --uuid option
using the primary sites Oracle VM
Manager UUID. An Oracle VM
Manager --uuid installation allows
Oracle VM Manager to use the
primary site' replicated repositories
and virtual machines.
The Oracle VM Manager UUID is
listed in the “.config ” file on the
Oracle VM Manager host in the
/u01/app/oracle/ovm-manager-3/
directory as well as in each server
pool' .ovsrepo file in the pool file
system.
Oracle VM
Server Builds
Oracle VM Servers will be
installed using an automated build
process.
Oracle VM servers are installed
using an automated PXE boot
configuration to ensure that each
server has a consistent installation
configuration.
Oracle VM
Server Backups
Oracle VM Servers will not backed
up at the primary site and restored
at the DR site.
The time required to backup and
restore an Oracle VM Server is
significently greater then an
automated PXE boot kickstart
installation.
Oracle VM servers are installed
using an automated PXE boot
configuration to ensure that each
server has a consistent installation
configuration.
Storage A replica of the primary site's
Oracle VM pool file system and
virtual machine file system
repositories will be hosted at the
disaster recovery site.
As soon as the replicated storage
repositories are available, the
failover process for a warm
recovery site starts with the
installation of Oracle VM Manager
with the runInstall.sh --uuid option
using the primary sites Oracle VM
Manager UUID. An Oracle VM
Manager --uuid installation allows
Oracle VM Manager to use the
primary site' replicated repositories
and virtual machines.
Virtual machines that are restored
at a disaster recovery site expect
the same storage as in the primary
site. In the event that the disaster
recovery site has different storage
each virtual machine would need
to be recreated or edited to use the
new storage before services can be
restored.
Networks A replica of the primary site's
Oracle VM networks will be
maintained at the disaster recovery
site.
Virtual machines that are restored
at a disaster recovery site expect
the same networks as in the
primary site. In the event that the
disaster recovery site has different
networks each virtual machine
would need to be edited to use the
new networks before services can
be restored.
Infrastructure
Services
A replica of the primary site's
infrastructure services will be
maintained at the disaster recovery
site.
Virtual machines that are restored
at a disaster recovery site expect
the same infrastructure services as
in the primary site. In the event
that the disaster recovery site has
different infrastructure services,
Oracle Desktop Virtualization Security Solution at DISA Mission Partner Conference 2012
building an appliance? physical ? virtual? production quality? use Oracle Linux
understanding memory allocation in oracle vm / xen
Oracle VM Administration: Oracle VM Server for x86 course schedule
figuring out cpu topology in oracle vm
Collaborate12 Starts Today!
Oracle VM Administration: Oracle VM Server for x86 - new Training
More Oracle VM templates for PeopleSoft and Oracle Enteprise Manager
Oracle Ebusiness Suite 12.1.3 Oracle VM templates
Eight New Oracle Database Assemblies Ready to Run In Your Oracle VM Cloud with
Oracle Enterprise Manager 12c
each virtual machine operating
system would need to be edited to
use the new infrastructure services
before services can be restored.
Oracle VM Licensing, Support and
Packaging
Show a printer friendly, save as PDF version of the Oracle Cloud Cookbook
Distribution of the Oracle Cloud Cookbook or derivative of the work in any form for
commercial purposes is prohibited unless prior permission is obtained from the copyright
holder.
Author: Roddy Rodstein
Change Log
Revision Change Description Updated By Date
1.0 First Release Roddy Rodstein 09/17/11
1.1 Chapter updates Roddy Rodstein 05/10/12
Table of Contents Oracle VM Licensing and Support Options
The Oracle Unbreakable Linux Network
Oracle VM Packaging
Oracle Enterprise Manager 12c and Oracle VM
Oracle VM Licensing and Support Options Oracle VM is “not” a licensed Oracle technology product. There are no license fees for
Oracle VM. Oracle offers enterprise support for Oracle VM on third-party hardware as well
as bundled support with Sun hardware. Support for Oracle VM for third-party hardware is
purchased as an add-on component of Oracle’s enterprise support package. Support for
Oracle VM on Sun x64 hardware is bundled with hardware support as an add-on to the
Premier Support for Systems package.
Support for Oracle VM for third-party hardware is sold in two packages: Oracle VM
Premier Limited support for x64 servers with up to two sockets for $599.00 per server, per
year. Oracle VM Premier support for x64 servers with more than two sockets for $1,199.00
per server, per year. Both Oracle VM Premier support packages provide access to RPMs,
patches and updates from the Unbreakable Linux Network along with access to My Oracle
Support (MOS) to create and manage Oracle Support Service Requests (SRs). Support for
Oracle VM for third-party hardware “only” includes support for Oracle VM, operating
system support for Oracle Linux, Red Hat Enterprise Linux, Solaris 10 and 11 Express x86,
and Windows virtual machines must be purchased separately.
Note: Oracle offers free updates for Oracle Linux and a Network support package for
Linux with access exclusively to the Unbreakable Linux Network without My Oracle
Support. Oracle does not offer free updates or Network support for Oracle VM.
Premier Support for Systems costs 12% of the net Sun system purchase price and includes
support for the system hardware and firmware, as well as operating system support on the
Sun hardware for Solaris x86, Solaris 11 Express, Oracle Linux, and Oracle VM. The
operating system support with Premier Support for Systems covers an unlimited number of
virtual instances of Oracle Linux, Solaris 10 and 11 Express x86 hosted on Oracle VM on
the Sun hardware. Premier Support for Systems provides access to RPMs, patches and
updates from the Unbreakable Linux Network along with access to My Oracle Support
(MOS) to create and manage Oracle Support Service Requests (SRs).
The Oracle Unbreakable Linux Network The Oracle Unbreakable Linux Network is Oracle' cloud repository for Oracle VM, Oracle
Linux, Red Hat Enterprise Linux, Exadata and Exalogic RPMs, software patches, updates
and fixes. Access to the Oracle Unbreakable Linux Network is available to all levels of
Oracle VM, Oracle Linux and Sun Premier support customers. The Oracle Unbreakable
Linux Network has a simple dashboard to configure yum servers, manage customer service
identifiers (CSIs), and monitor the status of RPM repositories, software patches, updates
and fixes. The Oracle Unbreakable Linux Network dashboard is accessed with a web
browser and an associated Oracle Single Sign-on account. Existing “My Oracle Support
(MOS) Oracle Single Sign-on accounts” must be associated with the Oracle Unbreakable
Linux Network, in order to access the Unbreakable Linux Network.
To associate an existing Oracle Single Sign-on account, access the Oracle Unbreakable
Linux Network portal and click the Register link. To create a new Oracle Single Sign-on
account, access the Oracle Unbreakable Linux Network portal, click the Sign On button,
then from the Oracle Single Sign-on page, click the Sigh Up link.
Figure 1 shows the Oracle Unbreakable Linux Network dashboard.
The Oracle Unbreakable Linux Network and My Oracle Support, are entirely separate
systems, accessed by different URLs, and use different customer service identifiers (CSIs).
My Oracle Support is used to interface with Oracle’s enterprise support organization,
whereas the Oracle Unbreakable Linux Network is used to configure yum servers, manage
customer service identifiers (CSIs), monitor the status of RPM repositories, software
patches, updates and fixes. A valid customer service identifier (CSI) for Oracle VM or
Oracle Linux is required to access the RPM repositories, software patches, updates and
fixes at the Oracle Unbreakable Linux Network. The customer service identifiers for Oracle
VM and Oracle Linux are only valid for the Oracle Unbreakable Linux Network, not for
My Oracle Support.
Tip: The customer service identifiers for Oracle VM and Oracle Linux are not valid at the
My Oracle Support portal.
Oracle VM Packaging Oracle VM consists of a x64 server component, named Oracle VM Server and a manager
component, named Oracle VM Manager which is used to manage one or more clustered
servers. The Oracle VM Server Media Pack for Oracle VM Server and Oracle VM
Manager is available at the Oracle Linux and Oracle VM Cloud Portal. Access to the
Oracle Linux and Oracle VM Cloud Portal requires an Oracle.com user account and
password. The Oracle VM Media Packs are downloaded as a zip files that contain ISO
images. The ISO images can be burned to CD or mounted locally to install Oracle VM
Server and Oracle VM Manager. Oracle VM Server is distributed as Open Source software,
therefore the source code is also available along with the ISO image at the Oracle Linux
and Oracle VM Cloud Portal.
Oracle VM Server is installed on bare metal x64 hardware using the Oracle VM Media
Pack. Oracle VM Manager is a traditional Oracle application consisting of an Oracle
Database, one or more Oracle WebLogic servers hosting a J2EE web application with an
application development framework (ADF) browser based console. All of the Oracle VM
Manager components are supported exclusively on Oracle Linux 5U5 x64 or later. In the
context of Oracle VM Manager, the Oracle Database repository stores all of the
configuration data for an Oracle VM environment, including the data collected by the
Oracle VM Server Agents. WebLogic is the J2EE platform which hosts the Oracle VM
Manager application and the Core API. Oracle VM Manager provides a limited-use license
for a Standard Edition or Enterprise Edition Oracle Database and a limited-use license for
Standard Edition or Enterprise Edition WebLogic, as long as the Database and WebLogic
are “only” used for Oracle VM Manager.
Tip: Oracle Support Requests (SRs) for the limited-use license versions of the Oracle
Database and WebLogic should be created with the Oracle VM Manager Support identifier.
Oracle Enterprise Manager 12c and Oracle VM The Oracle VM product family; Oracle VM, Oracle VM Templates and Oracle Virtual
Assembly Builder can be managed from Oracle Enterprise Manager 12c Cloud Control
with a plug-in named the "Oracle Virtualization". The right to use the Oracle Virtualization
plug-in is bundled with all levels of Oracle VM support.
Managing Oracle VM Servers and virtual resources from the Oracle Enterprise Manager
12c Cloud Console requires an Oracle Linux host with Oracle VM Manager, an Oracle
Enterprise Manager 12c agent and the Oracle Virtualization plug-in.
Oracle Desktop Virtualization Security Solution at DISA Mission Partner Conference 2012
building an appliance? physical ? virtual? production quality? use Oracle Linux
understanding memory allocation in oracle vm / xen
Oracle VM Administration: Oracle VM Server for x86 course schedule
figuring out cpu topology in oracle vm
Collaborate12 Starts Today!
Oracle VM Administration: Oracle VM Server for x86 - new Training
More Oracle VM templates for PeopleSoft and Oracle Enteprise Manager
Oracle Ebusiness Suite 12.1.3 Oracle VM templates
Eight New Oracle Database Assemblies Ready to Run In Your Oracle VM Cloud with
Oracle Enterprise Manager 12c
Oracle VM for x86 Server Sizing Advisor
Version 2.0 - Copyright © 2012 Mokum Solutions, Inc. All rights reserved.
The Oracle VM for x86 Server Sizing Advisor offers Oracle VM 3.0 Server sizing
recommendations.
How to use Mokum Solutions, Inc.' Oracle VM Server Sizing Advisor.
This is the first page, where you enter the Oracle VM Server and virtual machine CPU,
RAM and storage requirements. Next, is a summary review page. The last page shows your
Oracle VM 3.0 server sizing results for an HA enabled pool with the ability to lose one
Oracle VM Server and still run all the virtual machines.
Each Oracle VM Server has: *2048
GB of
RAM
Each Oracle VM Server has: *160
CPU cores
Enter the Total Number of Virtual Machines: *
0
Enter the Total Number of Virtual Machine Virtual CPUs: *
0
Enter the Total Amount of RAM in GB for all of the Virtual Machines: *
0
Enter the Total Amount of Storage in GB for all of the Virtual Machines: *
12
Legal Notice: The Oracle VM for x86 Server Sizing Advisor tool is subject to change without notice and is provided as-is without
warranty of any kind, express or implied. Mokum Solutions, Inc. does not make any representations regarding the use,
validity, accuracy or reliability of the tool or the results of the use of the tool. The entire risk arising out of the use of this
tool remains solely with the customer. In no event shall Mokum Solutions, Inc. be liable for any direct, consequential,
incidental, special, punitive or other damages, even if Mokum Solutions, Inc. is negligent or has been advised of the
possibility of such damages, arising from use of the tool or the information provided herein.
Next Page >
Oracle VM Server CD-ROM Installation
Show a printer friendly, save as PDF version of the Oracle Cloud Cookbook
Distribution of the Oracle Cloud Cookbook or derivative of the work in any form for
commercial purposes is prohibited unless prior permission is obtained from the copyright
holder.
Author: Roddy Rodstein
Change Log
Revision Change Description Updated By Date
1.0 First Release Roddy Rodstein 09/10/11
1.1 Oracle VM Agent
Password Requirements Roddy Rodstein 09/15/11
1.2
Oracle VM Server
Installation Hangs
While Loading Xen.gz
Roddy Rodstein 11/10/11
1.3 Installation and VLANS Roddy Rodstein 04/13/12
1.4 Post Installation
Checklist Roddy Rodstein 04/17/12
1.5
Post Installation
Checklist - Disable C-
states
Roddy Rodstein 05/10/12
Table of Contents Oracle VM Server Installation Introduction
Oracle VM Installation Considerations
...Oracle VM Network Considerations
...Oracle VM Storage Considerations
Oracle VM Server Sizing
How to Download the Oracle VM Media Pack
Oracle VM CD-ROM Installation
Oracle VM Post Installation Checklist
How to Uninstall / Remove Oracle VM
Oracle VM Server Installation Hangs While Loading Xen.gz
Appendix
...Oracle VM Default Runlevel Settings for System Services
...Oracle VM install.log File
...Oracle VM install.log.syslog File
...Oracle VM anaconda-ks.cfg File
Oracle VM Server Installation Introduction Oracle VM Server can be installed on x86_64 hardware using a bootable CD-ROM or over
the network using a pre-boot execution environment (PXE). Both Oracle VM Server
installation methods, CD-ROM and PXE boot, require the Oracle VM Server Media Pack.
The Oracle VM Server Media Pack is available at the Oracle Linux and Oracle VM Cloud
Portal. Access to the Oracle Linux and Oracle VM Cloud Portal requires an Oracle.com
user account and password. The Oracle VM Server Media Pack is downloaded as a zip file
that contains the Oracle VM Server ISO image. The Oracle VM Server ISO image can be
burned to a bootable CD and used for a CD-ROM installation as well as staged on a boot
server for a PXE boot installation. Oracle VM is distributed as Open Source software,
therefore the source code is also available along with the ISO image at the Oracle Linux
and Oracle VM Cloud Portal.
Note: There is no Oracle VM 2.x to Oracle VM 3 upgrade path for Oracle VM Manager or
Oracle VM Server. Oracle VM 2.x virtual machines can be imported and used with Oracle
VM 3. Oracle VM 3 is supported only on x86_64 hardware.
Oracle VM Server can be installed from a CD-ROM, or from a hard drive, NFS server, FTP
server, or HTTP server. The difference between installing Oracle VM Server from a CD-
ROM, or from a hard drive, NFS server, FTP server, or HTTP server is how the server
boots and the location of the installation media. Contemporary servers can boot from a
bootable CD in a local CD-ROM drive, from a remote CD-ROM drive using a Lights out
Management (LOM) solution as well as over the network using a pre-boot execution
environment (PXE). Once the server boots, the installation program can install Oracle VM
Server from the CD-ROM, or from a hard drive, NFS server, FTP server, or HTTP server.
To install Oracle VM Server from a hard disk, an NFS share, FTP server or an HTTP
server, boot the server with the bootable CD and when presented with the Install Method
screen, enter the path to the installation media.
Tip: Occasionally CD-ROM installations using Lights out Management (LOM) solutions
terminate with file copy errors. If you encounter file copy errors with a Lights out
Management (LOM) installation, the workaround is to stage the Oracle VM Server media
files on the server’s hard disk, or on an NFS share, FTP server or an HTTP server on the
same network as the target server. Once the Oracle VM Server media files have been staged
on the server’s hard disk, an NFS share, FTP server or an HTTP server, boot the server with
the bootable CD and when presented with the Install Method screen, enter the path to the
installation media.
Oracle VM Installation Considerations Oracle VM Server is supported exclusively on x86_64 hardware with a 64-bit Intel or
AMD processor. Oracle VM 3.0 is not supported on x86 hardware with 32-bit processors.
Oracle recommends a dual core CPU or multiple CPUs with at least 1GB or 2GB of RAM.
Oracle’s minimum CPU and RAM recommendation for Oracle VM Server is a starting
point for running only a couple guests for a test environment.
Tip: A minimum of 1GB of RAM is required to boot an Oracle VM Server.
Oracle VM supports two unique virtualization modes, paravirtualization mode (PV mode)
and hardware virtualization mode (HVM mode). Oracle VM Servers can support both
paravirtualization mode and hardware virtualization mode simultaneously on a single
x86_64 server that has either Intel or AMD virtualization technologies. Intel and AMD
virtualization is a requirement only for hardware virtualization mode, not for
paravirtualization mode. Intel and AMD virtualization technologies are enabled and
managed using the system BIOS.
Paravirtualization mode requires the virtual machine operating system to run a Xen kernel
and Xen network and I/O drivers. Xen paravirtualized kernels are available for the Oracle
Linux and Red Hat Enterprise Linux operating systems. Paravirtualized virtual machines
are hypervisor aware and run without the additional overhead of hardware emulation.
Paravirtualization requires much less overhead for timers, interrupts, I/O traffic, and
context switches, allowing superior scalability under heavy loads, when compared to
hardware virtualization mode.
Unlike paravirtualization mode, which requires the virtual machine to run a Xen kernel,
hardware virtualization mode supports unmodified operating systems. Virtual machines that
run under hardware virtualization mode are called “hardware virtualized machines”
(HVM). Hardware virtualized machines are unaware that they have been virtualized and
think they are on physical hardware. To provide acceptable performance, hardware
virtualized machines should use paravirtualized network and I/O drivers. From Oracle
Linux and Red Hat Enterprise Linux 4.7 onwards, the stock kernels have provided
paravirtualized network and I/O drivers for hardware virtualized guests. From Solaris 10
10/09 onwards, the stock kernels have provided paravirtualized network and I/O drivers for
hardware virtualized machines. Windows does not have native paravirtualization support,
although Windows virtual machines can run as hardware virtualized machines using
Oracle's paravirtualized network and I/O drivers. Oracle has released paravirtualized
network and I/O drivers for the Windows operating system that can be freely downloaded
from the Oracle Linux and Oracle VM Cloud Portal.
Oracle VM Network Considerations A minimum of one Ethernet network interface (NIC) card is required to install Oracle VM,
although two or four NICs is strongly recommended. Both 802.3AD NIC bonding, port-
based VLANs and/or 802.1Q tag-based VLANs are supported and configured post Oracle
VM Server installation with Oracle VM Manager. Network redundancy, i.e. 802.3AD NIC
bonding, will double the number of required NICs. Oracle VM 3.0 supports two NICs ports
per network bond and a total of five network bonds per Oracle VM Server.
Table 1 shows the three supported 802.3AD NIC bonding modes.
Bond Name Bond
Mode Description Cisco Settings
Active
Backup
Mode 1
Active-
backup
policy
Default bond setting. Only
one slave in the bond is
active. A different slave
becomes active if, and only
if, the active slave fails.
LACP, and
Ethernet interface
mode (not bond
mode) are
recommended
Link
Aggregation
Mode 4
802.3ad
Creates aggregation groups
that share the same speed
and duplex settings. Utilizes
all slaves in the active
aggregator according to the
802.3ad specification.
LACP, and port
aggregation mode
are recommended
Load
balancing
Mode 6
balance-
alb
Includes balance-tlb plus
receive load balancing (rlb)
for IPV4 traffic. The receive
load balancing is achieved
by ARP negotiation.
LACP, and port
aggregation mode
are recommended
The exact number of network interfaces for an Oracle VM Server entirely depends on your
organization’s business requirements and network and storage infrastructure capabilities.
For example, an Oracle VM Server with two GigE interfaces, configured with one
802.3AD bond, using 802.1Q tag-based VLANs, with SAN storage, could support the most
demanding network and storage requirements, with only two network interfaces. By
contrast, an Oracle VM Server using 802.3AD bonds with port-based VLANs, with NFS or
iSCSI storage would require a 802.3AD bond with two interfaces per port-based VLAN, as
well as a two interfaces bond for the storage.
Oracle VM Server networking routes all virtual machine traffic through a Xen bridge. A
Xen bridge operates at layer 2 of the OSI model, effectively acting as a layer 2 (L2) switch
passing packets to the egress port, relying on the TCP protocol for rate and packet loss
control.
Table 2 shows the OSI model. Note that Xen bridges operate in layer 2.
Layer Description
7 Application Layer
6 Presentation Layer
5 Session Layer
4 Transport Layer
3 Network Layer
2 Data Link Layer
LLC sublayer
MAC sublayer
1 Physical Layer
Packets that arrive at the physical NIC are handled by dom0’s Ethernet driver and appear
on a Xen bridge. Xen bridges distribute packets like a layer-two switch for virtual machines
running on an Oracle VM Server. Xen bridges route guest packets based on the guest's
MAC address.
The Oracle VM 3.0 installation program allows the server' IP address to be assigned using
DHCP or as a static IP address. It is recommended to use a static IP address for Oracle VM
Servers to ensure that each server always receives the same IP address. Using DHCP
assigned IP addresses can result in unexpected IP address changes due to DHCP lease
expiry setting causing unexpected results.
The Oracle VM 3.0 installation program asks to select the Oracle VM Management
interface (NIC). The Oracle VM Management interface is used for, and should be dedicated
to, the Oracle VM Management traffic. Oracle VM Manager dispatches commands to each
Oracle VM Server pool master, which in turn dispatches commands to each Oracle VM
Server pool member using the Oracle VM Management interface. Additionally, each
Oracle VM Server pool member uses a network heartbeat over the management interface. If
any node in an Oracle VM Server pool fails to update/respond to its network heartbeat, the
node is fenced from the pool and promptly reboots, then all HA-enabled guests are restarted
on a live server in the Oracle VM Server pool. It is recommended to have a decided bonded
interface on an isolated network or vlan for the Oracle VM Management traffic.
Tip: The Oracle VM Management interface is selected during the Oracle VM server
installation and can be edited after the installation in the /etc/ovs-config file.
Oracle VM Storage Considerations The default behavior of the Oracle VM installation program is to install Oracle VM Server
on the server's local disk allocating only 3 GB of storage for the root “/” partition. The
remaining available storage will be free space. The free space can not be used for local
virtual machine storage. To support local virtual machine storage, a second disk must be
used.
Tip: Since Oracle VM Server only requires 3 GB of storage, consider procuring disk-less
hardware with a small flash storage module to reduce operating costs or consider the boot
from SAN installation option.
Oracle VM Server Sizing The minimum CPU, RAM, network and storage requirement for your Oracle VM hardware
depends entirely on your organizations business requirements, the Oracle VM Server pool
configurations along with the CPU, RAM and storage requirements of the virtual machines.
For example, Oracle recommends a dual core CPU or multiple CPUs with at least 1GB or
2GB of RAM. Oracle’s minimum CPU and RAM recommendation for Oracle VM Server
is a starting point for running only a couple guests for a test environment. To size Oracle
VM Server hardware and Oracle VM Server pools, it is necessary to know the resource
requirements of all of the virtual machines and organization specific high-availability and
disaster-recovery requirements.
Tip: Please use our Oracle VM for x86 Server Sizing Advisor to accurately calculate the
number of servers you will need for your environment.
The resource requirements of all of your virtual machines provides the data necessary to
calculate the CPU, RAM and storage requirements of the Oracle VM Servers hardware. For
example, a single Oracle VM Server supports up to 160 CPU cores or threads, 2TB of
memory and a maximum of 128 virtual disks or 128 virtual machines with “one” virtual
disk.
An Oracle VM Server with 2TB of memory and 160 CPU cores could allocate the
“majority” of 2TB of memory and “more” than 160 CPU cores to running virtual machines.
Oracle VM Server supports CPU oversubscription, which means that an Oracle VM Server
with 160 CPU cores could overallocate the total number of CPU cores to virtual machines.
Oracle VM Server does not support memory oversubscription, which means that an Oracle
VM Server with 2TB of memory cannot overallocate memory to virtual machines. By
default, each Oracle VM Server reserves 512MB of memory for the Oracle VM Server
(dom0). The average memory overhead for each running guest on an Oracle VM Server is
approximately 20MB plus 1% of each virtual machine' memory allocation. The remaining
physical memory can be allocated to virtual machines.
Avoid oversubscribing CPU-bound workloads such as Oracle Database workloads. CPU
oversubscription with CPU-bound workloads negatively affects performance and
availability. CPU oversubscription for non-CPU-bound workloads, such as Oracle Fusion
Middleware technologies, is recommended. It is common to oversubscribe one CPU cores
up to 3x with non-CPU-bound workloads. For example, each CPU core could be allocated
to 3 virtual CPUs for non-CPU-bound workloads, without performance penalties.
Note: Virtual machines cannot aggregate CPU and memory resources from more than one
Oracle VM Server. That is, a virtual machine consumes resources “only” from the Oracle
VM Server where the virtual machine is running.
An organization’s high-availability and disaster-recovery requirements provide the data
necessary to calculate the number of Oracle VM Servers, Oracle VM Server pools and
virtual machines. High availability is a strategy that allows organizations to meet service
level agreements (SLAs) by minimizing or eliminating planned and unplanned downtime.
SLAs specify the levels of availability. For example, mission critical applications might
have SLAs requiring operational continuity in the event of system failure. Conversely, a
non-mission critical application might have an SLA that allows several hours or days of
downtime.
Oracle offers a wide variety of high availability solutions for databases, middleware,
applications, operating systems and hardware that offer different levels of availability. For
example, Oracle Real Application Cluster (RAC) is Oracle’s database high availability
solutions offering operational continuity for Oracle Databases in the event of node failure.
Oracle DataGuard and Oracle ApplicationGuard are two other high availability solutions
that offer operational continuity in the event of node failure.
Oracle VM has two built-in high availability features; virtual machine HA, which is
referred to as “Oracle VM HA” and Live Migration. Oracle VM HA automatically restarts
virtual machines when an Oracle VM Server fails or restarts. Oracle VM HA minimizes
unplanned downtime by restarting virtual machines that have been taken off-line by an
Oracle VM Server failure. Live Migration is used to eliminate planned downtime by
migrating running virtual machines off one Oracle VM Server to another during a
maintenance event, i.e. for repairs or an upgrade. Both HA and Live migration require an
Oracle VM pool configuration with shared storage and a minimum of two Oracle VM
servers with sufficient memory to run all the virtual machines on “one” of the two Oracle
VM Servers.
An organization’s high availability and disaster recovery requirements will directly impact
the numbers of virtual machines, Oracle VM Servers and Oracle VM server pools required
to meet availability SLAs. For example, an SLA that states that mission critical databases
requires operational continuity would require a clustering solution like RAC, with a
minimum of two clustered nodes. Each RAC database would require a minimum of two
Oracle VM Servers. Each Oracle VM Server would host one of the two RAC nodes. The
former example illustrates how an SLA impacts the number of Oracle VM Servers and
virtual machines. If disaster recovery is a requirement, additional Oracle VM Servers,
Oracle VM Server pools and virtual machines will be deployed at the disaster recovery site.
How to Download the Oracle VM Media Pack The Oracle VM Media Pack is available at the Oracle Linux and Oracle VM Cloud Portal.
Access to the Oracle Linux and Oracle VM Cloud Portal requires an Oracle.com user
account and password to authenticate in to the Oracle Linux and Oracle VM Cloud Portal.
If you do not already have an Oracle.com user account, visit the Oracle Linux and Oracle
VM Cloud Portal, click the Sign In / Register link or button to create an Oracle.com
account.
Figure 1 shows the Oracle Linux and Oracle VM Cloud Portal.
From the Sign In page, enter your Oracle.com user name and password, then click the
Sign In button.
Figure 2 shows the Oracle Linux and Oracle VM Cloud Portal Sign In page.
Once authenticated, accept the registration/export regulations to access to the Oracle VM
and Oracle Linux Media.
Figure 3 shows the registration/export regulations form.
After completing the registration/export regulation form, you will be redirected to the
Media Pack Search page. From the Media Pack Search page, select Oracle VM from the
Select a Product Pack dropdown menu. Next, select x86 64-bit from the Platform
dropdown menu, then click the Go button to be taken to the Oracle VM Media Pack
download page.
Tip: If you do not see Oracle VM from the Select a Product Pack dropdown menu, you
are not in the Oracle Linux and Oracle VM section of the Cloud Portal. Click the Cloud
Portal link in the page header, then click the Oracle Linux/VM drop down menu to be
redirected to the Oracle Linux and Oracle VM section of the Cloud Portal.
Figure 4 shows the Media Pack Search page.
From the Oracle VM Media Pack page, click the Oracle VM 3.1.1 Media Pack for x86
64 (64 bit) radio button, then the Continue button, or click the Oracle VM 3.1.1 Media
Pack for x86 64 (64 bit) hyperlink to go to the download page.
Figure 5 shows the Oracle VM Media Pack page highlighting the Oracle VM 3.0.1
Media Pack for x86 64 (64 bit) hyperlink with the Continue button.
From the Oracle VM 3.1.1 Media Pack for x86 64 (64 bit) Media Pack download page,
click the Oracle VM Server 3.1.1 for x86 64 (64 bit) Download button to download the
Oracle VM Server 3.0.1 media pack.
Figure 6 shows the Oracle VM 3.0.1 Media Pack for x86 64 (64 bit) download page.
The Oracle VM Server media is delivered as a zip file. The zip file name corresponds to the
Part Number listed on the download page. Once the zip file is downloaded, use your
favorite zip utility to unzip the Oracle VM ISO file. Next, burn the ISO file to a bootable
CD or DVD to be able to install Oracle VM Server using a CD-ROM drive.
Oracle VM Server Installation Using a CD-ROM 1. Insert the Oracle VM Server media into the CD-ROM drive.
2. Boot the server with the Oracle VM Server media in the CD-ROM drive.
3. The Oracle VM Server Welcome screen is displayed, as shown in Figure 7.
Figure 7 shows the Oracle VM Server Welcome screen.
Oracle VM Server Welcome screen From Oracle VM Server Welcome screen press the Enter key to start the install program. If
the Enter key is not pressed for one minute, the install program will automatically start.
The CD Found screen On the CD Found screen, you can test the media for errors. To test the media, use the Tab
key to select the OK button and press Enter. Once the media test is completed, any errors
will be reported. To skip the media test and continue with the install, use the Tab key to
select the Skip button and press Enter to continue.
Figure 8 shows the CD Found screen.
The Keyboard Selection screen On the Keyboard Selection screen, use the Tab key to select the list of keyboard models.
Then use the UP and DOWN keys (↑ or ↓) to select the desired keyboard model. The
keyboard that is selected becomes the default keyboard for dom0. Next, use the Tab key to
select OK, and press Enter to continue.
Figure 9 shows the Keyboard Selection screen.
End User License Agreement screen On the User License Agreement screen, use the UP and DOWN keys (↑ or ↓) to read the
License Agreement. Next, use the Tab key to select the ACCEPT button to continue.
Figure 10 shows the End User License Agreement screen.
Warning screen If you see the Warning screen, use the Tab key to select the Yes button, then press Enter
to continue.
Figure 11 shows the Warning screen.
Partitioning Type screen The Partitioning Type screen offers the following four partitioning options:
Remove all partitions and create a new default partition layout
Remove all Linux partitions and create a new default partition layout
Use the free space on selected drives to create a new default partition layout
Create a custom partition layout
Tip: The default behavior of the Oracle VM installation program is to install Oracle VM
server on the server's local disk allocating only 3 GB of storage for the root “/” partition.
The remaining available storage will be free space. Since Oracle VM Server only requires 3
GB of storage, consider re-allocating the free space to the root “/” partition.
Use the Tab key to select the Remove all partitions and create a new default partition
layout option. Ensure that the appropriate drive is selected in the Which drive(s) do you
want to use for this installation section. Use the Tab key to select the OK button to
continue.
Figure 12 shows the Partitioning Type screen.
Warning screen Since we selected the Remove all partitions and create a new default partition layout
option, a Warning screen is displayed to confirm that we want to remove the partition(s),
including all of the data contained on any of the selected partitions. Use the Tab key to
select the YES button to continue.
Figure 13 shows the Warning screen.
Review Partition Layout screen On the Review Partition Layout screen, use the Tab key to select the YES button to
continue to the Partitioning screen.
Figure 14 shows the Review Partition Layout screen.
Partitioning screen On the Partitioning screen, use the Tab key to select the root “/” partition, then use the
Tab key to select the Edit button. Press Enter to continue.
Figure 15 shows the Partitioning screen.
Add Partition screen On the Add Partition screen, use the Tab key to select the Fill all available space option.
Next, press the Space bar to select the Fill all available space option. Use the Tab key to
select the OK button to proceed.
Figure 16 shows the Add Partition screen
Partitioning screen On the Partitioning screen, use the Tab key to select the OK button. Press Enter to
continue.
Figure 17 shows the Partitioning screen.
The Boot Loader Configuration screen On the Boot Loader Configuration screen, use the Tab key to select the Master Boot
Record (MBR) or the First sector of boot partition as the location to install the boot
loader. For this example, we have selected the Master Boot Record (MBR) option. Next,
use the Tab key to select the OK button and press Enter to continue.
Figure 18 shows the Boot Loader Configuration screen.
Oracle VM Server Management Interface screen On the Oracle VM Server Management Interface screen, use the Tab key to select the
network interface that will be dedicated for the server management. If your using 802.1Q
(VLANs), select the Add to VLAN tab to enter the VLAN ID of the server management
network. Once the network interface is selected, use the Tab key to select the OK button
and press Enter to continue.
Note: The management interface defaults to eth0, which is controlled in the /etc/ovs-config
file. The management interface as well as the VLAN can be changed after the installation.
Figure 19 shows the Oracle VM Server Management Interface screen.
The IPv4 Configuration for eth0 screen The IPv4 Configuration for eth0 screen offers the following three options:
Dynamic IP configuration (DHCP)
Manual address configuration
IP Address and Prefix (netmask)
If your Oracle VM server will use DHCP to assign its IP address, select the Dynamic IP
configuration (DHCP) option. To select the Dynamic IP configuration (DHCP) entry,
use the Tab key to highlight the Dynamic IP configuration (DHCP) entry, then use the
Space bar to select the Dynamic IP configuration (DHCP) entry. Use the Tab key to
select the OK button to continue.
If your Oracle VM server will use a static IP address, select the Manual address
configuration entry. To select the Manual address configuration entry use the Tab key
to highlight the Manual address configuration entry, then use the Space bar to select the
Manual address configuration entry. Next, use the Tab key to enter the IP Address and
Prefix (netmask). Use the Tab key to select the OK button to continue.
Figure 20 shows the IPv4 Configuration for eth0 screen.
The Miscellaneous Network Settings screen On the Miscellaneous Network Settings screen, use the Tab key to select the Gateway,
Primary DNS and optional Secondary DNS to enter the networking settings for your
environment. Use the Tab key to select the OK button and press Enter to continue.
Figure 21 shows the Miscellaneous Network Settings screen.
Hostname Configuration screen On the Hostname Configuration screen, select one of the following two options:
automatically via DHCP
manually
If the machine uses DHCP to assign its hostname, select the automatically via DHCP
option. Then, use the Tab key to select the OK button to continue.
To assign a hostname for your Oracle VM server, select the manually option and enter the
fully qualified domain name (FQDN) in the text box. Then, use the Tab key to select the
OK button to continue.
Figure 22 shows the Hostname Configuration screen.
Time Zone Selection screen On the Time Zone Selection screen select the System clock uses UTC option to use
Coordinated Universal Time (UTC), then use the Tab key and the UP or DOWN key (↑ or
↓) to select the time zone closest to your Oracle VM server’s physical location. Next, use
the Tab key to select the OK button and press Enter to continue.
Figure 23 shows the Time Zone Selection screen.
Oracle VM Agent password screen On the Oracle VM Agent password screen, enter the password for the Oracle VM agent in
the Password field. The Agent password should "not" contain special character, i.e. ;:#,!,
etc. In the Password (confirm) field, re-enter the password. Use the Tab key to select the
OK button and press Enter to continue. If the two passwords do not match, the installation
program will ask you to re-enter the passwords.
The Oracle VM agent password is used by Oracle VM Manager and the Oracle VM
Management Pack to dispatch commands and to retrieve pool-status data. The Oracle VM
agent password can be changed after the installation from dom0 by typing “ovs-agent-
passwd admin” for the “admin” account or “ovs-agent-passwd oracle” for the oracle
account.
Figure 24 shows the Oracle VM Agent password screen
Root Password screen On the Root Password screen, enter a password with at least six characters for the root
user in the Password field. In the Password (confirm) field, re-enter the password. Use the
Tab key to select the OK button and press Enter to continue. If the two passwords do not
match, the installation program will ask you to re-enter the passwords.
Figure 25 shows the Root Password screen.
Installation to begin screen On the Installation to begin screen, select OK and press Enter to continue.
Figure 26 shows the Installation to begin screen.
Complete screen When the Complete screen appears, remove the Oracle VM Server media from the CD-
ROM drive and press Enter to reboot the Oracle VM server.
Figure 27 shows the Complete screen.
Oracle VM Server login prompt screen On the Oracle VM Server login prompt screen, enter the root username and the
password to access the dom0 console.
Figure 28 shows the Oracle VM Server login prompt screen.
After installing Oracle VM, review and complete all of the necessary tasks on the post-
installation checklist before the server is added to a pool. Once the post-installation
checklist is completed, the Oracle VM Server can be added to a server pool and patched
using Oracle VM Manager or Oracle Enterprise Manager.
Oracle VM Post Installation Checklist After installing Oracle VM, review and complete all of the necessary tasks on the post-
installation checklist before the Oracle VM Server is added to a pool. These tasks involve
validating the Oracle VM Server's networking prerequisites and disabling CPU operating
states (C-states) in the BIOS.
1. The Oracle VM Server(s) must have consistent name resolution using DNS with both
forward and reverse lookups.
First, open the “/etc/resolv.conf” file by typing “vi /etc/resolv.conf” and validate that the
domain names(s) and two available DNS servers are listed. The next example shows one
doman name and two DNS servers listed in a resolve.conf file.
# vi /etc/resolve.conf
search <DOMAIN NAME>
nameserver <MY DNS SERVER1 IP ADDRESS>
nameserver <MY DNS SERVER2 IP ADDRESS>
From each Oracle VM server ping each DNS server listed in the resolv.conf file to ensure
network connectivity.
Next, validate the forward and reverse lookups for each Oracle VM Server and the Oracle
VM Manager host using the “getent hosts” command. For example, to validate server2's
forward lookup from server1 type “getent hosts server2” as shown in the next example.
# getent hosts server2
server2 has address 192.168.4.6
Next, to validate server2's reverse lookup from server1 type “getent hosts 192.168.4.6” as
shown in the next example.
# getent hosts 192.168.4.6
6.4.168.192.in-addr.arpa domain name pointer
server2
Note: Using hosts files without DNS is not advised and may produce unpredictable results.
2. The Oracle VM Server’s host name in the /etc/hosts file must be associated with the
server's public IP address. If an Oracle VM Server host name is associated with 127.0.0.1,
the cluster.conf file will be malformed and the cluster will not be operational.
The next example shows the proper syntax for an Oracle VM Server’s hosts file entry.
127.0.0.1 localhost.localdomain localhost
192.168.4.8 servername.com servername
The next example shows the improper syntax from an Oracle VM Server's hosts file entry.
127.0.0.1 servername.com servername localhost.localdomain localhost
192.168.4.8 servername.com servername
3. Cluster heartbeat network connectivity between each Oracle VM pool members must be
operational before creating an Oracle VM Server Pool.
Validate the cluster heartbeat network connectivity between each Oracle VM pool members
by typing "nc -zv <MY ORACLEVM SERVER> 7777". For example, if you have two
Oracle VM Servers named ovs1 and ovs2, from ovs1 type "nc -zv ovs2 7777". Typing "nc -
zv ovs2 7777" from ovs1 should return "succeeded!". If you receive a "failed: Connection
refused" message between any of the Oracle VM Servers, something (firewall, switch,
router, cable, etc..) is restricting communication between the hosts.
4. To reduce the risk of unexpected server reboots, C-states should be disabled in the BIOS
of each Oracle VM Server. If the BIOS has a settings named "Active Power Controller
mode", disable this option as well.
The Intel Nehalem CPU introduced a CPU power-saving feature called deep CPU operating
states (C-states). C-states allow an idle processor to turn off unused components to save
power. Some of the components that C-states turns off include the processor clock and
interrupts. Under certain conditions, when C-states turns off unused CPU components the
Oracle VM OCFS2 heartbeat mechanism will trigger an unexpected server reboot.
C-states server reboots log the following log entries in /var/log/messages.
May 4 16:45:40 <HOST NAME> syslogd 1.4.1: restart.
May 4 16:45:40 <HOST NAME> kernel: klogd 1.4.1, log source = /proc/kmsg started.
On alive servers in the pool, the following OCFS2 o2net connection error appear in
/var/log/messages.
server2 kernel: o2net: Connection to node "<HOST NAME>" (num 0) at
xx.xx.xxx.xxx:7777 has been idle for 60.5 secs, shutting it down.
To validate if C-states is enabled, as root log into the to an Oracle VM Server and type:
# xenpm get-cpuidle-states | grep total | uniq
total C-states : 2
If the "total C-states" is greater than 2, then C-states is enabled in the server's BIOS. How to Uninstall / Remove Oracle VM There is not an option to “uninstall” Oracle VM, although there are many ways to remove
Oracle VM from a system. The method you select to remove Oracle VM from a system
depends on your organizations security requirements. For example, if corporate policy
states that the data on the hard drive needs to be securely deleted, formatting or re-
partitioning the hard drive will not completely remove the data from the disks. To
completely wipe Oracle VM from disk, boot the system using data destruction application,
like Darik's Boot and Nuke (DBAN), and wipe the disk(s). If the data on the hard drive
does not need to be securely deleted, you could a) delete all the files on the disks b) format
or re-partition the hard drives c) uninstall the bootloader and d) install another operating
system on top of the existing one.
List 1 shows several of the options to remove Oracle Linux from a system.
Boot the system using data destruction application like Darik's Boot and Nuke
(DBAN) and wipe all of the disks.
Delete all the files on the disks, i.e. type “rm -rf /” as root.
Format or delete the partitions.
Uninstall the bootloader.
Install another operating system on top of Oracle Linux or Red Hat Enterprise
Linux.
Oracle VM Server Installation Hangs While Loading Xen.gz The installation of Oracle VM Server 3.0.x hangs while loading xen.gz on servers with
Intelligent Platform Management Interface (IPMI) cards or with console redirection
enabled in the BIOS.
The next example shows a hung boot screen.
COM32 Multiboot loader v0.1. Copyright (C) 2005 Tim Deegan
Kernel: xen.gz
Loading: xen.gz
IPMI cards or enabled console redirection change the default Component Object Model
(COM) port inside the BIOS from COM A (COM 1) to COM B (COM 2). When the
Component Object Model (COM) port becomes COM B (COM 2) the installation program
hangs as described above.
Resolution 1. Access the system BIOS, open the Advanced menu, and validate the Console Redirection
settings. Either DISABLE Console Redirection or change it to COM1.
2. Exit and Save the BIOS changes.
3. Restart the Oracle VM Server installation.
Appendix Oracle VM Default Runlevel Settings for System Services
Oracle VM install.log File
Oracle VM install.log.syslog File
Oracle VM anaconda-ks.cfg File
Oracle VM Default Runlevel Settings for System Services The next example show the Oracle VM 3.0 default runlevel settings for system services.
anacron 0:off 1:off 2:on 3:on 4:on 5:on 6:off
dnsmasq 0:off 1:off 2:off 3:off 4:off 5:off 6:off
ebtables 0:off 1:off 2:off 3:off 4:off 5:off 6:off
haldaemon 0:off 1:off 2:off 3:on 4:on 5:on 6:off
ip6tables 0:off 1:off 2:off 3:off 4:off 5:off 6:off
ipmievd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
iptables 0:off 1:off 2:off 3:off 4:off 5:off 6:off
irqbalance 0:off 1:off 2:on 3:on 4:on 5:on 6:off
iscsi 0:off 1:off 2:off 3:on 4:on 5:on 6:off
iscsid 0:off 1:off 2:off 3:on 4:on 5:on 6:off
kudzu 0:off 1:off 2:off 3:on 4:on 5:on 6:off
lvm2-monitor 0:off 1:on 2:on 3:on 4:on 5:on 6:off
mcstrans 0:off 1:off 2:on 3:on 4:on 5:on 6:off
messagebus 0:off 1:off 2:off 3:on 4:on 5:on 6:off
mpp 0:off 1:off 2:off 3:on 4:off 5:on 6:off
multipathd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
netconsole 0:off 1:off 2:off 3:off 4:off 5:off 6:off
netfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off
netplugd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
network 0:off 1:off 2:on 3:on 4:on 5:on 6:off
nfs 0:off 1:off 2:off 3:off 4:off 5:off 6:off
nfslock 0:off 1:off 2:off 3:on 4:on 5:on 6:off
ntpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
o2cb 0:off 1:off 2:on 3:on 4:on 5:on 6:off
ocfs2 0:off 1:off 2:on 3:on 4:on 5:on 6:off
ovm-consoled 0:off 1:off 2:off 3:on 4:on 5:on 6:off
ovmwatch 0:off 1:off 2:off 3:on 4:on 5:on 6:off
ovs-agent 0:off 1:off 2:on 3:on 4:on 5:on 6:off
ovs-devmon 0:off 1:off 2:off 3:on 4:on 5:on 6:off
portmap 0:off 1:off 2:off 3:on 4:on 5:on 6:off
qlayer-monitor 0:off 1:off 2:on 3:on 4:on 5:on 6:off
rawdevices 0:off 1:off 2:off 3:on 4:on 5:on 6:off
rdisc 0:off 1:off 2:off 3:off 4:off 5:off 6:off
restorecond 0:off 1:off 2:on 3:on 4:on 5:on 6:off
rpcgssd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
rpcidmapd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
rpcsvcgssd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
saslauthd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
sshd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
syslog 0:off 1:off 2:on 3:on 4:on 5:on 6:off
xend 0:off 1:off 2:off 3:on 4:on 5:on 6:off
xendomains 0:off 1:off 2:off 3:on 4:on 5:on 6:off
Oracle VM install.log File The next exmaple shows a Oracle VM install.log file.
Installing libgcc-4.1.2-48.el5.x86_64
warning: libgcc-4.1.2-48.el5: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Installing setup-2.5.58-7.100.3.el5.noarch
Installing filesystem-2.4.0-3.0.1.el5.x86_64
Installing basesystem-8.0-5.1.1.0.1.noarch
Installing cracklib-dicts-2.8.9-3.3.x86_64
Installing 1:termcap-5.5-1.20060701.1.noarch
Installing tzdata-2010k-1.el5.x86_64
Installing glibc-common-2.5-49.el5_5.4.x86_64
Installing glibc-2.5-49.el5_5.4.x86_64
Installing chkconfig-1.3.30.2-2.el5.x86_64
Installing zlib-1.2.3-3.x86_64
Installing glib2-2.12.3-4.el5_3.1.x86_64
Installing 3:mktemp-1.5-23.2.2.x86_64
Installing audit-libs-1.7.17-3.el5.x86_64
Installing popt-1.10.2.3-20.el5_5.1.x86_64
Installing bzip2-libs-1.0.3-6.el5_5.x86_64
Installing expat-1.95.8-8.3.el5_5.3.x86_64
Installing elfutils-libelf-0.137-3.el5.x86_64
Installing libcap-1.10-26.x86_64
Installing libstdc++-4.1.2-48.el5.x86_64
Installing tcp_wrappers-7.6-40.7.el5.x86_64
Installing libtermcap-2.0.8-46.1.x86_64
Installing bash-3.2-24.el5.x86_64
Installing info-4.8-14.el5.x86_64
Installing libsepol-1.15.2-3.el5.x86_64
Installing ncurses-5.5-24.20060715.x86_64
Installing readline-5.1-3.el5.x86_64
Installing nspr-4.8.6-1.el5.x86_64
Installing nss-3.12.7-2.0.1.el5.x86_64
Installing sed-4.1.5-5.fc6.x86_64
Installing gawk-3.1.5-14.el5.x86_64
Installing sqlite-3.3.6-5.x86_64
Installing iptables-1.4.7-3.100.3.el5.x86_64
Installing libattr-2.4.32-1.1.x86_64
Installing libacl-2.2.39-6.el5.x86_64
Installing diffutils-2.8.1-15.2.3.el5.x86_64
Installing libidn-0.6.5-1.1.x86_64
Installing libxml2-2.6.26-2.1.2.8.0.2.x86_64
Installing db4-4.3.29-10.el5_5.2.x86_64
Installing libsysfs-2.0.0-6.x86_64
Installing gdbm-1.8.0-26.2.1.x86_64
Installing libgpg-error-1.4-2.x86_64
Installing cyrus-sasl-lib-2.1.22-5.el5_4.3.x86_64
Installing lsscsi-0.23-2.el5.x86_64
Installing slang-2.0.6-4.el5.x86_64
Installing libgcrypt-1.4.4-5.el5.x86_64
Installing bridge-utils-1.1-2.x86_64
Installing iproute-2.6.32-10.100.2.el5.x86_64
Installing iptables-ipv6-1.4.7-3.100.3.el5.x86_64
Installing hmaccalc-0.9.6-3.el5.x86_64
Installing procps-3.2.7-16.el5.x86_64
Installing less-436-2.el5.x86_64
Installing gzip-1.3.5-11.0.1.el5_4.1.x86_64
Installing binutils-2.17.50.0.6-14.el5.x86_64
Installing cpio-2.6-23.el5_4.1.x86_64
Installing iputils-20020927-46.el5.x86_64
Installing ovs-utils-1.0-34.x86_64
Installing udhcp-0.9.8-3.x86_64
Installing bzip2-1.0.3-6.el5_5.x86_64
Installing pcre-6.6-2.el5_1.7.x86_64
Installing grep-2.5.1-55.el5.x86_64
Installing libusb-0.1.12-5.1.x86_64
Installing tftp-0.49-2.0.1.x86_64
Installing libevent-1.4.13-1.x86_64
Installing 1:dmidecode-2.10-3.el5.x86_64
Installing sgpio-1.2.0_10-2.0.1.el5.x86_64
Installing sg3_utils-libs-1.25-4.el5.x86_64
Installing sg3_utils-1.25-4.el5.x86_64
Installing libaio-0.3.106-5.x86_64
Installing device-mapper-multipath-libs-0.4.9-23.100.20.el5.x86_64
Installing libyaml-0.1.3-1.el5.x86_64
Installing mingetty-1.07-5.2.2.x86_64
Installing libvolume_id-095-14.21.100.1.el5_5.1.x86_64
Installing ethtool-6-4.el5.x86_64
Installing keyutils-libs-1.2-1.el5.x86_64
Installing crontabs-1.10-8.noarch
Installing kernel-ovs-firmware-2.6.32.21-38.x86_64
Installing enterprise-linux-ovs-5-0.472.x86_64
Installing nash-5.1.19.6-61.100.1.el5_5.5.x86_64
Installing anacron-2.3-45.0.1.el5.x86_64
Installing sysfsutils-2.0.0-6.x86_64
Installing ed-0.2-39.el5_2.x86_64
Installing unzip-6.0-3.100.1.el5.x86_64
Installing liblockfile-1.06.1-3.x86_64
Installing 1:mcelog-1.0pre3_20101112-0.6.100.1.el5.x86_64
Installing nc-1.84-10.fc6.x86_64
Installing file-4.17-15.el5_3.1.x86_64
Installing reflink-0.1.0-1.x86_64
Installing hdparm-6.6-2.x86_64
Installing vconfig-1.9-3.x86_64
Installing libdrm-2.0.2-1.1.x86_64
Installing setserial-2.17-19.2.2.x86_64
Installing numactl-0.9.8-11.100.1.el5.x86_64
Installing grub-0.97-13.5.100.2.x86_64
Installing ovs-release-3.0-0.472.x86_64
Installing vbox-img-1.0-1.x86_64
Installing rootfiles-8.1-1.1.1.noarch
Installing ql2xxx-firmware-1.01.01-0.1.el5.noarch
Installing libselinux-1.33.4-5.5.el5.x86_64
Installing e2fsprogs-libs-1.39-23.el5.x86_64
Installing device-mapper-1.02.39-1.el5_5.2.x86_64
Installing 2:shadow-utils-4.0.17-15.el5.x86_64
Installing kpartx-0.4.9-23.100.20.el5.x86_64
Installing e2fsprogs-1.39-23.el5.x86_64
Installing 1:findutils-4.2.27-6.el5.x86_64
Installing coreutils-5.97-23.100.1.el5_4.5.x86_64
Installing krb5-libs-1.6.1-36.el5_5.5.x86_64
Installing openssl-0.9.8e-12.el5_4.6.x86_64
Installing python-2.4.3-27.100.1.el5_5.6.x86_64
Installing xen-tools-4.0.0-79.el5.x86_64
Installing python-simplejson-2.0.7-2.el5.x86_64
Installing openldap-2.3.43-12.el5_5.2.x86_64
Installing newt-0.52.2-15.el5.x86_64
Installing libxml2-python-2.6.26-2.1.2.8.0.2.x86_64
Installing python-zope-interface-3.0.1-11.100.1.el5.x86_64
Installing libgssapi-0.10-2.x86_64
Installing net-tools-1.60-81.el5.x86_64
Installing rpm-libs-4.4.2.3-20.el5_5.1.x86_64
Installing 2:tar-1.15.1-30.el5.x86_64
Installing libselinux-utils-1.33.4-5.5.el5.x86_64
Installing nfs-utils-lib-1.0.8-7.6.el5.x86_64
Installing audit-libs-python-1.7.17-3.el5.x86_64
Installing cracklib-2.8.9-3.3.x86_64
Installing pam-0.99.6.2-6.el5_4.1.x86_64
Installing libuser-0.54.7-2.1.el5_4.1.x86_64
Installing passwd-0.73-1.x86_64
Installing usermode-1.88-3.el5.2.x86_64
Installing SysVinit-2.86-15.el5.x86_64
Installing python-crypto-2.0-1.rf.x86_64
Installing multiprocessing-2.6.1.1-1.x86_64
Installing python-elementtree-1.2.6-5.x86_64
Installing yum-metadata-parser-1.1.2-3.el5.x86_64
Installing libselinux-python-1.33.4-5.5.el5.x86_64
Installing libsemanage-1.9.1-4.4.el5.x86_64
Installing PyYAML-3.09-5.el5.x86_64
Installing python-sqlite-1.1.7-1.2.1.x86_64
Installing pyOpenSSL-0.6-1.p24.7.2.2.x86_64
Installing python-twisted-core-8.2.0-3.3.el5.x86_64
Installing curl-7.15.5-9.el5.x86_64
Installing python-pycurl-7.15.5.1-4.100.1.el5.x86_64
Installing stunnel-4.15-2.100.1.el5.x86_64
Installing socat-1.7.1.3-1.el5.x86_64
Installing device-mapper-multipath-0.4.9-23.100.20.el5.x86_64
warning: /etc/multipath.conf saved as /etc/multipath.conf.rpmorig
Installing MAKEDEV-3.23-1.2.x86_64
Installing udev-095-14.21.100.1.el5_5.1.x86_64
Installing util-linux-2.13-0.52.100.1.el5_4.1.x86_64
Installing which-2.16-7.x86_64
Installing cryptsetup-luks-1.0.3-5.el5.x86_64
Installing device-mapper-event-1.02.39-1.el5_5.2.x86_64
Installing lvm2-2.02.56-8.el5_5.6.x86_64
Installing logrotate-3.7.4-9.x86_64
Installing rpm-4.4.2.3-20.el5_5.1.x86_64
Installing rpm-python-4.4.2.3-20.el5_5.1.x86_64
Installing psmisc-22.2-7.x86_64
Installing prelink-0.4.0-2.el5.x86_64
Installing authconfig-5.3.21-6.el5.x86_64
Installing system-config-securitylevel-tui-1.6.29.1-5.100.2.el5.x86_64
Installing pygobject2-2.12.1-5.el5.x86_64
Installing python-numeric-23.7-2.2.2.x86_64
Installing iscsi-initiator-utils-6.2.0.872-6.0.2.el5.x86_64
Installing python-hashlib-20081119-4.el5.x86_64
Installing PyXML-0.8.4-4.el5_4.2.x86_64
Installing wget-1.11.4-2.el5_4.1.x86_64
Installing OpenIPMI-tools-2.0.16-7.el5.x86_64
Installing rdac-mpp-tools-1.0.1-5.x86_64
Installing parted-1.8.1-27.el5.x86_64
Installing lsof-4.78-3.x86_64
Installing 2:vim-minimal-7.0.109-6.el5.x86_64
Installing osc-plugin-manager-1.2.8-8.el5.noarch
Installing python-urlgrabber-3.9.1-9.100.1.el5.noarch
Installing pykickstart-0.43.8-1.100.5.el5.noarch
Installing redhat-lsb-3.1-12.3.100.1.EL.x86_64
Installing open-ovf-1.1-1.0.43.el5.noarch
Installing ovs-agent-3.0-568.x86_64
warning: /etc/ovs-agent/passwdfile created as /etc/ovs-agent/passwdfile.rpmnew
Generating RSA private key, 1024 bit long modulus
..............................................++++++
............................++++++
e is 65537 (0x10001)
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [GB]:State or Province Name (full name)
[Berkshire]:Locality Name (eg, city) [Newbury]:Organization Name (eg, company) [My
Company Ltd]:Organizational Unit Name (eg, section) []:Common Name (eg, your name
or your server's hostname) []:Email Address []:
Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:An optional company name []:Signature ok
subject=/CN=localhost.localdomain
Getting Private key
Installing python-iniparse-0.2.3-4.el5.noarch
Installing ovmwatch-1.0-15.x86_64
Installing devmon-1.0-20.x86_64
Installing yum-3.2.22-26.el5.noarch
Installing p2v-util-0.10-8.x86_64
Installing osc-plugin-manager-devel-1.2.8-8.el5.noarch
Installing osc-oracle-generic-1.1.0-39.el5.noarch
Installing xen-4.0.0-79.el5.x86_64
Installing bfa-firmware-2.3.2.0-1.el5.noarch
Installing ovm-consoled-0.1-1.noarch
Installing monitor-1.0.1-23.noarch
Installing python-paramiko-1.7.2-1.rf.noarch
Installing sos-1.7-9.49.0.2.el5.noarch
Installing osc-sccaller-0.4.0-12.el5.noarch
Installing xen-devel-4.0.0-79.el5.x86_64
Installing xenpvboot-0.1-5.el5.noarch
Installing pypxeboot-0.0.2-11.noarch
Installing ovs-python-uuid-1.2.6-6.el5.noarch
Installing ovs-storage-utils-1.0.0-20.x86_64
Installing pexpect-2.3-3.el5.noarch
Installing ntp-4.2.2p1-9.el5_4.1.x86_64
Installing initscripts-8.45.30-2.100.14.el5.x86_64
Installing fipscheck-lib-1.2.0-1.el5.x86_64
Installing dbus-libs-1.1.2-14.el5.x86_64
Installing openssh-4.3p2-41.el5_5.1.x86_64
Installing dbus-1.1.2-14.el5.x86_64
Installing dmraid-1.0.0.rc13-63.el5.x86_64
Installing dbus-glib-0.73-10.el5_5.x86_64
Installing kbd-1.12-21.el5.x86_64
Installing mcstrans-0.2.11-3.el5.x86_64
Installing portmap-4.0-65.2.2.1.x86_64
Installing fipscheck-1.2.0-1.el5.x86_64
Installing dmraid-events-1.0.0.rc13-63.el5.x86_64
Installing openssh-clients-4.3p2-41.el5_5.1.x86_64
Installing openssh-server-4.3p2-41.el5_5.1.x86_64
Installing sysklogd-1.4.1-46.100.2.el5.x86_64
Installing 2:irqbalance-0.55-15.el5.x86_64
Installing cyrus-sasl-2.1.22-5.el5_4.3.x86_64
Installing policycoreutils-1.33.12-14.8.el5.x86_64
Installing 12:dhclient-3.0.5-23.el5_5.2.x86_64
Installing mkinitrd-5.1.19.6-61.100.1.el5_5.5.x86_64
Installing module-init-tools-3.3-0.pre3.1.60.el5.x86_64
Installing ocfs2-tools-1.8.0-9.el5.x86_64
Installing hwdata-0.213.22-1.el5.noarch
Installing pciutils-2.2.3-8.el5.x86_64
Installing 1:nfs-utils-1.0.9-47.el5_5.x86_64
Installing osc-oracle-ocfs2-0.1.0-31.el5.noarch
Installing kernel-ovs-2.6.32.21-38.x86_64
Installing hal-0.5.8.1-59.el5.x86_64
Installing kudzu-1.2.57.1.24-1.x86_64
Installing pm-utils-0.99.3-10.el5.x86_64
install.log.syslog
anaconda-ks.cfg
Oracle VM install.log.syslog File The next exmaple shows an Oracle VM install.log.syslog file.
<86>Aug 28 10:14:04 groupadd[584]: new group: name=audio, GID=63
<86>Aug 28 10:14:22 groupadd[605]: new group: name=floppy, GID=19
<86>Aug 28 10:14:22 useradd[609]: new group: name=vcsa, GID=69
<86>Aug 28 10:14:22 useradd[609]: new user: name=vcsa, UID=69, GID=69, home=/dev,
shell=/sbin/nologin
<86>Aug 28 10:14:48 groupadd[677]: new group: name=ntp, GID=38
<86>Aug 28 10:14:51 useradd[681]: new user: name=ntp, UID=38, GID=38,
home=/etc/ntp, shell=/sbin/nologin
<86>Aug 28 10:14:53 groupadd[689]: new group: name=utmp, GID=22
<86>Aug 28 10:14:57 useradd[704]: new group: name=dbus, GID=81
<86>Aug 28 10:14:57 useradd[704]: new user: name=dbus, UID=81, GID=81, home=/,
shell=/sbin/nologin
<86>Aug 28 10:15:02 groupadd[717]: new group: name=rpc, GID=32
<86>Aug 28 10:15:03 useradd[721]: new user: name=rpc, UID=32, GID=32, home=/,
shell=/sbin/nologin
<86>Aug 28 10:15:05 useradd[728]: new group: name=sshd, GID=74
<86>Aug 28 10:15:05 useradd[728]: new user: name=sshd, UID=74, GID=74,
home=/var/empty/sshd, shell=/sbin/nologin
<86>Aug 28 10:15:31 useradd[767]: new group: name=rpcuser, GID=29
<86>Aug 28 10:15:31 useradd[767]: new user: name=rpcuser, UID=29, GID=29,
home=/var/lib/nfs, shell=/sbin/nologin
<86>Aug 28 10:15:32 useradd[775]: new group: name=nfsnobody, GID=4294967294
<86>Aug 28 10:15:32 useradd[775]: new user: name=nfsnobody, UID=4294967294,
GID=4294967294, home=/var/lib/nfs, shell=/sbin/nologin
<86>Aug 28 10:15:59 useradd[2472]: new group: name=haldaemon, GID=68
<86>Aug 28 10:15:59 useradd[2472]: new user: name=haldaemon, UID=68, GID=68,
home=/, shell=/sbin/nologin
Oracle VM anaconda-ks.cfg File
The next exmaple shows an Oracle VM an anaconda-ks.cfg file.
# Kickstart file automatically generated by anaconda.
install
eula Accepted
url --url http://192.168.8.12/repo/ovs/3.0/iso
lang en_US.UTF-8
keyboard us
network --device eth0 --bootproto static --ip 192.168.8.8 --netmask 255.255.255.0 --
gateway 192.168.8.254 --nameserver 192.168.8.11 --hostname ovs3.0
ovsagent --iscrypted xxxxxxxxxxxxxxxxxxxxxxxxxxxxx=
ovsmgmntif eth0
rootpw --iscrypted xxxxxxxxxxxxxxxxxxxxxxxxxxxxx=
firewall --enabled --port=21:tcp --port=22:tcp --port=53:udp --port=53:tcp --port=80:tcp --
port=2049:tcp --port=5900-7999:tcp --port=8002:tcp --port=8003:tcp --port=8899:tcp --
port=7777:tcp
authconfig --enableshadow --enablemd5
selinux --disabled
timezone --utc America/Los_Angeles
bootloader --location=mbr --dom0_mem=514 --driveorder=sda
# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
#clearpart --all --drives=sda
#part /boot --fstype ext3 --size=100 --ondisk=sda
#part / --fstype ext3 --size=3072 --ondisk=sda
#part swap --size=1024 --ondisk=sda
%packages
@base
@core
@ovs-virtualization
Oracle Desktop Virtualization Security Solution at DISA Mission Partner Conference 2012
building an appliance? physical ? virtual? production quality? use Oracle Linux
understanding memory allocation in oracle vm / xen
Oracle VM Administration: Oracle VM Server for x86 course schedule
figuring out cpu topology in oracle vm
Collaborate12 Starts Today!
Oracle VM Administration: Oracle VM Server for x86 - new Training
More Oracle VM templates for PeopleSoft and Oracle Enteprise Manager
Oracle Ebusiness Suite 12.1.3 Oracle VM templates
Eight New Oracle Database Assemblies Ready to Run In Your Oracle VM Cloud with
Oracle Enterprise Manager 12c
Oracle VM Manager 3.0 Installation
Show a printer friendly, save as PDF version of the Oracle Cloud Cookbook
Distribution of the Oracle Cloud Cookbook or derivative of the work in any form for
commercial purposes is prohibited unless prior permission is obtained from the copyright
holder.
Author: Roddy Rodstein
Change Log
Revision Change Description Updated By Date
1.0 First Release Roddy Rodstein 09/19/11
1.1 Oracle VM Manager Backup Roddy Rodstein 10/15/11
1.2
Oracle Enterprise Manager 12c
Agent Installation & Oracle VM
Manager 3.0
Roddy Rodstein 10/18/11
1.3 Oracle VM 3.0.3 Updates Roddy Rodstein 01/12/12
1.4 Introduction Updates & New
Images Roddy Rodstein 04/02/12
1.5
Oracle VM Manager 3.0 Inter
Component Communication and
Data Exchange Updates
Roddy Rodstein 04/03/12
1.6 Chapter Updates Roddy Rodstein 04/06/12
Table of Contents Oracle VM Manager Introduction
Oracle VM Manager Installation Options
Oracle VM Manager Design Considerations
Oracle VM Manager Inter Component Communication and Data Exchange
Oracle VM Manager Firewall Requirements
How to Download the Oracle VM Manager Installation Media
How to Mount the Oracle VM Manager Installer Media
Oracle VM Manager Installation Passwords Requirements
Oracle VM Manager Prerequisite Packages
Oracle VM Manager Host Oracle XE User Requirements
The Oracle VM Manager Host /u01 Installation Directory Requirements
The Oracle VM Manager Host /etc/hosts Requirements
How to Run the Oracle VM Manager Environment Configuration Script
Oracle VM Manager Demo Installation
Oracle VM Manager Production Installation
How to Uninstall Oracle VM Manager
How to Backup Oracle VM Manager
...How to Backup Oracle VM Manager Configuration File
...How to Backup the Oracle VM Manager Database Repository
......How to Backup an Oracle 11g Standard or Enterprise Edition Database Repository
......How to Backup an Oracle 11g Express Database Repository Backup
Oracle VM Manager Introduction Oracle VM Manager 3.x is a traditional Oracle application consisting of an Oracle
Database, one Oracle WebLogic servers hosting a J2EE web application with an
application development framework (ADF) browser based console. All of the Oracle VM
Manager components are supported exclusively on Oracle Linux 5U5 x86_64 bit or later
and Oracle Linux 6+. In the context of Oracle VM Manager, the Oracle Database
repository stores the configuration data for an Oracle VM environment, including the data
collected by the Oracle VM Server Agents. WebLogic is the J2EE platform which hosts the
Oracle VM Manager application and the Core API. Oracle VM Manager provides a
limited-use license for a Standard Edition or Enterprise Edition Oracle Database and a
limited-use license for Standard Edition or Enterprise Edition WebLogic, as long as they
are “only” used for Oracle VM Manager.
Tip: Oracle Support Requests (SRs) for the limited-use license versions of Standard
Edition or Enterprise Edition Oracle Database and WebLogic should be created with the
Oracle VM customer support identifier (CSI).
The Oracle Database repository is an Oracle 11g Database that stores all of the
configuration data for an Oracle VM environment, including the data collected by the
Oracle VM Server Agents. The Oracle VM Manager application and the Core API are
deployed on a WebLogic server in the Oracle Middleware home. The Oracle Middleware
home is the parent directory of the Oracle WebLogic Server home. Administrative
operations made in the Oracle VM Manager console are dispatched to each Oracle VM
server pool' master agent. The Oracle VM Manager console can be accessed using Firefox
3.5 and above, Safari 5.0 and above, Chrome 1.0 and above and Internet Explorer 9.0 and
above.
Figure 1 shows Oracle VM Manager and its interaction with Oracle VM Server Pools.
As shown in Figure 1, an Oracle VM 3.0 deployment, has the following components:
List 1 explains each of the components from an Oracle VM 3.0 deployment.
List 1
Oracle VM Manager Console: The Oracle VM Manager console is used to configure and
manage the entire Oracle VM environment. The Oracle VM Manager console can be
accessed with the the default “admin” account via http or https using Firefox 3.5 and above,
Safari 5.0 and above, Chrome 1.0 and above and Internet Explorer 9.0 and above. The next
example shows the http and https URLs for the Oracle VM Manager 3.0 console:
http://<ORACLE VM MANAGER 3.0 HOST>:7001/ovm/console/faces/login.jspx
https://<ORACLE VM MANAGER 3.0 HOST>:7002/ovm/console/faces/login.jspx
Note: The WebLogic Server Administration console is available at:
https://<ORACLE VM MANAGER 3.0 HOST>:7001/console/login/LoginForm.jsp
Oracle VM Manager Host: The Oracle Linux 5 or 6 x64 virtual or physical hosts on
which Oracle VM Manager 3.x is installed. The Oracle VM Manager host runs the
administrative console and Core. Administrative operations made in the Oracle VM
Manager console are dispatched using XML RPC calls from Oracle VM Manager to each
Oracle VM server pool' master agent.
Oracle Management Agent and the Virtualization plug-in: The Oracle VM product
family; Oracle VM Servers, Oracle VM Manager, Oracle VM Templates and Oracle
Virtual Assembly Builder can be managed with Oracle VM Manager and Oracle Enterprise
Manager Cloud Control. To be able to manage the Oracle VM product family with
Enterprise Manager Cloud Control, the Oracle VM Manager host must have the Oracle
Management Agent (OMA) along with the Virtualization plug-in installed, as well as be a
monitored target in Oracle Enterprise Manager 12c.
Note: The Virtualization plug-in is supported exclusively with a Production Oracle VM
Manager installation. The Demo installation is not supported by the Virtualization plug-in.
Oracle VM Server(s): Oracle VM Server is installed bare metal on x64 hardware with
Intel or AMD CPUs. An Oracle VM Server installation “only” requires 3GB of local
storage using an on-board SSD or flash module, i.e. no traditional hard drives required.
Oracle VM Servers must belong to an Oracle VM server pool. Each server pool can have
up to 32 Oracle VM Servers. There are a total of three Oracle VM Server pools show in
Figure 1.
Oracle VM Agent: Oracle VM Manager facilitates centralized management of server
pools and their resources using an agent-based architecture. The Oracle VM Agent is an
Oracle VM Server default component. There are a total of three Oracle VM Agent roles; 1)
the Server Pool Master, 2) the Utility Server and 3) the Virtual Machine Server. Oracle VM
Manager dispatches commands using XML RPC to each server pool master agent, which,
in turn, dispatches commands to other pool members over a dedicated management
interfac. The Oracle VM Agents are shown as blue dots within each Oracle VM Server in
Figure 1.
Server Pools: Oracle VM Manager uses the concept of a server pool to group together and
manage one or more clustered Oracle VM Servers. A Server Pool defines the management
boundaries of its Oracle VM Servers, virtual machines, and server pool resources. Once a
server pool is created, resources such as storage, networks, Oracle VM Servers, virtual
machines, operating system installation ISO files, Oracle VM templates can be configured
and managed within the context of the server pool.
Storage: Oracle VM uses two unique types of storage repositories supported on Fiber
Channel SAN, iSCSI and/or NFS. The first type of storage repository is the pool file system
that is used to host a server pool's cluster configurations. There can only be one pool file
system repository per server pool. The other type of storage repository is the virtual
machine file system (VMFS) used to host virtual machine configuration files, images, ISO
files, templates and assemblies.
Berkeley DB: Each Oracle VM Server has a local Berkeley DB that hosts persistent cluster
configurations such as mount points and OCFS2 locks. Each Oracle VM server pool also
has a shared Berkeley DB located in the pool file system that is managed by the Oracle VM
agent. The Berkeley DBs are shown as red dots within each Oracle VM Server in Figure 1.
Oracle VM Manager Installation Options The Oracle VM Manager application installer provides the option to select a Demo or
Production installation. A Demo installation is an all-in-one installation with Oracle 11g
Express Database, WebLogic 11g 10.3.5.0, and the Oracle VM Manager applications. A
Production installation installs WebLogic 11g 10.3.5.0, and the Oracle VM Manager
applications using an existing local or remote Oracle 11g Standard or Enterprise Edition
database. A Demo installation is “unsupported” by Oracle Enterprise Manager and Oracle
support due to the use of the Oracle 11g Express Database, which is a free unsupported
version of the Oracle Database.
Tip: An Oracle VM Manager Demo installation is intended “only” for evaluations, not for
production.
Oracle VM Manager Design Considerations The Oracle VM Manager Database repository, WebLogic and Oracle VM Manager can be
installed in an “unsupported” all-in-one configuration for evaluations (Demo Mode) or in a
multi-tier architecture for production (Production Mode). A Production Oracle VM
Manager installation should not be placed on a single server, nor should the Oracle VM
Manager Database repository be shared with production or test databases on the same
server. For production, the Oracle VM Manager Database repository as well as the
WebLogic hosts should be on dedicated virtual or physical servers. If your Oracle VM
environment starts out small, make sure to have a plan to scale out your Oracle VM
Manager infrastructure.
For the Oracle VM Manager Database repository, scaling out means moving from a single
server Database to a multi node RAC cluster. An important consideration when scaling out
an Oracle VM Manager environment is to determine if the underlying hardware where the
Oracle VM Manager Database repository runs is capable to transition to RAC. If the
hardware is not capable to transition to RAC, it is possible to move and/or export the
Oracle VM Manager Database repository to a different system with more resources.
Oracle VM Manager Inter Component Communication and Data Exchange The Oracle VM Manager console, the Oracle Database repository and the WebLogic server
running Oracle VM Manager can be on different hosts throughout your enterprise.
Understanding Oracle VM Manager intra component communication and data exchange
will help configure firewalls in order to allow Oracle VM Manager to operate in your
enterprise. During the Oracle VM Manager installation, the default communication ports
for each component will be selected and assigned. If the default ports are modified be sure
to use the new port assignments when you configure your firewalls.
Table 1 shows the default ports used by Oracle VM Manager.
Port Usage
7001 HTTP access to the Oracle VM Manager console.
7002 HTTPS access to the Oracle VM Manager console.
Note: By default Oracle VM Manager uses a self-signed SSL certificate.
54321 The Oracle VM Manager Core API management port.
1521 The Oracle Database listener.
8080 Oracle Database 11g Express Edition (XE) Only: HTTP access to the
Oracle Database XE console.
15901 Oracle VM uses the Remote Access Service java applet to proxy all virtual
machine VNC console access from the Oracle VM Manager host to the
“ovs-consoled” service on the Oracle VM servers.
Figure 2 shows the Oracle VM Manager intra component communication and data
exchange.
Oracle VM Manager Firewall Requirements The default firewall used by an Oracle Linux 5U5 and above Oracle VM Manager host is
iptables. In order to use Oracle VM Manager, the Core API and the Oracle Management
Agent with iptables enabled, it is necessary to open tcp ports 7001, 7002, 54321, 15901 and
3872. To open the necessary ports in iptables, edit the /etc/sysconfig/iptables file, or run the
environment configuration script (createOracle.sh) located in the Oracle VM Manager
installation media.
Note: The environment configuration script (createOracle.sh) does not open port 3872 used
for the OEM Agent.
To open the necessary ports in iptables, as root edit the /etc/sysconfig/iptables add the bold
iptables rules as shown in the following example.
# vi /etc/sysconfig/iptables
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state NEW -m tcp -p tcp --dport 7001 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 7002 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 15901 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 54321 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 3872 -j ACCEPT
COMMIT
:wq!
Next, restart iptables, by typing the following command:
# /etc/init.d/iptables restart
If you experience connection challenges, a troubleshooting first step is to “temporarily”
disable iptables.
To disable iptables, as root, type the following command:
# /etc/init.d/iptables stop && chkconfig iptables off
To re-enable iptables, as root, type the following command:
# chkconfig iptables on && /etc/init.d/iptables start
How to Download the Oracle VM Manager Installation Media The Oracle VM Media Pack is available at the Oracle Linux and Oracle VM Cloud Portal.
Access to the Oracle Linux and Oracle VM Cloud Portal requires an Oracle.com user
account and password to authenticate in to the Oracle Linux and Oracle VM Cloud Portal.
If you do not already have an Oracle.com user account, visit the Oracle Linux and Oracle
VM Cloud Portal, click the Sign In / Register link or button to create an Oracle.com
account.
Figure 3 shows the Oracle Linux and Oracle VM Cloud Portal.
From the Sign In page, enter your Oracle.com user name and password, then click the Sign
In button.
Figure 4 shows the Oracle Linux and Oracle VM Cloud Portal Sign In page.
Once authenticated, accept the registration/export regulations to access to the Oracle VM
and Oracle Linux Media.
Figure 5 shows the registration/export regulations form.
After completing the registration/export regulation form, you will be redirected to the
Media Pack Search page. From the Media Pack Search page, select Oracle VM from the
Select a Product Pack dropdown menu. Next, select x86 64-bit from the Platform dropdown
menu, then click the Go button to be taken to the Oracle VM Media Pack download page.
Tip: If you do not see Oracle VM from the Select a Product Pack dropdown menu, you are
not in the Oracle Linux and Oracle VM section of the Cloud Portal. Click the Cloud Portal
link in the page header, then click the Oracle Linux/VM drop down menu to be redirected
to the Oracle Linux and Oracle VM section of the Cloud Portal.
Figure 6 shows the Media Pack Search page.
From the Oracle VM Media Pack page, click the desired Oracle VM Manager 3.0.x radio
button, then the Continue button, or click the Oracle VM Manager 3.x hyperlink to go
directly to the download page.
Figure 7 shows the Oracle VM Media Pack page highlighting the Oracle VM Manager
3.0.1 hyperlink with the Continue button.
From the Oracle VM Manager 3.x Media Pack download page, click the Oracle VM Server
3..x for x86 64 (64 bit) Download button to download the Oracle VM Server 3.0.x media
pack.
The Oracle VM Manager media is delivered as a zip file. The zip file name corresponds to
the Part Number listed on the download page. The zip file contains the Oracle VM Manager
ISO file. The Oracle VM Manager ISO file contains: Oracle Database 11g Express,
WebLogic 11g 10.3.5.0, and two J2EE applications, the Core API, and the Oracle
Application Development Framework 11g Faces user interface. The two J2EE applications
are deployed in to the WebLogic server in the Oracle Middleware home. The Oracle
Middleware home is the parent directory of the Oracle WebLogic Server home.
Once the zip file is downloaded, use your favorite zip utility to unzip the Oracle VM
Manager ISO file. Next, burn the ISO file to DVD to be able to install Oracle VM Manager
with a CD-ROM drive, or copy the ISO file to the Oracle VM Manager host, mount the
ISO file and then perform the installation.
How to Mount the Oracle VM Manager Installer Media In order to run the Oracle VM Manager installer, the installation media must be made
available to the Oracle VM Manager host. The Oracle VM Manager installation media can
be burned to DVD for a CD-ROM installation, or the ISO file can be copied to Oracle VM
Manager host and mounted locally to start the install program.
The next example shows how to mount the Oracle VM Manager ISO file and start the
installer program.
1. Download the Oracle VM Manager ISO file from the Oracle Linux and Oracle
VM Cloud Portal.
2. Use your favorite zip utility to unzip the Oracle VM Manager ISO file.
3. Copy the Oracle VM Manager ISO file to a directory on the Oracle VM Manager
host, i.e. to the /home/oracle directory. Note: The directory must be writable by
the oracle user account.
4. Log in to the Oracle VM Manager host as root.
5. Create a directory to mount the ISO file, i.e. mkdir -p /home/oracle/mount-point.
6. Mount the ISO file by typing “mount -o loop OracleVM-Manager-
<VERSION>.iso /home/oracle/mount-point”
7. Change to the directory where the ISO file is mounted, i.e. “cd
/home/oracle/mount-point.
8. Run the installer script as root, by typing “./runInstaller.sh”
Oracle VM Manager Installation Passwords Requirements During the Oracle VM Manager installation, the installation program asks for the following
passwords:
If the Oracle 11g XE Database is selected, the Oracle XE SYS and SYSTEM account
passwords must be selected. The Oracle XE SYS and SYSTEM account passwords cannot
contain special characters
The Oracle VM Manager OVS Database schema password:
Oracle 11g XE Database The password cannot contain special characters
Passwords must be between 8 and 16 characters in length.
Passwords must contain at least 1 lower case and 1 upper case letter.
Passwords must contain at least 1 numeric value or special character.
Oracle 11g SE and EE Database The password must be a minimum of 8 characters in length
The password cannot be the same as the username
The password cannot be the same length as the username
The password cannot be the username spelled backwards
The password cannot be the same as the server name or the server name with digits from 1
to 100 appended
Simple passwords will be rejected
The password must include 1 digit and 1 alpha character
The Oracle 11g SE and EE Database SYSTEM password The password must be a minimum of 8 characters in length.
The password cannot be the same as the username.
The password cannot be the same length as the username.
The password cannot be the username spelled backwards.
The password cannot be the same as the server name or the server name with digits from 1
to 100 appended
Simple passwords will be rejected
The password must include one digit and one alpha character
The Oracle WebLogic admin account password The password must be between 8 and 16 characters in length
The password must have at least 1 lower case and 1 upper case letter
The password must have at least 1 numeric value or special character
Tip: The WebLogic Server Administration Console is available after the installation at:
http://<ORACLE VM MANAGER 3.0 HOST>:7001/console/login/LoginForm.jsp
The Oracle VM Manager admin account The password must be between 8 and 16 characters in length
The password must have at least 1 lower case and 1 upper case letter
The password must have at least 1 numeric value or special character
As shown in the list above, each service has a slightly different password policy. Select
your passwords carefully to avoid installation errors and post installation challenges.
Tip: The alphanumeric character set consists of the numbers 0 to 9 and letters A to Z.
Oracle VM Manager Prerequisite Packages Oracle VM Manager 3.x has a total of two operating system prerequisite packages, libaio
0.3.104 or above, which is only necessary with the Oracle XE Database and unzip 3.3.2.4.2
or above. To validate if an Oracle VM Manager host has libaio and unzip, as root, type “
rpm -qa libaio unzip” as shown in the next example.
# rpm -qa libaio unzip
unzip-5.52-3.el5
libaio-0.3.106-5
libaio-0.3.106-5
The above examples shows that the Oracle VM Manager host has both of the prerequisite
packages.
If your Oracle VM Manager host is missing one or both of the prerequisite packages, both
RPM packages are available at the Oracle Unbreakable Linux Network.
If your Oracle VM Manager host is registered with Oracle Unbreakable Linux Network, as
root, type “up2date -i libaio” for Oracle Linux 5U5 and above systems, or “yum install
libaio” for Oracle Linux 6 and above systems. To install the libaio package from the Oracle
Linux DVD or ISO file, as root, mount the DVD or ISO file, cd to the directory with the
libaio.rpm, and type “rpm -ivh libaio-version.rpm” or to upgrade libaio, type “rpm -Uvh
libaio-version.rpm”.
To install unzip from the Oracle Unbreakable Linux Network, as root, type “up2date -i
unzip” for Oracle Linux 5U5 and above systems, or “yum install unzip” for Oracle Linux 6
and above systems.
The next example shows how to mount the Oracle Linux ISO file.
1. Download the Oracle Linux ISO file from the Oracle Linux and Oracle VM
Cloud Portal.
2. Log in to the Oracle VM Manager host as root.
3. Copy the Oracle Linux ISO file to a directory on the Oracle VM Manager host,
i.e. to the /tmp/mount-point directory.
4. Create a directory to mount the ISO file, i.e. mkdir -p /tmp/mount-point.
5. Mount the ISO file by typing “mount -o loop <FILE NAME>.iso /tmp/mount-
point”
6. Change to the directory where the ISO file is mounted, i.e. “cd /tmp/mount-point.
Oracle VM Manager Host Oracle XE User Requirements When using the Oracle XE Database as the Oracle VM Manager Database repository, it is
necessary to have a user account named “oracle” which is a member of a group named dba.
If the oracle user and/or the dba group does not not exist, as root, type the following
commands, or run the environment configuration script (createOracle.sh ) located in the
Oracle VM Manager installation media.
# groupadd dba
# useradd -g dba oracle
# passwd oracle
If the oracle user already exists, add the oracle account to the dba group by typing the
following command:
# usermod -g dba oracle
The oracle user account must have several security limits configured as well as hard nofiles
and soft nofiles minimum set to at least 8192. To add the setting, as root edit the
/etc/security/limits.conf file and include the following entries, or run the environment
configuration script (createOracle.sh ) located in the Oracle VM Manager installation
media.
oracle hard nofile 8192
oracle soft nofile 8192
oracle soft nproc 4096
oracle hard nproc 4096
oracle soft core unlimited
oracle hard core unlimited
The Oracle VM Manager Host /u01 Installation Directory Requirements Oracle VM Manager installer expects a directory named /u01 with a minimum of 2.4 GB of
available space. Oracle VM Manager and the Core will be installed into the /u01/app/oracle
directory. The “oracle” user account, in the “dba” group, must be the owner of the
“/u01/app/oracle” directory.
Tip: The /u01 installation directory follows the Optimal Flexible Architecture (OFA)
standard. The OFA Optimal Flexible Architecture is a set of recommendations for naming
files and folders when installing and implementing an Oracle technology products.
The “/u01/app/oracle” directory can be created and prepared using the configuration script
(createOracle.sh ) located in the Oracle VM Manager installation media, or as root by
typing the following commands.
# mkdir -p /u01/app/oracle
# chown oracle:dba /u01/app/oracle
The Oracle VM Manager Host /etc/hosts Requirements All Oracle technology products, including Oracle VM Manager 3.0, rely on a properly
formatted /etc/hosts file which allows the host to be pingable, with long and short host
names. The host name in the /etc/hosts file must be associated with the server's public IP
address.
The next example shows the proper syntax from a /etc/hosts file. Note that the localhost
entries are one one line, and the IP address with the long and short names are on the next
line.
127.0.0.1 localhost.localdomain localhost
192.168.4.8 servername.com servername
The next example shows an improperly formatted /etc/hosts file. Note that the long and
short names are on the same line as the localhost entries.
127.0.0.1 servername.com servername localhost.localdomain localhost
192.168.4.8 servername.com servername
The /etc/hosts file can be edited by the root user bu typing “vi /etc/hosts”, as shown in the
next example.
# vi
127.0.0.1 localhost.localdomain localhost
192.168.4.8 servername.com servername
:wq!
How to Run the Oracle VM Manager Environment Configuration Script The createOracle.sh is on the Oracle VM Manager 3.0 ISO file and can be used to prepare
the oracle user account, the /u01 directory and iptables for an Oracle VM Manager 3.0
installation. The createOracle.sh script must be run as root. The createOracle.sh will
perform the following tasks:
Creates the dba group
Creates the oracle user and adds the oracle user to the dba group
Creates the /u01 directory
Configures the /etc/security/limits.conf file
Opens the required port in iptables by editing the /etc/sysconfig/iptables file
To run the createOracle.sh script, as root, mount the Oracle VM Manager installer ISO file,
change to the mount point and type “./createOracle.sh”.
The next example shows how to mount the Oracle VM Manager 3.0 ISO file and run the
createOracle.sh script.
1. Download the Oracle VM Manager ISO file from the Oracle Linux and Oracle
VM Cloud Portal.
2. Use your favorite zip utility to unzip the Oracle VM Manager 3.0 ISO file.
3. Copy the Oracle VM Manager ISO file to a directory on the Oracle VM Manager
host, i.e. to the /home/oracle directory.
4. Log in to the Oracle VM Manager 3.0 host as root.
5. Create a directory to mount the ISO file, i.e. mkdir -p /home/oracle/mount-point.
6. Mount the ISO file by typing “mount -o loop OracleVM-Manager-
<VERSION>.iso /home/oracle/mount-point”
7. Change to the directory where the ISO file is mounted, i.e. “cd
/home/oracle/mount-point.
8. Type “./createOracle.sh” to run the createOracle.sh script.
Oracle VM Manager Demo Installation The next example shows how to perform a “Demo” Oracle VM Manager installation.
Please note that a Demo installation is “not” supported by Oracle Enterprise Manager or
Oracle support due to the use of the Oracle 11g XE Database. The Oracle 11g XE Database
is a free unsupported release of the Oracle Database.
Tip: Minimum swap space requirement for Oracle Database XE is 2 GB or twice the size
of RAM, whichever is lesser.
1. Download the Oracle VM Manager ISO file from the Oracle Linux and Oracle
VM Cloud Portal.
2. Use your favorite zip utility to unzip the Oracle VM Manager ISO file.
3. Copy the Oracle VM Manager ISO file to a directory on the Oracle VM Manager
host, i.e. to the /home/oracle directory. Note: The directory where the ISO file is
mounted must be writable by the oracle user account.
4. Log in to the Oracle VM Manager host as root.
5. Check that host name in the /etc/hosts file is associated with the server's public IP
address.
6. Create a directory to mount the ISO file, i.e. mkdir -p /home/oracle/mount-point.
7. Mount the ISO file by typing “mount -o loop OracleVM-Manager-
<VERSION>.iso /home/oracle/mount-point”
8. Change to the directory where the ISO file is mounted, i.e. “cd
/home/oracle/mount-point.
9. Run the installer script as root, by typing “./runInstaller.sh”
Note: Remember, do no select passwords containing special character (!;:# etc.)
[root@ovm /home/oracle/mount-point]# ./runInstaller.sh
Oracle VM Manager Release 3.0.3 Installer
Oracle VM Manager Installer log file:
/tmp/ovmm-installer.selfextract_VP3882/install-2011-09-05-171403.log
Please select an installation type:
1: Demo
2: Production
3: Uninstall
4: Help
Select Number (1-4): 1
Starting demo installation ...
The Demo installation type will use an XE database. The usage of XE is for *demo
purposes only* and is not supported for production. Please *do not* plan to start with XE
and migrate to a supported version of the database as this may not be possible. For
production environments or any long term usage please use the "Production" option with an
SE or EE database.
1: Continue
2: Abort
Select Number (1-2): 1
Verifying installation prerequisites ...
One password is used for all users created and used during the installation.
Enter a password for all logins used during the installation:
Enter a password for all logins used during the installation (confirm):
Verifying configuration ...
Start installing the configured components:
1: Continue
2: Abort
Select Number (1-2): 1
Step 1 of 9 : Database ...
Installing Database ...
Retrieving Oracle Database 11g XE ...
Installing Oracle Database 11g XE ...
Configuring Oracle Database 11g XE ...
Step 2 of 9 : Java ...
Installing Java ...
Step 3 of 9 : Database Schema ...
Creating database schema 'ovs' ...
Step 4 of 9 : WebLogic ...
Retrieving Oracle WebLogic Server 11g ...
Installing Oracle WebLogic Server 11g ...
Step 5 of 9 : ADF ...
Retrieving Oracle Application Development Framework (ADF) ...
Unzipping Oracle ADF ...
Installing Oracle ADF ...
Step 6 of 9 : Oracle VM ...
Retrieving Oracle VM Manager Application ...
Extracting Oracle VM Manager Application ...
Installing Oracle VM Manager Core ...
Step 7 of 9 : Domain creation ...
Creating Oracle WebLogic Server domain ...
Starting Oracle WebLogic Server 11g ...
Configuring data source 'OVMDS' ...
Creating Oracle VM Manager user 'admin' ...
Step 8 of 9 : Deploy ...
Deploying Oracle VM Manager Core container ...
Deploying Oracle VM Manager UI Console ...
Deploying Oracle VM Manager Help ...
Enabling HTTPS ...
Granting ovm-admin role to user 'admin' ...
Step 9 of 9 : Oracle VM Manager Shell ...
Retrieving Oracle VM Manager Shell & API ...
Extracting Oracle VM Manager Shell & API ...
Installing Oracle VM Manager Shell & API ...
Retrieving Oracle VM Manager Upgrade tool ...
Extracting Oracle VM Manager Upgrade tool ...
Installing Oracle VM Manager Upgrade tool ...
Copying Oracle VM Manager shell to '/usr/bin/ovm_shell.sh' ...
Installing ovm_admin.sh in '/u01/app/oracle/ovm-manager-3/bin' ...
Installing ovm_upgrade.sh in '/u01/app/oracle/ovm-manager-3/bin' ...
Enabling Oracle VM Manager service ...
Oracle VM Manager installed.
Installation Summary
--------------------
Database configuration:
Database host name : localhost
Database instance name (SID): XE
Database listener port : 1521
Application Express port : 8080
Oracle VM Manager schema : ovs
Weblogic Server configuration:
Administration username : weblogic
Oracle VM Manager configuration:
Username : admin
Core management port : 54321
UUID : 0004fb0000010000b2eec9e45f02c823
Passwords:
There are no default passwords for any users. The passwords to use for Oracle VM
Manager, Oracle Database 11g XE, and Oracle WebLogic Server have been set by you
during this installation. In the case of a default install, all passwords are the same.
Oracle VM Manager UI:
http://ORACLE VM MANAGER 3.0 HOST:7001/ovm/console
https://ORACLE VM MANAGER 3.0 HOST:7002/ovm/console
Log in with the user 'admin', and the password you set during the installation.
Please note that you need to install tight-vnc on this computer to access a virtual machine's
console.
For more information about Oracle Virtualization, please visit:
http://www.oracle.com/virtualization/
Oracle VM Manager installation complete.
To access Oracle VM Manager 3.0, enter one of the two addresses (http or https) listed at
the end of the installation.
http://<ORACLE VM MANAGER 3.0 HOST>:7001/ovm/console/faces/login.jspx
https://<ORACLE VM MANAGER 3.0 HOST>:7002/ovm/console/faces/login.jspx
Figure 8 shows the Oracle VM Manager Login page.
To login to Oracle VM Manager, use the "admin" user account with the password entered
during the installation. Figure 9 shows the Oracle VM Manager administrative console.
Oracle VM Manager Production Installation The next example shows how to perform a “Production” Oracle VM Manager installation.
Note: A Production installation requires that the Oracle SE or EE Database has already
been created. The installer will ask for the Oracle Database System ID (SID), the Oracle
Database SYSTEM password, the Oracle Database listener port (the default is 1521), the
Oracle VM Manager database schema (the default name is “ovs”, any name can be used),
and the Oracle VM Manager database schema password.
1. Download the Oracle VM Manager ISO file from the Oracle Linux and Oracle
VM Cloud Portal.
2. Use your favorite zip utility to unzip the Oracle VM Manager ISO file.
3. Copy the Oracle VM Manager ISO file to a directory on the Oracle VM Manager
host, i.e. to the /home/oracle directory. Note: The directory where the ISO file is
mounted must be writable by the oracle user account.
4. Log in to the Oracle VM Manager host as root.
5. Check that host name in the /etc/hosts file is associated with the server's public IP
address.
6. Create a directory to mount the ISO file, i.e. mkdir -p /home/oracle/mount-point.
7. Mount the ISO file by typing “mount -o loop OracleVM-Manager-
<VERSION>.iso /home/oracle/mount-point”
8. Change to the directory where the ISO file is mounted, i.e. “cd
/home/oracle/mount-point.
9. Run the installer script as root, by typing “./runInstaller.sh”
[root@ovm /home/oracle/mount-point]# ./runInstaller.sh
Oracle VM Manager Release 3.0.3 Installer
Oracle VM Manager Installer log file:
/tmp/ovmm-installer.selfextract_LP3677/install-2011-09-12-190813.log
Please select an installation type:
1: Demo
2: Production
3: Uninstall
4: Help
Select Number (1-4): 2
Starting standard installation ...
Verifying installation prerequisites ...
Oracle Database Repository
==========================
Would you like to install Oracle Database 11g Express Edition (XE) or connect to an
existing Oracle database?
1: Install Oracle Database 11g XE
2: Use an existing Oracle database
Select Number (1-2): 2
Enter the Oracle Database hostname [localhost]: db-archer.sf.mokum.solutions.com
Enter the Oracle Database System ID (SID) [XE]: orcl
Enter the Oracle Database SYSTEM password:
Enter the Oracle Database listener port [1521]:
Enter the Oracle VM Manager database schema [ovs]:
Enter the Oracle VM Manager database schema password:
Enter the Oracle VM Manager database schema password (confirm):
Oracle Weblogic Server 11g
==========================
Enter the Oracle WebLogic Server 11g user [weblogic]:
Enter the Oracle WebLogic Server 11g user password:
Enter the Oracle WebLogic Server 11g user password (confirm):
Oracle VM Manager application
=============================
Enter the username for the Oracle VM Manager administration user [admin]:
Enter the admin user password:
Enter the admin user password (confirm):
Verifying configuration ...
Start installing the configured components:
1: Continue
2: Abort
Select Number (1-2): 1
Step 1 of 9 : Database ...
Installing Database ...
Database installation skipped ...
Step 2 of 9 : Java ...
Installing Java ...
Step 3 of 9 : Database Schema ...
Creating database schema 'ovs' ...
Step 4 of 9 : WebLogic ...
Retrieving Oracle WebLogic Server 11g ...
Installing Oracle WebLogic Server 11g ...
Step 5 of 9 : ADF ...
Retrieving Oracle Application Development Framework (ADF) ...
Unzipping Oracle ADF ...
Installing Oracle ADF ...
Step 6 of 9 : Oracle VM ...
Retrieving Oracle VM Manager Application ...
Extracting Oracle VM Manager Application ...
Installing Oracle VM Manager Core ...
Step 7 of 9 : Domain creation ...
Creating Oracle WebLogic Server domain ...
Starting Oracle WebLogic Server 11g ...
Configuring data source 'OVMDS' ...
Creating Oracle VM Manager user 'admin' ...
Step 8 of 9 : Deploy ...
Deploying Oracle VM Manager Core container ...
Deploying Oracle VM Manager UI Console ...
Deploying Oracle VM Manager Help ...
Enabling HTTPS ...
Granting ovm-admin role to user 'admin' ...
Step 9 of 9 : Oracle VM Manager Shell ...
Retrieving Oracle VM Manager Shell & API ...
Extracting Oracle VM Manager Shell & API ...
Installing Oracle VM Manager Shell & API ...
Retrieving Oracle VM Manager Upgrade tool ...
Extracting Oracle VM Manager Upgrade tool ...
Installing Oracle VM Manager Upgrade tool ...
Copying Oracle VM Manager shell to '/usr/bin/ovm_shell.sh' ...
Installing ovm_admin.sh in '/u01/app/oracle/ovm-manager-3/bin' ...
Installing ovm_upgrade.sh in '/u01/app/oracle/ovm-manager-3/bin' ...
Enabling Oracle VM Manager service ...
Oracle VM Manager installed.
Installation Summary
--------------------
Database configuration:
Database host name : db-archer.sf.mokum.solutions.com
Database instance name (SID): orcl
Database listener port : 1521
Application Express port : None
Oracle VM Manager schema : ovs
Weblogic Server configuration:
Administration username : weblogic
Oracle VM Manager configuration:
Username : admin
Core management port : 54321
UUID : 0004fb0000010000d04b7f4bf11773e1
Passwords:
There are no default passwords for any users. The passwords to use for Oracle VM
Manager, Oracle Database 11g XE, and Oracle WebLogic Server have been set by you
during this installation. In the case of a default install, all passwords are the same.
Oracle VM Manager UI:
http://ORACLE VM MANAGER 3.0 HOST:7001/ovm/console
https://ORACLE VM MANAGER 3.0 HOST:7002/ovm/console
Log in with the user 'admin', and the password you set during the installation.
Please note that you need to install tight-vnc on this computer to access a virtual machine's
console.
For more information about Oracle Virtualization, please visit:
http://www.oracle.com/virtualization/
Oracle VM Manager installation complete.
To access Oracle VM Manager 3.0, enter one of the two addresses (http or https) listed at
the end of the installation.
http://<ORACLE VM MANAGER 3.0 HOST>:7001/ovm/console/faces/login.jspx
https://<ORACLE VM MANAGER 3.0 HOST>:7002/ovm/console/faces/login.jspx
Figure 10 shows the Oracle VM Manager Login page.
To login to Oracle VM Manager, use the "admin" user account with the password entered
during the installation. Figure 11 shows the Oracle VM Manager administrative console.
How to Uninstall Oracle VM Manager The next example shows how to uninstall a Demo Oracle VM Manager installation. The
Oracle VM Manager media is required to uninstall Oracle VM Manager.
Tip: It is necessary to uninstall all of the Oracle VM Manager componinets to sucessfully
uninstall then reinstall Oracle VM Manager.
1. Download the Oracle VM Manager ISO file from the Oracle Linux and Oracle
VM Cloud Portal
2. Use your favorite zip utility to unzip the Oracle VM Manager ISO file
3. Copy the Oracle VM Manager ISO file to a directory on the Oracle VM Manager
host, i.e. to the /home/oracle directory. Note: The directory must be writable by
the oracle user account.
4. Log in to the Oracle VM Manager host as root
5. Shut down Oracle VM Manager by typing “/etc/init.d/ovmm stop ”
6. Create a directory to mount the ISO file, i.e. mkdir -p /home/oracle/mount-point.
7. Mount the ISO file by typing “mount -o loop OracleVM-Manager-
<VERSION>.iso /home/oracle/mount-point”
8. Change to the directory where the ISO file is mounted, i.e. “cd
/home/oracle/mount-point
9. Run the installer script as root, by typing “./runInstaller.sh
[root@ovm /home/oracle/mount-point]# ./runInstaller.sh
Oracle VM Manager Release 3.0.3 Installer
Oracle VM Manager Installer log file:
/tmp/ovmm-installer.selfextract_gx5525/install-2011-09-10-160853.log
Please select an installation type:
1: Demo
2: Production
3: Uninstall
4: Help
Select Number (1-4): 3
Uninstall Oracle VM Manager
Product component : Oracle 11g XE in '/u01/app/oracle/product'
Oracle 11g XE is installed ...
Uninstall options
1: Uninstall Oracle 11g XE
2: Skip uninstall of Oracle 11g XE
Select Number (1-2): 1
Removing Oracle 11g XE installation ...
Product component : Java in '/u01/app/oracle/java/'
Java is installed ...
Uninstall options
1: Uninstall Java
2: Skip uninstall of Java
Select Number (1-2): 1
Removing Java installation ...
Product component : Oracle VM Manager in '/u01/app/oracle/ovm-manager-3/'
Oracle VM Manager is installed ...
Uninstall options
1: Uninstall Oracle VM 3.0 Manager
2: Skip uninstall of Oracle VM 3.0 Manager
Select Number (1-2): 1
Removing Oracle VM Manager installation ...
Product component : Oracle WebLogic Server in '/u01/app/oracle/Middleware/'
Oracle WebLogic Server is installed
Uninstall options
1: Uninstall Oracle WebLogic Server
2: Skip uninstall of Oracle WebLogic Server
Select Number (1-2): 1
Removing Oracle WebLogic Server installation ...
Uninstall completed ...
How to Backup Oracle VM Manager Before upgrading Oracle VM Manager, a best practice is to backup the Oracle VM
Manager configuration file as well as the Oracle VM Manager Database repository. To be
able to restore Oracle VM Manager from backup, a backup of the Oracle VM Manager
configuration file and the Oracle VM Manager Database repository is required.
To restore Oracle VM Manager from backup, a backup of the Oracle VM Manager hosts'
“.config” file is used with the Oracle VM Manager runInstaller.sh script to re-install Oracle
VM Manager using the backed up configurations. The runInstaller.sh script is located in the
Oracle VM Manager ISO image. When Oracle VM Manager is re-installed with a backup
of the .config file, Oracle VM Manager can re-discover the Oracle VM Servers, repositories
and virtual machines resources.
Tip: The Oracle VM Manager installation parameters can be listed by running
“runInstaller.sh -h”.
If the Oracle VM Manager Database repository needs to be restored from backup, access
the Database system and restore the Oracle VM Manager ovs database schema from a
backup.
In the event that Oracle VM Manager configurations need to be modified to restore from
backup, the “ovm_admin" utility is used to modify Oracle VM Manager configurations.
The next example shows the help file from the ovm_admin utility.
/u01/app/oracle/ovm-manager-3/bin/ovm_admin --help
Oracle VM Manager Release 3.0.3 Admin tool
Usage: /u01/app/oracle/ovm-manager-3/bin/ovm_admin [options]
options
--help Shows this message
--createuser <admin> <password> Create new Oracle VM Manager
admin user
--deleteuser <admin> Delete Oracle VM Manager admin
user
--listusers List Oracle VM Manager users
--modifyuser <admin> <password>
<new_password>
Modify Oracle VM Manager user
password
--lockusers <tries> Max login tries before locking
account. This setting is global.
--unlockuser <admin> Unlock user account
--modifyds <SID> <host> <port>
<schema> <password> Modify Data Store 'OVMDS'
--listconfig List configuration
--rotatelogsdaily <time> Rotate Logs Daily (HH:MM)
--rotatelogsbysize <size> Rotate Logs By Size (KB)
How to Backup Oracle VM Manager Configuration File The Oracle VM Manager configuration file “.config ” is located on the Oracle VM
Manager host(s) in the /u01/app/oracle/ovm-manager-3/ directory. The next example show
the syntax of the Oracle VM Manager .config file.
DBHOST=<THE HOSTNAME OF THE DATABASE SERVER>
SID=<ORACLE DATABASE SID>
LSNR=<THE LISTENER PORT FOR THE DATABASE>
APEX=<THE APPLICATION EXPRESS PORT>
OVSSCHEMA=<THE DEFAULT ORACLE VM MANAGER DATABASE SCHEMA
NAME>
WLSADMIN=<THE DEFAULT WEBLOGIC SERVER ADMIN NAME>
OVSADMIN=<THE DEFAULT ORACLE VM MANAGER ADMIN NAME>
COREPORT=<THE DEFAULT ORACLE VM MANAGER CORE PORT>
UUID=<THE ORACLE VM MANAGER UUID>
The next example shows a .config file from a production Oracle VM Manager host.
# cat /u01/app/oracle/ovm-manager-3/.config
DBHOST=db-archer
SID=orcl
LSNR=1521
APEX=None
OVSSCHEMA=ovs
WLSADMIN=weblogic
OVSADMIN=admin
COREPORT=54321
UUID=0004fb0000010000d04b7f4bf11773e1
BUILDID=1361
Before backing up the .config file, Oracle VM Manager must be shut down. To shut down
Oracle VM Manager, access the Oracle VM Manager host as the root user, and type
“service ovmm stop”, as shown in the next example.
# service ovmm stop
Stopping Oracle VM Manager [ OK ]
Once Oracle VM Manager is stopped, backup the /u01/app/oracle/ovm-manager-3/.config.
The next example shows how to backup the .config file in the root users home directly with
a descriptive name “ovm-back-” and the date.
# zip -9r /~ovm-back-`hostname -s`-`date +%F`.zip /u01/app/oracle/ovm-manager-3/.config
Once the .config file is backed up, start Oracle VM Manager by typing “service ovmm
start” as shown in the following example.
# service ovmm start
Starting Oracle VM Manager [ OK ]
How to Backup the Oracle VM Manager Database Repository Once the Oracle VM Manager configuration file is backed up, and Oracle VM Manager is
running, the Oracle VM Manager repository should be backed up. Oracle recommends a
full database repository backup. If you're brave, “only” backup the ovs schema.
The following example shows how to do a full Oracle Express, Standard or Enterprise
Edition Database repository backup using the exp utility.
Note: The exp utility is one of many applications that can be used to do a full Oracle VM
Manager Database repository backup.
The exp utility can be run in one of three modes: interactive dialogue, controlled through
bypassed parameters and parameter file controlled. For the sake of brevity, we will use the
interactive dialogue mode to do a full Oracle VM Manager 11g Standard or Enterprise
Edition Database repository backup.
The exp utility usage is a field unto itself, a detailed review is beyond the scope of this
book. The goal of this section is to explain how to do a full Oracle VM Manager 11g
Standard or Enterprise Edition Database repository backup using the exp utility.
How to Backup an Oracle 11g Standard or Enterprise Edition Database Repository The following example shows how to do a full Oracle VM Manager 11g Standard or
Enterprise Edition Database repository backup using the exp utility.
Log into the Oracle VM Manager Database repository system as the oracle user, or as root
and type “su - oracle” to change to the oracle user.
Tip: The exp utility help files are available by typing “exp help=yes”
# su - oracle
$ exp
Export: Release 11.1.0.6.0 - Production on Tue Oct 4 14:03:33 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Username: <USER NAME>
Password: <PASSWORD>
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit
Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Enter array fetch buffer size: 4096 >
Export file: expdat.dmp >
(1)E(ntire database), (2)U(sers), or (3)T(ables): (2)U > 1
Export grants (yes/no): yes >
Export table data (yes/no): yes >
Compress extents (yes/no): yes >
/
Export terminated successfully with warnings.
The above example creates a back up of the Database repository named expdat.dmp in the
working directory.
The next example show how to backup “only” the Oracle VM Manager 11g Standard or
Enterprise Edition Database repository ovs schema. Change the user name and password
for your environment.
$ exp USERID=<USER NAME>/<PASSWORD> OWNER=ovs FILE=exp_ovs.dmp
Export: Release 11.1.0.6.0 - Production on Mon Oct 3 16:24:09 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit
Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses WE8MSWIN1252 character set (possible charset conversion)
/
Export terminated successfully with warnings.
How to Backup an Oracle 11g Express Database Repository The next example shows how to backup an Oracle 11g Express Database repository using
the exp utility.
Log into the Oracle VM Manager host as the oracle user, or as root and type “su - oracle” to
change to the oracle user. As the oracle user type the following commands to backup the
Oracle VM Manager 11g XE Database repository.
Note: Replace <PASSWORD> with the ovs database schema password that was selected
during the Oracle VM Manager installation. In the below example a file named
“ovsbackup.dmp” is created in the /tmp directory. Any name or directory can be used with
the “file=” argument.
export ORACLE_HOME=/u01/app/oracle/product/11.2.0/xe
export PATH=$ORACLE_HOME/bin:$PATH
export ORACLE_SID=XE
Oracle Desktop Virtualization Security Solution at DISA Mission Partner Conference 2012
building an appliance? physical ? virtual? production quality? use Oracle Linux
understanding memory allocation in oracle vm / xen
Oracle VM Administration: Oracle VM Server for x86 course schedule
figuring out cpu topology in oracle vm
Collaborate12 Starts Today!
Oracle VM Administration: Oracle VM Server for x86 - new Training
More Oracle VM templates for PeopleSoft and Oracle Enteprise Manager
Oracle Ebusiness Suite 12.1.3 Oracle VM templates
Eight New Oracle Database Assemblies Ready to Run In Your Oracle VM Cloud with
Oracle Enterprise Manager 12c
Oracle VM Patch Updates
Show a printer friendly, save as PDF version of the Oracle Cloud Cookbook
Distribution of the Oracle Cloud Cookbook or derivative of the work in any form for
commercial purposes is prohibited unless prior permission is obtained from the copyright
holder.
This chapter of the Oracle Cloud Cookbook reviews how to apply patch updates to Oracle
VM Manager and Oracle VM Server. When updating Oracle VM, Oracle VM Manager
must be updated first, followed by the Oracle VM Servers managed by Oracle VM
Manager.
Change Log
Revision Change Description Updated By Date
1.0 First Release Roddy
Rodstein 10/05/11
1.1 3.0.3 Updates Roddy
Rodstein 01/20/12
1.2 Yum Server Setup and Oracle VM Server Upgrades
and Updates with Oracle VM Manager
Roddy
Rodstein 04/01/12
1.3 Oracle VM 3.1.1 Upgrades and Updates Roddy
Rodstein 05/09/12
Table of Contents Change log
Oracle VM Releases
Oracle VM Upgrade Roadmap
How to Backup Oracle VM Manager
...How to Backup an Oracle VM Manager Configuration File
...How to Backup an Oracle VM Manager Database Repository
…...How to Backup an Oracle VM Manager Standard or Enterprise Edition Database
Repository
…...How to Backup an Oracle VM Manager Express Database Repository
How to Download the Oracle VM Upgrade Media from the Oracle Linux and Oracle VM
Cloud Portal
How to Mount the Oracle VM Manager Media and Run the Oracle VM 3.1.1
runUpgrader.sh Script
Oracle VM Server Upgrade, Updates and Patching with a Yum Server
...Oracle Yum Server Configurtaion Road Map
...Register the Oracle Linux Yum Server with the Oracle Unbreakable Linux Network
...Install and configure Apache on the Oracle Linux Yum Server
...Oracle Unbreakable Linux Network Yum Server Configuration
...Populated and Synchronize the Yum Server with Oracle Unbreakable Linux Network
...Oracle VM Manager Yum Server Configuration
Oracle VM Releases At Oracle OpenWorld 2007, Oracle announced its entry into the x86 server virtualization
market with the first release of Oracle VM. The first release of Oracle VM was actually
version 2.1 because of Larry Ellison's aversion to using 1.0 for Oracle product releases to
help drive early adoption. As of this wrtining, there has been a total of 11 Oracle VM
Releases.
A key component of a successful Oracle VM deployment is acquiring and vetting new
releases, patches and updates for production systems. New Oracle VM releases, patches
and updates must be researched to identify which release, patches and updates are
applicable to your environment. Newly released versions, patches and updates should be
vetted before being deployed in to production. A best practice is to run the latest stable
release of Oracle VM. As of this writing, the latest stable Oracle VM release is 3.0.3.
The relevant parts of Oracle VM releases are:
Major release numbers: 2.1, 2.2, 3.0 and 3.1
Minor release numbers: 2.1.x, 2.2.x and 3.0.x
Oracle VM 3.0.1 Release
Oracle VM 3.0.1 was released on August 23rd 2011. Oracle VM 3.0.1 was the first
Oracle VM 3.0 release.
Oracle VM 3.0.2 Release
Oracle VM 3.0.2 was released on September 30th 2011. Oracle VM Manager 3.0.2
includes over 140 fixes without any new features.
Oracle VM 3.0.3 Release
Oracle VM 3.0.3 was released on Janurary 20th 2012. Oracle VM Manager 3.0.3
includes numerious bug fixes along with several new features.
Oracle VM 3.1.1 Release
Oracle VM 3.1.1 was released on May 8th 2012. Oracle VM Manager 3.1.1
includes numerious bug fixes along with several new features.
Oracle VM Upgrade Roadmap Step 1 Backup Oracle VM Manager
Step 2 Download the Oracle VM Manager Upgrade or Installation Media and/or the patch
update
Step 3 Stage and Mount the Oracle VM Manager Upgrade or Installation ISO File and/or
patch update on the Oracle VM Manager host and run the upgrade script
Step 4 Update the Oracle VM Servers using a Local YUM repository
How to Backup Oracle VM Manager Before upgrading Oracle VM Manager, a best practice is to backup the Oracle VM
Manager configuration file as well as the Oracle VM Manager Database repository. To be
able to restore Oracle VM Manager from backup, a backup of the Oracle VM Manager
configuration file and a backup of the Oracle VM Manager Database repository is
necessary.
How to Backup an Oracle VM Manager Configuration File The Oracle VM Manager configuration file “.config ” is located on the Oracle VM
Manager host in the /u01/app/oracle/ovm-manager-3/ directory. The next example show the
syntax of the Oracle VM Manager .config file.
DBHOST=<THE HOSTNAME OF THE DATABASE SERVER>
SID=<ORACLE DATABASE SID>
LSNR=<THE LISTENER PORT FOR THE DATABASE>
APEX=<THE APPLICATION EXPRESS PORT>
OVSSCHEMA=<THE DEFAULT ORACLE VM MANAGER DATABASE SCHEMA
NAME>
WLSADMIN=<THE DEFAULT WEBLOGIC SERVER ADMIN NAME>
OVSADMIN=<THE DEFAULT ORACLE VM MANAGER ADMIN NAME>
COREPORT=<THE DEFAULT ORACLE VM MANAGER CORE PORT>
UUID=<THE ORACLE VM MANAGER UUID>
The next example shows a .config file from a production Oracle VM Manager host.
# cat /u01/app/oracle/ovm-manager-3/.config
DBHOST=localhost
SID=orcl
LSNR=1521
APEX=None
OVSSCHEMA=ovs
WLSADMIN=weblogic
OVSADMIN=admin
COREPORT=54321
UUID=0004fb00000100009edfaa0f93184f44
BUILDID=3.1.1.305
FROMVERSION=3.0.3
TOVERSION=3.1.1
Before backing up the .config file, Oracle VM Manager must be shut down. To shut down
Oracle VM Manager, access the Oracle VM Manager host as the root user, and type
“service ovmm stop”, as shown in the next example.
# service ovmm stop
Stopping Oracle VM Manager [ OK ]
Once Oracle VM Manager is stopped, backup the /u01/app/oracle/ovm-manager-3/.config.
The next example shows how to backup the .config file in the root users home directly with
a descriptive name “ovm-back-” and the current date.
# zip -9r ovm-back-`hostname -s`-`date +%F`.zip /u01/app/oracle/ovm-manager-3/.config
Once the .config file is backed up, start Oracle VM Manager by typing “service ovmm
start” as shown in the following example.
# service ovmm start
Starting Oracle VM Manager [ OK ]
How to Backup an Oracle VM Manager Database Repository Once the Oracle VM Manager configuration file is backed up, and Oracle VM Manager is
running, the Oracle VM Manager repository should be backed up. Oracle recommends a
full database repository backup. If you're brave, “only” backup the ovs schema.
The next example shows how to do a full Oracle VM Manager 11g Standard or Enterprise
Edition Database repository backup using the exp utility.
Note: The exp utility is one of many applications that can be used to do a full Oracle VM
Manager Database repository backup.
The exp utility can be run in one of three modes: interactive dialogue, controlled through
bypassed parameters and parameter file controlled. For the sake of brevity, we will use the
interactive dialogue mode to do a full Oracle VM Manager 11g Standard or Enterprise
Edition Database repository backup.
How to Backup an Oracle VM Manager Standard or Enterprise Edition Database
Repository The following example shows how to do a full Oracle VM Manager 3.0 11g Standard or
Enterprise Edition Database repository backup using the exp utility.
Log into the Oracle VM Manager Database repository system as the oracle user, or as root
and type “su - oracle” to change to the oracle user.
Tip: The exp utility help files are available by typing “exp help=yes”
# su - oracle
$ exp
Export: Release 11.1.0.6.0 - Production on Tue Oct 4 14:03:33 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Username: <USER NAME>
Password: <PASSWORD>
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit
Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Enter array fetch buffer size: 4096 >
Export file: expdat.dmp >
(1)E(ntire database), (2)U(sers), or (3)T(ables): (2)U > 1
Export grants (yes/no): yes >
Export table data (yes/no): yes >
Compress extents (yes/no): yes >
/
Export terminated successfully with warnings.
The above example creates a back up of the Database repository named expdat.dmp in the
working directory.
The next example show how to backup “only” the Oracle VM Manager 11g Standard or
Enterprise Edition Database repository ovs schema. Change the user name and password
for your environment.
$ exp USERID=<USER NAME>/<PASSWORD> OWNER=ovs FILE=exp_ovs.dmp
Export: Release 11.1.0.6.0 - Production on Mon Oct 3 16:24:09 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit
Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses WE8MSWIN1252 character set (possible charset conversion)
/
Export terminated successfully with warnings.
How to Backup an Oracle VM Manager Express Database Repository
The next example shows how to backup an Oracle VM Manager 11g Express Database
repository using the exp utility.
Log into the Oracle VM Manager host as the oracle user, or as root and type “su - oracle” to
change to the oracle user. As the oracle user type the following commands to backup the
Oracle VM Manager 11g XE Database repository.
Note: Replace <PASSWORD> with the ovs database schema password that was selected
during the Oracle VM Manager installation. In the below example a file named
“ovsbackup.dmp” is created in the /tmp directory. Any name or directory can be used with
the “file=” argument.
export ORACLE_HOME=/u01/app/oracle/product/11.2.0/xe
export PATH=$ORACLE_HOME/bin:$PATH
export ORACLE_SID=XE
exp ovs/<PASSWORD> grants=y compress=y file=/tmp/ovsbackup.dmp
How to Download the Oracle VM Upgrade Media from the Oracle Linux and Oracle
VM Cloud Portal In order to upgrade Oracle VM Manager, the installation or upgrade media must be
downloaded and made available to the Oracle VM Manager host. Oracle VM Server can
also be upgraded using the installation media or with a local YUM repository. The Oracle
VM Manager installation and upgrade media can be burned to DVD and applied using a
CD-ROM, or the ISO file can be copied to Oracle VM Manager host and mounted locally
to start the upgrade program.
Tip: This chapter of the Oracle Cloud Cookbook covers how to upgrade Oracle VM Server
using a local YUM repository.
As of this writing, the latest installation media for Oracle VM Manager is Oracle VM
Manager 3.1.1, and the latest upgrade media is Oracle VM Manager 3.1.1 - Upgrade
only. Oracle VM Manager can be upgraded using the installation media and/or with the
upgrade only media. The upgrade only media is a much smaller and fatser to download.
The latest installation media for Oracle VM Servers is Oracle VM Server 3.1.1 for x86_64
(64 bit). The Oracle VM installation and upgrade media is available at the Oracle Linux and Oracle
VM Cloud Portal. Access to the Oracle Linux and Oracle VM Cloud Portal requires an
Oracle.com user account and password to authenticate in to the Oracle Linux and Oracle
VM Cloud Portal. If you do not already have an Oracle.com user account, visit the Oracle
Linux and Oracle VM Cloud Portal, click the Sign In / Register link or button to create an
Oracle.com account.
Figure 1 shows the Oracle Linux and Oracle VM Cloud Portal.
From the Sign In page, enter your Oracle.com user name and password, then click the
Sign In button.
Figure 2 shows the Oracle Linux and Oracle VM Cloud Portal Sign In page.
Once authenticated, accept the registration/export regulations to access to the Oracle VM
and Oracle Linux Media.
Figure 3 shows the registration/export regulations form.
After completing the registration/export regulation form, you will be redirected to the
Media Pack Search page. From the Media Pack Search page, select Oracle VM from the
Select a Product Pack dropdown menu. Next, select x86 64-bit from the Platform
dropdown menu, then click the Go button to be taken to the Oracle VM Media Pack
download page.
Tip: If you do not see Oracle VM from the Select a Product Pack dropdown menu, you
are not in the Oracle Linux and Oracle VM section of the Cloud Portal. Click the Cloud
Portal link in the page header, then click the Oracle Linux/VM drop down menu to be
redirected to the Oracle Linux and Oracle VM section of the Cloud Portal.
Figure 4 shows the Media Pack Search page.
From the Oracle VM Media Pack page, click the desired Oracle VM Media Pack radio
button, then the Continue button, or click the desired Oracle VM Media Pack hyperlink
to go to the download page.
From the Oracle VM Media Pack download page, click the desired Oracle VM Manager
and Server Download button to download the Oracle VM Media Pack. As of this writing,
the latest installation media for Oracle VM Manager is Oracle VM Manager 3.1.1, and the
latest upgrade media is Oracle VM Manager 3.1.1 - Upgrade only. Oracle VM Manager
can be upgraded using the installation media and/or with the upgrade only media. The
upgrade only media is a much smaller and fatser to download. The latest installation media
for Oracle VM Servers is Oracle VM Server 3.1.1 for x86_64 (64 bit).
The Oracle VM media is delivered as a zip file. The zip file name corresponds to the Part
Number listed on the download page. The Oracle VM Manager and/or Server zip file
contains an ISO file.
Once the zip file(s) is downloaded, use your favorite zip utility to unzip the Oracle VM
Manager media. Next, burn the ISO file to DVD to be able to install and or upgrade Oracle
VM with a CD-ROM drive, or copy the ISO file to the Oracle VM Manager host, mount
the ISO file and then perform the upgrade.
How to Mount the Oracle VM Manager Media and Run the Oracle VM 3.1.1
runUpgrader.sh Script In order to run the Oracle VM Manager runUpgrader.sh script, the upgrade or installation
media (ISO file) must be made available to the Oracle VM Manager host. The Oracle VM
Manager upgrade or installation media can be burned to DVD and applied using a CD-
ROM, or the ISO file can be copied to Oracle VM Manager host and mounted locally to
start the upgrade program.
List 2 walks through the steps to mount an Oracle VM Manager ISO file and start the
upgrade program.
1. Download the desired Oracle VM Manager media from the Oracle Linux and
Oracle VM Cloud Portal.
2. Use your favorite zip utility to unzip the Oracle VM Manager zip file.
3. Copy the ISO file to a directory on the Oracle VM Manager host, i.e. to the
/home/oracle directory.
1. Note: The directory where the ISO file will be mounted must be writable
by the oracle user account.
4. Log in to the Oracle VM Manager host as root.
5. Create a directory to mount the ISO file, i.e. mkdir -p /home/oracle/mount-point.
6. Mount the ISO file by typing “mount -o loop OracleVM-Manager-
<VERSION>.iso /home/oracle/mount-point”
7. Change to the directory where the ISO file is mounted, i.e. “cd
/home/oracle/mount-point.
8. Run the installer script as root, by typing “./runUpgrader.sh”, as shown in the
following example.
# ./runUpgrader.sh
Stating OVM Manager upgrade on Wed May 9 09:38:49 PDT 2012
Oracle VM Manager 3.1.1.305 upgrade utility
Upgrade logfile : /tmp/upgrade-2012-05-09-38.log
It is highly recommended to do a full database repository backup prior to upgrading Oracle
VM Manager ...
Press any key to continue ...
Oracle VM Manager is running ...
Verifying installation status ...
Read Oracle VM Manager config file ...
Found Oracle VM Manager install files ...
Found Oracle VM Manager upgrader ...
Found Oracle WebLogic Server ...
Found Java ...
Using the following information :
Database Host : localhost
Database SID : orcl
Database LSNR : 1521
Oracle VM Schema : ovs
Oracle VM Manager UUID : 0004fb00000100009edfaa0f93184f44
Current Build ID : 3.0.3.126
Upgrade from version : 3.0.3
Upgrade to version : 3.1.1
Using /tmp/workdir.mScEt29478 for backup and export location.
Using /tmp/patchdir.xuEM29479 for patching.
Enter password for user ovs :
Undeploying previous version of Oracle VM Manager application ...
Undeploying Oracle VM Manager help ...
Undeploying Oracle VM Manager console ...
Undeploying Oracle VM Manager core ...
Waiting for Oracle VM Manager core to fully undeploy...
Waiting...
Finished undeploying previous version ...
Exporting Oracle VM Manager repository ...
Please wait as this can take a long time ...
Oracle VM Manager repository export completed ...
Creating backup file ...
Oracle VM Manager repository backup in /tmp/ovm-manager-3-backup-2012-05-09.zip
Upgrading Oracle VM Manager ...
Backing up old files to /tmp/ovm-manager-3-backup-2012-05-09-094359...
Removing old files ...
Unpacking Oracle VM Manager 3.1.1.305
`transform_003001001000_010.xsl' ->
`/tmp/patchdir.xuEM29479/transform_003001001000_010.xsl'
`transform_003001001000_020.xsl' ->
`/tmp/patchdir.xuEM29479/transform_003001001000_020.xsl'
`deletedClasses.xml' -> `/tmp/patchdir.xuEM29479/deletedClasses.xml'
Filtering full repository export to the selective export subset at
/tmp/workdir_sel.rDZob29899 ...
cp: omitting directory `/tmp/workdir.mScEt29478/jrnl'
cp: omitting directory `/tmp/workdir.mScEt29478/objs'
adding: objs/81/818.cl.xml (deflated 73%)
adding: objs/64/6470.cl.xml (deflated 82%)
adding: objs/23/2369.cl.xml (deflated 74%)
adding: objs/50/506.cl.xml (deflated 73%)
adding: objs/9.cl.xml (deflated 93%)
adding: objs/88/883.cl.xml (deflated 81%)
adding: objs/44/445.cl.xml (deflated 87%)
adding: objs/62/628.cl.xml (deflated 72%)
adding: objs/74/748.cl.xml (deflated 87%)
adding: objs/52/5279.cl.xml (deflated 83%)
adding: objs/16/161.cl.xml (deflated 67%)
adding: objs/89/899.cl.xml (deflated 72%)
adding: objs/89/892.cl.xml (deflated 81%)
adding: objs/36/3695.cl.xml (deflated 73%)
adding: objs/36/3610.cl.xml (deflated 73%)
adding: objs/61/615.cl.xml (deflated 81%)
adding: objs/60/607.cl.xml (deflated 81%)
adding: objs/13/1354.cl.xml (deflated 77%)
adding: objs/13/1326.cl.xml (deflated 77%)
adding: objs/13/1381.cl.xml (deflated 76%)
adding: objs/49/4988.cl.xml (deflated 83%)
adding: objs/45/459.cl.xml (deflated 69%)
adding: objs/29/2920.cl.xml (deflated 71%)
adding: objs/19/193.cl.xml (deflated 70%)
adding: objs/14/1408.cl.xml (deflated 76%)
adding: objs/14/1435.cl.xml (deflated 77%)
adding: objs/32/3224.cl.xml (deflated 77%)
adding: objs/12/1241.cl.xml (deflated 76%)
adding: objs/12/1297.cl.xml (deflated 77%)
adding: objs/76/764.cl.xml (deflated 68%)
adding: objs/27/2766.cl.xml (deflated 71%)
Selective export is at /tmp/workdir_sel.rDZob29899
31 objects selected (out of 4725) to be upgraded
Transform XSL files used:
-rw-r--r-- 1 root root 56678 May 9 09:44
/tmp/patchdir.xuEM29479/transform_003001001000_010.xsl
-rw-r--r-- 1 root root 10079 May 9 09:44
/tmp/patchdir.xuEM29479/transform_003001001000_020.xsl
Changed classes encountered in selective export set:
com.oracle.ovm.mgr.api.manager.BusinessManagerDbImpl
com.oracle.ovm.mgr.api.manager.ModelManagerDbImpl
com.oracle.ovm.mgr.api.manager.RasManagerDbImpl
com.oracle.ovm.mgr.api.physical.network.BondPortDbImpl
com.oracle.ovm.mgr.api.physical.network.EthernetPortDbImpl
com.oracle.ovm.mgr.api.physical.network.InternalPortDbImpl
com.oracle.ovm.mgr.api.physical.ServerDbImpl
com.oracle.ovm.mgr.api.virtual.VirtualMachineDbImpl
com.oracle.ovm.mgr.api.virtual.VirtualMachineTemplateDbImpl
com.oracle.ovm.mgr.api.virtual.XenHypervisorDbImpl
Upgrading Oracle VM Manager repository ...
Please wait as this can take a long time ...
Oracle VM Manager repository upgrade completed ...
Validating Oracle VM Manager repository ...
Oracle VM Manager repository validation completed ...
Refresh system-jazn-data.xml file ...
Redeploying Oracle VM Manager core container ...
Redeploying Oracle VM Manager console ...
Redeploying Oracle VM Manager help ...
Install ADF Patch ...
Completed upgrade to 3.1.1.305 ...
Writing updated config in /u01/app/oracle/ovm-manager-3/.config
Restart WebLogic ...
Stopping Oracle VM Manager [ OK ]
Starting Oracle VM ManagerTime out...
OVM Manager upgrade finished on Wed May 9 10:18:27 PDT 2012
#
Oracle VM Manager has just been sucessfully updated.
The new Oracle VM Manager version number can be validated by viewing the release
number listed on the BUILDID line in the .config file. The next example show the .config
file before the upgrade.
# cat /u01/app/oracle/ovm-manager-3/.config
DBHOST=localhost
SID=orcl
LSNR=1521
APEX=None
OVSSCHEMA=ovs
WLSADMIN=weblogic
OVSADMIN=admin
COREPORT=54321
UUID=0004fb00000100009edfaa0f93184f44
BUILDID=3.1.1.305
FROMVERSION=3.0.3
TOVERSION=3.1.1
Oracle VM Server Upgrade, Updates and Patching with a Yum Server When upgrading Oracle VM, Oracle VM Manager must be upgraded first, followed by the
Oracle VM Servers managed by Oracle VM Manager. Oracle VM Servers are updated and
patched using a local yum repository. A local yum repository can be configured on any
Internet accessible Oracle Linux or Red Hat Enterprise Linux web server that has been
registered with the Unbreakable Linux Network. A valid customer service identifier (CSI)
for Oracle Linux and/or Oracle VM is required to configure a yum server at the
Unbreakable Linux Network.
Oracle Yum Server Configurtaion Road Map List 3 shows the steps to configure, update and patch an Oracle VM Server.
1- Register an Oracle Linux or Red Hat Enterprise Linux host with the Unbreakable Linux
Network.
2- Install and configure Apache on the Linux host.
3- Login to the Unbreakable Linux Network, edit the properties of the Linux host, select the
yum server check box, and select and save the desired RPM channels, i.e. Oracle VM 3
latest.
4- Use Oracle' 167283.sh script to populate the RPM channels from the Unbreakable Linux
Network.
5- Login to Oracle VM Manager and enter the URL of the Oracle VM 3 latest RPM
repository in the Server Update Management (YUM) dialog box.
6- Update and/or patch the Oracle VM Servers using Oracle VM Manager.
Register the Oracle Linux Yum Server with the Oracle Unbreakable Linux Network Before an Oracle Linux or Red Hat Enterprise Linux host can connect to the Oracle
Unbreakable Linux Network, Oracle’s GPG key must be imported using the rpm command.
To import the Oracle’s GPG key, as root type “rpm --import /etc/pki/rpm-gpg/RPM-GPG-
KEY”, as shown in the next example.
# rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY
Once the GPG key has been imported, the Linux host can be registered at the Oracle
Unbreakable Linux Network from the command line or using an X Windows application.
Linux 4 and 5 systems use the up2date command as root to access the registration screen by
typing “up2date --register” for X Windows or "up2date --nox --register" for text mode.
Linux 6 systems use the "uln_register" command as root to to access the registration screen.
The registration process requires you to enter your Unbreakable Linux Network associated
Oracle Single Sign-on user name and password and a valid Oracle Linux Support Identifier
number (CSI).
If a proxy server is in the mix, for Oracle Linux 4 and 5 systems, as root type “up2date --
configure” to list and edit the up2date program defaults. There are five proxy
configurations that can be edited to allow access from your Linux host to the internet. The
next example shows the up2date proxy configuration items with their default settings and
item numbers.
3. enableProxy No
4. enableProxyAuth No
11. httpProxy
21. proxyPassword
22. proxyUser
To edit an up2date program item, type the item number, i.e. enter 3 or 4, etc.... then type C
to clear the default value or type q to quit without saving. Next, type the new value and
press Enter to save the new value and to exit. If you need to enter multiple values, separate
them with semicolons (;).
Oracle Linux 6 systems use the “--proxy” option to specify an http proxy, i.e. “#
uln_register –proxy=<HOST NAME>:<PORT NUMBER> “. If your proxy server requires
authentication, use the “--proxyUser” and “--proxyPassword” to add a username and
password, i.e “# uln_register –proxy=<HOST NAME>:<PORT NUMBER> --
proxyUser=<USER NAME> --proxyPassword=<PASSWORD>”
List 4 shows the six steps to register a Linux host with the Oracle Unbreakable Linux
Network:
1. Review the Unbreakable Linux Privacy Statement
2. Register a User Account
3. Register a System Profile—Hardware
4. Register a System Profile—Packages
5. Send Profile Information to the Unbreakable Linux Network
6. Finished Registration
The following examples walk through the six steps to register a Linux host with the Oracle
Unbreakable Linux Network.
Step 1. Review the Unbreakable Linux Privacy Statement From the Review the Unbreakable Linux Privacy Statement screen use the Alt key to
select the Next tab, once the Next tab is selected press the Enter key to proceed.
Figure 5 shows the Review the Unbreakable Linux Privacy Statement screen.
Step 2. Register a User Account On the Register a User Account screen, enter your your Unbreakable Linux Network
associated Oracle Single Sign-on User name, Password, Password confirmation and a
valid Oracle VM CSI number. Use the Alt key to select the Next tab, and then press the
Enter key to proceed.
Figure 6 shows the Register a User Account screen.
Step 3. Register a System Profile—Hardware On the Register a System Profile—Hardware screen, accept the defaults and use the Alt
key to select the Next tab. Once the Next tab is selected, press the Enter key to proceed.
Note: The information gathered from the system profile step is saved in your user profile at
the Oracle Unbreakable Linux Network.
Figure 7 shows the Register a System Profile—Hardware screen.
Step 4. Register a System Profile— Packages On the Register a System Profile—Packages screen, accept the defaults and use the Alt
key to select the Next tab. Once the Next tab is selected, press the Enter key to proceed.
Figure 8 shows the Register a System Profile—Packages screen.
Step 5. Send Profile Information to the Unbreakable Linux Network From the Send Profile Information to the Unbreakable Linux Network screen, accept
the defaults and use the Alt key to select the Next tab. Once the Next tab is selected, press
the Enter key to proceed.
Figure 9 shows the Send Profile Information to the Unbreakable Linux Network screen.
Step 6 Finished Registration On the Finished Registration screen, accept the defaults and use the Alt key to select the
Next tab. Once the Next tab is selected, press the Enter key to proceed.
Figure 10 shows the Finished Registration screen.
The Oracle Linux host has been successfully registered.
Install and configure Apache on the Oracle Linux Yum Server Installing Apache from an Unbreakable Linux Network registered Oracle Linux host is
accomplished by typing “up2date -i httpd” and /or "yum install httpd" while logged in as
root. Once Apache is installed, configure Apache to automatically start by typing
“chkconfig httpd on”. Next, start Apache by typing “service httpd start”. The next example
shows how to install, configure and start Apache.
Using up2date, as root type:
# up2date -i httpd
# chkconfig httpd on && service httpd start
Using yum, as root type:
# yum install httpd
# chkconfig httpd on && service httpd start
Once the “up2date -i httpd”, “chkconfig httpd on” and “service httpd start” commands have
completed, test Apache by pointing a web browser to the fully qualified domain name
(FQDN) or the IP address of the Apache server. You will see the default Apache test page
as shown in Figure 11.
Tip: If you don’t see the default Apache test page, check if iptables is blocking http traffic
on the Apache host. Consider disabling iptables to test Apache by typing “sudo
/sbin/service iptables stop”.
Next, create a the yum repository base directory in /var/www/html by typing "mkdir -p
/var/www/html/yum".
Table 2 shows the approximate disk space requirements for each Oracle VM RPM channel:
Channel Binaries
ovm*_latest 147M
ovm*_base 400M
ovm*_patch 100M
Oracle Unbreakable Linux Network Yum Server Configuration
Once your yum server has been registered, and apache has been installed and configured,
access the Oracle Unbreakable Linux Network dashboard and click the Systems tab. From
the Systems tab click on the yum server to access its System Details page.
Figure 12 shows the Systems tab and the YUM server.
From the YUM servers Systems Details page click the Edit button, as shown in Figure 13.
From the Edit Systems Properties page, select the Yum Server check box, enter a valid
CSI number, then click the Apply Changes button, as shown in Figure 14.
Next, click the Manage Subscriptions button, as shown in in Figure 15.
From the System summary page select the Oracle VM 3 latest channel. Next, click the
Save Subscriptions button to save the changes, as shown in Figure 16.
The yum server has been successfully configured using the the Oracle Unbreakable Linux
Network dashboard. The next step is to populated and synchronize the local yum repository
with the Oracle Unbreakable Linux Network using the 167283.sh script.
Populated and Synchronize the Yum Server with Oracle Unbreakable Linux Network Local yum repositories are populated and synchronized to the Unbreakable Linux Network
using a script (167283.sh) and a cron job, or with Oracle Enterprise Manager. To populate
the yum repository using the 167283.sh script, as root type “cd”, then “wget
http://www.oracle.com/ocom/groups/public/@otn/documents/webcontent/167283.sh” to
download the 167283.sh script. Next, type “chmod 755 167283.sh” to make the script
executable. Then type “nohup sh 167283.sh &” to run the script. Once the 167283.sh script
completes, the yum RPM repository will be populated and ready to update or patch Oracle
VM Servers.
To automatically synchronize your local yum RPM repository to the Unbreakable Linux
Network, use a cron job with the 167283.sh script. As root or any other user with access to
the 167283.sh script, type "chrontab -e" to edit your crontab file, or create a new crontab
file if one does not already exist. The next example show how to create a crontab file as
root that will run the 167283.sh script at midnight every weekday.
# crontab -e
0 0 * * 1-5 /root/167283.sh
:wq!
To view the current cronjob on a Oracle Linux host, type "crontab -l". To edit the cronjob
type "crontab -e".
Crontab Syntax:
1 2 3 4 5 /path/to/command arg1 arg2
1: Minute (0-59)
2: Hours (0-23)
3: Day (0-31)
4: Month (0-12 [12 == December])
5: Day of the week(0-7 [7 or 0 == sunday])
/path/to/command - Command name or script to schedule
Oracle VM Manager Yum Server Configuration To patch Oracle VM Servers, a yum server should be added to Oracle VM Manager' Server
Update Management (YUM) menu. To add a Yum repository to Oracle VM Manager,
select the Tools and Resources tab, and then click the Server Update Management
(YUM) link to add the base URL and GPG key details.
Enter the following information in the Server Update Management (YUM) page to
configure a YUM repository:
YUM Base URL: Enter the URL from the Oracle VM latest channel, i.e.:
http://<YUM SERVER IP OR FQDN>/yum/OracleVM/OVM3/latest/x86_64/
Enable GPG Key: GPG keys are used to validate the identity of a Yum server and
its RPM packages (RPMs). Select the Enable GPG Key checkbox to be able to
enter the YUM GPG Key.
Note: If you elect"not" to configure the GPG key, it is necessary to type "rpm --
import /etc/pki/rpm-gpg/RPM-GPG-KEY" as root on each Oracle VM Server that
uses the configured yum reporitory.
YUM GPG Key: An Oracle-signed GPG key for ULN is pre-installed on Oracle
Linux hosts at /etc/pki/rpm-gpg/RPM-GPG-KEY-oracle. To to use the pre-
installed GPG key, enter “file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oracle” in the
YUM GPG Key text box. It is also possible to copy the GPG key to the web
server, i.e. “cp /etc/pki/rpm-gpg/RPM-GPG-KEY-oracle /var/www/html/yum/
&& chown apache:apache /var/www/html/yum/RPM-GPG-KEY-oracle” and
enter http://<YUM SERVER IP OR FQDN>/yum/ RPM-GPG-KEY-oracle in the
YUM GPG Key text box.
Note: The GPG key field is only enabled when you select Enable GPG Key.
Click Apply to save the setting.
Figure 17 shows the Server Update Management (YUM) page.
Once the YUM repository is added, as shown in Figure 18, Oracle VM Manager will
automatically query all the managed Oracle VM Servers and update the Update Required
status to Yes or No.
Select the Update Server option from Oracle VM Manager to upgrade one or more hosts.
Upgrading a server automatically puts the server into maintenance mode and if possible
Live Migrates any running VMs to a available node.
Firgure 19 shows the Update Server menu.
Once the Yum repository has been configured, each Oracle VM Server will have a new
files named ovm.repo in the /etc/yum.repos.d directory.
The next example show the contents of the ovm.repo file.
# cat /etc/yum.repos.d /ovm.repo
[ovm_repo]
gpgkey = http://<YUM SERVER IP OR FQDN>/yum/RPM-GPG-KEY-oracle
gpgcheck = 1
baseurl = http://<YUM SERVER IP OR FQDN>/yum/OracleVM/OVM3/latest/x86_64/
Oracle Desktop Virtualization Security Solution at DISA Mission Partner Conference 2012
building an appliance? physical ? virtual? production quality? use Oracle Linux
understanding memory allocation in oracle vm / xen
Oracle VM Administration: Oracle VM Server for x86 course schedule
figuring out cpu topology in oracle vm
Collaborate12 Starts Today!
Oracle VM Administration: Oracle VM Server for x86 - new Training
More Oracle VM templates for PeopleSoft and Oracle Enteprise Manager
Oracle Ebusiness Suite 12.1.3 Oracle VM templates
Eight New Oracle Database Assemblies Ready to Run In Your Oracle VM Cloud with
Oracle Enterprise Manager 12c
Oracle Linux 6 Installation with Oracle
VM Manager
Show a printer friendly, save as PDF version of the Oracle Cloud Cookbook
Copyright © 2012 Mokum Solutions, Inc. All rights reserved.
Distribution of the Oracle Cloud Cookbook or derivative of the work in any form for
commercial purposes is prohibited unless prior permission is obtained from the copyright
holder.
Change Log
Revision Change Description Updated By Date
1.0 First Release Roddy
Rodstein 10/10/11
1.1 Linux Patch Management with Free Updates and
Errata from Oracle
Roddy
Rodstein 04/29/12
Table of Contents Change Log
Oracle VM Manager 3.0: Oracle Linux 6 Installation Overview
Oracle VM Manager 3.0: Oracle Linux 6 Staging for HVM Installs (ISO Imports)
Oracle VM Manager 3.0: Oracle Linux 6 Staging for PVM Installs ( FTP / HTTP / NFS )
Oracle VM Manager 3.0: How to Add Virtual Network Interfaces (Vnic's)
Oracle VM Manager 3.0: Oracle Linux 6 HVM Installation
Oracle VM Manager 3.0: Oracle Linux 6 PVM Installation
Oracle VM Manager 3.0: Oracle Linux 6 Installation using Graphical (GUI) Mode
Oracle VM Manager 3.0: Oracle Linux 6 Installation using Text Mode
Oracle VM Manager 3.0: How to Add a Virtual Disk
Oracle VM Manager 3.0: How to Add a Virtual Network Interface
Linux Patch Management with Free Updates and Errata from Oracle
Oracle VM Manager 3.0: How to Delete a Virtual Machine
Oracle VM Manager 3.0: Oracle Linux 6 Installation Overview There are two unique installation options for Oracle Linux 6 with Oracle VM Manager 3.0.
Oracle Linux 6 can be installed using paravirtualization mode (Xen PVM) and /or hardware
virtualization mode (Xen HVM). Xen PVM and Xen HVM installations have slightly
different prerequisites and installation selections. For example, Xen PVM installations can
“not” boot from a DVD or from an ISO image, the installation tree must be available on a
Web or FTP server to boot a Xen PVM installation. Xen HVM installations can boot from
an ISO image, as long as the ISO image has been imported using Oracle VM Manager.
Xen PVM and Xen HVM use very different techniques to provide resources to virtual
machines. For example, Xen HVM uses Intel or AMD virtualization technologies for
memory management and to emulate the boot environment. Xen HVM also uses QEMU in
dom0 for device emulation. Xen PVM leverages the guest operating system's Xen kernel
for the boot process using the pygrub bootloader, Xen for memory management, and dom0
for device support, without emulation. Xen PVM virtual machines are hypervisor aware
and run without the overhead of hardware emulation. Xen HVM virtual machines think
they are running on native hardware, when in fact they are running on emulated hardware.
Xen PVM requires much less overhead for timers, interrupts, I/O traffic, and context
switches, allowing superior scalability under heavy loads when compared to Xen HVM.
Oracle VM Servers can support both Xen PVM and Xen HVM virtual machines
simultaneously on a single x86_64 server that has either Intel or AMD virtualization
technologies. Intel and AMD virtualization is a requirement only for Xen HVM virtual
machines, not for Xen PVM virtual machines. Intel and AMD virtualization technologies
are enabled, managed and tuned using the system BIOS.
The only way to determine which virtualization mode will provide the best performance for
your environment is to benchmark the same workload using a Xen PVM and a Xen HVM
virtual machine. If you do not have the time or expertise to conduct the benchmarks,
consider only using Xen PVM for your virtual machines. Over the years I have seen Xen
PVM outperform Xen HVM in every benchmark.
Note: Starting with the 2.6.32 Linux kernel (Unbreakable Enterprise Kernel and OL 6),
Linux can boot on bare metal, in Xen HVM mode, and in Xen PVM mode using
paravirt_ops with the same Linux kernel. In contrast to the 2.6.32 Linux kernel (OL 5U4-),
the 2.6.18 Linux kernel can boot on bare metal and in Xen HVM mode, and must use a Xen
paravirtualized kernel for Xen PVM mode.
The graphical and text installation programs and the installation steps are identical for all of
the Oracle Linux 6 releases, i.e. 6.0, 6U1, etc... The Oracle Linux installation media is
freely available from the Oracle eDelivery Linux portal as a single DVD (single download)
for Oracle Linux 6 and above.
Note:The GUI installation of an Oracle Linux 6 VM requires a minimum of 1gb RAM. Use
the GUI installer for the greatest set of installation options. The text-based installer will do
a Minimum Install only.
List 1 reviews the Oracle Linux installation considerations.
Disk Partitioning Setup. Depending upon your comfort level with installing Linux,
you can accept the default partition layout or select a custom layout.
o The default partition layout. Selecting the default partitioning layout will create a 500MB “/boot”
partition and a LVM with two volume groups, a root “/” partition
and a swap partition.
o Custom layout. 100% customizable.
Network Configuration o Configure a static IP address or use DHCP.
Time Zone Selection o Select the time zone settings for your area
o Configure UTC for the system clock
Package Installation o Use the default software selection and click on Next
Oracle recommends installing Oracle Linux and Red Hat Enterprise using the default
software package selection without any customization. Using the default software packages
without customization includes most of the prerequisite packages for Oracle technology
products and helps limit the number of manual prerequisite checks. After an Oracle Linux
and/or Red Hat Enterprise Linux installation, Oracle recommends to register your server
with the Unbreakable Linux Network (ULN) and to install the Legacy Software
Development packages by typing:
# yum groupinstall @ Legacy Software Development
Installing the Legacy Software Development packages will meet most of the Oracle
technology product prerequisite packages.
Oracle VM Manager 3.0: Oracle Linux 6 Staging for HVM Installs (ISO Imports) HVM installs require the use of ISO images that will be mounted on a virtual CDROM
drive during the install process. Oracle Linux ISOs can be downloaded from the Oracle
Linux and Oracle VM Cloud Portal. Access to the Oracle Linux and Oracle VM Cloud
Portal requires an Oracle.com user account and password.
Once you have the Oracle Linux ISO file, the next step is to stage the ISO file on a Web or
FTP server. Oracle VM Manager will then be used to import the ISO file. After which, it
will be possible to continue on with our HVM install.
First, select Server Pools, then Repositories, then ISOs. Next, click on the Import ISO
icon. Choose to which server you wish to add the ISO file and then enter the full URL for
your ISO image file to be imported. Click OK.
Figure 1
Oracle VM Manager 3.0: Oracle Linux 6 Staging for PVM Installs ( FTP / HTTP /
NFS ) You may be inclined to wonder why HVM installs can be done with an ISO file imported
directly into Oracle VM Manager while PVM installs require the ISO file be mounted
(mount -o loop) and made available via an FTP, HTTP or NFS server. That's because
paravirtualized guests don't have a BIOS from which a DVD device can be boot-strapped
and the installer DVD doesn't contain a Xen paravirtualized domU kernel so its not possible
to boot from an ISO image. You just have to think Xen.
Here is one method for staging the install tree on a web server:
# mount -o loop,ro OracleLinux-R6-U1-Server-x86_64-dvd.iso /mnt
# mkdir -p /var/www/html/repo/ol/6.1/iso/
# cp -avr /mnt/* /var/www/html/repo/ol/6.1/iso/
# umount /mnt
The contents of the ISO file are now staged on the Web server and ready to use for your
PVM install.
Here is a method for staging the install tree on an NFS server:
# mount -o loop,ro OracleLinux-R6-U1-Server-x86_64-dvd.iso /mnt
# mkdir -p /isos/ol61-x64
# cp -avr /mnt/* /isos/ol61-x64
# umount /mnt
# echo “/isos/ol61-x64 *(ro)” >> /etc/exports
# exportfs -a
The contents of the ISO file are now staged on the NFS server and ready to use for your
PVM install.
Oracle VM Manager 3.0: How to add Virtual Network Interfaces (Vnic's) Before you can continue on with creating a virtual machine you must first create a pool of
virtual NICs to be made available to the VMs during the Virtual Machine creation phase.
From the Oracle VM Manager, select Tools, then click Vnic Manager.
Figure 2
Click Next to set the next free range of octets for our VNICs. Select the number of VNICs
to create and then click Generate. You now have an available pool of VNICs for your
Virtual Machines.
Oracle VM Manager 3.0: Oracle Linux 6 HVM Installation After you have added the ISO into your VM Manager you are ready to install your new
Oracle Linux 6 VM. Right-click on the server from which you wish to install oracle Linux
6 VM and select Create Virtual Machine. In this example we will create the new VM on
ovs-chapel.
Figure 3
In the Create Virtual Machine window, choose a name for your new VM. You may also
choose to give a brief description of your VM in the description field. Next, choose the
amount of memory to give your new VM.
Note: A minimum of 1024MB is required to do a graphical install. A GUI install allows for
the greatest number of options during the install phase. The text-based installer will
perform a Minimum Installation only.
Adjust Priority and Processor Cap% for your VCPU needs depending on your environment.
Defaults are usually fine. Choose Xen PVM for the Domain Type. Choose Oracle Linux 6
for the Operating System. Enable HA as needed and choose the proper repository for your
environment. Click Next to adjust Networking Options.
Figure 4
Select a VNIC and add it to your VM. Click Next to Create Storage.
Figure 5
Best practices: Define a Virtual Disk Naming convention for your environment so that you
can easily recall Virtual Disk information in the future. In this example, we have decided
on the convention (vm_name-disk0) for the system disk. If you add a second disk, you
would name it (vm_name-disk1), and so on. Define your naming convention from the
beginning and stick with it.
Choose a name for your Virtual Disk and set the disk size. If you wish to make this disk
sharable between multiple VMs, select the Shareable checkbox.
Figure 6
Under Storage Options select the Oracle Linux 6.1 ISO that you've already staged. This
will be used to install your new VM.
Figure 7
Under disk order, we see that the ISO is listed first followed by our virtual disk.
Figure 8
Finally, we add the CDROM (Our ISO file) to the Boot Order and click Finish. We are now
ready to install Oracle Linux 6 on our new VM.
Figure 9
Oracle VM Manager 3.0: Oracle Linux 6 PVM Installation After you have mounted the ISO image and staged the mounted ISO image on your HTTP,
FTP or NFS server, you are ready to install your new Oracle Linux 6 VM. First, right-click
on the server you wish to install Oracle Linux 6 VM and select “Create Virtual Machine”.
In the Create Virtual Machine window, choose a name for your new VM. You may also
choose to give a brief description of your VM in the description field. Next, choose the
amount of memory to give your new VM.
Note: A minimum of 1024MB is required to do a graphical install. A GUI install allows for
the greatest number of options during the install phase. The text-based installer will
perform a Minimum Installation only.
Adjust Priority and Processor Cap% for your VCPU needs depending on your environment.
Defaults are usually fine. Choose Xen PVM for the Domain Type. Choose Oracle Linux 6
for the Operating System. Enable HA as needed and choose the proper repository for your
environment.
Figure 10
Click Next to adjust Networking Options. Select a VNIC and add it to your VM.
Figure 11
Click Next to Create Storage.
Best practices: Define a Virtual Disk naming convention for your environment so that you
can easily recall Virtual Disk information in the future when using the VM Manager GUI.
In this example, we have decided on the convention (vm_name-disk0) for the system disk.
If you add a second disk, you would name it (vm_name-disk1), and so on. Define your
naming convention from the beginning and stick with it.
Choose a name for your Virtual Disk and set the disk size. If you wish to make this disk
sharable between multiple VMs, select the Shareable checkbox.
Figure 12
Click Next to adjust Storage Options. For a PVM install you will not be adding ISOs at this
stage. Verify that the Virtual Disk has been added. Add Physical disks as need.
Figure 13
Click Next to choose the Disk Order. Typically, your newly created Virtual Disk will be at
the top of the Disk Order.
Figure 14
Finally, click Next to adjust Boot Options. Add Network to the Boot Order and define the
Network Boot Path parameters. In this example, we staged the Oracle Linux 6 ISO Image
on a Web Server 192.168.4.12 in the directory /var/www/html/repo/ol/6.1/iso. So, for the
network path:
--kernel images/pxeboot/vmlinuz –ramdisk images/pxeboot/initrd.img
http://192.168.4.12/repo/ol/6.1/iso/
If we wanted to do a Kickstart install then, based on our previous ISO staging work, we
would add a few options to the end, like so:
--kernel images/pxeboot/vmlinuz –ramdisk images/pxeboot/initrd.img
ks=http://192.168.4.12/repo/ol/6.1/ks.cfg http://192.168.4.12/repo/ol/6.1/iso/
where ks.cfg is the custom built kickstart configuration file for our environment.
Or, if we wanted to install over the network using NFS, you would do something in the
form “nfs:machine_name:network_path” like this:
nfs:192.168.4.12:/repo/ol/6.1/iso/
Figure 15
The following is an example kickstart file.
install
lang en_US.UTF-8
keyboard us
url --url http://192.168.4.12/repo/ol/6.1/iso
network --noipv6 --device eth0 --bootproto dhcp --onboot yes
rootpw --iscrypted $1$9xBiH0$0000de222aaaa&5og.0
firewall --service=ssh
authconfig --enableshadow --passalgo=sha512
selinux --disabled
timezone --utc America/Los_Angeles
bootloader --location=mbr --driveorder=xvda --append="crashkernel=auto rhgb quiet"
zerombr
clearpart --all --initlabel --drives=xvda
%packages --nobase
@core
%end
Oracle VM Manager 3.0: Oracle Linux 6 Installation using Graphical (GUI) Mode This section reviews how to install Oracle Linux 6 with the graphical (GUI) mode using
Oracle VM Manager 3.0.
1- Boot the VM. At the boot prompt, press the Enter key to start the Oracle Linux
installation in graphical mode.
Figure 16
2- On the CD Found window, you can perform a media test to validate the integrity of the
installation media. The media test is optional and time consuming. In this example, we will
not perform a media test.
Press the tab key to select the Skip key. Once the Skip key is selected, press the Enter key
to proceed.
Figure 17
3- On the Welcome screen, click the Next button or Alt+N to proceed.
Figure 18
4- On the Language Selection screen, select the preferred language that will be used
during the installation process. In this example, select the default language, English
(English).
Accept the default English (English) language selection, then click the Next button or
press Alt+N to proceed.
Figure 19
5- On the Keyboard Selection screen, select the desired keyboard setting for the system. In
this example, select the default keyboard selection, US English.
Accept the default US English keyboard selection, then click the Next button or press
Alt+N to proceed.
Figure 20
6- On the Storage Device screen, you can select the Basic Storage Devices or the
Specialized Storage Devices options.
In this example, accept the default Basic Storage Devices option, click the Next button or
press Alt+N to proceed.
Figure 21
7- A disk initialization Warning dialogue box will appear after you make your Storage
Device selection. Click the Re-initialize button or press Alt+R to proceed with the
installation.
Figure 22
8- On the Networking configuration screen, you can accept the default DHCP setting or
configure the networking manually. To use DHCP, accept the defaults, and click the Next
button or press Alt+N to proceed.
Click the Configure Network button to review the network configurations.
Figure 23
9- From the Network Connections screen, select the desired connection, i.e. eth0 and click
the Edit button.
Figure 24
10- On the Editing System screen select the Connect automatically checkbox to enable
the interface to automatically start at boot time. To configure the networking manually,
click the desired tab to configure the selected interface. Click the Apply button to save the
networking setting and to return to the Network Connections screen.
Figure 25
11- On the Networking Connections screen, click the Close button or press Alt+C, next
click the Next button or Alt+N to proceed.
Figure 26
12- On the Time Zone screen, select the time zone for your area by clicking your region on
the map. Accept the default System clock uses UTC setting, and click the Next button or
press Alt+N to proceed.
Figure 27
13- On the Root Password screen enter a root password for the server, then click the Next
button or press Alt+N to proceed.
Figure 28
14- On the Installation Type screen, you can select the desired partitioning layout or create
your own partitioning layout.
In this example, accept the default Replace Existing Linux System(s), click the Next
button or press Alt+N to proceed.
Note: To edit the default partitioning layout, select Review and modify partitioning
layout option and click Next or Alt+N.
Figure 29
15- A partition table Warning dialogue box will now appear. Click the Write changes to
disk or press Alt+W to proceed.
Figure 30
16- On the Software Selection screen, you can accept the default selections or select one or
more roles for the server and/or customize the entire software selection by selecting the
Customize now.
Oracle recommends installing Linux using the default software package selection without
any customization. Using the default software packages without customizations includes
most of the prerequisite packages and helps limit the number of manual checks.
Select the Desktop option without any customization, then click the Next button or press
Alt+N to proceed.
Figure 31
17- On the Installation Progress screen, you will see a dialogue box about the installation
starting. Once the Starting Installation process screen is gone, the installation begins and
you see the progress indicators. The installation will take a few minutes.
Figure 32
18- The Congratulations screen informs you that the installation is complete and to
remove your DVD media from the system and to reboot the system. Remove the CD/DVD
media from the system
Figure 33
At this point you would be advised to shutdown the VM using the VM Manager GUI
because the DVD is still listed first in the boot order for this VM. Go to the VM Manager
and right-click on our newly created Oracle Linux 6 VM and then left-click Stop. Wait for
the VM Manager to indicate that the VM is shutdown completely as indicated by a removal
of the lock icon and the VM icon now appearing in the color red. Right-click on the VM
and then left-click Edit. Click Next until you get to the Boot Order screen and remove the
DVD from the Boot Order. Click Next, then click Finish. You can now start the VM by
again right-clicking on the VM from the VM Manager GUI and selecting Start.
19- After the system reboots, you will be presented with the Welcome screen. Click the
Forward button or press Alt+F to proceed.
Figure 34
20- On the License Agreement screen, accept the license agreement and click the
Forward button or press Alt+F to proceed.
Figure 35
21- On the Set Up Software Updates screen, select the desired Unbrekable Linux
Network registration option, then click the Forward button or press ALT+F to proceed.
Figure 36
22- If you selected No from the previous screen, click the No thanks, I'll connect later.
button to proceed.
Figure 37
23- On the Finish Update Setup screen click the Forward button or press ALT+F to
proceed.
Figure 38
24- On the Create User screen, you can create new system users. Click the Forward
button or press Alt+F to proceed.
Figure 39
25- On the Date and Time screen you can configure the Date and Time and Network
Time Protocol (NTP) settings. Configure the Date and Time and Network Time
Protocol settings, then click the Forward button or press Alt+F to proceed.
Figure 40
26- On the Kdump screen, accept the default setting and click the Forward button or press
Alt+F to proceed.
Figure 41
27- On the Login screen, click on the desired user name and enter the password to access
the desktop.
Figure 42
28- Once you have successfully authenticated, you have a fully functional GNOME
desktop environment.
Figure 43
Oracle VM Manager 3.0: Oracle Linux 6 Installation using using Text Mode
After creating your Oracle Linux 6 VM using the VM Manager GUI you are now ready to
begin installation. If your VM has less than 1024MB of RAM then the installer will default
to text-mode. This section will guide you through the text-based installer for Oracle Linux
6.1.
From the Oracle VM Manager, right-click on your newly created VM and select “Start”.
After the VM has started, right-click again on the VM and select Start Console.
Figure 44
Press <Enter> to begin the Installation process.
We do not need to test the installation media, so select “Skip” and then press <Enter>.
Figure 45
This takes us to the Welcome screen. Press <Enter> to continue.
Figure 46
Choose your language, press <Tab> to highlight the OK button then press <Enter>.
Figure 47
Select the model of your keyboard, press <Tab> to highlight the OK button, then press
<Enter>.
Figure 48
Press <Tab> to highlight the Re-initialize button then press <Enter> to continue.
Figure 49
Use the default UTC (Coordinated Universal Time) if appropriate for your environment.
Select your Time Zone then press <Tab> to highlight the OK button then press <Enter>.
Figure 50
Define the root password for your new VM. Press <Tab> to highlight the OK button then
press <Enter>.
Figure 51
Partition using the entire drive, select the appropriate drive then press <Tab> to highlight
the OK button then press <Enter>.
Figure 52
Press <Tab> to highlight the Write changes to disk button then press <Enter>.
Figure 53
The installer now creates and formats the volume group and filesystems.
Figure 54
At this point, installation of your new Oracle Linux 6 VM will begin.
Figure 55
This is a Minimal Install so only the base 226 packages are now installed.
Figure 56
When you get to this screen, do not reboot.
Figure 57
Instead switch back to the VM Manager GUI and shutdown the Virtual Machine.
Figure 58
After the shutdown operation completes, you can right-click on the VM, select Edit, click
next until you get to the Storage Options. You can now uncheck the ISO image. You no
longer need it.
Figure 59
Under storage options you see that our Virtual disk is in the disk order.
Figure 60
Now, remove CDROM from the boot order. In its place add Disk. Click Finish. You are
now ready to start your newly installed VM for the first time by launching the console from
the VM Manager GUI.
To register your new VM to receive patches and updates from the Oracle Unbreakable
Linux Network run the uln_register command.
# uln_register
If your behind a proxy server, use the “--proxy” option to specify an http proxy, i.e. “#
uln_register –proxy=<HOST NAME>:<PORT NUMBER> “
If your proxy server requires authentication, use the “--proxyUser” and “--proxyPassword”
to add a username and password, i.e “# uln_register –proxy=<HOST NAME>:<PORT
NUMBER> --proxyUser=<USER NAME> --proxyPassword=<PASSWORD>”
Oracle VM Manager 3.0: How to Add a Virtual Disk From the VM Manager GUI, select Home, then Server Pools, then Repositories and
choose the appropriate repository.
Figure 61
Next, select Virtual Disks. Click the Create Virtual Disk icon.
Figure 62
From the Create Virtual Disk screen give the virtual disk a name using your organization's
standardized naming convention and size the virtual disk. Click OK and wait for the Job to
complete.
Figure 63
Now right-click on the VM for which you wish to add an additional virtual disk and select
Edit. Note: you cannot complete this action on a running VM so make sure the VM has
been powered down first. Click Next until you get to the Storage Options and select the
newly created virtual disk. Click Next and then Finish.
Figure 64
When this Job completes you may start the VM, logon via the console or SSH and take the
appropriate steps to create a filesystem and mount the filesystem. Use the case below as a
starting point.
# fdisk -l
Disk /dev/xvda: 16.0 GB, 16000000000 bytes
255 heads, 63 sectors/track, 1945 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000ccd59
Device Boot Start End Blocks Id System
/dev/xvda1 * 1 64 512000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/xvda2 64 1946 15111168 8e Linux LVM
Disk /dev/xvdb: 50.0 GB, 50000000000 bytes
255 heads, 63 sectors/track, 6078 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000b3029
Device Boot Start End Blocks Id System
Disk /dev/mapper/VolGroup-lv_root: 13.4 GB, 13358858240 bytes
255 heads, 63 sectors/track, 1624 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_root doesn't contain a valid partition table
Disk /dev/mapper/VolGroup-lv_swap: 2113 MB, 2113929216 bytes
255 heads, 63 sectors/track, 257 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_swap doesn't contain a valid partition table
Here we see our newly created virtual disk /dev/xvdb, size 50GB.
# fdisk /dev/xvdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0x51b17688.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
switch off the mode (command 'c') and change display units to
sectors (command 'u').
Command (m for help): p
Disk /dev/xvdb: 50.0 GB, 50000000000 bytes
255 heads, 63 sectors/track, 6078 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x51b17688
Device Boot Start End Blocks Id System
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-6078, default 1):
Using default value 1
Last cylinder, +cylinders or +size{K,M,G} (1-6078, default 6078):
Using default value 6078
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
Create a partition using the fdisk tool. In this case we choose to use all of partition 1.
# pvcreate /dev/xvdb1
Physical volume "/dev/xvdb1" successfully created
# vgcreate vg0 /dev/xvdb1
Volume group "vg0" successfully created
# lvcreate -n lvol0 -l 100%FREE vg0
Logical volume "lvol0" created
# mkfs.ext4 /dev/vg0/lvol0
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
3055616 inodes, 12205056 blocks
610252 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
373 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 33 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
# mkdir /u01
# echo "/dev/vg0/lvol0 /u01 ext4 defaults 0 0" >> /etc/fstab
# mount /u01
# mount
/dev/mapper/VolGroup-lv_root on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0")
/dev/xvda1 on /boot type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
/dev/mapper/vg0-lvol0 on /u01 type ext4 (rw)
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup-lv_root
13G 764M 11G 7% /
tmpfs 495M 0 495M 0% /dev/shm
/dev/xvda1 485M 48M 412M 11% /boot
/dev/mapper/vg0-lvol0
46G 180M 44G 1% /u01
Create the Physical Volume, Volume Group and Logical Volume. Make an ext4 filesystem
on the logical volume. Add the filesystem to your /etc/fstab file so the newly created
filesystem is mounted automatically on reboot. Create the mount point and finally, mount
your new filesystem. Congratulations.
Oracle VM Manager 3.0: How to Add a Virtual Network Interface From the VM Manager GUI, right-click on your VM and select Edit. Note: you cannot
make changes to a running VM so shut it down before you begin this process.
From the Edit Virtual Machine screen, click next to access the Network Options screen.
Select a free VNIC and click the Add button to move it to the Selected Value(s) window.
Click Finish.
Figure 65
Now start your VM and then Console or SSH into it.
# cd /etc/sysconfig/network-scripts
# cp ifcfg-eth0 ifcfg-eth1
# vi ifcfg-eth1
# ifup eth1
Determining IP information for eth1... done.
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:21:F6:00:00:0F
inet addr:192.168.4.127 Bcast:192.168.4.255 Mask:255.255.255.0
inet6 addr: fe80::221:f6ff:fe00:f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1906 errors:0 dropped:0 overruns:0 frame:0
TX packets:1017 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:138940 (135.6 KiB) TX bytes:639453 (624.4 KiB)
Interrupt:243
eth1 Link encap:Ethernet HWaddr 00:21:F6:00:00:0A
inet addr:192.168.4.126 Bcast:192.168.4.255 Mask:255.255.255.0
inet6 addr: fe80::221:f6ff:fe00:a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:50 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3349 (3.2 KiB) TX bytes:1280 (1.2 KiB)
Interrupt:242
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
When you edit the ifcfg-eth1 file make sure to update the MAC Address to reflect the new
device, ie HWADDR="00:21:F6:00:00:0A", in this example.
Linux Patch Management with Free Updates and Errata from Oracle In March 2012, Oracle announced that Oracle Linux 4, 5 and 6 latest RPM patches, updates
and erratas are available at no cost from separate yum repositories on http://public-
yum.oracle.com. To to keep Oracle Linux and Red Hat Enterprise Linux system up to date
to the latest update version, subscribe hosts to their respective "_latest" repository. The free
Oracle Linux 4, 5 and 6 RPM patches, updates and erratas do not include Oracle support or
any of the benefits of the Oracle Linux Support program.
The Oracle Linux Support program offers the following benefits over and above the free
Oracle Linux RPM patches, updates and erratas:
Full indemnification against intellectual property claims. Remember the SCO law suits?
Use of the Oracle Enterprise Manager 12c Systems Management Plug-in for Linux for
provisioning, patching, management and monitoring. The Systems Management Plug-in for
Linux has feature parity with Red Hat Satellite Server.
Access to additional Oracle software channels on the Unbreakable Linux Network (ULN).
The ability to create Support Requests with Oracle' World Class support organization.
The Oracle public yum server latest RPM channels include the base OS version installation
RPM packages along with the latest software patches, updates and fixes. Patch jobs using
the latest RPM channel update hosts to their respected latest version update with the latest
software patches, updates and fixes. A patch job executed on a Oracle Linux 6 host would
update the host from 6 to 6U2 with the latest latest software patches, updates and fixes. To
keep a host at its respected update level, access to the Unbreakable Linux Network Rpm
channels is required where it is possible to remove the default “el*/ol*_latest” RPM
channel and select the el*/ol*_base along with the el*/ol*_patch RPM channel. When hosts
are patched using the el*/ol*_base and el*/ol*_patch RPM channels, the hosts are patched
with the latest software patches, updates and fixes from their respected update channel, i.e.
6, 6U1, 6U2.
To configure an Oracle Linux, Red Hat Enterprise Linux 6 host to use Oracle's public yum
repository, as root, change to the /etc/yum.repos.d/ directory and type “wget http://public-
yum.oracle.com/public-yum-ol6.repo” to download the public-yum-ol6.repo file. Next,
type “yum update” to patch the host.
The next example shows how to download the public-yum-ol6.repo file from Oracle and to
update an Oracle Linux or Red hat Enterprise Linux host. Type the following commands as
root:
# cd /etc/yum.repos.d/
# wget http://public-yum.oracle.com/public-yum-ol6.repo
# yum update
The next examples shows the public-yum-ol6.repo file.
Tip: You can enable any of the repositories in the public-yum-ol6.repo file by changing
enabled=0 to enabled=1.
# vi /etc/yum.repos.d/public-yum-ol6.repo
[ol6_latest]
name=Oracle Linux $releasever Latest ($basearch)
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6
gpgcheck=1
enabled=1
[ol6_ga_base]
name=Oracle Linux $releasever GA installation media copy ($basearch)
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/0/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6
gpgcheck=1
enabled=0
[ol6_u1_base]
name=Oracle Linux $releasever Update 1 installation media copy ($basearch)
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/1/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6
gpgcheck=1
enabled=0
[ol6_u2_base]
name=Oracle Linux $releasever Update 2 installation media copy ($basearch)
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/2/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6
gpgcheck=1
enabled=0
[ol6_UEK_latest]
name=Latest Unbreakable Enterprise Kernel for Oracle Linux $releasever ($basearch)
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/UEK/latest/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6
gpgcheck=1
enabled=0
[ol6_UEK_base]
name=Unbreakable Enterprise Kernel for Oracle Linux $releasever ($basearch)
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/UEK/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6
gpgcheck=1
enabled=0
Oracle VM Manager 3.0: How to Delete a Virtual Machine You can only delete a VM that is in Stop or Error state. If you're dead set on getting rid of a
VM, simple right-click on the VM to remove and select Delete. Choose any Virtual Disks
you also wish to delete and click OK. All files and properties associated with this VM
should now be deleted.
Tip: We have seen it happen that the Virtual Machine is still seen inside the VM Manager
GUI after deleting the Virtual Machine using the above process. As a workaround, we were
finally able to delete the problem VM by right-clicking on the VM, selecting Edit and then
clicking Next, removing all associated Vnic's, Boot Order devices and Virtual Disks
manually, then clicking Save. At this point we were able to successfully delete the VM.
Oracle Desktop Virtualization Security Solution at DISA Mission Partner Conference 2012
building an appliance? physical ? virtual? production quality? use Oracle Linux
understanding memory allocation in oracle vm / xen
Oracle VM Administration: Oracle VM Server for x86 course schedule
figuring out cpu topology in oracle vm
Collaborate12 Starts Today!
Oracle VM Administration: Oracle VM Server for x86 - new Training
More Oracle VM templates for PeopleSoft and Oracle Enteprise Manager
Oracle Ebusiness Suite 12.1.3 Oracle VM templates
Eight New Oracle Database Assemblies Ready to Run In Your Oracle VM Cloud with
Oracle Enterprise Manager 12c
Oracle Enterprise Manager 12c
Architecture, System Design and Sizing
Show a printer friendly, save as PDF version of the Oracle Cloud Cookbook
Distribution of the Oracle Cloud Cookbook or derivative of the work in any form for
commercial purposes is prohibited unless prior permission is obtained from the copyright
holder.
Author: Roddy Rodstein
Table of Contents Change Log
Oracle Enterprise Manager 12c Architecture and System Design
Oracle Enterprise Manager 12c Inter Component Communication and Data Exchange
Oracle Enterprise Manager 12c Server Sizing
Oracle Enterprise Manager 12c System Design Considerations
Change Log
Revision Change Description Updated By Date
1.0 Oracle Enterprise Manager 12c Architecture, System
Design and Sizing
Roddy
Rodstein 10/22/11
Oracle Enterprise Manager 12g Architecture and System Design Oracle Enterprise Manager 12c Cloud Control is Oracle's private and/or public cloud
systems management solution for the entire Oracle stack. Oracle Enterprise Manager 12c is
a systems management framework with product specific plug-ins for Oracle and non-
Oracle technologies. Systems are managed and monitored from a Web GUI named Oracle
Enterprise Manager 12c Cloud Control.
Firgue 1 shows Oracle Enterprise Manager 12c Cloud Control.
Oracle Enterprise Manager 12c is a systems monitoring and administration framework
consisting of an Oracle database, Oracle WebLogic, a J2EE application, an application
development frame work 11g (ADF) administrative Web GUI, server and client side plug-
ins, and a client side agent. In the context of Oracle Enterprise Manager, the Oracle
database repository is named the “Oracle Management Repository” or “OMR”. WebLogic
is the J2EE platform called the “Oracle Management Service” or “OMS”, that runs the
Oracle Enterprise Manager 12c J2EE application. The administrative Web GUI is named
Oracle Enterprise Manager Cloud Control. The client side agents are named the “Oracle
Management Agents” or “OMA”. The server and client side plug-ins share a unique name
for the managed product or technology. For example, the server and client plug-ins for
Oracle VM 3.0 are named Oracle Virtualization. Monitored hosts are referred to as targets.
All of the Oracle Enterprise Manager components are commonly referred to as Oracle
Enterprise Manager (OEM) or Enterprise Manager (EM).
The Oracle Management Repository is a Standard Edition or Enterprise Edition Oracle 11g
Database that stores all of the information collected by the Oracle Management Agents and
Plug-ins. The Oracle Management Agent and plug-ins are software applications that runs
on all monitored hosts facilitating a two-way communication between the hosts and the
Oracle Management Service. The Oracle Management Service is deployed on a WebLogic
server or a cluster of WebLogic servers in the Oracle Middleware home. The Oracle
Middleware home is the parent directory of the Oracle WebLogic Server home. The Oracle
Management Service collects XML data from the Oracle Management Agents and plug-ins,
and uploads the data into the Oracle Management Repository. The Oracle Management
Repository formats the data and the Oracle Management Service visualizes the data in
Oracle Enterprise Manager 12c Cloud Control. Administrative operations made using
Oracle Enterprise Manager 12c Cloud Control are dispatched to targets from the Oracle
Management Service. Oracle Enterprise Manager Cloud Control can be access using
Firefox, Safari, Chrome and Internet Explorer on Linux, MAC, Unix and Windows
workstations.
The Oracle Management Repository, the Oracle Management Service along with the Oracle
Management Agent can be installed on a single host in an all-in-one configuration for
evaluations or in an n-tier configuration for production. Traditionally, production Oracle
Enterprise Manager environments are not be placed on a single server, nor should the
Oracle Management Repository be shared with production or test databases on the same
server.
Figure 2 shows a traditional multiple node Oracle Enterprise Manager 12c installation with
the Oracle Management Repository hosted on a two-node RAC cluster, the Oracle
Management Service hosted on a two-node WebLogic cluster with three monitored Oracle
Linux hosts with the Oracle Management Agent.
Figure 2
Each of the Oracle Enterprise Manager components can be installed using the Oracle
Universal Installer (OUI) GUI, or using silent installation scripts, or with the software only,
configure later installation mode. The software only installation mode allows you to install
only the Oracle Enterprise Manager software binaries without any configurations. The
software only installation mode is ideal if you want to install the software at one point and
configure the software later.
Oracle Enterprise Manager 12c Inter Component Communication and Data
Exchange Oracle Enterprise Manager 12c Could Control, the Oracle Management Repository, the
Oracle Management Service and the Oracle Management Agents and Plug-ins can be on
different hosts throughout your enterprise. Understanding Oracle Enterprise Manager's intra
component communication and data exchange will help you configure your firewalls in
order to allow Oracle Enterprise Manager to operate in your enterprise. During the Oracle
Enterprise Manager installation, the default communication ports for each component will
be selected and assigned. If the default ports are modified be sure to use the new port
assignments when you configure your firewalls.
Table 1 shows the default ports used by Oracle Enterprise Manager.
Service Default Port
Enterprise Manager Upload HTTP Port 4889 - 4898
Service Default Port
Enterprise Manager Upload HTTPS (SSL)
Port
1159, 4899 - 4908
Management Agent Port 3872
Management Repository Database Port 1521
Cloud Control Console HTTP Port 7788 - 7798
Cloud Control Console HTTPS (SSL) Port 7799 -7809
EM Domain WebLogic Admin Server HTTP
Port
7001
EM Domain WebLogic Admin Server HTTPS
(SSL) Port
7101 - 7200
Cloud Control Managed Server HTTP Port 7201 - 7300
Cloud Control Managed Server HTTPS (SSL)
Port
7301 - 7400
WebLogic Node Manager HTTPS (SSL) Port 7401 - 7500
JVM Diagnostics Managed Server 3800
JVM Diagnostics Managed Server (SSL) 3801
Application Dependency and Performance
RMI Registry Port
51099
Application Dependency and Performance
Java Provider Port
5503
Application Dependency and Performance
Remote Service Controller Port
55000
Oracle Enterprise Manager 12c Server Sizing Oracle Enterprise Manager 12c server sizing is calculated by a) total number of managed
agents and targets, b) the future growth of your Oracle Enterprise Manager environment
and c) your organization's high availability requirements. For example, if you know the
total number of managed agents and targets, sizing WebLogic and the Oracle database is as
simple as following Table 2, Table 3 and Table 4. As you add more agents and targets, it is
important to consider the future growth of your Oracle Enterprise Manager environment as
well as the ability to scale up or to scale out with additional CPU, RAM and storage.
Table 2 shows the minimum physical memory and storage requirements for the WebLogic
server hosting the Oracle Management Service and the Oracle Management Agent.
Installation Type Physical Memory (RAM) Storage
Oracle Management Service *6 GB 10 GB
Oracle Management Agent
* To use BI Publisher add 1.5 GB of RAM.
Table 3 shows the recommended Oracle Management Service minimum RAM and CPU
cores requirements for WebLogic along with the recommended number of WebLogic hosts
for a small, medium and large number of agents and targets.
Deployment Size RAM Intel or AMD
CPU Cores Hosts
Small < 100 agents < 1000 targets *6 GB 2 1
Medium < 1000 agents < 10,000 targets *6 GB 4 1
Large > 1000 agents > 10,000 targets *6 GB 4 2
* To use BI Publisher add 1.5 GB of RAM.
Table 4 shows the minimum RAM, CPU cores, storage and the number of hosts for the
database server hosting the Oracle Management Repository..
Deployment Size RAM Intel or AMD CPU
Cores Storage Hosts
Small < 100 agents < 1000 targets 2 GB 2 62 GB 1
Medium < 1000 agents < 10,000
targets 4 GB 4 225 GB 1
Large > 1000 agents > 10,000
targets 6 GB 4 345 GB 2
Table 5 shows the minimum storage requirements for a standalone Oracle Management
Agent installation.
Platform Storage TMP Directory
Linux 32 bit 1.2 GB 400 MB
Linux x86_64 1.2 GB 400 MB
Oracle Enterprise Manager 12c System Design Considerations The Oracle Management Repository, the Oracle Management Service along with the Oracle
Management Agent can be installed on a single host in an all-in-one configuration for
evaluations or in an n-tier configuration for production. Traditionally, production Oracle
Enterprise Manager environments are not be placed on a single server, nor should the
Oracle Management Repository be shared with production or test databases on the same
server. For production, the Oracle Management Repository as well as WebLogic should be
on dedicated virtual or physical servers. If your Oracle Enterprise Manager environment
starts out small, make sure to have a plan to scale out your Oracle Enterprise Manager
infrastructure.
For the Oracle Management Repository, scaling out means moving to RAC for the Oracle
Management Repository database. An important consideration when scaling out an Oracle
Enterprise Manager environment, is to determine if the underlying hardware where the
Oracle Management Repository database runs is capable to transition to RAC? If the
hardware is not capable to transition to RAC, it is possible to move and/or export the
Oracle Management Repository database to a different system with more resources. If the
Oracle Management Repository is hosted on an Oracle VM virtual machine, transitioning
to RAC is a trivial operation.
Scaling out the WebLogic and Oracle Management Service tier entails adding a load
balancing (SLB) solution to front end multiple WebLogic servers hosting the Oracle
Management Service. Adding a load balancer with additional WebLogic servers introduces
a virtual host name for the WebLogic cluster. Introducing a virtual host name into an
existing Oracle Enterprise Manager environment will require a reconfiguration of all of
your Oracle Management Agents to resolve to the new virtual host name. Reconfiguring a
couple Oracle Management Agents is no trouble, although reconfiguring a lot of Oracle
Management Agents would demand a long service window. When you deploy Oracle
Enterprise Manager, consider using a virtual host name for the web tier.
An additional consideration when scaling out the WebLogic and Oracle Management
Service tier is to provision shared storage to hosts the XML files and the software library.
Next Ops Center Experts Webcast: Cloud Management
Cloud Control 12c released for Windows 64-bit
Testing in May: Keep the bugs away
Install Oracle VM Server 3
DB Startup Fails on WORKAREA_SIZE_POLICY
Integrate EM OPS Center 12c in EM Cloud Control 12c
Integrate EM OPS Center 12c, EM Cloud Control 12c and Oracle VM Manager
ON-DEMAND WEBCAST: Oracle Database Lifecycle Management with Oracle
Enterprise Manager 12c, Now Available
Using Metric Extensions in EM12c
Security On Top Of Security
Oracle Enterprise Manager 12c Server
Sizing Advisor
Version 1.0 - Copyright © 2012 Mokum Solutions, Inc. All rights reserved.
The Oracle Enterprise Manager 12c Server Sizing Advisor offers Oracle Enterprise
Manager 12c server sizing recommendations.
How to use Mokum Solutions, Inc.' Oracle Enterprise Manager 12c Server Sizing Advisor.
This is the first page, where you select the Oracle Enterprise Manager 12c deployment size.
The last page shows your Oracle Enterprise Manager server sizing results.
Deployment Size: *
Small < 100 agents < 1000 targets
Medium < 1000 agents < 10,000 targets
Large > 1000 agents > 10,000 targets
Legal Notice: The Oracle Enterprise Manager 12c Server Sizing Advisor tool is subject to change without notice and
is provided as-is without warranty of any kind, express or implied. Mokum Solutions, Inc. does not make any
representations regarding the use, validity, accuracy or reliability of the tool or the results of the use of the tool. The entire
risk arising out of the use of this tool remains solely with the customer. In no event shall Mokum Solutions, Inc. be liable
for any direct, consequential, incidental, special, punitive or other damages, even if Mokum Solutions, Inc. is negligent or
has been advised of the possibility of such damages, arising from use of the tool or the information provided herein.
Next Page >
Oracle Enterprise Manager 12c
Installation
Show a printer friendly, save as PDF version of the Oracle Cloud Cookbook
Copyright © 2012 Mokum Solutions, Inc. All rights reserved.
Distribution of the Oracle Cloud Cookbook or derivative of the work in any form for
commercial purposes is prohibited unless prior permission is obtained from the copyright
holder.
Author: Roddy Rodstein
Change Log
Revision Change Description Updated By Date
.1 Beta Release Roddy
Rodstein 12/02/11
1.0 First Release Roddy
Rodstein 12/11/11
1.1 .bash_profile Roddy
Rodstein 12/15/11
1.2 Replaced 12c Simple Installation with
Advanced
Roddy
Rodstein 12/23/11
Table of Contents Oracle Enterprise Manager 12c Installation Introduction
Oracle Enterprise Manager 12c Server Sizing
Oracle Linux Operating System Prerequisites
...oracle-validated RPM
...iptables
...SELinux
.../etc/hosts
...Adjust the Shared Memory File System for the Database Host
...Creat the Required Directories using the Optimal Flexible Architecture (OFA) Standard
...SSH and X11 Forwarding
Oracle Database 11g Enterprise Edition R2 (11.2.0.1.0) Installation
Automating Database Startup and Shutdown
Oracle Enterprise Manager 12c Installation
.bash_profile
Appendix
Oracle Enterprise Manager 12c Installation Introduction
Oracle Enterprise Manager 12c is a systems management framework consisting of an
Oracle database, Oracle WebLogic, a J2EE application, an application development frame
work 11g (ADF) administrative Web GUI, server and client side plug-ins, and a client side
agent. In the context of Oracle Enterprise Manager, the Oracle database repository is named
the “Oracle Management Repository” or “OMR”. WebLogic is the J2EE platform called
the “Oracle Management Service” or “OMS”, that runs the Oracle Enterprise Manager 12c
J2EE application. The administrative Web GUI is named Oracle Enterprise Manager Cloud
Control. The client side agents are named the “Oracle Management Agents” or “OMA”.
The server and client side plug-ins share a unique name for the managed product or
technology. Monitored hosts are referred to as targets. All of the Oracle Enterprise Manager
components are commonly referred to as Oracle Enterprise Manager (OEM) or Enterprise
Manager (EM).
The Oracle Management Repository, the Oracle Management Service along with the Oracle
Management Agent can be installed on a single x86-64 Linux host in an all-in-one
configuration for evaluations or in an n-tier configuration for production. Traditionally,
production Oracle Enterprise Manager environments are not be placed on a single server,
nor should the Oracle Management Repository be shared with production or test databases
on the same server. For production, the Oracle Management Repository as well as
WebLogic should be on dedicated virtual or physical servers. If your Oracle Enterprise
Manager environment starts out small, make sure to have a plan to scale out your Oracle
Enterprise Manager infrastructure.
As of this writing, Oracle Enterprise Manager 12c Release 1 (12.1.0.1) is supported on the
following Linux x86-64 operating systems:
Oracle Linux 5.x (5.x means 5.0 through 5U7)
Red Hat Enterprise Linux 5.x
Asianux 3
SUSE Linux Enterprise 10 and 11
This chapter uses Oracle Linux 5.x for the Oracle Enterprise Manager 12c installation.
As of this writing, the Oracle Management Repository is certified with the following
database releases:
Oracle 11.2.0.3.0
Oracle 11.2.0.2.0
Oracle 11.2.0.1.0
Oracle 11.1.0.7.0
Oracle 10.2.0.5.0
Tip: Please review the preveious chapter Oracle Enterprise Manager 12c Architecture,
System Design and Sizing for architecture, system design and sizing recomendations.
Figure 1 shows a traditional multiple node Oracle Enterprise Manager 12c installation with
the Oracle Management Repository hosted on a two-node RAC cluster, the Oracle
Management Service hosted on a two-node WebLogic cluster with three monitored Oracle
Linux hosts with the Oracle Management Agent.
Each of the Oracle Enterprise Manager 12c components can be installed using the Oracle
Universal Installer (OUI) GUI, or using silent installation scripts, or with the software only,
configure later installation mode. The software only installation mode allows you to install
only the Oracle Enterprise Manager software binaries without any configurations. The
software only installation mode is ideal if you want to install the software at one point and
configure the software later.
Note: This chapter reviews the Oracle Universal Installer (OUI) installation mode.
Oracle Enterprise Manager 12c Server Sizing
Oracle Enterprise Manager 12c server sizing is calculated by a) total number of managed
agents and targets, b) the future growth of your Oracle Enterprise Manager environment
and c) your organization's high availability requirements. For example, if you know the
total number of managed agents and targets, sizing WebLogic and the Oracle database is as
simple as following Table 2, Table 3 and Table 4. As you add more agents and targets, it is
important to consider the future growth of your Oracle Enterprise Manager environment as
well as the ability to scale up or to scale out with additional CPU, RAM and storage.
Table 1 shows the minimum physical memory and storage requirements for the WebLogic
server hosting the Oracle Management Service and the Oracle Management Agent.
Installation Type Physical Memory (RAM) Storage
Oracle Management Service *6 GB 10 GB
Oracle Management Agent
* To use BI Publisher add 1.5 GB of RAM.
Table 2 shows the recommended Oracle Management Service minimum RAM and CPU
cores requirements for WebLogic along with the recommended number of WebLogic hosts
for a small, medium and large number of agents and targets.
Deployment Size RAM Intel or AMD
CPU Cores Hosts
Small < 100 agents < 1000 targets *6 GB 2 1
Medium < 1000 agents < 10,000 targets *6 GB 4 1
Large > 1000 agents > 10,000 targets *6 GB 4 2
* To use BI Publisher add 1.5 GB of RAM.
Table 3 shows the minimum RAM, CPU cores, storage and the number of hosts for the
database server hosting the Oracle Management Repository..
Deployment Size RAM Intel or AMD CPU
Cores Storage Hosts
Small < 100 agents < 1000 targets 2 GB 2 62 GB 1
Medium < 1000 agents < 10,000
targets 4 GB 4 225 GB 1
Large > 1000 agents > 10,000
targets 6 GB 4 345 GB 2
Table 4 shows the minimum storage requirements for a standalone Oracle Management
Agent installation.
Platform Storage TMP Directory
Linux 32 bit 1.2 GB 400 MB
Linux x86_64 1.2 GB 400 MB
Oracle Linux Operating System Prerequisites
Oracle recommends installing Oracle Linux and Red Hat Enterprise using the default
software package selection without any customization. Using the default software packages
without customizations includes most of the prerequisite packages for Oracle Enterprise
Manager 12c and helps limit the number of manual prerequisite checks. After an Oracle
Linux and/or Red Hat Enterprise Linux installation, Oracle recommends to register your
server with the Unbreakable Linux Network (ULN) and to install the Legacy Software
Development packages by typing “up2date -i @ Legacy Software Development“ or if you
have a local yum repository type “yum groupinstall "Legacy Software Development"” to
install most of the remaining Oracle technology product prerequisite packages. Once the
Legacy Software Development packages are installed, install the oracle-validated RPM to
meet all of the remaining Oracle Enterprise Manager 12c prerequisite packages.
oracle-validated RPM The oracle-validated RPM simplifies meeting the software and system configuration
prerequisites for installing the Oracle Enterprise Manager 12c Infrastructure and the Oracle
Database. Installing the oracle-validated RPM automatically installs all of the software
RPM prerequisites for the Oracle Enterprise Manager 12c Infrastructure and the Oracle
Database as well as meeting the system configuration prerequisites, such as creating an
oracle user and the oinstall and dba groups, configuring the sysctl.conf settings, system
startup parameters, user limits, and driver parameters.
The oracle-validated RPM is available at the Oracle Unbreakable Linux Network, on the
Oracle Linux media, and from the Oracle public yum repository. The oracle-validated RPM
can be installed from the Oracle Unbreakable Linux Network by typing "up2date --install
oracle-validated", ULN registration and a valid Linux CSI is required. If you do not have
access to Oracle Unbreakable Linux Network, the oracle-validated RPM can be installed
from a local DVD repository as well as from Oracle' public yum repository.
Oracle Linux maintains yum repository lists in the /etc/yum.repos.d/ directory. For
example, to setup a DVD repository, mount the Oracle Linux 5.x DVD, and create a file in
the /etc/yum.repos.d/<MY FILE>.repo directory that instructs the yum client to use the
DVD repository. The next examples shows the syntax of a .repo file pointing to a mounted
Oracle Linux DVD in the /mnt/dvd/ directory.
# cat /etc/yum.repos.d/ol-5U7-dvd.repo
[ol5_u7_dvd]
name=Oracle Linux $releasever - $basearch
baseurl=file:///mnt/dvd/Server/
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oracle
Before installing the oracle-validated RPM, clean the yum cache by typing “yum clean all”
to re-read the repodata and caches. Once the DVD is mounted and the <MY FILE>.repo
file is created, type “yum install oracle-validated” to install the oracle-validated RPM.
To install the oracle-validated RPM from the public yum repository, as root, change to the
/etc/yum.repos.d/ directory and type “wget http://public-yum.oracle.com/public-yum-
el5.repo” to download the public-yum-el5.repo file. Next, edit the public-yum-el5.repo file
and enable the base repository for your Oracle Linux version by changing enabled=0 to
enabled=1.
The next examples shows the public-yum-el5.repo file.
# vi /etc/yum.repos.d/public-yum-el5.repo
[el5_ga_base]
name=Enterprise Linux $releasever GA - $basearch - base
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/0/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[el5_u1_base]
name=Enterprise Linux $releasever U1 - $basearch - base
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/1/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[el5_u2_base]
name=Enterprise Linux $releasever U2 - $basearch - base
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/2/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[el5_u3_base]
name=Enterprise Linux $releasever U3 - $basearch - base
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/3/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[el5_u4_base]
name=Enterprise Linux $releasever U4 - $basearch - base
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/4/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[el5_u5_base]
name=Enterprise Linux $releasever U5 - $basearch - base
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/5/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[ol5_u5_base]
name=Oracle Linux $releasever - U5 - x86_64 - base
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL5/5/base/x86_64/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[ol5_u6_base]
name=Oracle Linux $releasever - U6 - $basearch - base
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL5/6/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[ol5_u7_base]
name=Oracle Linux $releasever - U7 - $basearch - base
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL5/7/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[el5_addons]
name=Enterprise Linux $releasever - $basearch - addons
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/addons/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[el5_oracle_addons]
name=Enterprise Linux $releasever - $basearch - oracle_addons
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/oracle_addons/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
Tip: Enable a repository by changing enabled=0 to enabled=1. Enable the base repository
for the Oracle Linux version being used. The next examples shows how to enable the
Oracle Linux 5U7 base repository.
[ol5_u7_base]
name=Oracle Linux $releasever - U7 - $basearch - base
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL5/7/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=1
The next examples shows how to enable the Oracle Linux 5U6 base repository.
[ol5_u6_base]
name=Oracle Linux $releasever - U6 - $basearch - base
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL5/6/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=1
Once you have enabled the desired base repository by changing enabled=0 to enabled=1,
clean the yum cache by typing “yum clean all” to re-read the repodata and caches. Next,
type “yum install oracle-validated” to install the oracle-validated RPM.
iptables iptables is a userspace firewall application used to configure the Linux IPv4 and IPv6
packet filtering rulesets. iptables is installed and enabled by default on Oracle Linux with a
default policy and ruleset in /etc/sysconfig/iptables. iptables rules can be configured at the
command line as well as with the system setup utility, i.e. "/usr/bin/setup".
Host firewalls, for example iptables, are a fundamental part of an information security
program. If your information security program requires host firewalls, a best practice is to
configure host firewalls during the last phase of the Enterprise Manager deployment.
iptables can be disabled by typing the following command as root.
# service iptables stop && service ip6tables stop && chkconfig iptables off && chkconfig
ip6tables off
iptables can be re-inabled by typing the following command as root.
# service iptables start && service ip6tables start && chkconfig iptables on && chkconfig
ip6tables on
SELinux Security Enhanced Linux (SELinux) is a default Linux feature that offers mandatory access
controls, using Linux kernel security modules (LSM) along with user-space tools. Starting
with Oracle Database 11g Release 2 (11.2), Security Enhanced Linux is supported for
Oracle Linux 4, Red Hat Enterprise Linux 4, Oracle Linux 5, and Red Hat Enterprise Linux
5. Security Enhanced Linux is not supported for the Oracle Enterprise Manager 12c Oracle
Management Service.
Mandatory access controls, for example Security Enhanced Linux, may be a part of your
organizations information security program. If your information security program requires
mandatory access controls for the 12c Oracle Management Repository, a best practice is to
configure Security Enhanced Linux during the last phase of the Enterprise Manager
deployment.
Security Enhanced Linux can be temporarily disabled by typing "echo 0 >
/selinux/enforce", as root. Security Enhanced Linux can be re-enabled by typing "echo 1 >
/selinux/enforce", as root.
Security Enhanced Linux can be permanently disabled by changing the
"SELINUX=enforcing" entry to "SELINUX=disabled" in the "/etc/selinux/config" file.
Security Enhanced Linux can be re-enabled by changing the "SELINUX=disabled" entry to
"SELINUX=enforcing" in the "/etc/selinux/config" file. A re-boot is required after
changing the "SELINUX=” value to enable to new settings.
/etc/hosts Oracle technology products, including Oracle Enterprise Manager, rely on a properly
formatted /etc/hosts file which allows the host to be pingable, with long and short host
names. The host name in the /etc/hosts file must be associated with the server's public IP
address.
The next example shows the proper syntax from a /etc/hosts file. Note that the localhost
entries are one one line, and the IP address with the long and short names are on the next
line.
127.0.0.1 localhost.localdomain localhost
192.168.4.8 servername.com servername
The next example shows an improperly formatted /etc/hosts file. Note that the long and
short names are on the same line as the localhost entries.
127.0.0.1 servername.com servername localhost.localdomain localhost
192.168.4.8 servername.com servername
The /etc/hosts file can be edited by the root user bu typing “vi /etc/hosts”, as shown in the
next example.
# vi
127.0.0.1 localhost.localdomain localhost
192.168.4.8 servername.com servername
:wq!
Adjust the Shared Memory File System for the Database Host To meet the Oracle Management Repository configuration requirements, the shared
memory file system size should be increased to 4 GB.
Note: The shared memory file system size needs to be increased only on the Database host.
To check the current size of the shared memory file system, type “df -k /dev/shm” as shown
in the next example.
# df -k /dev/shm
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 3056052 0 3056052 0% /dev/shm
The above examples shows a 3 GB shared memory file system.
To set the shared memory file system size to 4 GB, as root, type the following commands.
# umount tmpfs
# mount -t tmpfs shmfs -o size=4g /dev/shm
Next, add the following entry in /etc/fstab to automatically mount the 4 GB shared memory
file system.
tmpfs /dev/shm tmpfs size=4g 0 0
Creat the Required Directories using the Optimal Flexible Architecture (OFA)
Standard The Optimal Flexible Architecture (OFA) standard is a set of file naming recommendations
for managing Oracle installations. The Optimal Flexible Architecture standard offers mount
point, directory, and file-naming conventions that work with the Oracle Universal Installer.
The Optimal Flexible Architecture includes where to install each part of each Oracle
product including the storage of the applications and the data.
To create the directories for Oracle software installation using the Optimal Flexible
Architecture standard, as root, type the following commands.
# mkdir -p /u01/app/oracle/product/
# chown -R oracle:oinstall /u01
# chmod -R 775 /u01
SSH and X11 Forwarding Installing the Oracle Enterprise Manager 12c components using the Oracle Universal
Installer (OUI) GUI requires local or remote access to the server' console or a remote X
Windows (X11) session. This section reviews how to configure Oracle Linux to install the
Oracle Enterprise Manager 12c components remotely, using ssh and X11 forwarding.
SSH and X11 forwarding enables the redirection of an X11 session from a remote Oracle
Linux machine to a local desktop. For example, from a local desktop, ssh to a remote
Oracle Linux server using X11 forwarding and run the Oracle Universal Installer, i.e. by
typing “./runInstaller”. The Oracle Universal Installer will be displayed on the local desktop
and the Oracle Enterprise Manager 12c components can be installed on the remote Oracle
Linux server.
On the Oracle Linux server, enable X11 forwarding in the /etc/ssh/sshd_config by adding
"ForwardX11 yes" to the file as shown in the next example.
Change
#X11Forwarding no
to
X11Forwarding yes
Once the "ForwardX11 yes" entry has been added to the /etc/ssh/sshd_config file, restart
ssh by typing "service sshd restart" to enable X11 forwarding. With X11 forwarding
enabled, the Oracle Universal Installer (OUI) GUI can be exported from the Oracle Linux
server to your local desktop.
To enable X11 forwarding from a Linux desktop, use the "-X" switch with ssh. For
example, type "ssh -X oracle@<ORACLE LINUX SERVER>" to create a ssh tunnel with
X11 forwarding. If your using a Windows PC, a PC X Server like XMing is required to run
an X Windows session, along with an ssh client like putty that supports X11 forwarding.
Oracle Database 11g Enterprise Edition R2 (11.2.0.1.0) Installation This section walks through the installation of Oracle Database 11g Release 2 (11.2.0.2.0)
using the Oracle Universal Installer (OUI) on Oracle Linux 5U7.
With the software downloaded and staged for the Oracle Linux host, as the oracle user, run
the runInstaller script by typing "./runInstaller" as shown in the next example.
# ssh -X oracle@<DATABASE HOST>
$ cd /u01/app/stage/database
$ ./runInstaller
Starting Oracle Universal Installer...
Checking Temp space: must be greater than 120 MB. Actual 3967 MB Passed
Checking swap space: must be greater than 150 MB. Actual 6189 MB Passed
Checking monitor: must be configured to display at least 256 colors. Actual 16777216
Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2011-11-30_04-53-
29PM. Please wait ...
On the Configure Security Updates screen, to receive support information (optional),
enter your email address and My Oracle Support password and click the Next button, or
uncheck the I wish to receive security updates via My Oracle Support checkbox and
click the Next button.
Figure 2
On the Select Install Option screen, select Create and configure a database. Click the
Next button to proceed.
Figure 3
On the System Class screen, select the Server Class option. Click the Next button to
proceed.
Figure 4
On the Node Selection screen, select the Single instance database installation option.
Click the Next button to proceed.
Figure 5
On the Select Install Type screen, select the Tipical install option. Click the Next button
to proceed.
Figure 6
On the Typical Install Configuration screen, accept the defaults, enter a Administrative
password. Click the Next button to proceed.
Figure 7
On the Summary screen, click the Finish button to start the product installation.
Figure 8
The Install Product screen shows the installation progress.
Note: The Install Product screen remains open until the last Finish screen.
Figure 9
The Database Configuration Assistant screen shows the progress of the database
configuration.
Figure 10
The second Database Configuration Assistant screen shows the database configurations.
Click the OK button to close the Database Configuration Assistant screen.
Figure 11
The Execute Configuration script screen appears and shows what scripts needs to be
executed as the root user.
Figure 12
Next, as root open a terminal and root.sh script.
# /u01/app/oracle/product/11.2.0/dbhome_1/root.sh
Running Oracle 11g root.sh script...
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /u01/app/oracle/product/11.2.0/dbhome_1
Enter the full pathname of the local bin directory: [/usr/local/bin]:
Copying dbhome to /usr/local/bin ...
Copying oraenv to /usr/local/bin ...
Copying coraenv to /usr/local/bin ...
Creating /etc/oratab file...
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root.sh script.
Now product-specific root actions will be performed.
Finished product-specific root actions.
Next, click OK to close the Execute Configuration script screen.
On the Install Product screen, click the Finish button to proceed.
Figure 13
The Finish screen shows the Enterprise Manager Database Control URL. Click the
Close button to close the installation program
Figure 14
Next, as the oracle user drop Enterprise Manager Database Control by typing the
following command. Substitute <sys pasword> with the sys password and <sysman
password> with the sysman password selected during the database installation.
$ emca -deconfig dbcontrol db -repos drop -SYS_PWD <sys pasword> -SYSMAN_PWD
<sysman password>
STARTED EMCA at Nov 22, 2011 1:44:08 PM
EM Configuration Assistant, Version 11.2.0.0.2 Production
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Enter the following information:
Database SID: orcl
Listener port number: 1521
Do you wish to continue? [yes(Y)/no(N)]: Y
Nov 22, 2011 1:44:23 PM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at
/u01/app/oracle/product/cfgtoollogs/emca/orcl/emca_2011_11_22_13_44_08.log.
Nov 22, 2011 1:44:23 PM oracle.sysman.emcp.util.DBControlUtil stopOMS
INFO: Stopping Database Control (this may take a while) ...
Nov 22, 2011 1:44:45 PM oracle.sysman.emcp.EMReposConfig invoke
INFO: Dropping the EM repository (this may take a while) ...
Nov 22, 2011 1:47:18 PM oracle.sysman.emcp.EMReposConfig invoke
INFO: Repository successfully dropped
Enterprise Manager configuration completed successfully
FINISHED EMCA at Nov 22, 2011 1:47:21 PM
Next, assess the database as sysdba and create a pfile from the spfile.
sqlplus / AS SYSDBA
create pfile from spfile;
Next, edit the database init file and change the *.memory_target parameter to 3221225472,
i.e. add a new line with "*.memory_target=3221225472" in the init file:
# vi /u01/app/oracle/product/11.2.0/dbhome_1/dbs/initorcl.ora
*.memory_target=3221225472
:wq!
Next, create a directory for the redo log files, as shown in the next example.
# mkdir /u01/app/oracle/product/redo_logs/
Next, access the database as sysdba and make the following initialization parameter
changes, then restart the database.
sqlplus / AS SYSDBA
ALTER SYSTEM SET processes=300 SCOPE=SPFILE;
System altered.
ALTER SYSTEM SET session_cached_cursors=200 SCOPE=SPFILE;
System altered.
ALTER SYSTEM SET sga_target=2G SCOPE=SPFILE;
System altered.
ALTER SYSTEM SET shared_pool_size=600M SCOPE=SPFILE;
System altered.
ALTER SYSTEM SET pga_aggregate_target=1G SCOPE=SPFILE;
System altered.
ALTER SYSTEM SET job_queue_processes=20 SCOPE=SPFILE;
System altered.
ALTER DATABASE force logging;
System altered.
ALTER TABLESPACE users FORCE LOGGING;
System altered.
EXEC dbms_auto_task_admin.disable('auto optimizer stats collection',null,null);
PL/SQL procedure successfully completed.
ALTER DATABASE ADD LOGFILE ('/u01/app/oracle/product/redo_logs/log1c.rdo',
'/u01/app/oracle/product/redo_logs/log2c.rdo',
'/u01/app/oracle/product/redo_logs/log3c.rdo') SIZE 100M;
System altered.
SHUTDOWN IMMEDIATE;
SQL> CREATE SPFILE FROM PFILE;
SQL> startup;
ORACLE instance started.
Total System Global Area 3206836224 bytes
Fixed Size 2217632 bytes
Variable Size 1744832864 bytes
Database Buffers 1442840576 bytes
Redo Buffers 16945152 bytes
Database mounted.
Database opened.
SQL> quit
Automating Database Startup and Shutdown There are several steps to automate the database startup and shutdown process with Oracle
Linux.
Once the database has been installed, a file called oratab is created in the /etc directory. The
oratab file has a Y/N flag to specify if the database should be re-started when the server
boots.
As root, edit the /etc/oratab file and change “N” to “Y”, as shown below.
The default setting is N, as shown in the next example.
orcl:/u01/app/oracle/product/11.2.0/dbhome_1:N
Change the N to Y, as shown in the next example.
orcl:/u01/app/oracle/product/11.2.0/dbhome_1:Y
The next example shows an oratab file from the above database installation with the Y flag.
# cat /etc/oratab
#
# This file is used by ORACLE utilities. It is created by root.sh
# and updated by the Database Configuration Assistant when creating
# a database.
# A colon, ':', is used as the field terminator. A new line terminates
# the entry. Lines beginning with a pound sign, '#', are comments.
#
# Entries are of the form:
# $ORACLE_SID:$ORACLE_HOME:<N|Y>:
#
# The first and second fields are the system identifier and home
# directory of the database respectively. The third filed indicates
# to the dbstart utility that the database should , "Y", or should not,
# "N", be brought up at system boot time.
#
# Multiple entries with the same $ORACLE_SID are not allowed.
#
#
orcl:/u01/app/oracle/product/11.2.0/dbhome_1:Y
Next, as root, create a database startup and shutdown script named dbora /etc/init.d. The
dboar script calls the dbstart and dbshut routines.
The next example show the dbora script.
# vi /etc/init.d/dbora
#!/bin/sh
# chkconfig: 345 99 10
# description: Oracle auto start-stop script.
#
# Set ORA_HOME to be equivalent to the $ORACLE_HOME
# from which you wish to execute dbstart and dbshut;
#
# Set ORA_OWNER to the user id of the owner of the
# Oracle database in ORA_HOME.
ORA_HOME=/u01/app/oracle/product/11.2.0/dbhome_1
ORA_OWNER=oracle
if [ ! -f $ORA_HOME/bin/dbstart ]
then
echo "Oracle startup: cannot start"
exit
fi
case "$1" in
'start')
# Start the Oracle databases:
# The following command assumes that the oracle login
# will not prompt the user for any values
su - $ORA_OWNER -c "$ORA_HOME/bin/dbstart $ORA_HOME"
touch /var/lock/subsys/dbora
;;
'stop')
# Stop the Oracle databases:
# The following command assumes that the oracle login
# will not prompt the user for any values
su - $ORA_OWNER -c "$ORA_HOME/bin/dbshut $ORA_HOME"
rm -f /var/lock/subsys/dbora
;;
esac
:wq!
After the script is created, set the privileges for dbora to 750, by typing “chmod 750
/etc/init.d/dbora”. The dbora script can now be configured as a Linux service.
Next, set the runlevels for the dbora service to 3, 4 and 5 by typing “chkconfig dbora on”.
Typing “chkconfig --list|grep dbora” will validate the dbora script is on at runlevels 3, 4
and 5, as shown in the next example.
# chkconfig --list|grep dbora
dbora 0:off 1:off 2:on 3:on 4:on 5:on 6:off
The last step is to created soft links for init.d to automate the database startup and shutdown
process with Oracle Linux boot process. As root, type the following commands to create
the init.d soft links.
# ln -s /etc/init.d/dbora /etc/rc.d/rc0.d/K01dbora
# ln -s /etc/init.d/dbora /etc/rc.d/rc3.d/S96dbora
# ln -s /etc/init.d/dbora /etc/rc.d/rc5.d/S96dbora
Oracle Enterprise Manager 12c Installation
This section walks through an Advanced installation of the Oracle Enterprise Manager 12c
Release 1 (12.1.0.1) Oracle Management Service and the Oracle Management Agent using
the Oracle Universal Installer (OUI) on Oracle Linux 5U7.
Tip: Make sure that the Oracle user environmental variables are not set until after the
installation of Oracle Enterprise Manager. For example, do not setup the .bash_profile file
until after the installation of all the software. To temporarily unset the Oracle user
environmental variables, as the oracle user type "unset ORACLE_BASE ORACLE_HOME
EMDROOT AGENT_HOME OMS_HOME ORACLE_INSTANCE ORACLE_SID
ORACLE_UNQNAME ORACLE_TERM".
With the software downloaded and staged for the Oracle Linux host, as the oracle user, run
the runInstaller script by typing "./runInstaller" as shown in the next example.
# ssh -X oracle@<ORACLE MANAGEMENT SERVICE HOST>
$ cd /u01/app/stage/oem12c
$ ./runInstaller
Starting Oracle Universal Installer...
Checking Temp space: must be greater than 400 MB. Actual 3965 MB Passed
Checking swap space: must be greater than 150 MB. Actual 6160 MB Passed
Checking monitor: must be configured to display at least 256 colors. Actual 16777216
Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2011-12-01_11-13-
51AM. Please wait ...
On the My Oracle Support screen, to receive support information (optional), enter your
Email address and My Oracle Support Password and click the Next button, or uncheck
the I wish to receive security updates via My Oracle Support checkbox and click the
Next button.
Figure 15
On the Sofware Updates screen select Skip, then click the Next button to proceed.
Note: As of this writing there are no Oracle Enterprise Manager 12c updates.
Figure 16
On the Prerequisite Checks screen the installer checks the system prerequisites. Failed
steps can be fixed and be retested or just ignored. Click the Next button to proceed.
Figure 16
On the Installation Types screen select Advanced under Create a new Enterprise
Manager System. Next, in the Middelware Home Location text box type the path to the
Middleware Home, i.e. /u01/app/oracle/product/Middleware. Click the Next button to
proceed.
Figure 18
On the Select Plug-ins screen select the desired Plug-ins. To support subsequent chapters
of the Oracle Cloud Cookbook, please select Exalogic Elastic Cloud Infrastructure,
Oracle Chargeback and Capacity Planning, Oracle Cloud Application and Oracle
Virtualization. Click the Next button to proceed.
Figure 19
On the WebLogic Server Configuration Details screen enter the WebLogic User Name
and Password for the GCDomain and the Node Manager Password. Click the Next
button to proceed.
Figure 20
On the Database Connection Details screen enter the Database Host Name, the Database
Port number, the Database Service ID and the Database SYS Password. Click the Next
button to proceed.
Tip: Make sure that no Oracle environmental variables are set until after the installation of
the Oracle Management Manager. If the Oracle environmental variables are set, i.e. in the
~/.bash_profile file or by hand, the Configuration Details screen will generate errors.
Figure 21
On the Repository Configuration Details screen, enter the SYSMAN Password and the
OMA Registration Password. Accept the defaults for the Management Tablespace,
Configuration Data Tablespace and the IVM Diagnostics Data Tablespace. Click the
Next button to proceed.
Figure 22
From the Port Configuration Details screen accept the defaults and click the Next button
to proceed.
Figure 23
On the Review screen, click the Install button to start the product installation.
Figure 24
The Installation Progress Details screen shows the installation progress.
Note: The Installation Progress Details screen remains open until the last Finish screen.
Figure 25
The Execute Configuration script screen appears and shows what scripts needs to be
executed as the root user.
Figure 26
Next, as the root user open another terminal window to the host, and run the allroot.sh
script as shown in the next example.
# /u01/app/oracle/product/Middleware/oms/allroot.sh
Starting to execute allroot.sh .........
Starting to execute /u01/app/oracle/product/Middleware/oms/root.sh ......
Running Oracle 11g root.sh script...
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /u01/app/oracle/product/Middleware/oms
Enter the full pathname of the local bin directory: [/usr/local/bin]:
Copying dbhome to /usr/local/bin ...
Copying oraenv to /usr/local/bin ...
Copying coraenv to /usr/local/bin ...
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root.sh script.
Now product-specific root actions will be performed.
/etc exist
/u01/app/oracle/product/Middleware/oms
Finished execution of /u01/app/oracle/product/Middleware/oms/root.sh ......
Starting to execute /u01/app/oracle/product/Middleware/agent/core/12.1.0.1.0/root.sh ......
Finished product-specific root actions.
/etc exist
Finished execution of /u01/app/oracle/product/Middleware/agent/core/12.1.0.1.0/root.sh
......
Next, click OK to close the Execute Configuration script screen.
The Finish screen shows the location of the setupinfo.txt file and the URLs for Oracle
Enterprise Manager Cloud Control and the WebLogic Admin server.
Figure 27
Note: The details from the Finish screen are also available in the file setupinfo.txt file.
Click the Close button to close the installation program
The following examples how the setupinfo.txt file.
# cat /u01/app/oracle/product/Middleware/oms/install/setupinfo.txt
This information is also available at:
/u01/app/oracle/product/Middleware/oms/install/setupinfo.txt
See below for information pertaining to your Enterprise Manager installation:
Use the following URL to access:
1. Enterprise Manager Cloud Control URL: https://oem-tuvok.sf.mokum.com:7801/em
2. Admin Server URL: https://oem-tuvok.sf.mokum.com:7102/console
The following details need to be provided during the additional OMS install:
1. Admin Server Hostname: oem-tuvok.sf.mokum.com
2. Admin Server Port: 7102
NOTE:
An encryption key has been generated to encrypt sensitive data in the Management
Repository. If this key is lost, all encrypted data in the Repository becomes unusable.
Please run following command to backup the Management Service configuration including
the emkey and keep the backup on another system:
emctl exportconfig oms -dir <backup location>
Open a browser and enter the Enterprise Manager Cloud Control URL, i.e. https://<HOST
NAME>:7801/em. Enter sysman in the User Name text box and enter the password
specified during the installation in the Password text box. Click the Logon button to
proceed.
Figure 28
On the Oracle Enterprise Manager Cloud Control 12c License Agreement page click
the I Accept button to accept the License Agreement and access Cloud Control 12c.
Figure 29
Next, you are presented with the Select Enterprise Manager Home page. You can select
one of the home pages now or later as your Oracle Enterprise manager home page.
.bash_profile
Add the following Oracle Settings in the /home/oracle/.bash_profile file as a reference
point for your 12c environment.
Note: The following .bash_profile file can be used “as is” with an all-in-one Oracle
Enterprise Manager 12c Installation. For a fresh all-in-one Oracle Enterprise Manager
Cloud Control 12c installation, do “not” set the Oracle environment until “after” the
installation.
# Oracle Settings
TMP=/tmp; export TMP
TMPDIR=$TMP; export TMPDIR
ORACLE_BASE=/u01/app/oracle/product; export ORACLE_BASE
ORACLE_HOME=$ORACLE_BASE/11.2.0/dbhome_1; export ORACLE_HOME
EMDROOT=$ORACLE_BASE/11.2.0/dbhome_1; export EMDROOT
AGENT_HOME=$ORACLE_BASE/Middleware/agent/agent_inst; export
AGENT_HOME
OMS_HOME=$ORACLE_BASE/Middleware/oms; export OMS_HOME
ORACLE_INSTANCE=/u01/app/oracle/product/Middleware/gc_inst/WebTierIH1; export
ORACLE_INSTANCE
ORACLE_SID=orcl; export ORACLE_SID
ORACLE_UNQNAME=orcl; export ORACLE_UNQNAME
ORACLE_TERM=xterm; export ORACLE_TERM
PATH=/usr/sbin:$PATH; export PATH
PATH=$ORACLE_HOME/bin:$PATH; export PATH
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRARY_PATH
CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbm
s/jlib; export CLASSPATH
if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
fi
Appendix The following logs where printed to the console during the OME 12c installation:
Unzipping operation is succeed..
the location is :
/u01/app/oracle/product/Middleware/oms/install/tmp_installer/oracle.sysman.db/12.1.0.1.0
Unzipping operation is succeed..
the location is :
/u01/app/oracle/product/Middleware/oms/install/tmp_installer/oracle.sysman.xa/12.1.0.1.0
Unzipping operation is succeed..
the location is :
/u01/app/oracle/product/Middleware/oms/install/tmp_installer/oracle.sysman.emas/12.1.0.1
.0
Unzipping operation is succeed..
the location is :
/u01/app/oracle/product/Middleware/oms/install/tmp_installer/oracle.sysman.mos/12.1.0.1.
0
Unzipping operation is succeed..
the location is :
/u01/app/oracle/product/Middleware/oms/sysman/install/plugins/oracle.sysman.oh/12.1.0.1
.0
Unzipping operation is succeed..
the location is :
/u01/app/oracle/product/Middleware/oms/sysman/install/plugins/oracle.sysman.emrep/12.1
.0.1.0
Unzipping operation is succeed..
the location is :
/u01/app/oracle/product/Middleware/oms/sysman/install/plugins/oracle.sysman.csa/12.1.0.
1.0
Unzipping operation is succeed..
the location is :
/u01/app/oracle/product/Middleware/oms/sysman/install/plugins/oracle.sysman.beacon/12.
1.0.1.0
Running command : /u01/app/oracle/product/Middleware/oms/perl/bin/perl
/u01/app/oracle/product/Middleware/oms/install/oneoffs/apply_NewOneoffs.pl
/u01/app/oracle/product/Middleware/oms true
creating logger..
Connection exception in action logger path calculated:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/
action logger path calculated:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/
action logger path calculated finally:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/
no action logger file name from previous session
action logger filename after search: emschema.log
action logger filename finally: emschema.log
filename:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/emschema.log
already exists:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/emschema.log
Driver: oracle.jdbc.driver.OracleDriver
jdbcUrl =
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
action is non-transx - RCU based action
logger null: check if repos user exists
logger null: check if repos user exists..
logger null: found connection for DB user
logger null: query DB for repos user existence check
action logger path calculated finally:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/
action logger path calculated finally:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/
action logger filename finally: emschema.log.CREATE
filename:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/emschema.log.CREATE
already exists:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/emschema.log.CREATE
action logger path calculated finally:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/
jdbcUrl =
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
jdbcUrl =
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
jdbcUrl =
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
jdbcUrl =
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
jdbcUrl =
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
jdbcUrl =
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
jdbcUrl =
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
jdbcUrl =
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
jdbcUrl =
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
jdbcUrl =
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
jdbcUrl =
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
jdbcUrl =
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
PLUGIN_DEP_LIST={}
PLUGIN_PURGE_LIST={}
jdbcUrl =
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
jdbcUrl =
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
jdbcUrl =
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
jdbcUrl =
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
Processing command line ....
Repository Creation Utility - Checking Prerequisites
Checking Global Prerequisites
Repository Creation Utility - Checking Prerequisites
Checking Component Prerequisites
Repository Creation Utility - Creating Tablespaces
Validating and Creating Tablespaces
Repository Creation Utility - Create
Repository Create in progress.
Percent Complete: 5
Percent Complete: 10
Percent Complete: 15
Percent Complete: 20
Percent Complete: 25
Percent Complete: 37
Percent Complete: 42
Percent Complete: 47
Percent Complete: 52
Percent Complete: 57
Percent Complete: 62
Percent Complete: 67
Percent Complete: 72
Percent Complete: 77
Percent Complete: 82
Percent Complete: 87
Percent Complete: 92
Percent Complete: 97
Percent Complete: 100
action logger filename after search: emschema.log
action logger filename finally: emschema.log
filename:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/emschema.log
already exists:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/emschema.log
no action logger file name from previous session
action logger filename after search: emschema.log
action logger filename finally: emschema.log
filename:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/emschema.log
newly created:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/emschema.log
no action logger file name from previous session
action logger filename after search: emschema.log
action logger filename finally: emschema.log
filename:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/emschema.log
newly created:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/emschema.log
no action logger file name from previous session
action logger filename after search: emschema.log
action logger filename finally: emschema.log
filename:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/emschema.log
newly created:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/emschema.log
no action logger file name from previous session
action logger filename after search: emschema.log
action logger filename finally: emschema.log
filename:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/emschema.log
newly created:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/emschema.log
Driver: oracle.jdbc.driver.OracleDriver
jdbcUrl =
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
HTTP Test Inserted Successfully
Successfully Added HTTP Query Descriptors
DHTML Test Inserted Successfully
Successfully Added DHTML Query Descriptors
HTTPPING Test Inserted Successfully
Ping Test Inserted Successfully
Successfully Added PING Query Descriptors
DNS Test Inserted Successfully
Successfully Added DNS Query Descriptors
FTP Test Inserted Successfully
Successfully Added FTP Query Descriptors
Port Test Inserted Successfully
Successfully Added Port Query Descriptors
TNS Test Inserted Successfully
Successfully Added TNS Query Descriptors
SQLT Test Inserted Successfully
Successfully Added SQLT Query Descriptors
JDBC Test Inserted Successfully
Successfully Added JDBC Query Descriptors
Forms Test Inserted Successfully
Successfully Added Forms Query Descriptors
OS Test Inserted Successfully
Successfully Added OS Query Descriptors
Oats Test Inserted Successfully
Successfully Added OPENSCRIPT Query Descriptors
******** ORACLE_HOME is /u01/app/oracle/product/Middleware/oms
test properties path:
/u01/app/oracle/product/Middleware/oms/sysman/admin/emdrep/prop/imap.properties
CreateTestType:createCompleteTest: BEGIN
CreateTestType:createTestMetadataObject: BEGIN
CreateTestType:createTestMetadataObject: END
CreateTestType:createPropertyGroups: BEGIN
CreateTestType:createPropertyGroups: END
CreateTestType:createStrayProperties: BEGIN
CreateTestType:createStrayProperties: END
CreateTestType:createDefaultPromotions: BEGIN
CreateTestType:createDefaultPromotions: END
CreateTestType:createDefaultThresholds: BEGIN
CreateTestType:createDefaultThresholds: END
CreateTestType:createMetrics4TestType: BEGIN
CreateTestType:createMetrics4TestType: END
PropertyName :imap_host
PropertyName :imap_port
PropertyName :imap_user_name
PropertyName :imap_password
PropertyName :numretries
PropertyName :retryinterval
CreateTestType:createQueryDescriptor: BEGIN
CreateTestType:createQueryDescriptor: END
Enabled test for: IMAP , generic_service , 1.0
CreateTestType:createCompleteTest: END
******** ORACLE_HOME is /u01/app/oracle/product/Middleware/oms
test properties path:
/u01/app/oracle/product/Middleware/oms/sysman/admin/emdrep/prop/imap.properties.v2
CreateTestType:createCompleteTest: BEGIN
CreateTestType:createTestMetadataObject: BEGIN
CreateTestType:createTestMetadataObject: END
CreateTestType:createPropertyGroups: BEGIN
CreateTestType:createPropertyGroups: END
CreateTestType:createStrayProperties: BEGIN
CreateTestType:createStrayProperties: END
CreateTestType:createDefaultPromotions: BEGIN
CreateTestType:createDefaultPromotions: END
CreateTestType:createDefaultThresholds: BEGIN
CreateTestType:createDefaultThresholds: END
CreateTestType:createMetrics4TestType: BEGIN
CreateTestType:createMetrics4TestType: END
PropertyName :imap_host
PropertyName :imap_port
PropertyName :imap_user_name
PropertyName :imap_password
PropertyName :imap_header_count
PropertyName :connection
PropertyName :secure_auth
PropertyName :timeout
PropertyName :numretries
PropertyName :retryinterval
CreateTestType:createQueryDescriptor: BEGIN
CreateTestType:createQueryDescriptor: END
Enabled test for: IMAP , generic_service , 1.0
CreateTestType:createCompleteTest: END
******** ORACLE_HOME is /u01/app/oracle/product/Middleware/oms
test properties path:
/u01/app/oracle/product/Middleware/oms/sysman/admin/emdrep/prop/smtp.properties
CreateTestType:createCompleteTest: BEGIN
CreateTestType:createTestMetadataObject: BEGIN
CreateTestType:createTestMetadataObject: END
CreateTestType:createPropertyGroups: BEGIN
CreateTestType:createPropertyGroups: END
CreateTestType:createStrayProperties: BEGIN
CreateTestType:createStrayProperties: END
CreateTestType:createDefaultPromotions: BEGIN
CreateTestType:createDefaultPromotions: END
CreateTestType:createDefaultThresholds: BEGIN
CreateTestType:createDefaultThresholds: END
CreateTestType:createMetrics4TestType: BEGIN
CreateTestType:createMetrics4TestType: END
PropertyName :smtp_address
PropertyName :smtp_sender_id
PropertyName :smtp_recipient_id
PropertyName :numretries
PropertyName :retryinterval
CreateTestType:createQueryDescriptor: BEGIN
CreateTestType:createQueryDescriptor: END
Enabled test for: SMTP , generic_service , 1.0
CreateTestType:createCompleteTest: END
******** ORACLE_HOME is /u01/app/oracle/product/Middleware/oms
test properties path:
/u01/app/oracle/product/Middleware/oms/sysman/admin/emdrep/prop/smtp.properties.v2
CreateTestType:createCompleteTest: BEGIN
CreateTestType:createTestMetadataObject: BEGIN
CreateTestType:createTestMetadataObject: END
CreateTestType:createPropertyGroups: BEGIN
CreateTestType:createPropertyGroups: END
CreateTestType:createStrayProperties: BEGIN
CreateTestType:createStrayProperties: END
CreateTestType:createDefaultPromotions: BEGIN
CreateTestType:createDefaultPromotions: END
CreateTestType:createDefaultThresholds: BEGIN
CreateTestType:createDefaultThresholds: END
CreateTestType:createMetrics4TestType: BEGIN
CreateTestType:createMetrics4TestType: END
PropertyName :smtp_address
PropertyName :smtp_port
PropertyName :smtp_sender_id
PropertyName :smtp_recipient_id
PropertyName :connection
PropertyName :secure_auth
PropertyName :timeout
PropertyName :numretries
PropertyName :retryinterval
CreateTestType:createQueryDescriptor: BEGIN
CreateTestType:createQueryDescriptor: END
Enabled test for: SMTP , generic_service , 1.0
CreateTestType:createCompleteTest: END
******** ORACLE_HOME is /u01/app/oracle/product/Middleware/oms
test properties path:
/u01/app/oracle/product/Middleware/oms/sysman/admin/emdrep/prop/smtp.properties.v3
CreateTestType:createCompleteTest: BEGIN
CreateTestType:createTestMetadataObject: BEGIN
CreateTestType:createTestMetadataObject: END
CreateTestType:createPropertyGroups: BEGIN
CreateTestType:createPropertyGroups: END
CreateTestType:createStrayProperties: BEGIN
CreateTestType:createStrayProperties: END
CreateTestType:createDefaultPromotions: BEGIN
CreateTestType:createDefaultPromotions: END
CreateTestType:createDefaultThresholds: BEGIN
CreateTestType:createDefaultThresholds: END
CreateTestType:createMetrics4TestType: BEGIN
CreateTestType:createMetrics4TestType: END
CreateTestType:createQueryDescriptor: BEGIN
CreateTestType:createQueryDescriptor: END
Enabled test for: SMTP , generic_service , 1.0
CreateTestType:createCompleteTest: END
******** ORACLE_HOME is /u01/app/oracle/product/Middleware/oms
test properties path:
/u01/app/oracle/product/Middleware/oms/sysman/admin/emdrep/prop/ldap.properties
CreateTestType:createCompleteTest: BEGIN
CreateTestType:createTestMetadataObject: BEGIN
CreateTestType:createTestMetadataObject: END
CreateTestType:createPropertyGroups: BEGIN
CreateTestType:createPropertyGroups: END
CreateTestType:createStrayProperties: BEGIN
CreateTestType:createStrayProperties: END
CreateTestType:createDefaultPromotions: BEGIN
CreateTestType:createDefaultPromotions: END
CreateTestType:createDefaultThresholds: BEGIN
CreateTestType:createDefaultThresholds: END
CreateTestType:createMetrics4TestType: BEGIN
CreateTestType:createMetrics4TestType: END
PropertyName :ldap_address
PropertyName :ldap_port
PropertyName :ldap_user_name
PropertyName :ldap_password
PropertyName :numretries
PropertyName :retryinterval
PropertyName :ldap_filter
PropertyName :ldap_base
PropertyName :ldap_attrname
PropertyName :ldap_attrvalue
PropertyName :ldap_timeout
CreateTestType:createQueryDescriptor: BEGIN
CreateTestType:createQueryDescriptor: END
Enabled test for: LDAP , generic_service , 1.0
CreateTestType:createCompleteTest: END
******** ORACLE_HOME is /u01/app/oracle/product/Middleware/oms
test properties path:
/u01/app/oracle/product/Middleware/oms/sysman/admin/emdrep/prop/ldap.properties.v2
CreateTestType:createCompleteTest: BEGIN
CreateTestType:createTestMetadataObject: BEGIN
CreateTestType:createTestMetadataObject: END
CreateTestType:createPropertyGroups: BEGIN
CreateTestType:createPropertyGroups: END
CreateTestType:createStrayProperties: BEGIN
CreateTestType:createStrayProperties: END
CreateTestType:createDefaultPromotions: BEGIN
CreateTestType:createDefaultPromotions: END
CreateTestType:createDefaultThresholds: BEGIN
CreateTestType:createDefaultThresholds: END
CreateTestType:createMetrics4TestType: BEGIN
CreateTestType:createMetrics4TestType: END
PropertyName :ldap_address
PropertyName :ldap_port
PropertyName :ldap_user_name
PropertyName :ldap_password
PropertyName :numretries
PropertyName :retryinterval
PropertyName :ldap_filter
PropertyName :ldap_base
PropertyName :ldap_attrname
PropertyName :ldap_attrvalue
PropertyName :ldap_timeout
PropertyName :connection
PropertyName :secure_auth
CreateTestType:createQueryDescriptor: BEGIN
CreateTestType:createQueryDescriptor: END
Enabled test for: LDAP , generic_service , 1.0
CreateTestType:createCompleteTest: END
******** ORACLE_HOME is /u01/app/oracle/product/Middleware/oms
test properties path:
/u01/app/oracle/product/Middleware/oms/sysman/admin/emdrep/prop/pop.properties
CreateTestType:createCompleteTest: BEGIN
CreateTestType:createTestMetadataObject: BEGIN
CreateTestType:createTestMetadataObject: END
CreateTestType:createPropertyGroups: BEGIN
CreateTestType:createPropertyGroups: END
CreateTestType:createStrayProperties: BEGIN
CreateTestType:createStrayProperties: END
CreateTestType:createDefaultPromotions: BEGIN
CreateTestType:createDefaultPromotions: END
CreateTestType:createDefaultThresholds: BEGIN
CreateTestType:createDefaultThresholds: END
CreateTestType:createMetrics4TestType: BEGIN
CreateTestType:createMetrics4TestType: END
PropertyName :pop_host
PropertyName :pop_user_name
PropertyName :pop_password
PropertyName :numretries
PropertyName :retryinterval
CreateTestType:createQueryDescriptor: BEGIN
CreateTestType:createQueryDescriptor: END
Enabled test for: POP , generic_service , 1.0
CreateTestType:createCompleteTest: END
******** ORACLE_HOME is /u01/app/oracle/product/Middleware/oms
test properties path:
/u01/app/oracle/product/Middleware/oms/sysman/admin/emdrep/prop/nntp.properties
CreateTestType:createCompleteTest: BEGIN
CreateTestType:createTestMetadataObject: BEGIN
CreateTestType:createTestMetadataObject: END
CreateTestType:createPropertyGroups: BEGIN
CreateTestType:createPropertyGroups: END
CreateTestType:createStrayProperties: BEGIN
CreateTestType:createStrayProperties: END
CreateTestType:createDefaultPromotions: BEGIN
CreateTestType:createDefaultPromotions: END
CreateTestType:createDefaultThresholds: BEGIN
CreateTestType:createDefaultThresholds: END
CreateTestType:createMetrics4TestType: BEGIN
CreateTestType:createMetrics4TestType: END
PropertyName :nntp_address
PropertyName :nntp_newsgroup
PropertyName :numretries
PropertyName :retryinterval
CreateTestType:createQueryDescriptor: BEGIN
CreateTestType:createQueryDescriptor: END
Enabled test for: NNTP , generic_service , 1.0
CreateTestType:createCompleteTest: END
******** ORACLE_HOME is /u01/app/oracle/product/Middleware/oms
test properties path:
/u01/app/oracle/product/Middleware/oms/sysman/admin/emdrep/prop/soap.properties
CreateTestType:createCompleteTest: BEGIN
CreateTestType:createTestMetadataObject: BEGIN
CreateTestType:createTestMetadataObject: END
CreateTestType:createPropertyGroups: BEGIN
CreateTestType:createPropertyGroups: END
CreateTestType:createStrayProperties: BEGIN
CreateTestType:createStrayProperties: END
CreateTestType:createDefaultPromotions: BEGIN
CreateTestType:createDefaultPromotions: END
CreateTestType:createDefaultThresholds: BEGIN
CreateTestType:createDefaultThresholds: END
CreateTestType:createMetrics4TestType: BEGIN
CreateTestType:createMetrics4TestType: END
PropertyName :soap_endpoint
PropertyName :soap_payload
PropertyName :soap_action_uri
PropertyName :soap_auth_realm
PropertyName :soap_auth_username
PropertyName :soap_auth_password
PropertyName :numretries
PropertyName :retryinterval
PropertyName :soap_wsdl_url
PropertyName :soap_operation
PropertyName :soap_parameters
CreateTestType:createQueryDescriptor: BEGIN
CreateTestType:createQueryDescriptor: END
Enabled test for: SOAP , generic_service , 1.0
CreateTestType:createCompleteTest: END
******** ORACLE_HOME is /u01/app/oracle/product/Middleware/oms
test properties path:
/u01/app/oracle/product/Middleware/oms/sysman/admin/emdrep/prop/siebel.properties
CreateTestType:createCompleteTest: BEGIN
CreateTestType:createTestMetadataObject: BEGIN
CreateTestType:createTestMetadataObject: END
CreateTestType:createPropertyGroups: BEGIN
CreateTestType:createPropertyGroups: END
CreateTestType:createStrayProperties: BEGIN
CreateTestType:createStrayProperties: END
CreateTestType:createDefaultPromotions: BEGIN
CreateTestType:createDefaultPromotions: END
CreateTestType:createDefaultThresholds: BEGIN
CreateTestType:createDefaultThresholds: END
CreateTestType:createMetrics4TestType: BEGIN
CreateTestType:createMetrics4TestType: END
PropertyName :retryinterval
PropertyName :txnDetails
PropertyName :timeoutduration
PropertyName :granularity
PropertyName :username
PropertyName :password
PropertyName :isSecureCommand
CreateTestType:createQueryDescriptor: BEGIN
CreateTestType:createQueryDescriptor: END
CreateTestType:createCompleteTest: END
******** ORACLE_HOME is /u01/app/oracle/product/Middleware/oms
test properties path:
/u01/app/oracle/product/Middleware/oms/sysman/admin/emdrep/prop/xmpp.properties
CreateTestType:createCompleteTest: BEGIN
CreateTestType:createTestMetadataObject: BEGIN
CreateTestType:createTestMetadataObject: END
CreateTestType:createPropertyGroups: BEGIN
CreateTestType:createPropertyGroups: END
CreateTestType:createStrayProperties: BEGIN
CreateTestType:createStrayProperties: END
CreateTestType:createDefaultPromotions: BEGIN
CreateTestType:createDefaultPromotions: END
CreateTestType:createDefaultThresholds: BEGIN
CreateTestType:createDefaultThresholds: END
CreateTestType:createMetrics4TestType: BEGIN
CreateTestType:createMetrics4TestType: END
PropertyName :host
PropertyName :port
PropertyName :user_name
PropertyName :password
PropertyName :contact_name
PropertyName :connection
PropertyName :secure_auth
PropertyName :timeout
PropertyName :numretries
PropertyName :retryinterval
CreateTestType:createQueryDescriptor: BEGIN
CreateTestType:createQueryDescriptor: END
Enabled test for: XMPP , generic_service , 1.0
CreateTestType:createCompleteTest: END
******** ORACLE_HOME is /u01/app/oracle/product/Middleware/oms
test properties path:
/u01/app/oracle/product/Middleware/oms/sysman/admin/emdrep/prop/webdav.properties
CreateTestType:createCompleteTest: BEGIN
CreateTestType:createTestMetadataObject: BEGIN
CreateTestType:createTestMetadataObject: END
CreateTestType:createPropertyGroups: BEGIN
CreateTestType:createPropertyGroups: END
CreateTestType:createStrayProperties: BEGIN
CreateTestType:createStrayProperties: END
CreateTestType:createDefaultPromotions: BEGIN
CreateTestType:createDefaultPromotions: END
CreateTestType:createDefaultThresholds: BEGIN
CreateTestType:createDefaultThresholds: END
CreateTestType:createMetrics4TestType: BEGIN
CreateTestType:createMetrics4TestType: END
PropertyName :url
PropertyName :user_name
PropertyName :password
PropertyName :trash_url
PropertyName :secure_auth
PropertyName :timeout
PropertyName :numretries
PropertyName :retryinterval
CreateTestType:createQueryDescriptor: BEGIN
CreateTestType:createQueryDescriptor: END
Enabled test for: WebDAV , generic_service , 1.0
CreateTestType:createCompleteTest: END
******** ORACLE_HOME is /u01/app/oracle/product/Middleware/oms
test properties path:
/u01/app/oracle/product/Middleware/oms/sysman/admin/emdrep/prop/caldav.properties
CreateTestType:createCompleteTest: BEGIN
CreateTestType:createTestMetadataObject: BEGIN
CreateTestType:createTestMetadataObject: END
CreateTestType:createPropertyGroups: BEGIN
CreateTestType:createPropertyGroups: END
CreateTestType:createStrayProperties: BEGIN
CreateTestType:createStrayProperties: END
CreateTestType:createDefaultPromotions: BEGIN
CreateTestType:createDefaultPromotions: END
CreateTestType:createDefaultThresholds: BEGIN
CreateTestType:createDefaultThresholds: END
CreateTestType:createMetrics4TestType: BEGIN
CreateTestType:createMetrics4TestType: END
PropertyName :url
PropertyName :user_name
PropertyName :password
PropertyName :view_date
PropertyName :secure_auth
PropertyName :timeout
PropertyName :numretries
PropertyName :retryinterval
CreateTestType:createQueryDescriptor: BEGIN
CreateTestType:createQueryDescriptor: END
Enabled test for: CalDAV , generic_service , 1.0
CreateTestType:createCompleteTest: END
no action logger file name from previous session
action logger filename after search: emschema.log
action logger filename finally: emschema.log
filename:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/emschema.log
newly created:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/emschema.log
Repository Creation Utility: Create - Completion Summary
Database details:
Connect Descriptor :
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)
(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
Connected As : SYS
RCU Logfile :
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/rcu.log
Component schemas created:
Component Status Logfile
EM Repository Creation Configuration Success
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/em_repos_config.log
EM Repository Init Configuration Success
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/em_repos_init.log
EM Repository Common Success
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/em_repos_common.log
Repository Creation Utility - Create : Operation Completed
action is non-transx - RCU based action
logger null: check if repos user exists
logger null: check if repos user exists..
logger null: found connection for DB user
logger null: query DB for repos user existence check
action logger path calculated finally:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1235_PM.MY_ORACLE_SUPPORT/
action logger filename finally: emschema.log.MY_ORACLE_SUPPORT
filename:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/emschema.log.MY_ORACLE_SUPPORT
already exists:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/emschema.log.MY_ORACLE_SUPPORT
action logger path calculated finally:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1235_PM.MY_ORACLE_SUPPORT/
2011-12-01 12:35:32.812 rcu:Extracting Statement from File Name:
'/u01/app/oracle/product/Middleware/oms/sysman/admin/emdrep/sql//core/latest/mos/mos_
add_creds_after_install.sql'Line Number: 27
2011-12-01 12:35:32.812 rcu:Extracted SQL Statement: [DECLARE
mos_username MGMT_MOS_USER_CREDENTIALS.MOS_USERNAME%TYPE;
mos_password MGMT_MOS_USER_CREDENTIALS.MOS_PASSWORD%TYPE;
BEGIN
-- get the My Oracle Support credentials (if available)
mos_username := '&1';
dbms_output.put_line('My Oracle Support user name as obtained from setup: ' ||
mos_username);
mos_password := '&2';
dbms_output.put_line('My Oracle Support user password as obtained from setup: ' ||
'**********');
IF (mos_username IS NULL OR
length(trim(mos_username)) = 0 OR
UPPER(mos_username) = '_NOT_AVAILABLE_')
THEN
dbms_output.put_line('My Oracle Support user name is not specified');
ELSE IF (mos_password IS NULL OR
length(trim(mos_password)) = 0 OR
UPPER(mos_password) = '_NOT_AVAILABLE_')
THEN
dbms_output.put_line('My Oracle Support user password is not specified');
ELSE
BEGIN
-- set the My Oracle Support credentials for SYSMAN.
MGMT_MOS_CORE.set_mos_credentials(mos_username, mos_password);
COMMIT;
dbms_output.put_line('My Oracle Support user name is specified as: ' || mos_username);
dbms_output.put_line('My Oracle Support user password is specified as: ' || '**********');
EXCEPTION
WHEN others THEN
dbms_output.put_line('UNHANDLED EXCEPTION while setting My Oracle Support
credentials' || ', SQLCODE: ' || SQLCODE || ', SQLERRM: ' || SQLERRM);
END;
END IF;
END IF;
END;
]
2011-12-01 12:35:32.812 rcu:Statement Type: 'BEGIN/END Anonymous Block'
Processing command line ....
Repository Creation Utility - Checking Prerequisites
Checking Global Prerequisites
Repository Creation Utility - Checking Prerequisites
Checking Component Prerequisites
Repository Creation Utility - Creating Tablespaces
Validating and Creating Tablespaces
RCU-6108:DB TablespaceFreeMB Prerequisite failure for: MGMT_TABLESPACE
Current space is 41MB. It should be be greater than 50MB.
Repository Creation Utility - Create
Repository Create in progress.
Percent Complete: 0
Percent Complete: 10
Percent Complete: 20
Percent Complete: 20
Percent Complete: 50
Percent Complete: 100
Repository Creation Utility: Create - Completion Summary
Database details:
Connect Descriptor :
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)
(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
Connected As : SYS
Prefix for (prefixable) Schema Owners : SYSMAN
RCU Logfile :
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/rcu.log
Component schemas created:
Component Status Logfile
Metadata Services Success
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/mds.log
Repository Creation Utility - Create : Operation Completed
Driver: oracle.jdbc.driver.OracleDriver
creating logger..
no action logger file name from previous session
action logger filename after search: emschema.log
action logger filename finally: emschema.log
filename:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1235_PM.MY_ORACLE_SUPPORT/emschema.log
already exists:
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1235_PM.MY_ORACLE_SUPPORT/emschema.log
jdbcUrl =
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
Processing command line ....
Repository Creation Utility - Checking Prerequisites
Checking Global Prerequisites
Repository Creation Utility - Checking Prerequisites
Checking Component Prerequisites
Repository Creation Utility - Creating Tablespaces
Validating and Creating Tablespaces
RCU-6108:DB TablespaceFreeMB Prerequisite failure for: MGMT_TABLESPACE
Current space is 41MB. It should be be greater than 50MB.
RCU-6108:DB TablespaceFreeMB Prerequisite failure for: TEMP
Current space is 29MB. It should be be greater than 50MB.
Repository Creation Utility - Create
Repository Create in progress.
Percent Complete: 10
2011-12-01 12:35:39,096 [Thread-405] WARN - Ignorable error when running rcu
Percent Complete: 30
2011-12-01 12:35:39,296 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,326 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,365 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,387 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,403 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,420 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,437 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,453 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,470 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,487 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,504 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,545 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,572 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,604 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,620 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,637 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,654 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,670 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,687 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,704 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,720 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,737 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,754 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,770 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,787 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,912 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,929 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,945 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,962 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,979 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:39,995 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:40,012 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:40,029 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:40,046 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:40,062 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:40,079 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:40,096 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:40,112 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:40,129 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:40,146 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:40,162 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:40,179 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:40,196 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:40,212 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:40,229 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:40,246 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:40,382 [Thread-405] WARN - Ignorable error when running rcu
2011-12-01 12:35:40,432 [Thread-405] WARN - Ignorable error when running rcu
Percent Complete: 50
2011-12-01 12:35:44,987 [Thread-405] WARN - Ignorable error when running rcu
Percent Complete: 50
Percent Complete: 100
Repository Creation Utility: Create - Completion Summary
Database details:
Connect Descriptor :
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)
(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
Connected As : SYS
Prefix for (prefixable) Schema Owners : SYSMAN
RCU Logfile :
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/rcu.log
Component schemas created:
Component Status Logfile
Oracle Platform Security Services Success
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/opss.log
Repository Creation Utility - Create : Operation Completed
Processing command line ....
Repository Creation Utility - Checking Prerequisites
Checking Global Prerequisites
Repository Creation Utility - Checking Prerequisites
Checking Component Prerequisites
Repository Creation Utility - Creating Tablespaces
Validating and Creating Tablespaces
Repository Creation Utility - Create
Repository Create in progress.
Percent Complete: 0
Percent Complete: 10
Percent Complete: 30
2011-12-01 12:35:47,148 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,164 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,181 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,198 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,217 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,231 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,248 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,265 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,281 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,298 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,315 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,331 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,348 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,365 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,381 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,398 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,415 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,431 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,448 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,465 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,481 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,498 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,515 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,557 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,598 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,615 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,632 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,648 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,665 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,682 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,698 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,715 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,732 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,748 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,765 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,782 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,798 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,815 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,832 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,848 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,865 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,882 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,898 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,915 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,932 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:47,949 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:48,085 [Thread-411] WARN - Ignorable error when running rcu
2011-12-01 12:35:48,136 [Thread-411] WARN - Ignorable error when running rcu
Percent Complete: 50
Percent Complete: 50
Percent Complete: 100
Repository Creation Utility: Create - Completion Summary
Database details:
Connect Descriptor :
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)
(PORT=1521)))(CONNECT_DATA=(SID=orcl)))
Connected As : SYS
Prefix for (prefixable) Schema Owners : SYSMAN
RCU Logfile :
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/rcu.log
Component schemas created:
Component Status Logfile
Authorization Policy Manager Success
/u01/app/oracle/product/Middleware/oms/sysman/log/schemamanager/m_120111_1154_A
M/m_120111_1154_AM.CREATE/apm.log
Repository Creation Utility - Create : Operation Completed
Next Ops Center Experts Webcast: Cloud Management
Cloud Control 12c released for Windows 64-bit
Testing in May: Keep the bugs away
Install Oracle VM Server 3
DB Startup Fails on WORKAREA_SIZE_POLICY
Integrate EM OPS Center 12c in EM Cloud Control 12c
Integrate EM OPS Center 12c, EM Cloud Control 12c and Oracle VM Manager
ON-DEMAND WEBCAST: Oracle Database Lifecycle Management with Oracle
Enterprise Manager 12c, Now Available
Using Metric Extensions in EM12c
Security On Top Of Security
Oracle Enterprise Manager 12c Upgrade
Show a printer friendly, save as PDF version of the Oracle Cloud Cookbook
Distribution of the Oracle Cloud Cookbook or derivative of the work in any form for
commercial purposes is prohibited unless prior permission is obtained from the copyright
holder.
Change Log
Revision Change Description Updated By Date
1.0 Oracle Enterprise Manager 12c Upgrade Roddy Rodstein 10/29/11
1.1 12c .bash_profile Roddy Rodstein 11/11/11
Table of Contents
Change Log
Oracle Enterprise Manager 12c Upgrade Intro and Overview
Oracle Enterprise Manager 12c Upgrade Console Installation
Oracle Enterprise Manager 12c 1-System Upgrade
Oracle Enterprise Manager 12c Upgrade Intro and
Overview
There are a number of factors to consider if your organization wants to upgrade to the latest
version of Oracle Enterprise Manager, now re-branded, in full, as Oracle Enterprise
Manager Cloud Control 12c. In general, you have three upgrade paths to choose from: 1-
System, 2-System and 1-System on a different host. As the name implies, 1-System will
upgrade Grid Control to Cloud Control on the same host. While Oracle's documentation
does make mention of the baggage and overhead associated with upgrading Grid control to
Cloud control, it is somewhat buried in the voluminous documentation.
Firstly, your storage requirements will be increased because the 12c Agents are not really
upgraded so much as installed fresh into a new 12c Agent home directory, effectively
doubling your agent space. The same is also true for Oracle Management Service (OMS) as
it is also installed into a fresh 12c OMS home directory. Also consider that you will also
carry forward all the code baggage from the earlier version of Grid Control, whether its 10g
or 11g. For these and other preupgrade details please refer to the Oracle Documentation.
The 2-System upgrade path is probably the most versatile upgrade solution and offers
almost zero downtime for Oracle Enterprise Manager from start to finish. It is also the most
complicated upgrade path with a number of manual steps in between. On the other hand, if
you want to upgrade hardware from old x86 to modern x64 architecture then the 2-System
upgrade path offers you that opportunity. Somewhere in the middle between the 1-System
and 2-System upgrade is the 1-System on a different host.
This is probably the cleanest upgrade path in that, because you will upgrade to a new host,
the code baggage from the previous EM installation is eliminated. While this option does
require additional hardware, you take the opportunity to make the switch from an x86 to
x64 architecture, or vice-versa, as the case may be. But there is downtime associated with
this upgrade path while the database and repository are copied to the new host, as well as
the actual upgrade itself.
Now that you know some of the conditions and hurdles surrounding the Oracle Enterprise
Manager Cloud Control 12c upgrade, you make be asking whether or not its all worth it.
Some schools of thought say that its better to discard all the baggage from the older release
and start fresh – new hardware (virtual or physical) , new database, new Oracle software.
Others may not be able to live without the years of collected target's data. Ultimately this is
the decision you will have to make.
Before taking the plunge, it is advised to setup a test environment and play around with the
various options to gauge the difficulty of each upgrade path and see what's right for your
organization. You could also take a look at Oracle's all-in-one Oracle Enterprise Manager
Grid Control 11g Oracle VM template and give that a spin to explore the “1-System”
upgrade approach and to quickly see Oracle Enterprise Manager Cloud Control 12c in
action. But if you do want to try an upgrade, the first step is to install the Preupgrade
console.
Oracle Enterprise Manager 12c Upgrade Console
Installation
Throughout this section it would be helpful to have our environment setup properly. Use
the following two /home/oracle/.bash_profile examples as a reference point for your 11g
and 12c environment.
Note: The following .bash_profile file can be used “as is” with Oracle's all-in-one Oracle
Enterprise Manager Grid Control 11g Oracle VM template. For a fresh all-in-one Oracle
Enterprise Manager Cloud Control 12c installation, do “not” set the Oracle environment
until “after” the installation.
# 11g User specific environment and startup programs
# Oracle Settings
TMP=/tmp; export TMP
TMPDIR=$TMP; export TMPDIR
ORACLE_BASE=/u01/OracleHomes; export ORACLE_BASE
#ORACLE_HOME=$ORACLE_BASE/db11g; export ORACLE_HOME
ORACLE_HOME=$ORACLE_BASE/Middleware/oms11g; export ORACLE_HOME
AGENT_HOME=$ORACLE_BASE/Middleware/agent11g; export AGENT_HOME
OMS_HOME=$ORACLE_BASE/Middleware/oms11g; export OMS_HOME
ORACLE_INSTANCE=/u01/OracleHomes/gc_inst/WebTierIH1; export
ORACLE_INSTANCE
ORACLE_SID=emrep; export ORACLE_SID
ORACLE_TERM=xterm; export ORACLE_TERM
PATH=/usr/sbin:$PATH:$HOME/bin:/u01/OracleHomes/Middleware/oms11g/OPatch:$O
RACLE_HOME/bin; export PATH
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRARY_PATH
CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbm
s/jlib; export CLASSPATH
if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
fi
# Post upgrade 12c User specific environment and startup programs
# Oracle Settings
TMP=/tmp; export TMP
TMPDIR=$TMP; export TMPDIR
ORACLE_BASE=/u01/OracleHomes; export ORACLE_BASE
ORACLE_HOME=$ORACLE_BASE/db11g; export ORACLE_HOME
AGENT_HOME=$ORACLE_BASE/Middleware/agent12g/core/12.1.0.1.0/; export
AGENT_HOME
OMS_HOME=$ORACLE_BASE/Middleware12c/oms; export OMS_HOME
ORACLE_INSTANCE
ORACLE_INSTANCE=/u01/OracleHomes/Middleware12c/gc_inst/WebTierIH1; export
ORACLE_INSTANCE
ORACLE_SID=emrep; export ORACLE_SID
ORACLE_TERM=xterm; export ORACLE_TERM
PATH=/usr/sbin:$PATH; export PATH
PATH=$ORACLE_HOME/bin:$PATH; export PATH
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRARY_PATH
CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbm
s/jlib; export CLASSPATH
if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
fi
The first thing to do is to gather all the resources we will need to perform the upgrade. This
includes the Agent Core files and Oracle Enterprise Manager 12c installer, both x86 and
x64 versions as needed, and the prerequisite patches. For the sake of this walkthrough, we
assume that you are upgrading Oracle Enterprise Manager Grid Control 11g and that your
staging directory is writable by user oracle.
The Agent Core and Enterprise Manager 12c files can be downloaded from
http://www.oracle.com/technetwork/oem/grid-control/downloads/index.html. The Agent
Core files can be downloaded by following the Oracle Enterprise Manager Agent
Downloads link and scrolling to the bottom of the page to the Oracle Enterprise Manager
Agent 12.1 files for Self Update Feature section. Here you will find both x86 and x64
versions of the Agent upgrade.
First, download these files and then unzip them to your staging directory. It is
recommended to find the AgentCore zips and put them together in the same directory.
Later, when you have successfully installed the preupgrade console and want to
manage/validate your software, the console will be looking for two files:
12.1.0.1.0_AgentCore_226.zip for the x64 agent upgrade or 12.1.0.1.0_AgentCore_46.zip
for the x86 upgrade agent.
At the top of the grid-control downloads site is a section entitled Oracle Enterprise Manager
Cloud Control 12c. Here you will find links to both the x86 and x64 versions of the Oracle
Enterprise Manager 12c Installer. The installer is divided into two disks. The first disk is
the Oracle Enterprise Manager Cloud Control 12c upgrader. The second disk contains the
plugins for the Agent upgrade, so in fact disk 2 goes hand in hand with the AgentCore zips.
Download disk 1 as appropriate for your environment.
For our example, Oracle Enterprise Manager Grid Control 11g is running on x86 in an all-
in-one configuration, so we need disks 1 and 2 from the Oracle Enterprise Manager 12c x86
upgrader. We have Agent running on a x64 target so we need to download only disk 2 of
the Oracle Enterprise Manager 12c x64 upgrader. Further more, we have combined disks 1
and 2 into one directory called em12_linux_x86. From disk 2 we grabbed only the files
located in the plugins directory and placed them in another directory called em12_linux64.
The next example shows the stage directory with the files from above.
$ cd /u01/stage
$ ls -lh
total 468M
drwxrwxr-x 4 oracle oinstall 4.0K Oct 14 09:11 10044087
drwxr-xr-x 5 oracle oinstall 4.0K Oct 13 15:55 10065631
-rw-r--r-- 1 oracle oinstall 221M Sep 23 02:53 12.1.0.1.0_AgentCore_226.zip
-rw-r--r-- 1 oracle oinstall 214M Oct 13 13:41 12.1.0.1.0_AgentCore_46.zip
drwxr-xr-x 3 oracle oinstall 4.0K Oct 14 15:22 em12_linux64
drwxr-xr-x 10 oracle oinstall 4.0K Oct 13 15:06 em12_linux_x86
-rw-r--r-- 1 oracle oinstall 3.6M Oct 13 14:49 p10044087_111010_Generic.zip
-rw-r--r-- 1 oracle oinstall 598K Oct 13 14:49 p10065631_111010_Generic.zip
-rw-r--r-- 1 oracle oinstall 29M Oct 13 14:51 p6880880_111000_LINUX.zip
$ ls -lh em12_linux_x86
total 1.6G
drwxr-xr-x 7 oracle oinstall 4.0K Oct 13 14:34 install
drwxr-xr-x 4 oracle oinstall 4.0K Oct 13 14:34 jdk
drwxr-xr-x 4 oracle oinstall 4.0K Oct 13 14:40 oms
drwxr-xr-x 3 oracle oinstall 4.0K Oct 14 09:36 plugins
drwxr-xr-x 2 oracle oinstall 4.0K Oct 13 14:40 Preupgrade_Console_Patch
-rw-r--r-- 1 oracle oinstall 99K Oct 10 17:50 Release_Notes.pdf
drwxr-xr-x 2 oracle oinstall 4.0K Oct 13 14:40 response
-rwxr-xr-x 1 oracle oinstall 5.9K Oct 10 17:50 runInstaller
drwxr-xr-x 9 oracle oinstall 4.0K Oct 13 14:41 stage
drwxr-xr-x 2 oracle oinstall 4.0K Oct 13 14:44 wls
-rw-r--r-- 1 oracle oinstall 1.6G Oct 10 18:01 WT.zip
$ ls -lh em12_linux64
total 1.2G
-rw-r--r-- 1 oracle oinstall 567K Sep 23 04:26 12.1.0.1.0_oracle.em.sidb_2000_0.opar
-rw-r--r-- 1 oracle oinstall 3.8M Sep 23 04:26 12.1.0.1.0_oracle.em.soee_2000_0.opar
-rw-r--r-- 1 oracle oinstall 594K Sep 23 04:26 12.1.0.1.0_oracle.em.ssad_2000_0.opar
-rw-r--r-- 1 oracle oinstall 102M Sep 23 04:25
12.1.0.1.0_oracle.sysman.beacon_2000_0.opar
-rw-r--r-- 1 oracle oinstall 489K Sep 23 04:25 12.1.0.1.0_oracle.sysman.csa_2000_0.opar
-rw-r--r-- 1 oracle oinstall 593M Sep 23 04:25 12.1.0.1.0_oracle.sysman.db_2000_0.opar
-rw-r--r-- 1 oracle oinstall 420M Sep 23 04:25 12.1.0.1.0_oracle.sysman.emas_2000_0.opar
-rw-r--r-- 1 oracle oinstall 2.7M Sep 23 04:26 12.1.0.1.0_oracle.sysman.emct_2000_0.opar
-rw-r--r-- 1 oracle oinstall 27M Sep 23 04:26 12.1.0.1.0_oracle.sysman.emfa_2000_0.opar
-rw-r--r-- 1 oracle oinstall 6.3M Sep 23 04:26 12.1.0.1.0_oracle.sysman.empa_2000_0.opar
-rw-r--r-- 1 oracle oinstall 291K Sep 23 04:25
12.1.0.1.0_oracle.sysman.emrep_2000_0.opar
-rw-r--r-- 1 oracle oinstall 8.6M Sep 23 04:26 12.1.0.1.0_oracle.sysman.mos_2000_0.opar
-rw-r--r-- 1 oracle oinstall 484K Sep 23 04:25 12.1.0.1.0_oracle.sysman.oh_2000_0.opar
-rw-r--r-- 1 oracle oinstall 2.2M Sep 23 04:26 12.1.0.1.0_oracle.sysman.ssa_2000_0.opar
-rw-r--r-- 1 oracle oinstall 8.4M Sep 23 04:26 12.1.0.1.0_oracle.sysman.vt_2000_0.opar
-rw-r--r-- 1 oracle oinstall 3.4M Sep 23 04:26 12.1.0.1.0_oracle.sysman.xa_2000_0.opar
Next, we need to take care of some prerequisites before we can continue on with the
installation of the Preupgrade Console. First take care that you are running the latest
version of opatch. Login to http://support.oracle.com/ and go to patches and downloads.
There search for 6880880. Download the patch associated with your level of Oracle
Enterprise Manager and unzip that patch to /u01/OracleHomes/Middleware/oms11g to
overwrite the older opatch.
Note: Ensure that you use the correct path to your opatch directory.
We will then download two patches. Search for and download 10044087 and 10065631.
Unzip these patches into our stage directory. Now we are ready to do the final steps for
installing the Preupgrade Console.
$ cd /u01/stage
$ opatch lsinventory
$ opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir ./10065631
$ emctl stop oms
$ cd 10065631/
$ opatch apply
$ cd ../10044087
$ opatch apply
After this we need to run rcuJDBCEngine which should be in your PATH. Make
substitutions for <PASSWORD> and <IP ADDRESS> as needed. In this example, sysman
is the OEM administrative user. <IP ADDRESS> will be OEM's IP address. 1521 is the
port on which the database listens and emrep is the SID.
rcuJDBCEngine sysman/<PASSWORD>@<IP ADDRESS>:1521:emrep JDBC_SCRIPT
$ORACLE_HOME/sysman/preupgc/puc_dblink_pkgdef.sql
rcuJDBCEngine sysman/<PASSWORD>@<IP ADDRESS>:1521:emrep JDBC_SCRIPT
$ORACLE_HOME/sysman/preupgc/puc_dblink_pkgbody.sql
rcuJDBCEngine sysman/<PASSWORD>@<IP ADDRESS>:1521:emrep JDBC_SCRIPT
$ORACLE_HOME/sysman/preupgc/pre_upg_console.sql
If you are able to run rcuJDBCEngine successfully all three times then you can now restart
OMS.
$ emctl start oms
You can now log into Oracle Enterprise Manager 11g, click on the Deployments tab and
look for Oracle Enterprise Manager 12c Upgrade Console under the Upgrade section.
Figure 1
Oracle Enterprise Manager 12c 1-System Upgrade
Looking at the Upgrade Console, you will see that it has been divided into sections starting
at the top with the Agent Upgrade Status and Other Links. As the name implies, this section
gives a high level view of where we are in the Agent upgrade process. The Preupgrade
console has been designed to allow the systems administrator to perform the upgrade in a
flow, starting at the top and working their way down, step by step, but if any problems crop
up you can always refer to this top section to track things down or just get a quick status
report of your progress.
Figure 2
Choose 1-System under the Select Upgrade Type as we will be performing a simple same
system upgrade of Grid Control, which Oracle now calls Cloud Control.
Figure 3
It is advised that you click on the Overview link in the Preupgrade Steps section to better
understand the general steps we will be following while doing this 1-System upgrade.
Afterwards, click on the Manage Software link.
Figure 4
What we want to do now is start adding and then validating the PATH to our previously
staged AgentCore zips, 12c Installer and Agent plugins directories. Oracle's documentation
says that you should stage all the files together in the same directory but you can just add
and validate files and directories successively.
Figure 5
Figure 6
Figure 7
Once we have validated all of our software, we are ready to proceed to the next section.
Click on the Deploy and Configure Agents tab in the Upgrade Agents Steps section.
Figure 8
Here, its just a matter of filling the blanks and adding a few details so that we can begin the
Agent deployment and configuration. Starting at the top, you can leave the Operational
Name with the default setting. If you run the deploy and config multiple times it will update
the Operational Name to something unique. Note: if you have successive failures during
this phase of the operation, keep in mind that this can fill up your /tmp directory. If you see
that you are starting to run out of space after running this operation too many times, simply
go into your /tmp directory and clear out some space.
In the Select Operation Type section we want to leave the defaults, ie both Deploy and
Configure should be selected. In the next section, Search Agents, simply click Search and
all your available agents should show up.
Figure 9
In the Agent Credentials section it should be OK to leave it with the default Use Oracle
Home Preferred Credentials because a good systems administrator has taken the time to set
up their environment properly, but if you're in a hurry and just want to do this down and
dirty then you can click on the Override Oracle Home Preferred Credentials tab and the fill
in the username and password applicable to your environment.
Figure 10
Click Next to go to the next page. Here you should fill in the blanks as appropriate. You
will need to enter your root user details in order to run the root.sh script, which runs during
the deploy and config phase.
Figure 11
At this point you will see a Confirmation at the top of the page and a Job #. Simply click on
the job link and hit <F5> on your keyboard occasionally to refresh the browser so you can
follow the progress of the Agent Deployment and Configuration.
Figure 12
Next Ops Center Experts Webcast: Cloud Management
Cloud Control 12c released for Windows 64-bit
Testing in May: Keep the bugs away
Install Oracle VM Server 3
DB Startup Fails on WORKAREA_SIZE_POLICY
Integrate EM OPS Center 12c in EM Cloud Control 12c
Integrate EM OPS Center 12c, EM Cloud Control 12c and Oracle VM Manager
ON-DEMAND WEBCAST: Oracle Database Lifecycle Management with Oracle
Enterprise Manager 12c, Now Available
Using Metric Extensions in EM12c
Security On Top Of Security
Register Oracle VM Manager 3.0 in Oracle
Enterprise Manager 12c
Show a printer friendly, save as PDF version of the Oracle Cloud Cookbook
Distribution of the Oracle Cloud Cookbook or derivative of the work in any form for
commercial purposes is prohibited unless prior permission is obtained from the copyright
holder.
Author: Roddy Rodstein
Change Log
Revision Change Description Updated By Date
1.0 First Release Roddy Rodstein 09/20/11
Table of Contents Oracle VM Manager 3.0 Registration in Oracle Enterprise Manager 12c Introduction
Oracle VM Manager 3.0 Registration Prerequisites
How to Register Oracle VM Manager in Oracle Enterprise Manager 12c Cloud Control
Oracle VM Manager 3.0 Registration in Oracle Enterprise Manager 12c Introduction The Oracle VM 3.0 product family; Oracle VM Server, Oracle VM Manager, Oracle VM
Templates and Oracle Virtual Assembly Builder can be managed with Oracle VM Manager
as well as Oracle Enterprise Manager 12c Cloud Control with a plug-in named "Oracle
Virtualization". Unlike Oracle VM 2.x, which could “only” be managed by Oracle VM
Manager or Oracle Enterprise Manager, not both, Oracle VM 3.0 can be managed
simultaneously by Oracle VM Manager 3.0 along with Oracle Enterprise Manager 12c
Cloud Control. The Oracle Virtualization plug-in with the Oracle VM Manager Core API
integrate “all” of Oracle VM Manager' functionally to the “Infrastructure Cloud” pages in
the Oracle Enterprise Manager 12c Cloud Control console.
Figure 1 shows the Infrastructure Cloud home page.
Tip: Oracle VM server pools, storage, networks, virtual machines, assemblies, etc, can be
configured before or after registering Oracle VM Manager in Oracle Enterprise Manager
12c Cloud Control.
A plug-in is an Enterprise Manager module that extends the managing and monitoring
capabilities of the Oracle Management Service (OMS). Oracle Enterprise Manager 12c
plug-ins have a server (OMS) and an agent (Oracle Management Agent (OMA))
component. The Oracle Management Service collects plug-in data in XML format. The
plug-in data is stored in the Oracle Management Repository (OMR) and is visualized by the
Oracle Management Service in Oracle Enterprise Manager 12c Cloud Control console.
Figure 2 shows each of the Enterprise Manager 12c Cloud Control components.
The Oracle Virtualization plug-in must be enabled on the Oracle Management Service
host(s) as well as be deployed to the Oracle VM Manager host. The Oracle Virtualization
plug-ins along with the Oracle Enterprise Manager 12c agent can be managed and deployed
using the Oracle Enterprise Manager 12c Cloud Control console.
Oracle VM Manager 3.0 Registration Prerequisites The following prerequisites must be meet before Oracle VM Manager can be registered in
Oracle Enterprise Manager 12c Cloud Control.
1. The Oracle Virtualization plug-in must be install and enabled on the Oracle
Management Service.
2. The Oracle VM Manager host must have the Oracle Management Agent (OMA)
and be a monitored target in Oracle Enterprise Manager 12c Cloud Control.
3. The Oracle VM Manager host must have the Oracle Virtualization plug-in.
4. The preferred credentials for the Oracle VM Manager host must be configured in
Oracle Enterprise Manager 12c Cloud Control.
5. The Oracle Management Service and the Oracle VM Manager host must have
consistent name resolution using DNS with both forward and reverse lookups.
How to Register Oracle VM Manager in Oracle Enterprise Manager 12c Cloud
Control The first step to register Oracle VM Manager is to authenticated to the Oracle Enterprise
Manager 12c Cloud Control console. Once authenticated, click the Enterprise menu, then
select Infrastructure Cloud, and click Home to access the Infrastructure Cloud page.
Figure 3 shows the path from the Enterprise menu.
From the Infrastructure Cloud page, there are two options to access the Register Oracle
VM Manager page.
1. Right click the Infrastructure Cloud link under the Target Navigation section,
then on the submenu click Register Oracle VM Manager
2. Click the Infrastructure Cloud drop down menu under the History menu, then
click Register Oracle VM Manager.
Figure 4 shows both menu options to select Register Oracle VM Manager.
From the Register Oracle VM Manager page, enter the Name, EM Agent URL, Oracle
VM Manager Core, Automatic Synchronization, Monitoring Credentials for Oracle
VM Manager, Administration Credentials for Oracle VM Manager / Use
Administration Credentials, Oracle VM Manager Console URL, then click the Submit
button.
Figure 5 shows the Oracle VM Manager registration page with the required entries listed in
Table 1.
Table 1 shows the syntax of the required entries on the Oracle VM Manager registration
page.
Table 1
Oracle VM Manager Registration Page
Title
Entry Selections and Entry Syntax
1. Name The name entered in the “Name” text box is
displayed on the Infrastructure Cloud
page.
2. EM Agent URL The EM Agent URL is selected by clicking
the magnifying glass icon. A pop-up window
will appear, select the Oracle VM Manager
agent from the list. The EM Agent URL
syntax is: “https://<AGENT-
FQDN>:3872/emd/main/”
Note: The Oracle VM Manager host can be
selected as long as the host is managed target
by OEM with the Oracle Virtualization plug-
in.
3. Oracle VM Manager Core Enter “tcp://<ORACLE VM MANAGER
HOST FQDN>:54321” in the
Oracle VM Manager Core URL text box.
4. Automatic Synchronization Select the Automatic Synchronization
check box to enable automated
synchronization between OEM and the
Oracle VM API Core.
5. Monitoring Credentials for Oracle
VM Manager
Enter the Oracle VM Manager admin user
name and the admin password in the
Monitoring Credentials for Oracle VM
Manager text fields.
6. Administration Credentials for
Oracle VM Manager / Use
Administration Credentials
Enter the Oracle VM Manager admin user
name and the admin password in the
Administration Credentials for Oracle VM
Manager text fields.
Select the Use Administration Credentials
check box.
7. Oracle VM Manager Console URL Enter the non-SSL Oracle VM Manager
URL, i.e.http://<ORACLE VM MANAGER
HOST
FQDN>:7001/ovm/console/faces/login.jspx
in the Oracle VM Manager Console URL
text box.
8. Submit Once all of the information has been entered,
click the Submit button to start the
registration job.
After the Submit button is clicked, a job named
REGISTEROVMMANAGER_SYSTEM is started. The
REGISTEROVMMANAGER_SYSTEM job can be accessed from a link on the Job
Activity page. The Job Activity page is accessed by clicking the Enterprise menu, Job,
then Activity.
Figure 6 show the REGISTEROVMMANAGER_SYSTEM job.
Once the REGISTEROVMMANAGER_SYSTEM job successfully completes, the
registered Oracle VM Manager system can be used to manage and monitor your virtual
infrastructure in Oracle Enterprise Manager 12c Cloud Control. For example, storage,
networking, pools, virtual machines and assemblies can be managed and monitored from
Oracle VM Manager as well as from Oracle Enterprise Manager 12c Cloud Control.
Oracle Desktop Virtualization Security Solution at DISA Mission Partner Conference 2012
building an appliance? physical ? virtual? production quality? use Oracle Linux
understanding memory allocation in oracle vm / xen
Oracle VM Administration: Oracle VM Server for x86 course schedule
figuring out cpu topology in oracle vm
Collaborate12 Starts Today!
Oracle VM Administration: Oracle VM Server for x86 - new Training
More Oracle VM templates for PeopleSoft and Oracle Enteprise Manager
Oracle Ebusiness Suite 12.1.3 Oracle VM templates
Eight New Oracle Database Assemblies Ready to Run In Your Oracle VM Cloud with
Oracle Enterprise Manager 12c
Oracle Enterprise Manager 11g
Architecture, System Design and Sizing
Show a printer friendly, save as PDF version of the Oracle Cloud Cookbook
Distribution of the Oracle Cloud Cookbook or derivative of the work in any form for
commercial purposes is prohibited unless prior permission is obtained from the copyright
holder.
Author: Roddy Rodstein
Table of Contents Change Log
Oracle Enterprise Manager 11g Architecture and System Design
Oracle Enterprise Manager 11g Inter Component Communication and Data Exchange
Oracle Enterprise Manager 11g Server Sizing
Oracle Enterprise Manager 11g System Design Considerations
Change Log
Revision Change Description Updated By Date
1.0 Oracle Enterprise Manager Architecture,
System Design and Sizing
Roddy
Rodstein 06/13/11
1.0 Table 2 and Table 5 Roddy
Rodstein 06/28/11
1.0 Table 2 OMA storage requirements Roddy
Rodstein 09/12/11
Oracle Enterprise Manager 11g Architecture and System
Design
Oracle Enterprise Manager is Oracle's systems management solution for the Oracle stack.
Oracle Enterprise Manager consists of a framework with product specific plug-ins for
Oracle and none Oracle technologies. The Oracle Enterprise Manager plug-ins provides the
administrative interface displayed in the Oracle Enterprise Manager Grid Control portal.
The Oracle Enterprise Manager framework is a traditional Oracle application consisting of
an Oracle database, an Oracle WebLogic server, a J2EE web application with an
application development frame work (ADF) administrative GUI, with client side agents. In
the context of Oracle Enterprise Manager, the Oracle database repository is named the
“Oracle Management Repository” or “OMR”. WebLogic is the J2EE platform called the
“Oracle Management Service” or “OMS”, that runs the Oracle Enterprise Manager J2EE
application. The administrative Web GUI is named Oracle Enterprise Manager Grid
Control. The client side agents are named the “Oracle Management Agents” or “OMA”.
Monitored hosts are referred to as targets. All of the Oracle Enterprise Manager
components are commonly referred to as Oracle Enterprise Manager or Enterprise
Manager.
The Oracle Management Repository is an Oracle 11g database that stores all of the
information collected by the Oracle Management Agents. The Oracle Management Agent is
a software application that runs on all monitored hosts facilitating a two-way
communication between the hosts and the Oracle Management Service. The Oracle
Management Service is deployed on a WebLogic server or a cluster of WebLogic servers in
the Oracle Middleware home. The Oracle Middleware home is the parent directory of the
Oracle WebLogic Server home. The Oracle Management Service collects data from the
Oracle Management Agents and uploads the data into the Oracle Management Repository.
The Oracle Management Repository formats the data which allows the Oracle Management
Service to visualize the data in the Oracle Enterprise Manager Grid Control portal.
Administrative operations made using the Oracle Enterprise Manager Grid Control console
are dispatched to targets from the Oracle Management Service. The Oracle Enterprise
Manager Grid Control portal can be access using Firefox, Safari, Chrome and Internet
Explorer on Linux, MAC, Unix and Windows hosts.
The Oracle Management Repository, the Oracle Management Service along with the Oracle
Management Agent can be installed in an all-in-one configuration on a single physical or
virtual Oracle Linux host or in a multiple node HA configuration.
Figure 1 shows an all-in-one installation with the Oracle Management Repository, the
Oracle Management Service and the Oracle Management Agent on a single Oracle Linux
host.
Figure 2 shows a multiple node Oracle Enterprise Manager installation with the Oracle
Management Repository hosted on a two-node RAC cluster, the Oracle Management
Service hosted on a two-node WebLogic cluster with three monitored Oracle Linux hosts
with the Oracle Management Agent.
Each of the Oracle Enterprise Manager components can be installed using the Oracle
Universal Installer (OUI) GUI, or using silent installation scripts, or with the software only,
configure later installation mode. The software only installation mode allows you to install
only the Oracle Enterprise Manager software binaries without any configurations. The
software only installation mode is ideal if you want to install the software at one point and
configure the software later.
Oracle Enterprise Manager 11g Inter Component
Communication and Data Exchange
The Oracle Enterprise Manager Grid Control portal, the Oracle Management Repository,
the Oracle Management Service and the Oracle Management Agents can be on different
hosts throughout your enterprise. Understanding Oracle Enterprise Manager's intra
component communication and data exchange will help you configure your firewalls in
order to allow Oracle Enterprise Manager to operate in your enterprise. During the Oracle
Enterprise Manager installation, the default communication ports for each component will
be selected and assigned. If the default ports are modified be sure to use the new port
assignments when you configure your firewalls.
Table 1 shows the default ports used by Oracle Enterprise Manager.
The Default Ports used by Oracle Enterprise Manager
Upload Ports Console Ports
HTTP 4889 (default) or Port range
from 4889 to 4898
The first available free port from the
range 7788 - 7798 is selected.
HTTPS 1159 (default) or Port Range
from 4899 to 4908
The first available free port from the
range 7799 - 7809 is selected.
Figure 3 shows Oracle Enterprise Manager's intra component communication and data
exchange.
Oracle Enterprise Manager 11g Server Sizing
Oracle Enterprise Manager server sizing is calculated by a) total number of managed
targets, b) the future growth of your Oracle Enterprise Manager environment and c) your
organization's high availability requirements. For example, if you know the total number of
managed targets, sizing WebLogic and the Oracle database is as simple as following Table
2, Table 3 and Table 4. As you add more targets, it is important to consider the future
growth of your Oracle Enterprise Manager environment as well as the ability to scale up or
to scale out with additional CPU, RAM and storage.
Table 2 shows the minimum physical memory and storage requirements for the WebLogic
server hosting the Oracle Management Service and the Oracle Management Agent.
Installation Type
Physical Memory
(RAM) Storage
Oracle Management Service 3 GB 1 GB
Middleware Home NA 6 GB
Oracle Management Agent 512 MB 1.2 GB
Table 3 shows the recommended minimum physical memory requirements for the
WebLogic server hosting the Oracle Management Service with a small, medium and large
number of monitored targets.
Deployment Size Physical Memory (RAM)
Small < 100 monitored targets 3 GB
Medium < 1000 monitored targets 4 GB
Large < 10,000 monitored targets 6 GB
Table 4 shows the recommended physical memory and storage requirements for the
database server hosting the Oracle Management Repository.
Deployment Size Physical Memory (RAM) Storage
Small < 100 monitored targets 2 GB 50 GB
Medium < 1000 monitored targets 4 GB 100 GB
Large < 10,000 monitored targets 6 GB 400 GB
Table 5 shows the storage requirements for a standalone Oracle Managemement Agent
installation.
Platform Storage
Linux 32 bit 850 MB
Linux x86_64 850 MB
Oracle Enterprise Manager 11g System Design
Considerations
The Oracle Management Repository, the Oracle Management Service along with the Oracle
Management Agent can be installed in an all-in-one configuration for evaluations and
testing or in an n-tier configuration for production. A production Oracle Enterprise
Manager environment should not be placed on a single server, nor should the Oracle
Management Repository be shared with production or test databases on the same server.
For production, the Oracle Management Repository as well as the WebLogic hosts should
be on dedicated virtual or physical servers. If your Oracle Enterprise Manager environment
starts out small make sure to have a plan to scale out your Oracle Enterprise Manager
infrastructure.
For the Oracle Management Repository, scaling out means moving to RAC for the Oracle
Management Repository database. An important consideration when scaling out an Oracle
Enterprise Manager environment is to determine if the underlying hardware where the
Oracle Management Repository database runs is capable to transition to RAC? If the
hardware is not capable to transition to RAC, it is possible to move and/or export the
Oracle Management Repository database to a different system with more resources.
Scaling out the WebLogic and Oracle Management Service tier entails adding a load
balancing (SLB) solution to front end a WebLogic cluster hosting the Oracle Management
Service. Adding a load balancer with additional WebLogic servers introduces a virtual host
name for the WebLogic cluster. Introducing a virtual host name into an existing Oracle
Enterprise Manager environment will require a reconfiguration of all of your Oracle
Management Agents to point to the new virtual host name. Reconfiguring a couple Oracle
Management Agents is no trouble, although reconfiguring a lot of Oracle Management
Agents would demand a long service window.
An additional consideration when scaling out the WebLogic and Oracle Management
Service tier is providing shared storage to hosts the XML files and the software library.
Next Ops Center Experts Webcast: Cloud Management
Cloud Control 12c released for Windows 64-bit
Testing in May: Keep the bugs away
Install Oracle VM Server 3
DB Startup Fails on WORKAREA_SIZE_POLICY
Integrate EM OPS Center 12c in EM Cloud Control 12c
Integrate EM OPS Center 12c, EM Cloud Control 12c and Oracle VM Manager
ON-DEMAND WEBCAST: Oracle Database Lifecycle Management with Oracle
Enterprise Manager 12c, Now Available
Using Metric Extensions in EM12c
Security On Top Of Security
Oracle Linux 5 Installation
Distribution of the Oracle Cloud Cookbook or derivative of the work in any form for
commercial purposes is prohibited unless prior permission is obtained from the copyright
holder.
Author: Roddy Rodstein
This chapter of the Oracle Cloud Cookbook reviews how to perform an Oracle Linux 5
installation from the DVD/CD-ROM, using the graphical (GUI) mode. The chapter starts
with an Oracle Linux installation and Oracle Linux Support introduction followed by the
Oracle Linux 5 installation from the DVD/CD-ROM, using the graphical (GUI) mode. The
chapter concludes with the steps on how to remove Oracle Linux from a system.
Note: Oracle Linux is a Red Hat Enterprise Linux clone. Oracle offers support for Oracle
Linux and Red Hat Enterprise Linux. Red Hat offers support exclusively for Red Hat
Linux.
Table of Contents Change Log
Oracle Linux Installation and Oracle Linux Support Introduction
Oracle Linux Packaging and Support Pricing
Oracle Linux 5 Installation from the DVD/CD-ROM, using the Graphical (GUI) Mode
Linux Patch Management with Free Updates and Errata from Oracle
How to Uninstall or Remove Oracle Linux
Change Log
Revision Change Description Updated
By Date
1 First Release Roddy
Rodstein 06/22/11
1.1
Linux Patch Management with
Free Updates and Errata from
Oracle
Roddy
Rodstein 04/29/12
Oracle Linux Installation and Oracle Linux Support
Introduction
Oracle Linux can be installed either from a CD-ROM drive or over the network using a pre-
boot execution environment (PXE). To install Oracle Linux using the CD-ROM or PXE
boot method, visit the Oracle eDelivery Linux portal to download the Oracle Linux media.
The Oracle Linux media is delivered as a zip file that contains a CD or a DVD with an
Oracle Linux ISO file. The Oracle Linux ISO file can be burned as a bootable disk and used
to install Oracle Linux from a CD-ROM drive.
An Oracle Linux PXE boot installation requires several additional steps; for example, a
boot server and a kickstart file to automate the Oracle VM server installation must be
created. The boot server allows a bare-metal system to automatically receive an IP address
via DHCP, load a kernel via TFTP, and then boot without an operating system. Once the
bare-metal server boots, Oracle Linux can be installed using the installation media or a
kickstart file to automate the Oracle Linux installation.
The graphical installation program and the installation steps are similar for Oracle Linux 5,
5U1, 5U2, 5U3, 5U4, 5U5, 5U6, 5U7 and 5U8. The Oracle Linux installation media is
freely available from the Oracle eDelivery Linux portal as a CD collection (multiple
downloads) and as a single DVD (single download) for Oracle Linux 5, 5U1, 5U2, 5U3,
5U4, 5U5, 5U6, 5U7 and 5U8. If you install Oracle Linux using the CD collection, start the
installation with CD #1, and when prompted enter the requested CDs.
List 1 reviews the Oracle Linux installation considerations.
1. Disk Partitioning Setup.
Depending upon your comfort level with installing Linux, you can accept the default
partition layout or select a custom layout.
The default partition layout.
Selecting the default partitioning layout will create a 100MB “/boot” partition and a
LVM with two volume groups, a large root “/” partition and a swap partition.
Custom layout.
100% customizable.
2. Network Configuration
Configure a static IP address or use DHCP.
3. Time Zone Selection
Select the time zone settings for your area
Configure UTC for the system clock
4. Package Installation
Use the default software selection and click on Next
5. Firewall Configuration
For the initial OS and Oracle technology product installations, enable or disable the
firewall
6. SELinux
For the initial OS and Oracle technology product installations, enable or disable
SELinux
Oracle recommends installing Oracle Linux and Red Hat Enterprise using the default
software package selection without any customization. Using the default software packages
without customizations includes most of the prerequisite packages for Oracle technology
products and helps limit the number of manual prerequisite checks. After an Oracle Linux
and/or Red Hat Enterprise Linux installation, Oracle recommends to register your server
with the Unbreakable Linux Network (ULN) and to install the Legacy Software
Development packages by typing “up2date -i @ Legacy Software Development“ or if you
have a local yum repository type “yum groupinstall "Legacy Software Development"” to
install most of the remaining Oracle technology product prerequisite packages.
The Oracle Unbreakable Linux Network is a cloud resource for the Oracle Linux Support
program that hosts the Oracle Linux, Oracle VM, Exadata and Exalogic RPM repositories,
including software patches, updates and fixes. The Oracle Unbreakable Linux Network
portal is located at http://linux.oracle.com. The Oracle Unbreakable Linux Network portal
provides a simple dashboard and management interface for registered systems and RPM
channels. The Oracle Unbreakable Linux Network repositories are used to patch and install
RPMs for Oracle Linux, Oracle VM, Exadata and Exalogic systems. Oracle Linux support
customers have the option to access patchs and RPMs for Oracle Linux, Oracle VM,
Exadata and Exalogic systems from the Oracle Unbreakable Linux Network using the
up2date program, or from a local yum repository.
The Unbreakable Linux Network is password protected. Before you can access the Oracle
Unbreakable Linux Network you must have a valid Oracle Linux support contract, CSI
number and an Oracle Single Sign-on account. Your existing My Oracle Support (MOS)
Oracle Single Sign-on account will not work with the Oracle Unbreakable Linux Network
until the account has been registered with the Oracle Unbreakable Linux Network. Click
the Register link at the Oracle Unbreakable Linux Network portal to a) create a new Oracle
Single Sign-on account or to b) associate your existing Oracle Single Sign-on account with
the Oracle Unbreakable Linux Network. Once you have a valid support contract, and CSI
number, you can register Oracle Linux systems at the Unbreakable Linux Network by
typing “up2date --register” as root.
In March 2012, Oracle announced that Oracle Linux 4, 5 and 6 latest RPM patches, updates
and erratas are available at no cost from separate yum repositories on http://public-
yum.oracle.com. To to keep Oracle Linux and Red Hat Enterprise Linux system up to date
to the latest update version, subscribe hosts to their respective "_latest" repository. The free
Oracle Linux 4, 5 and 6 RPM patches, updates and erratas do not include Oracle support or
any of the benefits of the Oracle Linux Support program.
The next example shows how to download the public-yum-el5.repo file from Oracle, then
use the public-yum-el5.repo file to update the host, and install the Legacy Software
Development packages. Type the following commands as root:
# cd /etc/yum.repos.d/
# wget http://public-yum.oracle.com/public-yum-el5.repo
# yum update
# yum groupinstall "Legacy Software Development"
Oracle Linux Packaging and Support Pricing
Oracle Linux is not a licensed Oracle technology product. The Oracle Linux installation
media is freely available from the Oracle eDelivery Linux portal. Support for Oracle Linux
and access to the Unbreakable Linux Network is available as an add-on component of
Oracle’s enterprise support package as well as with Sun x86 hardware as an add-on Premier
Support for Systems package. Oracle Linux running on third-party hardware (not on Sun
Hardware) is always sold as an add-on support component of Oracle’s enterprise support
package.
Premier Support for Systems costs 12% of the net Sun system purchase price and includes
comprehensive support for the system hardware and firmware, as well as operating system
support for Oracle Linux, Solaris x86, Solaris 11 Express, and Oracle VM for x86. Along
with hardware and firmware support, Premier Support for Systems includes operating
system support for one or more virtual instances Oracle Linux, Solaris 10 x86, and Solaris
11 Express x86 running on Oracle VM for x86.
Support for Oracle Linux installed on third-party hardware is sold in three packages: Oracle
Linux Network, Oracle Linux Basic, and Oracle Linux Premier.
List 2 highlights the difference between the three different Oracle Linux support packages.
Oracle Linux Network Support includes access to the Unbreakable Linux
Network for patches, fixes and security alerts. Oracle Linux Network support
does not include 24x7 global OS support. For example, Oracle Linux Network
Support does not include the ability to create Service Requests (SRs) to work
with Oracle support.
Oracle Linux Basic Support includes 24x7 global OS support, access to the
Unbreakable Linux Network for patches, fixes and security alerts, the Linux
Management Pack (An Oracle Enterprise Manager Linux server lifecycle
management Plug-in), and Oracle's OCFS2 cluster software for servers with up
to two sockets.
Oracle Linux Premier Support includes 24x7 global OS support, access to the
Unbreakable Linux Network for patches, fixes and security alerts, the Linux
Management Pack (An Oracle Enterprise Manager Linux server lifecycle
management Plug-in), Oracle's OCFS2 cluster software, Premier backports, and
Oracle Lifetime Support for servers with four or more sockets.
Oracle Linux 5 Installation from the DVD/CD-ROM,
using the Graphical (GUI) Mode
This section reviews how to install Oracle Linux and Red Hat Enterprise Linux from the
DVD/CD-ROM, using the graphical (GUI) mode.
1- Boot the server using the DVD ISO image. At the boot prompt, press the Enter key to
start the Oracle Linux installation in graphical mode.
Figure 1
2- On the CD Found window, you can perform a media test to validate the integrity of the
installation media. The media test is optional and time consuming. In this example, we will
not perform a media test.
Press the tab key to select the Skip key. Once the Skip key is selected, press the Enter key
to proceed.
Figure 2
3- On the Welcome screen, click the Next button or Alt+N to proceed.
Note: to read the Release Notes, press the Release Notes button or press Alt+R.
Figure 3
4- On the Language Selection screen, select the preferred language that will be used
during the installation process. In this example, select the default language, English
(English).
Accept the default English (English) language selection, then click the Next button or
press Alt+N to proceed.
Figure 4
5- On the Keyboard Selection screen, select the desired keyboard setting for the system. In
this example, select the default keyboard selection, US English.
Accept the default US English keyboard selection, then click the Next button or press
Alt+N to proceed.
Figure 5
6- A partition tableWarning dialogue box will appear after you make your Keyboard
selection. Click the Yes button or press Alt+Y to proceed with the installation. If you click
No, the installation will terminate.
Figure 6
7- On the Partitioning screen, you can select the default partitioning layout or create your
own partitioning layout. Selecting the default partitioning layout will create a 100MB
“/boot” partition and a LVM with two volume groups, a large root “/” partition and a swap
partition.
In this example, accept the defaults, click the Next button or press Alt+N to proceed.
Figure 7
8- A partition table Warning dialogue box will appear after clicking the previous Next
button. Click the Yes or press Alt+Y to proceed.
Figure 8
9- On the Networking configuration screen, you can accept the default DHCP setting or
configure the networking manually.
To use DHCP, accept the defaults, and click the Next button or press Alt+N to proceed.
Figure 9
10- To configure the networking manually, click the Edit button or press Alt+E to access
the Edit Interface screen. On the Edit Interface screen, select Manual Configuration and
enter the IP address and Netmask. Next, unselect Enable IPv6 support. Click the Ok
button or press ALT+O to save the networking setting and to return to the Networking
configuration screen.
Figure 10
11- On the Networking configuration screen, select manually and enter the hostname,
gateway and DNS information. Click the Next button or press Alt+N to proceed.
Figure 11
12- On the Time Zone screen, select the time zone for your area by clicking your region on
the map. Accept the default System clock uses UTC setting, and click the Next button or
press Alt+N to proceed.
Figure 12
13- On the Root Password screen enter a root password for the server, then click the Next
button or press Alt+N to proceed.
Figure 13
14- On the Software Selection screen, you can accept the default selections or select one or
more roles for the server and/or customize the entire software selection by selecting the
Customize now.
Oracle recommends installing Linux using the default software package selection without
any customization. Using the default software packages without customizations includes
most of the prerequisite packages and helps limit the number of manual checks.
Accept the default software package selection without any customization, then click the
Next button or press Alt+N to proceed.
Figure 14
15- On the About to Install screen, click the Next button or press Alt+N to start the
installation.
Note: If you are installing Oracle Linux using the CD ISO images, you will be prompted to
enter additional CDs.
Figure 15
16- On the Installation Progress screen, you will see a dialogue box about the hard drive
being formatted. Once the hard drive is formatted, the installation begins and you see the
progress indicators. The installation will take a few minutes.
Figure 16
17- The Congratulations screen informs you that the installation is complete, and to
remove your DVD media from the system and to reboot the system.
Remove the CD/DVD media from the system, and click the Next button or press Alt+t to
reboot the system.
Figure 17
18- After the system reboots, you will be presented with the Welcome screen. Click the
Forward button or press Alt+F to proceed.
Figure 18
19- On the License Agreement screen, accept the license agreement and click the
Forward button or press Alt+F to proceed.
Figure 19
20- On the Firewall screen, change the default Enabled selection to Disabled and click the
Forward button or press Alt+F to proceed.
Figure 20
21- Disabling the firewall opens a dialogue window that informs you about changing the
security setting of the system. Click the Yes button or press ALT+Y to proceed.
Figure 21
22- On the SELinux screen, change the default Enabled selection to Disabled and click
the Forward button or press Alt+F to proceed.
Figure 22
23- Disabling SELinux opens a dialogue window that informs you about changing the
SELinux setting and the need to reboot the system. Click the Yes button or press ALT+Y
to proceed.
Figure 23
24- On the Kdump screen, accept the default setting and click the Forward button or press
Alt+F to proceed.
Figure 24
25- On the Date and Time screen you can configure the Date and Time and Network
Time Protocol (NTP) settings. Configure the Date and Time and Network Time
Protocol settings, then click the Forward button or press Alt+F to proceed.
Figure 25
26- On the Create User screen, you can create new system users. Click the Forward
button or press Alt+F to proceed.
Figure 26
27- On the Sound Card screen, click the Forward button or press Alt+F to proceed.
Figure 27
28- On the Additional CDs screen, click the Finish button or press Alt+F to complete the
installation and to reboot the system.
Figure 28
29- As soon as the system has rebooted, you are presented with the Oracle Linux 5 login
screen. Once you have successfully authenticated, you have a fully functional GNOME
desktop environment.
Figure 29
Linux Patch Management with Free Updates and Errata
from Oracle
In March 2012, Oracle announced that Oracle Linux 4, 5 and 6 latest RPM patches, updates
and erratas are available at no cost from separate yum repositories on http://public-
yum.oracle.com. To to keep Oracle Linux and Red Hat Enterprise Linux system up to date
to the latest update version, subscribe hosts to their respective "_latest" repository. The free
Oracle Linux 4, 5 and 6 RPM patches, updates and erratas do not include Oracle support or
any of the benefits of the Oracle Linux Support program.
The Oracle Linux Support program offers the following benefits over and above the free
Oracle Linux RPM patches, updates and erratas:
Full indemnification against intellectual property claims. Remember the SCO
lawsuits?
Use of the Oracle Enterprise Manager 12c Systems Management Plug-in for Linux
for provisioning, patching, management and monitoring. The Systems
Management Plug-in for Linux has feature parity with Red Hat Satellite Server.
Access to additional Oracle software channels on the Unbreakable Linux Network
(ULN).
The ability to create Support Requests with Oracle' World Class support
organization.
The Oracle public yum server latest RPM channels include the base OS version installation
RPM packages along with the latest software patches, updates and fixes. Patch jobs using
the latest RPM channel update hosts to their respected latest version update with the latest
software patches, updates and fixes. A patch job executed on a Oracle Linux 5U2 host
would update the host from 5U2 to 5U8 with the latest latest software patches, updates and
fixes. To keep a host at its respected update level, access to the Unbreakable Linux
Network Rpm channels is required where it is possible to remove the default
“el*/ol*_latest” RPM channel and select the el*/ol*_base along with the el*/ol*_patch
RPM channel. When hosts are patched using the el*/ol*_base and el*/ol*_patch RPM
channels, the hosts are patched with the latest software patches, updates and fixes from
their respected update channel, i.e. 5U2, 5U3, 5U4, 5U6 and 5U7 not with the latest, i.e.
5U8 channel.
To configure an Oracle Linux, Red Hat Enterprise Linux 5 host to use Oracle's public yum
repository, as root, change to the /etc/yum.repos.d/ directory and type “wget http://public-
yum.oracle.com/public-yum-el5.repo” to download the public-yum-el5.repo file. Next, type
“yum update” to patch the host.
The next example shows how to download the public-yum-el5.repo file from Oracle and to
update an Oracle Linux or Red hat Enterprise Linux host. Type the following commands as
root:
# cd /etc/yum.repos.d/
# wget http://public-yum.oracle.com/public-yum-el5.repo
# yum update
The next examples shows the public-yum-el5.repo file.
Tip: You can enable any of the repositories in the public-yum-el5.repo file by changing
enabled=0 to enabled=1.
# vi /etc/yum.repos.d/public-yum-el5.repo
[el5_latest]
name=Oracle Linux $releasever Latest ($basearch)
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL5/latest/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=1
[el5_ga_base]
name=Oracle Linux $releasever GA installation media copy ($basearch)
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/0/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[el5_u1_base]
name=Enterprise Linux $releasever Update 1 installation media copy ($basearch)
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/1/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[el5_u2_base]
name=Enterprise Linux $releasever Update 2 installation media copy ($basearch)
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/2/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[el5_u3_base]
name=Enterprise Linux $releasever Update 3 installation media copy ($basearch)
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/3/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[el5_u4_base]
name=Enterprise Linux $releasever Update 4 installation media copy ($basearch)
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/4/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[el5_u5_base]
name=Enterprise Linux $releasever Update 5 installation media copy ($basearch)
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/5/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[ol5_u5_base]
name=Oracle Linux $releasever Update 5 installation media copy ($basearch)
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL5/5/base/x86_64/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[ol5_u6_base]
name=Oracle Linux $releasever Update 6 installation media copy ($basearch)
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL5/6/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[ol5_u7_base]
name=Oracle Linux $releasever Update 7 installation media copy ($basearch)
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL5/7/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[ol5_u8_base]
name=Oracle Linux $releasever Update 8 installation media copy ($basearch)
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL5/8/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[el5_addons]
name=Enterprise Linux $releasever Add ons ($basearch)
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/addons/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[el5_oracle_addons]
name=Oracle Software addons for Enterprise Linux $releasever ($basearch)
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/oracle_addons/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[ol5_UEK_latest]
name=Latest Unbreakable Enterprise Kernel for Oracle Linux $releasever ($basearch)
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL5/UEK/latest/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[ol5_UEK_base]
name=Unbreakable Enterprise Kernel for Oracle Linux $releasever ($basearch)
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL5/UEK/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
[el5_unsupported]
name=Productivity Applications for Enterprise Linux $releasever ($basearch)
baseurl=http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/unsupported/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0
How to Uninstall or Remove Oracle Linux
There is not an option to “uninstall” Oracle Linux, although there are many ways to remove
Oracle Linux from a system. The method you select to remove Oracle Linux or Red Hat
Enterprise Linux from a system will depend on your organizations security requirements.
For example, if the data on the hard drive needs to be securely deleted, formatting or re-
partitioning the hard drive will not completely remove the data from the disks. To
completely wipe Oracle Linux or Red Hat Enterprise Linux as well as the data from the
hard disks, boot the system using data destruction application like Darik's Boot and Nuke
(DBAN) and wipe all of the disks. If the data on the hard drive does not need to be securely
deleted, you could a) delete all the files on the disks b) format or re-partition the hard drives
c) uninstall the bootloader and d) install another operating system on top of the existing
one.
List 3 shows several of the options to remove Oracle Linux from a system.
Boot the system using data destruction application like Darik's Boot and Nuke
(DBAN) and wipe all of the disks.
Delete all the files on the disks, i.e. type “rm -rf /” as root.
Format or delete the partitions.
Uninstall the bootloader.
Install another operating system on top of Oracle Linux or Red Hat Enterprise
Linux.
Accelerate your Linux Deployments with Oracle Validated Configurations
LIVE WEBCAST: Top Tips to Get the Most Out of Your Linux Deployments
RFC5424 or cee-enhanced syslog?
MongoDB, BSON and templates...
rsyslog templates & json
rsyslog & elasticsearch: async replication and timeout
Oracle Linux and Oracle VM Hardware Certification Program
rsyslog & ElasticSearch: using dynamic index and type
new rsyslog v5-beta released
rsyslog group on Facebook
Oracle Linux 6 Installation
Distribution of the Oracle Cloud Cookbook or derivative of the work in any form for commercial purposes is prohibited unless prior permission is obtained from the copyright holder. Author: Roddy Rodstein This chapter of the Oracle Cloud Cookbook reviews how to perform an Oracle Linux 6 installation from the DVD/CD-ROM, using the graphical (GUI) mode. The chapter starts with an Oracle Linux installation and Oracle Linux Support introduction followed by the Oracle Linux 6 installation from the DVD/CD-ROM, using the graphical (GUI) mode. The chapter concludes with the steps on how to remove Oracle Linux from a system. Note: Oracle Linux is a Red Hat Enterprise Linux clone. Oracle offers support for Oracle Linux and Red Hat Enterprise Linux. Red Hat offers support exclusively for Red Hat Linux. Table of Contents Change Log Oracle Linux Installation and Oracle Linux Support Introduction Oracle Linux Packaging and Support Pricing Oracle Linux 6 Installation from the DVD/CD-ROM, using the Graphical (GUI) Mode Linux Patch Management with Free Updates and Errata from Oracle How to Uninstall or Remove Oracle Linux Change Log
Revision Change Description Updated By Date
1 First Release Roddy
Rodstein 07/15/11
1.1 Linux Patch Management with Free Updates
and Errata from Oracle
Roddy
Rodstein 04/29/12
Oracle Linux Installation and Oracle Linux Support Introduction
Oracle Linux can be installed either from a CD-ROM drive or over the network using a pre-boot execution environment (PXE). To install Oracle Linux using the CD-ROM or PXE boot method, visit the Oracle eDelivery Linux portal to download the Oracle Linux media. The Oracle Linux media is delivered as a zip file that contains a CD or a DVD with an Oracle Linux ISO file. The Oracle Linux ISO file can be burned as a bootable disk and used to install Oracle Linux from a CD-ROM drive. An Oracle Linux PXE boot installation requires several additional steps; for example, a boot server and a kickstart file to automate the Oracle VM server installation must be created. The boot server allows a bare-metal system to automatically receive an IP address via DHCP, load a kernel via TFTP, and then boot without an operating system. Once the bare-metal server boots, Oracle Linux can be installed using the installation media or a kickstart file to automate the Oracle Linux installation. The graphical installation program and the installation steps are identical for Oracle Linux 6,and 6.1. The Oracle Linux installation media is freely available from the Oracle eDelivery Linux portal as a single DVD (single download) for Oracle Linux 6 and 6.1. List 1 reviews the Oracle Linux installation considerations. 1. Disk Partitioning Setup. Depending upon your comfort level with installing Linux, you can accept the default partition layout or select a custom layout.
The default partition layout.
Selecting the default partitioning layout will create a 100MB “/boot” partition and a LVM with two volume groups, a large root “/” partition and a swap partition.
Custom layout.
100% customizable.
2. Network Configuration
Configure a static IP address or use DHCP.
3. Time Zone Selection
Select the time zone settings for your area
Configure UTC for the system clock
4. Package Installation
Use the default software selection and click on Next
Oracle recommends installing Oracle Linux and Red Hat Enterprise using the default software package selection without any customization. Using the default software packages without customizations includes most of the prerequisite packages for Oracle technology products and helps limit the number of manual prerequisite checks. After an Oracle Linux and/or Red Hat Enterprise Linux installation, Oracle recommends to register your server with the Unbreakable Linux Network (ULN) and to install the Legacy Software Development packages by typing “yum groupinstall @ Legacy Software Development“ to install most of the remaining Oracle technology product prerequisite packages. The Oracle Unbreakable Linux Network is a cloud resource for the Oracle Linux Support program that hosts the Oracle Linux, Oracle VM, Exadata and Exalogic RPM repositories, including software patches, updates and fixes. The Oracle Unbreakable Linux Network portal is located at http://linux.oracle.com. The Oracle Unbreakable Linux Network portal provides a simple dashboard and management interface for registered systems and RPM channels. The Oracle Unbreakable Linux Network repositories are used to patch and install RPMs for Oracle Linux, Oracle VM, Exadata and Exalogic systems. Oracle Linux support customers have the option to access patchs and RPMs for Oracle Linux, Oracle VM, Exadata and Exalogic systems from the Oracle Unbreakable Linux Network using the up2date program, or from a local yum repository. The Unbreakable Linux Network is password protected. Before you can access the Oracle Unbreakable Linux Network you must have a valid Oracle Linux support contract, CSI number and an Oracle Single Sign-on account. Your existing My Oracle Support (MOS) Oracle Single Sign-on account will not work with the Oracle Unbreakable Linux Network until the account has been registered with the Oracle Unbreakable Linux Network. Click the Register link at the Oracle Unbreakable Linux Network portal to a) create a new Oracle Single Sign-on account or to b) associate your existing Oracle Single Sign-on account with the Oracle Unbreakable Linux Network. Once you have a valid support contract, and CSI number, you can register Oracle Linux systems at the Unbreakable Linux Network by typing “up2date -register” as root. In March 2012, Oracle announced that Oracle Linux 4, 5 and 6 latest RPM patches, updates and erratas are available at no cost from separate yum repositories on http://public-yum.oracle.com. To to keep Oracle Linux and Red Hat Enterprise Linux system up to date to the latest update version, subscribe hosts to their respective "_latest" repository. The free Oracle Linux 4, 5 and 6 RPM patches, updates and erratas do not include Oracle support or any of the benefits of the Oracle Linux Support program. The next example shows how to download the public-yum-el5.repo file from Oracle, then use the public-yum-el5.repo file to update the host, and install the Legacy Software Development packages. Type the following commands as root:
# cd /etc/yum.repos.d/ # wget http://public-yum.oracle.com/public-yum-el5.repo # yum update # yum groupinstall @ Legacy Software Development
Oracle Linux Packaging and Support Pricing
Oracle Linux is not a licensed Oracle technology product. The Oracle Linux installation media is freely available from the Oracle eDelivery Linux portal. Support for Oracle Linux and access to the Unbreakable Linux Network is available as an add-on component of Oracle’s enterprise support package as well as with Sun x86 hardware as an add-on Premier Support for Systems package. Oracle Linux running on third-party hardware (not on Sun Hardware) is always sold as an add-on support component of Oracle’s enterprise support package. Premier Support for Systems costs 12% of the net Sun system purchase price and includes comprehensive support for the system hardware and firmware, as well as operating system support for Oracle Linux, Solaris x86, Solaris 11 Express, and Oracle VM for x86. Along with hardware and firmware support, Premier Support for Systems includes operating system support for one or more virtual instances Oracle Linux, Solaris 10 x86, and Solaris 11 Express x86 running on Oracle VM for x86. Support for Oracle Linux installed on third-party hardware is sold in three packages: Oracle Linux Network, Oracle Linux Basic, and Oracle Linux Premier. List 2 highlights the difference between the three different Oracle Linux support packages.
Oracle Linux Network Support includes access to the Unbreakable Linux Network for patches, fixes and security alerts. Oracle Linux Network support does not include 24x7 global OS support. For example, Oracle Linux Network Support does not include the ability to create Service Requests (SRs) to work with Oracle support.
Oracle Linux Basic Support includes 24x7 global OS support, access to the Unbreakable Linux Network for patches, fixes and security alerts, the Linux Management Pack (An Oracle Enterprise Manager Linux server lifecycle management Plug-in), and Oracle's OCFS2 cluster software for servers with up to two sockets.
Oracle Linux Premier Support includes 24x7 global OS support, access to the Unbreakable Linux Network for patches, fixes and security alerts, the Linux Management Pack (An Oracle Enterprise Manager Linux server lifecycle management Plug-in), Oracle's OCFS2 cluster software, Premier backports, and Oracle Lifetime Support for servers with four or more sockets.
Oracle Linux 6 Installation from the DVD/CD-ROM, using the Graphical (GUI) Mode
This section reviews how to install Oracle Linux and Red Hat Enterprise Linux from the DVD/CD-ROM, using the graphical (GUI) mode. 1- Boot the server using the DVD ISO image. At the boot prompt, press the Enter key to start the Oracle Linux installation in graphical mode. Figure 1
2- On the CD Found window, you can perform a media test to validate the integrity of the installation media. The media test is optional and time consuming. In this example, we will not perform a media test. Press the tab key to select the Skip key. Once the Skip key is selected, press the Enter key to proceed. Figure 2
3- On the Welcome screen, click the Next button or Alt+N to proceed. Figure 3
4- On the Language Selection screen, select the preferred language that will be used during the installation process. In this example, select the default language, English (English). Accept the default English (English) language selection, then click the Next button or press Alt+N to proceed. Figure 4
5- On the Keyboard Selection screen, select the desired keyboard setting for the system. In this example, select the default keyboard selection, US English. Accept the default US English keyboard selection, then click the Next button or press Alt+N to proceed. Figure 5
6- On the Storage Device screen, you can select the Basic Storage Devices or the Specialized Storage Devices options.
In this example, accept the default Basic Storage Devices option, click the Next button or press Alt+N to proceed. Figure 6
7- A disk initialization Warning dialogue box will appear after you make your Storage Device selection. Click the Re-initialize button or press Alt+R to proceed with the installation. Figure 7
8- On the Networking configuration screen, you can accept the default DHCP setting or configure the networking manually. To use DHCP, accept the defaults, and click the Next button or press Alt+N to proceed. Click the Configure Network button to review the network configurations.
Figure 8
9- From the Network Connections screen, select the desired connection, i.e. eth0 and click the Edit button. Figure 9
10- On the Editing System screen select the Connect automatically checkbox to enable the interface automatically start when the system is starts. To configure the networking manually, click
the desired tab to configure the selected interface. Click the Apply button to save the networking setting and to return to the Network Connections screen. Figure 10
11- On the Networking Connections screen, click the Close button or press Alt+C, next click the Next button or Alt+N to proceed. Figure 11
12- On the Time Zone screen, select the time zone for your area by clicking your region on the map. Accept the default System clock uses UTC setting, and click the Next button or press Alt+N to proceed. Figure 12
13- On the Root Password screen enter a root password for the server, then click the Next button or press Alt+N to proceed. Figure 13
14- On the Installation Type screen, you can select the desired partitioning layout or create your own partitioning layout. In this example, accept the default Replace Existing Linux System(s), click the Next button or press Alt+N to proceed. Note: To edit the default partitioning layout, select Review and modify partitioning layout option and click Next or Alt+N. Figure 14
15- A partition table Warning dialogue box will appear after clicking the previous Next button. Click the Write changes to disk or press Alt+W to proceed. Figure 15
16- On the Software Selection screen, you can accept the default selections or select one or more roles for the server and/or customize the entire software selection by selecting the Customize now. Note: The default selections will not install a desktop environment. Oracle recommends installing Linux using the default software package selection without any customization. Using the default software packages without customizations includes most of the prerequisite packages and helps limit the number of manual checks. Select the Desktop option without any customization, then click the Next button or press Alt+N to proceed. Figure 16
17- On the Installation Progress screen, you will see a dialogue box about the installation starting. Once the Starting Installation process screen is gone, the installation begins and you see the progress indicators. The installation will take a few minutes. Figure 17
18- The Congratulations screen informs you that the installation is complete, and to remove your DVD media from the system and to reboot the system.
Remove the CD/DVD media from the system, and click the Next button or press Alt+t to reboot the system. Figure 18
19- After the system reboots, you will be presented with the Welcome screen. Click the Forward button or press Alt+F to proceed. Figure 19
20- On the License Agreement screen, accept the license agreement and click the Forward button or press Alt+F to proceed. Figure 20
21- On the Set Up Software Updates screen, select the desired Unbrekable Linux Network registration option, then click the Forward button or press ALT+F to proceed. Figure 21
22- If you selected No from the previous screen, click the No thanks, I'll connect later. button to proceed. Figure 22
23- On the Finish Update Setup screen click the Forward button or press ALT+F to proceed. Figure 23
24- On the Create User screen, you can create new system users. Click the Forward button or press Alt+F to proceed.
Figure 24
25- On the Date and Time screen you can configure the Date and Time and Network Time Protocol (NTP) settings. Configure the Date and Time and Network Time Protocol settings, then click the Forward button or press Alt+F to proceed. Figure 25
26- On the Kdump screen, accept the default setting and click the Forward button or press Alt+F to proceed.
Figure 26
27- On the Login screen, click on the desired user name and enter the password to access the desktop. Figure 27
28- Once you have successfully authenticated, you have a fully functional GNOME desktop environment. Figure 28
Linux Patch Management with Free Updates and Errata from Oracle
In March 2012, Oracle announced that Oracle Linux 4, 5 and 6 latest RPM patches, updates and erratas are available at no cost from separate yum repositories on http://public-yum.oracle.com. To to keep Oracle Linux and Red Hat Enterprise Linux system up to date to the latest update version, subscribe hosts to their respective "_latest" repository. The free Oracle Linux 4, 5 and 6 RPM patches, updates and erratas do not include Oracle support or any of the benefits of the Oracle Linux Support program. The Oracle Linux Support program offers the following benefits over and above the free Oracle Linux RPM patches, updates and erratas:
Full indemnification against intellectual property claims. Remember the SCO lawsuits?
Use of the Oracle Enterprise Manager 12c Systems Management Plug-in for Linux for provisioning, patching, management and monitoring. The Systems Management Plug-in for Linux has feature parity with Red Hat Satellite Server.
Access to additional Oracle software channels on the Unbreakable Linux Network (ULN).
The ability to create Support Requests with Oracle' World Class support organization.
The Oracle public yum server latest RPM channels include the base OS version installation RPM packages along with the latest software patches, updates and fixes. Patch jobs using the latest RPM channel update hosts to their respected latest version update with the latest software patches, updates and fixes. A patch job executed on a Oracle Linux 6 host would update the host from 6 to 6U2 with the latest latest software patches, updates and fixes. To keep a host at its respected update level, access to the Unbreakable Linux Network Rpm channels is required where it is possible to remove the default “el*/ol*_latest” RPM channel and select the el*/ol*_base along with the el*/ol*_patch RPM channel. When hosts are patched using the el*/ol*_base and el*/ol*_patch
RPM channels, the hosts are patched with the latest software patches, updates and fixes from their respected update channel, i.e. 6, 6U1, 6U2. To configure an Oracle Linux, Red Hat Enterprise Linux 6 host to use Oracle's public yum repository, as root, change to the /etc/yum.repos.d/ directory and type “wget http://public-yum.oracle.com/public-yum-ol6.repo” to download the public-yum-ol6.repo file. Next, type “yum update” to patch the host. The next example shows how to download the public-yum-ol6.repo file from Oracle and to update an Oracle Linux or Red hat Enterprise Linux host. Type the following commands as root: # cd /etc/yum.repos.d/ # wget http://public-yum.oracle.com/public-yum-ol6.repo # yum update The next examples shows the public-yum-ol6.repo file. Tip: You can enable any of the repositories in the public-yum-ol6.repo file by changing enabled=0 to enabled=1. # vi /etc/yum.repos.d/public-yum-ol6.repo [ol6_latest] name=Oracle Linux $releasever Latest ($basearch) baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/$basearch/ gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6 gpgcheck=1 enabled=1 [ol6_ga_base] name=Oracle Linux $releasever GA installation media copy ($basearch) baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/0/base/$basearch/ gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6 gpgcheck=1 enabled=0 [ol6_u1_base] name=Oracle Linux $releasever Update 1 installation media copy ($basearch) baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/1/base/$basearch/ gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6 gpgcheck=1 enabled=0 [ol6_u2_base] name=Oracle Linux $releasever Update 2 installation media copy ($basearch) baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/2/base/$basearch/ gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6 gpgcheck=1 enabled=0 [ol6_UEK_latest] name=Latest Unbreakable Enterprise Kernel for Oracle Linux $releasever ($basearch) baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/UEK/latest/$basearch/ gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6 gpgcheck=1 enabled=0
[ol6_UEK_base] name=Unbreakable Enterprise Kernel for Oracle Linux $releasever ($basearch) baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/UEK/base/$basearch/ gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6 gpgcheck=1 enabled=0
How to Uninstall or Remove Oracle Linux
There is not an option to “uninstall” Oracle Linux, although there are many ways to remove Oracle Linux from a system. The method you select to remove Oracle Linux or Red Hat Enterprise Linux from a system will depend on your organizations security requirements. For example, if the data on the hard drive needs to be securely deleted, formatting or re-partitioning the hard drive will not completely remove the data from the disks. To completely wipe Oracle Linux or Red Hat Enterprise Linux as well as the data from the hard disks, boot the system using data destruction application like Darik's Boot and Nuke (DBAN) and wipe all of the disks. If the data on the hard drive does not need to be securely deleted, you could a) delete all the files on the disks b) format or re-partition the hard drives c) uninstall the bootloader and d) install another operating system on top of the existing one. List 3 shows several of the options to remove Oracle Linux from a system.
Boot the system using data destruction application like Darik's Boot and Nuke (DBAN) and wipe all of the disks.
Delete all the files on the disks, i.e. type “rm -rf /” as root.
Format or delete the partitions.
Uninstall the bootloader.
Install another operating system on top of Oracle Linux or Red Hat Enterprise Linux.
Accelerate your Linux Deployments with Oracle Validated Configurations
LIVE WEBCAST: Top Tips to Get the Most Out of Your Linux Deployments
RFC5424 or cee-enhanced syslog?
MongoDB, BSON and templates...
rsyslog templates & json
rsyslog & elasticsearch: async replication and timeout
Oracle Linux and Oracle VM Hardware Certification Program
rsyslog & ElasticSearch: using dynamic index and type
new rsyslog v5-beta released
rsyslog group on Facebook
