不是bug的bug?
2004-10-27 10:42
232 查看
我们先看如下的一系列执行:
SQL> create or replace view v_bmw_pay_online_new as
2 select *
3 from taobao.bmw_pay_online_new@lnk_db215;
SQL> create or replace procedure sp_v_test is
2 v_id number;
3 begin
4 select id into v_id from v_bmw_pay_online_new where id=1;
5 end;
6 /
Procedure created
SQL> create or replace synonym s_bmw_pay_online_new
2 for taobao.bmw_pay_online_new@lnk_db215;
Synonym created
SQL> create or replace procedure sp_s_test is
2 v_id number;
3 begin
4 select id into v_id from s_bmw_pay_online_new where id=1;
5 end;
6 /
Warning: Procedure created with compilation errors
SQL> show error
Errors for PROCEDURE TAOBAO.SP_S_TEST:
LINE/COL ERROR
-------- ------------------------------------------------------------------------------------
4/29 PL/SQL: ORA-00600: 内部错误代码,参数: [17069], [0x57E77854], [], [], [], [], [], []
4/4 PL/SQL: SQL Statement ignored
可以看到,在同样一个远程对象上面,我可以通过创建视图,然后在该视图上创建存储过程,是没有任何问题的,但是如果我对该远程操作做一个同义词,再在同义词上创建存储过程,则报出了Ora-00600。跟踪也无果,看产生的日志文件也不能看出来什么,上metalink,搜索"ora-00600 17069",发现查出现的东西一大堆,大致是library cache错误,但是到底怎么会产生这个错误呢,online联系上一个oracle在线技术支持,聊了一会儿,问题是解决了,但是他就是不承认是bug,呵呵。
以下是聊天的总结:
ORA-00600 [17069] reorted on compiling a procedure.
Invalid lock in library cache.
Unable to pin the object and hence the Error.
<Note:39616.1> "Failed to pin a library cache object after 50 attempts"
Clearing the shared memory will help to get rid of inconsistant information in memory which is causing the error.
The inconsistency was suspected to be in the remote site. But flushing the shared pool in remote location didnt help.
Tried recreation of the procedure after dropping and recreating the synonym in the local database. But the same failed.
Flushed the shared pool in local database abd successfully created the procedure.
SQL> create or replace view v_bmw_pay_online_new as
2 select *
3 from taobao.bmw_pay_online_new@lnk_db215;
SQL> create or replace procedure sp_v_test is
2 v_id number;
3 begin
4 select id into v_id from v_bmw_pay_online_new where id=1;
5 end;
6 /
Procedure created
SQL> create or replace synonym s_bmw_pay_online_new
2 for taobao.bmw_pay_online_new@lnk_db215;
Synonym created
SQL> create or replace procedure sp_s_test is
2 v_id number;
3 begin
4 select id into v_id from s_bmw_pay_online_new where id=1;
5 end;
6 /
Warning: Procedure created with compilation errors
SQL> show error
Errors for PROCEDURE TAOBAO.SP_S_TEST:
LINE/COL ERROR
-------- ------------------------------------------------------------------------------------
4/29 PL/SQL: ORA-00600: 内部错误代码,参数: [17069], [0x57E77854], [], [], [], [], [], []
4/4 PL/SQL: SQL Statement ignored
可以看到,在同样一个远程对象上面,我可以通过创建视图,然后在该视图上创建存储过程,是没有任何问题的,但是如果我对该远程操作做一个同义词,再在同义词上创建存储过程,则报出了Ora-00600。跟踪也无果,看产生的日志文件也不能看出来什么,上metalink,搜索"ora-00600 17069",发现查出现的东西一大堆,大致是library cache错误,但是到底怎么会产生这个错误呢,online联系上一个oracle在线技术支持,聊了一会儿,问题是解决了,但是他就是不承认是bug,呵呵。
以下是聊天的总结:
ORA-00600 [17069] reorted on compiling a procedure.
Invalid lock in library cache.
Unable to pin the object and hence the Error.
<Note:39616.1> "Failed to pin a library cache object after 50 attempts"
Clearing the shared memory will help to get rid of inconsistant information in memory which is causing the error.
The inconsistency was suspected to be in the remote site. But flushing the shared pool in remote location didnt help.
Tried recreation of the procedure after dropping and recreating the synonym in the local database. But the same failed.
Flushed the shared pool in local database abd successfully created the procedure.
相关文章推荐
- 这不是bug,而是语言特性
- 如果说这个世界不是真实存在的,只是一段代码,迄今为止你发现了哪些bug?
- 这不是bug,而是特性(uva 658)
- 例题11-6 这不是bug,而是特性 UVa658
- 《C专家编程》第二章——这不是Bug,而是语言特性
- gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-2ubuntu1~12.04) 编译器的一个BUG(不是bug)
- 测试不是为了找出所有BUG,而是为了满足用户需求
- 不是bug的bug,从svn下的”错误“代码。
- 不是你写的代码,修什么BUG
- [原创]分享IE7一个神奇的BUG(不是封闭标签的问题,的确是IE7的BUG)
- 软件测试是找bug,不是找茬
- Woring Practice-bug系统的被reopen的错误,把更多的精力放在那个问题上,而不是情绪上。
- CURL库FTP传输文件,当ftpServer端默认登录的目录不是根目录/时,有一个bug会产生
- 基本上,把switch,用设计模式代替,肯定是bug和过度设计。想想,本来修改一个文件几行代码可以解决的问题,变成修改3-6个类才能实现一样的功能。不是傻是什么?
- .NET深入学习之---一个不是Bug的Bug
- mfc中0xC015000F:正在被停用的激活上下文不是最近激活的bug
- 第2章 这不是Bug, 而是语言特性
- 程序员最大的绝望或许并不是电脑里的bug……
- BUG就是BUG,BUG不是灵异