oro:install breaks when run a MySQL DB using GTID replication

Oracle’s preferred method for MySQL HA is to use GTID based replication. To enable GTID based replication, two things need to be added to the /etc/my.cnf file

enforce_gtid_consistency = ON gtid_mode = ON

1 2	enforce_gtid_consistency = ON gtid_mode = ON

The oro_search_index_text table is MyISAM. Updates to a MyISAM table have certain restrictions when using GTIDs.

The install script will break when the target database is set up for GTID based replication. The specific error is:

An exception occurred while executing 'INSERT INTO oro_search_index_text (field, value, item_id) VALUES (?, ?, ?)' with params ["name", "default", 1]: SQLSTATE[HY000]: General error: 1785 Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.

1 2

An exception occurred while executing 'INSERT INTO oro_search_index_text (field, value, item_id) VALUES (?, ?, ?)' with params ["name", "default", 1]: SQLSTATE[HY000]: General error: 1785 Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.

Running this statement outside a transaction (or in autocommit mode) should solve this.

Topic

[andrew wilcoxParticipant]

(Using MySQL 5.7 BTW. GTIDs are post 5.1 IIRC)

[Artem LiubeznyiSpectator]

Hi Andrew,

Thanks for sharing the issue. Is there anything we can help you in this regard, or you’re just sharing the knowledge to the community?

[andrew wilcoxParticipant]

Hi Artem,

Just sharing the issue and hoping for a fix in the near future.
Andrew.

[Author]

Replies