View Issue Details

IDProjectCategoryView StatusLast Update
0004320SymmetricDSBugpublic2020-03-17 14:43
Reporterelong Assigned Toelong  
Prioritynormal 
Status closedResolutionfixed 
Product Version3.10.0 
Target Version3.11.7Fixed in Version3.11.7 
Summary0004320: MySQL upgrade gets sym_transaction_id_pre_5_7_6 does not exist
DescriptionSymmetricDS alters tables, runs the upgrade listener (which syncs triggers), and then createsRequiredDatabaseObjects. The syncing of triggers updates the triggers, but the triggers require the missing function that is created by createsRequiredDatabaseObjects. An update of sym_channel causes the triggers to fire prior to createsRequiredDatabaseObjects so you get the following error and SymmetricDS doesn't start.

org.jumpmind.db.sql.SqlException: FUNCTION storedb.sym_transaction_id_pre_5_7_6 does not exist
at org.jumpmind.db.sql.AbstractSqlTemplate.translate(AbstractSqlTemplate.java:305)
at org.jumpmind.db.sql.AbstractSqlTemplate.translate(AbstractSqlTemplate.java:294)
at org.jumpmind.db.sql.JdbcSqlTemplate.execute(JdbcSqlTemplate.java:519)
at org.jumpmind.db.sql.JdbcSqlTemplate.update(JdbcSqlTemplate.java:358)
at org.jumpmind.db.sql.AbstractSqlTemplate.update(AbstractSqlTemplate.java:227)
at org.jumpmind.symmetric.db.DatabaseUpgradeListener.afterUpgrade(DatabaseUpgradeListener.java:217)
at org.jumpmind.symmetric.db.AbstractSymmetricDialect.createOrAlterTablesIfNecessary(AbstractSymmetricDialect.java:546)
at org.jumpmind.symmetric.db.AbstractSymmetricDialect.initTablesAndDatabaseObjects(AbstractSymmetricDialect.java:159)
at org.jumpmind.symmetric.AbstractSymmetricEngine.setupDatabase(AbstractSymmetricEngine.java:513)
at org.jumpmind.symmetric.AbstractSymmetricEngine.setup(AbstractSymmetricEngine.java:487)
TagsNo tags attached.

Relationships

related to 0004318 closedelong MySQL upgrade gets sym_transaction_id_pre_5_7_6 does not exist 

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2020-03-17 11:20 elong New Issue
2020-03-17 11:20 elong Status new => assigned
2020-03-17 11:20 elong Assigned To => elong
2020-03-17 11:20 elong Issue generated from: 0004318
2020-03-17 11:20 elong Relationship added related to 0004318
2020-03-17 11:21 elong Status assigned => resolved
2020-03-17 11:21 elong Resolution open => fixed
2020-03-17 11:21 elong Fixed in Version => 3.11.7
2020-03-17 14:43 admin Status resolved => closed