A new release of PCA has just been published. Here's a list of new features and
changes:
* Ignore missing showrev/patchadd on Solaris 11
* Remove useless attempt to guess file type with zip files from Oracle
* Documentation: add information about minimal option
* Whitelist: add 115336,
Dennis Clarke wrote:
I guess really the question is, can MOS and Oracle be trusted to provide a
kernel patch that won't make things far worse?
I can't answer that, but I agree in that the bug descriptions have become pretty
useless recently (since Oracle took over?). Like revision 04 of
laur...@elanor.org wrote:
However, I believe we are hitting a fundamental flaw of the Oracle patch
download system here:
If you go back to my previous email with the debug run, the request for
the patch is secure: https://updates.oracle.com/all_unsigned/121118-19.zip
If the patch were
laur...@elanor.org wrote:
It's at 20111018-01. I just installed all this, on a Linux box, all clean.
That's strange, indeed. To start with, it works fine for me both on Solaris and
Linux. First thing I spotted is that you seem to get a different file:
Connecting to proxy|0.1.2.3|:8080...
laur...@elanor.org wrote:
Under what conditions is PCA downloading .jar instead of .zip? Because
in that case, it's still PCA which asked for it. Maybe you could remove
it or deprecate it, disabled unless it is explicitly asked for?
I just checked - PCA will only look for JAR files in local
BABAULT.Daniel wrote:
I can't find what patch cause this. Did somebody have an idea ?
I think that /usr/sbin/prtconf is the culprit, maybe that helps to isolate the
patch.
But you're not alone with that issue, as it seems:
Fred wrote:
It used to be that when I used the --askauth option, pca would merrily
download patches from the pca proxy's cache until it found a new one, in
which case the proxy would fail (the same unauthorized error) and pca
client would go right to Oracle. This is where my support creds were
Don,
So, let me ask this question a slightly different way; what information do you
feel you are not getting from patchdiag.xref today?
Your list is pretty complete, as far as I'm concerned (no wonder, we've talked
about that before :) ). But the question remains:
Would Oracle mind, if we
Fred wrote:
--2011-11-02 09:37:43-- http://pca-proxy/cgi-bin/pca-proxy.cgi?115337-05
Resolving proxy-host... xxx.xxx.xxx.xxx
Connecting to proxy-host|xxx.xxx.xxx.xxx|:18082... connected.
Proxy request sent, awaiting response... 401 Unauthorized
Authorization failed.
Failed (Error 401:
James Adams wrote:
Same problem, same patches. The patches aren't yet available for
download yet.
I had the same problem. As usual, waiting for 24 hours helped, and all patches
are available for download now. Seems as if now and then new patches get stuck
in the publication process
Hi Don and all,
In the READMEs of the new patches 124630-60 and 119534-29 a note has been added:
NOTE: The list of 'patches required with this patch' (above) has been
modified from the list specified at patch creation time. The reason for
the modification is that one or more of the
Thomas Gouverneur wrote:
Isn't it because the 124628-02 is obsolete that it's not inside the
patchdiag.xref ?
The problematic patch is 126677-02 - it's listed as required for 119534-29 and
124630-60 in patchdiag.xref, but there is no information about any revision of
126677 itself.
Martin.
Thomas Gouverneur wrote:
Something that could be integrated into PCA, related to my other post
on the mailling, is the new way of getting patches metadata (with XML
API). This way, when you have a broken dep' like this, you could check
the proper metadata of the missing patch directly @ Oracle
Solaris 9 will transition to Vintage Support at the end of October. This means
that any Solaris 9 patches (or patch revisions) released from Nov 1st onwards
will require Vintage support level. Details on Gerry Haskins' blog:
Lisa,
Others have already described various options you have. As for my 2 cent: Take a
look at the PCA documentation, especially the parts about setting up a local
patch server (in your situation, a PCA local caching proxy might suit best, and
there are detailed step-by-step instructions in
Hi Jonathan,
Thanks for the background information and the confirmation that --minimal
works for you. I decided to make it official now, and have added documentation
to the development release of PCA now.
Without gushing too much we have found PCA too useful to not use. It
simplifies and
Dennis Clarke wrote:
Anyone know why these patches are special and secret ? Is this just more
stupidity on the part of Oracle ?
Most probably you do not have the appropriate support entitlement for these
patches. Unlike Solaris patches, all fo them are for unbundled software and the
Asif Iqbal wrote:
Thanks for the patch. I actually would prefer a variable instead of
hard coding wesunsolve.net, like the the original $o{patchurl} or
$o{ohost}
The problem is that you probably want different formats when using pca
--readme (in a terminal pure text is preferred) and in the
Thomas Gouverneur wrote:
You can try the simpler patch of the world, attached to this email
against current stable version of PCA. It will add a link for each
patch inside the HTML report to wesunsolve.net website.
Thanks to Asif and Thomas for the idea and the patch!
I've integrated the
Don O'Malley wrote:
In the case of EMC, the date I heard for a hotfix for EMC PowerPath was the 7th
October. To get further information you need to follow up with the ISV in question.
I just read this in one of the Oracle forums:
I confirm that the updated version of PowerPath
Hi Daniel,
i'd welcome if pca could log own activities as well as patchadd
activities in better way then current syslog possibility ..
Making PCA log more shouldn't be a problem, but what exactly would be useful? I
wouldn't want to direct the complete debug output to syslog, so I need some
Craig S. Bell wrote:
Martin, regarding pca-dev and multi-element xrefurl: Should pca -x
always try the proxy when I include proxy-specific options such as
-F and/or --nocache?
No, it will always try the sources strictly in the order as specified in
xrefurl. It will use the first xref it
Don O'Malley wrote:
That said, something has happened to trigger 119081-25 being marked as obsolete
(I suspect this is a result of an internal process).
In the current patchdiag.xref (Oct/02/11) the state of 119081-25 has been
reverted to active (not obsolete) again. Same for the other 7
In today's patchdiag.xref, patch 119081-25 is suddenly marked as Obsolete. nut
there is no sign by which patch it would have been obsoleted: usually, the
synopsis (last column in xref file) contains a note Obsoleted by xx-xx.
As there are two patches which require 119081-25 (namely
Craig S. Bell wrote:
Bonus: I like how it will never try MoS without a keyword -- that's
exactly what I want for my clients.
I can take user=dontask out of my client config file, since it will
not unintentionally try MoS now.
Ah, thanks for the reminder! The dontask keyword is not needed
Craig S. Bell wrote:
Can I somehow configure pca to look on the share first, then query the
proxy server if any of the desired patches are not present?
The new development version of PCA (20110928-01) supports multiple URLs and path
names with the patchurl and the xrefurl option. Example:
Craig S. Bell wrote:
Can I somehow configure pca to look on the share first, then query the
proxy server if any of the desired patches are not present? I should say
that I want patchdir to be somewhere different altogether, so I can stage
patches locally on each client.
I guess I know what
Tate, Robert B wrote:
Thank you! I missed that. I would argue that is should ignore it as requested
and then show that the others were ignored also when they were done. Or a
separate option to Force the ignore anyway. I see the reason for not doing it
that way also, but the only problem with
Tate, Robert B wrote:
I don't know why there is a whitelist at all or why it overrides the wishes of
the user.
I will look to see if I can find an older version that works. I hadn't thought
of that.
It's not the whitelist which causes this, so an older version of PCA won't help
here.
First of all, if you use /usr/sfw/bin/wget with PCA (as recommended), this
doesn't matter at all to you.
For all of those who compile their own versions of wget or use e.g. the
pre-compiled binary from sunfreeware, you should be aware that version 1.13.3
contains a stupid which makes PCA fail
dpecka wrote:
i'm suggesting to think about these fields:
- patch bundle
- readme md5sum
- zipped patch md5sum
I'll add these from my wishlist:
- patch properties (rebootafter, etc.)
- patch size (zipped/unzipped)
- a new flag always install first for the patch utilities patches etc.
-
Thomas,
I wonder if this feature could be integrated into We Sun Solve website,
as from the patchdiag.xref archive, I could generate a patchdiag.xref with
latest revision as base and then add older revision of patches into it by
looking at
patchdiag.xref archive.
Yes, you're right.
Hi Daniel,
i'm missing in pca few less important features like for example
possibility to list released patches by date ..
You're right, there is currently no way to show the release date of a patch with
PCA, only the age.
I've fixed that in the current development release (20110905-01).
Hi Lisa,
sorry for the late reply, I was out of town. It seems as if it's a problem with
the wget binary (/usr/local/bin/wget) on your system:
/usr/local/bin/wget --progress=dot:binary
https://getupdates.oracle.com/all_unsigned/119254-81.zip;
--ca-certificate=./pca.perl -O
Coskun, Aydin wrote:
Can anyone please help me? I get this error :
Checking files for safe patch installation
failed file verification:
ERROR: /usr/sbin/flarcreate
modtime 04/27/10 11:35:04 AM expected 11/18/10 10:48:50 AM actual
file size 32320 expected 32420 actual
file cksum
A new release of PCA has just been published. Here's a list of new features and
changes:
* Always set proxy both for HTTP and HTTPS when wgetproxy is set
* Recognize new obscure way of Oracle server saying login failed
* New option to unzip patches (--unzip)
* Remove useless attempt to
Due to some recent backend changes in the Oracle patch download service there
might be issues with failing patch downloads with PCA in certain situations:
If you are using a firewall which restricts outgoing access, it might be
necessary to add a few extra rules for the new additional content
Michele Vecchiato wrote:
Martin, as always you are right ... :-)
Tell that to my wife :)
Thanks for the confirmation, and also thanks to Tim Frost, who had experienced
the same problem and provided analysis plus a patch for PCA off-list.
Martin.
Don O'Malley wrote:
There is load balancing performed on the backend to share the load between
limelight and Akamai.
To cover all scenario's the following should be added to your firewall:
A really long list. Lucky me that I don't have to deal with rules for outgoing
connections on our
There are two different problems here:
Your user/password was wrong. It seems as if Oracle now uses a very obscure and
non-standard way to tell us that. Instead of an HTTP ERROR 401 it returns a
text/html file with 2009 bytes, which points at the problem in the HTML content
(p
James,
My request is:
Put the MD5 value as a text string somewhere on the page.
Ok, I've changed that now.
Still, IMHO, listing checksums on the same webpage as the downloadable file
doesn't make much sense, security-wise. If an attacker can modify the script, he
most probably can change
A new release of PCA has just been published. Here's a list of new features and
changes:
* Deprecate option supplevel after Oracle broke query interface
* Fix showing errors when running pca proxy in debug mode
* Whitelist: add 144500, 144501
* Whitelist: replace 143647/143648 with
Don O'Malley wrote:
Everything went very smoothly, but you may notice that there is now an
additional level of redirection added to patch downloads.
Requests to getupdates.oracle.com now redirect to updates.oracle.com via
login.oracle.com (for authentication).
Downloads work for me, but it
Jeff Earickson wrote:
Paul, it would be nice if pca spit up a message if a URL connection
times out, even if you are not running in debug mode.
I agree in that it would be nice, but it won't happen. I'm leaving all the
download stuff to wget - and I'm very glad that I don't have to care about
BABAULT.Daniel wrote:
No problem for me
patchdiag-110707.xref 07-Jul-2011 23:11 3.4M
patchdiag-110708.xref 08-Jul-2011 23:11 3.4M
patchdiag-110709.xref 09-Jul-2011 23:11 3.4M
patchdiag-110710.xref 10-Jul-2011 23:11 3.4M
But if you compare the files, you'll see that nothing
Don O'Malley wrote:
Gerry is on vacation at the moment, but he will be blogging about this when he's
back online.
Gerry's blog entry is now online as well:
http://blogs.oracle.com/patch/entry/a_solaris_recommended_patchset_to
Thanks for the info, Don!
Martin.
Jeff wrote:
A new procedure
would have pca download a copy of 144488-11, grab the dependency info from
within the zip, replace the info in a temporary patchdiag.xref, and then do
the normal dependency checks.
Not that I wouldn't have thought about that before :)
I'm not sure how practical it
Ateeq Altaf wrote:
Could we approach this a different way by first getting a list of missing
patches relevant to a patchdiag slightly *newer* than the CPU, then filter
that list with the list of patches on the CPU?
Should get you close. It also depends whether you succeed in finding the
Rajiv,
I kind of disagree on using CPU for couple of reasons.
Maybe you got me wrong - it's not that I use the CPU myself - I agree with what
you say. Personally, I don't see much sense in installing an outdated revision
of a patch. Why not get *all* available fixes, when I'm installing a
little help wrote:
Glenn,
That seems to provide a bit more detail, which seems to make sense had I
not seen the patchinfo file. I ran the pca command against the patch
without a revision (see below) and then ran the same command against the
dependencies to see if they had any pre-requisites
Jeff wrote:
From the way I understand how PCA works, when specifying a specific revision
of a patch, it does no checking prior to trying to install, since it can't
reference pre-reqs and supercedings in patchdiag.xref. As a test, I grabbed
the patch list from the CPU readme and fed it into
As the method which PCA uses to determine the support levels for an MOS Account
with the --supplevel doesn't work anymore for 2 months now, and as I found no
other method to query the required information, I see no alternative to
deprecating this option.
I've already made the required changes
Hi Kresimir,
this seems to be cookie issue with wget. If you save JSESSIONID cookie
using mozilla browser into file (you may capture it with Live HTTP
headers plugin for example) and then load this cookie file using
--load-cookies wget option, wget will return XML file correctly.
Interesting,
Steve Goldthorpe wrote:
With patch 119534-24 and above, createflar creates version 3.0 flash
archives that cannot be read by Solaris 10u9 miniroots. As Solaris 10u10 is
not out yet (which allegedly bring this capability), I have to ensure I only
patch to 119534-23 and not beyond.
To do this
Jeff wrote:
Guess the question is to Martin or Don: Do you know if this is intentional?
Sorry, I have no idea whether this is a mistake or intentional, I only can
confirm your findings and otherwise leave it to Don to provide an explanation.
Martin.
little help wrote:
I wanted to get feedback on what other are doing when installing patches.
For hosts in the environment I am trying to decide if I simply install all
patches or missingrs? I am aware of the added time and somewhat risk that
installing all introduces, but I have not had a
little help wrote:
Martin,
Agreed. However, as you know management loves charts and percentage
graphs. I just need some type of measurable indicator as to how much/often
we are patching hosts in the environment. The option you provide below
seems to be valid but would also become a
Ateeq Altaf wrote:
I've made the following addition to not overwrite a higher patch rev with a
lower one in the code, which I think should address the problem but not sure
if it's too simple and I've missed something:
Your fix is perfectly fine, and I've integrated it into my version of
Paul B. Henson wrote:
On Wed, May 11, 2011 at 11:47:34AM -0700, Ron Halstead wrote:
Please turn off your DAMN vacation notice. It is cluttering up the list.
Already had that conversation with Don; seems the official oracle
vacation message app is horribly broken -- it both replies to mailing
Hi Lee,
Both this:
Trying http://10.44.19.68/pca-proxy.cgi?
Failed (Error 401: MOS data missing)
.. and that:
I have debug=1 in my /etc/pca-proxy.conf file on my PCA proxy, but for
some reason it isn't writing a debug log in /var/tmp/.
.. strongly point at pca-proxy.cgi not reading
Fred wrote:
Ideally, I would like the sysadmin running the pca client to use the -a
argument so that he/she is prompted for the MOS credentials interactively,
but doing this doesn't seem to send the credentials to the proxy server.
This should work, actually. You should see this in the
Ben Taylor wrote:
On Wed, Apr 20, 2011 at 3:45 AM, Martin Paul mar...@par.univie.ac.at wrote:
I think some time ago, patches for older versions of Sun Studio were
available without the Software entitlement, but I just checked versions
12, 12.1 and 12.2 - for all of these the Software
Stanley Laufer wrote:
I'm now able to download a firmware patch that previously was unavailable
to us a month ago...
Same here. Can you do me a favor and use the method described in this link to
check for your patch entitlements:
Bleek Thomas wrote:
Same here, I have just notized this myself:-(
Sigh. Too bad, this option was very useful to diagnose patch access problems.
If you want, you can try the underlying wget command and see if the problem is
exactly the same. Run:
wget --no-check-certificate --http-user
Stanley Laufer wrote:
Thought this might be of interest to some of you. While working with
Oracle on the renewal of our OS support contract, I was just told the
following:
Oracle has changed their stance on Firmware and they will cover
Firmware support under OS coverage
Thats sounds
King, Jeff (GE Tech Infra, US) wrote:
My security team produces a list of mandatory security patches that must
be installed monthly.
Is there a way to give pca this list of patches and have it return, a
status to represent either no patching action required, or patching
required?
PCA itself
Stuart F. Biggar wrote:
I guess I could use some pointers or does PCA not work with SunRay due to the
way Oracle does patches for it? It looks to me like the current cross
reference file doesn't have appropriate info for SunRay on x86 Solaris 10?
That's new to me, but as Richard says - the
Roland Soderstrom wrote:
To me it's really not a problem as I downloaded them from MOS, but maybe PCA
needs a tweak.
As Don describes, it is old patches and tweaking PCA might not be worth the
effort.
It always depends on the effort which is required :) Here it wasn't too hard, so
I've
Roland Soderstrom wrote:
Got this when downloading this firmware patch.
I downloaded it using MOS without any problem, could there be a pca
problem?.
I can't check that, as I don't have a support contract which includes access to
firmware patches right now. So I get Error 403: You are not
Hi Scott,
For some reason, I have a habit of setting --wgetproxy manually on the
command line when I run pca so maybe that's why things have worked in the
past even though I didn't have https_proxy set in wgetrc?
Yes, that's likely. PCA deals with the proxy setting in a different way than
Grzymala-Busse, Dobroslawa M wrote:
I try to download patches for my OS 10 and I am unable to get 1/3 of them.
Also, when I tried to download 110254 I am getting: Failed (Error 403: Service
Error)
but I am able to read the 110254 README file.
Patch 110254 (Veritas Volume Manager 3.1) is
Nishimura, Scott L (IT Solutions) wrote:
Unfortunately, I can't get *any* patches. I used to be able to, even after
the MOS transition [some time after 12/10]. My internal proxy guy says the
403 error I'm getting is due to the remote server, not our internal one.
Ok, so we'll try to rule out
Nishimura, Scott L (IT Solutions) wrote:
Summary
I'll take a look at the detailed output later, but one thing I noticed
immediately:
# cat /.wgetrc
use_proxy=on
http_proxy=proxy
proxy-user= user
proxy-passwd=password
check-certificate=off
You only set http_proxy here - please try to set
Studer Olivier wrote:
I would like know, if it's possible to run pca in single user mode to install
patch need this mode ?
pca runs fine in single user mode, and if you can afford the downtime,
installing patches like that is the safest method anyway.
It might be best to pre-download
Nishimura, Scott L (IT Solutions) wrote:
I'm running PCA for the first time in a few months [20101221-01]. I'm now getting
403 Service Error when trying to download any patch.
As you say in a few months - have you ever used it after the switch to the new
Oracle servers? Just to be sure -
little help wrote:
Thanks for the quick reply. What is the -askauth parameter? I dont see it
as an option.
It's deprecated, as it's the default now. Previously it was required to make PCA
ask for authentication data if it isn't provided via a config file or an option.
Nowadays PCA will
Seems as if the most recent patches from today's patchdiag.xref haven't made it
to Oracle's server yet. Patch download for these fails with 404
h1/all_unsigned/xx-xx.zip Not Found/h1:
Patch IR CR RSB Age Synopsis
-- -- - -- --- ---
Hi Jan,
since all stuff went to MOS I started to use pca --readme a lot more.
I understand that - I try to avoid using interactive MOS as far as possible as
well :)
My problem is that if you do something like --readme 144574
(Patch without revision) it will get all other readme files
Rajiv Gunja wrote:
I was looking through Oracle Patch Cluster Read-me and saw that they had 2
other patches than 119254.
120900-04 SunOS 5.10: libzonecfg Patch
121133-02 SunOS 5.10: zones library and zones utility patch
119254-78 SunOS 5.10: Install and Patch Utilities Patch
Do you think we
Am 08.02.2011 16:32, schrieb Fairburn, Jeremy:
I think I may be confused with the local caching proxy and the web
proxy. The local caching proxy has access to the internet so I guess I
don't need a web proxy. Is that correct?
Yes, that's correct. I understand that the various types of
Hi Jeremy,
Fairburn, Jeremy wrote:
I'm trying to download patches from servers not connected to the
Internet through our proxy server but am getting the following error
from wget. I've searched through the archives and haven't seen anyone
with this error so I probably don't have something
Jeremy,
I am using the wgetrc file to feed information to the proxy. I get the
same error when running that command. I also tried to set the
username/password in the wgetrc file which didn't help either. I am
using the username/password for my Oracle account. Please let me know
if that's
Am 07.02.2011 17:38, schrieb Fairburn, Jeremy:
Does the apache server need to be configured with SSL? I just checked
and it is not.
I'm confused. Which role does the apache server play? The message you
showed seems to come from a generic web proxy, have you set up a PCA
local caching proxy
BABAULT.Daniel wrote:
Trying to install 10_sparc_0910_patchbundle I found a problem on on server
# /usr/sbin/patchadd 142909-17
...
Looks as if the patch installed fine after all?
Is the system in question by chance a Niagara machine (sun4v from `arch -k`)? If
so, the messages only apply
Craig Bell wrote:
Hello all - I recently ran into an issue using pca(8) with zones and $TMPDIR.
Have you seen this before?
Not me. I have only minimal experience with patch zones (and zones in general).
So I can only comment on this sub-question:
Alternate theory: I recall years ago
Hi Jeremy,
Does anybody know of a way to make pca recurse and look to see if a patch
which has obsoleted the listed patch is installed on the system?
Not directly. But you can maybe use the chkmin script I've put onto
http://www.par.univie.ac.at/solaris/pca/contrib.html - its primary use is
Hi,
Alasdair Lumsden wrote:
This morning I registered for My Oracle Support, and had our Solaris 10
support entitlement added to the account.
I'm able to download patches fine via My Oracle Support, however when
using an updated PCA, I mostly get 502 Proxy Errors (But sometimes it
works -
Laurent Blume wrote:
That they might be giving up on dependencies is not very good news though.
To be fair, the issue we're talking about is a very special case, and actually
there's no good solution for this problem in the current patch infrastructure:
Patch requirements aren't added to an
Hi Laurent,
But how exactly is it possible to install this patch prior to this one?
142910 17 = 17 RS- 134 SunOS 5.10_x86: kernel patch
The idea with this Place Holder Patch was that the kernel patches would always
depend on it, so when a new kernel patch is installed, the place holder patch
Laurent Blume wrote:
Yes, the lack of dependency is kind of surprising. Is there some other
special handling of them in PCA or Sun patching tools to ensure they are
applied in the correct order if needed?
12/125556 are not handled in a special way in PCA. I do sort the patch
utility
dpecka wrote:
sorry for this deviantic molestation with Error: 403 but it seems like
something has changed on oracle site with year of 2011 ..
I've download a few patches today, and it worked fine.
https://getupdates.oracle.com/all_unsigned/145668-01.zip
Resolving getupdates.oracle.com...
Coskun, Aydin wrote:
I am having bit of issues with setting up my PCA server. If I use
pca.conf file I get Failed (Unknown Error) but if don't use pca.conf and
I enter username and password interactively it works. Please help!
...
Here is my setup:
# cat /pca/Scripts/pca.conf
#My Oracle
It's really strange that interactive access to MOS works, while downloads via
PCA/wget don't. You'll have to go a step back and take PCA out of the equation.
Take a look at the wget examples in article 1199543.1:
Michele Vecchiato wrote:
2010/12/27 Martin Paul mar...@par.univie.ac.at:
If you try that, and see 404 again, please let me know what you find in the
pca-proxy-debug file.
Setup debug=1 to the pca-proxy.conf and i watched the trouble is
/etc/wgetrc permissions:
r...@pdpcasrv1 # ls -al /etc
Richard Skelton wrote:
There is a problem with PCA when trying to install a patch from a proxy
when the patch is already being downloaded by the proxy:-
120185 21 22 RS- 6 StarOffice 8 (Solaris): Update 17
There have been some timing issues with large patches in the past, and the
A new release of PCA has just been published. Here's a list of new features and
changes:
* New option to show support levels of a given MOS Account (--supplevel)
* Send authentication to Oracle server without being asked
* Use links to getupdates.oracle.com in HTML output
* Rename option
Dennis Clarke wrote:
Well, still I am told that my contract is not recognized and is not a
valid support identifier.
Just to be sure - during registration you're asked to enter either a Support
Identifier or a Contract Number. AFAIK an existing Sun Contract Number will
only be recognized in
Recently Mike Brown provided a document ID (1269292.1, available on My Oracle
Support) which explains the correlation between Support Contracts, Support
Levels and Patches.
In short, a certain Support Level is required to access any patch. A certain
type of Support Contract includes one or
Mike Brown wrote:
The following knowledge article is available with this information - How
Patches and Updates Entitlement Works (Doc ID 1269292.1)
Thanks Mike, very informative!
The method to determine what Support Levels a User has looks a little, uhm,
rough :-) Hopefully this is just
Jeff,
Thanks for adding this feature, I just tried it (after fiddling with my
firewall, this feature requires http/https access to support.oracle.com and
login.oracle.com).
Good point. I've now added a sentence about firewall configuration to the
installation instructions on the PCA site.
101 - 200 of 503 matches
Mail list logo
