Re: ORA-00001 on non-unique index!

DA Morgan wrote:
> charles.a.berger_at_gmail.com wrote:

-- removed original post for brevity
>
> Is there be a previously existing unique index on the column?
> --
> Daniel A. Morgan
> University of Washington
> damorgan_at_x.washington.edu
> (replace x with u to respond)
> Puget Sound Oracle Users Group
> www.psoug.org

There's only one unique index on the table and the datecol is not part of it. The numcol is but the index has 6 columns altogether. Furthermore, the error message does not name that index.

I doubt the datecol has ever been or ever would be included in a unique index as it is often set to a constant value ('31-DEC-3000') or to sysdate. It doesn't make sense to me to include it in a unique index.

I know that Oracle modifies a non unique B-tree index under the covers to be unique by adding the rowid to the column list to make it unique - I'm wondering if somehow I'm getting two rows with the same rowid (which I find very hard to believe) and that is causing the problem.

Otherwise I'm thinking it must be a bug in Oracle, although a search of Metalink yesterday revealed no matches.

Cheers,

Charles. Received on Tue Nov 07 2006 - 02:36:02 CST