if we can issue it without too many false positives, that is
So the docs say when compatibility is set to 12.2 or higher, table/column names can be up to 128 bytes in length rather than 30 bytes.
We can check this compatibility setting via SQL but that doesn't seem to matter when looking at an Oracle 12 R2 db (my local instance is set to 12.2.0 compatibility by default).
People have reported that Streams, Xstreams, and LogMiner were not adjusted; only that users can create tables with names using the longer lengths.
I'll check Oracle 19 to be sure whether it exhibits the same limitation.
database.history.skip.unparseable.ddl=true; so we need to fix the grammar bug you've illustrated, thanks!