[Oracle] Fix Oracle CDC fetch two different db name for the same table

[e-mhui]

Fix Oracle CDC fetch two different db name for the same table

• Fixes [Bug][Oracle] Oracle CDC fetch two different db name for the same  #2087

Motivation

If the database name configured for Oracle CDC in Flink SQL is lowercase, such as the following example ('database-name' = 'xe'),

CREATE TABLE products (
     ID INT NOT NULL,
     NAME STRING,
     DESCRIPTION STRING,
     WEIGHT DECIMAL(10, 3),
     PRIMARY KEY(id) NOT ENFORCED
     ) WITH (
     'connector' = 'oracle-cdc',
     'hostname' = 'localhost',
     'port' = '1521',
     'username' = 'flinkuser',
     'password' = 'flinkpw',
     'database-name' = 'xe',
     'schema-name' = 'FLINKUSER',
     'table-name' = 'TEST_03');

the following problems will occur:

1. For the same table (TEST_03)，the snapshot phase will use the lowercase database name (xe.FLINKUSER.TEST_03 ), and the incremental phase will use the uppercase database name (XE.FLINKUSER.TEST_03 ).
2. For the same table (TEST_03 ), after being captured in the snapshot phase, it will be captured again in the incremental phase because their database names are inconsistent.

In OracleConnectorConfig, the database name in Flink SQL is converted to uppercase, but the database name used in the snapshot phase is directly taken from Flink SQL. Therefore, when constructing the tableId, the database name in Flink SQL also needs to be converted to uppercase.

Modifications

When constructing the tableId, the database name in Flink SQL needs to be converted to uppercase.

[ruanhang1993]

@e-mhui Thanks for the contribution.
Please rebase the master branch. And the debezium version has been update to 1.9.7.Final. Could you help to check whether the error still exists?

Besides these, I think maybe we should use database name in upper case at the beginning. For example, in the constructor of the Source.

[e-mhui]

@e-mhui Thanks for the contribution. Please rebase the master branch. And the debezium version has been update to 1.9.7.Final. Could you help to check whether the error still exists?

Besides these, I think maybe we should use database name in upper case at the beginning. For example, in the constructor of the Source.

@ruanhang1993 Thanks you reply, it has rebased the mater branch. The error still exist in 2.4 and master branch. pls review it again.
In the incremental phase, debezium has already capitalized the database name, so I believe it is necessary to also do so in the snapshot phase.

[ruanhang1993]

LGTM. @e-mhui Please rebase master branch and let's pass the CI.

[e-mhui]

LGTM. @e-mhui Please rebase master branch and let's pass the CI.

Thanks, it has been done.

[e-mhui]

@ruanhang1993 Hi, pls review it.