'Value too large for defined data type' error while running flexanlg

While trying to run flexanlg to analyze my access log file I have received the following error:
Could not open specified log file 'access': Value too large for defined data type
The command I was running is
${iPLANET_HOME}/extras/flexanlg/flexanlg -F -x -n "Web Server" -i ${TMP_WEB_FILE} -o ${OUT_WEB_FILE} -c hnrfeuok -t s5m5h5 -l h30c+5 -p ctl
Which should generate a html report of the web statistics
The file has approx 7 Million entries and is 2.3G in size
Ideas?

I've concatenated several files together from my web servers as I wanted a single report, several reports based on individual web servers is no use.
I'm running iWS 6.1 SP6 on Solaris 10, on a zoned T2000
SunOS 10 Generic_118833-23 sun4v sparc SUNW,Sun-Fire-T200
Cheers
Chris

Similar Messages

Alter mount database failing: Intel SVR4 UNIX Error: 79: Value too large for defined data type

Hi there,
I am having a kind of weird issues with my oracle enterprise db which was perfectly working since 2009. After having had some trouble with my network switch (replaced the switch) the all network came back and all subnet devices are functioning perfect.
This is an NFS for oracle db backup and the oracle is not starting in mount/alter etc.
Here the details of my server:
- SunOS 5.10 Generic_141445-09 i86pc i386 i86pc
- Oracle Database 10g Enterprise Edition Release 10.2.0.2.0
- 38TB disk space (plenty free)
- 4GB RAM
And when I attempt to start the db, here the logs:
Starting up ORACLE RDBMS Version: 10.2.0.2.0.
System parameters with non-default values:
processes                = 150
shared_pool_size         = 209715200
control_files            = /opt/oracle/oradata/CATL/control01.ctl, /opt/oracle/oradata/CATL/control02.ctl, /opt/oracle/oradata/CATL/control03.ctl
db_cache_size            = 104857600
compatible               = 10.2.0
log_archive_dest         = /opt/oracle/oradata/CATL/archive
log_buffer               = 2867200
db_files                 = 80
db_file_multiblock_read_count= 32
undo_management          = AUTO
global_names             = TRUE
instance_name            = CATL
parallel_max_servers     = 5
background_dump_dest     = /opt/oracle/admin/CATL/bdump
user_dump_dest           = /opt/oracle/admin/CATL/udump
max_dump_file_size       = 10240
core_dump_dest           = /opt/oracle/admin/CATL/cdump
db_name                  = CATL
open_cursors             = 300
PMON started with pid=2, OS id=10751
PSP0 started with pid=3, OS id=10753
MMAN started with pid=4, OS id=10755
DBW0 started with pid=5, OS id=10757
LGWR started with pid=6, OS id=10759
CKPT started with pid=7, OS id=10761
SMON started with pid=8, OS id=10763
RECO started with pid=9, OS id=10765
MMON started with pid=10, OS id=10767
MMNL started with pid=11, OS id=10769
Thu Nov 28 05:49:02 2013
ALTER DATABASE   MOUNT
Thu Nov 28 05:49:02 2013
ORA-00202: control file: '/opt/oracle/oradata/CATL/control01.ctl'
ORA-27037: unable to obtain file status
Intel SVR4 UNIX Error: 79: Value too large for defined data type
Additional information: 45
Trying to start db without mount it starts without issues:
SQL> startup nomount
ORACLE instance started.
Total System Global Area 343932928 bytes
Fixed Size                  1280132 bytes
Variable Size             234882940 bytes
Database Buffers          104857600 bytes
Redo Buffers                2912256 bytes
SQL>
But when I try to mount or alter db:
SQL> alter database mount;
alter database mount
ERROR at line 1:
ORA-00205: error in identifying control file, check alert log for more info
SQL>
From the logs again:
alter database mount
Thu Nov 28 06:00:20 2013
ORA-00202: control file: '/opt/oracle/oradata/CATL/control01.ctl'
ORA-27037: unable to obtain file status
Intel SVR4 UNIX Error: 79: Value too large for defined data type
Additional information: 45
Thu Nov 28 06:00:20 2013
ORA-205 signalled during: alter database mount
We have already checked in everywhere in the system, got oracle support as well without success. The control files are in the place and checked with strings, they are correct.
Can somebody give a clue please?
Maybe somebody had similar issue here....
Thanks in advance.

Did the touch to update the date, but no joy either....
These are further logs, so maybe can give a clue:
Wed Nov 20 05:58:27 2013
Errors in file /opt/oracle/admin/CATL/bdump/catl_j000_7304.trc:
ORA-12012: error on auto execute of job 5324
ORA-27468: "SYS.PURGE_LOG" is locked by another process
Sun Nov 24 20:13:40 2013
Starting ORACLE instance (normal)
control_files = /opt/oracle/oradata/CATL/control01.ctl, /opt/oracle/oradata/CATL/control02.ctl, /opt/oracle/oradata/CATL/control03.ctl
Sun Nov 24 20:15:42 2013
alter database mount
Sun Nov 24 20:15:42 2013
ORA-00202: control file: '/opt/oracle/oradata/CATL/control01.ctl'
ORA-27037: unable to obtain file status
Intel SVR4 UNIX Error: 79: Value too large for defined data type
Additional information: 45
Sun Nov 24 20:15:42 2013
ORA-205 signalled during: alter database mount

[SOLVED] Value too large for defined data type in Geany over Samba

Some months ago Geany started to output an error whith every attempt to open a file mounted in smbfs/cifs.
The error was:
Value too large for defined data type
Now the error is solved thanks to a french user, Pierre, on Ubuntu's Launchpad:
https://bugs.launchpad.net/ubuntu/+bug/ … comments/5
The solution is to add this options to your smbfs/cifs mount options (in /etc/fstab for example):
,nounix,noserverino
It works on Arch Linux up-to-date (2009-12-02)
I've writed it on the ArchWiki too: http://wiki.archlinux.org/index.php/Sam … leshooting

An update on the original bug. This is the direct link to launchpad bug 455122:
https://bugs.launchpad.net/ubuntu/+sour … bug/455122

OPMN Failed to start: Value too large for defined data type

Hello,
Just restared opmn and it failed to start with folloiwing errors in opmn.log:
OPMN worker process exited with status 4. Restarting
/opt/oracle/product/IAS10g/opmn/logs/OC4J~home~default_island~1: Value too large for defined data type
Does anyone have ideas about cause of this error? Server normally worked more than 6 month with periodic restarts...

Hi,
You could get error messages like that if you try to access a file larger than 2GB on a 32-bit OS. Do you have HUGE log files?
Regards,
Mathias

Mkisofs: Value too large for defined data type too large

Hi:
Does anyone meet the problem when use mkisofs command?
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Warning: creating filesystem that does not conform to ISO-9660.
mkisofs 2.01 (sparc-sun-solaris2.10)
Scanning iso
Scanning iso/rac_stage1
mkisofs: Value too large for defined data type. File iso/rac_stage3/Server.tar.gz is too large - ignoring
Using RAC_S000 for /rac_stage3 (rac_stage2)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Thanks!

An update on the original bug. This is the direct link to launchpad bug 455122:
https://bugs.launchpad.net/ubuntu/+sour … bug/455122

Value too large for defined data type

Hi,
i have a Sun Netra t1 105. Sometimes when I try to start top, i get the error message in $SUBJECT.
Does someone have a hint?
Thanks in advance
Tosh42

I've concatenated several files together from my web servers as I wanted a single report, several reports based on individual web servers is no use.
I'm running iWS 6.1 SP6 on Solaris 10, on a zoned T2000
SunOS 10 Generic_118833-23 sun4v sparc SUNW,Sun-Fire-T200
Cheers
Chris

(gdb)procfs: target_wait (wait_for_stop) : Value too large for defined ...

When trying to debug a cpp program using dbx within the solaris9 I get the following error.
How Can I fix this error? Please give me a help.
Thanks.
[UC]gdb nreUC100
GNU gdb 6.0
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "sparc-sun-solaris2.9"...
(gdb) l
130 * 1 -
131 * 99 -
132 * DB Table : N/A
133 ******************************************************************************/
134 int
135 main(int argc, char* argv[])
136 {
137 struct sigaction stSig;
138
139 stSig.sa_handler = sigHandler;
(gdb)
140 stSig.sa_flags = 0;
141 (void) sigemptyset(&stSig.sa_mask);
142
143 sigaction(SIGSEGV, &stSig, 0);
144
145 if ((argc < 5) ||
146 (strlen(argv[1]) != NRATER_PKG_ID_LEN) ||
147 (strlen(argv[2]) != NRATER_SVC_ID_LEN) ||
148 (strlen(argv[3]) != NRATER_PROC_ID_LEN) ||
149 (isNumber(argv[4])))
(gdb)
150 {
151 Usage(argv[0]);
152
153 return NRATER_EXCEPT;
154 }
155
156 ST_PFNM_ARG stArg;
157 memset(&stArg, 0x00, sizeof(stArg));
158
159 memcpy(stArg.strPkgID_, argv[1], NRATER_PKG_ID_LEN);
(gdb) b 157
Breakpoint 1 at 0x1a668: file nreUC100.cpp, line 157.
(gdb) r 02 000001 000001 1
Starting program: /UC/nreUC100 02 000001 000001 1
couldn't set locale correctly
procfs: target_wait (wait_for_stop) line 3931, /proc/19793: Value too large for defined data type.
(gdb)

Sorry, there are not too many gdb experts that monitor
this forum. Assuming you are on Solaris, you can
use the truss command to see what gdb is doing.
First start gdb
% gdb
(gdb)
Then in another window, attach truss to it.
% pgrep gdb
12345
% truss -p 12345
The go back to gdb and run the program.
IS the line number in the gdb error a line number
in the gdb source code? Or is gdb complaining
about a location in your application source code?
If it's in your app, then looking at that line might
help you figure out what 's going on.
Otherwise, you can always download the gdb source
and grep for that error message and see what
makes it happen.
I found this similar problem when a user can't
debug a setuid program.
http://sources.redhat.com/ml/gdb-prs/2004-q1/msg00129.html
Here is another similar warning that I found with google.
http://www.omniorb-support.com/pipermail/omniorb-list/2005-May/026757.html
Perhaps you are debugging a 32-bit program with a 64-bit gdb or vice versa?

Var/adm/utmpx: value too large for defined datatype

Hi,
On a Solaris 10 machine I cannot use last command to view login history etc. It tells something like "/var/adm/utmpx: value too large for defined datatype".
The size of /var/adm/utmpx is about 2GB.
I tried renaming the file to utmpx.0 and create a new file using head utmpx.0 > utmpx but after that the last command does not show any output. The new utmpx file seems to be updating with new info though... as seen from file last modified time.
Is there a standard procedure to recreate a new utmpx file once it grows too largs?? I couldnt find much in man pages
Thanks in advance for any help

The easiest way is to cat /dev/null to utmpx - this will clear out the file to 0 bytes but leave it intact.
from the /var/adm/ directory:
cat /dev/null > /var/adm/utmpx
Some docs suggest going to single user mode to do this, or stopping the utmp service daemon first, but I'm not positive this is necessary. Perhaps someone has input on that aspect. I've always just sent /dev/null to utmpx and wtmpx without a problem.
BTW - I believe "last" works with wtmpx, and "who" works with utmpx.

Data Profiling - Value too large for column error

I am running a data profile which completes with errors. The error being reported is an ORA 12899 Value too large for column actual (41 maximum 40).
I have checked the actual data in the table and the maximum is only 40 characters.
Any ideas on how to solve this. Even though it completes no actual profile is done on the data due to the error.
OWB version 11.2.0.1
Log file below.
Job     Rows Selected     Rows Inserted     Rows Updated     Rows Deleted     Errors     Warnings     Start Time     Elapsed Time
Profile_1306385940099                                   2011-05-26 14:59:00.0     106
Data profiling operations complete.
Redundant column analysis for objects complete in 0 s.
Redundant column analysis for objects.
Referential analysis for objects complete in 0.405 s.
Referential analysis for objects.
Referential analysis initialization complete in 8.128 s.
Referential analysis initialization.
Data rule analysis for object TABLE_NAME complete in 0 s.
Data rule analysis for object TABLE_NAME
Functional dependency and unique key discovery for object TABLE_NAME complete in 0 s.
Functional dependency and unique key discovery for object TABLE_NAME
Domain analysis for object TABLE_NAME complete in 0.858 s.
Domain analysis for object TABLE_NAME
Pattern analysis for object TABLE_NAME complete in 0.202 s.
Pattern analysis for object TABLE_NAME
Aggregation and Data Type analysis for object TABLE_NAME complete in 9.236 s.
Aggregation and Data Type analysis for object TABLE_NAME
Functional dependency and unique key discovery for object TABLE_NAME complete in 0 s.
Functional dependency and unique key discovery for object TABLE_NAME
Domain analysis for object TABLE_NAME complete in 0.842 s.
Domain analysis for object TABLE_NAME
Pattern analysis for object TABLE_NAME complete in 0.187 s.
Pattern analysis for object TABLE_NAME
Aggregation and Data Type analysis for object TABLE_NAME complete in 9.501 s.
Aggregation and Data Type analysis for object TABLE_NAME
Functional dependency and unique key discovery for object TABLE_NAME complete in 0 s.
Functional dependency and unique key discovery for object TABLE_NAME
Domain analysis for object TABLE_NAME complete in 0.717 s.
Domain analysis for object TABLE_NAME
Pattern analysis for object TABLE_NAME complete in 0.156 s.
Pattern analysis for object TABLE_NAME
Aggregation and Data Type analysis for object TABLE_NAME complete in 9.906 s.
Aggregation and Data Type analysis for object TABLE_NAME
Functional dependency and unique key discovery for object TABLE_NAME complete in 0 s.
Functional dependency and unique key discovery for object TABLE_NAME
Domain analysis for object TABLE_NAME complete in 0.827 s.
Domain analysis for object TABLE_NAME
Pattern analysis for object TABLE_NAME complete in 0.187 s.
Pattern analysis for object TABLE_NAME
Aggregation and Data Type analysis for object TABLE_NAME complete in 9.172 s.
Aggregation and Data Type analysis for object TABLE_NAME
Functional dependency and unique key discovery for object TABLE_NAME complete in 0 s.
Functional dependency and unique key discovery for object TABLE_NAME
Domain analysis for object TABLE_NAME complete in 0.889 s.
Domain analysis for object TABLE_NAME
Pattern analysis for object TABLE_NAME complete in 0.202 s.
Pattern analysis for object TABLE_NAME
Aggregation and Data Type analysis for object TABLE_NAME complete in 9.313 s.
Aggregation and Data Type analysis for object TABLE_NAME
Execute data prepare map for object TABLE_NAME complete in 9.267 s.
Execute data prepare map for object TABLE_NAME
Execute data prepare map for object TABLE_NAME complete in 10.187 s.
Execute data prepare map for object TABLE_NAME
Execute data prepare map for object TABLE_NAME complete in 8.019 s.
Execute data prepare map for object TABLE_NAME
Execute data prepare map for object TABLE_NAME complete in 5.507 s.
Execute data prepare map for object TABLE_NAME
Execute data prepare map for object TABLE_NAME complete in 10.857 s.
Execute data prepare map for object TABLE_NAME
Parameters
O82647310CF4D425C8AED9AAE_MAP_ProfileLoader                              1     2011-05-26 14:59:00.0     11
ORA-12899: value too large for column "SCHEMA"."O90239B0C1105447EB6495C903678"."ITEM_NAME_1" (actual: 41, maximum: 40)
Parameters
O68A16A57F2054A13B8761BDC_MAP_ProfileLoader                              1     2011-05-26 14:59:11.0     5
ORA-12899: value too large for column "SCHEMA"."O0D9332A164E649F3B4D05D045521"."ITEM_NAME_1" (actual: 41, maximum: 40)
Parameters
O78AD6B482FC44D8BB7AF8357_MAP_ProfileLoader                              1     2011-05-26 14:59:16.0     9
ORA-12899: value too large for column "SCHEMA"."OBF77A8BA8E6847B8AAE4522F98D6"."ITEM_NAME_2" (actual: 41, maximum: 40)
Parameters
OA79DF482D74847CF8EA05807_MAP_ProfileLoader                              1     2011-05-26 14:59:25.0     10
ORA-12899: value too large for column "SCHEMA"."OB0052CBCA5784DAD935F9FCF2E28"."ITEM_NAME_1" (actual: 41, maximum: 40)
Parameters
OFFE486BBDB884307B668F670_MAP_ProfileLoader                              1     2011-05-26 14:59:35.0     9
ORA-12899: value too large for column "SCHEMA"."O9943284818BB413E867F8DB57A5B"."ITEM_NAME_1" (actual: 42, maximum: 40)
Parameters

Found the answer. It was the database character set for multi byte character sets.

File_To_RT data truncation ODI error ORA-12899: value too large for colum

Hi,
Could you please provide me some idea so that I can truncate the source data grater than max length before inserting into target table.
Prtoblem details:-
For my scenario read data from source .txt file and insert the data into target table.suppose source file data length exceeds max col length of the target table.Then How will I truncate the data so that data migration will be successful and also can avoid the ODI error " ORA-12899: value too large for column".
Thanks
Anindya

Bhabani wrote:
In which step you are getting this error ? If its loading step then try increasing the length for that column from datastore and use substr in the mapping expression.Hi Bhabani,
You are right.It is for Loading SrcSet0 Load data.I have increased the column length for target table data store
and then apply the substring function but it results the same.
If you wanted to say to increase the length for source file data store then please tell me which length ?Physical length or
logical length?
Thanks
Anindya

Getting error ORA-01401: inserted value too large for column

Hello ,
I have Configured the scenario IDOC to JDBC .In the SXMB_MONI am getting the succes message .But in the Adapter Monitor am getting the error message as
ORA-01401: inserted value too large for column and the entries also not inserted in to the table.I hope this is because of the date format only.In Oracle table date field has defined in the format of '01-JAN-2005'.I am also passing the date field in the same format only for INVOICE_DATE and INVOICE_DUE_DATE.Please see the target structure .
<?xml version="1.0" encoding="UTF-8" ?>
- <ns:INVOICE_INFO_MT xmlns:ns="http://sap.com/xi/InvoiceIDoc_Test">
- <Statement>
- <INVOICE_INFO action="INSERT">
- <access>
<INVOICE_ID>0090000303</INVOICE_ID>
<INVOICE_DATE>01-Dec-2005</INVOICE_DATE>
<INVOICE_DUE_DATE>01-Jan-2005</INVOICE_DUE_DATE>
<ORDER_ID>0000000000011852</ORDER_ID>
<ORDER_LINE_NUM>000010</ORDER_LINE_NUM>
<INVOICE_TYPE>LR</INVOICE_TYPE>
<INVOICE_ORGINAL_AMT>10000</INVOICE_ORGINAL_AMT>
<INVOICE_OUTSTANDING_AMT>1000</INVOICE_OUTSTANDING_AMT>
<INTERNAL_USE_FLG>X</INTERNAL_USE_FLG>
<BILLTO>0004000012</BILLTO>
<SHIPTO>40000006</SHIPTO>
<STATUS_ID>O</STATUS_ID>
</access>
</INVOICE_INFO>
</Statement>
</ns:INVOICE_INFO_MT>
Please let me know what are all the possible solution to fix the error and to insert the entries in the table.
Thanks in Advance!

Hi muthu,
// inserted value too large for column
When your oracle insertion throws this error, it implies that some value that you are trying to insert into the table is larger than the allocated size.
Just check the format of your table and the respective size of each field on your oracle cleint by using the command,
DESCRIBE <tablename> .
and then verify it with the input. I dont think the problem is with the DATE format because if it is not a valid date format, you would have got on error like
String Literal does not match type
Hope this helps,
Regards,
Bhavesh

SQL Error: ORA-12899: value too large for column

Hi,
I'm trying to understand the above error. It occurs when we are migrating data from one oracle database to another:
Error report:
SQL Error: ORA-12899: value too large for column "USER_XYZ"."TAB_XYZ"."COL_XYZ" (actual: 10, maximum: 8)
12899. 00000 - "value too large for column %s (actual: %s, maximum: %s)"
*Cause:    An attempt was made to insert or update a column with a value
which is too wide for the width of the destination column.
The name of the column is given, along with the actual width
of the value, and the maximum allowed width of the column.
Note that widths are reported in characters if character length
semantics are in effect for the column, otherwise widths are
reported in bytes.
*Action:   Examine the SQL statement for correctness. Check source
and destination column data types.
Either make the destination column wider, or use a subset
of the source column (i.e. use substring).
The source database runs - Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
The target database runs - Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
The source and target table are identical and the column definitions are exactly the same. The column we get the error on is of CHAR(8). To migrate the data we use either a dblink or oracle datapump, both result in the same error. The data in the column is a fixed length string of 8 characters.
To resolve the error the column "COL_XYZ" gets widened by:
alter table TAB_XYZ modify (COL_XYZ varchar2(10));
-alter table TAB_XYZ succeeded.
We now move the data from the source into the target table without problem and then run:
select max(length(COL_XYZ)) from TAB_XYZ;
-8
So the maximal string length for this column is 8 characters. To reduce the column width back to its original 8, we then run:
alter table TAB_XYZ modify (COL_XYZ varchar2(8));
-Error report:
SQL Error: ORA-01441: cannot decrease column length because some value is too big
01441. 00000 - "cannot decrease column length because some value is too big"
*Cause:
*Action:
So we leave the column width at 10, but the curious thing is - once we have the data in the target table, we can then truncate the same table at source (ie. get rid of all the data) and move the data back in the original table (with COL_XYZ set at CHAR(8)) - without any issue.
My guess the error has something to do with the storage on the target database, but I would like to understand why. If anybody has an idea or suggestion what to look for - much appreciated.
Cheers.

843217 wrote:
Note that widths are reported in characters if character length
semantics are in effect for the column, otherwise widths are
reported in bytes.You are looking at character lengths vs byte lengths.
The data in the column is a fixed length string of 8 characters.
select max(length(COL_XYZ)) from TAB_XYZ;
-8
So the maximal string length for this column is 8 characters. To reduce the column width back to its original 8, we then run:
alter table TAB_XYZ modify (COL_XYZ varchar2(8));varchar2(8 byte) or varchar2(8 char)?
Use SQL Reference for datatype specification, length function, etc.
For more info, reference {forum:id=50} forum on the topic. And of course, the Globalization support guide.

Error on reverse on XML: value too large for column

Hi All,
I am trying to reverse engineer while creating the data model on XML technology.
My JDBC URL on data server reads this:
jdbc:snps:xml?d=../demo/abc/CustomerPartyEBO.xsd&s=MYEBO
I get an error while doing the reverse.
java.sql.SQLException: ORA-12899: value too large for column "PINW"."SNP_REV_KEY_COL"."KEY_NAME" (actual: 102, maximum: 100)
After doing some check through selective reverse, found that this is happening only for few tables, whose names are quite longer.
Tried setting the "maximum column name length" and "maximum table name length" to 120 and even higher values on XML technology from Topology Manager. No luck there.
Thanks in advance for any help here.

That is not the place to change.
The error states that the SNP_REV_KEY_COL.KEY_NAME in the Work Repository schema PINW has maximum length defined to be 100.
I donot know if Oracle will support this change but you will have to make a change to the Work Repository table SNP_REV_KEY_COL and change the column lengths as a workaround.

Update trigger fails with value too large for column error on timestamp

Hello there,
I've got a problem with several update triggers. I've several triggers monitoring a set of tables.
Upon each update the updated data is compared with the current values in the table columns.
If different values are detected the update timestamp is set with the current_timestamp. That
way we have a timestamp that reflects real changes in relevant data. I attached an example for
that kind of trigger below. The triggers on each monitored table only differ in the columns that
are compared.
CREATE OR REPLACE TRIGGER T_ava01_obj_cont
BEFORE UPDATE on ava01_obj_cont
FOR EACH ROW
DECLARE
v_changed boolean := false;
BEGIN
IF NOT v_changed THEN
    v_changed := (:old.cr_adv_id IS NULL AND :new.cr_adv_id IS NOT NULL) OR
                 (:old.cr_adv_id IS NOT NULL AND :new.cr_adv_id IS NULL)OR
                 (:old.cr_adv_id IS NOT NULL AND :new.cr_adv_id IS NOT NULL AND :old.cr_adv_id != :new.cr_adv_id);
END IF;
IF NOT v_changed THEN
    v_changed := (:old.is_euzins_relevant IS NULL AND :new.is_euzins_relevant IS NOT NULL) OR
                 (:old.is_euzins_relevant IS NOT NULL AND :new.is_euzins_relevant IS NULL)OR
                 (:old.is_euzins_relevant IS NOT NULL AND :new.is_euzins_relevant IS NOT NULL AND :old.is_euzins_relevant != :new.is_euzins_relevant);
END IF;
[.. more values being compared ..]
    IF v_changed THEN
    :new.update_ts := current_timestamp;
END IF;
END T_ava01_obj_cont;Really relevant is the statement
:new.update_ts := current_timestamp;So far so good. The problem is, it works the most of time. Only sometimes it fails with the following error:
SQL state [72000]; error code [12899]; ORA-12899: value too large for column "LGT_CLASS_AVALOQ"."AVA01_OBJ_CONT"."UPDATE_TS"
(actual: 28, maximum: 11)
I can't see how the value systimestamp or current_timestamp (I tried both) should be too large for
a column defined as TIMESTAMP(6). We've got tables where more updates occur then elsewhere.
Thats where the most of the errors pop up. Other tables with fewer updates show errors only
sporadicly or even never. I can't see a kind of error pattern. It's like that every 10.000th update
or less failes.
I was desperate enough to try some language dependend transformation like
IF v_changed THEN
    l_update_date := systimestamp || '';
    select value into l_timestamp_format from nls_database_parameters where parameter = 'NLS_TIMESTAMP_TZ_FORMAT';
    :new.update_ts := to_timestamp_tz(l_update_date, l_timestamp_format);
END IF;to be sure the format is right. It didn't change a thing.
We are using Oracle Version 10.2.0.4.0 Production.
Did anyone encounter that kind of behaviour and solve it? I'm now pretty certain that it has to
be an oracle bug. What is the forum's opinion on that? Would you suggest to file a bug report?
Thanks in advance for your help.
Kind regards
Jan

Could you please edit your post and use formatting and tags. This is pretty much unreadable and the forum boogered up some of your code.
Instructions are here: http://forums.oracle.com/forums/help.jspa

EXEC SQL Error: ORA-01401: Inserted value too large for column

Getting this SQL Error: ORA-01401: Inserted value too large for column..on an EXEC SQL Insert statement when writing to an
external Oracle DB from SAP.
On further analysis..it appears that this happens to the fields..when the string length matches the field length.
Example: Plant field is defined as char(4) on the SAP side and it is a Varchar2(4) on the Oracle side.
When a value like '1015' is passed thru a variable in the insert statement then this ORA-01401 error pops up.
No error:
   - if the value '1015' is passed directly in the insert statement to the external table (or)
   - when a value with 3 chars or less(like the first three chars..101) is passed thru a variable defined as 'Plant(4) type c'.
   - when using EXEC sql within SAP
   - when reading from the external db table
This was working ok until the Oracle Patch P9147110 was installed recently.
Any suggestions !

Hello Dvas,
what's the characterset of your external database?
What's the column definition in your external database (byte or character based)?
If you use a characeterset like UTF8 it is possible, that one character needs more than one byte and then you will run into such kind of issues if the definition is too small.
Regards
Stefan

'Value too large for defined data type' error while running flexanlg

Similar Messages

Maybe you are looking for