Good news, everyone! We've been assigned to a new support engineer (after much complaining), who states:
> We do support PCA as a patching tool, by the way. We may get to the bottom of this yet... We reverted our environments, and are running a completely unpatched 10u8 for now. We also have provided Sun Managed Services with a list of 104 patches we'd like them to apply *by hand* to our test environment, per our contract. Strange how PCA is suddenly a supported tool after sending the patch list :) I'll continue providing occasional updates as this progresses, assuming you're not all bored yet. Thanks for the support and advice... --Scott On 03/09/2010 07:02 PM, Paul B. Henson wrote: > On Tue, 9 Mar 2010, Scott A. Severtson wrote: > > >>> 3) revert to a point before PCA was used and return to the current patch >>> levels without it. If the issue persists we can begin developing a fix as >>> mentioned above so you can revert once more and then apply the fix. >>> > Yah, I woulda picked option 3, but skipped the "backout patches and reapply > by hand" part ;). Other than possible pca invocations in your shell history > file, I can't think of any possible forensic evidence proving patchadd was > called by pca as opposed to run by hand from a shell prompt. > > That's just pitiful support. > > >
