Binary logging not possible

KB Home   |   Binary logging not possible

Main.BinaryLoggingNotPossible History

Hide minor edits - Show changes to output

Added lines 15-16:
Please confirm with your database administrator before making this change.
Changed line 16 from:
''Categories:'' [[Category.Misc+]],
''Categories:'' [[Category.Databases+]],
Changed lines 3-4 from:
When upsizing to Microsoft SQL server you may encounter the following error message with some configurations.
Added lines 1-17:
(:title Binary logging not possible:)

[@SQL state [HY000]; error code [1598]; Binary logging not possible. Message:@]
[@Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode@]
[@'STATEMENT'; nested exception is java.sql.BatchUpdateException: Binary logging@]
[@not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not@]
[@safe for binlog mode 'STATEMENT@]

Customers who encounter the above error when using Microsft SQL server may need to run the following SQL command:

[@SET GLOBAL binlog_format = 'ROW'@]

''Categories:'' [[Category.Misc+]],
[-Keywords: -]


Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on October 31, 2014, at 05:57 AM
Printable View   |   Article History   |   Edit Article