-
Bug
-
Resolution: Fixed
-
Medium
-
6.0.2
-
6
-
When upgrading JIRA and connect database with Oracle 11g, during the startup, it will show the following error in log file:
2013-06-22 09:56:51,094 localhost-startStop-1 ERROR [core.entity.jdbc.DatabaseUtil] Could not create missing indices for entity "ReplicatedIndexOperation" 2013-06-22 09:56:51,094 localhost-startStop-1 ERROR [core.entity.jdbc.DatabaseUtil] SQL Exception while executing the following: CREATE INDEX node_id_index_operation_time_idx ON replicatedindexoperation (NODE_ID, AFFECTED_INDEX, OPERATION, INDEX_TIME) Error was: java.sql.SQLSyntaxErrorException: ORA-00972: identifier is too long
JIRA is able to start up, so far all JIRA features seems working fine. Re-index in JIRA UI can be done successfully.
UPDATE: Also happens on a Fresh JIRA 6.0.2 installation connected to Oracle database and starting up.
Workaround:
Referring to the KB article and make changes in entitymodel.xml or upgrade to JIRA 6.0.4
- is cloned from
-
JRASERVER-30604 Regressions: Upgrading JIRA get index error: ORA-00972: identifier is too long when running JIRA with Oracle
- Closed
-
JRADEV-22250 Loading...
- is duplicated by
-
JRASERVER-33622 During starting JIRA 6 SQL exception is throw to the log
- Closed