[
https://issues.apache.org/jira/browse/SENTRY-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151051#comment-15151051
]
Sravya Tirukkovalur edited comment on SENTRY-1066 at 2/17/16 7:52 PM:
----------------------------------------------------------------------
Seems like drop index is the one we want here. Although according to the
documentation dropping a constraint should automatically drop any implicitly
created indexes for the constraint. It might be possible that the drop failed
the first time (as part of drop constraint), and then the explicit drop passed
later on? Cascade seems to be dropping any further constraints like foreign key
constraints on this unique key which is not relevant for our case? Disclaimer:
I am no oracle expert too :-)
JFYI: Also, in another stack overflow post I saw some one saying drop
constraint did not drop the implicit index if it is executed by a non owner.
was (Author: sravya):
Seems like drop index is the one we want here. Although according to the
documentation dropping a constraint should automatically drop any implicitly
created indexes for the constraint. It might be possible that the drop failed
the first time (as part of drop constraint), and then the explicit drop passed
later on? Cascade seems to be dropping any further constraints like foreign key
constraints on this unique key which is not relevant for our case? Disclosure:
I am no oracle expert too :-)
JFYI: Also, in another stack overflow post I saw some one saying drop
constraint did not drop the implicit index if it is executed by a non owner.
> Sentry oracle upgrade script failed with ORA-0955 duplicate name issue
> ----------------------------------------------------------------------
>
> Key: SENTRY-1066
> URL: https://issues.apache.org/jira/browse/SENTRY-1066
> Project: Sentry
> Issue Type: Bug
> Affects Versions: 1.5.1, 1.7.0
> Reporter: Anne Yu
> Assignee: Anne Yu
> Priority: Blocker
> Attachments: SENTRY-1066.0.patch, SENTRY-1066.1.patch
>
>
> We've seen ORA-0955 duplicate name issue while running Sentry upgrade scripts.
> Running Oracle 11g. We eventually tracked it to
> /opt/cloudera/parcels/CDH/lib/sentry/scripts/sentrystore/upgrade/004-SENTRY-74.oracle.sql:
> {code:sql}
> ALTER TABLE SENTRY_DB_PRIVILEGE DROP CONSTRAINT
> "SENTRY_DB_PRIV_PRIV_NAME_UNIQ";
> ALTER TABLE SENTRY_DB_PRIVILEGE ADD CONSTRAINT
> "SENTRY_DB_PRIV_PRIV_NAME_UNIQ" UNIQUE
> ("SERVER_NAME","DB_NAME","TABLE_NAME","COLUMN_NAME","URI","ACTION","WITH_GRANT_OPTION");
> {code}
> Although constraint was dropped, it fails to re-add, as there was an implicit
> index added with same name as well (expected behavior according to docs:
> http://docs.oracle.com/cd/B19306_01/server.102/b14200/clauses002.htm See:
> "Unique Constraints").
> Dropping the index allowed us to finish upgrading the schema successfully.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
