Links
Home
Oracle DBA Forum
Frequent Oracle Errors
TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found'>ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated
ORA-01401: inserted value too large for column

ORA-01401: inserted value too large for column

2005-02-24       - By Paul Drake

Reply:     1     2     3     4     5     6     7     8  

Niall,

If you do get anyone to use it, make certain that it gets cleared out.

Better than they NEVER use dbms_application_info than to use it improperly.
False positives (it never being unset) is far worse than it being blank.

dbms_monitor in 10g will never make a difference to me based upon what
is set by dbms_app_info - as I can't trust it one bit.

my favorite is seeing something about "login" in there in the midst of
some heinously large report. those are real useful.

Paul


On Thu, 24 Feb 2005 20:22:58 +0000, Niall Litchfield
<niall.litchfield@(protected)> wrote:
> Comments embedded
>
> On Thu, 24 Feb 2005 14:30:18 +0100, Tony.Adolph@(protected)
> <Tony.Adolph@(protected)> wrote:
> > Hi all,
> > A developer here is trying to find the source of the error "ORA-01401 (See ORA-01401.ora-code.com):
> > inserted value too large for column".  He want to know which table /
> > column(s) are causing the problem.
> >
> > The error is not logged in the alert log.
>
> That would be normal, it should be thrown back to the offending
> application. All this rather suggests that the app could do with
> rather better exception handling, c'est la vie.
>
> > I set sql_trace = true and had him repeate his tests.  Although we got
> > bucket loads of trace files in both user_dump_dest and
> > backfround_dump_dest we did not get any trace files or errors relating to
> > ORA-01401 (See ORA-01401.ora-code.com).
>
> If you set this at the instance level - which it rather sounds like
> you did - I suggest you unset it before you fill the disk!
>
> >  I tried to grep for just the 1401 string, still nothing.
> >
> > How can find the culprit here folks?
>
> A number of ways.
>
> You can set a 1401 event in the init.ora/spfile
> You can persuade the developer to set event 10046 at logon.
> You could even persuade them to use DBMS_APPLICATION_INFO
> You can use an after servererror trigger like the one I posted for the
> temp tablespace error a couple of days ago.
>
> --
> Niall Litchfield
> Oracle DBA
> http://www.niall.litchfield.dial.pipex.com
> --
> http://www.freelists.org/webpage/oracle-l
>


--
#/etc/init.d/init.cssd stop
# f=ma, divide by 1, convert to moles.
--
http://www.freelists.org/webpage/oracle-l