Oracle Solaris Installation, Booting and Patching (MOSC)

MOSC Banner

Best practices - pkg verify, SRU update

edited Mar 25, 2018 5:03AM in Oracle Solaris Installation, Booting and Patching (MOSC) 1 commentAnswered

I have some questions for my fellow SysAdmins out there. We are just beginning our first patch cycle after updating to Solaris 11.3 from Solaris 10. A little background on us:

We run Solaris 11.3 with OVM with Guest LDOMs running almost totally Solaris 11 zones, but a few Solaris 10 branded zones as well. We are running on T7-2 and T5-4 servers. One Control Domain and one Service Domain per hardware serving the Guest LDOMs. We were at SRU 16 and are updating to SRU 28.

In the first round of updates to the new SRU, we found that we had several packages that needed correction when we ran pkg verify after the update. We were just curious to see the state of things after the update. Most of what we found, were self-inflicted issues of file permissions, missing files for services we weren't using, etc. A few were kernel level and required a reboot to fix after using pkg fix to fix them.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center