[Oracle] An error occurred in SCN when Oracle was synchronizing CLOB type fields.

[Apollo Elon]

Ask for help !!!

【 Debezium version:  1.9.8.Final 】

When I attempted to synchronize the clob type field of Oracle through lob.enabled=true, I found that if there was no clob type field in my table, an SCN-related error would occur, and SCN would be set to a value that existed in oracle. I will add more detailed error messages later. 

[Chris Cranford]

Hi -

Can you please provide your complete connector configuration and the full stack trace of the error when you provide the additional details?

Thanks
-cc

On 8/6/25 12:13 PM, Apollo Elon wrote:

Ask for help !!!

【 Debezium version:  1.9.8.Final 】

When I attempted to synchronize the clob type field of Oracle through lob.enabled=true, I found that if there was no clob type field in my table, an SCN-related error would occur, and SCN would be set to a value that existed in oracle. I will add more detailed error messages later.  --
You received this message because you are subscribed to the Google Groups "debezium" group.
To unsubscribe from this group and stop receiving emails from it, send an email to debezium+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/debezium/c9bfe79e-629e-4b7a-bccc-6c7cd0cee313n%40googlegroups.com.

[Apollo Elon]

Yes, thank you very much for paying attention to my question. I will describe in detail the problem I encountered.
I am currently using flink-cdc(v3.3) to synchronize oracle's data from the library to kafka. The debezium version used at the bottom layer of flink-cdc is v1.9.8.Final. The debezium parameter I passed in when constructing OraclSource is:
{
       "decimal.handling.mode" = "string"
       "include-comment-changes" = "true"
        "include-schema-changes" = "true"
       "log.mining.strategy" = "online_catalog"
       "lob.enabled" = "true"
        "message.key.columns" = "ORCL.TB:ID"
}
My table creation statement is:
create table ORCL.TB
(
INVENTORY_DETAID     NUMBER(30) not null,
INVENTORYDETA_REL_ID NUMBER(30) not null,
ID                   NUMBER(14)
)
It is worth noting that there is no clob type field in my table. I have already placed the error message of the program after startup in the attachment. I know that since flik-cdc was introduced in the synchronization, the error might not have been caused by debezium, but I can't find a solution to the problem now and can only look for answers in both communities. In the absence of an upgrade to the debezium version, how can I solve this problem? Do I need to merge some code from the higher version or add some configuration to solve it? Thank you again for paying attention to my question !!!

[Chris Cranford]

Hi,

Thank you now I understand.

The ORA-01291 (missing log file) error can happen when an archive log is removed physically from the file system in the Oracle archive destination, but the log catalog was not synchronized with the file system state. When this happens, Debezium sees the log file, adds it to the LogMiner queue to be read, and then LogMiner fails and throws ORA-01291 because the file is not present on disk.

You should contact your DBA and have them perform an RMAN cross-check because the log catalog appears to be out of sync with the file system.

Thanks
-cc

To view this discussion visit https://groups.google.com/d/msgid/debezium/e467b587-112b-4d98-af43-2908c178a95an%40googlegroups.com.

[Apollo Elon]

Thank you very much for your help. We have now contacted the DBA to pay attention to this issue. After this practice, we will use Debezium to directly replace flink-cdc to synchronize data to Kafka in the future. Thanks to Debezium for such a great project 🎉🎉.