Re: ORA-12899: value too large for column with Oracle Patch 10.2.0.4
Date: 08 Oct 2008 09:25:47 GMT
Arne Ortlinghaus <Arne.Ortlinghaus_at_acs.it> wrote:
> Yes, normally I know this message only from illegitimate inserts. But now I
> had this type of error at least two different program/places at two
> different sites for perhaps 20 times in total. In this time the
> corresponding SQL statements have been executed several 10000 of times
> without errors. When executing the statement afterwards again everything is
> Before updating to 10.2.0.4 I have never seen this error at these two
> different places.
> It is difficult to generate a Service request with these informations
> because I have not the the statement which is really executed.
You are right, it would be very helpful to know which SQL statement causes the error.
I could not find anything similar on Metalink; all references that sounded remotely relevant were for SQL*Loader.
Can you reproduce the error ar will or does it only occur sometimes?
What program or application issues the statement, and which API is used to access Oracle?
In any case I would try to enable SQL tracing on the server side to catch the statement that causes the problem.
You can use DBMS_MONITOR.DATABASE_TRACE_ENABLE(FALSE, TRUE) to enable
tracing for the whole database or
DBMS_MONITOR.SESSION_TRACE_ENABLE(NULL, NULL FALSE, TRUE) to trace the current session.
Tracing will slow down things and generate a lot of output.
To find the statement that causes the error, you can search for the error
number in the trace files.
To reduce the amount of data logged, you could write a logon trigger that enables tracing only for a certain user.
Laurenz Albe Received on Wed Oct 08 2008 - 04:25:47 CDT