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

Manually publishing FCM data fails with database error

SA-36416

Summary



When a user tries to publish data in FCMR through the FCMR landing page, a database error is thrown in the log. User tried multiple times for “Work”, “Administrative” and “Assignments” options. No error appears on screen, but the logs show errors and data is not published in FCMR.

Error Messages



Last SQL: SELECT "PARENTPC0".L1 AS "pyPublishType" , "PARENTPC0".L2 AS "pyRecordsSavedCount" , "PARENTPC0".L3 AS "pyTimeLeft" , "PARENTPC0".L4 AS "pxCreateDateTime" , "PARENTPC0".L5 AS "pyTotalRecords" , "PARENTPC0".L6 AS "pzInsKey" , "PARENTPC0".L7 AS "pyUserIdentifier" , "PARENTPC0".L8 AS "pyOperation" , "PARENTPC0".L9 AS "pyOperationStatus" , "PARENTPC0".L10 AS "pzRank" FROM ( SELECT "PC0".PYPUBLISHTYPE AS "L1" , "PC0".PYRECORDSSAVEDCOUNT AS "L2" , FCMR.pr_read_from_stream('.pyTimeLeft', "PC0".pzInsKey, "PC0".pzPVStream) AS "L3" , "PC0".PXCREATEDATETIME AS "L4" , "PC0".PYTOTALRECORDS AS "L5" , "PC0".PZINSKEY AS "L6" , "PC0".PYUSERIDENTIFIER AS "L7" , "PC0".PYOPERATION AS "L8" , "PC0".PYOPERATIONSTATUS AS "L9" , ROW_NUMBER() OVER (ORDER BY "PC0".PXCREATEDATETIME DESC NULLS LAST) AS "L10" FROM PEGADATA.PR_LOG_FCMR "PC0" WHERE ( "PC0".PYOPERATION <> ? AND "PC0".PYOPERATION <> ? AND ( "PC0".PYOPERATIONSTATUS <> ? OR "PC0".PYOPERATIONSTATUS IS NULL ) ) AND "PC0".pxObjClass = ? ) "PARENTPC0" WHERE "PARENTPC0".L10 <= ? ORDER BY 10 ASC
com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-440, SQLSTATE=42884, SQLERRMC=PR_READ_FROM_STREAM;FUNCTION, DRIVER=3.72.24

Steps to Reproduce



Go to the FCMR landing page and click the Publish button.

Root Cause



A defect in Pegasystems’ code or rules
Pega-provided User Defined Functions (UDFs) should not be needed, but because a column is not exposed initially, they are called.


Resolution



Perform the following local-change:
Expose the pyTimeLeft column in the PegaDATA.PR_LOG_FCMR table.


Published May 2, 2017 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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