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 on the trigger to ignore errors (priority is making sure the purchased app is OK), some of the audits didn't get written. We can probably recreate those audits manually, but I'm wondering if there was a better way to handle this in the trigger. We don't want the trigger to return an exception to the caller, since the caller is most likely the vendor app. Basically, we want our trigger to be completely unobtrusive/unknown to the app. For example, in an EXCEPTION clause, is it possible to force the current process to dump a trace without affecting the current transaction? I was also thinking that the EXCEPTION could attempt to write to an error table in another tablespace, but since it's still DML, there's no real guarantees that it won't bonk either. The only other thing I could think of is to write a proc that UTL_FILE's a pseudo-trace out to disk that would be picked up by our custom Oracle log checkers. Anyone done anything like this before or have any suggestions/pros/cons? TIA! Rich Jesse System/Database Administrator [EMAIL PROTECTED] Quad/Tech International, Sussex, WI USA -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Jesse, Rich INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
