Hi all,
In 8.1.7 on HP/UX 11.0, we've got some homemade triggers on a vendor's
schema. One of these triggers tried to write an audit record to a table in
a tablespace different from the table that was being updated, but the audit
table's tablespace filled up.
Since we had an exception clause
if you can (and I assume you can) change the trigger code and if you are on
8i, make use of autonomous transactions. so you can capture all required
information and insert it into a table.
You may want to write this as a separate procedure and call that with
appropriate information from the
How about monitoring the audit tablespace to ensure it doesn't fill up?
Jared
Jesse, Rich [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
02/22/02 10:43 AM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:
Send an email to whomever in the EXCEPTION clause? Actually, the whomever
should be some email account that the DBAs can subscribe to (and unsubscribe
when they get that six figure job somewhere else).
Also, is there any interest in coding for those this full type error
messages and then
I agree since it's better than auditing the audit!
-Original Message-
Sent: Friday, February 22, 2002 2:18 PM
To: Multiple recipients of list ORACLE-L
How about monitoring the audit tablespace to ensure it doesn't fill up?
Jared
Jesse, Rich [EMAIL PROTECTED]
Sent by: [EMAIL
