Andreas' Adventures

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/

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

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

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/

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 ;-)

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.