I don't have my notes to hand, but I seem to recall I ran into issues with this trigger on a Standard Edition database that had been upgraded with spatial in place. Note 1091950.1 covers the base issues that we had, but I can't recall what the actual trigger problem that we had was now. We too removed spatial as it wasn't actually used. On Wed, Aug 25, 2010 at 9:53 AM, Connor McDonald <mcdonald.connor@xxxxxxxxx>wrote: > That's an interesting result. > > The call to delete from sdo_geor_ddl__table$$ is a "on servererror" > trigger....I'm surprised that removing it solved your problem, because > removing the servererror trigger naturally would not be expected to remove > the server error in the first place ... > > Cheers > Connor > > On Wed, Aug 25, 2010 at 8:57 AM, Jack van Zanen <jack@xxxxxxxxxxxx>wrote: > >> Hi All, >> >> >> The mystery is solved, sort of. >> >> >> >> >> Jack van Zanen >> >> ------------------------- >> This e-mail and any attachments may contain confidential material for the >> sole use of the intended recipient. If you are not the intended recipient, >> please be aware that any disclosure, copying, distribution or use of this >> e-mail or any attachment is prohibited. If you have received this e-mail in >> error, please contact the sender and delete all copies. >> Thank you for your cooperation >> >> >> On 25 August 2010 00:11, Hemant K Chitale <hkchital@xxxxxxxxxxxxxx>wrote: >> >>> >>> The trace file would have an ERR# entry before the "SQL*Net >>> break/reset client". The ERR# would be the Error Number. >>> >>> Hemant K Chitle >>> >>> >>> At 02:10 PM Tuesday, Jack van Zanen wrote: >>> >>> Error: >>>> ORA-06510: PL/SQL: unhandled user-defined exception >>>> >>>> >>>> When we trace the application we can see the statement executed >>>> returning no rows and having the "SQL*Net break/reset to client" waits >>>> with >>>> it. These waits point to an error in the call, but what I really like to >>>> see >>>> is the actual oracle error generated which is unfortunately hidden by the >>>> user defined exception. >>>> >>>> How can I find out, without going back to the vendor, what the actual >>>> error message is. >>>> >>>> >>>> I will try "alter system set events '6510 trace name errorstack level >>>> 1';", but will it help? >>>> >>>> >>>> Jack van Zanen >>>> >>>> >>> >>> Hemant K Chitale >>> >>> http://hemantoracledba.blogspot.com >>> >>> >>> >>> >>> >>> >> > > > -- > Connor McDonald > =========================== > email: connor_mcdonald@xxxxxxxxx > web: http://www.oracledba.co.uk > > "Semper in excremento, sole profundum qui variat" > -- Niall Litchfield Oracle DBA http://www.orawin.info