Dump with ORA-01438: value larger than specified prec
Hello All,
I am getting a dump in production with the above said error and the ST22 gives me further analysis that
"If the error occurred in Open SQL, there is probably an inconsistency
between the NAMETAB and the ABAP/4 Dictionary.
Compare the length specifications of the fields in the NAMETAB with
those in the ABAP/4 Dictionary and contact someone who is able to
perform a consistency check and eliminate the problem.
In most cases, this person will be your SAP consultant.
Please make a note of the actions and input which caused the error.
Please make a note of the actions and input which caused the error.
To resolve the problem, contact your
SAP system administrator.
Choose "Print" for a hard coopy of the termination message. You can
display and adminster short dump messages using Transaction ST22.
Error analysis
The problem has arisen because, within the database interface,
one of the data buffers made available for the INSERT (UPDATE)
is longer than the maximum defined in the database.
On the other hand, it may be that the length in the NAMETAB
does not match the maximum length defined in the database.
(In this case, the length in the NAMETAB is longer.) "
First time it gave me one record so I dropped that record and again executed the program but next time it gave me other record.
So I am not sure it is related to data error or database error. I can not debug the program in production and dev also as it is difficult to repeat the data in dev.
Any clues on this ?
Thanks in advance
Sameer
Looks like a precision error:
ORA-01438: value larger than specified precision allowed for this column
Cause: When inserting or updating records, a numeric value was entered that exceeded the precision defined for the column.
Action: Enter a value that complies with the numeric column's precision, or use the MODIFY option with the ALTER TABLE command to expand the precision.
Rob
Similar Messages
-
INI: XOQ-01600: OLAP DML Error "ORA-01438: value larger than specified prec
I have created a Time dimension in AWM 11.1.0.7.0B.
I have added two Hierarchies to it. One Hierarchy has All Years, Year, Week, day. The second hierarchy has All Years, Year, Quarter.
When I maintain the dimension, the following error occurs:
An error has occurred on the server
Error class: Express Failure
Server error descriptions:
INI: Error creating a definition manager, Generic at TxsOqConnection::generic<BuildProcess>
INI: XOQ-01600: OLAP DML Error "ORA-01438: value larger than specified precision allowed for this column
" while executing DML "SYS.AWXML!R11_LOAD_DIM('TIME.ALL_GREGORIAN_YEARS.LEVEL' SYS.AWXML!___R11_LONG_ARG_VALUE(SYS.AWXML!___R11_LONG_ARG_DIM 1) 'TIME.END_DATE.ATTRIBUTE' 'TIME.TIME_SPAN.ATTRIBUTE' 'TIME.LONG_DESCRIPTION.ATTRIBUTE' 'TIME.SHORT_DESCRIPTION.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_END_DATE.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_TIME_SPA.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_LONG_DES.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_SHORT_DE.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_TIME_SPA1.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_TIME_SPA2.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_TIME_SPA3.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_LONG_DES1.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_SHORT_DE1.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_TIME_SPA4.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_LONG_DES2.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_SHORT_DE2.ATTRIBUTE' 'TIME.GREGORIAN_QUARTER_END_DATE.ATTRIBUTE' 'TIME.GREGORIAN_QUARTER_TIME_SPAN.ATTRIBUTE' 'TIME.GREGORIAN_QUAOLAP DML Error "%(1)s" while executing DML "%(2)s", Generic at TxsOqStdFormCommand::execute
at oracle.olapi.data.source.DataProvider.callGeneric(Unknown Source)
at oracle.olapi.data.source.DataProvider.callGeneric(Unknown Source)
at oracle.olapi.data.source.DataProvider.executeBuild(Unknown Source)
at oracle.olap.awm.wizard.awbuild.UBuildWizardHelper$1.construct(Unknown Source)
at oracle.olap.awm.ui.SwingWorker$2.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)The most likely explanation is that you have a numeric attribute whose data type precision is less than that of the column it is mapped to. For example if you had an attribute with data type NUMBER(2) and you mapped it to a column with data type NUMBER(5), then you could get this error on load. Note that some of the attributes may not be visible in AWM. The offending SQL statement should be in the OUTPUT column of the CUBE_BUILD_LOG, but you may be able to fix this by just describing the view associated with the dimension. For example, here is the description of a TIME view created in 11.2..
Name Null? Type
DIM_KEY VARCHAR2(60)
LEVEL_NAME VARCHAR2(30)
MEMBER_TYPE VARCHAR2(1)
DIM_ORDER NUMBER
END_DATE DATE
TIME_SPAN NUMBER
LONG_DESCRIPTION VARCHAR2(60 CHAR)
SHORT_DESCRIPTION VARCHAR2(60 CHAR)
MONTH_END_DATE DATE
MONTH_TIME_SPAN NUMBER(5)
MONTH_LONG_DESCRIPTION VARCHAR2(60 CHAR)
MONTH_SHORT_DESCRIPTION VARCHAR2(60 CHAR)
FISCAL_QUARTER_END_DATE DATE
FISCAL_QUARTER_TIME_SPAN NUMBER(5)
FISCAL_QUARTER_LONG_DESC VARCHAR2(60 CHAR)
FISCAL_QUARTER_SHORT_DES VARCHAR2(60 CHAR)
FISCAL_YEAR_END_DATE DATE
FISCAL_YEAR_TIME_SPAN NUMBER(5)
FISCAL_YEAR_LONG_DESCRIP VARCHAR2(60 CHAR)
FISCAL_YEAR_SHORT_DESCRI VARCHAR2(60 CHAR)
CALENDAR_QUARTER_END_DAT DATE
CALENDAR_QUARTER_TIME_SP NUMBER(5)
CALENDAR_QUARTER_LONG_DE VARCHAR2(60 CHAR)
CALENDAR_QUARTER_SHORT_D VARCHAR2(60 CHAR)
CALENDAR_YEAR_END_DATE DATE
CALENDAR_YEAR_TIME_SPAN NUMBER(5)
CALENDAR_YEAR_LONG_DESCR VARCHAR2(60 CHAR)
CALENDAR_YEAR_SHORT_DESC VARCHAR2(60 CHAR)You can get the same information from user_cube_attributes
SQL> select attribute_name, data_precision from user_cube_attributes where dimension_name = 'TIME' and data_type = 'NUMBER';
ATTRIBUTE_NAME DATA_PRECISION
TIME_SPAN
MONTH_TIME_SPAN 5
FISCAL_QUARTER_TIME_SPAN 5
FISCAL_YEAR_TIME_SPAN 5
CALENDAR_QUARTER_TIME_SPAN 5
CALENDAR_YEAR_TIME_SPAN 5 -
CDC Failed with Error ORA-01438: value larger than specified precision
Hi,
I have created Asynchronous Distributed Change Data Capture Set-up as per the Guildines from Oracle.
Now My Change Set has become Invalid with error: ORA-01438: value larger than specified precision allowed for this column.
I Compared Change Table Structures with Source Table on Source Database and the structure is matching.
Now I am trying to Run below script:
Begin
dbms_cdc_publish.alter_change_set (Change_Set_name =><<Change Set Name>>,
recover_after_error => 'Y'
End;
I am getting the below error:
ORA-01438: value larger than specified precision allowed for this column
ORA-06512: at "SYS.DBMS_APPLY_ERROR", line 147
ORA-06512: at "SYS.DBMS_APPLY_ERROR", line 301
ORA-06512: at "SYS.DBMS_APPLY_ADM", line 490
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_CDC_PUBLISH", line 580
ORA-06512: at line 2
Still the error is existing, I couldn't find any issues with Change Table structure as it is in Line with Source Table Structure.
Can anyone please help me on this.
Staging Database details:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
TNS for Linux: Version 10.2.0.4.0 - Production
Source Database details:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
TNS for HPUX: Version 10.2.0.4.0 - Production
Also Can anyone let me know if it is possible to run CDC Set-up without DBA Privileges. i,e once the CDC Set-up is done, if we revoke the DBA Privilege will the Capture work properly. I know that for creating Change Table, Set and Source we require DBA Access. But once the set-up is done, do we really require DBA Privileges?
Thanks,
Shashi
Edited by: user8254952 on 09-Mar-2010 05:57
Edited by: user8254952 on 09-Mar-2010 06:00Hi Shashi,
As CDC is built on top of Oracle streams framework, for better responses you can post this ques under {forum:id=70} category.
"ORA-01438: value larger than specified precision allowed for this column" is usually encountered for NUMBER datatype columns. At what level did you check the datatypes? Please confirm if the precision(for NUMBER datatype) are also similar.
Please attach output for the following queries:
select error_message from dba_capture;
select error_number, error_message from dba_apply_error;Please re-validate the data types and then run the same API with remove_ddl = 'Y' option, like this:
exec DBMS_CDC_PUBLISH.ALTER_CHANGE_SET(change_set_name=>'CHANGE_SET_NAME' , recover_after_error=>'Y' , remove_ddl=>'Y');
Hope it helps!
Cheers,
AA -
Strange ORA-01438: value larger than specified precision...error
When i issue a query like
SELECT * FROM shp_dtls WHERE shp_locn='AL';
i get the error
ORA-01438: value larger than specified precision allowed for this columnWhy do i get an error like this for a SELECT query. Isn't this an INSERT related error?Normally this error happens on INSERT or UPDATE statement. There are 2 possibilities I think for it to happen on SELECT:
1) your FGA policy defined on select for this table that inserts data into wrong column (you should also be getting the violating procedure name in your error message);
2) wrong data has been inserted into table using OCI (in which case Oracle does not verify data correctness) or corrupted export file was impored. -
ORA-01438: value larger than specified precisio
Hi All,
I have a problem when using OCCI.
Oracle DB table A has one column, data type is NUMBER(10,0).
c++ code>>
Query from table
rs = stmt->executeQuery(...select * from A...);
long long n = (long long)(long double)rs->getNumber(1);
Insert to table-
Number nVal= Number((long double)n);
stmt->setNumber(1, nVal);
--Error: ORA-01438: value larger than specified precisio
How shall I do this insert(c++ data type is long long, DB column data type is NUMBER(10, 0))?
Message was edited by:
user591149Try to convert __int64 to std::string, then
Number num = 0;
num.fromText(env, strNumber, '999999999999');
and use this occi Number in your statement. -
ORA-01438: value larger than specified precision
I'm using a web application, and when try to insert a value larger than the column precision, I get the error ORA-01438.
I need to capture this error and show my own error when this happen, is any way to do this?
.You can write your own message using syntax like
PRAGMA EXCEPTION_INIT(exception_name, -Oracle_error_number);
Detailed information is here
http://download-west.oracle.com/docs/cd/B10501_01/appdev.920/a96624/07_errs.htm#707 -
Catching ORA-01438 live / value larger than specified precision allowed for
I've yet another question! Is it possible to catch the ORA-01438 error right away before the user submits the data?
I have a db column that is used to store numbers of length 3,0. When entering 4 digits, the ORA-01438 is raised.
The Apexlib doesn't work, since I have some conditional regions on that particular page!
Thanks for posting your thoughts and hints.
Regards,
SebSeb,
simply create a validation and check the length of user input.
brgds,
Peter
Blog: http://www.oracle-and-apex.com
ApexLib: http://apexlib.oracleapex.info
Work: http://www.click-click.at
Training: http://www.click-click.at/apex-4-0-workshops -
Problem with ORA-01438.
Hello, I work with Oracle Database XE and Application Express 3.0.1, I created a table named ORDERS:
CREATE TABLE "ALMACEN"."ORDERS"
( "COMPRA_COD" NUMBER(15,0) NOT NULL ENABLE,
"PROVEEDOR_COD" NUMBER(10,0) NOT NULL ENABLE,
"LOCAL_COD" CHAR(3 BYTE) NOT NULL ENABLE,
"FECHA_EMISION" DATE NOT NULL ENABLE,
"FECHA_VENCIMIENTO" DATE,
"DESCUENTO" NUMBER(14,2),
"VALOR_IVA" NUMBER(3,2),
"IVA_PAGADO" NUMBER(14,2),
"SUBTOTAL" NUMBER(14,2),
"TOTAL" NUMBER(14,2),
"OBSERVACION" VARCHAR2(2000 BYTE),
"TIPO_DOCUMENTO" CHAR(3 BYTE) NOT NULL ENABLE,
CONSTRAINT "COMPRAS_TIPO_DOCUMENTOS_CHK" CHECK (
tIPO_DOCUMENTO IN('FAC','NOV')
The insertions performed with the stored procedure:
Create or replace
PROCEDURE "SP_ADD_COMPRAS"
(P_COMPRA_COD IN COMPRAS.COMPRA_COD type%
, P_PROVEEDOR_COD IN COMPRAS.PROVEEDOR_COD type%
, P_LOCAL_COD IN COMPRAS.LOCAL_COD type%
, P_DATE_EMISION IN COMPRAS.FECHA_EMISION type%
, P_DATE_VENCIMIENTO IN COMPRAS.FECHA_VENCIMIENTO type%
, P_DESCUENTO IN COMPRAS.DESCUENTO type%
, P_VALOR_IVA IN COMPRAS.VALOR_IVA% default type 0
, P_IVA_PAGADO IN COMPRAS.IVA_PAGADO% default type 0
, P_SUBTOTAL IN COMPRAS.SUBTOTAL% default type 0
, P_TOTAL IN COMPRAS.TOTAL% default type 0
, P_OSERVACION IN COMPRAS.OBSERVACION type%
, In P_tipo_documento type COMPRAS.TIPO_DOCUMENTO%
) AS
BEGIN
Insert into almacen.COMPRAS
Values (P_COMPRA_COD, P_PROVEEDOR_COD, P_LOCAL_COD, P_DATE_EMISION,
P_DATE_VENCIMIENTO, P_DESCUENTO, P_VALOR_IVA, P_IVA_PAGADO,
P_SUBTOTAL, P_TOTAL, P_OSERVACION, p_tipo_documento);
Commit;
END SP_ADD_COMPRAS;
In Apex I refer to the procedure in a process, using as parameters the page elements to capture data.
DECLARE
N_desc compras.DESCUENTO% Type;
N_valor_iva compras.VALOR_IVA% Type;
N_subtotal compras.SUBTOTAL% Type;
N_total compras.TOTAL% Type;
BEGIN
N_desc: = nv (: P6_DESCUENTO);
N_valor_iva: = nv (: P6_VALOR_IVA);
N_subtotal: = nv (: P6_IVA_PAGADO);
N_total: = nv (: P6_TOTAL);
OWNER # #. SP_ADD_COMPRAS (
P_COMPRA_COD =>: P6_COMPRA_COD,
P_PROVEEDOR_COD =>: P6_PROVEEDOR_COD,
P_LOCAL_COD =>: P6_LOCAL_COD,
P_DATE_EMISION =>: P6_DATE_EMISION,
P_DATE_VENCIMIENTO =>: P6_DATE_VENCIMIENTO,
P_DESCUENTO => n_desc,
P_VALOR_IVA => 12,
P_IVA_PAGADO => n_valor_iva,
P_SUBTOTAL => n_subtotal ,
P_TOTAL => n_total,
P_OSERVACION =>: P6_OSERVACION,
P_TIPO_DOCUMENTO =>: P6_TIPO_DOCUMENTO);
END;
If I run the reports the error:ORA-01438: value greater than that enables the precision specified for this column
Roberto.I recommend that you debug your PL/SQL using SQL*Plus before trying to use it in your application. It takes Application Express out of the picture.
Scott -
Having trouble with my screen becoming larger than my phone supports. Can this be corrected without taking the phone to an Apple store?
The sign on screen (where the current time and the slide to unlock) and if I can get it to open, the next screen that show all the apps. Have been unable to get any further that that second screen. The screen contents appear to be about twice the size they should be. I have been able to "reset" the phone by turning it off, but the problem happening several times a day and now occasioanally the reset does not work. This just started happening about 3 days ago and is increasing in frequency. I have had this phone about 14 months.
-
Hey guys,
I started a new project. I set the file criteria for 4" wide 5" high, 300 resolution, CMYK.
When I save the file as a JPEG and export it for print the image is huge. I don't know what I'm doing wrong.
I check the settings again, after noticing they are huge, and the settings show it's still 4" wide 5" high, with 1200 pixels wide, 1500 pixels high.
What am I doing wrong? How can I avoid it on future projects, and how can I fix this project?
Thanks!!!Sorry for confusing you guys. I've been working 80 hours this week, and I guess my cognitive ability has been impaired, LOL. I'm sending the files via JPEG to a friend, who in turn is taking them to FedEx kinko's to have them printed out. When she opens the files for print she says the come out way too large. I'll send her TIFFs as well and see if that helps.
-
Query abort with ora-30036 after more than 20 hours and 180g of undo
Dear all,
A developper transmits me a query. It fails after more than 20 hours and an undotbs of 180g (i change undo-retention, size of undo tbs, without results). That query makes a lot of inserts. How can i rewrite it to be more performant (my database is on 10.2.0.3 and i can't change it).
here's the query :
set serveroutput on size unlimited
set pages 0
set trims on
set lines 1000
set feed off
set pagesize 50
set linesize 1000
set head off
set echo off
set verify off
set feedback off
WHENEVER SQLERROR EXIT SQL.SQLCODE
DECLARE
v_annee VARCHAR(4) := '2012';
v_dkm_id NUMBER := '108';
v_entretien NUMBER;
v_nb_feuilles_cr NUMBER := 0;
v_nb_etats_cr NUMBER := 0;
v_action_id NUMBER;
v_rm_id NUMBER;
v_personne_id NUMBER;
CURSOR c_evaluation IS
SELECT E.ID# AS E_ID, W.ID# AS WF_ID , E.NATURE_ECHELON AS ECHELON
FROM T_EVALUATION E
JOIN T_DKM_LOCALE L ON L.ID#=E.DKM_LOCALE_ID
JOIN T_WORKFLOW W ON (W.CODE=E.CODE_WORKFLOW_INITIAL AND W.ANNEE=v_annee )
WHERE L.DKM_NAT_ID=v_dkm_id;
r_evaluation c_evaluation%ROWTYPE;
BEGIN
SELECT ID#
INTO v_personne_id
FROM T_PERSONNE
WHERE ID_FONCTIONNEL = 'herve.collin';
dbms_output.put_line('===== MAJ evaluations / statut_harmo_shd =============');
dbms_output.put_line('===== Creation des feuilles ==========================');
SELECT ID# MOTIF_ID
INTO v_entretien
FROM T_REF_MOTIF_TENUE_ENTRETIEN
WHERE CODE='PLA';
OPEN c_evaluation;
LOOP
FETCH c_evaluation INTO r_evaluation;
EXIT WHEN c_evaluation%NOTFOUND;
IF r_evaluation.ECHELON = 'T'
THEN
SELECT ID#
INTO v_rm_id
FROM T_REF_REDUCMAJO
WHERE ANNEE = v_annee
AND CATEGORIE_GRADE = 'ET'
AND CODE = 'V1';
END IF;
IF r_evaluation.ECHELON = 'F' OR r_evaluation.ECHELON = 'V'
THEN
SELECT ID#
INTO v_rm_id
FROM T_REF_REDUCMAJO
WHERE ANNEE = v_annee
AND CATEGORIE_GRADE = 'FV'
AND CODE = 'R1';
END IF;
UPDATE T_EVALUATION
SET STATUT_HARMO_SHD = 'C' , REF_REDUCMAJO_PROP_SHD_ID = v_rm_id
WHERE DKM_LOCALE_ID IN ( SELECT ID# FROM T_DKM_LOCALE WHERE DKM_NAT_ID = v_dkm_id );
INSERT INTO T_FEUILLE(ID#, REF_MOTIF_TENUE_ENT_ID, EVALUATION_ID, WORKFLOW_ID)
VALUES (S_FEUILLE.NEXTVAL , v_entretien , r_evaluation.E_ID, r_evaluation.WF_ID);
v_nb_feuilles_cr := v_nb_feuilles_cr + 1;
END LOOP;
CLOSE c_evaluation;
dbms_output.put_line(' -> '||v_nb_feuilles_cr||' feuilles crees');
COMMIT;
END;
set serveroutput off
exit
What is the bester choice ? drop the indexes on the table before insert, start the insert without fetching the data in cursor ?
nb: sorry for my bad english
Best regards
Catherine Andre
@mail: [email protected]user4443606 wrote:
Thanks for your reply !
I'll try to grow the undo tbs space but i stay convinced that the problem is in the query.You can be convinced & wrong at the same time.
row by row INSERT is slow by slow.
It can be done as single INSERT; but that won't change the amount of UNDO that is required. -
Imacs come with a weaker graphics processor than specified by apple
Recently I bought an 24inch 2.8Ghz Imac which really works fine, but i discovered something rather strange when running some benchmark programs in windows XP. Apple advertises that the new 24inch Imacs come with ATI Radeon HD 2600 PRO graphics card, however benchmark software programs like 3dMark06 and Sisoftware Sandra recognise the video card as a ATI Mobility Radeon HD 2600XT; which is a notebook video card and thus weaker in performance.
The video card in the new imacs really are the weakest components, but now apple delivers an even weaker notebook videocard set while selling it as being a desktop videocard. I think it is hard to believe that they mistakenly put a wrong videochipset only in my imac so I was wondering if more people have noticed this and if yes, what action can we take??Hi,
What model does System Profiler claim the graphics card is?
however benchmark software programs like 3dMark06 and Sisoftware Sandra recognise the video card as a ATI Mobility Radeon HD 2600XT
How up to date are those benchmarking tools? If they're older than the graphics card in question, maybe they default to the closest they can find.
If it really is the wrong chipset, contact Apple directly via the Apple Store telephone number. -
Photoshop is consistently printing my images slightly larger than specified?
Photoshop CS6 on an iMac with OS 10.9.5 printing to an Epson 7900.
Epson say that its not a printer issue. Anyone know where I should be looking to resolve this issue?"Scale to fit media" should not be checked.
If your printer is printing properly on apps outside Photoshop, usually a reset of Preferences will fix it.
Hold down cmd-opt-shift and start Photoshop, agree to the reset. -
Error during Compression of an InfoCube (ORA-01438)
Hi all,
I am getting an error while trying to compress a request on an infocube,
I have attached the logs from the compression;
START cond CUBE BADR_C01 at 105833 on 20080606 maxreqid 2740 maxcnsid 0 refpoint update + NO NULL ELIM
The primary index on the E table was deleted
System error: ORA-01438: value larger than specified precision a
System error: llows for this column
System error: CONDENSE_FACTTABLE-5- ERROR:1438-
Collapse terminated: Data target BADR_C01, from to 2740
I have searched the SDN and OSS Notes for the ORA-1438 error but cannot find anything helpful.
Has anyone else come across this during a compression.
By the way, the compression on another cube works okay, just seems to be this cube and it is the first request I am trying to compress on this cube.
We are on BW 3.5 with an Oracle DB release 9.2.0.7.0.
Points awarded for any helpful or successful answers,
Thanks,
Shane.Hi Viki and Shambhu,
thanks for your quick replies.
Viki, on our TableSpaces we have the following percentage used, do you know what to check?
Table Space Percentage Used
PSAPBBP 82
PSAPBBP640 69
PSAPBBPUSR 15
PSAPTEMP 0
PSAPUNDO 60
SYSTEM 78
Shambhu, I have looked at the e table in SE11 and there is the following indexes ;
Index using Dimension BADR_C01P
Index using Dimension BADR_C01T
Index using Dimension BADR_C01U
Index using Dimension BADR_C011
Index using Dimension BADR_C012
Index using Dimension BADR_C013
Index using Dimension BADR_C014
Index using Dimension BADR_C015
Index using Dimension BADR_C016
Index using Dimension BADR_C017
Index using Dimension BADR_C018
Index using Dimension BADR_C019
Index using Dimension BADR_C01A
Index using Dimension BADR_C01B
Index using Dimension BADR_C01C
Non-Unique Index (Key Fields) for Table /BIC/EBADR
Is there anything else to check here???
Thanks for your help,
Shane. -
Repeated SOA ORA-01438 errors in the Logs
h1. ORA-01438: value larger than specified precision allowed for this column
We are using below versions and we keep getting error. And our Datasource goes to Suspended state.
h2. Versions
h3. Weblogic: 10.3.3.0
h3. Application Server 11g SOA Patchset 11.1.1.3.0
h3. Database: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
h3. MDS Metadata Services 11.1.1.2.0
h3. SOAINFRA SOA Infrastructure Services 11.1.1.3.0
h3. ORASDPM SDP Messaging 11.1.1.2.0
h2. Error
[2011-04-08T03:50:40.335+02:00] [soa3] [ERROR] [] [oracle.soa.bpel.engine.xml] [tid: orabpel.invoke.pool-4.thread-5] [userId: <anonymous>] [ecid: 0000Ivcetaf7a6GMyyYfMG1DYWXc000IJe,0:3:0x5f61edf:41:0x5f61c1f:23:0x5f61dc2:17:0x5f61e0a:14:0x5f61e41:5:0x5f62076:18:0x5f620ab:3:0x5f620b2:22:0x5f620c8:10:0x5f5e252:27:0x5f5e823:6:0x5f5e85b:4:3:100013816] [APP: soa-infra] [composite_name: OrderComposite] [component_name: Process] [component_instance_id: 755926] <XMLElement__CXPM::save> java.lang.NullPointerException [[
[2011-04-08T03:50:40.354+02:00] [soa3] [ERROR] [] [oracle.soa.bpel.system] [tid: orabpel.invoke.pool-4.thread-5] [userId: <anonymous>] [ecid: 0000Ivcetaf7a6GMyyYfMG1DYWXc000IJe,0:3:0x5f61edf:41:0x5f61c1f:23:0x5f61dc2:17:0x5f61e0a:14:0x5f61e41:5:0x5f62076:18:0x5f620ab:3:0x5f620b2:22:0x5f620c8:10:0x5f5e252:27:0x5f5e823:6:0x5f5e85b:4:3:100013816] [APP: soa-infra] [composite_name: Update] [component_name: UpdateProcess] [component_instance_id: 755867] <BaseCubeSessionBean::logError > Error while invoking bean "cube delivery": Exception not handled by the Collaxa Cube system.[[
an unhandled exception has been thrown in the Collaxa Cube systemr; exception reported is: "ORABPEL-00000
Exception not handled by the Collaxa Cube system.
an unhandled exception has been thrown in the Collaxa Cube systemr; exception reported is: *"java.sql.SQLDataException: ORA-01438: value larger than specified precision allowed for this column*
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:83)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:135)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:210)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:473)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:423)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1095)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:205)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1040)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1379)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3568)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3694)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1508)
at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:172)
at oracle.integration.platform.instance.activity.MessageProcessedActivity.performComponentCompletedWithFault(MessageProcessedActivity.java:133)
at oracle.integration.platform.instance.activity.MessageProcessedActivity.perform(MessageProcessedActivity.java:69)
at oracle.integration.platform.instance.store.DOStore.performImmediate(DOStore.java:504)
at oracle.integration.platform.instance.store.DOStore.perform(DOStore.java:497)
at oracle.integration.platform.instance.InstanceManagerImpl.componentInstanceCompletes(InstanceManagerImpl.java:1844)
at oracle.fabric.CubeFabricUtil.callInstanceTracking(CubeFabricUtil.java:1162)
at oracle.fabric.CubeFabricUtil.callComponentInstanceCompletes(CubeFabricUtil.java:1142)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:562)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:654)
at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:355)
at sun.reflect.GeneratedMethodAccessor1501.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:88)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:414)
at oracle.security.jps.wls.JpsWeblogicEjbInterceptor.runJaasMode(JpsWeblogicEjbInterceptor.java:61)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:106)
at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:106)
at sun.reflect.GeneratedMethodAccessor1421.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy253.handleInvoke(Unknown Source)
at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.handleInvoke(BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.java:462)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:35)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:141)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:82)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
An internal exception has not been properly handled by the server.
Set the logging level for all loggers to debug, and resubmit your request again. The server log should contain a more detailed exception report.
Exception: java.sql.SQLDataException: ORA-01438: value larger than specified precision allowed for this column
-----Thats a bug in SOA 11gR1.The problem is with the precision of the column COMPOSITE_INSTANCE.LIVE_INSTANCES currently defined to be NUMBER(3) which can at the most hold a value up to 999. As there is no explicit limitation on this column, the correct way to handle this is to increase the precision of this column to accommodate more instances.
Check the solution here, It worked for me
http://oraclefusionfacts.blogspot.com/2012/03/ora-01438value-larger-than-specified.html
Soumya
Maybe you are looking for
-
Unable to access Internet using a Mobile Network
Hello friends I recently updated my SE Xperia mini pro 17i (2011 model) to ICS, initially there were some issues and I had to re-update it to finally get authentic interface of ICS. Even after the successful update I am unable to use the mobile netwo
-
Hi I generated a report and I found that it is syntactically correct also execution is successful but when I executed the same program after 10 minutes a blank screen appears stating that [Abap Runtime Error Error Code - SQL error in the databa
-
Error when launching SCORM Compliant Content
When launching a piece of SCORM Content, OLM is kicking out an error that says "Unable to Locate the LMS's API Implementation. Communication with the LMS will not occur" We have verified the physical and virtual paths for the content server and the S
-
Your ideas for setting up an Arch-64 system with only OSS software?
-oops, wrong place- Last edited by Bob-Hur (2007-12-28 14:30:34)
-
When in Full Screen mode on Mozilla Firefox, the Minimize, Maximize, and Close buttons are extremely small. How do I change the size of these buttons?