[
https://issues.apache.org/jira/browse/AMBARI-14144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-14144:
----------------------------------
Description:
{noformat}
ALTER TABLE permission_roleauthorization ADD CONSTRAINT
FK_permission_roleauthorization_permission_id FOREIGN KEY (permission_id)
REFERENCES adminpermission(permission_id)
Error report -
SQL Error: ORA-00972: identifier is too long
00972. 00000 - "identifier is too long"
*Cause: An identifier with more than 30 characters was specified.
*Action: Specify at most 30 characters.
{noformat}
was:
{noformat}
2015-12-01 14:54:34,519 ERROR [main] (DBAccessorImpl.java:724) executeQuery() -
Error executing query: ALTER TABLE permission_roleauthorization ADD CONSTRAINT
FK_permission_roleauthorization_permission_id FOREIGN KEY (permission_id)
REFERENCES adminpermission (permission_id)
java.sql.SQLSyntaxErrorException: ORA-00972: identifier is too long
at
oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:91)
{noformat}
> FK_permission_roleauthorization_permission_id is too long for a constraint
> identifier
> -------------------------------------------------------------------------------------
>
> Key: AMBARI-14144
> URL: https://issues.apache.org/jira/browse/AMBARI-14144
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.3.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Priority: Blocker
> Labels: rbac
> Fix For: 2.3.0
>
>
> {noformat}
> ALTER TABLE permission_roleauthorization ADD CONSTRAINT
> FK_permission_roleauthorization_permission_id FOREIGN KEY (permission_id)
> REFERENCES adminpermission(permission_id)
> Error report -
> SQL Error: ORA-00972: identifier is too long
> 00972. 00000 - "identifier is too long"
> *Cause: An identifier with more than 30 characters was specified.
> *Action: Specify at most 30 characters.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
