Ora 06512 описание ошибки

Did you get an ORA-06512 error when running an SQL query? Learn what this error is and how to resolve it in this article.

The ORA-06512: At Line error is caused by an exception in your query that is not handled. The error message you get will look similar to this:

ORA-06512: at line n.

Where n is a line number.

This ORA-06512: At Line error message is a generic PL/SQL error message that happens when an exception is not handled.

When an error message is displayed, a stack trace is also shown, which shows the sequence of calls made to the database by the code. There might be several lines here, and one of them will be the ORA-06512 error.

Here’s an example from SQL Developer”

So, how do you resolve it?

ORA-06512 Solution

There are two main ways to resolve this error:

1. Fix the code that is causing the error
2. Add an exception handler to your PL/SQL code.

I’ll show an example of this error, and how to resolve it using both of these errors in this article.

Example of This Error

Let’s say you had this PL/SQL stored procedure:

CREATE OR REPLACE PROCEDURE TestOutput AS
pName VARCHAR2(5);
BEGIN
  pName := 'Steven';
END;
/

This is a simple procedure that sets a variable.

If we run the statement to create the procedure, there is no issue.

Procedure TESTOUTPUT compiled

Now, if we run the procedure itself:

EXEC TestOutput;

Error starting at line : 8 in command -
EXEC TestOutput
Error report -
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "SYSTEM.TESTOUTPUT", line 4
ORA-06512: at line 1
06502. 00000 -  "PL/SQL: numeric or value error%s"
*Cause:    An arithmetic, numeric, string, conversion, or constraint error
           occurred. For example, this error occurs if an attempt is made to
           assign the value NULL to a variable declared NOT NULL, or if an
           attempt is made to assign an integer larger than 99 to a variable
           declared NUMBER(2).
*Action:   Change the data, how it is manipulated, or how it is declared so
           that values do not violate constraints.

It gives us an error that wasn’t found when it was compiled.

If you look at the message, you’ll see our ORA-06512 error:

ORA-06512: at "SYSTEM.TESTOUTPUT", line 4
ORA-06512: at line 1

However, the actual error that occurred is further up in the message.

>ORA-06502: PL/SQL: numeric or value error: character string buffer too small

If we resolve this error, then the ORA-06512 should also disappear.

Let’s take a look at the procedure.

CREATE OR REPLACE PROCEDURE TestOutput AS
pName VARCHAR2(5);
BEGIN
  pName := 'Steven';
END;
/

It looks like the error is being triggered on line 4, where pName is being initialised. It’s happening because the pName variable is 5 characters long, but the variable is 6 characters.

We can resolve this in two ways. First, we can adjust the size of the variable.

CREATE OR REPLACE PROCEDURE TestOutput AS
pName VARCHAR2(6);
BEGIN
  pName := 'Steven';
END;
/

I’ve increased pName from 5 to 6 characters to handle the value of “Steven”.

Or, we can add an exception handler. This will mean that any errors that are found are treated in a certain way.

Let’s say if the value is over 5 characters then we trim it to 5 characters.

CREATE OR REPLACE PROCEDURE TestOutput AS
pName VARCHAR2(5);
BEGIN
  pName := 'Steven';
EXCEPTION
  WHEN OTHERS THEN
    pName := SUBSTR('Steven', 1, 5);
END;
/

If we run this procedure now, then the error does not appear.

ORA-06512 at sys.utl_file line 536

Are you getting this specific error message, which mentions the sys.utl_file package?

This is most likely happening because of a permissions issue when exporting a file to a directory. This question on StackExchange and this question on StackOverflow are a couple of examples.

To resolve it, you can do several things:

1. Make sure the user that is running the procedure has write access to the directory you’re mentioning. Double-check this – as it can often seem like the right permissions are defined but they are not.
2. Check that the directory is correct. It often needs a trailing slash, or if using a network directory, the full path might be needed.

So, in summary, the ORA-06512 error appears because there is an unhandled error in the PL/SQL code being called. To resolve it, either fix the error in the code or add an exception handler.

If you just want to export data once-off and not in PL/SQL, you could use SQL Developer’s export functionality which I’ve written about here.

ORA-06512 Error Message

Error Ora-06512 means the backtrace message as the stack is being unwound by unhandled exceptions in your PLSQL code. This is a catch-all error for PLSQL exceptions and is commonly seen.

Ora-06512 does not indicate the actual error, but the line number of the unhandled error in the PLSQL code. Ora-06512 will typically appear in a message stack in which the preceding message names the reason for the error, such as in the following example:

ORA-06502: PL/SQL: numeric or value error

ORA-06512: at line 12

The preceding message names the reason for the error (“numeric or value error”) while Ora-06512 indicates the line number of the error (line 12).

There are 3 ways to resolve Ora-06512:

Fix the error causing the unhandled error.

Write an exception handler for the unhandled error.

Contact the database administrator (DBA).

The Solution

The steps of fixing the error will depend on the error itself. This is an example of an Ora-06512 message in a “AProc” procedure for which the error is fixed:

CREATE OR REPLACE PROCEDURE AProc

AS

a_number number(3);

BEGIN

a_number := 1000;

END;

/

When this procedure is written, you will see the following error message:

execute AProc();

BEGIN AProc(); END;

*

ERROR at line 1:

ORA-06502: PL/SQL: numeric or value error: number precision too large

ORA-06512: at “EXAMPLE.APROC”, line 5

ORA-06512: at line 1

The preceding error indicates the user the error (number precision too large). Ora-06512 indicates the line number in which the error occurred (line 5). In this case, the error occurred because a 4-digit number was assigned to the variable a_number which is set to handle only 3 digits. The error is resolved by setting the variable a_number to handle 4 digits:

CREATE OR REPLACE PROCEDURE AProc

AS

a_number number(4);

BEGIN

a_number := 1000;

END;

/

Write an Exception Handler

To resolve the same example error as above, you may choose to write an exception handler rather than fixing the error. The following is how you would write an exception handler:

CREATE OR REPLACE PROCEDURE AProc

AS

a_number number(3);

BEGIN

a_number := 1000;

EXCEPTION

WHEN OTHERS THEN

a_number := 999;

END;

/

Since the variable a_number can only handle 3-digits, you can write an exception handler to set the variable a_number to a 3-digit number (999) when this error occurs.

If you cannot resolve the error by fixing the error or writing an exception hander, contact your DBA.