xen discuss - Dec 2007 - Tuning F7 (CentOS 5) DomU (64 bit) for Oracle 11g (10GR2) install

Yesterday night I've tuned F7 DomU for Oracle 11g install
successfully installed Oracle , made checks for EM Console
and shutdown DomU.

Today morning :-
# xm start FDR7PVM
# xm console FDR7PVM

Fedora release 7 (Moonshine)
Kernel 2.6.20-2925.9.fc7xen on an x86_64

Server11G login: root
Password: 

Module is unknown

Fedora release 7 (Moonshine)
Kernel 2.6.20-2925.9.fc7xen on an x86_64

Server11G login: 

However, ssh login from SNV76 Dom0 side works fine.
It appears possible to bring up database:-
$ dbstart $ORACLE_HOME
 and start dbconsole
$ emctl start dbconsole

But attempt to “ https://IP-DomU:1158/em/” by Solaris FireFox 
(or remote Windows Explorer)
causes F7 DomU to hang. Any DomU screen appears to be frozen.

Next:-

# xm shutdown FDR7PVM

I also found out that console login failure with message "Module is
unknown"
is caused just by tuning F7 DomU for Oracle 11g as well Oracle 10gR2
installations.
No need to install oracle itself. Just install required rpms and tune
/etc/sysctl.conf.
It will immediately cause failure to login from console to F7 DomU.
Yesterday I proceeded with Oracle installation right after tuning F7 DomU
environment without   reboot. It properly brought up Oracle Instance completely
functional ... until first F7 DomU reboot or shutdown.
Some time ago I tried to work with CentOS 5 DomU in reagrd of tuning for
Oracle 11g or 10g installation . It behaved exactly the same way
 
 
This message posted from opensolaris.org
_______________________________________________
xen-discuss mailing list
xen-discuss@opensolaris.org

Even if I selected all available packages   during F7 DomU installation at SNV76
Dom0.To succeed with Oracle 11g install on F7 following rpms should be
downloaded from the Net and installed on the system:-

rpm -Uvh  libaio-0.3.106-3.2.x86_64.rpm \
    libaio-devel-0.3.106-3.2.x86_64.rpm
rpm -Uvh  sysstat-7.0.4-3.fc7.x86_64.rpm
rpm -Uvh  unixODBC-devel-2.2.12-2.fc7.x86_64.rpm

I believe that this action is a route cause of console login failure and
abnormal
F7 domU behavior  afterwards.In case with CentOS 5 DomU “libaio” rpms would be
already installed from ISO image.
 
 
This message posted from opensolaris.org
_______________________________________________
xen-discuss mailing list
xen-discuss@opensolaris.org

Managing CentOS 5 DomU at CentOS 5 Dom0 (on top of embedded Xen 3.0.3)
it’s possible to install any additional required by business needs RPMs on DomU
without any negative consequences for  DomU functionality.
 
 
This message posted from opensolaris.org
_______________________________________________
xen-discuss mailing list
xen-discuss@opensolaris.org

I was wrong. Following action required by Oracle 11g , 10g manuals:-
********************************************************************************************
Add the following line to the /etc/pam.d/login file, if it does not already
exist:
session    required     /lib/security/pam_limits.so
session    required     pam_limits.so
*********************************************************************************************
causes F7 DomU console login failure at nex reboot.
If mentiioned lines get removed from /etc/pam.d/login 
console login reverts back to normal shape.
 
 
This message posted from opensolaris.org

I''ve got Oracle 11g on F7 DomU at SNV76 Dom0 (64 bit)
running stable with untouched /etc/pam.d/login  file,
what is acceptable in testing and development environment.
 
 
This message posted from opensolaris.org