For retirement projects, the Data Vault Loader process runs for days.
When you build retirement entities, do not use one entity for all of the source tables. If an entity includes a large number of tables, the Data Vault Loader may have memory issues. Create one entity for every 200-300 tables in the source application.
You can use a wizard to automatically generate entities. Or, you can manually create entities if you want the entities to have special groupings, such as by function or size.
When you create entities with smaller amounts of tables, you receive the following benefits:
The Data Vault Loader job performance increases.
Reduces staging space requirement as the retirement project uses less staging space.
You can resolve code page configuration issues earlier.
You can start to validate data earlier with the Data Validation Option.
Overall, provides better utilization of resources.
The Data Vault Loader job fails when Dynamic Data Masking connection details are used in the target connection.
Before you run the loader, change the target connection port in the