Troubleshooting "BBP Error 1551" in Sisense ElastiCube Builds
Summary
This article provides a comprehensive guide to troubleshooting the "BBP error 1551" that occurs during the build process of ElastiCubes in the Sisense Windows environment. The error typically indicates a discrepancy between the logical schema and the actual result of the ElastiCube, leading to build failures.
Main Content
Step-by-Step Instructions to Resolve the Issue
- Identify the Error:
- The BBP error '1551' indicates a mismatch between the logical schema and the actual data/indexes in the ElastiCube. This is done to prevent inconsistencies.
- Initial Troubleshooting Steps:
- Run Build Schema Changes:
- After creating a Custom Table, run Build Schema Changes.
- Add the Relationship and run Build Schema Changes again.
- Run Full Build:
- Perform a Full Build (Replace All) to ensure all data and indexes are correctly aligned.
- Check Logs for Detailed Error Information:
- Build Process Logs: %ProgramData%\SiSense\PrismServer\ElastiCubeProcessLogs\
- ElastiCube Server Logs: %ProgramData%\Sisense\PrismServer\PrismServerLogs\
- Review these logs to identify any specific issues or patterns that may be causing the build failure.
- Frequency and Environment Check:
- Determine how often the scheduled build runs and how frequently it fails with this error.
- If possible, duplicate the ElastiCube or create a new one for testing purposes and set its schedule to be more frequent. Observe if the issue's frequency increases.
- Accumulative Build Check:
- If the error occurs during an accumulative build, consider running a Full Build (Replace All) to reset the schema and data alignment.
Troubleshooting Tips and Alternative Solutions
- No Recent Changes:
- If no changes have been made to the ElastiCube and the error persists, it may be necessary to investigate any underlying system or environmental changes that could affect the build process.
- Monitor and Report:
- Continuously monitor the build process after implementing the above steps.
- If the issue reoccurs, provide detailed logs and error messages to the support team for further analysis.
Check out this related content:
