ORA-06512 : at line

ORA 06512 or ORA 6512 is a common error faced by oracle users and administrators alike during the operations of an oracle database. The ORA-06512 error in itself does not indicate the actual issue or an exception code. ORA-06512 normally indicates the line number at which the oracle PL/SQL code has caused an error or exception condition. The rest of the article provides steps to analyze this error along with further references that can be leveraged for solving an error ORA-06512.

Error Description.
[Oracle][ODBC][Ora]ORA-01013: user requested cancel of
current operation
ORA-06512: at "MMS_TEST.YPPAMERGE", line 93
ORA-06512: at line 1

In the above example, ORA 6512 message generated by the oracle database server indicates that the error 1013 was caused by the user cancelling the current operation while the ORA 06512 error indicates the line number at which the code execution was cancelled.

You should try to focus on the ORA-01013 oracle error in this case and use the ORA 6512 to identify the line number or code which has caused an exception and fix the exception or add an additional exception handler based on the type of error.

ORA-06512 at string line 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

ORA-06512 Notes :

Q : ORA-6512 and ORA-00600 ..I am running into the following error when I try to export my database in 10g...

exporting pre-schema procedural objects and actions
. exporting cluster definitions
EXP-00056: ORACLE error 600 encountered
ORA-00600 : internal error code, arguments: [qmtInit1],
ORA-06512 : at "SYS.DBMS_METADATA", line 1511

A: ORA-06512 : You may be running into a known XDB Bug listed at the following documents in Metalink..looks like an xdb bug listed in bug id's 3939845, 2626241, 2730857. Look up in metalink for answers surrounding the same.