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 does not extract data when using UserID in script

SA-72975

Summary



Business Intelligence Exchange (BIX) extract is run from the Command Line using the -a and -p parameters. The extract runs and terminates without logging an error.
The BIX extract does not extract data when an operator ID is used as a parameter in the script.



Error Messages



In PegaBIX log, INFO and DEBUG log messages display.

INFO - {b=1, a=yourbixuser, i=yourEXTRACTRule, p=password}

DEBUG - Successfully Connected to DB: PegaRULESReports


Steps to Reproduce



Pass the Pega username and password to run the BIX using -a and -p parameters.


Root Cause



A defect or configuration issue in the operating environment.

The pxActorsCount expression rule assembly was incorrect in the database.
The query must be run as below to compare the results from this environment to another on the same application version.


SELECT LENGTH(pzbinarycontent), pzsha1, pzclass FROM rules.PR_ASSEMBLEDCLASSES WHERE pzclass LIKE '%pxactorscount%.class'


Resolution



Perform the following local-change: 
  1. Navigate to System Management Application (SMA) > Advanced > Virtual Rule Table Cache Management.
  2. Enter the below values in the fields,

    Rule Class: Rule-Declare-Expressions
    Instance Name: !.PXACTORSCOUNT!

     
  3. Click the 'Lookup Virtual Table Cache Detail' button to lookup the rule.
  4. Click Reassemble Candidates.
  5. Log in to the application to trigger the reassembly.

 
Suggest Edit

Published February 20, 2019 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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