Found out what caused it.
When updating the opening of the cursor had a mutating table error,
but because I had the exception WHEN OTHERS THEN NULL;
I did not get the error and the update continued.
(Bit) stupid of me to use the when other exception in this way.
Thanks for the replies.
I now have to think about a way to work around this, with out using 3
exceptions.
On 2 Dec, 07:32, eteunisse <[EMAIL PROTECTED]> wrote:
> That would be the most logic thing, but when I insert the cursor does
> neatly get my record.
>
> On 1 Dec, 20:23, "Michael Moore" <[EMAIL PROTECTED]> wrote:
>
> > Must be that
> > OPEN c_osn_01 (piv_proces_cd_pre);
> > is blowing up.
>
> > On Mon, Dec 1, 2008 at 6:17 AM, ddf <[EMAIL PROTECTED]> wrote:
>
> > > On Dec 1, 7:33 am, eteunisse <[EMAIL PROTECTED]> wrote:
> > > > The strange thing is that when I do an insert, all the outpulines do
> > > > appear, only with an update they do not.
> > > > And the updatetrigger does work because I do get the first two
> > > > outputlines.
> > > > I'm lost.
>
> > > > On 1 Dec, 14:14, eteunisse <[EMAIL PROTECTED]> wrote:
>
> > > > > This is the case:
> > > > > In a procedure which is part of an input/output trigger I put some
> > > > > dbms_output.put_line statements.
> > > > > Nothing strange about that.
> > > > > The first few outputlines do appear correct when I fire an update or
> > > > > insert.
> > > > > But the output lines some statements further in de procedure do not
> > > > > appear any more.
> > > > > There are no IF-statements that prevent them from displaying. (see
> > > > > code beneath)
> > > > > Does anyone have an idea what causes the sudden stop of displaying my
> > > > > outputlines?
>
> > > > > BEGIN
> > > > > lvv_name := mta_br_osn.gcv_pack_name || '.' || lcv_proc_name ;
>
> > > > > lvv_step := 'Controle prioriteit pre-proces';
>
> > > > > dbms_output.put_line ('TEST start'); --this one DOES appear
>
> > > > > IF piv_proces_cd_pre IS NOT NULL
> > > > > THEN
> > > > > dbms_output.put_line ('TEST 00'); --this one DOES appear
>
> > > > > OPEN c_osn_01 (piv_proces_cd_pre);
>
> > > > > dbms_output.put_line ('TEST 01'); --THIS ONE DOES NOT APPEAR!!!
>
> > > > > FETCH c_osn_01
> > > > > INTO lvn_prio_pre;
>
> > > > > dbms_output.put_line ('TEST 02'); --THIS ONE DOES NOT APPEAR!!!
>
> > > > > IF c_osn_01%NOTFOUND
> > > > > THEN
> > > > > CLOSE c_osn_01;
> > > > > lvv_melding := 'Pre-proces niet gevonden';
> > > > > RAISE le_not_found;
> > > > > END IF;
>
> > > > > CLOSE c_osn_01;
>
> > > > > dbms_output.put_line ('TEST 03'); --THIS ONE DOES NOT APPEAR!!!
>
> > > > > IF lvn_prio_pre != pin_prioriteit-1
> > > > > THEN
> > > > > lvv_melding := 'ERROR';
> > > > > RAISE le_fout;
> > > > > ELSE
> > > > > dbms_output.put_line ('TEST 04'); --THIS ONE DOES NOT APPEAR!!!
> > > > > END IF;
> > > > > END IF;- Hide quoted text -
>
> > > > - Show quoted text -
>
> > > First, post the complete code for the trigger along with the DDL and
> > > sample data for any tables involved with this process. Second, post
> > > the Oracle version you're using, to at least 4 numbers.
>
> > > When this information is available someone can then help you.
>
> > > David Fitzjarrell
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Oracle PL/SQL" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Oracle-PLSQL?hl=en
-~----------~----~----~----~------~----~------~--~---
