Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Startup Trigger Can't Do DDL ...

Re: Startup Trigger Can't Do DDL ...

From: Domenic <domenicg_at_hotmail.com>
Date: 30 Apr 2004 06:57:37 -0700
Message-ID: <c7e08a19.0404300557.2f74a4c8@posting.google.com>


And what would that be? You didn't answer the question -- the docs say that an autonomous trigger can perform DDL -- and it doesn't work.  It should regardless of whether I want to drop a sequence or not. What good are these advanced features if they don't work!!

Domenic.

Holger Baer <holger.baer_at_science-computing.de> wrote in message news:<c6t489$j3h$1_at_news.BelWue.DE>...
> Howard J. Rogers wrote:
> >
> > And never mind the loss of numbers when an instance crashes: what about
> > the loss of numbers that will happen when somebody rolls back their
> > transaction (or suffers a blue screen of death in mid-transaction and
> > has PMON roll it back for them)? Or when the junior DBA wanting to know
> > what the last sequence number issued was happens to select from currval?
> >
>
> Just curious (or lazy if you wan't, because I didn't dig into the
> documentation just now): What do you think that happens?
> Selecting from currval returns the last retrieved number for the *CURRENT*
> session - if it had never been retreived you get an
>
> select sequencename.currval from dual;
>
> ORA-08002: sequence <sequencename> is not yet defined in this session
>
>
> This is what a quick test on 10g confirmed.
>
> Regards,
>
> Holger
Received on Fri Apr 30 2004 - 08:57:37 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US