Moved to Australia

I finally have made the jump over to Australia. After a somewhat bumpy first week (oh man - what a jet-lag) I started to settle down.

On my project I will do a lot of stuff with Coherence, WebLogic Portal, the OSB, Grid Control and a RAC database.

I'm looking forward to do this. This is part of re-inventing myself, while being in a nice place.

I will also try to blog some of my experiences in
http://yetanotheraustraliablog.blogspot.com/

Oracle VM memory issue

After some first baby steps with Oracle VM I wanted to push this thing a little bit further. So my idea was to have more than a couple of VM's running simultaneously.
The Oracle VM told me however that I had not enough memory to do this.
So I was sitting in front of my dedicated laptop and told the screen that there should be 4 GB inside. The laptop however had one of his funny days and told me (using free and top) that really nothing more than 572 MB would be inside the machine.

Hmm - when a machine tells me something I am the first to listen. So I shutdown everything, got my screwdriver, opened the memory compartment and had a look. Indeed 1 bank of 2GB. I didn't check the second bank as this is hidden underneath the keyboard. Closing the machine and powering it up, I prepared myself for another round of telling it that it should recognize a little bit more than 572 MB.

I examined the dmesg and still it told me that there was only 572 MB inside.

Now imagine, you have just seen 2 GB inside (and hope that 3 or 4 are in there) while the Oracle VM keeps telling me that only a very limited part of that memory was there.

So friends and neighbors, there are two possibilities:
a) The memory was KAPUT
b) Something prevents Linux to see/use it all.

As I could not prove or examine option a) I had a look at option b).

A long long time ago I was pretty good with low level Linux (baking my own kernels and so on). And then I remembered that with Xen it is possible to fool around with the memory during boot time.

Checking the menu.lst of the GRUB I found the following:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda2
# initrd /initrd-version.img
#boot=/dev/sda
# Detect64 claims this is 64 bit box
default=2
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Oracle VM Server-ovs (xen-3.4.0 2.6.18-128.2.1.4.9.el5ovs)
root (hd0,0)
kernel /xen-32bit.gz dom0_mem=572M
module /vmlinuz-2.6.18-128.2.1.4.9.el5xen ro root=UUID=ad545ccc-b2bb-450b-a048-a58b22c51cc4
module /initrd-2.6.18-128.2.1.4.9.el5xen.img
title Oracle VM Server-ovs serial console (xen-3.4.0 2.6.18-128.2.1.4.9.el5ovs)
root (hd0,0)
kernel /xen-32bit.gz console=com1,vga com1=57600,8n1 dom0_mem=572M
...

Gotcha!

dom0_mem=572M

So I found the reason for the lack of memory (an amnesic laptop ;-)

Off we go - with a modified menu.lst:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda2
# initrd /initrd-version.img
#boot=/dev/sda
# Detect64 claims this is 64 bit box
default=2
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Oracle VM Server-ovs (xen-3.4.0 2.6.18-128.2.1.4.9.el5ovs)
root (hd0,0)
kernel /xen-32bit.gz dom0_mem=572M
module /vmlinuz-2.6.18-128.2.1.4.9.el5xen ro root=UUID=ad545ccc-b2bb-450b-a048-a58b22c51cc4
module /initrd-2.6.18-128.2.1.4.9.el5xen.img
title Andreas VM Server-ovs (xen-3.4.0 2.6.18-128.2.1.4.9.el5ovs)
root (hd0,0)
kernel /xen-32bit.gz dom0_mem=2048M
module /vmlinuz-2.6.18-128.2.1.4.9.el5xen ro root=UUID=ad545ccc-b2bb-450b-a048-a58b22c51cc4
module /initrd-2.6.18-128.2.1.4.9.el5xen.img
title Oracle VM Server-ovs serial console (xen-3.4.0 2.6.18-128.2.1.4.9.el5ovs)
root (hd0,0)
kernel /xen-32bit.gz console=com1,vga com1=57600,8n1 dom0_mem=572M
...

I added the "Andreas Server-ovs" stanza, to prevent me from a re-installation if something would not work.

So after a reboot my laptop tells me that it has the large amount I was hoping for.

As this part of the memory is just the amount Xen is using there is some more in it.

Checking what really is in there:

[root@ovm ~]# xm info | grep memory
total_memory : 3447
free_memory : 1363
node_to_memory : node0:1363

This looks better.
Well i keep it like this for a while and play with my 2GB for now.

Startup problems of OSB on OEL

Another thing I came across when dealing with the OSB was that the Workshop throw an error and didn't start at all. When you end up with a large dialog box showing a list of startup parameters (which all originate from the workshop.ini file) have a look at this site: http://wiki.oracle.com/page/How+to+get+Oracle+Workshop+for+Weblogic+10GR3+working+in+Linux?t=anon

Problem when starting the Eclipse Workshop for OSB

During the startup of the Eclipse Workshop in my OSB environment I encountered the following error:
“requested array is larger than heap”

The solution (from the OTN forums) is to delete the publish*.dat from the following directory:

FMW_HOME/user_projects/workspaces/YOUR_WORKSPACE/.metadata/.plugins/org.eclipse.wst.server.core/publish/

Leightweight is not always good

I am busy installing the latest version of the Oracle Enterprise Manager. Obviously I need a database for this.
In order to protect my resources in the Oracle VM image that use I switched off all extra Database options. Among others the Partitioning option is offered. Well - during the installation of the OEM I found out the hard way that the Partitioning option is required for the database.
I know that the OEM creates a lot of partitions - which will then get emptied during the data consolidation process. I happened to forget this.

The funny thing is that the OEM installer checks this and comes back with a warning box, stating:
Using the Partitoning option is strongly recommended. Being a wise guy I tried to ignore this. But when Oracle says that they STRONGLY RECOMMEND something they mean it. So I am deinstalling and reinstalling the database software as I write this ;-)

Starting an Oracle VM image from the commandline

Just for your convenience:

When you start an Oracle VM image from the commandline with

xm create -c ./vm.cfg

you will see that the boot process continues until the login is displayed:

EXT3-fs: mounted filesystem with ordered data mode.
type=1403 audit(1272761495.554:2): policy loaded auid=4294967295 ses=4294967295

Enterprise Linux Enterprise Linux Server release 5.4 (Carthage)
Kernel 2.6.18-164.0.0.0.1.el5xen on an i686

soa.mydomain.local login:

In order to get back to your commandline type CTRL-] and you will get back the control.