Solaris Patches: Difference between revisions
No edit summary |
No edit summary |
||
(6 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
'''NOTE''' after Oralce took Sun everything changed. Our support identifier is 17019053, goto http://www.oracle.com/us/sun/index.html and click on Support->My Oracle Support. | |||
Sometimes | |||
Run ''updatemanager'', subscribe and install patches (service plan # NK20211311). If machine does not have direct access to the web (for example clon20 on subnet 86), configure proxy from Update Manager's login page (proxy server: jprox.jlab.org, port:8080). More information about jlab proxy can be found at https://wiki.jlab.org/cc/external/wiki/index.php/Proxy_For_Special_Networks. Some patches will not be installed by ''updatemanager'', you will be advised to install them manually. Use command ''smpatch'', for example ''smpatch add -i 121431-44'', it will look for patches in ''/var/sadm/spool/'' directory where ''updatemanager'' places uninstalled patches. Unless you do manual installation, patch wil shows up in ''updatemanager'' window again and again. | |||
Sometimes manual intervention is required, read all messages carefully. | |||
Manual intervention 1: | Manual intervention 1: | ||
Line 18: | Line 21: | ||
patchsvr start | patchsvr start | ||
More information about these changes is available at > http://forums.sun.com/ann.jspa?annID=75 | More information about these changes is available at > http://forums.sun.com/ann.jspa?annID=75 | ||
'''NOTE''': old patches will be saved in ''/var/sadm/pkg'', sometimes it takes too much space. Goto that directory and type: ''rm -r */save/*'' (IS IT OK ???). |
Latest revision as of 13:27, 25 April 2011
NOTE after Oralce took Sun everything changed. Our support identifier is 17019053, goto http://www.oracle.com/us/sun/index.html and click on Support->My Oracle Support.
Run updatemanager, subscribe and install patches (service plan # NK20211311). If machine does not have direct access to the web (for example clon20 on subnet 86), configure proxy from Update Manager's login page (proxy server: jprox.jlab.org, port:8080). More information about jlab proxy can be found at https://wiki.jlab.org/cc/external/wiki/index.php/Proxy_For_Special_Networks. Some patches will not be installed by updatemanager, you will be advised to install them manually. Use command smpatch, for example smpatch add -i 121431-44, it will look for patches in /var/sadm/spool/ directory where updatemanager places uninstalled patches. Unless you do manual installation, patch wil shows up in updatemanager window again and again.
Sometimes manual intervention is required, read all messages carefully.
Manual intervention 1:
Date: 2009/02/03 Perform the following 3 steps in the given order. 1) Apply the latest smpatch certificate patches for Solaris 10: SPARC 121118-15 x86 121119-15 2) Update Manager: select the collection "Current Available Updates, after 01/2009" smpatch users: run "smpatch set patchpro.patchset=current2" 3) If you are using a Local Patch Server, make sure the patchsigning3 alias is added to the server configuration file: Set 'patchSigningCertAlias' property in the file '/var/patchsvr/lps/WEB-INF/applicationContext-lps.xml' to 'patchsigning:patchsigning2:patchsigning3' 4) Then restart the patchsvr with patchsvr stop patchsvr start More information about these changes is available at > http://forums.sun.com/ann.jspa?annID=75
NOTE: old patches will be saved in /var/sadm/pkg, sometimes it takes too much space. Goto that directory and type: rm -r */save/* (IS IT OK ???).