hp uggrade

[John_1017]

Hi, This is concerning cold-installation from 11.00 to 11i, I was wondering what type of error messages will pop-up in sw logs and their importance. Also, when would you recommend an ignite backup? Immediately after the installation OR after installing all other software and patches? Or both before and after installing software? Finally, what system parameters or configurations need changes after install?

[A. Clay Stephenson]

You should see very few error messages of any kind during install (assuming conditions like big enough filesystems are met; network parameters are set; etc.).

I would wait until you have your system up, with all patches and HP software installed and tuned reasonably well before doing a make_tape_recovery.

At a minimum, reduce the dbc_max_pct from 50% to a more reasonable value (10-15%) and min_dbc_pct to 3-5% (or my preference - set bufpages to a non-zero value and thus create a static buffer cache). Generally, the default maxXsiz values are too small. Stack should be increased to about 32MB, maxdsiz should be 1GB or so, maxtsiz should be 256-512MB. These are the 32-bit versions the 64-bit versions should be larger although even in 64-bit land 32MB for maxssiz should be adequate for well-written code.

[Pete Randall]

John,

There should be very few, if any error messages. As far as Ignite backups, I would recommend one before you begin and after installing applications and patches. Afterwards, you will need to tune the kernel and customize things like /etc/passwd, nsswitch.conf, resolv.conf, etc. I'm attaching a script that I use to copy over all of our customized files when I build a new server. Some of these are exclusive to us and you won't have them, but it provides a good starting point to think about.


Pete

[Bharat Katkar]

Hi,
I would prefer following way:

0. Make note of changed kernel parameters, software installed, licenses applied, mapfile of all VG's except VG00.
1. Shutdown the server.
2.Add fresh internal disk to the systems.
3. Make newly added disk as primary boot path (current disk should be alternate) and continue installing 11i on the newly installed disk.
4. Installed necessary software, upodate kernel parameters, apply licenses, create VG structre and import mapfiles etc.
5. Try rebooting the server an dcheck whether everything goes fine with the lates version 11i, in case it doesn't work make the old disk as primary path and try trouble shoot the problem.

Hope that helps.
Regards,

[Geoff Wild]

Ignite: Prior to upgrade, then after.

Cold Install - change dbc_max_pct so that it works out to between 400 and 750 MB of avail of ram (11iv2 - you can do this on the fly - no reboot!)

If you have Oracle - your dba will have to re-link the Oracle binaries...

Rgds...Geoff

[Steven E. Protter]

Before you start.

make_tape_recovery Ignite backup. The cold install may fail and you may need to go back.

Cold install will not preserve anything or applications on the system.

I do not believe you will have any significant error messages that will come up.

Put the Hardware eneablement pack and Bundle and latest quartery release right after install before you do anything else or install any applications.

SEP