Details
-
Feature Request
-
Resolution: Not a Bug
-
Major
-
None
-
1.7.1.Final
-
None
-
False
-
None
-
False
-
0
-
0%
Description
In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
<1.7.1.final>
What is the connector configuration?
<oracle-connector>
What is the captured database version and mode of depoyment?
(E.g. on-premises, with a specific cloud provider, etc.)
<local>
Hello, I deployed the debezium source code environment in idea and used the debezium server mode to run. When monitoring Oracle, I found a problem about time type:
When debezium executes "select SCN, sql_redo from V $logmnr_contents", the "sql_redo" value queried is the same as the SQL I queried in the local test code_ Redo time is not right
The result of debezium query is:
"update "INMON"."TZ_DBZ_TD" set "t_date" = TO_DATE('2022-04-28 15:02:16', 'YYYY-MM-DD HH24:MI:SS') where "id" = '4' and "t_date" = TO_DATE('2022-04-28 15:02:14', 'YYYY-MM-DD HH24:MI:SS') and "t_timestamp" = TO_TIMESTAMP('2022-04-28 15:02:19.') and "t_tz" = TO_TIMESTAMP_TZ('2022-04-28 15:02:19.000000 +08:00') and "t_tlz" = TO_TIMESTAMP_TZ('2022-04-26 19:33:22.555555');"
The results I found in the local test environment:
"update "INMON"."TZ_DBZ_TD" set "t_date" = TO_DATE('28-4月 -22', 'DD-MON-RR') where "id" = '4' and "t_date" = TO_DATE('28-4月 -22', 'DD-MON-RR') and "t_timestamp" = TO_TIMESTAMP('28-4月 -22 03.02.19 下午') and "t_tz" = TO_TIMESTAMP_TZ('28-4月 -22 03.02.19.000000 下午 +08:00') and "t_tlz" = TO_TIMESTAMP_TZ('27-4月 -22 03.33.22.555555 上午')"
My question is: why does the "sql_redo" queried by debezium contain the time field to_ Timestamp ('2022-04-26 19:33:22.555555 '), which I found locally, is indeed to_ For the format of timestamp ('28-april-22 03.02.19 PM '), did you convert the format during the query?
Second question: according to the comparison between the results of debezium and the local query above, it can be found that the time of "t_tlz" field is not right. The local query is "3:33:32.555555" and T in the database table_ The tlz field value is the same, but debeizum finds that "19:33:32.555555" does not match the field value of the database table
Forget to add that the "t_tlz" field type is "timestamp with local time zone"