Hi Ken, to add up to previous suggestions, if you're still struggling of course..
> Now that you kind people have pointed me in the right direction as far > as log-bin was concerned, I've moved on to trying to replicate the > databases from the primary to the secondary. > > I've created the connection profile and started the secondary > connection, but when I ran > > show slave 'master01' status\G > > I got the following error: > > Last_Errno: 1062 > Last_Error: Could not execute Write_rows_v1 event on table > databasename.oc_filecache; Duplicate entry '110' for key 'PRIMARY', > Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's > master log master-bin.00000#, end_log_pos ###### > > How do I resolve this duplicate entry error? And do I need to do the > same resolution on the primary as well? For some reason the slave could not execute the SQL statement. There's nothing to do on the master side but to examine its binlog, especially when your slave has binlogging ON. Execute mysqlbinlog -v on relevant binlog files of the both sides and look after records with the PK of the failed one. Most probably you'll soon find a discrepancy between the log on the record. E.g a DELETE operation was not applied on slave while it was done (so binlogged) om master. > > Ubuntu Server 23.10, mariadb version 15.1 Distrib 10.11.6-MariaDB > > Ken Cheers, Andrei _______________________________________________ discuss mailing list -- [email protected] To unsubscribe send an email to [email protected]
