On 09/03/2010 06:51, Ben Taylor wrote:
Escalate higher. This is a ridiculous argument by some clueless
Sunsolve engineer.
The first rule of PCA is: You do not talk about PCA to Sun support.
I wouldn't bother escalating. It sounds like he's hit a backline OS
engineer, and said engineer has taken the hump. Close the case, then
open a new one and hopefully you'll get a different backline engineer
that hasn't seen the previous ticket. Tell him/her that you're using
patchadd to add 142901-05. Observe the first rule of PCA at all times.
Dave
On Tue, Mar 9, 2010 at 12:01 AM, Scott A. Severtson
<scott.severt...@digitalmeasures.com> wrote:
All,
Per Sun's support engineer:
---
PCA is not a supported way to apply patches and it must be used at the
user's own risk.
This system is not supportable. I recommend we close this case and ask the
customer to use upgrade media to return to a supportable state. If the issue
persists you or he can open a new case referencing this original.
---
That's fantastic.
--Scott
On 03/08/2010 05:05 PM, Scott A. Severtson wrote:
Alan,
We have a case open with Sun (#72559404), which you may want to
reference. They've done some diagnostics, and have some clues, but
nothing definitive yet.
All the machines involved run Postgres within a zone, regardless if the
patch was successful or not.
However, I'm glad to know I'm not crazy :)
--Scott
On 03/08/2010 04:55 PM, Alan Wilson wrote:
Has anyone else successfully deployed 142901-05? Any ideas what we're
doing wrong?
Many thanks,
--Scott Severtson
We're having exactly the same issue as you....
The patch installed fine on one x4140 but not the other.
We had exactly the same symptoms as you.
The only difference is the problem server runs postgres.
Is that the case with you?
Our solaris support people recommended we open a
support case with Sun.
Alan
