Sunday, April 29, 2007

Installing Oracle on CentOS 5.0 (x86_64)

During OS install both GNOME and KDE desktops were selected
as well as all components of all available groups except
"Virtualisation","Clustering","Cluster Storage"
KDE Session has been selected for system login.
Firewall and SELINUX have been disabled.

Hard disk partitions layout before installing Oracle.

CentOS 5.0 preinstall configuration.

File /etc/redhat-release has been edited to contain:-
to avoid installer's exit at startup.
Following lines added to the /etc/security/limits.conf file:-

* soft nproc 2047
* hard nproc 16384
* soft nofile 1024
* hard nofile 65536

Following line added to the /etc/pam.d/login file:-

session required /lib/security/

1. Check for required rpms to be installed.

2. Install rpms , which have not been attached to system during CentOS 5.0 installation, from DVD.

3.Tune /etc/sysctl.conf

Then run:-

# /sbin/sysctl -p

5. Run as root following script:-

groupadd oinstall
groupadd dba
groupadd oper
useradd -g oinstall -G dba oracle
passwd oracle
mkdir -p /u01/app/oracle/product/10.2.0/db_1
chown -R oracle.oinstall /u01
mkdir -p /u02/oradata
chown -R oracle.oinstall /u02

6. Configure oracle's .bash_profile.
Actually, Oracle recommends export only ORACLE_BASE and ORACLE_SID,
what makes installer able to generate ORACLE_HOME by itself
But,anyway you will have modify .bash_profile after installation.
Line: ulimit -u 16384 -n 65536 has not been included into .bash_profile
due to testing environment

7.Copy archive to disk and extract it:-

# xhost +
# su - oracle

Installation screenshots:-

Login to EM console:-

Saturday, April 21, 2007

Marvell Yukon Driver (SK-9E22) for Solaris (x64)
installation procedure in Solaris Express (SNV 59)

At mean time many people are experiencing problems with installing Solaris Express
on PC with boards based on Marvell Yukon Gigabit PCI-X Ethernet adapter.
Version for download from :

may be installed but actually doesn’t work. Workaround for this issue follows bellow

Run to find out vendor-id and device-id :

# prtconf –pv
device-id : 4364
vendor-id: 11ab

on your board

Modify script ./SKGEsolx/installation/postinstallation :-
Edit add_drv parameters list and put yours "pci11ab,4364" on the list.

# pkgadd -d . SKGEsolx

It will exit and report:
that original checksum of postinstallation script is XXXXX and differs from actual YYYYY.
Then edit ./SKGEsolx/pkgmap and put in postinstallation line instead of XXXXX value YYYYY.
Run again:-

# pkgadd -d . SKGEsolx

Script should complete OK and report , that skge0 was plumbed and brought up.

Proceed as was advised by John Brewer :-
Run as root:-

# sys-unconfig

This program will unconfigure your system. It will cause it
to revert to a "blank" system - it will not have a name or know
about other systems or networks.
This program will also halt the system.
Do you want to continue (y/n) ? y
Then the system will shutdown and when you reboot,
it asks all new server questions out of the box:

What your server name is ?
Are you on the network ?
Ask for DHCP or IP ?
What is your netmask ?
Do you have a defaultrouter ?
Root passwd?
Which interface ? ( skge0 will be there, it in the kernel now and have to be selected)

Finally it run the kdmconfig and tries to configure your X-display adapter and monitor size,mouse ps/2 USB or serial

When system reboots interface skge0 will be really up and running
Interface skge0 has been assigned new IP-address:

Saturday, April 14, 2007

Snoop -P -d skge0 statistics when pinging SNV 59 (64 bit) from remote Windows box

Would it be enough ?