Numeric overflow with DBMS_CDC_PUBLISH.CREATE_CHANGE_TABLE

Hello all-
I'm running Oracle 9i on WinXP sp. 2.
I'm trying to create a CDC table with the standard SYS package and am getting a numeric overflow error. The code I'm attempting to execute is this:
BEGIN
sys.dbms_cdc_publish.create_change_table(
OWNER => 'CDC_USER',
CHANGE_TABLE_NAME => 'PA_BUDGET_ENTRY_METHODS',
CHANGE_SET_NAME => 'SYNC_SET',
SOURCE_SCHEMA => 'PA',
SOURCE_TABLE => 'PA_BUDGET_ENTRY_METHODS',
COLUMN_TYPE_LIST => 'BUDGET_ENTRY_METHOD_CODE VARCHAR2(30)',
CAPTURE_VALUES => 'NEW',
RS_ID => 'N',
ROW_ID => 'Y',
USER_ID => 'Y',
TIMESTAMP => 'Y',
OBJECT_ID => 'N',
SOURCE_COLMAP => 'N',
TARGET_COLMAP => 'N',
OPTIONS_STRING => NULL);
END;
The error I'm getting is this:
ORA-01426: numeric overflow
ORA-06512: at "SYS.DBMS_CDC_PUBLISH", line 299
ORA-06512: at line 2
This happens every time, regardless of the source table i'm trying to capture changes for.
Clearly this is a normal exception (i.e., not only thrown in the CDC packages) so I'm having a hard time figuring out what it could be. Anyone out there familiar with CDC have any thoughts?
Thanks in advance,
James

I tried that but no luck yet, also tried put all in a single line, but the same error. It doesn't something tricky here, but actual problem with package. "ddl_markers" is new to 11g and not much documentation is available on that.
Also setting ddl_markers=N removed 3 columns from Publisher table, and the effect of it on Subscriber's view is still a gray area,

Similar Messages

Unexpected Numeric Overflow on empty tables when scanning with DMU

I have an instance of oracle running on an isolated network (oracle 11.2.0.3), on a Windows Server 2008 r2, x64 dell R705 server
When using the DMU to scan tables, I get the following error:
ORA-01426: numeric overflow
DBMS_DUMA_INTERNAL: line 8
DBMS_DUMA_INTERNAL: line 43
at line 1
I get his on multiple tables, but in each case, the table is empty (0 rows)
Can I safely ignore this? How do I get DMU to ignore the errors and continue?
Thanks in advance.

The fix for bug 8743409 is not included in the 11.2.0.1 release. Please check the DMU supported configurations. In order to use DMU on any versions of the database before 11.2.0.3, you need to apply a prerequisite server-side patch on one of the supported configurations. If you can upgrade to 11.2.0.3, there is no need to apply additional patches and the aforementioned fix is included.

ORA-01426: numeric overflow when creating job

Hello,
When executing the following script to create a job I get the error "ORA-01426: numeric overflow" . When I execute the same script on another database with same version and same configuration I do not get the error and the job is created.
Can anyone help me out solving this issue?
Script:
DECLARE
X NUMBER;
BEGIN
SYS.DBMS_JOB.SUBMIT
( job => X
,what => 'insert into dba.dba_logs values (''SGC'',''TRL03'',sysdate,null);
commit;
,next_date => to_date('07-11-2010 02:00:00','dd/mm/yyyy hh24:mi:ss')
,interval => 'NEXT_DAY(TRUNC(SYSDATE)+2/24,''SUNDAY'')'
,no_parse => FALSE
SYS.DBMS_OUTPUT.PUT_LINE('Job Number is: ' || to_char(x));
COMMIT;
END;
Database version: 11.2.0.1
OS: HPUX

We are planning to migrate to dbms_scheduler, but that's in the future. for now we have this error first to solve.
We also tried the following with dbms_scheduler and it gives the same error. The strange is that in another database with same version and same OS it works fine.
BEGIN
SYS.DBMS_SCHEDULER.CREATE_JOB
job_name => 'JOB_CLIENTES_IN'
,start_date => SYSTIMESTAMP
,repeat_interval => 'FREQ=MINUTELY;INTERVAL=10'
,end_date => NULL
,job_type => 'STORED_PROCEDURE'
,enabled => TRUE
,job_action => 'JOB_CLIENTES_FTP_IN'
,comments => 'Job que carrega os ficheiros de pre-aviso de cliente'
END;
ORA-01870: the intervals or datetimes are not mutually comparable
ORA-01426: numeric overflow
ORA-01426: numeric overflow
ORA-06512: at "SYS.DBMS_ISCHED", line 124
ORA-06512: at "SYS.DBMS_SCHEDULER", line 271
ORA-06512: at line 2
Edited by: cibernauta on Nov 4, 2010 12:48 PM

Numeric overflow error in aggregation level formula

The formula for Revenue/Quantity is giving me the following error:
Error: [314]: numeric overflow: search table error: [6944] AttributeEngine: overflow in numeric calculation;Error executing physical plan: exception 6944: AttributeEngine/Parallel/Aggregation.cpp:573 AttributeEngine: overflow in numeric calculation; $function$=read; $message$=unable to read measures RAOL01:_SYS_CE__popid_24_531C272BF80A349FE10000007F000002_558972en TEST_Revenue fixed16.12 ,in executor::Executor in cube: RAOL01:_SYS_CE_$REQUEST$_popid_24_531C272BF80A349FE10000007F000002_558973: calcEngine search on olapIndex failed.
I am aware that if Quantity is zero then we get this error, but I have already handled it and Quantity is never zero.
Both the measures are Decimal, any suggestions as to how to handle this?

My first guess you have reached the upper limit of the datatype on concerned column and the AttributeEngine is not capable now to handle the numeric overflow, hence throwing the error message.
Try converting it to higher datatypes like double, you can also try to do an workaround with datatype conversion functions like TO_DOUBLE before aggregation func.
If you are using something like sum("COL1") try using sum(TO_DOUBLE("COL1"))

Numeric Overflow error on NPer function

I am trying to use this NPer function and it's acting real weird. If I use the same numbers that my database fields hold, it works and when I switch to database fields it works fine one time and next time I try to refresh data, it gives me this "numeric overflow" error..
In Crystal help example, they shows that the payment has to be a negative number. So I am following that. If i switch it to the positive number, then it works bit it gives me negative # of months plus it's wrong number.
Not sure whats going on and would really appreciate any help...
Thanks
Raj

Please re-post if this is still an issue or purchase a case and have a dedicated support engineer work with your directly

Numeric overflow error using binary integer

Hi experts,
I am facing issue while solving a numeric overflow error. after analyzing we came to know that in the below code BINARY_INTEGER is causing the issue as input is exceeding its range. I tried to replace BINARY_INTEGER by varchar2(20) but its saying
"Error(580,20): PLS-00657: Implementation restriction: bulk SQL with associative arrays with VARCHAR2 key is not supported."
We need to remove this binary_integer. I dont know how to do this. Can anybody give some idea or what code change required here ? thanks in advance. Cheers.. Below is the code,
===================================================
   PROCEDURE UpdateCost_
      p_Cost_typ IN OUT NOCOPY CM_t,
   IS
      TYPE ObjektIdTab_itabt IS TABLE OF ObjektId_tabt INDEX BY BINARY_INTEGER;
      v_cost_IdTab_itab ObjektIdTab_itabt;
      v_CM_ID INTEGER := p_Cost_typ.costm.CM_ID;
      BEGIN
            SELECT CAST(MULTISET
                    (SELECT Costwps.CMKostId
                      FROM CM_Pos_r NRPos,
                            CMK_z_r costzpps,
                            CMG_Cost_v Costwps
                      WHERE NRPos.CM_ID = v_CM_ID
                        AND NRPos.SNRId_G = SNRCT.SNRPos.SNRId_G
                        AND costzpps.CM_ID = NRPos.CM_ID
                        AND costzpps.CMSNRPosId = NRPos.CMSNRPosId
                        AND costzpps.Kost_s = Kost.Costnzl.Kost_s
                        AND Costwps.CMKz_Id = costzpps.CMKz_Id
                        AND Costwps.TypCode NOT IN
                            (SELECT kw.TypCode
                               FROM TABLE(Kost.Kostwt_tab) kw
                    ) AS ObjektId_tabt )
              BULK COLLECT
              INTO v_cost_IdTab_itab
              FROM TABLE(p_Cost_typ.SNR_tab) SNRCT,
                   TABLE(SNRCT.Kost_tab) Kost
         FOR v_i IN 1 .. v_cost_IdTab_itab.COUNT LOOP
            FOR v_j IN 1 .. v_cost_IdTab_itab(v_i).COUNT LOOP
               DELETE FROM CMG_Cost_v WHERE CMKostId = v_cost_IdTab_itab(v_i)(v_j);
            END LOOP;
         END LOOP;
END;
===================================================

Thanks for your reply. I tried with INDEX by NUMBER. but oracle says its not a valid use of index by thing. and moreover I also tried with by removing INDEX BY clause. but in that case we are not at all getting any data in for loop. some people says to use extend clause. But again I am not sure How to do so. Can you please let me know code for this.
I know you are trying to help by you need to STOP telling us what problem you have and SHOW US. Saying 'Oracle says' is useless. Post EXACTLY what code you are using, the EXACT steps you are using to compile that code and the EXACT result that you are getting.
You also made no comment about the 'overflow' issue. A BINARY_INTEGER (PLS_INTEGER) has a very large range of values:
http://docs.oracle.com/cd/E11882_01/appdev.112/e25519/datatypes.htm#i10726
>
The PLS_INTEGER data type stores signed integers in the range -2,147,483,648 through 2,147,483,647, represented in 32 bits.
>
If you are trying to create a collection of more than 2 BILLION of anything you have a serious problem with either WHAT you are trying to do or HOW you are trying to do it. Your 'overflow' issue is more likely a symptom that you are really running out of memory. You should ALWAYS have a LIMIT clause when you do BULK COLLECT statements.
Also see this section in that doc: SIMPLE_INTEGER Subtype of PLS_INTEGER
You need to address your LIMIT issue first and then address any other issues that arise from actually executing the code.
Then see the section 'SELECT INTO Statement with BULK COLLECT Clause' in that doc
http://docs.oracle.com/cd/E11882_01/appdev.112/e25519/tuning.htm#BABEIACI
That section has an example that shows you do NOT need to use an INDEX BY clause to create collections as you are trying to do. So your not 'getting any data in for loop' is NOT related to the lack of that clause.
That example also shows you that you do NOT use 'extends' when doing BULK COLLECT. The bulk collection automatically extends the collection as needed to hold the entire results (assuming you don't run out of memory for 2 BILLION things).
Example 12-22 in that same doc shows the proper way to use a double loop and a BULK COLLECT with a LIMIT clause
http://docs.oracle.com/cd/E11882_01/appdev.112/e25519/tuning.htm#BABCCJCB
Here is very simple sample code you can use in the SCOTT schema to understand how the double loop and LIMIT clauses work together.
>
The FETCH does a BULK COLLECT of all data into 'v'. It will either get all the data or none if there isn't any.
The LOOP construct would be used when you have a LIMIT clause so that Oracle would 'loop' back to
get the next set of records. Run this example in the SCOTT schema and you will see how the LIMIT clause works.
I have 14 records in my EMP table.
DECLARE
CURSOR c1 IS (SELECT * FROM emp);
TYPE typ_tbl IS TABLE OF c1%rowtype;
v typ_tbl;
BEGIN
OPEN c1;
LOOP                                                 --Loop added
    FETCH c1 BULK COLLECT INTO v LIMIT 3; -- process 3 records at a time
        -- process the first 3 max records
       DBMS_OUTPUT.PUT_LINE('Processing ' || v.COUNT || ' records.');
        FOR i IN v.first..v.last LOOP
            DBMS_OUTPUT.PUT_LINE(v(i).empno);
        END LOOP;
    EXIT WHEN c1%NOTFOUND;
END LOOP;
DBMS_OUTPUT.PUT_LINE('All done');
END;
In the FOR loop you would do any processing of the nested table you want to do
and could use a FORALL to do an INSERT into another table.
>
I strongly suggest that you modify your code to work with a VERY SMALL set of data until it works properly. Then expand it to work with all of the data needed, preferably by using an appropriate LIMIT clause of no more than 1000.

ORA-01426: Numeric Overflow During Cube Build (Doc ID 1494869.1)

Our cube builds starting failing and we received this error after the cube log table sequence reached 32787.
After recreating the sequence the builds run successfully. This seems to be an unacceptable bug for an enterprise level product.
I have been unable to find a patch on the Oracle support site for it. Is a patch avaliable?
COMP_NAME
VERSION
OLAP Analytic Workspace
11.2.0.4.0
Oracle OLAP API
11.2.0.4.0
OLAP Catalog
11.2.0.4.0

I found what appears to be a related bug Bug 14627371 - ORA-01426: NUMERIC OVERFLOW DURING CUBE BUILD
. This bug is marked as fixed in 12.1 of the database.
I think that you may want to pursue this issue with support to see whether this can be back-ported ton 11.2.0.4.0.
--Ken Chin

Numeric overflow in data modeling tool

It only happens with one of my schemas but when I attempt to import it from the data dictionary it fails with a numeric overflow error:
2009-04-01 10:15:34,899 [Thread-2] ERROR AbstractDBMExtractionHandler - java.sql.SQLException: Numeric Overflow
2009-04-01 10:22:50,532 [Thread-3] ERROR AbstractDBMExtractionHandler - java.sql.SQLException: Numeric Overflow
2009-04-01 10:27:12,888 [Thread-4] ERROR AbstractDBMExtractionHandler - java.sql.SQLException: Numeric Overflow
Has anyone seen this before. I'm pretty sure it's only a subset of my tables as I can select a few here or there (out of 300) and it's fine.
Thanks,
Coburn

Hi Coburn,
we have this bug reported several times. Unfortunately we cannot reproduce it. The bug is related to something specific - I import my whole database (1800 tables, object types, object tables) and no problem. We want to sort it out but we cannot fix it if we cannot reproduce it. Any help is welcome.
Thanks in advance,
Philip

Cfstoredproc - Numeric Overflow Error - CF8

I recently upgraded to CF8 and have started having problems
with cfstoredproc. Here is the code:
<cfstoredproc datasource="#request.myDSN#"
procedure="dbo.p_online_password.get_account" >
<cfprocparam cfsqltype="cf_sql_varchar"
value="#attributes.email#" type="in" maxlength="50">
<cfprocparam cfsqltype="cf_sql_bigint" type="out"
variable="appvars.online_password_id">
<cfprocparam cfsqltype="cf_sql_varchar" type="in"
value="#attributes.password#" maxlength="30">
<cfprocparam cfsqltype="cf_sql_bigint" type="out"
variable="appvars.account_status">
<cfprocparam cfsqltype="cf_sql_varchar" type="out"
variable="appvars.loginmessage" maxlength="500">
<cfprocparam cfsqltype="cf_sql_bigint" type="out"
variable="appvars.personid">
</cfstoredproc>
Here is the logged dbcall:
spy(2007/12/27 15:29:58.361)>> Driver Name = Oracle
spy(2007/12/27 15:29:58.361)>> Driver Version = 3.60.26
(023731.010811.016225)
spy(2007/12/27 15:29:58.361)>> Database Name = Oracle
spy(2007/12/27 15:29:58.361)>> Database Version =
9.2.0.8.0
spy(2007/12/27 15:29:58.361)>> OK (Connection[6])
spy(2007/12/27 15:29:58.361)>>
Connection[6].setTransactionIsolation(int level)
spy(2007/12/27 15:29:58.361)>> level = 2
spy(2007/12/27 15:29:58.361)>> OK
spy(2007/12/27 15:29:58.361)>>
Connection[6].isReadOnly()
spy(2007/12/27 15:29:58.361)>> OK (false)
spy(2007/12/27 15:29:58.361)>>
Connection[6].getAutoCommit()
spy(2007/12/27 15:29:58.361)>> OK (true)
spy(2007/12/27 15:29:58.361)>>
Connection[6].prepareCall(String sql)
spy(2007/12/27 15:29:58.361)>> sql = {call
dbo.p_online_password.get_account(?, ?, ?, ?, ?, ?)}
spy(2007/12/27 15:29:58.377)>> OK
(CallableStatement[1])
spy(2007/12/27 15:29:58.377)>>
CallableStatement[1].setObject(int parameterIndex, Object x, int
targetSqlType)
spy(2007/12/27 15:29:58.377)>> parameterIndex = 1
spy(2007/12/27 15:29:58.377)>> x =
[email protected]
spy(2007/12/27 15:29:58.377)>> targetSqlType = 12
spy(2007/12/27 15:29:58.377)>> OK
spy(2007/12/27 15:29:58.377)>>
CallableStatement[1].registerOutParameter(int parameterIndex, int
sqlType)
spy(2007/12/27 15:29:58.377)>> parameterIndex = 2
spy(2007/12/27 15:29:58.377)>> sqlType = -5
spy(2007/12/27 15:29:58.377)>> OK
spy(2007/12/27 15:29:58.377)>>
CallableStatement[1].setObject(int parameterIndex, Object x, int
targetSqlType)
spy(2007/12/27 15:29:58.377)>> parameterIndex = 3
spy(2007/12/27 15:29:58.377)>> x =
spy(2007/12/27 15:29:58.377)>> targetSqlType = 12
spy(2007/12/27 15:29:58.377)>> OK
spy(2007/12/27 15:29:58.377)>>
CallableStatement[1].registerOutParameter(int parameterIndex, int
sqlType)
spy(2007/12/27 15:29:58.377)>> parameterIndex = 4
spy(2007/12/27 15:29:58.377)>> sqlType = -5
spy(2007/12/27 15:29:58.377)>> OK
spy(2007/12/27 15:29:58.377)>>
CallableStatement[1].registerOutParameter(int parameterIndex, int
sqlType)
spy(2007/12/27 15:29:58.377)>> parameterIndex = 5
spy(2007/12/27 15:29:58.377)>> sqlType = 12
spy(2007/12/27 15:29:58.377)>> OK
spy(2007/12/27 15:29:58.377)>>
CallableStatement[1].registerOutParameter(int parameterIndex, int
sqlType)
spy(2007/12/27 15:29:58.377)>> parameterIndex = 6
spy(2007/12/27 15:29:58.377)>> sqlType = -5
spy(2007/12/27 15:29:58.377)>> OK
spy(2007/12/27 15:29:58.377)>>
CallableStatement[1].execute()
spy(2007/12/27 15:29:58.486)>> java.sql.SQLException:
[Macromedia][Oracle JDBC Driver]Numeric overflow. ErrorCode=0
SQLState=HY000
java.sql.SQLException: [Macromedia][Oracle JDBC
Driver]Numeric overflow.
at
macromedia.jdbc.base.BaseExceptions.createException(Unknown Source)
at macromedia.jdbc.base.BaseExceptions.getException(Unknown
Source)
at macromedia.jdbc.oracle.OracleVNU.convertVNUToLong(Unknown
Source)
at
macromedia.jdbc.oracle.OracleImplStatement.convertAndPropagateOutputParams(Unknown
Source)
at
macromedia.jdbc.oracle.OracleImplStatement.execute(Unknown Source)
at macromedia.jdbc.base.BaseStatement.commonExecute(Unknown
Source)
at
macromedia.jdbc.base.BaseStatement.executeInternal(Unknown Source)
at
macromedia.jdbc.base.BasePreparedStatement.execute(Unknown Source)
at
macromedia.jdbc.base.BasePreparedStatementPoolable.execute(Unknown
Source)
at macromedia.jdbcspy.SpyPreparedStatement.execute(Unknown
Source)
at
coldfusion.server.j2ee.sql.JRunPreparedStatement.execute(JRunPreparedStatement.java:89)
at coldfusion.sql.Executive.executeCall(Executive.java:860)
at coldfusion.sql.Executive.executeCall(Executive.java:775)
at coldfusion.sql.Executive.executeCall(Executive.java:726)
at coldfusion.sql.SqlImpl.executeCall(SqlImpl.java:445)
at
coldfusion.tagext.sql.StoredProcTag.executeQuery(StoredProcTag.java:272)
at
coldfusion.tagext.sql.StoredProcTag.doEndTag(StoredProcTag.java:225)
at
cfprocGetAccount2ecfm1970365621.runPage(C:\Inetpub\wwwroot\FBARO\model\login\procGetAccou nt.cfm:63)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:192)
at
coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:366)
at
coldfusion.runtime.CfJspPage._emptyTag(CfJspPage.java:2644)
at
cflogin2eloginuser2ecfm500887643._factor72(C:\Inetpub\wwwroot\FBARO\parsed\login.loginuse r.cfm:24)
at
cflogin2eloginuser2ecfm500887643._factor80(C:\Inetpub\wwwroot\FBARO\parsed\login.loginuse r.cfm:17)
at
cflogin2eloginuser2ecfm500887643._factor81(C:\Inetpub\wwwroot\FBARO\parsed\login.loginuse r.cfm:5)
at
cflogin2eloginuser2ecfm500887643.runPage(C:\Inetpub\wwwroot\FBARO\parsed\login.loginuser. cfm:1)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:192)
at
coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:366)
at
coldfusion.runtime.CfJspPage._emptyTag(CfJspPage.java:2644)
at
cffusebox52ecfm1910112018.runPage(C:\Inetpub\wwwroot\FBARO\fusebox5.cfm:179)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:192)
at
coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:366)
at
coldfusion.runtime.CfJspPage._emptyTag(CfJspPage.java:2644)
at
cffusebox42eruntime2ecfmx2ecfm1434713790.runPage(C:\Inetpub\wwwroot\FBARO\fusebox4.runtim e.cfmx.cfm:1)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:192)
at
coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:366)
at
coldfusion.runtime.CfJspPage._emptyTag(CfJspPage.java:2644)
at
cfindex2ecfm1115026679.runPage(C:\Inetpub\wwwroot\FBARO\index.cfm:28)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:192)
at
coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:366)
at
coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65)
at
coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:279)
at
coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:48)
at
coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:40)
at coldfusion.filter.PathFilter.invoke(PathFilter.java:86)
at
coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:70)
at
coldfusion.filter.BrowserDebugFilter.invoke(BrowserDebugFilter.java:74)
at
coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:2 8)
at
coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38)
at
coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:46)
at
coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38)
at
coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)
at
coldfusion.filter.RequestThrottleFilter.invoke(RequestThrottleFilter.java:126)
at coldfusion.CfmServlet.service(CfmServlet.java:175)
at
coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:86)
at
coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42 )
at
coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)
at jrun.servlet.FilterChain.service(FilterChain.java:101)
at
jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)
at
jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at
jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:284)
at
jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)
at
jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203)
at
jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:320)
at
jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
at
jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
spy(2007/12/27 15:29:58.486)>>
CallableStatement[1].close()
spy(2007/12/27 15:29:58.486)>> OK
spy(2007/12/27 15:29:58.502)>>
Connection[6].setAutoCommit(boolean autoCommit)
spy(2007/12/27 15:29:58.502)>> autoCommit = true
spy(2007/12/27 15:29:58.502)>> OK
spy(2007/12/27 15:29:58.502)>>
Connection[6].setTransactionIsolation(int level)
spy(2007/12/27 15:29:58.502)>> level = 2
spy(2007/12/27 15:29:58.502)>> OK
spy(2007/12/27 15:29:58.502)>>
Connection[6].setReadOnly(boolean readOnly)
spy(2007/12/27 15:29:58.502)>> readOnly = false
spy(2007/12/27 15:29:58.502)>> OK
Any ideas?
Thanks,
Jim

FYI, there is a table near the bottom of the LiveDocs page
for the
cfqueryparam
tag that "
shows the mapping of ColdFusion SQL data types with JDBC SQL
types and those of the listed database management systems".
(The same mapping applies to the cfprocparam tag as well, and I am
surprised that they don't have it listed there as well.)
You will notice that CF_SQL_BIGINT doesn't map to Oracle, and
that only CF_SQL_DECIMAL and CF_SQL_FLOAT seem to map to Oracle
type number. However, I use CF_SQL_NUMERIC all of the time with
Oracle 10g and Oracle type NUMBER with CF7, but I can't speak for
CF8 since we are still on 7.
Phil

Function giving numeric overflow

When i call this function with parameter-
6244628707
i get this error-numeric overflow.
CREATE OR REPLACE FUNCTION TATA_ICR.isprime (p_number NUMBER)
RETURN NUMBER
IS
BEGIN
IF p_number = 3 or p_number=1
THEN
RETURN 1;
END IF;
FOR i IN 3 .. p_number - 1
LOOP
IF MOD (p_number, i) = 0
THEN
RETURN 0;
END IF;
END LOOP;
RETURN 1;
END;
/

Well, see the example and read the documentation!.
SQL> BEGIN
2   --The limit of BINARY_INTEGER/PLS_INTEGER is 2,147,483,647
3   FOR i IN 1..2147483648 LOOP --1 added to the upper limit.
4    NULL;
5   END LOOP;
6 END;
7 /
BEGIN
ERROR at line 1:
ORA-01426: numeric overflow
ORA-06512: at line 3
SQL> This is something do with this statements in the documentation
indexName for the implicitly declared integer variable that is local to the FOR LOOP statement. Statements outside the loop cannot reference index. Statements inside the loop can reference index, but cannot change its value. After the FOR LOOP statement runs, index is undefined.

[Macromedia][Oracle JDBC Driver]Numeric overflow

I am moving from CF 6.1 to CF 9 using Oracle 9i. I get the following error when I use cfstoredproc to call a procedure in a package: [Macromedia][Oracle JDBC Driver]Numeric overflow. In spite of throwing the error, the stored procedure seems to execute properly. Has anyone encountered this problem?

I cannot consistently replicate the problem. Values that work the first time may not work the second time. The data is always entered in the database, but sometimes an error message is thrown regardless of the fact that the data was entered into the database. Calling the procedure with PL/SQL works every time. Here is a dump of the info. from cfcatch:
The database operation failed.
Type: Database
Message: Error Executing Database Query.
Detail: [Macromedia][Oracle JDBC Driver]Numeric overflow.
Native Error Code: 0
SQLState: HY000
SQL: {call pk_name.proc_name ( (param 1) , (param 2) , (param 3) , (param 4) , (param 5) , (param 6) , (param 7) , (param 8) , (param 9) , (param 10) , (param 11) , (param 12) , (param 13) , (param 14) , (param 15) , (param 16) , (param 17) , (param 18) , (param 19) , (param 20) , (param 21) , (param 22) , (param 23) , (param 24) , (param 25) , (param 26) , (param 27) , (param 28) , (param 29) , (param 30) , (param 31) , (param 32) , (param 33) , (param 34) , (param 35) , (param 36) , (param 37) , (param 38) , (param 39) , (param 40) , (param 41) , (param 42) , (param 43) , (param 44) )}
Query Error: [Macromedia][Oracle JDBC Driver]Numeric overflow.
Where:
(param 1) = [type='INOUT', value='null', sqltype='cf_sql_integer'] ,
(param 2) = [type='IN', class='java.lang.Integer', value='41014', sqltype='cf_sql_integer'] ,
(param 3) = [type='IN', class='java.lang.String', value='N', sqltype='cf_sql_char'] ,
(param 4) = [type='IN', class='java.lang.String', value='N', sqltype='cf_sql_char'] ,
(param 5) = [type='IN', class='java.lang.String', value='LastName, FirstName ', sqltype='cf_sql_varchar'] ,
(param 6) = [type='IN', class='java.lang.String', value='12345', sqltype='cf_sql_varchar'] ,
(param 7) = [type='IN', class='java.lang.String', value='10063', sqltype='cf_sql_varchar'] ,
(param 8) = [type='IN', class='java.lang.String', value='LastName, FirstName', sqltype='cf_sql_varchar'] ,
(param 9) = [type='IN', class='java.lang.String', value='(123) 456-7890', sqltype='cf_sql_varchar'] ,
(param 10) = [type='IN', class='java.lang.String', value='abc_201102_163', sqltype='cf_sql_varchar'] ,
(param 11) = [type='IN', class='java.lang.String', value='test', sqltype='cf_sql_varchar'] ,
(param 12) = [type='IN', class='java.lang.String', value='test', sqltype='cf_sql_varchar'] ,
(param 13) = [type='IN', class='java.lang.String', value='test', sqltype='cf_sql_varchar'] ,
(param 14) = [type='IN', class='java.lang.String', value='test', sqltype='cf_sql_varchar'] ,
(param 15) = [type='IN', class='java.lang.String', value='test', sqltype='cf_sql_varchar'] ,
(param 16) = [type='IN', class='java.lang.String', value='', sqltype='cf_sql_varchar'] ,
(param 17) = [type='IN', class='java.lang.Integer', value='38', sqltype='cf_sql_integer'] ,
(param 18) = [type='IN', class='java.lang.String', value='', sqltype='cf_sql_varchar'] ,
(param 19) = [type='IN', class='java.lang.String', value='', sqltype='cf_sql_varchar'] ,
(param 20) = [type='IN', class='java.lang.Integer', value='2', sqltype='cf_sql_integer'] ,
(param 21) = [type='IN', class='java.lang.String', value='EA', sqltype='cf_sql_varchar'] ,
(param 22) = [type='IN', class='java.lang.String', value='test', sqltype='cf_sql_varchar'] ,
(param 23) = [type='IN', class='java.lang.String', value='D', sqltype='cf_sql_varchar'] ,
(param 24) = [type='IN', class='java.lang.String', value='', sqltype='cf_sql_varchar'] ,
(param 25) = [type='IN', value='null', sqltype='cf_sql_varchar'] ,
(param 26) = [type='IN', class='java.lang.String', value='', sqltype='cf_sql_varchar'] ,
(param 27) = [type='IN', class='java.lang.String', value='', sqltype='cf_sql_varchar'] ,
(param 28) = [type='IN', class='java.lang.String', value='', sqltype='cf_sql_varchar'] ,
(param 29) = [type='IN', class='java.lang.String', value='', sqltype='cf_sql_varchar'] ,
(param 30) = [type='IN', value='null', sqltype='cf_sql_integer'] ,
(param 31) = [type='IN', class='java.lang.String', value='', sqltype='cf_sql_varchar'] ,
(param 32) = [type='IN', value='null', sqltype='cf_sql_varchar'] ,
(param 33) = [type='IN', class='java.lang.String', value='', sqltype='cf_sql_varchar'] ,
(param 34) = [type='IN', class='java.lang.String', value='A5E', sqltype='cf_sql_varchar'] ,
(param 35) = [type='IN', class='java.lang.String', value='B5', sqltype='cf_sql_varchar'] ,
(param 36) = [type='IN', class='java.lang.String', value='CEJ', sqltype='cf_sql_varchar'] ,
(param 37) = [type='IN', class='java.lang.String', value='A', sqltype='cf_sql_varchar'] ,
(param 38) = [type='IN', class='java.lang.String', value='15', sqltype='cf_sql_varchar'] ,
(param 39) = [type='IN', class='java.lang.String', value='', sqltype='cf_sql_varchar'] ,
(param 40) = [type='IN', class='java.lang.String', value='ABC DEF - GHI JK', sqltype='cf_sql_varchar'] ,
(param 41) = [type='IN', class='java.lang.String', value='ABCD EF1234 GHI JK', sqltype='cf_sql_varchar'] ,
(param 42) = [type='IN', value='null', sqltype='cf_sql_date'] ,
(param 43) = [type='OUT', sqltype='cf_sql_integer'] ,
(param 44) = [type='OUT', sqltype='cf_sql_varchar']

MSync numeric overflow

One of our clients is using Ora 9i Lite. It has worked perfectly well so far but they are now unable to MSync due to a numeric overflow error that occurred at the start of the Receiving phase.
We suspected some rogue value exceeding the permitted range but they have been unable to find anything so far. We had a similar problem on our dev box about a year ago due to a 1+126 value.
I have just dropped the Mobileclient user and re-created the repository with repwizard. I am seeing this error during the Processing phase.
on@82751 || Overflow Exception
It is now imperative that we fix this so help much appreciated.

looking at msync (same if the APIs are used) from the perspective of the client device, the behaviour of the four progress bars can be a bit misleading
First bar is composing - this is an extract from the client database to create a packed binary file (you should see something like username_snd, or just _snd)
If there is already a send file, then this is added to each time - this in itself can be a problem, as some types of errors (invalid block length for example) are related to corruption in this file
Second bar is sending - this will move progressively across as the data is uploaded, unpacked and inserted into the in queue tables - more data, longer it takes. The end of this stage is EITHER the end of the data file OR an error being sent from the server (ie: a server error causes premature ending of the upload) due to an upload problem. In the case of a server error, you will sometimes see the sending bar suddenly jump to the end
Third bar is recieving - normally there is a slight delay between the end of sending and recieving (whilst the server prepares the data for download), and it then it moves progressively across as the data is downloaded (to a binary file on the client <username>olres.bin). If this jumps across to the end quickly, this is normally due to either an upload error (nothing to download), or a failure during the select for download (constraint violations, invalid packages etc.)
last bar is processing - this is the downloaded binary file being unpacked and written to the client database (you will see second copies of the database files appearing on the client whilst this is running). If the server has sent an error in the download file, it will stop at that point and report the eror.
NOTE the binary files do not get automatically cleared, so you may have to manually remove them, or they will get re-processed next time you sync, and you will see the same error even if it has been fixed.
So from the above
error on upload (normally related to unpacking the upload file, or the inserts into the in queue table) will make the sending complete quickly, go through recieving queickly and fail almost immediately in the processing stage
error on download (normally data selection issues on the server) will have a normal sending phase (and in fact the data will be on the server ready for processing, or in the error queue), but the recieving phase will suddenly jump to the end. The failure will be reported part way thouigh the processing stage

Error message "ORA-01426: numeric overflow"

Could somebody please explain with me examples as when you get this error.
error message "ORA-01426: numeric overflow"
Thank You for your help.

You get 1426 when a number, usually from a caclulation, is too big, or too small for Oracle to represent. For example:
SQL> SELECT POWER(99,99) FROM dual;
SELECT POWER(99,99) FROM dual
ERROR at line 1:
ORA-01426: numeric overflowwhich my calculator tells me is 3.6973E+197
TTFN
John

NUMBER - numeric overflow

Hi all,
I just want to ask about the precision and scale of NUMBER datatype in SQL Developer. It seems to me, that it doesn't have default values but it's defined as NUMBER(10, 0)...
This piece of code works fine in SQL Worksheet and SQL*Plus, but not in developer:
variable var number;
exec :var := 0.12345678901;
print :var;
VAR
0
variable var number;
exec :var := 12345678901;
print :var;
Error report: Numeric overflowIs this a standard and expected behavior? Is there any way how to change it (some configuration)?
Thanks,
ivoB

Hi Ivan,
There is currently no way I know of to configure the output format of a bind variable for run script. I guess this is because SQL Developer does not support "set numformat" yet. It appears to assume a NUMBER(10,0) format.
Let's change your example slightly and see what the difference is between Run Statement (Ctrl+Enter) versus Run Script (F5):
variable var number
column var format 9.999999999999
exec :var := 0.12345678901;
print :var;
select :var as xyz, 0.12345678901 as xyz from dual;
--Run Statement will prompt for the value of 'var', then display both bind and literal to 11 digit precision:
Row XYZ           XYZ_1
1   0.12345678901 0.12345678901
--Run Script truncates or overflows the bind variable as you say, but at least it respects the "col ... format" syntax:
anonymous block completed
VAR
0
XYZ           XYZ
.000000000000 .123456789010 SQL*Plus behaves as one would expect, depending on the value of numformat. For the decimal fraction case, it truncates to 10 digits if numformat is set to the default. Similarly, for the overflow case with a default numformat setting, it uses scientific notation:
       VAR
1.2346E+10I logged a bug:
Bug 13790813 - FORUM: BIND VARIABLES IN RUN SCRIPT LIMITED TO NUMFORMAT(10,0) RANGE
Regards,
Gary
SQL Developer Team

Since you don't allow emails any more – I suspect because of the numerous complaints with your service and the way you treat people that you don't want documented, I am calling and I want this call recorded for future reference. I have been a long time fa

Since you don’t allow emails any more – I suspect because of the numerous complaints with your service and the way you treat people that you don’t want documented, I am calling and I want this call recorded for future reference.
I have been a long time faithful customer of vzw and although the past year I have been late on payments many times and really couldn’t afford your exorbitant prices for services lots of other companies offer sometimes three times cheaper than what you charge, I have hung in there trying my best to meet my obligations.
This month has been no exception. You don’t know the background; the whole story of people’s lives. I know you could care less because all you care about is the profit-the money that comes in.
I was told when I agreed to pay my bill on the third per the recorded message that I had 14 days to pay…you cut me off anyway. The phones are not the tissue; your suspending my service means I cannot work. I may lose my job…how do you justify that? In any case? The least you could do would be to keep 4986 on and cut the phones off. But no. You refuse to compromise and meet the basic needs of your customer. What does that say about your company? I tried to call back on three separate occasions to tell you I couldn’t pay because of unexpected expenses but couldn’t get out of the automated system…sadly couldn’t get to a real person which also speaks volumes to me.
All this tells me this is a company I don’t wish to be affiliated with any more. As soon as I can, I will discontinue service with you…I know you could care less. I will honor the remaining portion of the contract but that’s it. You don’t deserve my business. I am a good, hardworking person who, at the sacrifice of myself and my needs, always pays her bills…albeit late at times. I realize others tell you stories and lies to justify themselves. That’s not me. If you knew what I had been through the last 7 yrs you would marvel that I am still on my feet…don’t judge too quickly. You could be wrong…and in my eyes you are by doing this to me.
God will see us through this extremely scary time of that I have no doubt. No thanks to your company and lack of understanding and mercy. I am doing the best I can. Sadly you are not.
See I have choices. MANY choices of providers for services you offer. I don’t have to be treated like this. I don’t have to succumb to your coldness and callousness. I intend to choose better (and cheaper). If your company doesn’t get the “people factor” back you will be sorry.

Problem here is you admit you cannot afford the service.
And you want to blame Verizon for losing a job because you have no cell phone.
If your job depends on that phone I would pay it on time every time if you need a job to pay your bill.
No other service is going to treat you any different. And if you cannot afford Verizon's monthly invoice how are you going to afford new devices, activation fees, possible security deposits on any other cellular carrier? You can't.
Also if you made an arraignment to pay and then decide you cannot do so, why should Verizon extend you service or credit, or why is it you want to use the service and data and not pay for it as agreed.
Get a prepay phone. Its evident the cost is too high for you to afford on post pay.
Good Luck

Numeric overflow with DBMS_CDC_PUBLISH.CREATE_CHANGE_TABLE

Similar Messages

Maybe you are looking for