Cannot add a bunch of patches to a Solaris 2.6 box 3

[jerler]

Hello all,

Allow me to preface this post with a plea to excuse any glaringly obvious things I may have missed; I'm a Solaris newbie!

Anyway, my question: I have an Ultra 10 that I am trying to install all the "Recommended 2.6" patches on. However, it errors out on 10 or 11 of them, and they all seem to fail with the following:

"One or more patch packages included in xxxxxx-xx are not installed on this system".

I'm not sure how to interpret this error. Does it mean that there are some prerequisite patches that need to be installed ahead of time? If this is the case, I cannot find anything else in the error log that indicates what other patches are required. Even more confusing, the error seems to actually say that something it is trying to install isn't there in the first place. Well of course it's not! that's why I'm trying to install it!!

Help! Any light you all could shed would be GREATLY appreciated...

-Jason

 

[harris79]

The error means that the package that the patch fixes is not installed.

For example - There are packages for foreign character sets, if you haven installed these, then you can't patch them.

 

[harris79]

I should have added that you can see what each patch does by reading the README in the patch subdirectory or the README for the patch set. Look for either the package name (SUNWxxxxx) or a keyword (CDE, kernel)

You can then check for the accociated package on your system using

pkginfo | grep SUNWxxxxx
or
pkginfo | grep keyword.

 

[jerler]

harris79,

Thanks for your response! This sort of makes sense, since one of the pacthes that didn't go was a fix for a directory that doesn't even exist on the machine! It may also be useful to note that I received return codes 8 and 2 on the patches that failed. I'm still trying to figure out excactly what THAT means...

-Jason

 

[cfsalmeida]

0 No error
1 Usage error
2 Attempt to apply a patch that's already been applied
3 Effective UID is not root
4 Attempt to save original files failed
5 pkgadd failed
6 Patch is obsoleted
7 Invalid package directory
8 Attempting to patch a package that is not installed
9 Cannot access /usr/sbin/pkgadd (client problem)
10 Package validation errors
11 Error adding patch to root template
12 Patch script terminated due to signal
13 Symbolic link included in patch
14 NOT USED
15 The prepatch script had a return code other than 0.
16 The postpatch script had a return code other than 0.
17 Mismatch of the -d option between a previous patch install and the current one.
18 Not enough space in the file systems that are targets of the patch.
19 $SOFTINFO/INST_RELEASE file not found
20 A direct instance patch was required but not found
21 The required patches have not been installed on the manager
22 A progressive instance patch was required but not found
23 A restricted patch is already applied to the package
24 An incompatible patch is applied
25 A required patch is not applied
26 The user specified backout data can't be found
27 The relative directory supplied can't be found
28 A pkginfo file is corrupt or missing
29 Bad patch ID format
30 Dryrun failure(s)
31 Path given for -C option is invalid
32 Must be running Solaris 2.6 or greater
33 Bad formatted patch file or patch file not found

Regards,

Carlos Almeida,

 

[jerler]

Carlos,

Many thanks! This at least gives me a better idea of what's going on! May I ask where you found this? Is it availble somewhere on Sun's website? Or perhaps in a README somewhere?

Thanks,

-Jason

 

[harris79]

Thanks Carlos, I never knew some of them.

Steve

 

[cfsalmeida]

"patchadd" is the shell script used by "installcluster", if you edit "/usr/sbin/patchadd" information about error codes is in top of it.

Regards,

Carlos Almeida,

 

[DavidPhillips]

Cool, Thanks again for the info.

 

[MadBiker]

I am also getting the same error and I do indeed have those packages installed and still not luck

any ideas? How do I set the program to return the errorlevel?

Thanks!
James

 

[KenCunningham]

The error level should be returned in your interactive session and to a log file. Otherwise, just redirect the output to a file of your choosing:

patchadd <patch> 2>&1 /<yourfilename>

HTH.