Pega BIX extract - No instance found in database error in Pega Infinity 24.1.1
Hi Team,
We are currently using Pega Infinity 24.1.1 version. We are trying to extract few data columns to csv format and using BIX to achieve this.We have installed BIX 8.24.03 version and when I run the extract it display no instance found in the database.
NOTE: not running BIX from command-line. We are running the extract rule from Application.
We have gone through this support articles - https://support.pega.com/question/pega-bix-extract-no-instance-found-database-error and https://support.pega.com/question/pega-extract-no-instance-found-database
Any suggestions to resolve the error.
Maantic Technologies Pvt Ltd
US
Hi @upgrade24,
Hope you are doing well.
Here are a few things you can check and try to resolve the issue:
Hi @upgrade24,
Hope you are doing well.
Here are a few things you can check and try to resolve the issue:
1. BIX Configuration and Settings
- Check the Extract Rule Configuration: Ensure the extract rule is correctly configured. Check that it’s pointing to the correct class and data you intend to extract.
- Check Extract Condition (if any): If you have defined any filters or conditions in the extract, make sure they are correct. You might be unintentionally limiting the scope of the data being extracted.
2. Data Availability
- Verify Data in Database: Confirm that there are indeed records available in the database that meet the criteria specified by the extract rule.
- Check the Target Class: Make sure that the class you're trying to extract data from has data instances in it.
- Refresh the Database Connection: In some cases, the database connection might not be updated or synchronized properly. You can try to refresh or revalidate the database connection in Pega.
3. BIX Extraction Process
- Log Files: Check the BIX log files for any errors or warning messages that might indicate why no data is being extracted.
- You can check these logs in the Pega log files for any related issues or exceptions.
- Run a Simple Extract: Try running a simpler extract (without complex filters or conditions) to see if it returns any data. This can help rule out issues with the extract setup itself.
4. Permissions and Access
- Access to Data: Ensure that the BIX process has the appropriate permissions to read the data from the relevant tables or classes.
- Access to the Extract Rule: Verify that the user running the extract has sufficient privileges to execute the extract rule.
5. Database Schema and Compatibility
- Database Schema Version: Verify that your BIX installation is compatible with the version of the database you're using.
- Check for Indexing Issues: In some cases, Pega’s database schema might need indexing for faster and correct data retrieval.
6. Pega Version Compatibility
- Version Compatibility: Double-check that Pega Infinity 24.1.1 and BIX 8.24.03 are fully compatible. Sometimes BIX versions might have dependencies on certain versions of Pega, and there could be bugs or limitations in the integration.
7. Correct Extract Format
- CSV Format: Ensure that the extract rule is configured to output in CSV format, and that it’s being executed correctly.
Thank You
HCA Healthcare
US
@upgrade24 The "No instance found in the database" error in Pega BIX when running an extract rule in Pega Infinity 24.1.1 can occur due to data availability issues or filter misconfigurations. First, ensure that the extract rule's class references the correct database table and verify if the necessary data exists in the database for the specified filters. Check the filter criteria in the extract rule to confirm that they align with the available data. Also, validate the BIX version compatibility with your Pega Infinity version, as you’re using BIX 8.24.03. Update to the latest patch of BIX if required. If you’re using a date filter, ensure it matches the data format and time zone in the database. Additionally, review the Pega logs (pega or bix log files) for more specific error details. If the issue persists, verify if the necessary database indexes exist for the extract rule's performance and correctness.