BIX Extract Error due to data issue. How to easily identify the work item causing the issue?
Hi All,
Pega Product Version : PRPC V6.3 SP1
We are doing daily bix extraction of the work items in our production system. We received the following error today during the extraction process and bix extract rule execution history showed the below error.
"Could not process : String was not a datetime".
We have sorted out all the work items eligible for today's extraction and compared it with the Bix file extracted today to compare in which work item it is failed. This is a manul task and time consuming.
Is there any way we can find out easily, in which work item(probabaly, pyid or pzinskey of the work item) the extraction failed?
Pegasystems Inc.
US
Please post the PegaBIX log file from when this happened. It should have had the pzinskeys of the batch that failed which would narrow down the issue and then you could have used -z/-Z to find the specific one.
US Bank
US
I checked the PegaBIX log file and didn't find the pzinskey of the problematic work item. It shows only the error message "Could not process : String was not a datetime".
Could you please brief about what is -z/-Z option. I am not aware of it. Appreciate your help.
Pegasystems Inc.
US
It might be that all of the pzInskey values being extracted is only listed if you turn on debug. If the error was on inserting into a target database and a BatchUpdateException is thrown then it would also give you the list of pzInskeys in that batch.
If you look in the BIX User Guide under command line options you will find -z/-Z
-z <start key> Only extract instances with a pzInsKey equal to or greater than <start key>.
Note: The comparison is character by character with the pzInsKey and is not an integer comparison with
-Z <end key> Only extract instances with a pzInsKey equal to or less than <end key>.
Note: The comparison is character by character with the pzInsKey and is not an integer comparison with
Pegasystems
IN
In what format is the data being extracted (DB, XML or CSV)?
In the BIX log file, right at the beginning, the BIX relevant class versions are printed. Could you please provide us the same?
US Bank
US
Hi All,
I can see the pzinskey of the work items which are extracted succesfully. But not able to see the one which is failed.
The data being extracted in xml format.
US Bank
US
------- Module Versions of Extract Classes --------- $Id: ExtractImpl.java 36582 2012-10-15 13:22:25Z ZackGarbowitz $ $Id: ExtractParameters.java 27108 2012-05-08 19:21:06Z BinoyFernandez $ $Id: SQLSelector.java 35855 2012-10-03 13:44:10Z ZackGarbowitz $ $Id: SQLGenerator.java 35855 2012-10-03 13:44:10Z ZackGarbowitz $ $Id: SQLGeneratorOracle.java 35972 2012-10-04 13:38:32Z ZackGarbowitz $ $Id: SQLGeneratorDb2.java 35972 2012-10-04 13:38:32Z ZackGarbowitz $ $Id: SQLGeneratorDb2ZOS.java 35972 2012-10-04 13:38:32Z ZackGarbowitz $ $Id: SQLGeneratorApache.java 32575 2012-08-06 20:02:01Z MichaelLivingston $ $Id: SQLGeneratorMssql.java 35972 2012-10-04 13:38:32Z ZackGarbowitz $ $Id: PropertyData.java 12722 2011-08-05 11:15:08Z RajivKarumuri $ $Id: NodeData.java 12721 2011-08-05 11:14:38Z RajivKarumuri $ $Id: IOData.java 20759 2012-02-15 09:28:09Z srikanthchallapilla $ $Id: FilterData.java 12724 2011-08-05 11:16:38Z RajivKarumuri $ $Id: TransformFinder.java 12712 2011-08-05 11:01:41Z RajivKarumuri $ $Id: ParUtils.java 16651 2011-11-03 17:13:59Z KevinHickey $ $Id: DatabasePreparedStatement.java 27701 2012-05-17 14:30:09Z daviddority $ $Id: DatabaseUtilsCommonImpl.java 24172 2012-03-30 06:59:13Z srikanthchallapilla $ --------------------- End -------------------------- bix/useHistoryClasses setting has been disabled Value of pyLastUpdateDate in pr_Extract_Time at the beginning of BIX run: 2016-03-30 04:55:23.0 bix/useHistoryClasses setting has been disabled Value of pyLastUpdateDate in pr_Extract_Time at the beginning of BIX run: 2016-03-30 04
------- Module Versions of Extract Classes --------- $Id: ExtractImpl.java 36582 2012-10-15 13:22:25Z ZackGarbowitz $ $Id: ExtractParameters.java 27108 2012-05-08 19:21:06Z BinoyFernandez $ $Id: SQLSelector.java 35855 2012-10-03 13:44:10Z ZackGarbowitz $ $Id: SQLGenerator.java 35855 2012-10-03 13:44:10Z ZackGarbowitz $ $Id: SQLGeneratorOracle.java 35972 2012-10-04 13:38:32Z ZackGarbowitz $ $Id: SQLGeneratorDb2.java 35972 2012-10-04 13:38:32Z ZackGarbowitz $ $Id: SQLGeneratorDb2ZOS.java 35972 2012-10-04 13:38:32Z ZackGarbowitz $ $Id: SQLGeneratorApache.java 32575 2012-08-06 20:02:01Z MichaelLivingston $ $Id: SQLGeneratorMssql.java 35972 2012-10-04 13:38:32Z ZackGarbowitz $ $Id: PropertyData.java 12722 2011-08-05 11:15:08Z RajivKarumuri $ $Id: NodeData.java 12721 2011-08-05 11:14:38Z RajivKarumuri $ $Id: IOData.java 20759 2012-02-15 09:28:09Z srikanthchallapilla $ $Id: FilterData.java 12724 2011-08-05 11:16:38Z RajivKarumuri $ $Id: TransformFinder.java 12712 2011-08-05 11:01:41Z RajivKarumuri $ $Id: ParUtils.java 16651 2011-11-03 17:13:59Z KevinHickey $ $Id: DatabasePreparedStatement.java 27701 2012-05-17 14:30:09Z daviddority $ $Id: DatabaseUtilsCommonImpl.java 24172 2012-03-30 06:59:13Z srikanthchallapilla $ --------------------- End -------------------------- bix/useHistoryClasses setting has been disabled Value of pyLastUpdateDate in pr_Extract_Time at the beginning of BIX run: 2016-03-30 04:55:23.0 bix/useHistoryClasses setting has been disabled Value of pyLastUpdateDate in pr_Extract_Time at the beginning of BIX run: 2016-03-30 04:55:23.0
Pegasystems
IN
Since you mention that you can see the list of pzInsKeys that were successfully extracted, can you try to do Obj-Open for the instance which has the next ID value?
US Bank
US
We are able to identify the problematic record. We have sorted out all the work items eligible for today's extraction and compared it with the Bix file extracted today to compare in which work item it is failed. This is a manual task and time consuming.
I am looking for any easy way to identify which work item caused the bix extraction failure?
Pegasystems
IN
This hotfix also gets the feature of generating manifest files for BIX extracts which summarizes the details of what has been extracted. You can get further details on this feature in BIX 7.1 user guide - https://docs-previous.pega.com/bix-71-user-guide (page 12)