Re: Trigger problems with 7.2.3

From: MarkP28665 <markp28665_at_aol.com>
Date: 1997/04/02
Message-ID: <19970402233801.SAA09239@ladder01.news.aol.com>#1/1

>>> blank lines removed >>

I am running 7.2.3 on an HPUX 10.10 system and this trigger will fail if executed twice.
i.e. it won't replace it will however work find on 7.1.6. Any clues? CREATE OR REPLACE TRIGGER RTX_001_ai

	AFTER INSERT ON RTX_001
		REFERENCING NEW AS NEW FOR EACH ROW
        WHEN ( NEW.SPECIAL_NUMBER_IND IS NULL OR
              NEW.SPECIAL_NUMBER_IND != 'T')

begin

    update_mpufdtab(nvl(:new.r_p_customer_id,0),

                            nvl(:new.r_p_contract_id,0),
                             nvl(:new.rated_flat_amount,0) +
                             nvl(:new.toll_rate,0) +
                             nvl(:new.tap_net_rate,0) +
                             nvl(:new.tap_tax_rate,0) +
                             nvl(:new.roam_surcharge,0) );

end;
/
<<<
If you do not get a good answer you might try this:

1. remove the referencing new as new clause since new is the default.
2. I do not have a 7.2.3 SQL manual handy but if the above does not work you might check it for a syntax change/correction. (Unlikely, but Analyze was wrong in the 7.0 manual so...)

I think that all triggers should have an exception clause in them to handle unexpected Oracle type errors, but this is besides the point.

Good Luck.
Mark Powell -- The only advise that counts is the advise that you follow so follow your own advise Received on Wed Apr 02 1997 - 00:00:00 CST