I wrote this email because on Thu, 19 Jan 2012 15:29:04 +0100 Jan Pazdziora said:
> We've seen this workaround before but until we understand the nature > of the issue and why these would make the problem go away, I'm > resitant to include them in the distribution. Since we were not able > to reproduce the issue locally, we really cannot bring it up to the > database vendor support -- that's why I was asking people to do that. It appears to me that error is easily reproducible on off the shelf hardware and software. If someone can provide a stand alone SQL script to reproduce the error outside of spacewalk framework I may be able to follow up. 01.03.2012, 03:43, "Jan Pazdziora" <[email protected]>: > On Wed, Feb 29, 2012 at 11:26:11PM -0500, [email protected] wrote: > >> In response to >> https://www.redhat.com/archives/spacewalk-list/2012-January/msg00159.html >> >> I am very surprised that almost a year old problem is taking that long to >> reproduce. >> >> Seems like a clear shot. > > Alright. What did the Oracle support say about the issue? > > -- > Jan Pazdziora > Principal Software Engineer, Satellite Engineering, Red Hat _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
