Recent content by Shaper

Marco, have you reproduced the problem?

We compiled this trigger with and without debug information and tried to debug in both cases but the problem still occured. Having this trigger with just one code line "return" in the database cause the problem. Disabling the trigger resolve this problem. Have you reproduced the problem?

Yes, because "Add debug information when compiling" option is turned on.

A small misprint: CREATE OR REPLACE TRIGGER AUDIT_DATABASE_ASE AFTER SERVERERROR ON DATABASE BEGIN RETURN; END;

It easy to reproduce this problem on Oracle 10g(10.2.0.2 on RAC), here are steps: CREATE OR REPLACE TRIGGER AUDIT_DATABASE_ASE AFTER SERVERERROR ON DATABASE BEGIN END; END; Next start debugging any code and finnally call break at any code line - debugger will hang. Disabling the trigger...

Will this bug be fixed in the next version of PL/SQL Developer? Thanks.

We found out that PL/SQL Developer 7.0.2 also has this bug and it looks as follows: - ORA-20000: OFS-7 Path not found. path=New - ORA-06512: in "OFS.OFS", line 8 - ORA-06512: in "OFS.OFS", line 20 - ORA-06512: in "OFS.OFS", line 108 - ORA-06512: in "OFS.OFS", line 165 - ORA-06512: in line...

Now we have no spare time to download/install 7.0.2 version and check this issue. Have you fixed this problem in 7.0.2? Could you specify the link to 7.0.2 change/fix list? Thanks.

We use the following Developer: PL/SQL Developer - Version 7.0.1.1066 (MBCS)Enterprise edition on Windows XP version 6.0 (build 2600) Service Pack 2.

It is easy to reproduce that. I have done the following and got the same error (ORA-20000: OFS-7: Path not found...): 1. create user OFS identified by OFS; grant connect, resource, query rewrite to OFS; create user OFS_USER identified by OFS_USER; grant dba, connect to OFS_USER; 2. Next...

The ofs_private package contains the following procedure: - procedure force_unlock(p_id in OFS_ITEMS.id%type); As far as I understand this functionality is supposed to be use in case of we need to unlock forcedly opened with locking mode source by another user. But we have not found how to...