1

enter image description here

Anybody seen errors like this before? Any fixes? I'm expecting this to be something deep down in the Salesforce platform and not something I've done but any guidance appreciated.

(I notice Sneezy has made an appearance - and looking around the web it seems that other dwarves are available ;-) )

Richard Durrant
  • 3,092
  • 1
  • 16
  • 26

2 Answers2

2

The documentation from Oracle may help:

ORA-06512: at stringline string

Cause: Backtrace message as the stack is unwound by unhandled exceptions.

Action: Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or DBA.

Sounds like a ticket to salesforce is in your future. Good Luck!

Alternatively you can remove lines of your code until you get it to work, then add them back in to see what causes it. Sometimes it is your code doing it but the error is not very specific

Eric
  • 54,152
  • 11
  • 100
  • 195
0

The error is caused by adding an entry into the Standard pricebook that is fired by an after insert trigger when cloning a product. When the trigger fires there is (probably) an entry that has been added to the Standard Pricebook that isn't returned by a SOQL query and so my code thought a new one had to be added explicitly thereby causing an exception as there were now 2 PBEs in the same pricebook for the same product (and currency).

My solution was to set the function checking for the preexisting PBE to be a future method and so the PBE was selectable and updated as necessary in code. Stopping the duplicate PBE fixed the exception.

Richard Durrant
  • 3,092
  • 1
  • 16
  • 26