Another example

CREATE TABLE t1(a CHAR) ENGINE=InnoDB;

BINLOG ' O1ZVRw8BAAAAZgAAAGoAAAAAAAQANS4xLjIzLXJjLWRlYnVnLWxvZwAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAA7VlVHEzgNAAgAEgAEBAQEEgAAUwAEGggAAAAICAgC ';  # Table_map

BINLOG 'wlZOTxMBAAAAKgAAADwCAAAAACkAAAAAAAEABHRlc3QAAnQxAAIDAwAC wlZOTxcBAAAAJgAAAGICAAAAACkAAAAAAAEAAv/8AgAAAAgAAAA=';  # Format description

Whilst not commonly used SQL at the CLI, it highlights the issue well. At the CLI this gives:

10.9.0-dbg>BINLOG 'wlZOTxMBAAAAKgAAADwCAAAAACkAAAAAAAEABHRlc3QAAnQxAAIDAwAC wlZOTxcBAAAAJgAAAGICAAAAACkAAAAAAAEAAv/8AgAAAAgAAAA=';  # Format description

ERROR 1105 (HY000): Unknown error

Which is cryptic at best. However the error log clearly explains the issue:

2022-03-12 16:02:49 4 [ERROR]  BINLOG_BASE64_EVENT: Column 0 of table 'test.t1' cannot be converted from type 'int' to type 'char(1 octets) character set latin1', Internal MariaDB error code: 1677

Interestingly, there is another error code here too. Elkin fyi in case that's a bug.

Similar to the last example (same output):

BINLOG 'wlZOTw8BAAAA8QAAAPUAAAAAAAQANS41LjIxLU1hcmlhREItZGVidWctbG9nAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAEzgNAAgAEgAEBAQEEgAA2QAEGggAAAAICAgCAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA371saA==';

CREATE TABLE t1(a INT KEY,b CHAR (1));

BINLOG 'wlZOTxMBAAAAKgAAAGMBAAAAgCkAAAAAAAEABHRlc3QAAnQxAAIDAwAC wlZOTxcBAAAAJgAAAIkBAAAAgCkAAAAAAAEAAv/8AQAAAAgAAAA=';

Please also try this testcase against any bug fix

CREATE TABLE t (c INT) ENGINE=InnoDB;

ALTER TABLE t DISCARD TABLESPACE;

ALTER TABLE t ADD INDEX (c);

SELECT * FROM t;

investigating it

The error message for the example given in the body part of this Jira is already informative: https://github.com/MariaDB/server/blob/3883eb63dc5e663558571c33d086c9fd3aa0cf8f/storage/innobase/dict/dict0load.cc#L2234

Execution result in the database:

{{Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 4
Server version: 11.1.2-MariaDB Source distribution

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> show databases;
--------------------

--------------------

--------------------
1 row in set (0.000 sec)

MariaDB [(none)]> create database zhibo;
Query OK, 1 row affected (0.001 sec)

MariaDB [(none)]> use zhibo;
Database changed
MariaDB [zhibo]> CREATE TABLE t (i INT KEY);
Query OK, 0 rows affected (0.007 sec)

MariaDB [zhibo]> ALTER TABLE t DISCARD TABLESPACE;
Query OK, 0 rows affected (0.002 sec)

MariaDB [zhibo]> SELECT * FROM t;
ERROR 1814 (HY000): Tablespace has been discarded for table `t`}}

According error log:

2023-06-19 15:11:10 3 [Warning] InnoDB: Tablespace for table `zhibo`.`t` is set as discarded.

Reproduction of the second case mentioned in the comments:

```
MariaDB [test]> CREATE TABLE t1(a CHAR) ENGINE=InnoDB;
Query OK, 0 rows affected (0.007 sec)

MariaDB [test]> BINLOG ' O1ZVRw8BAAAAZgAAAGoAAAAAAAQANS4xLjIzLXJjLWRlYnVnLWxvZwAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAA7VlVHEzgNAAgAEgAEBAQEEgAAUwAEGggAAAAICAgC '; # Table_map
Query OK, 0 rows affected (0.000 sec)

MariaDB [test]> BINLOG 'wlZOTxMBAAAAKgAAADwCAAAAACkAAAAAAAEABHRlc3QAAnQxAAIDAwAC wlZOTxcBAAAAJgAAAGICAAAAACkAAAAAAAEAAv/8AgAAAAgAAAA='; # Format description
ERROR 1105 (HY000): Unknown error
```

In the error log:
2023-06-19 16:47:06 5 [ERROR] BINLOG_BASE64_EVENT: Column 0 of table 'test.t1' cannot be converted from type 'int' to type 'char(1 octets) character set latin1', Internal MariaDB error code: 1677

zhibozhang You can use {noformat} tags in JIRA.

In 11.1.2 rev 3883eb63dc5e663558571c33d086c9fd3aa0cf8f the Got error 194 seen with the original testcase is confirmed gone. However, the error remains for this testcase:

CREATE TABLE t (c INT) ENGINE=InnoDB;

ALTER TABLE t DISCARD TABLESPACE;

ALTER TABLE t ADD INDEX (c);

SELECT * FROM t;

Leads to:

2023-06-28 12:34:03 4 [ERROR] Got error 194 when reading table './test/t'

Which now makes me wonder if there is another issue/error at play here.

The place where error code 194 is defined https://github.com/MariaDB/server/blob/1a5e69b42b4ff0a3fd4585f1463adf01127241cd/include/my_base.h#L533

Error code 194 uses a default error message as shown in https://github.com/MariaDB/server/blob/d039346a7acac7c72f264377a8cd6b0273c548df/sql/unireg.h#L53

We need to replace the default error message with a customized error message for error code 194 in this line https://github.com/MariaDB/server/blob/b0e77c08e55c433e443a2cfbcb7315dd6f006b3e/sql/handler.cc#L498