Can't you tell your trigger to ignore this error as well.
-Original Message-
Sent: Saturday, August 30, 2003 7:19 AM
To: Multiple recipients of list ORACLE-L
Use a Database Trigger AFTER SERVERRROR.
[careful, the table might fill up pretty quickly -- e.g at my site a load
job
Yes, I could ignore ORA-001. But there are cases where I might want
to know of ORA-001's occurring.
Hemant
At 11:59 PM 31-08-03 -0800, you wrote:
Can't you tell your trigger to ignore this error as well.
-Original Message-
Sent: Saturday, August 30, 2003 7:19 AM
To: Multiple recipients
Is there anyway to setup oracle on the server side to log all fail and error
transaction in a file or something? I mean, error/fail transaction due to,
eg: Integrity Contraint violation, Check constraint, Not Null constraint, any
other error.
It would simply debugging since then we don't have
Use a Database Trigger AFTER SERVERRROR.
[careful, the table might fill up pretty quickly -- e.g at my site a load job
ignores ORA-0001 errors but this table gets a lot of ORA-0001 errors !!]
Try this :
drop table system.oracle_errors;
create table system.oracle_errors
(db_username
