-
Bug
-
Resolution: Done
-
Blocker
-
A-MQ 7.0.0.ER16
-
None
-
None
-
User Experience
Artemis generates identifiers for paging tables using pattern TABLE_NAME + GENERATED ID. Oracle database allows to use only identifiers of maximal length of 30 characters. Generated ID is type of long so it can have size up-to 20 characters what means that maximum length of table name can be only 10 characters. Otherwise error [1] may arises.
This issue is dangerous because it arises after some time and admin is not advised at start of EAP. EAP/Artemis should do some checks at start and at configuration of these parameters.
[1]
SQL STATEMENTS:
CREATE TABLE NODE2_PAGE_STORE_TABLE6442455442(ID NUMBER(19) GENERATED BY DEFAULT ON NULL AS IDENTITY, FILENAME VARCHAR(255), EXTENSION VARCHAR(10), DATA BLOB, PRIMARY KEY(ID))
SQL EXCEPTIONS:
SQLState: 42000 ErrorCode: 972 Message: ORA-00972: identifier is too long
Customer impact: Paging may stop working after some time depending on length of page table name and number of queues.
- clones
-
JBEAP-9732 JDBC store - ORA-00972: identifier is too long
-
- Closed
-
- is related to
-
ENTMQBR-3230 [Docs] JDBC Configuration should indicate page-store-table-name restrictions for Oracle
-
- Closed
-