Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
2 replies
Subscribers
7 subscribers
Views
1176 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
#Installation and Administration. Installing Appian 7.11 in JBOSS EAP
vamsib
over 9 years ago
#Installation and Administration.
Installing Appian 7.11 in JBOSS EAP 6.4
================================================
>> Getting the below error during Application Server startup
05:02:22,360 INFO [stdout] (ServerService Thread Pool -- 58) 2015-10-29 05:02:22,359 [ServerService Thread Pool -- 58] INFO com.appiancorp.rdbms.hb.DataSourceManagerHbImpl - [jdbc/firstds] Checking schema and migrating if necessary (appian/db/changelog/db-changelog-master.xml)...
05:02:25,618 INFO [stdout] (ServerService Thread Pool -- 58) 2015-10-29 05:02:25,615 [ServerService Thread Pool -- 58] ERROR liquibase - Error executing SQL ALTER TABLE `test_data` ADD UNIQUE (`obj_uuid`, `obj_version_id`, `obj_type`)
05:02:25,618 INFO [stdout] (ServerService Thread Pool -- 58) com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 1000 bytes
>> Recreated the primary database and tried with restarting App...
server.log
OriginalPostID-175753
OriginalPostID-175753
Discussion posts and replies are publicly visible
0
vamsib
over 9 years ago
...ian and JBOSS but getting the same error all the times.
>> Attaching server.log for more details.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Nick Vigilante
Appian Employee
over 9 years ago
Can you please speak to your DBA about configuring your primary database to use the innodb_large_prefix configuration option? By default, MySQL databases have this option disabled. This option restricts the maximum size of an index. In your case, it's 1000 bytes. Enabling this option will increase the maximum index size to 3072 bytes and it should bypass this error. More information can be found here:
dev.mysql.com/.../innodb-restrictions.html
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel