Hi, I have two productive 11g (single instance on RHEL 4-U6 64bit) systems running on 11g...migration was easy and without stress...thanks to new 11g features...I have faced some bugs but they are not 'critical' i.e. I can 'live' with them. here is the list with the problems I have faced - till now ;-) - Bug.6646326 (11) ORA-600[KSL_INVALID_LATCH], [KSLGES] - Bug.6145377 Gen V1110 (11) ORA-00600 INTERNAL ERROR CODE, ARGUMENTS [QKSWCINLINE1]: - bug 6651027 (Patch 6651027) - KRBR8B2 - ERROR VALIDATING FILE 2, BLOCK 33029: LOGICAL CORRUPTION - with this problem I can run compressed backup...but if next sequence within rman block is "restore database check logical validate;" I got error...w/o compress works OK...for now this is also not that much critical, for this DataMart we can live w/o compressed backup - once per week ;-) run { allocate channel c1 device type disk; backup as compressed backupset format="compress_bck_%d_%T_%t" database; restore database check logical validate; release channel c1; } The OSS is working on this issue... hth, goran On Wed, Apr 23, 2008 at 5:30 PM, Stephens, Chris < chris_stephens@xxxxxxxxxxxx> wrote: > Is there anyone out there that has taken the leap to 11g in production > yet? Any major problems? > > > > Is the general consensus that waiting for release 2 is the way to go? > > > > There is a ton of stuff in 11g that will be useful and I'm thinking about > heading down the upgrade path but if it is just a flat-out bad idea, I've > got plenty of other stuff to do. > > > > I realize this is very open ended but any input would be appreciated. > > > > Thanks! > > Chris > > CONFIDENTIALITY NOTICE: > This message is intended for the use of the individual or entity to which > it is addressed and may contain information that is privileged, > confidential and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient or the employee or agent > responsible for delivering this message to the intended recipient, you are > hereby notified that any dissemination, distribution or copying of this > communication is strictly prohibited. If you have received this > communication in error, please notify us immediately by email reply. > > >