Support Article

Bix Extract Failure

SA-34232

Summary



The user created a BIX Extract Rule to store all the properties present on a class group in database.
An agent has been configured to run every night on the rule.


Error Messages



2016-11-17 01:30:03,631 [ PegaRULES-Batch-5] [ ] [ Complaint:01.01.02] ( internal.access.ExtractImpl) INFO - Processing Class: QBEAU-CSM-Complaint-Work-ComDis with 314 instances
2016-11-17 01:30:03,631 [ PegaRULES-Batch-5] [ ] [ Complaint:01.01.02] ( internal.access.ExtractImpl) INFO - BIX Version : 7.1
2016-11-17 01:30:11,436 [ PegaRULES-Batch-5] [ ] [ Complaint:01.01.02] ( internal.access.ExtractImpl) INFO - Target database using batch inserts
2016-11-17 01:39:21,903 [ PegaRULES-Batch-5] [ ] [ Complaint:01.01.02] ( internal.access.ExtractImpl) ERROR - SQL error getting the next row to be extracted
2016-11-17 01:39:21,904 [ PegaRULES-Batch-5] [ ] [ Complaint:01.01.02] ( internal.access.ExtractImpl) ERROR - SQL error getting the next row to be extracted: errorCode = -4470 errorMessage:[jcc][t4][10120][10898][4.18.60] Invalid operation: result set is closed. ERRORCODE=-4470, SQLSTATE=null
2016-11-17 01:39:21,947 [ PegaRULES-Batch-5] [ ] [ Complaint:01.01.02] ( internal.access.ExtractImpl) INFO - PAL Statistics for BIX Extract run :
Non-rule-resolved instances accessed from the database: 568
CPU time accessing non-rule-resolved instances from the database: 0
Elapsed Time accessing non-rule-resolved instances from the database: 548.515
CPU time retrieving rule-resolved Rules from the database: 0
Rule-resolved rules requested from database or cache: 2
Bytes read from database Storage Streams (uncompressed): 364180
Number of database requests that exceeded the time threshold: 2
CPU time spent performing BLOB decryption: 0
Elapsed time spent performing BLOB decryption: 0
BLOB decryption: 1

2016-11-17 01:39:21,948 [ PegaRULES-Batch-5] [ ] [ Complaint:01.01.02] ( internal.access.ExtractImpl) ERROR - Could not return target db statements
java.sql.SQLException: Connection has already been closed.


Steps to Reproduce

  1. Create a BIX Extract rule
  2. Schedule it with agent to save into database


Root Cause



Extract configured to run through agent in recurring mode for once in a day. The database is inactive for 24 Hours and the first extract connection is performing the db activation and creating connection. This leads to the issue by taking some time.

Resolution



Activate the DB2 database, before making the first connection. This resolves the issue

Published February 27, 2017 - Updated March 11, 2017

Have a question? Get answers now.

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