Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

BIX extract error: no instance found in the database

SA-37406

Summary



User was attempting to run a ​Business Intelligence Exchange (BIX) extract on a cloud environment.

The class associated with the extract rule contain instances and the extract rule should find those instances.

However, when they run the extract it is reporting that no instances are found.


Error Messages

"No instance found in the database" error on the screen.

Steps to Reproduce



1. Log in as an operator that has access to the extract rule.
2. Open the extract rule.
3. From the Actions menu choose Run.
4. Click on the Perform Extract button.


Root Cause



Prior to an attempt to run the extract, the logging level was set to DEBUG for the following logger:

com.pega.pegarules.data.internal.access.ExtractImpl


During the run of the export this produced the following lines in the PegaRULES-BIX log:

2017-04-26 13:53:41,370 [ PegaRULES-Batch-1] [ STANDARD] [ BIXTest:01.01.01] ( internal.access.ExtractImpl) DEBUG bixtestadmin - Where Condition is:
2017-04-26 13:53:41,370 [ PegaRULES-Batch-1] [ STANDARD] [ BIXTest:01.01.01] ( internal.access.ExtractImpl) DEBUG bixtestadmin - sql statement is: SELECT pzPVStream FROM PEGADATA.pc_MyClass-Work WHERE pzInsKey like ? ORDER BY pzInsKey
2017-04-26 13:53:41,370 [ PegaRULES-Batch-1] [ STANDARD] [ BIXTest:01.01.01] ( internal.access.ExtractImpl) DEBUG bixtestadmin - Generated SQL: SELECT pzPVStream FROM PEGADATA.pc_MyClass-Work WHERE pzInsKey like ? ORDER BY pzInsKey <MYORGJOCFC-BIXTEST-WORK%>
2017-04-26 13:53:41,371 [ PegaRULES-Batch-1] [ STANDARD] [ BIXTest:01.01.01] ( internal.access.ExtractImpl) INFO bixtestadmin - Processing Class: MyOrgJOCFC-BIXTest-Work with 1 instances
2017-04-26 13:53:41,371 [ PegaRULES-Batch-1] [ STANDARD] [ BIXTest:01.01.01] ( internal.access.ExtractImpl) INFO bixtestadmin - BIX Version : 7.1
2017-04-26 13:53:41,374 [ PegaRULES-Batch-1] [ STANDARD] [ BIXTest:01.01.01] ( internal.access.ExtractImpl) DEBUG bixtestadmin - xml output file name : MyClass-Work_TestExtract2_14
2017-04-26 13:53:41,374 [ PegaRULES-Batch-1] [ STANDARD] [ BIXTest:01.01.01] ( internal.access.ExtractImpl) DEBUG bixtestadmin - xml schema file name : MyClass-Work_TestExtract2_14
2017-04-26 13:53:41,375 [ PegaRULES-Batch-1] [ STANDARD] [ BIXTest:01.01.01] ( internal.access.ExtractImpl) DEBUG bixtestadmin - xml manifest output file name : MyClass-Work_TestExtract2_14_manifest
2017-04-26 13:53:41,375 [ PegaRULES-Batch-1] [ STANDARD] [ BIXTest:01.01.01] ( internal.access.ExtractImpl) INFO bixtestadmin - XML Schema File MyClass-Work_TestExtract2_14 is created in //mymountpoint/tomcat/node1/temp/BIXTemp
2017-04-26 13:53:41,426 [ PegaRULES-Batch-1] [ STANDARD] [ BIXTest:01.01.01] ( internal.access.ExtractImpl) INFO bixtestadmin - XML File MyClass-Work_TestExtract2_14 is created in /mymountpoint/tomcat/node1/temp/BIXTemp
2017-04-26 13:53:41,431 [ PegaRULES-Batch-1] [ STANDARD] [ BIXTest:01.01.01] ( internal.access.ExtractImpl) DEBUG bixtestadmin - Number of row(s) skipped: 0
2017-04-26 13:53:41,433 [ PegaRULES-Batch-1] [ STANDARD] [ BIXTest:01.01.01] ( internal.access.ExtractImpl) INFO bixtestadmin - XML File MyClass-Work_TestExtract2_14_manifest is created in /mymountpoint/tomcat/node1/temp/BIXTemp
2017-04-26 13:53:41,433 [ PegaRULES-Batch-1] [ STANDARD] [ BIXTest:01.01.01] ( internal.access.ExtractImpl) INFO bixtestadmin - Node level information will not be added to the manifest when getAllProperties is selected in the extract rule form for XML extraction
2017-04-26 13:53:41,433 [ PegaRULES-Batch-1] [ STANDARD] [ BIXTest:01.01.01] ( internal.access.ExtractImpl) INFO bixtestadmin - Node level information will not be added to the manifest when getAllProperties is selected in the extract rule form for XML extraction
2017-04-26 13:53:41,438 [ PegaRULES-Batch-1] [ STANDARD] [ BIXTest:01.01.01] ( internal.access.ExtractImpl) ERROR bixtestadmin - Error creating zip file: java.io.FileNotFoundException: /BIXExtract/BIX_MyClass-Work_TestExtract2_14.zip (No such file or directory)

The entries seemed to suggest that this run had identified a record to extract and this also showed that it was skipping 0 records.

So data was expected to be extracted.

However, an error can be seen when it attempts to read the contents from the /BIXExtract directory.

The BIXFTPListener rule was subsequently opened and the "Test Connection" button produced the same error regarding the /BIXExtract directory.



Resolution



On examination of the underlying operating system the /BIXExtract directory was configured in the wrong location.

The "BIX/sharedpath" Dynamic System Setting was subsequently updated to the correct location for building the extracted file.

After making the above change the next time the extract was run this was shown to extract the expected record.

Published May 17, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us