- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 63 Insurance
- 535.7K On-Premises Infrastructure
- 138.1K Analytics Software
- 38.6K Application Development Software
- 5.6K Cloud Platform
- 109.3K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71K Infrastructure Software
- 105.2K Integration
- 41.5K Security Software
Have the mapping not fail if the source data file is absent
Does anybody have any recommendations on how to handle a situation in ODI when a flat file that mapping first loads from (first interface between the flat file datastore and a staging table datastore) is absent and not have the mapping fail, but rather have the rest of the package continue on?
A typical use case would be:
Our package deals with loading a bunch of files that come in as a batch.
Everything get loaded into target tables as a full replace (truncate / control append).
Some days only some of the files may come in. The others may not.
In cases like that, we would not want the whole package to trip up on the absent file, but rather keep the target table intact (not truncate, i.e. use previous days' data), but we would load the other target tables whole new flat data files did come in.