Redo logs get rotated, archived, backed-up and deleted automatically in an standard Oracle setup. This means that redo log are not always available for old data. In general terms, you should make sure you are ingesting a time range still available in redo logs. If unsure, you can query view v$log and v$archived_log, and check then columns first_time and next_time. At first glance, it looks as if you are trying to ingest data “too” old in terms of redo logs lifecycle.  

Thanks for your inputs. May I know where I need to check for v$log and v$archived_log.

@Haripriya Those are Oracle system views. Please, refer to Oracle’s official documentation for further details.