ORA-01401: Value inserted too large for column

DBA Geral (instalação, configuração do banco, scripts do Sql*Plus, shell scripts, batch scripts, etc...)
Post Reply
thiago.sousa
Rank: Programador Júnior
Rank: Programador Júnior
Posts: 28
Joined: Fri, 09 Dec 2005 9:17 am
Location: Itajai-SC
_______________________________________
Thiago Antonio
SCJP - Sun Certified Java Programer
SCJA - Sun Certified Java Associate

Guys, how do I find out which value is greater than the column ... ????
urgently.


Thanks;
User avatar
dr_gori
Moderador
Moderador
Posts: 5026
Joined: Mon, 03 May 2004 3:08 pm
Location: Portland, OR USA
Contact:
Thomas F. G

Você já respondeu a dúvida de alguém hoje?
https://glufke.net/oracle/search.php?search_id=unanswered

I think you have to go testing ... I think a debug was to solve.
thiago.sousa
Rank: Programador Júnior
Rank: Programador Júnior
Posts: 28
Joined: Fri, 09 Dec 2005 9:17 am
Location: Itajai-SC
_______________________________________
Thiago Antonio
SCJP - Sun Certified Java Programer
SCJA - Sun Certified Java Associate

This error only takes place on the client, is a very complex and difficult to debug routine.

I wanted some command or trigger to get the SQL that was running and see the value of the columns.
User avatar
dr_gori
Moderador
Moderador
Posts: 5026
Joined: Mon, 03 May 2004 3:08 pm
Location: Portland, OR USA
Contact:
Thomas F. G

Você já respondeu a dúvida de alguém hoje?
https://glufke.net/oracle/search.php?search_id=unanswered

An idea is to do the following:
puts an exception in this insert.
Within this exception, you do the same insert for a table with the fields much larger than normal ...

Example:
If the field is Varchar2 (15), creates a table with this VARCHAR2 (200) field, etc.

ie, if error, exception will insert on this other table. After inserting, you gives a raise and for the application. Then you can take a calm what is being inserted ...

There must be better ways ... But I think so you were going to be able to know what is being inserted ...

If you did not want to insert, put a dbms_output for each field on the exception ... hence the SQL * plus your routine ..: - /
thiago.sousa
Rank: Programador Júnior
Rank: Programador Júnior
Posts: 28
Joined: Fri, 09 Dec 2005 9:17 am
Location: Itajai-SC
_______________________________________
Thiago Antonio
SCJP - Sun Certified Java Programer
SCJA - Sun Certified Java Associate

I imagined the following.
some way to do this in a generic way.
Because this happens routinely, the programmers end up forgetting to limit the fields and I get in this impasse.

I wish I did not have to move on their routines, I would like to do everything in the bank, in a way that can be dynamic.
ruevers
Rank: DBA Sênior
Rank: DBA Sênior
Posts: 324
Joined: Fri, 02 Jun 2006 1:48 pm
Location: sp
Contact:

It generates a trace of the guy's session, then just look there = :-)
Post Reply
  • Information
  • Who is online

    Users browsing this forum: No registered users and 1 guest