We had the same problem. I advised the developer putting it in, that having
a unique index besides the primary key on the same columns on the same table
would be silly. He called the vendor who agreed with us. How it was
allowed to exist in the first place we still don't know. Even stranger, the
upgrade went perfectly in the prior test where the main schema had been
exported from production and imported into test. A bug??
David Spaisman wrote in message <369C38E1.5C32D7C9_at_intercall.com>...
>Hello:
>
>I am working on NT with oracle 8.0.4.
>
>I am trying to set up another test database
>based upon a production database.
>
>Based upon an extract of ddl by DBArtisan, I ran the extract ddl and
>most of the objects were created i nthe test database. One object not
>created were three indices. The error message given was : ora-01408:
>
>on editool.app_activity_log(act_id asc)
>*
>ORA-01408: such column list already indexed
>
>And in fact there is also a primary index constraint which utilizes the
>same column(act_id). But when I look at production(this is a package
>bought from a vendor) the primary index and this same second index
>exist!! I can't figure out how. I looked at the original ddl we got from
>the vendor and it is the same as what I am running?
>
>
>1) so how did this happen?
>
>2) How do I get this second index created in the test database?
>
>Thanks.
>
>DAvid Spaisman
>
Received on Thu Jan 14 1999 - 23:19:52 CST
