Solaris 8 Patch Manager Error

Anyone have any idea what this error is or how to resolve it? I'm trying to run smpatch on a Solaris 8 Sun Blade 100 box and getting the following error:
/usr/sadm/bin/smpatch download -i 112438-01
Requested patches:
112438-01
Downloading the requested patches
Error: PatchPro failed: StateMachine.start(): State machine failed.
State.getActionResult(): No valid result.
com.sun.patchpro.util.NoResultException: State.getActionResult(): No valid result.
at com.sun.patchpro.util.State.getActionResult(State.java:405)
at com.sun.patchpro.util.StateMachine.getActionResult(StateMachine.java:490)
at com.sun.patchpro.model.PatchProModel.getPatchAccumulator(PatchProModel.java:1041)
at com.sun.patchpro.cli.SMPatchServices.downloadPatches(SMPatchServices.java:1724)
at com.sun.patchpro.cli.SMPatchServices.main(SMPatchServices.java:709)

Hi,
I've just found the following in another thread:
The workaround for the bugID 6221832 (java being in another path than the default /usr/j2se/bin/ for Patch Manager 2.0 on Solaris 8) is to edit the pprosetup and pprosvc scripts
from /usr/sbin/pprosvc :
JAVACMD=/usr/j2se/bin/java
edit pprosetup and pprosvc scripts file and set JAVACMD locale variable to newly java installed path and launch smpatch get command again
Thank you. I've editted both scripts and changed the JAVACMD variable to be ${JAVA_HOME}/bin/java and now everything is working.
Thanks.

Similar Messages

Solaris Patch Manager gets status:302 behind Proxy

Hi Colleagues,
I am trying to get Solaris Patch Manager on my Solaris 8 up and running.
But if I say "smpatch analyze", the smpatch just reports a "Response code was 302" I think this means something like: "temporary moved".
I think my problem is, that the proxy doesn't follow the moved object.
Can anybody tell me where I can manualy download the detectors.jar and patchdb.zip?

Any news on this posting? I'm trying to do the same thing, as I dont want to use a caching proxy to download patches, I just want to use
a local source to perform analysis, downloads, and updates.
Cheers.

HTTP error while downloading solaris patches using wget

Hello,
I am getting a HTTP error while downloading solaris patches using wget.
'Downloading unsigned patch 113096-03.
--2010-06-18 03:51:15-- http://sunsolve.sun.com/pdownload.pl?target=113096-03&method=h
Resolving sunsolve.sun.com (sunsolve.sun.com)... 192.18.108.40
Connecting to sunsolve.sun.com (sunsolve.sun.com)|192.18.108.40|:80... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: http://sunsolve.sun.com/pdownload.do?target=113096-03&method=h [following]
--2010-06-18 03:51:15-- http://sunsolve.sun.com/pdownload.do?target=113096-03&method=h
Reusing existing connection to sunsolve.sun.com:80.
HTTP request sent, awaiting response... 401 Unauthorized
Unknown authentication scheme.
Authorization failed.
Problem downloading 113096-03.
What am i missing here... The credentials to login to sunsolve are correct and are updated in the downloadpatch.sh script.
Please assist
Thanks
Sunny

Try download via browser url:
[http://sunsolve.sun.com/pdownload.pl?target=113096-03&method=h]
You need a valid support contract not just Sunsolve account for many patches.

Difficulty in installing Patch manager 2 on Solaris 9

Hello,
I have a Solaris 9 machine on which I am trying to install Patch Manager
2. I have PatchPro 2.2 also installed on the same machine.
Since PatchManager2 requires some patches to be installed previously
like: 112945 117593 117595, I tried to install these. The last one
117595 if I understood correctly contains the patch manager itself. The
problem is that I installed 112945-40 which the patch manager doesn't
like and would instead require 112945-27. I tried patchrm 112945-40 and
patchrm -f 112945-40 but invain. I also tried patchadd 112945-27 and
patchadd -u 112945-27 but invain also.
# patchadd -u 112945-27
Checking installed patches...
Executing prepatch script...
Verifying sufficient filesystem capacity (dry run method)...
Patch 112945-27 failed to install due to a failure produced by pkgadd.
See /var/sadm/patch/112945-27/log for details
Patchadd is terminating.
The following is the log file:
Package not patched:
PKG=SUNWdclnt
Original package not installed.
Package not patched:
PKG=SUNWlvma
Original package not installed.
Package not patched:
PKG=SUNWmga
Original package not installed.
Package not patched:
PKG=SUNWpmgr
Original package not installed.
Package not patched:
PKG=SUNWwbdev
Original package not installed.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
PaTcH_MsG 1 Patch number 112945-27 is superceded by the already
applied 112945-40.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
WARNING: /etc/rc0.d/K36wbem <no longer a regular file>
WARNING: /etc/rc1.d/K36wbem <no longer a regular file>
WARNING: /etc/rc2.d/S90wbem <no longer a regular file>
WARNING: /etc/rcS.d/K36wbem <no longer a regular file>
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
I am really confused as what I need to do since even trying to install
117595-03 gives:
# patchadd 117595-03
Checking installed patches...
One or more patch packages included in
117595-03 are not installed on this system.
Patchadd is terminating.
Can anyone help me out please?
Regards,
Darren

Similar problems with patch manager...
Since PPro is being decommisioned and the suggestion is to go with PM 2, I went ahead and uninstalled PPro.
Now, for PM, the required patch is 112945-35 or higher, which I had on the system, excep that I have no smpatch command anywhere.. I backed out 112945-40 and reinstalled it, only to get the following:
Checking installed patches...
Executing prepatch script...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...
Patch number 112945-40 has been successfully installed.
See /var/sadm/patch/112945-40/log for details
Executing postpatch script...
cp: cannot access //usr/sadm/lib/wbem/providerutility.jar
cp: cannot access //usr/sadm/lib/wbem/sunwbem.jar
Unable to access "/usr/sadm/lib/wbem/providerutility.jar"
Usage:
smccompile -c <beanname>
smccompile -j tool|service [-n <altname>] <jarfile>
smccompile -j library [-n <altname>] ALL|ALLTOOL|ALLSERVICE|<tool or ser
vice bean to attach to> <jarfile>
Patch packages installed:
SUNWdclnt
SUNWlvma
SUNWmccom
SUNWwbapi
SUNWwbcor
SUNWwbmc
TIA...

Patch Manager for Solaris 9 9/05

I am trying to locate the Patch Manager download for Solaris 9 9/05 but all I have been able to locate on the downloads site is the version for Solaris 8. Does anyone have a link to the Solaris 9 version? Thanks.

Exactly, whith that configuration all works well (if my server is connected to Internet).
The problem is when I have another server, not connected to Internet, that requires new patches.
If I have good understood I can install patch manager(2.0) on that server, require patches to my local patch server and if the patches required aren't on the disk the local patch server requires them to Sun. During this request it seems that my local patch server doesn't connect trough the proxy (snoop doesn't report connections). even if the configuration is set. (I have tried a reboot too).

Luactivate error message re: Solaris Volume Manager

Is this something I need to be concerned about?
2009-04-02 16:40:18 # luactivate sol10_1008_stage2
ERROR: Solaris Volume Manager, (Root) file missing: </dev/md>.
ERROR: Solaris Volume Manager, (Root) file missing: </dev/md>.
Activating the current boot environment <sol10_1008_stage2> for next reboot.
The current boot environment <sol10_1008_stage2> has been activated for the next reboot.
2009-04-02 16:40:25 #Thanks,
Mark

Is this something I need to be concerned about?
2009-04-02 16:40:18 # luactivate sol10_1008_stage2
ERROR: Solaris Volume Manager, (Root) file missing: </dev/md>.
ERROR: Solaris Volume Manager, (Root) file missing: </dev/md>.
Activating the current boot environment <sol10_1008_stage2> for next reboot.
The current boot environment <sol10_1008_stage2> has been activated for the next reboot.
2009-04-02 16:40:25 #Thanks,
Mark

Solaris 10 - Tools for Patch Management Automation

Hi,
What are the best tools (both Sun and third party) for patch management automation for a company using Solaris 10 with zones?
What are the pros / cons and cost of these tools? Which ones are the most widely used / the most recommended?
Current objectives for automation are to eliminate the current manual processes and to reduce planned and unplanned downtime.
Thanks!

I don't think you would want to fully automate it. You need to be able to test patches first on a test system to ensure they don't conflict with established applications and cause problems. You wouldn't want to install patches that relate to applications you don't have, or for upgrades you do not have or don't plan on having. That said, the smpatch utility can connect with Sun Solve, find patches, and download them, even install them if desired. You could easily script the process and run via cron to make it automated. I just don't think that's a good idea without having someone make decisions on what SHOULD be patched at any given time. The SMC facility also has a function that mimics smpatch, although you could not automate that. Also, smpatch can only be run from the global zone, and patches will percolate down to non-global zones automatically - smpatch will not run in a non-global zone (unless there's been changes made recently that I'm not aware).
There's also the problem where some patches require reboot while others do not. If the patch kills the system, what mechanism do you have in place for someone to know what patch was applied that killed the system, if the process is automated and a number of patches were applied?

Adobe Reader and Acrobat Pro updates for 11.0.10 being pushed out through SolarWinds Patch Manager are not being recognized as applicable.

I am trying to update our Adobe Reader and Acrobat Pro to 11.0.10 using the default MSP packages with SolarWinds Patch Manager. All of the systems keep reporting as 'NOT APPLICABLE'. All of the workstations have Reader11.0.09, with about 10% still on 11.0.08 (due to the fact that the reader 11.0.09 package only patched about 2/3 of the systems). All systems that have Acrobat Pro are 11.0.09.
In SolarWinds I am using the "Adobe Systems, Inc. Packages" node.
Adobe Systems Acrobat 11 Catalog
Adobe Systems Reader 11 Catalog
and the SW Patch Manager downloads the msp's straight from Adobe.
I have checked the msp's manually and they will update at least back to 11.0.07 in Reader, and 11.0.0 in Acrobat Pro. (I had an old stand alone system that still had Reader 11.0.07, and I did a new install of Pro and went straight to update 11.0.10)
The SolarWinds Tech said, "Okay. That content is produced by Adobe. Any questions concerning applicability logic or diagnosing why a package reports as NotApplicable when that's not expected would need to be directed to Adobe, as they are solely responsible for that content and its behavior".
I am new to SolarWinds Patch Manager, and any help or advice would be greatly appreciated.

It sounds like you are attempting to use the SCUP catalogs outside of the MS solution. I can almost guarantee you that Adobe didn't test it if it's not referenced in the ETK: 11 SCCM-SCUP — Enterprise Administration Guide
That being said there "should" be logging available in any deployment solution. Since I am not familiar with Solar-Winds particular solution I can't say if it logs errors and how verbose those logs might be. If you have logs then post the output and the forum members "might" be able to assist you.

Solaris Volume Manager packages installation fails

During the OS installation phase while jumpstarting, the output is as follows for Solaris Volume Manager (see below).
To begin with, why are SUNWmdr and SUNWmdu packages trying to install? They are not mentioned in my Profile file, neither are they included in CORE OS. Is this a bug and has anyone found a fix to it?
/tmp/install2gaGwn/checkinstall4gaGwn: /tmp/sh68390: cannot create
pkgadd: ERROR: checkinstall script did not complete successfully
Installation of <SUNWmdr> failed.
No changes were made to the system.
/tmp/installHBaqyn/checkinstallJBaqyn: /tmp/sh68530: cannot create
pkgadd: ERROR: checkinstall script did not complete successfully
Installation of <SUNWmdu> failed.
No changes were made to the system.
3751 blocks
Thanks in advance,
David
p.s. This is happening while installing Sol9 sparc 04/2004 version (CORE) on Blade100, V480 and V240 machines.

<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>grestep wrote on Fri, 24 September 2004 14:34</b></td></tr><tr><td class="quote">
Unfortunately, this is a bug in the Sun jumpstart process.
You will have to install the same packages in a postinstall phase.
This bug has been there for years.
It is fixed in the latest Solaris 9 cdroms dated 09/04.
I know of no other fix except the latest cdroms.
It is also fixed in Solaris 10.
Solaris 8 even the most recent cdroms have the bug.
This bug only appears in a jumpstart. It works fine in a cdrom install. I haven't investigated why the jumpstart from a jumpstart server fails, but installing the package in a postinstall phase works.
I recommend that you download the latest Solaris 9 cdroms if it is Solaris 9 that is having the problem. For Solaris 8, postinstall phase is your only option.
I don't remember this bug in Solaris 7.
</td></tr></table>
Any idea how to fix this ? Ive jumped a lot of machines using this jumpstart server using JET, always using the SDS product from JET, it always worked well, until I tried to jump this v210 recently acquired and firmware updated.
I got those errors and have no clue how to fix this .. :
SDS: Installing sds....
SDS: Installing SUNWmdr from: /a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
/a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc/SUNWmdr/inst all/checkinstall: /t
mp/sh39790: cannot create
pkgadd: ERROR: checkinstall script did not complete successfully
Installation of <SUNWmdr> failed.
No changes were made to the system.
SDS: SUNWmdr installation complete
SDS: Installing SUNWmdu from: /a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
/a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc/SUNWmdu/inst all/checkinstall: /t
mp/sh40210: cannot create
pkgadd: ERROR: checkinstall script did not complete successfully
Installation of <SUNWmdu> failed.
No changes were made to the system.
SDS: SUNWmdu installation complete
SDS: Installing SUNWmdx from: /a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
/a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc/SUNWmdx/inst all/checkinstall: /t
mp/sh40640: cannot create
pkgadd: ERROR: checkinstall script did not complete successfully
Installation of <SUNWmdx> failed.
No changes were made to the system.
SDS: SUNWmdx installation complete
SDS: Installing SUNWmdnr from: /a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
/a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc/SUNWmdnr/ins tall/checkinstall: /
tmp/sh41060: cannot create
pkgadd: ERROR: checkinstall script did not complete successfully
Installation of <SUNWmdnr> failed.
No changes were made to the system.
SDS: SUNWmdnr installation complete
SDS: Installing SUNWmdnu from: /a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
/a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc/SUNWmdnu/ins tall/checkinstall: /
tmp/sh41460: cannot create
pkgadd: ERROR: checkinstall script did not complete successfully
Installation of <SUNWmdnu> failed.
No changes were made to the system.
SDS: SUNWmdnu installation complete
SDS: Apply patch 108693-25
Using : SunOS Release 5.8 Version Generic_117350-16 64-bit
All other packages installed without problem
Any insights ?

Deployment Manager Error with Oracle Weblogic Server 10.3.1

I have installed Identity Manager 9.1.0.2 (patch upgraded from 9.1.0.1) on OEL 5.3 64bit and Weblogic 10.3.1
Database:Oracle 11gR2 (remote machine).
**I am aware that IM 9.1.0.2 is not certified on Weblogic 10.3.1 (it is only certified on 10.3),
The installation was successful and OIManager is up and running. Able to create Users, Resources etc. as well.
As part of configuring OIM Connectors tried to Import .xml file using Import option from Deployment Management section as below and the following error was displayed.
"Either your session timed out or you are trying to access a page without logging in".
Did all workarounds like enabling java, changing browsers, restarting machine etc as per the below discussion but in vain.
Deployment Manager Error with Oracle Weblogic Server
Can any one suggest any workaround or solution for this problem.
Or atleast can any one confirm there is no Identity manager available on this date which is compatible with 10.3.1? and cannot be continued further.
Thanks in Advance
Sudheer
Edited by: SudheerPrabhala on Oct 20, 2009 1:26 AM

You are facing this issue because you're using a non certified combination.
Other folks who tried to use OIM in 10.3.1 ended up in the same problem you're facing.

Sun update manager with patch manager

I need to use both products since I have systems running Solaris 10, 9 and 8. Is there a way to get them to work together?
Ideally, I would like to have 1 system talk to SUN to manage the application and downloads. I would want the system to distribute the patches to all the other systems.

Yes, this is possible. We would recommend setting up Sun Update Manager on Solaris 10 as your patch proxy (with a connection to Sun). Both Update Manager on Solaris 10 and Patch Manager on Solaris 8 and 9 can then be configured as clients.

What is Sun's answer about PCA patch manager free tool ?

Hi all,
this post aims on echoing customers'feedback.
from customers'experience it seems that smpatch from patch manager tool is suffering of a lack of reliability.
One of them moved to a new freeware called PCA-Patch Check Advanced
http://www.par.univie.ac.at/solaris/pca/
From PCA Web Site we can read:
Sun has offered various tools in the past to analyze Sun/Solaris systems for patches which are installed or missing, e.g. PatchDiag, PatchCheck, PatchPro, smpatch (see the Sun Patch Portal for details). Some of them are not actively maintained, some are huge and opaque, some don't run on older Solaris releases or stripped-down machines. None of them really made me happy. Based on PatchCheck source I implemented PCA, which gets rid of the disadvantages of Sun's own tools.
I would like to know what is Sun's position and could it be possible to integrate such a tool ?
Thanks.
Malek.

- Sun is always interested in customer feedback, and is interested in
the concerns expressed here.I'd also very muck like Sun to be interested in fixing the customers problems, which has not been done in my cases. No solution or explanation has been given to my many cases opened on smpatch, and this, even though in some cases, patches were made (months later): I was never told about them. Which makes me wonder about the point of having paid support contracts in the first place.
But since UM was developed by interns, it's no wonder there's trouble maintaining it (how do I know? I've been an intern doing Java development, and I made the exact same beginner's mistakes, not knowing to handle exceptions, leaving debug output on stdout, being unable to make proper localisation).
It's obviously not the work of experienced Java programmers. Hard to trust it...
- We do understand that opaque is bad, but one of Sun's goals is to
provide complex analysis beyond matching patches with installed
packages. This analysis and its support processes will necessarily
be somewhat opaque.What analysis are you talking about? smpatch is not even able to tell me that security fixes are available for NSS, which has been part of Solaris for years. PCA does.
And what about Studio? Why can't smpatch tell me there are patches for that, too? And why aren't free patches, that are neither recommended nor security (such as the man patches) shown by smpatch when running without a contract?
- We are interested in the concerns surrounding stripped-dow
systems, and are considering a "light" version of our tools that would
support minimal systems. However at this time there are no plans to
release a light version.And what about systems without a network?
And what about not forcing me to read and agreeing to a, abusive license agreement, which can't even be printed, nor shown full screen (5 lines at a time!)?
And, please, can you explain me why I should agree to respect Reuters so-called intellectual property? What does it have to do to with keeping my systems up to date reliably and easily? Is it a competition between Sun and Microsoft to put the most ludicrous licenses on line?
Anyway, I'm sure Solaris 11 will introduce some new bloated offspring of the PatchProManagerUpdateConnection family, so I'm not holding my breath. Rather than repeat this experience again and again, I'll stick with PCA.
Laurent

Install patch 8333939, error occurs

Dear All,
My customer trying to apply patch 8333939, but error occurs.
Referred
Note 1224313.1: Getting Started with Oracle E-Business Suite Plug-in, Release 4.0 (Doc ID 1224313.1)
when running in the Section 5: Preparing Oracle Enterprise Manager 11g Grid Control
and installing patch 8333939, error occurs:
"the staging area needs oracle universal installer version 11.1.0.7.0 or late"
EBS version: 11.5.10.2
Platform: Linux x86-64
I have following questions:
1. Is this patch need to install on DB or APP?
2. Customer has two OUI home, does he need to upgrade OUI home to 11.1.0.7.0 or later? How? Is there a patch number or something?
[applprod3@ITEEBSTE oui]$ cat oraparam.ini |grep OUI_VERSION
OUI_VERSION=10.1.0.6.0
[applprod3@ITEEBSTE oui]$ pwd
/EBSTEST/PROD3/apps/tech_st/10.1.3/oui
[applprod3@ITEEBSTE oui]$ cat oraparam.ini |grep OUI_VERSION
OUI_VERSION=10.1.0.6.0
[applprod3@ITEEBSTE oui]$ pwd
/EBSTEST/PROD3/apps/tech_st/10.1.2/oui
Thanks,
Jackie

Hussein,
I have a question.
Is this means customer need to execute following steps first
3. Install Oracle Enterprise Manager 11g Grid Control (11.1.0.1.0)
3.1. Install OEM on the OMS server
3.2. Install OEM Agents on the Targets (where EBS is installed)
3.2.1. Targets having the same OS version as the OMS server
3.2.2. Targets having different OS versions as compared to the OMS server
Then, patch 8333939 can be applied successfully?
Because refer to
http://docs.oracle.com/cd/E17559_01/em.111/e18708/T506934T511454.htm
Section "Running Oracle Universal Installer"
It says:
Stop all the Management Services before installing the pack to a Management Service. Management Services will be restarted automatically after the pack has been installed.
Stop the OMS.
$PROMPT> $ORACLE_HOME/bin/emctl stop oms
Note: If your EM Repository (EM Database) is on the same machine, it must be left running. Only OMS and Agent services need to be taken down.
Set the environment variable ORACLE_HOME to ORACLE_HOME of Management Service 11.1.0.1 as shown here:
export ORACLE_HOME=/d1/oracle/em11g/oms11g
Then unzip this patch and install it. Am I right?
My customer's purpose is to install EM on R12, does
Note 1224313.1: Getting Started with Oracle E-Business Suite Plug-in, Release 4.0 (Doc ID 1224313.1)
is the correct note?
Thanks,
Jackie
Edited by: Jackie Han on Sep 3, 2012 8:28 PM

Patch install error

Patch install error
As part of the Upgrading developer 6i with E-Business 11i
I was asked to apply patch 4586086
The following command failed
make -f cus_forms60w.mk libso_install
make: *** No rule to make target `libso_install'. Stop.
I was asked to
To Check X version
===================
Linux:
rpm -qa|grep openmotif
openmotif-2.1.30-4_MLI 7.1
openmotif-2.1.30-11
openmotif-devel-2.1.30-11
I am running SUSE Linux
Is it important to have only the above.....
Could I not have the latest version of openmotif ?
Please guide me

Hi
This is my current situation.
I installed the patches recommended by you.
Currently the output of rpm -qa|grep motif is
oracle@test-app:/apps11510/dev/devora/8.0.6/bin> rpm -qa|grep motif
openmotif-libs-2.2.2-519.4
openmotif-2.2.2-519.4
openmotif21-libs-2.1.30MLI4-119.4
I am applying patches as per document 125767.1
I think I must have made some mistake in the sequence of steps or some other error....
First let me give some details about my environment
We have two servers
a) test-db
This runs Oracle database and
Reports Server and
Concurrent Manager and
Reports review agent
b) test-app
This runs Forms Metric Server and
Forms Server Listener and
Forms Metric client and
Report Review agent and
HTTP Web server and
Discoverer Server and
Fulfillment server
I am confident that I have correctly followed all steps 1 - 5 of the
document 125767.1
Now step 6
I have installed all the following patches on ONLY test-app
6194129 and
7343387 and
7156414 and
6125732 and
6857221 and
3830807 and
4586086 ( This is where it failed)
Question - Should I have installed these patches on both servers test-app and test-db
Question - should all the patches mentioned in the document be applied
(6194129,7343387,7156414,6125732,6857221,3830807,4586086)
as part of step 6 and step 7 and then move to step 8 ?

What is the best approach for patch management

Hi,
I'm new about patch management. I would like to ask you how manage patch on few Solaris 10 servers using command line.
I would like to know:
1. Using only command line how to download latest patches
2. There are some dependencies how to check this and install only those patches which meets dependecy requirements?
3. Is there possiblity to atomate this?
4. Is it possible to have one patch server and others servers will download and install this patches?
5. What if some patches are not installed?
6. How to find out which patches are necessary and which patches don't have to be installed? Or maybe or patches to be installed?
7. Could you please describe your approach for managing patches? Or maybe you can recommend some books/web page/articles that can help me to understand patch management.
Thanks in advance,
Daniel

smpatch is the command line tool to manage solaris patching. first you need to register yours system - this can be done using sconadm, detailed here:
http://sunsolve.sun.com/search/document.do?assetkey=1-9-82688-1
smpatch analyze will list all required patches and resolve dependencies. smpatch download will download all the required patches, and smpatch update will apply them. You can set up a Local Patch Server to download patches, then your clients will download the patches they require from it. This is detailed in chapter 6 of the update connection admin guide

Solaris 8 Patch Manager Error

Similar Messages

Maybe you are looking for