CNS-9025 ORA - 01438

Good morning,
In a client device I have the following error:
CNS - 9025 An internal error has occurred.
ORA - 01 438: value specified precision Larger Than Allowed for this column.
I made a script to update the field.
In mSQL, I checked it is updated.
Returning to try to synchronize with Msync, still gives me the same error.
In the installation folder ORACE are the following files:
Userolerr.bin
olsynclog.txt
snd1001509.bin
I renamed these files, and tried to sync, but still gives me the same error.
Could anyone give me a solution?
Regards,

yep i think you are:P
let me give you an example
lets say i have a wince client(a pda)
1)i try to sync
2)olite creates the bin snd files and tries to send them (lets say 1snd.bin and 2snd.bin)
3)network is down (e.g. gprs is not working)
4)a network disconnected error comes out and sync fails
5)then you do some update inserts deletes and try tos ync again
6)oltie creates lets say 3snd.bin 4snd.bin or something like that
7)you try to sync but again network is down
8)then you make some more changes and try to sync again
9)olite creates 5snd.bin 6snd.bin etc
10)network is fine now so it sends all files to server 1snd.bin, 2snd.bin.....6snd.bin
11)it receives the new server side data in a file myuserolres
12 then in the processing it applies them
now people say do not delete under any circumstances the bin files and they are absolutely right
these files are olite created files. BUT if for some reason your client is frozen, you get an error ,you dont know what
to do, you dont have time, customer is angry etc etc then delete the files, free the sync , let it sync once with success,
open the msql, do an update sync, go in mobile manager error queue check there to resolve any issue. sync the handheld again (very like that it will force
a full refresh) and give the device back to the angry customer....something like that.
it is always a good idea to investigate why that happens, was the publication false, did you make some schema changes that were not downloaded ont he handheld correctly, create debug files etc etc.

Similar Messages

  • CNS-9025 An internal error occurred. ORA-00904: EXTRA_COL: invalid ID

    With our new version of Mobile Server (10.2.0.2) a lot of problems seem to have been solved. In older versions we didn't succeed in republishing. Meaning we had to drop the old version en publish a new version. Doing this meant we had to redo data subsetting for every user, which is a lengthy task. Besides it triggers full refresh for every user, that is a major one as well.
    In the new version a lot goes better, but still we are experiencing some problems (or challenges).
    Again the main issue is that in the course of time our application grows.
    Now we stumble into the simple issue:
    We want to add a column to our database.
    What we do is the following (as described by Oracle):
    - Add the column (EXTRA_COL) to our 'mother'database
    - Alter the snapshot definition for this column (add the column)
    - Republish...
    When I resynch the new column appears on my client, so far so good.
    However if I change something to the data on the client and I do a resynch I get:
    "CNS-9025 An internal error occurred. ORA-00904: EXTRA_COL: invalid ID.
    It seems as though 'internally' the column is not added everywhere it should be.
    For example the CEQ$table does not have the EXTRA_COL column.
    I'm quite sure that somebody else should encounter these problems as well as new views lead to data structure changes quite often.
    Anybody encountering this as well, and more important, somebody got a clue on what is going on?
    Thnx in advance.

    There is a bug with 10.2 where the re-publish of a item that has has ddl changes (like an extra column) does not always work correctly. It seems to be intermittent (at least in our environment) and the symptoms are
    alter base schema table
    re-publish snapshot (note if the snapshot definition is the standard 'select * from ...' you should not need to do anything apart from republishing)
    no errors reported in the re-publish
    however the new column has not been added to either CEQ$object OR CFM$WTGPI_nnnnn (the inqueue table for the object) - the missing column on the CFM$ table is the source of the error shown above in the posting as there is a mismatch when the data is uploaded
    dropping the publication item would fix the problem, but be aware if you have any users out there, when they synchronise any data being uploaded for a publication item that has been dropped and re-created will be LOST with no error being reported (in the sync history you will see a blank name in the upload section), due to the internal mapping having changed
    We have found that normally when this happens forcing a republish of the affected object by making a change to the selection logic (eg adding something like 'id is not null') and republishing again fixes the problem - as with a lot of mobile issues, fiddle with it enough and it will eventiually sort itself out

  • 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.

  • 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

  • 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

  • ORA-01438 occurred during "Explain plan"!

    Here is my query:
    SELECT
    rtrim(T1.col_id) Field0
    , count(T2.col_id) Field2
    , count(T3.col_id) Field3
    FROM SS.Table1 T1
    LEFT JOIN SS.Table2 T2
    ON (rtrim(T1.col_id) = rtrim(T2.col_id))
    LEFT JOIN SS.Table3 T3
    ON (rtrim(T1.col_id) = rtrim(T2.col_id))
    GROUP BY T1.col_id
    When I try to explain it plan I receive an error:
    "ORA-01438: value larger than specified precision allowed for this column"
    Can someone explain this?
    Thanks for the help in advance
    Regards,
    Beroetz

    Hi,
    Not sure how u r getting the explain plan...is it via a third party tool of SQLPLUS. Anyway by looking at the error it doesno tlook like there is a problem in explain plan.Did u run the script and check whether there is any error???There is a datatype error i guess.Please check ur script and the data in it.
    Regards
    Bharath

  • 11G Memory Issue - ORA-01438

    We have begun playing with OLAP for Oracle 11G. So far we have noticed this error popping up from time to time.
    ORA-01438: value larger than specified precision allowed for this column.
    We have generated this error when trying to return a large ammount of rows using the new select * from [CUBE]_View functionality and also every cube build I have built so far, only 2, has failed in the Analyze step after aggregation with this error.
    Anyone else notice this? Any thoughts? Any on 11G OLAP yet?

    Hi ZeroWing,
    Can you please log a TAR with Oracle Support so we can track this issue. I will research this and see if we have seen this during the beta and internal testing.
    Thanks
    Keith Laker
    Oracle EMEA Consulting
    BI Blog: http://oraclebi.blogspot.com/
    DM Blog: http://oracledmt.blogspot.com/
    BI on Oracle: http://www.oracle.com/bi/
    BI on OTN: http://www.oracle.com/technology/products/bi/
    BI Samples: http://www.oracle.com/technology/products/bi/samples/

  • 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

  • No database table exists for table ZTAB1 after ORA-01438

    Dear friends,
    We have a problem in our test system.
    One developer performed a transport which tried to change column from length 11 to 10 and after the transport, table is missing from database. We observed ABAP dumps DBIF_RSQL_SQL_ERROR with ORA-01438 which suggested us that there was some problem with field lenght change. After discussin, we have find out the culprate filed.
    But, with me now problem is Partially active table which Does not exist in the database.
    So now, what i should do to fix this problem.. Shuld i again increase filed length manually in test system and then try to perform SE14>Continue adjustment or what ?
    In SE14 : Analyze Adjustment provide this information :
    Seq of steps
       1 Initialization
       2 Dropping of indexes, renaming of original table
       3 No action
       4 Activation of transparent table
       5 Conversion of data to new table, deletion of renamed table
       6 Creation of sec. indexes
        Adjustment terminated in step 5
    Initial table                         Table type                 Status
    ZTAB1 Transparent                Renamed
    Renamed original table
    QCMZTAB1                        transparent                Existent
    Tgt.table
    ZTAB1 Transparent                Renamed
    thanks
    ashish

    I had tried to reactivate table.. but it will not work as I had Terminated conversion : Adjustment terminated in step 5.
    database object itself was not existent.. so consistency check is not helpful.
    We recognized the problem.. at present, we have DDIC object for table with a field length 10(new lenght), a QCMtable which contains original data with filed lenght 11(Old value) and a conversion table QCM8table which has filed lenght 10(new value).
    Now, in my case, original table had some Rows for that column lenght 11 and it was unable to transfer them to QCM8table.
    I had raised an OSS to SAP.
    thanks
    ashish

  • 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

  • Error FRM-40735 , ORA-01438

    Hi,
    In my form, for the Master-Details Data Block, the DML source is Procedure,
    For eg, the DetailsBlock name is "Files", and given below is the procedure to update that block. I have two doubts regarding to it,
    1. When user click Save button , i want to execute this procedure for all the records, now it is updating only one row, because of dmlset(1) (how should i do loop, I am new baby).
    2. Insert into TableA query is not executing, i am getting the error ORA -01438
    Scenario is :
    The datas are loaded into block from TableA and TableB.If the value of the column VALIDREJECTION is "InValid" then that row shoube be updated in the TableA, if it is not in TableA, then it should be inserted to TableA. That is TableB contains all records(both Valid & InValid) , but TableA contains only records with VALIDREJECTION ='InValid"
    My Procedure is :
    procedure filesUpdate(dmlset in out disputeFiles_tab) is
    cursor c_files is
    select FILEID
    from TableA
    where FILEID=dmlset(1).FILEID;
    tempout TableA.fileid%type;
    begin
    if dmlset(1).VALIDREJECTION='Valid' then
         DELETE FROM TABLEA WHERE FILEID=dmlset(1).FILEID;
    else
    --if Valid changed to InValid and updated, then it should be inserted
    open c_files;
    fetch c_files into tempout;
    IF c_files%NOTFOUND then
    insert into TableA(FILEID,VALIDREJECTION,USERID)
    values(dmlset(1).FILEID,dmlset(1).VALIDREJECTION,
    dmlset(1).USERID);
    ELSE
    update TableA
    set FILEID=dmlset(1).FILEID,
    VALIDREJECTION=dmlset(1).VALIDREJECTION,
    USERID=dmlset(1).USERID,
    where FILEID=dmlset(1).FILEID;
    END IF;
    close c_files;
    end if;
    end;
    Thanks in Advance ,
    bye bye

    Hi,
    From oracle error documentation...
    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.
    May be you are trying to enter CHAR value to NUMBER field.
    Check it out!

  • 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.

  • 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,
    Seb

    Seb,
    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

  • 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

  • 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:
    user591149

    Try to convert __int64 to std::string, then
    Number num = 0;
    num.fromText(env, strNumber, '999999999999');
    and use this occi Number in your statement.

Maybe you are looking for