Given: table with trigger (BEFORE INSERT OR UPDATE, FOR EACH ROW) supposed to record changes to journal table; the trigger definitely uses new: and old: to insert record into journal. The problem: mass load of data supposed to cause considerable amount of changes sometimes does not change the main table, nonetheless the changes (as they are supposed to happen) are always properly reflected in journal table; the effect is almost completely random, however it has never been met of fresh (just restarted) instance; even more, if the process is repeated after the instance has been restarted the outcome is quite right; the problem first occurred on Oracle 7.3.4 EE, then there has been upgrade to 8.1.6, nonetheless the effect is still here;
Most strange there is, though we have several customers using our product in question, only one of them encounters this problem (on HP UX). They have surrounded the application with some amount of code of their own using our data structures, nonetheless all users outside application are limited to read only access to application tables. I do not understand if it'd be even possible in terms on Oracle transaction if data inserted by trigger is committed and data causing that insert doesn't. Have anybody met anything similar? Any ideas and suggestions appreciated, TIA, Uldis Pavuls DBA, Tieto Konts Financial Systems Ltd. 41 Lacplesa Str., Riga, Latvia, LV 1011 phone +371 7 286 660, fax +371 7 243 000 mailto:[EMAIL PROTECTED], http://www.konts.lv -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Uldis 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).
