When you run ETL to load data from a source system into the Oracle Business Analytics Warehouse, it is possible that you may 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 healthcheck ETL phase. These issues need to be fixed 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. Able to connect to source or target database but the query fails to run due to lack of temp space, disk space, and so on. For files it could due to inadequate space where the file needs 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 would require 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. For information about automatic correction and restart, see About Diagnostics Healthcheck and ETL Diagnostics and Automatic Correction.