Posts Tagged ‘feature’

Installing Oracle Enterprise Manager Cloud Control 12 on OEL 6.1

October 7th, 2011 2 comments

Few days ago Oracle announced the release of Oracle Enterprise Manager Cloud Control 12c. I tried to summarize most of the information in my post so I’ll not discuss any details here, but I’ll go only with few details regarding EM12c installation.

For the purpose I have setup a VMWare virtual machine with 2 CPUs, 4GB RAM and 32 GB HDD, one network interface. Installed Oracle Enterprise Linux 6.1 (64 bit) with following parameters:

  • Perform custom disk layout, I dedicated 4GB for swap and the rest for the root (/) file system and formatted it with ext4.
  • Perform default installation, needed packages will be installed later.
  • Set hostname, timezone and root password.
  • After installation disable the firewall and most of some of the services, like IPV6.

After installation the network adapter won’t be available that why you have to install several packages and then compile the VMWare tools. Insert the installation DVD/ISO and install the following packages:

mount /dev/cdrom /mnt
rpm -ivh -ivh gcc-4.4.5-6.el6.x86_64.rpm cloog-ppl-0.15.7-1.2.el6.x86_64.rpm cpp-4.4.5-6.el6.x86_64.rpm glibc-devel-2.12-1.25.el6.x86_64.rpm
glibc-headers-2.12-1.25.el6.x86_64.rpm kernel-uek-headers-2.6.32-100.34.1.el6uek.x86_64.rpm ppl-0.10.2-11.el6.x86_64.rpm
mpfr-2.4.1-6.el6.x86_64.rpm kernel-uek-devel-2.6.32-100.34.1.el6uek.x86_64.rpm
umount /dev/cdrom

Then disconnect the drive and from the console go to VM->Guest->Install/Upgrade VMWare Tools, then install the guest additions:

cp /mnt/VMwareTools-8.3.2-257589.tar.gz /tmp
umount /mnt
cd /tmp
tar xfz VMwareTools-8.3.2-257589.tar.gz
cd vmware-tools-distrib

At this point you should be able to configure the network interfaces.

Before starting the installation, download the packages from OTN and transfer them to the server. The installation consist of two zip packages, which are 5.5GB total, but this includes Oracle Weblogic Server 10.3.5, which is installed by default from the wizard.


Oracle Enterprise Manager Cloud Control 12c installation prerequisites

For the installation of Enterprise Manager Cloud Control I’m following the documentation:
Oracle® Enterprise Manager Cloud Control Basic Installation Guide 12c Release 1 (

1. From Oracle Database onwards, all versions are certified for Management Repository. The last two releases and do not need additional patches for it to be configured successfully. For the rest of the version additional patches are needed, refer to MOS for more information.

Except the support for Management Repository few more parameters are needed to be set. They could be set before or after the installation. For setting database initialization parameters refer to Table-6 or Table-7 from Appendix A at the documentation.

Once you are ready you could run the EM Prerequisite Kit which is run by the wizard during the installation.

2. According to the Oracle documentation for small environment, you need following servers parameters:
For the OMS: 2 CPUs, 4 GB RAM and 7 GB space excluding the installation which is 5.5 GB.
For the Management Repository: 2 CPUs, 2 GB RAM and 50 GB space.

3. Packages and kernel parameters required for OMS:
The following packages should be installer, either from ISO or from public yum server:

yum install make.x86_64 binutils.x86_64 libaio.x86_64 glibc-common.x86_64 libstdc++.x86_64 sysstat.x86_64 glibc-devel.i686 glibc-devel.x86_64

The shmmax kernel parameter should be set to value bigger than 4GB. In OEL 6.1 this parameter is far beyond and it’s set to 64GB. Its current value could be retrieved by following command:

cat /proc/sys/kernel/shmmax

4. Create group and user for the installation of Enterprise Manager 12c
The installation could not be done by root and oracle user has to be created. I’m using the same group id and user id as they would be created by oracle-validated package (which is not yet available for OEL 6.x).

groupadd -g 54321 oinstall
useradd -u 54321 -g oinstall -s /bin/bash -d /home/oracle -m oracle
passwd oracle

5. Configure limits.conf file:
The following two parameter has to be set in /etc/security/limits.conf file
oracle soft nofile 4096
oracle hard nofile 4096


Oracle Enterprise Manager Cloud Control 12c installation

Proceed with default installation and following the installation wizard.

If the wizard gives you warning at “Checking whether required GLIBC installed on system” although you have installed all the prerequisites you could ignore the warning. The installer is checking whether the package glibc-devel.i386 is installed, but you have already installed glibc-devel.i686.

Supply the repository details and please be sure to check whether the database control doesn’t exists. Otherwise you’ll get an error after supplying the database credentials to drop the database control of the repository database:
$ORACLE_HOME/bin/emca -deconfig dbcontrol db -repos drop -SYS_PWD <sys_password> -SYSMAN_PWD <sysman_password>

Once the installation is complete you’ll get a screen with installation summary and details how to access the console.

Then you could login and select default home page. This is how the console look like:


Meanwhile I just saw two useful installation guides:


Categories: linux, oracle Tags: , , ,

How to setup virtual iLO Remote Console

September 14th, 2011 No comments

In the new release of HP Integrity Virtual Machines 4.30, HP added a new feature which allows you to access the guest console by logging into a specific IP address. This feature is called virtual iLO Remote Console and should be configured with hpvmmodify.

Looking at the guest status (hpvmstatus -p) the following is observed:
[Remote Console]
Remote Console not configured

This is how to configure the IP address of the virtual iLO Remote Console:
root@vmhost1:/# hpvmmodify -p 1 -K -L

What the command does is configuring IP alias as could be seen in netstat:
lan0:110  1500  0                  0     0                  0     0

Running again hpvmstatus we see that the Remote Console is now configured:
[Remote Console]
Remote Console Ip Address:
Remote Console Net Mask:

Now about the users, by default the root user of the host is able login to all virtual consoles, although it’s not listed in following section:
[Authorized Administrators]
Oper Groups             :
Admin Groups            :
Oper Users              :
Admin Users             :

Let’s create a dedicated user for the first guest and then login:
root@vmhost1:/root# useradd -d /var/opt/hpvm/guests/vm01 -c ‘vm01 console’ adminvm1
root@vmhost1:/root# passwd adminvm1
root@vmhost1:/root# hpvmmodify -p 1 -u adminvm1:admin

Running status again we can see that the user is added to the administrators:
[Authorized Administrators]
Oper Groups             :
Admin Groups            :
Oper Users              :
Admin Users             : adminvm1

Let’s try now to login with our newly created user:
sve@angmar:~$ ssh adminvm1@


CO: Console
CM: Command Menu
CL: Console Log
SL: Show Event Logs
VM: Virtual Machine Menu
HE: Main Help Menu
X: Exit Connection

[vm01] vMP>

Voila, it’s working!


To enable access to the virtual iLO Remote Console through telnet (which by default is not supported) these two patches has to be applied on the host: PHCO_41595 and PHNE_41452. Two more considerations should be taken into consideration: The virtual iLO Remote Console’s SSH server host keys can change as it uses the host system’s SSH server host keys. If the guest is migrated to another system then these host keys will change. Another one is that guest administrator accounts are not migrated during Online VM Migration.


Categories: hp-ux Tags: , ,

HP EVA4400 support for big LUNs, no thanks

May 11th, 2011 No comments

I was part of project for upgrading an EVA4400 with FC drives, which currently has only FATA drives. The final task was to have equal count of FATA and FC drives in the system (8 cages). Because the FATA group was not fully allocated we’ve decided to create a FC group with some drives and using the snapclone functionality replicate the LUNs from FATA group to FC group. Later we would delete the FATA disk group, group more FC drives and create new FATA disk group with less drives.

Going with this setup I’ve decided to see for how long one LUN would be replicated and make the calculations. Then guess what, I’ve got a message saying that we cannot create snapclone of the disk because it’s too big, the LUN was just a little bigger than the 2TB. This EVA was upgraded with the latest firmware which gives you the ability to create LUNs up to 32TB. It was already written in the release notes, although with different words:

  • Virtual disk size. Create virtual disks (LUNs) that are larger than 2 TB (maximum of 32 TB). You can only create, present, and delete virtual disks that are 2 TB or greater. You cannot perform replication tasks or extend and shrink virtual disks that are 2 TB or greater.

So what happens if I have a database running on top of 5TB LUN and I want to create a snapshot, for reporting let’s say … it would be just impossible.

Vdisk size must be an integer between 1 and 2047 in order this functionallity to work, otherwise you’ll get the following error:

Operation failed!
The requested operation is not currently support by the installed firmware for luns 2TB in size.

I’m not completely sure if this issue exists in EVA6/8400.


Categories: storage Tags: