My understanding from CA is that it was pulled because it caused a problem
in the Spectrum<->EEM integration, which we¹re not using. Regardless, we¹re
stuck on H04 since hotfixes do not contain a rollback mechanism like patches
do. We¹re putting in an ER for this.


On 5/26/11 9:49 AM, "David Game" <[email protected]> wrote:

> Jim ­ HF04 has been pulled due to an inordinate number of bugs!  If you can
> roll back to H03 until HF04 is ³fixed² I¹d strongly advise it.
>  
>  
> 
> From: Pfleger, Jim [mailto:[email protected]]
> Sent: 26 May 2011 16:09
> To: spectrum
> Subject: [spectrum] H04 experiences (WAS: Problems with Spectrum 9.2 H03)
>  
> As promised, here¹s an update on the issues from my previous email ­ all four
> were addressed in H04. I¹m awaiting final confirmation from our reporting guru
> on the SRM issue, but I believe it¹s been resolved. Also, we¹re occasionally
> getting duplicate notifications again, but the debug looks different from the
> last time this happened, so we¹re treating it as a separate issue.
> 
> Because of these fixes (and others) we installed H04 as soon as it was
> available, so I can provide some early feedback.
> * We¹ve found two events (so far) that are no longer logged to the events
> database (0x1010a and 0x1010d, for model attr changes). We¹re going to now
> conduct a full audit of what other undocumented event changes came with H04.
> * It seems that our failover servers are sometimes being started as root
> instead of ssadmin, which is mangling file permissions. The problem started
> after H04, but it¹s not clear why yet, partly because it¹s only happening on
> some of our failover servers.
> * The negative alarm counts issue citied in the release notes is not
> (completely) fixed, and we already have a new ticket open on it.
> 
> That¹s all I have so far on H04. When I have anything else of note, I¹ll
> definitely share it with the group.
> 
> HTH,
> Jim
> 


---
To unsubscribe from spectrum, send email to [email protected] with the body: 
unsubscribe spectrum [email protected]

Reply via email to