Start receiving ORA-01291: missing log file for present file

Petar Partlov

unread,

Mar 20, 2023, 9:08:28 AM3/20/23

to debezium

Hi, I suddenly start receiving ORA-01291: missing log file for arc files on oracle which actually exists.

Part of log:

2023-03-20 08:42:37,318 DEBUG [prod-debezium-psrf-connector|task-0] [649905, /u01/fra/PSRF_8/archivelog/2023_03_20/o1_mf_1_649905_l1h4b3t3_.arc, 2023-03-20 01:45:28.0, 2023-03-20 01:48:33.0, 4223892512, PSRF, 61730001712, 2018-10-17 17:38:07.0, 19.0.0.0.0, 1, 649905, 8916854783858, 8916855139610, NO, NO, ARCHIVE, 512, 4364270080, null, 2, 0] (io.debezium.connector.oracle.logminer.LogMinerDatabaseStateWriter) [debezium-oracleconnector-prod_cdc_psrf-change-event-source-coordinator]
2023-03-20 08:42:37,318 DEBUG [prod-debezium-psrf-connector|task-0] [649906, /u01/fra/PSRF_8/archivelog/2023_03_20/o1_mf_1_649906_l1h4c6js_.arc, 2023-03-20 01:48:33.0, 2023-03-20 01:49:04.0, 4223892512, PSRF, 61730001712, 2018-10-17 17:38:07.0, 19.0.0.0.0, 1, 649906, 8916855139610, 8916855180886, NO, NO, ARCHIVE, 512, 2273798656, null, 2, 0] (io.debezium.connector.oracle.logminer.LogMinerDatabaseStateWriter) [debezium-oracleconnector-prod_cdc_psrf-change-event-source-coordinator]
2023-03-20 08:42:37,318 DEBUG [prod-debezium-psrf-connector|task-0] [649907, Missing log file(s) for thread 1, sequence(s) 649907 to 649907, 2023-03-20 01:49:04.0, 2023-03-20 01:49:06.0, 4223892512, null, 61730001712, 2018-10-17 17:38:07.0, 19.0.0.0.0, 1, 649907, 8916855180886, 8916855183132, NO, NO, ARCHIVE, 512, 2273798656, MISSING_LOGFILE, 4, 0] (io.debezium.connector.oracle.logminer.LogMinerDatabaseStateWriter) [debezium-oracleconnector-prod_cdc_psrf-change-event-source-coordinator]
2023-03-20 08:42:37,318 DEBUG [prod-debezium-psrf-connector|task-0] [649908, /u01/fra/PSRF_8/archivelog/2023_03_20/o1_mf_1_649908_l1h4f2q1_.arc, 2023-03-20 01:49:06.0, 2023-03-20 01:50:03.0, 4223892512, PSRF, 61730001712, 2018-10-17 17:38:07.0, 19.0.0.0.0, 1, 649908, 8916855183132, 8916855288316, NO, NO, ARCHIVE, 512, 4370205696, null, 2, 0] (io.debezium.connector.oracle.logminer.LogMinerDatabaseStateWriter) [debezium-oracleconnector-prod_cdc_psrf-change-event-source-coordinator]
2023-03-20 08:42:37,318 DEBUG [prod-debezium-psrf-connector|task-0] [649909, /u01/fra/PSRF_8/archivelog/2023_03_20/o1_mf_1_649909_l1h4h0sr_.arc, 2023-03-20 01:50:03.0, 2023-03-20 01:51:02.0, 4223892512, PSRF, 61730001712, 2018-10-17 17:38:07.0, 19.0.0.0.0, 1, 649909, 8916855288316, 8916855371632, NO, NO, ARCHIVE, 512, 4354325504, null, 2, 0] (io.debezium.connector.oracle.logminer.LogMinerDatabaseStateWriter) [debezium-oracleconnector-prod_cdc_psrf-change-event-source-coordinator]

Here are available files:

I can actually start mining session manually and see this file, but not sure why debezium can't.

There are also 2 more files in current batch reported as missing, but they are present on server.

Petar Partlov

unread,

Mar 20, 2023, 10:39:13 AM3/20/23

to debezium

I found out that DEST_ID in V$ARCHIVED_LOG for all missing files has incorrect value, and that's why they are filtered out.

We are investigating issue now to see what that happened.

Javierchik Paz Zagaceta

unread,

Mar 20, 2023, 12:08:59 PM3/20/23

to debezium

Are you using RAC ? or maybe you make a failover.

Petar Partlov

unread,

Mar 20, 2023, 12:31:09 PM3/20/23

to debezium

Database was switched to standby during the night. We don't use RAC.

I suppose that is and issue. Strange that only for 3 arc files DEST_ID is set to wrong value.

Javierchik Paz Zagaceta

unread,

Mar 20, 2023, 1:47:20 PM3/20/23

to debezium

So thats why, in your STBY the DEST_ID is diferent, and these 3 where created on the STNBY and then replicated.

select distinct(DEST_ID) from v$archived_log

Reply all

Reply to author

Forward