Announcement

Announcement Module
Collapse
No announcement yet.

5.0 -> 5.5 Replication Problems

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • 5.0 -> 5.5 Replication Problems

    Hi!
    I'm preparing 5.0 to 5.5 migration, so the replication is the first step.

    Master: 5.0.67
    Slave: 5.5.16

    I get different unclear warnings at the slave as follow:


    [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them. Statement: UPDATE im_config SET conf_value = '602' WHERE config_name = 'ReplDelay'

    The matter is that im_config is an InnoDB table.


    [Warning] Invalid (old?) table or database name '#sql-12a6_34'

    Probably this is a temporary table. Where does it come to light from? I haven't such warning in 5.0 to 5.0 replication.

  • #2
    DenisM wrote on Tue, 01 November 2011 13:07
    The matter is that im_config is an InnoDB table.
    It seems the warning results from trigger which inserts into a MyISAM table.

    Comment


    • #3
      DenisM wrote on Tue, 01 November 2011 13:07

      [Warning] Invalid (old?) table or database name '#sql-12a6_34'
      This follows OPTIMIZE TABLE.

      Comment

      Working...
      X