I may be jumping in late on this, but=20
alter session set events '1401 trace name errorstack level 10'
... will dump a trace file with the offending piece of SQL.
- John
- Original Message -----
From: Paul Drake <bdbafh_at_gmail.com>
To: Tony.Adolph_at_o2.com
Cc: oracle-l_at_freelists.org, Jonas.Kilian_at_o2.com
Sent: Thu, 24 Feb 2005 11:56:31 -0500
Subject: Re: ORA-01401: inserted value too large for column
> Tony,
>=20
> v$active=5Fsession=5Fhistory.
> as perscribed by others here on the list, set statistics=5Flevel=3D'BA=
SIC'
> and these will go away. (thanks, Niall).
>=20
> this was for 10.1.0.3 on win32 - but since you did not include the
> database version and OS ... I'm just guessing. (hint)
>=20
> Paul
>=20
>=20
> On Thu, 24 Feb 2005 14:30:18 +0100, Tony.Adolph_at_o2.com
> <Tony.Adolph_at_o2.com> wrote:
> > Hi all,
> > A developer here is trying to find the source of the error "ORA-0140=
1:
> > inserted value too large for column". He want to know which table /
> > column(s) are causing the problem.
> >=20
> > The error is not logged in the alert log.
> >=20
> > I set sql=5Ftrace =3D true and had him repeate his tests. Although =
we got
> > bucket loads of trace files in both user=5Fdump=5Fdest and
> > backfround=5Fdump=5Fdest we did not get any trace files or errors re=
lating to
> > ORA-01401. I tried to grep for just the 1401 string, still nothing.
> >=20
> > How can find the culprit here folks=3F
> >=20
> > Cheers
> > Tony
> >=20
> > --
> > http://www.freelists.org/webpage/oracle-l
> >=20
>=20
>=20
> --=20
> #/etc/init.d/init.cssd stop
> # f=3Dma, divide by 1, convert to moles.
> --
> http://www.freelists.org/webpage/oracle-l
>=20
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Feb 24 2005 - 12:06:35 CST
