• State Not Answered
  • Replies 6 replies
  • Subscribers 9 subscribers
  • Views 6567 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Administration

MySQLSyntaxErrorException: Table already exists

Jim Schweitzer
Certified Lead Developer

I'm attempting to migrate from a local 7.5 windows installation to a (new) local 7.6 linux installation. I am also migrating the mysql database from the same previous windows host to the new linux host. I get the following error in the jboss log when trying to start the server for the first time:

17:03:09,825 INFO [stdout] (ServerService Thread Pool -- 57) 2014-09-03 17:03:09,822 [ServerService Thread Pool -- 57] INFO com.appiancorp.rdbms.config.PrimaryDataSourceConfig - Validating and initializing the primary data source: jdbc/app72primary
17:03:12,636 INFO [stdout] (ServerService Thread Pool -- 57) 2014-09-03 17:03:12,634 [ServerService Thread Pool -- 57] INFO com.appiancorp.rdbms.hb.DataSourceManagerHbImpl - [jdbc/app72primary] Checking schema and migrating if necessary (appian/db/changelog/db-changelog-master.xml)...
17:03:16,963 INFO [stdout] (ServerService Thread Pool -- 57) 2014-09-03 17:03:16,962 [ServerService Thread Po...

OriginalPostID-121114

OriginalPostID-121114

  Discussion posts and replies are publicly visible

Parents
  • 0
    Might try this, create a new schema on the new sql server by letting appian startup etc. Then truncate the data leaving the tables, then migrate the data from the old database to the new, truncate the changelog table, import the data from the newly created database \\ changelog and start appian again, see if that works. you will need two new databases to do this. One for a blank install as a new instance, then a second one to move data from the old. lets say appian1 is the new instance, appian 2 is new instance on the new server but is a duplicate of the old windows server sql data.
    Bring appian up on appian 1.... then truncate all tables except dbchangelog or changelog. then copy in the old data from appian2 database not overwritting dbchangelog and then bootup appian2. have to change the appian-ds.xml files and standalone.xml for databases.. luckily you only have to do one driver on linux.. We went from sql to oracle. Its been a real nightmare.
Reply
  • 0
    Might try this, create a new schema on the new sql server by letting appian startup etc. Then truncate the data leaving the tables, then migrate the data from the old database to the new, truncate the changelog table, import the data from the newly created database \\ changelog and start appian again, see if that works. you will need two new databases to do this. One for a blank install as a new instance, then a second one to move data from the old. lets say appian1 is the new instance, appian 2 is new instance on the new server but is a duplicate of the old windows server sql data.
    Bring appian up on appian 1.... then truncate all tables except dbchangelog or changelog. then copy in the old data from appian2 database not overwritting dbchangelog and then bootup appian2. have to change the appian-ds.xml files and standalone.xml for databases.. luckily you only have to do one driver on linux.. We went from sql to oracle. Its been a real nightmare.
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.