问题三

1.错误描述

9i升级到11g之后执行储存过程报错

ORA-29471: DBMS_SQL 访问被拒绝 ORA-06512: 在

"SYS.DBMS_SQL", line 1192 ORA-06512: 在  "REINSDEV.LRE_COMMON_INTERFACE_PKG", line 195

ORA-01002: 提取违反顺序 ORA-06512: 在 line 1

2：问题根源

Oracle在10g及之后：PL/SQL raises an

exception if you try to fetch from a FOR UPDATE cursor after

doing a commit. The FOR UPDATE clause locks the

rows when you open the cursor, and unlocks them  when you commit.

3：解决方案

修改代码，去掉FOR UPDATE和WHERE CURRENT

OF

ps:这里有个很好笑的事情，当时给oracle提供SR以后，oracle回复如下

1、Generally ORA-01002 will be thrown when FOR UPDATE

is involved. For update cursors cannot be fetched across commits, I

can see in your code (ie)

lre_common_interface_pkg.update_fac_proportion you are using FOR

UPDATE cursor and also doing a commit in between.

This is not allowed, you should re-design the code to avoid

this.

This behavior is not specific to 11g, its present in 10g

also.

2、Plsql

Guide (Refer to section "Fetching Across Commits")

Error Information

Both the docs clearly says that FOR UPDATE cursor can't be

fetched after a commit have been issues. In this case ORA-01002 is

an expected error.

3、Note: This is INTERNAL ONLY research. No

action should be taken by the customer on this information. This is

research only, and may NOT be applicable to your specific

situation.

也就是说报错的关键在于使用了FOR

UPDATE游标，9i不报错而11g报错，这个是Oracle的内部设计，客户没必要知道。

问题四

1.错误描述

ORA-01779:

无法修改与非键值保存表对应的列

2：问题根源

Bug 14561826 : UPDATE

STATEMENTS FAILS WITH ORA-01779 ERROR AFTER UPGRADE TO 11G

DATABASE

3：解决方案

3.1、Bug 14561826 : UPDATE STATEMENTS FAILS WITH

ORA-01779 ERROR AFTER UPGRADE TO 11G DATABASE，

打补丁解决

3.2、在该表上创建惟一索引(最好是主键)