The CHARACTER/CHARACTER(p)/CHARACTER VARYING(p) data types not recognized as JDBC type CHAR

When a DDL event is captured during the streaming phase and the table contains a column that uses the CHARACTER data type, the Oracle DDL parser does not recognize this as a JDBC type CHAR data type, and instead maps it as OTHER. The net outcome is that the column's values are not propagated by the connector.

The Oracle DDL parser should map CHARACTER column data types just like it does CHAR.