When you run ETL to load data from a source system into the Oracle Business Analytics Warehouse, you might need to restart the ETL load after a failure. This section explains the options available for restart and describes the implications of using each of those options.
Examples of circumstances and reasons for load plan failure include the following:
Issues identified in the health check ETL phase. Fix these issues before restarting the load plan.
Problem with access either to source or target database due to network failure or expired or otherwise incorrect user names and passwords.
Failure of ODI agent.
Problem with space or storage. You can connect to the source or target database, but the query fails to run due to lack of temp space, disk space, and so on. It might be due to inadequate space where files need to be placed.
Problem with data, for example incorrect data with lengths larger than the target column can hold, or null values in Not Null columns.
After such a failure during ETL, to avoid restarting the entire load plan after a failure, which requires inefficient re-runs of all ETL tasks, you must restart the load from the same point in its execution once the cause of failure has been diagnosed and resolved. Some of these circumstances for failure are automatically diagnosed and resolved by ETL diagnostics and auto-correction. See About Diagnostics Health Check and ETL Diagnostics and Automatic.