Support Article

Could not write manifest summary : null



On BIX 7.2.2 running extract to a target database, the inserts into the manifest table fail with an error "Could not write manifest summary : null " .

Error Messages

In execution history tab:

Could not write manifest summary : null

In PegaRULES log file:

2017-05-18 03:17:34,673 [ PegaRULES-Batch-1] [ STANDARD] [ ] [ Catalyst:02.01.03] (ernal.bix.BIXManifestWriterDDL) ERROR - could not insert the row into pr_extract_details table. Writing the row data to logs : ORA-00904: "PXTOTALINSTANCECOUNT": invalid identifier

2017-05-18 04:03:01,533 [egaRULESUsageDaemon] [ STANDARD] [ ] [ ] (nitor.internal.UsageDaemonImpl) ERROR - Usage Failure Reason 1: ORA-01438: value larger than specified precision allowed for this column

Steps to Reproduce

  1. Run Bix
  2. Check Extract rule Execution History tab
  3. Check if it has "Could not write manifest summary : null"

Root Cause

A defect or configuration issue in the operating environment. There are actually multiple errors contributing to the issue.

If the target database tables are in a separate schema from the manifest tables there is an issue writing to the manifest tables as the code is using the database connection of the target database instead of the manifest database.

In BIX 7.2.2 there is a new column that needs to be added to one of the manifest tables.

There was an additional sporadic error related to writing to the precision of colums in the pr_perf_stats table.


Make the following change to the operating environment:
  1. Apply HFix-34281 for the issue with the wrong database connection being used to connect to the manifest tables.
  3. See SA-38281 for details on correcting the percision of columns in the pr_perf_stats table.

Published May 19, 2017 - Updated June 27, 2017

Have a question? Get answers now.

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