When using a schema or a field with a very long name (>30 chars), the table or column in Oracle is not using an appropriately shortened name which leads to the error below.
The table and column name show be shortened below 30 chars, with no collision possible, but still be readable.
ERROR [MCFConnectionInterceptor] Error occurred creating ManagedConnection for org.apache.geronimo.connector.outbound.ConnectionInfo@bec438
org.nuxeo.ecm.core.storage.StorageException: java.sql.SQLException: ORA-00972: identifier is too long
at org.nuxeo.ecm.core.storage.sql.jdbc.JDBCMapper.createDatabase(JDBCMapper.java:133)
at org.nuxeo.ecm.core.storage.sql.jdbc.JDBCBackend.newMapper(JDBCBackend.java:156)
at org.nuxeo.ecm.core.storage.sql.RepositoryImpl.getConnection(RepositoryImpl.java:335)
...
Caused by: java.sql.SQLException: ORA-00972: identifier is too long
...
at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1552)
at org.nuxeo.ecm.core.storage.sql.jdbc.JDBCMapper.createTables(JDBCMapper.java:199)
at org.nuxeo.ecm.core.storage.sql.jdbc.JDBCMapper.createDatabase(JDBCMapper.java:130)
- depends on
-
NXP-3785 SQL Storage: make sure all Oracle identifiers are below 30 chars
- Resolved
- is required by
-
NXP-8956 Don't fail on directory names that produce too long table names
- Resolved
-
NXS-320 The VCS storage engine don't work corectly with Oracle (MAX 30 characters/table name)
- Resolved
-
NXP-8111 Fix SQL generation for long schema names
- Resolved
-
NXS-304 The names of generated schema for virtual navigation are too long with Oracle
- Resolved