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 resolve this problem.
Could you fix the developer to have the ability to use this kind of trigger in the database?
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 resolve this problem.
Could you fix the developer to have the ability to use this kind of trigger in the database?