MegaCli and Solaris

Some SUN servers like (Blade X6270 ) uses lsi raid controller to manage disks.

The problem here will come if we have  faulty disk and wants to replace ,DO NOT THINK IT IS STRAIGHT FORWARD AT ALL.

the raid controller will not map disk directly to server ,disk must be in raid-level so the Solaris can detect it and reuse it.

First of all download MegaCli tool from this link

extract the megacli to a folder ,reach that folder and follow this sequence:

1- list all disks ,get the new inserted disk details ( Enlosure ID and Slot Number )

#./MegaCli -PDList -aAll

Adapter #0
………………………output omitted

Enclosure Device ID: 32
Slot Number:  1

2- use Enclosure ID ,Slot number to build raid0 on newly  inserted disk

#./MegaCli -CfgLdAdd -r0 [32:1] -a0

3- do rescan new attached devices

# devfsadm -Cv

you should be able to see the new disk now.

Hint: normally all disks attached to lsi raid will be as raid0 unless another plan was implemented.

Unplugging and plugging back a disk , doesn’t make the controller rebuild the array with that disk,the disk maybe marked as bad and its service LED is on.
Here is what to do:

1- list all disks ,and get EnlosureID and Slot for the Disk with [Foreign State:Foreign ]

# ./MegaCli -PDlist -a0

Hint: I assumed the raid controller is (a0) ,to get list of all available raid controllers (megacli -AdpAllInfo -aAll)

2. mark this disk as good (to switch off service LED )

# ./MegaCli -PDMakeGood -PhysDrv[32:3] -a0

3. scan and assure there is a foreign configuration on the raid controller

# ./MegaCli -CfgForeign -Scan -a0

4. clear this foreign configuration from array

# ./MegaCli -CfgForeign -Clear -a0

Sources :

1- Oracle Doc ID 1671764.1


Aside | Posted on by | Tagged , , , , , , , | Leave a comment

Solaris 11.2 Webcast


Today ,there was a big event talking about Solaris 11.2 release

Important Points covered ;
Solaris Life cycle Management
Virtualization and SDN ( Software Driven network)
Solaris Open Stack
Plz don’t miss watching these videos from the following url

To Download Software and Learn Solaris 11.2


Posted in Uncategorized | 1 Comment

sending email from solaris using mailx

Always use these options with (mailx) command

mailx -v -s “Subject_of_email”

then press Enter key on keyboard,then start typing email data,then on a separate line just put (.) and press enter.

if you want to send an  email to mthe format is :


mailx -v -s “Solarisway” (press Enter )

Hi John,(press Enter )

Hope your doing well.(press Enter )

regards.(press Enter )

. (press Enter )



Normally,mailx uses configuration file (/etc/mail/ for sending emails,this file is read-only file,so u have to force saving after you finish configuration (:wq!) when using vi editor.


Inside that file there is a parameter named (D{MTAHost}),so depending on the value of this parameter,the mailx command will behave as following :

1-if it looks  like D{MTAHost}[]   , mailx will use IP of (mailhost) which is configured in /etc/hosts

2- if D{MTAHost} has another IP rather than,then mailx will use this IP as Relay to send its outgoing emails.

Posted in Uncategorized | Tagged , , , , , , , , , , , , , , | Leave a comment

Add SRU to Solaris 11 Repository

How to Update an Oracle Solaris 11.1 Package Repository.

to update your local repositroy directly with new SRU ,you shold do these steps

1-mount the new SRU image from EIS-DVD,or download from oracle

2-sync the directory of local repository with contents from SRU image.

3-Rebuild the search indexes for the repository

4-(option) if you publish your repository over http (means u deployed package server),restart the service

here is commands used to do this :

1. Mount the ISO image as a filesystem.

# mount -F hsfs /root/sru_13   /mnt

2. Import the SRU packages to your existing Oracle Solaris 11.1 repository.

# rsync -aP /mnt/repo/ /rpool/Sol11.1/repo

3. Rebuild the search indexes for the repository.

# pkgrepo rebuild -s /rpool/Sol11.1/repo

4. If the repository is managed by pkgserv, restart the appropriate

# svcadm restart svc:/application/pkg/server:default

So, now you updated your local repository with new patches/updates,your installed packages is not updated yet ,first you can compare between packages installed on your system and the one inside repository

#pkg list -u   —> to list available updates for current installed packages

# pkg update —–> to update all installed packages

or if needed ,you can update a specific package by :

#pkg update pkg_name

Posted in repository, Solaris 11 | Tagged , , , , , , , , | Leave a comment

OVM step by Step

OVM ( Oracle Virtual Machine) environment installation/configuration step by step guide.

In This document,i tried to make it simple as much as I can.

Since,I suffered to understand OVM environment during installation/configuration.

Anyway,to get OVM (Oracle Virtual Machines) ready you need these software:

1- OVM server 3.2.7 ,its size 250 MB

2- OVM Manager 3.2.6 ,its size 2.5 GB.

3- OVM Manager patch 3.2.7,after you install OVM Manager 3.2.6 ,you will apply patch to upgrade it to 3.2.7.

4- Oracle Linux 6.4,its size 3.5 GB,you need it as OVM manager will be installed on Linux.

5- a small package(tightvnc) to be installed on linux after you finish ovm manager installation, link is

Use the following link to  download OVM step by step Guide:

Posted in OVM | Tagged , , , , , , , , , , , , , , , | 1 Comment

Prepare Oracle Linux or Redhat Linux for Oacle Software

Oracle released an amazing rpm for Linux 5.x and 6.x ,that will do all pre installation tasks to be done on Oracle Linux as well as Redhat Linux.

for both linux(5.x and 6.x) first build your local repository using linux installation image ( )

for Oracle Linux 5.x :

first get full package name by this command :
# yum list all | grep -i oracle-validated 
output: oracle-validated.x86_64                  1.1.0-17.el5                  installed
# yum install  oracle-validated.x86_64

for Oracle Linux 6.x :

first get full package name by this command :
# yum list all | grep -i oracle-rdbms-server 
then use yum install pkg_name_you_get from_previous_command


Posted in Uncategorized | Tagged , , , , , , , , , , , | Leave a comment

ERP GO-Live Consideration

The old saying, “nothing happens until the deadline gets close” certainly applies to ERP (Enterprise Resource Planning) projects. In the case of ERP, the deadline is called “Go-Live” meaning the new system is turned on and the old system turned off or at least idled. Unfortunately, many Go-Live dates become known as the Day of Disaster. Follow these guidelines to make Go-Live survivable.

Training Early and Training Late

Demand your consultants helping with your ERP project have completely separate teams for training and implementation. Letting the team leads “manage” training as one of their bullet points guarantees problems on Go-Live.


Related: The Most Important Thing About ERP


Training for end user leaders begins with the first demonstration of the first potential ERP vendor. You can never have too much end user feedback during an ERP project, because those end users, or the end user representative, know they are the ones who will have to live with the system on a daily basis.


The majority of the users should be trained the month before Go-Live. Too much training too soon just means the refresher memos at Go-Live will be replaced by full training sessions. When the end users know they’ll be using the new ERP system in a matter of weeks, more attention will be paid during training.


End user team leaders, however, should be trained constantly during the customization process. Every workflow change, each new screen item, and each new report should be taught to the team leaders, so they can give their feedback and verify the final training classes will be up to date.


Incorporate Changes from User Acceptance Testing

UAT, or User Acceptance Testing, is a critical step in all ERP projects. Too often, however, UAT becomes just a check-list item to be rushed through. When this happens, and UAT feedback is not incorporated into the ERP customization process, Go-Live bombs because the user’s contributions were ignored.


This UAT dismissal causes two major problems. First, the users expect one thing and get another, slowing their work. Second, they then realize their comments and demands for workflow improvements were ignored, and they can imagine the system will only get worse going forward. Complaints will fly up the management chain, meetings will be called, and real work will grind to a halt.


Go-Live is not the time for surprises. Aggravating entire user departments leads to far more extra work than making the changes they asked for during UAT.


Three is the Magic Number

Every project needs deadlines, and ERP projects are certainly no exception. Don’t tell anyone, but expect to have two false Go-Live dates before you finally commit to the complete cutover.


No ERP project can Go-Live on the first date set, because that date was set at the beginning of the project and based on the vendor’s promises of how smoothly everything will run. In reality, your project will take, typically, twice as long, and cost twice, as much as first estimated.


Go-Live project date Number One will come and go. The second Go-Live date will be about 50 percent later than the first date. So if your project was supposed to take a year and end in October, the next Go-Live will be about April the next year.


From Inside CRM: CRM And The Long-Cycle Sell


The third Go-Live date, following our example above, will be either September or November. This will be the real deadline, and Go-Live will function more or less correctly. Why? Because your company will have had the right amount of time to make the customizations and the Go-Live process will have been partially tested twice.


A third Go-Live date is a successful Go-Live date


About the Author

James Gaskin writes books, articles, and jokes about technology, and consults for those who don’t read his books and articles. Email him at


Original :


Posted in General Knowledge | Tagged , , , , , , , | Leave a comment