Issues that prevent data generation
The following issues prevent a data generation or subsetting job.
Structural and workspace access or permissions
Issue | Description | How to resolve |
---|---|---|
Structural license expired | The current Structural license is expired. | |
No workspace configured | The Structural instance does not have any workspaces to generate data from. | |
Insufficient workspace permissions | You do not have permission to run data generation on this workspace. |
Source and destination data availability
Issue | Description | How to resolve |
---|---|---|
Unable to connect to the source database | The source database connection is either missing or incomplete. | Edit the workspace configuration to complete the source database connection. Make sure to test the connection. |
Unable to connect to the destination database | The destination database connection is either missing or incomplete. | Edit the workspace configuration to complete the destination database connection. Make sure to test the connection. |
Only for licenses that have a configured size limit - The source database size exceeds the maximum allowed | Only applies to licenses that are configured to enforce a maximum data size. When a Structural license is configured with a maximum source database size, then if the source database is larger than that maximum, the generation fails. | Reduce the size of the source database. |
Table mode and generator configuration
Issue | Description | How to resolve |
---|---|---|
Scale mode - Invalid generators | A table that uses Scale mode has columns with assigned generators that are not valid for Scale mode. | Change the selected generator for the columns. |
Scale mode - Passthrough generator or sub-generator for the Conditional generator | A table that uses Scale mode has columns that use the Conditional generator, and that are assigned Passthrough as a generator or sub-generator. | Change the selected generator, sub-generator, or default generator. |
Preserve Destination - cannot resolve foreign key references | A table that uses Preserve Destination mode is referenced from another table. | |
Truncate - cannot resolve foreign key references | A table that uses Truncate mode is referenced from another table. | |
Cross Table Sum - incomplete generation | A column is assigned the Cross Table Sum generator, but some required configuration field values are missing. | |
Incremental mode - circular foreign key dependency | There is a circular foreign key dependency between tables that use Incremental mode. |
Schema changes
Issue | Description | How to resolve |
---|---|---|
Unresolved schema changes | There are detected schema changes that are not resolved. |
Subsetting configuration
The following errors occur when you attempt to generate a subset. They do not apply if Use subsetting is turned off.
Issue | Description | How to resolve |
---|---|---|
No target tables configured | The subsetting configuration does not include any target tables. | |
Invalid target table configuration | A target table has an invalid percentage value or | |
In-subset table uses Scale mode | A table that is in the subset uses Scale table mode. | |
In-subset table uses Truncate mode. | A table that is in the subset uses Truncate table mode. | |
In-subset table uses Preserve Destination mode. | A table that is in the subset uses Preserve Destination table mode. | |
In-subset table uses Incremental mode. | A table that is in the subset uses Incremental table mode. |
Upsert issues
When upsert is enabled, the following issues cause the upsert job to fail.
Issue | Description | How to resolve |
---|---|---|
Destination database not populated | The destination database is empty. | Update the workspace to disable upsert, then run a regular data generation job to populate the destination database. You can then re-enable upsert. |
Invalid table mode | A table is assigned a mode other than De-Identify or Truncate. | Change the table mode to De-Identify or Truncate. |
Unable to connect to the intermediate database | The intermediate database connection is either missing or incomplete. | Edit the workspace configuration to complete the intermediate database connection. |
Unresolved schema conflicts | There are schema conflicts between the source and destination databases. | Update the source or destination database schema to resolve the changes. |
Last updated