topic corequisite errors in Operating System - HP-UX

corequisite errors

Donald Thaler — Tue, 01 Mar 2005 10:48:29 GMT

After downloading patches from the hp site using their patch download manager, i created a depot and looked at the log file swagent.log. This file showed a number of corequisite errors. Do I have to go back and download the patches that were identifed as missing or can I assume the hp patch download manager(not sure if thats the exact title of the process) would have included the required patches?

Re: corequisite errors

Pete Randall — Tue, 01 Mar 2005 10:53:44 GMT

Donald,

Generally the download manager will pick up all the co-requisite patches. Are you sure the errors are indicating that you're missing patches, or do the co-requisite errors refer to the software that the patch applies to? If that's the case, then this will be resolved when you actually apply the patch.

Pete

Re: corequisite errors

Donald Thaler — Tue, 01 Mar 2005 12:41:28 GMT

It says for example: 'the co-requisite phkl_29078 for phkl_29704 cannot be resolved'. I took this to mean the phkl_29078 wasn't found?

Re: corequisite errors

Pete Randall — Tue, 01 Mar 2005 12:46:59 GMT

That's correct. That leaves two possibilities. Either you already have it on your system or you're going to need to download it and install it together with the other one. Check your system first with "swlist -l product |grep -i 'ph'". That will give you a list of all your patches that you can compare against your co-requisites. Any that you don't already have installed on the system you will need to download from HP. Then swcopy them all into a depot that you can install all at once and your co-requisites should all be satisfied.

Pete

Re: corequisite errors

Donald Thaler — Thu, 03 Mar 2005 08:28:30 GMT

After going thru the iteration of finding the missing co-requisites and applying the patches I find the following:
(1) a co-requisite identified as unresolved, does in fact show up in the patch list (swlist -l patch)
(2) a co-requisite, phkl_25728 was superceeded by phkl_32061 and even though phkl_32061 was applied there is still a warning about phkl_25728 in the swagent.log