08-23-2013
8 More Discussions You Might Find Interesting
1. Solaris
Hello,
As explained, I've encountered an issue while installing Solaris 10 SPARC Recommended Patch Cluster (2009.10.23).
Actually, patch no 120011-14 stops with the following error:
ERROR: attribute verification of </var/run/.patchSafeMode/root/usr/bin/passwd> failed
file type <f>... (6 Replies)
Discussion started by: a.mauger
6 Replies
2. Solaris
Hi there,
Apologies if this question has been asked and answered already but I've not been able to find the thread.
Question: Is it possible to apply the Solaris 10 Recommended Patch Cluster to a whole root (non-global) zone locally? I.E. apply the patch cluster from the non-global in... (3 Replies)
Discussion started by: nm146332
3 Replies
3. Solaris
Hi Admins,
I came across an error while installing patch cluster on solaris.
# ./installcluster --s10cluster
ERROR: Another instance of an install script is already running for target
boot
environment '/'.
I did killed the related processes. Now there is no any process running from ps... (1 Reply)
Discussion started by: snchaudhari2
1 Replies
4. Solaris
I'm trying to setup our jumpstart server to automatically apply the latest patch cluster during installs, but I'm running into an issue. Every time Jumpstart runs it has this error. Obviously it's processing the patch_order file, so I'm not sure what I'm missing.
... (0 Replies)
Discussion started by: christr
0 Replies
5. Solaris
I have a question regarding installing recommended patch clusters via ZFS snapshots. Someone wrote a pretty good blog about it here:
Initial Program Load: Live Upgrade to install the recommended patch cluster on a ZFS snapshot
The person's article is similar to what I've done in the past. ... (0 Replies)
Discussion started by: christr
0 Replies
6. Solaris
Dear All,
We are facing some performance problems in our oracle DB qerries and reports recently. We applied Solaris 10 recommended patchset on april 24th. Our monthly report generation acitivity ran 3 days i.e may 11,12,13 and application team complained of degraded performance. I can see that... (9 Replies)
Discussion started by: abhi_8029
9 Replies
7. Solaris
Hello
I recently downloaded and installed the latest patchset for Solaris 10 (update 5) running on SPARC.
Actually I am new to Solaris (I come from Red Hat) and the security department asked me to update the system for security fixes.
I logged in to Oracle support and used the recommended patch... (3 Replies)
Discussion started by: abohmeed
3 Replies
8. Solaris
Hi Guys,
I'm looking to download the latest patche cluster, we install them on a monthly basis.
I have not seen anything released in the last couple months since January.
Did I miss an announcement?
Are they going to start releasing quarterly?
Or is it just so happening there are no... (2 Replies)
Discussion started by: BG_JrAdmin
2 Replies
LEARN ABOUT DEBIAN
shape_patch
SHAPE_PATCH(1) General Commands Manual SHAPE_PATCH(1)
NAME
shape_patch - shapeTools RMS generate patch file
SYNOPSIS
shape patch OLDRELEASE=<name1> NEWRELEASE=<name2> [PATCHFILE=<filename>]
DESCRIPTION
Shape patch generates a patch file for updating $(OLDRELEASE) to $(NEWRELEASE). Both releases are identified by release names associated
with the macros OLD-/NEWRELEASE on the command line. Valid release names are those generated by any of the shape_RMS (pre-)release building
procedures (see shape_releas(1)). Performing 'vl -all' with the release identification file as argument usually gives a good overview of
existing release names. Patch generation happens recursively over all subsystems being part of the current node. Hence, triggering shape
patch from the top node of the central source repository creates a patch file for the whole system.
The output of shape patch is stored in a file named <name1>+2+<name2>.pat. When the PATCHFILE macro is set on the command line, $(PATCH-
FILE) is taken as output file name instead. Defining PATCHFILE=- on the command line causes the patch to be written to standard output.
Note: For patches invoking multiple subsystems, $(PATCHFILE) should be set to an absolute pathname. If not, the patch generation procedure
will leave an equally named patch file for each visited subsystem.
The patch is constructed using the vdiff(1) command and can be applied to any installation of $(OLDRELEASE) by invoking patch(1).
INCONVENIENCES
On System V machines, the generated patch file name will almost certainly exceed the 14 characters filename length limit.
SEE ALSO
shape_releas(1), vdiff(1), patch(1)
FILES
<name1>+2+<name2>.pat
1.6.119 SHAPE_PATCH(1)