On Mon, Aug 06, 2012 at 10:44:32AM +0200, Mario Mikocevic wrote: > On 08/06/2012 09:28:14 AM, Jan Pazdziora wrote: > > > > What did Oracle support tell you when you reported this issue to them? > > Is it a bug and as such, when will it be fixed or what's the > > workaround? Or is it considered an expected behaviour? > > When my DB Admin coleague contacted Oracle about it, he got confirmation > that it is a bug in Oracle but with no immediate resolution fix.
Thank you for the confirmation. > Over the weekend we kinda fixed it, > oracle optimization bug is basicaly in skipping presetting and/or initializing > 'vital' DB areas so we just browsed through DB structure. > Granted, this works only for situations when DB is already set. > > So, my spacewalk production is back online. > > For instalations you can use > https://www.redhat.com/archives/spacewalk-list/2011-May/msg00023.html fix ! To make it work, do you always have to do the three selects, or would one select be enough to setup those DB areas? My fear as expressed in https://www.redhat.com/archives/spacewalk-list/2011-May/msg00024.html is that fixing it for one lookup value might still cause it to fail for a different one. Also, after the database restart, do you need to do tha select again or is it already set alright? -- Jan Pazdziora Principal Software Engineer, Satellite Engineering, Red Hat _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
