Unable to open an instance of a sub object

Document ID : KB000097215
Last Modified Date : 21/05/2018
Show Technical Document Details
Issue:
When trying to open only particular instance of a sub object, it throws an error: [en - Unable to process request - Server or Network error] 

In the app-ca log, it shows as 
Portlet view processing failed for portlet: odf.subObject

When trying to delete the instance, the delete button is missing and it throws the error in the log as 

ERROR 2018-05-20 23:16:23,491 [http-nio-14001-exec-24] niku.xql2 (email@domain.com:42082354__81CC27B0-939F-47A1-8C25-6B2B4A8ABA40:odf.deleteObjectInstancesConfirm) Internal Processing exception 
com.niku.union.odf.exception.ODFException: Error reading subobject instance with PK: 5000015 

Caused by: com.niku.union.persistence.PersistenceException: 
SQL error code: 1426 
Error message: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-01426: numeric overflow 

When trying to XOGOUT the instance to check for any invalid XML, the error thrown is

<NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_customObjectInstance.xsd"><Header action="write" externalSource="NIKU" objectType="customObjectInstance" version="14.4.0.234"/><customObjectInstances objectCode="td_test_program_info"></customObjectInstances><XOGOutput> <Object type="customObjectInstances"/> <Status state="FAILURE"/> <Statistics insertedRecords="0" failureRecords="0" totalNumberOfRecords="0" updatedRecords="0"/> <Records><Record><KeyInformation><column name="objectCode">subobject</column><column name="instanceCode">TPA000013</column></KeyInformation><ErrorInformation><Severity>FATAL</Severity><Description>Custom Object Instance Export Failed</Description><Exception><![CDATA[SQL Exception with error code : 1426]]></Exception></ErrorInformation></Record></Records></XOGOutput></NikuDataBus>
Resolution:
Try adding each attribute by attribute to the list view of the sub object instance. At one stage, the error shows up on the screen and the last added attribute is the "culprit". 
In this case, the attribute was calculated attribute and for this particular instance, it was dividing by 0 which caused the issue. 
Changed the attribute value which was used in the calculation and the issue got resolved. 

If this is not a calculated attribute, check from the backend, odf_ca_subobjectid and check for any anomalies in the value and get it corrected.