Patch Reviews - SUN (MOSC)

MOSC Banner

patchpro: how to set a patching baseline

edited Jul 10, 2011 9:31PM in Patch Reviews - SUN (MOSC) 3 commentsAnswered
 I set up a patchpro local server (SUNWppror) and patchsvr enabled with default cache location at /var/sadm/spool/cache/patchsvr. Now all seemed working.
Whenever I ran smpatch analyze, the current3.zip file got updated (/var/sadm/spool/cache/Database, both on the patchpro server and smpatch client).

My understanding is that if I want to keep a patching baseline "June 1", I should keep this current3.zip file generated on 6/1 under /var/sadm/spool/patchsvr on the patchpro server.  However, both on the client and the server, the patch.list got updated to the current value as pulling directly from the server getupdate.oracle.com

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

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center