Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Madhu Chalamaiah (_MadhuChalamaiah)
Rules cube
Lead Consultant
Rules cube
CA
_MadhuChalamaiah Member since 2013 11 posts
Rules cube
Posted: Feb 24, 2016
Last activity: Mar 17, 2016
Posted: 24 Feb 2016 12:02 EST
Last activity: 17 Mar 2016 12:10 EDT
Closed
Solved

BIX Extraction have nulls in few columns like pyStatusWork.

Hello,

We are extracting data from Pega database to a staging database using BIX. We run BIX extract in Batch mode.

We identified nulls in pyStatusWork column for cases that got extracted.  Also identified duplication of case id's in BIX database.


When i run the extraction manually in lower environments, I am getting an exception com.ibm.db2.jcc.am.BatchUpdateException. as this is generic issue and unable to find the root cause.

 

Can anybody help to understand the reason and process of extraction.

Pega version is 7.17

To see attachments, please log in.
System Administration

Accepted Solution

Posted: 8 years ago
Posted: 17 Mar 2016 12:10 EDT
Madhu Chalamaiah (_MadhuChalamaiah)
Rules cube
Lead Consultant
Rules cube
CA

Hi, We figured out the issue.

Its, because of below reasons BIX was failing to complete extraction.

1. Failed because of insufficient parameters

2. Because of Mandatory data missing for extraction.

We are using Shell script which is being executed as Command line.

With the help of below artical we corrected our arguments. https://community.pega.com/support/support-articles/bix-script-not-calling-highest-ruleset-version-extract-rule

Only concern was, if these errors are well articulated then we would have resolved the problem quickly.

Thanks,

Madhu

To see attachments, please log in.
Posted: 8 years ago
Posted: 24 Feb 2016 13:19 EST
Rajiv Nistala (nistr) Senior Manager - Engineering
Pegasystems
IN

Hi,

Without actual logs, details of what is being extracted and the actual value in case versus what is being extracted, we might not be able to point out the actual cause of this.

That said, how is BIX being executed - rule form or command line?

Can you share the command line arguments being used?

Can you tell us if there is more than one version of the extract rule in the rulesets?

Please share the logs.

BIX does not delete the data from the target tables. Please reach the following PDN article for details - https://pdn.pega.com/bix-design-models.

-Rajiv

To see attachments, please log in.

Accepted Solution

Posted: 8 years ago
Posted: 17 Mar 2016 12:10 EDT
Madhu Chalamaiah (_MadhuChalamaiah)
Rules cube
Lead Consultant
Rules cube
CA

Hi, We figured out the issue.

Its, because of below reasons BIX was failing to complete extraction.

1. Failed because of insufficient parameters

2. Because of Mandatory data missing for extraction.

We are using Shell script which is being executed as Command line.

With the help of below artical we corrected our arguments. https://community.pega.com/support/support-articles/bix-script-not-calling-highest-ruleset-version-extract-rule

Only concern was, if these errors are well articulated then we would have resolved the problem quickly.

Thanks,

Madhu

To see attachments, please log in.

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

Pega Collaboration Center 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