Re: 8.1.6 Bug - statement level triggers

Hello, Leng

Have the same problem. Both on UnixWare and NT. Looks like generic bug. Master/detail and delete triggers make detonating mix. One way triggers do not fire (see metalink), another crash. :-(. I appreciate very much if you let me know when you find solution

Vadim Gorbunov
Oracle DBA

Leng Kaing wrote:

> Hello everyone,
>
> If you're on Oracle 8.1.6 (any o/s will do) can you please try this and let
> me know if it's causing the same error as I'm encountering.
>
> <<trig.sql>>
> Essentially the scenario is this:
> 1. table SB1 is the parent of SB2
> 2. There are statement level triggers on both tables
> 3. If the statement level trigger on both tables are enabled, and I issue
> the statement DELETE * FROM SB1;, the client get ORA-3113. A trace file is
> generated in the udump area with the following dump:
>
> Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object),
> addr: 0x90, PC: kglpnp()+92
> *** 2000-06-06 15:27:11.280
> ksedmp: internal or fatal error
> ORA-07445: exception encountered: core dump [kglpnp()+92] [SIGSEGV] [Address
> not mapped to object] [144] [] []
> Current SQL statement for this session:
>
> If the statement level triggers on SB2 are disable, the delete statement is
> processed without any errors.
>
> I've tried the same scenario on 8.0.5 and it is ok. But the errors are there
> on 8.1.6.1.1.0 and 8.1.6.0.0.
>
> Thanks,
>
> > Leng.
> > -----------------
> > Leng Kaing
> > Tel: +61-3-9843-8440
> > Email: leng.kaing_at_hancorp.com.au
> >
>
> ------------------------------------------------------------------------
>
> trig.sqlName: trig.sql
> Type: application/x-unknown-content-type-sql_auto_file
Received on Wed Jun 07 2000 - 04:22:50 CDT