Compiling a form creates locks?

Question

I have run into a problem when trying to create a database trigger, its as if there are locks on objects when there are none evident e.g. I compile (not run) a form in Forms builder 9i, then in toad or the sqlplus command line I build a database trigger on the table referenced by the form I’ve just compiled. When I try to compile the trigger, it goes into a wait mode for several minutes and then reports….
ORA-04021: timeout occurred while waiting to lock object PAL.EMP
MY DATABASE TRIGGER CODE IS ..
CREATE OR REPLACE TRIGGER emp_ins
BEFORE INSERT ON EMP
FOR EACH ROW
DECLARE
     max_empno NUMBER(5);
BEGIN
     SELECT MAX(empno)+1
     INTO max_empno
     FROM EMP;
     :NEW.empno := max_empno;
END;
I have the following trigger in the form….
ON-UPDATE (DELETING THIS TRIGGER AND THE PROBLEM GOES)
message('Updating table');
update emp
set
ename = :emp.ename,
job = :emp.job,
sal = :emp.sal
where empno = :emp.empno;
I have checked for locks in toad in the session browser and none are showing up, so I really don’t understand whats going on. I can compile the database trigger no problem but the minute i compile the form i get the problem above. Why does compiling a form cause cause other objects to behave as if they are waiting for locks to be released?
Gus

Answer 1

I should add that after i compile the form i can happily run the following statements.
select * from pal.emp for update;
commit;
but trying to compile the database trigger causes...
ORA-04021: timeout occurred while waiting to lock object PAL.EMP
Gus ???