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.

Troubleshooting: Commit error after exposing new column

Suggest edit Updated on September 13, 2021

Symptom

A developer asks:

I'm trying to use the memo field of History to hold a list of the names of properties that were updated.  The property .pyMemo is an exposed column of 255 characters but is not long enough, so we are going to use a new BLOB column. 

First, I created a clone of the property and deleted pyMemo.  Then I made all the necessary database table changes. But when I try to commit to the database, I get an error message indicating that pyMemo is an invalid column. 

Since nothing requires pyMemo, why this error message?

Solution

To clear this message after making such database changes, stop and restart the Process Commander server.

  • Previous topic Troubleshooting: "maximum row size" error for pr4_rule table in V4.2 installation (SQL Server)
  • Next topic Troubleshooting: Connecting to IBM DB2 databases with JDBC

Tags

Pega Platform 7.1.1 - 8.3.1 System Architect System/Cloud Ops Administrator System Administration
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us