Hi,
I had noticed that one of our triggers is performing very badly. I had disabled the
trigger to test replication and there was a issue with the trigger. When the developer
changed the trigger and enabled it, replication slowed down to one record per second
(other tables are being updated, instered, and deleted from).
I analyzed the plans for all sql statements generated in the trigger itself
and they are all using the correct indices etc. There are no full table scans etc.
We have simliar trigger on our other replicated tables that are not seeing THIS bad
performance.
Any one have any suggestions/links for putting this trigger through the paces
to determine the bottleneck?
Thanks,
Hannah
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
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).
