metricsign
Start free
High severityresource

Power BI Refresh Error:
1197

What does this error mean?

A large transaction exceeded the binary log cache size limit — the transaction cannot be written to the binlog.

Common causes

  • 1A single large transaction (e.g., bulk INSERT or UPDATE) generates more binlog data than max_binlog_cache_size allows
  • 2ADF bulk inserts are not batched into smaller transactions
  • 3dbt full-refresh materializations on large tables generate a single massive transaction

How to fix it

  1. 1Step 1: Check the current limit: `SHOW VARIABLES LIKE 'max_binlog_cache_size';`
  2. 2Step 2: Increase it: `SET GLOBAL max_binlog_cache_size=2147483648;` (2GB) and add to my.cnf.
  3. 3Step 3: Break large transactions into smaller batches — process in chunks of 10,000-100,000 rows per transaction.
  4. 4Step 4: In dbt, use incremental materializations instead of full refresh to avoid single large transactions.

Frequently asked questions

Does this error mean my data was not committed?

Yes — MySQL rolls back the entire transaction when it exceeds max_binlog_cache_size. No data from that transaction is saved. You must retry with smaller batch sizes.

Can I disable binary logging to avoid this limit?

Yes: `SET SQL_LOG_BIN=0;` for the session disables binlog for that connection. Only do this if you do not need replication or point-in-time recovery for this load.

Can MetricSign detect when this error breaks an ADF pipeline?

Yes — MetricSign captures ADF pipeline failures and surfaces the MySQL error code in the incident detail, immediately alerting you to binlog cache exhaustion.

Official documentation: https://dev.mysql.com/doc/mysql-errors/8.0/en/server-error-reference.html

Other resource errors