Do I need PHKL_14280

[Steven Chen_1]

We are planning to upgrade K260 HPUX 10.20 by adding 512M memory and more hard disk in order to install Oracle V8.06 (we are having 512M memory and Oracle 7 now). I am not sure whether I need patch PHKL_14280, the kernel patch. I am wonderring if I would receive panic by increasing many kernel configuration parameters, such as memory parameters, etc..

I have been conservative about the patching -- not do it unless it is necessary.

Please advise.

[James R. Ferguson]

Steven:

The Support Plus (General Release) bundles are a good, safe bet. The June 2000 set is available and can be ordered from the ITRC.

...JRF...

[CHRIS_ANORUO]

You can use the latest patch bundle in HP-UX Support Plus for June 2000.
I have 1Gb of memory on a system, and glance does not report any memory bottlenecks. Look at the attached kernel parameters to assist you.

[Steven Chen_1]

I have downloaded this patch. Before patching it to system, I would like HP guru to confirm if I am OK to go forward. The followings are some lines of the patch text file:

------------------------------------------
Other Dependencies:
The system must have an initial memory module equal to or greater than 16 MBytes.

Supersedes: PHKL_6189 PHKL_7465 PHKL_7765 PHKL_13032
------------------------------------------

I don't know what "initial memory module" means, and I do find any supersedes patches in system.

Please help.

[James R. Ferguson]

Steven:

Especially since you say you generally don't patch your server, I strongly advise that you apply "coordinated" bundles as already suggested. These contain the patch dependencies needed and have been quality-assurance tested by HP. Get the Support Plus CDROM and use the General Release Patches bundle on it.

...JRF...

[Steven Chen_1]

James, How can I order the CD from ITRC?

[Kofi ARTHIABAH]

Ordering the CD:

Goto http://us-support2.external.hp.com/swd/bin/doc.pl/sid=cf2569e70d12c7240b

I think you may have to have a support contract with HP or at least a handle #

[James R. Ferguson]

Steven:

See:

http://us-support.external.hp.com/common/bin/doc.pl/screen=commonExtensionSW/sid=653e24630c0cf1cf8d

You will need your system handle.

...JRF...

[Steven Chen_1]

I do not see PHKL_14280 from the list of Support Plus from June 2000......

Can I just install the single patch then?

Chris Anoruo: do you have this patch installed before upgraded to 1G mem?

[Andy Monks]

Steven,

I remember this patch (it's an old friend). Basically if the size of your kernel (as returned by 'size /stand/vmunix' (or vmunix_test)) is over 13mb, then you'll need this patch.

Normally, this won't be the case unless your setting the message queue kernel parameters very high. This is normally only don't when running multiple instances of databases such as oracle etc (and normally, because people think 'oh for 1 instance I must set msg??? to X therefore as I have Y instances I must set msg??? to be X * Y) which isn't normally the case.

If you don't like installing patches and want to find out if you need it, just change the kernel parameters you want, build a new kernel (as vmunix_test) and then run size on it. As I said, over 13MB and you'll need the patch.

Btw, the patch (although kernel), doesn't actually touch the kernel. It updates the boot loaded in the LIF area, and therefore won't affect the stability of your machine.

[Steven Chen_1]

Andy, Thank you for your great explaination. My vmunix is now 8.9M only. Do I have to worry the expansion?

My msgmnb is 16384, and will no change it. strmsgsz will be from 0 to 65535 according to Chris's suggestion.

If that is not harmful, I want to do it. Should I?

Thank you all for the help.

[Andy Monks]

Steven,

That all looks fine. The str* parameter doesn't have enough of an effect to worry about. The message queue parameters (all msg*'s) are the problem ones, and therefore if you don't plan to change them that's fine.

After you've rebuilt the kernel, it will be worth either (a) booting from vmunix_test before moving it to vmunix or (b) just doing a 'size' on vmunix_test. 'b' is easier :-)