CA PPM: Getting System Error when accessing the Portlet Filter tab

Document ID : KB000103836
Last Modified Date : 22/01/2019
Show Technical Document Details
Question:
We have a portlet based on Project object. When we access the List Filter Section tab or when we try to add any field to the Filter Layout we get "Error: System error. Contact the system admin".

App log shows:

ERROR 2018-06-19 09:17:04,809 [http-nio-14001-exec-11] niku.xql2 (clarity:admin.com:17857806__B8585E29-FAEC-4E6B-8792-BB841C145342:npt.portletFilterLayout) Internal Processing exception 
com.niku.union.persistence.PersistenceException: 
SQL error code: 1461 
Error message: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-01461: can bind a LONG value only for insert into a LONG column 

Executed: 
UPDATE ODF_VIEW_ATTRIBUTES SET 

Caused by: java.sql.SQLException: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-01461: can bind a LONG value only for insert into a LONG column 

at 

Using input: 
{is_virtual=0, col=2, hidden=0, display_order=5, language=en, is_fixed_widget=0, type=browse, section_id=5161172, show_value=1, is_required=0, action_id=null, num_rows=0, is_multi_valued=1, attribute_name=z_size, id=5521600, is_not_equal_xpath=0, image=null, is_presence_required=0, view_id=5149147, num_cols=0, is_editable=1, default_value=<defaultValue value="&lt;defaultValue value=&quot;&amp;amp;lt;defaultValue value=&amp;amp;quot;&amp;amp;amp;amp;lt;defaultValue value=&amp;amp;amp;amp;quot;&amp;amp;amp;amp;amp;amp;lt;defaultValue value=&amp;amp;amp;amp;amp;amp;quot;&amp;amp;amp;amp;amp;amp;amp;amp;lt;defaultValue 

 
Answer:
One of the portlet entries are corrupt on default value atribute.

Two possible solutions:
I. Correct the existing portlet
1. XOG out the portlet using the attached XOG
2. Find the default value that is very long with values that look like this:
User-added image
3. Correct the default value to show only
<defaultValue value=""></defaultValue>
4. Note the defaultValue tags are used multiple times so we need to make sure we clear the correct ones, and all other tags are properly closed.
5. Save
6. XOG the portlet back in
7. Restart the services

Alternative option:
II. Recreate the portlet
Delete the portlet and recreate it from scratch
File Attachments:
portlets_read.xml