Solaris Patches - Revision history

129.57.76.91 at 18:27, 25 April 2011

2011-04-25T18:27:37Z

← Older revision		Revision as of 14:27, 25 April 2011
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~~.		'''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.

129.57.76.91 at 18:27, 25 April 2011

2011-04-25T18:27:20Z

← Older revision		Revision as of 14:27, 25 April 2011
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 ~~service~~->my oracle support.		'''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.

129.57.76.91 at 18:26, 25 April 2011

2011-04-25T18:26:48Z

← Older revision		Revision as of 14:26, 25 April 2011
Line 1:		Line 1:
	'''NOTE''' after Oralce took Sun everything changed. Our support identifier is 17019053, goto www.sun.~~com~~ and click on service->my oracle support.		'''NOTE''' after Oralce took Sun everything changed. Our support identifier is 17019053, goto http://www.oracle.com/us/sun/index.html and click on service->my oracle support.

129.57.76.91 at 18:25, 25 April 2011

2011-04-25T18:25:59Z

← Older revision		Revision as of 14:25, 25 April 2011
Line 1:		Line 1:
			'''NOTE''' after Oralce took Sun everything changed. Our support identifier is 17019053, goto www.sun.com and click on service->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.		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.

129.57.76.91 at 21:41, 12 February 2010

2010-02-12T21:41:47Z

← Older revision		Revision as of 17:41, 12 February 2010
Line 18:		Line 18:
	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 ???).

129.57.76.146 at 18:59, 10 February 2010

2010-02-10T18:59:02Z

← Older revision		Revision as of 14:59, 10 February 2010
Line 1:		Line 1:
	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-33'', 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.		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.		Sometimes manual intervention is required, read all messages carefully.

Boiarino at 13:20, 24 March 2009

2009-03-24T13:20:58Z

← Older revision		Revision as of 09:20, 24 March 2009
Line 1:		Line 1:
	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-33'', 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.		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-33'', 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 ~~manial~~ intervention is required, read all messages carefully.		Sometimes manual intervention is required, read all messages carefully.

	Manual intervention 1:		Manual intervention 1:

129.57.76.91 at 15:47, 6 February 2009

2009-02-06T15:47:02Z

← Older revision		Revision as of 11:47, 6 February 2009
Line 1:		Line 1:

	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-33'', 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.		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-33'', 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.

Line 7:		Line 6:

	Date: 2009/02/03 Perform the following 3 steps in the given order.		Date: 2009/02/03 Perform the following 3 steps in the given order.
	>		1) Apply the latest smpatch certificate patches for Solaris 10:
	> 1) Apply the latest smpatch certificate patches		SPARC 121118-15
	~~> S10:~~ SPARC 121118-15; x86 121119-15		x86 121119-15
	~~> S9: SPARC 140476-01; x86 140477-01~~		2) Update Manager: select the collection "Current Available Updates, after 01/2009"
	~~> S8: SPARC 140475-01~~		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:
	> 2) Update Manager: select the collection "Current Available Updates, after 01/2009"		Set 'patchSigningCertAlias' property in the file '/var/patchsvr/lps/WEB-INF/applicationContext-lps.xml' to
	> smpatch users: run "smpatch set patchpro.patchset=current2"		'patchsigning:patchsigning2:patchsigning3'
	>		4) Then restart the patchsvr with
	> 3)If you are using a Local Patch Server, make sure the patchsigning3 alias is added to the server configuration file.		patchsvr stop
	~~Alter the~~ patchSigningCertAlias property in the file /var/patchsvr/lps/WEB-INF/applicationContext-lps.xml ~~file~~ to		patchsvr start
	> patchsigning:patchsigning2:patchsigning3		More information about these changes is available at > http://forums.sun.com/ann.jspa?annID=75
	> 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

129.57.76.91 at 15:17, 6 February 2009

2009-02-06T15:17:28Z

← Older revision		Revision as of 11:17, 6 February 2009
Line 1:		Line 1:
	Use ''updatemanager'', ~~read messages carefully~~. Sometimes ~~manual~~ intervention is required.
			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-33'', 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 manial intervention is required, read all messages carefully.

	Manual intervention 1:		Manual intervention 1:

129.57.76.91 at 15:14, 6 February 2009

2009-02-06T15:14:25Z

New page

Use ''updatemanager'', read messages carefully. Sometimes manual intervention is required.

Manual intervention 1:

Date: 2009/02/03 Perform the following 3 steps in the given order.
>
> 1) Apply the latest smpatch certificate patches
> S10: SPARC 121118-15; x86 121119-15
> S9: SPARC 140476-01; x86 140477-01
> S8: SPARC 140475-01
>
> 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.
Alter the patchSigningCertAlias property in the file /var/patchsvr/lps/WEB-INF/applicationContext-lps.xml file to
> patchsigning:patchsigning2:patchsigning3
> 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