Why surface these errors rather than the generic GACK message. Either they aren't being caught by the GACK mechanism or they are being rethrown. Its also interesting that they tend to bypass the GACK. The presence of Oracle error codes like ORA-00001 and ORA-20191 plus the would indicate they are some sort of layer immediately above the database running Java. That doesn't mean we can't make some wild conjectures. I suspect anyone who can tell you exactly where they are in relation to the database has probably signed a non-disclosure agreement. See Salesforce, Snow White and the Seven Dwarfs and The Silver Lining - Meaningful Error Messages #94. There are references to them back in 2009. If you spot one of them, you need to contact support so they can be put back in their dwarfy walled garden. You should never see DOPEY, SLEEPY, DOC, GRUMPY, SNEEZY, BASHFUL, or HAPPY, but occasionally they break out and appear to a user. The Seven Dwarfs live in the platform code. This seems timely as Grumpy just popped out of the developer console at me.Īs per comment and answer to the linked question. Timeout expiredORA-06512: at "DOC.CAPEX", line 2200ORA-06512: at lineġ: SQLException while executing plsql statement: ([
: ORA-30006: resource busy acquire with WAIT
0 kommentar(er)
