PL/SQL 游标报错 ORA-06502: PL/SQL: numeric or value error

2014-01-06 04:48:11 741 阅读 AI 写同款 · GEO 优化AI 选题数据监测一键分发 ›

KingbaseES PL/SQL参数模式深度解析：IN、OUT、IN OUT实战与性能优化在数据库编程中，存储过程和函数的参数传递机制是核心基础概念，它决定了数据在调用者与子程序之间的流向与处理方式。其原理主要涉及值传递与引用传递两种底层机制，直接影响内存使用和程序性能。掌握参数模式的技术价值在于能够编写出更安全、高效且易于维护的数据层代码，尤其在处理大数据量、高并发场景时，合理选择参数模式能显著减少不必要的内存拷贝与锁竞争。应用场景广泛，包括但不限于数据查询封装、事务处理、批量操作以及模块化业务逻辑设计。本文聚焦于人大金仓KingbaseES数据库，深入探讨其PL/SQL兼容性中的IN、OUT 阅读详情

每天需要跑一个存过，备份一个表。但是经常跑失败，报错
报错信息为：ORA-06502: PL/SQL: numeric or value error。
在测试环境调试的时候打开游标也老是报这个错。

其中表中的一个字段是long字段，里面存的是一大串XML报文。
结构为以下。

c_send_packet LONG
=========里面存的内容为=========
<?xml version="1.0" encoding="GBK"?>
<PACKET type="RESPONSE">
<HEAD>
。。。。。。。。。。。。。。。。
</HEAD>
<BODY>
。。。。。。。。
</packet>

=========存过的内容为=============
for p in (select *
from t_table
where t_tm < add_months(sysdate,-1))loop

insert into table (content)values(p.content);
commit;

end loop;

...全文

告别Keil4！手把手教你用Keil C51 V9.61编译51单片机代码（附最新激活方法）本文详细介绍了Keil C51 V9.61在51单片机开发中的全栈升级指南，包括编译速度提升、调试器性能优化和现代开发支持等核心优势。通过智能安装方案、项目迁移实战和新特性深度应用，帮助开发者告别Keil4，大幅提升开发效率。附有最新激活方法和实用技巧，适用于嵌入式开发工程师。阅读详情

walkman154

Oracle 17,133 成员 55,258 内容

+ 关注 + 加入社区

切换为时间正序

walkman154 2014-01-08

打赏
举报

继续求解继续求解

westqueen 2014-01-07

打赏
举报

我也遇到这个问题，楼主有办法了吗？

大话EPM 2014-01-06

打赏
举报

没看你内容，表字段不要用long字段，用clob有什么不好呢 long只是用来后兼容的，问题一大堆 ref： The use of LONG values is subject to these restrictions: A table can contain only one LONG column. You cannot create an object type with a LONG attribute. LONG columns cannot appear in WHERE clauses or in integrity constraints (except that they can appear in NULL and NOT NULL constraints). LONG columns cannot be indexed. LONG data cannot be specified in regular expressions. A stored function cannot return a LONG value. You can declare a variable or argument of a PL/SQL program unit using the LONG data type. However, you cannot then call the program unit from SQL. Within a single SQL statement, all LONG columns, updated tables, and locked tables must be located on the same database. LONG and LONG RAW columns cannot be used in distributed SQL statements and cannot be replicated. If a table has both LONG and LOB columns, then you cannot bind more than 4000 bytes of data to both the LONG and LOB columns in the same SQL statement. However, you can bind more than 4000 bytes of data to either the LONG or the LOB column. In addition, LONG columns cannot appear in these parts of SQL statements: GROUP BY clauses, ORDER BY clauses, or CONNECT BY clauses or with the DISTINCT operator in SELECT statements The UNIQUE operator of a SELECT statement The column list of a CREATE CLUSTER statement The CLUSTER clause of a CREATE MATERIALIZED VIEW statement SQL built-in functions, expressions, or conditions SELECT lists of queries containing GROUP BY clauses SELECT lists of subqueries or queries combined by the UNION, INTERSECT, or MINUS set operators SELECT lists of CREATE TABLE ... AS SELECT statements ALTER TABLE ... MOVE statements SELECT lists in subqueries in INSERT statements Triggers can use the LONG data type in the following manner: A SQL statement within a trigger can insert data into a LONG column. If data from a LONG column can be converted to a constrained data type (such as CHAR and VARCHAR2), then a LONG column can be referenced in a SQL statement within a trigger. Variables in triggers cannot be declared using the LONG data type. :NEW and :OLD cannot be used with LONG columns

PL/SQL 游标 报错 ORA-06502: PL/SQL: numeric or value error

相关推荐

PL/SQL 游标报错 ORA-06502: PL/SQL: numeric or value error