Skip to content
Contact us Go to Customer Portal
  • There are no suggestions because the search field is empty.

Generators Release - 2.4.1

26/10/2026

Generator 2.4.1 fixes issues found in Generator 2.4.0. It updates the generators listed below. The other generators have no changes in this release.

Affected generators

  • Data Vault and the combined VaultAndMart generator, on all platforms
  • Data Store, on all platforms
  • Stage and Data Mart, on Oracle only

Data Vault

  • Fixed validation warning ID-10065 for Driving Key Links and Business Driving Key Links with more than one dataflow. The hashing table of each dataflow now gets its own name, for example RDV_DKLNK_<model object>_<dataflow>_HashingTable, as for Links. Only the name shown in the model changes. The generated artifacts stay the same. See Create a Driving Key Link.

Data Store

  • Fixed delete detection with Delete Detection Method PartialSet on Store Entities with SCD2 history. A key is now a deletion candidate only if its current version has a partial-term value that the load delivers. Earlier versions of the key are ignored.
  • Example: customer 3 moved from DE to CH, and a load delivers only DE. Generator 2.4.0 marked customer 3 as deleted because of its old DE version. Generator 2.4.1 leaves customer 3 unchanged. See Configure delete detection.

Oracle

These fixes apply to all Oracle generators: Stage, Data Store, Data Vault, Data Mart and VaultAndMart.

  • Fixed deployment of tables with a Partition Clause and a bitmap index. Oracle requires bitmap indexes on partitioned tables to be local (ORA-25122). Default and custom bitmap indexes on these tables are now created as local indexes.
  • Create as local Index now creates a local custom index on tables with a Partition Clause. On tables without a Partition Clause the setting is ignored, and validation warning ID-33001 reports this. Generator 2.4.0 also showed this warning for model objects with a Partition Clause. See Add an Index.

Before you upgrade

  • Data Vault. No action is required. After the update, the model shows the new hashing table names.
  • Data Store delete detection. Regenerate and deploy Store Entities that use PartialSet with SCD2 history. This fixes future loads only. Rows that earlier loads marked as deleted stay in the history. Check these Store Entities for keys that a 2.4.0 load marked as deleted although the load did not deliver the partial-term value of their current version.
  • Oracle indexes. Regenerate and deploy model objects that have a Partition Clause and a bitmap index or an index with Create as local Index.