Oracle VM Manager installation problem
--------------------------------------

On servers where a high number of cpu threads are presented to the operating 
system, Oracle VM Manager may not install properly when selecting the "Install 
a new Oracle XE database on localhost" option.  We have seen this on newer 
hardware having higher core counts.

The problem occurs at install time when Oracle XE starts up because the default
configuration supplied is close to the memory limit for Oracle XE.  When the 
number of cpus detected gets above 16, the internal memory usage computed 
exceeds this memory limit, and Oracle XE fails to start and errors out with:

  ORA-44412: XE edition memory parameter invalid or not specified

If your Oracle VM Manager install appears to have not worked correctly,
you can check if this ORA-44412 error show up in the /var/log/ovm-manager/db.log
log file.

Follow these steps to work around this problem and install Oracle VM Manager:

1.  Mount the the Oracle VM Manager ISO image or media 
    (e.g. /mnt/<iso_mount_point>)

2.  Make a temporary working directory and copy the contents of the ISO:
      # mkdir <working_dir>
      # cp -pR /mnt/<iso_mount_point>/* <working_dir>/

3.  Download the installer patch for this issue and patch runInstaller.sh:
      # cd <working_dir>
      # wget http://oss.oracle.com/oraclevm/manager/patch/installer-bug9505763.patch
      # patch runInstaller.sh installer-bug9505763.patch

   The patch updates the following 2 file

     /usr/lib/oracle/xe/app/oracle/product/10.2.0/server/config/scripts/init.ora
     /usr/lib/oracle/xe/app/oracle/product/10.2.0/server/config/scripts/initXETemp.ora
    
    used by Oracle XE and adds the following line at the end:

      cpu_count=2 

    before configuring the Oracle XE database 

4.  Start the installation
      # sh ./runInstaller

5.  If you already attempted to install Oracle VM Manager and hit the above 
    error, you will need to select the install optioni (2) for the init.ora 
    update to take effect:

      "2. Remove the Oracle XE database and install a new one"


The next media update of Oracle VM Manager will correct this issue.