sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anne Yu (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SENTRY-1066) Sentry oracle upgrade script failed with ORA-0955 duplicate name issue
Date Mon, 15 Feb 2016 06:46:18 GMT
Anne Yu created SENTRY-1066:
-------------------------------

             Summary: 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
            Reporter: Anne Yu
            Assignee: Anne Yu
            Priority: Blocker


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)

Mime
View raw message