Going from 11.0 to 11.i

[Ron Kinner]

My HP admin guys tell me they are thinking about an upgrade from 11.0 to 11i on our production systems. They are wondering if anyone has any warnings about pitfalls or suggestions to make it easier or maybe flatout warnings not to do it? Is a fresh install better than an upgrade? Does the upgrade even work? etc.

Ron

[Patrick Wallek · Accepted solution]

The general consensus on the Forums is that a fresh install is always better than trying to go the upgrade path.

If you have your VG00 mirrored then you can break the mirrors, install 11i on one of the disks, and if something fails then you have the other half of the mirror to fall back on.

Make sure you have a good plan for the installation and have appropriate backups of everything before you start.

[A. Clay Stephenson]

Hi:

Actually, I've had very good success upgrading 11.0 to 11.11 (unlike 10.20 to 11.0). I've done a number of 11.0 to 11.11 upgrades and all worked without a problem. My main piece of advice is to make sure that you have plenty of free space in both / and /stand. If you built with the default sizes originally then your upgrade will probably fail. I always allocate extra space for both / and /stand for just this reason. The 11x 32-bit to 64-bit upgrade also works well.

Regardless of whether you choose a cold-install or upgrade, make sure that you do a make_tape_recovery so that you can revert to the old OS in case of trouble.



Regards, Clay

[Rainer von Bongartz]

Hi Ron,

I fully agree with Clay; upgrade from 11.0 to 11i is no problem if
you have enough space in /stand.

I came from 10.20 to 11.0 and then to 11.i and the /stand partition was to small to do this upgrade.

I actually re-installed 11.0 using IGNITE and changed the lvm layout and then did the upgrade to 11i.

Sounds complicated but was no problem at all.

Regards
Rainer

[Bill McNAMARA_1]

See the guidelines at:

http://www.hp.com/go/hpux11

you may have problems with some apps and need oracle patches etc..

Some apps may need recompilation, but generally you shouldn't fall into these categories.

Check the checklist on the above site HP-UX 11i migration guide.

Later,
Bill

[Bill McNAMARA_1]

soory the link has gone:

check it out here:
http://devrsrc.external.hp.com/STK/

Later,
Bill

[Ron Kinner]

All the advice looks pretty good. This should give my admin guys a warm fuzzy feeling about the upgrade.

I'll leave this open a little longer to see if anyone else has something then I'll do the points. I plan to be generous but I don't want to scare any one off by putting up the rabbit yet.

Ron

[Ron Kinner]

I guess that's all I'm going to get so I'll close this out now. It looks like it's not as bad as the 10.20 to 11.0 so my admin guys are starting to feel more confident. Thanks.

Ron

[Lisa Mauer]

Hi:
I will be updating from 11.0 to 11.i this Saturday and I noticed a lot of you saying you need enough space in the root volume and in /stand. The book states "4GB root vol min", it does not state 4GB free space. I currently have a 16.95 GB /dev/vg00 and have 3.66 GB Free. For /stand the guide states 100MB free, I increased this and now have 117 Mb free.
Did you run into anything where the document was not correct on the size limitations? or anything else?
Thanks!
Lisa

[Ron Kinner]

Can't help you, Lisa, since I'm not the one who really works on the things and as far as I know they haven't done it yet. Suggest you post your question as a new query. People tend to ignore the ones which already have rabbits.

Ron

[Lisa Mauer]

Hi Ron:
I know you put up the rabbitt,but I wanted you to know that I did the upgrade from 11.0 to 11i, not a cold install. I did not run into any problems, except a library issue after the fact, which you won't encounter unless you use Tuxedo and Cobol.. Anyway, I ordered these CD's and printed off the following docs:
Order appropriate CD???s
Hp-ux 11i application software part 5012-0081
Hp-ux 11i support plus part 5012-0050
Hp-ux 11i operating environment part B3920-14060
Hp-ux 11i instant information part 50726-10439
Information from the ???Read before installing or updating to HP-UX 11i??? March 2002 release notes. Document part 5185-4385

HP-UX 11i Installation and Update Guide from hp website. Part 5185-6593.

I also checked present patches with any existing 11i patches that I would need to lay down after the update. I followed the instructions to a "T" and had no problems with the update.

I know everywhere you look it says to "cold install" but I didn't due to the amount of apps I would need to reinstall and it went very well, just a few minor issues that were easily identifiable and fixable on our end.
Thanks!
Lisa

[Jitendra Maikoo]

Hi Lisa.

I am about to do an upgrade at a customer from 11.0 ti 11i. This customer is running both Cobol and Tuxedo. Can you tell me what the problem was with the library(ies) and what you did to fix the problem?

Thanks in advance for your assistance.

[Lisa Mauer]

Well, here goes, hopefully it makes sense to you, if not let me know.....

Executables built on hp-ux 11.0 using the Cobol compiler, Tuxedo middleware and other libraries run fine on hp-ux 11.0. The build environment is quite complex and includes reference to a large number of HP and 3rd party
libraries as well as some special build tools such as "buildserver".

When the programs are executed on HP-UX version 11i (aka 11.11), then the programs will not load and get errors that indicate that
some symbol expected to be found in a shared library cannot be found. In particular:

Getting unresolved symbol errors:

usr/lib/dld.sl: Unresolved symbol: t_strmsgsz (storage) from insurance1 (our app server)
usr/lib/dld.sl: Unresolved symbol: t_strqlen (storage) from insurance1 (our app server)
usr/lib/dld.sl: Unresolved symbol: t_strctlsz (storage) from chgentry (our app server)

These particular symbols are for internal use only and should never be referenced by user (or 3rd party) code. They were removed from libxti.2 at 11.11 but were in that library at 11.0.

It appears that the MicroFocus Cobol compiler has generated references to these (and many other) symbols in an intermediate file
it creates called ldtab.s (an assembly language module). The compiler creates this file based up the intermediate cobol files it has created as a part of the build process as well as the other object (and library)
files that is passed during the build process.
The -U option that is being passed to the Cobol compiler is forcing the compiler to pick up the internal "t_str*" items. We load our Cobol programs in at run-time so we need the -U option (dynamically load unresolved symbols). That is the default behavior of the buildserver command supplied by Tuxedo.

We have a site specific patch that HP had to code for us specifically to correct this problem. Things run smoothly now.

[Michael Elleby III_1]

My only suggestion, confirm that all of your non-hp apps are compatible with 11i..

Fresh install was the best way in my case..

I ran into an issue with an HP J6700 workstation and a scientific application called Ansys.. Kept running into an issue with shared libraries...

Wound up re-installing app as well as the OpenGL drivers...

It was just an annoyance... But just keep this in mind..

Mike E.

[Lisa Mauer]

I posted earlier about unresolved symbols after an 11.0 to 11i upgrade - there is finally a General Release Streams Patch available today from the Patch Website.... Patch PHNE_27703. If you are having unresolved symbols and using Cobol you may want to check this patch out... We installed and everything is working as it should....