Data indexing error: Dim table corruption found on dimension table [Linux]
If you’re seeing error code 9300 with a “Data indexing error” message regarding dimension table corruption in Sisense for Linux, this guide will help you understand the cause and walk you through potential resolutions. Applies to Sisense version for both cloud and on-premises deployments. L2024.3
Step-by-Step Guide:
This error arises due to Sisense’s internal build validations, specifically the RelationDimTablesValidation check. This validation ensures all dimension tables used in table relations contain all possible key values, maintaining data integrity during query execution. More details on these checks are available in the Sisense documentation.
Recommended Solutions:
- Enable Build Retry: Automatically retry builds after a failure to resolve temporary issues without manual input.
How to enable Build Retry:
- Navigate to: Admin > System Management > Configuration
- Unlock additional build settings: Click the Sisense logo 5 times.
- Enable build retry: Set RetryBuild.value = true.
How Build Retry works:
The NumberOfBuildRetries parameter defines how many automatic retries occur after a failure (default is 0, meaning no retries unless set). When enabled, only the latest build logs remain after a retry.
Configuring retry parameters:
- Set NumberOfBuildRetries (number of attempts).
- Set WaitTimeAfterBuildFailedBeforeRetry (default: 60 seconds).
- Click “Save Changes” to apply.
- Disable Validations; If retries do not help and the error persists, disable specific validation checks one-by-one to identify the problematic one:
- DataIndexingValidation
- RelationDimTablesValidation
- IndexingDimTablesValidation
How to disable validations:
- Go to: Admin > System Management > Configuration
- Click the Sisense logo 5 times to unlock hidden settings.
- Scroll to the Build section.
- Set the relevant validation flags to false.
- Save changes.
Conclusion:
Sisense’s data integrity checks are designed to prevent the use of inconsistent data. If you encounter error 9300 related to dimension tables, enabling build retries or selectively disabling validations can resolve these issues. Always track changes and test in your environment before applying these solutions broadly.
References/Related Content
Disclaimer: This post outlines a potential custom workaround for a specific use case or provides instructions regarding a specific task. The solution may not work in all scenarios or Sisense versions, so we strongly recommend testing it in your environment before deployment. If you need further assistance with this, please let us know.
