Re: error ora-01466 and partitions

Hi Steve,

Many thanks for your answer,

Because English is not my native language I'm not completly sure to have well understood what you wrote.
Can it be resumed by :
It's impossible to modify (create/drop) any partition if a transaction is currently runing on the table concerned, even if the partition involved in (create/drop) operation is not involved in transaction ?

Steve Adams <steve.adams_at_ixora.com.au> :

>Hi Frédéric,
>
>Oracle's read-committed transaction isolation model requires that
>changes
>to the data since a transaction's snapshot SCN must not be visible to
>that
>transaction. Similarly, changes to the metadata of referenced tables
>must
>also not be visible. Otherwise, you could for example exchange
>partitions
>and thus introduce data to the table that was committed before the
>snapshot
>SCN, but that ought not to be read for the query because it was not
>part of
>that table at the snapshot SCN. Similarly, you might have dropped
>partitions
>that ought to have been read for the query. This error prevents such
>wrong
>results from being returned. It has to be based on the SCNs alone,
>because
>Oracle cannot tell in retrospect which partitions were affected by the
>metadata change(s), and whether they would have been needed for the
>query.
>You know that, but Oracle does not (at least, not in a way that's
>useful).

Regards
Frederic PAYANT - junior DBA ;-) Received on Mon Jun 16 2003 - 14:02:04 CDT