PRODUCTION - Errors when running the Resource Adapter

Document ID : KB000117065
Last Modified Date : 07/10/2018
Show Technical Document Details
Issue:

We executed our Resource Adapter in our Production environment and we are seeing a very high volume of errors in the run. Almost 2/3 of the records have failed.

We are getting XOG errors on the surface but a closer look shows that it is throwing the following exception in the Resource Adaptor logs when attempting to assign the department to the resource:

com.niku.union.utility.MessageKeyException: Invalid unitId value 5032193 given for attribute odf_obs_fin_dept.
at com.ca.platform.osf.object.obs.OBSEntityWriteService.process(OBSEntityWriteService.java:146)
at com.niku.odf.service.AttributeWriteService.doProcess(AttributeWriteService.java:77) ... 

Alternative STR:

Customer is trying to assign a department to a resource and gets the following error in the UI:

ERROR Invalid unitId value 5008268 given for attribute odf_obs_fin_dept. 

The full error in the logs is:

ERROR 2018-08-01 13:09:47,055 [http-nio-14001-exec-57] obs.OBSEntityWriteService (clarity:alan.smith@company.com:17031276__0082E4EC-78F7-4DAF-A17C-8E81FA8DD8B1:npt.gridUpdate) Cannot write Entity OBS : 
com.niku.union.odf.exception.ODFException: com.niku.union.utility.MessageKeyException: Invalid unitId value 5008268 given for attribute odf_obs_fin_dept. 
at 

...

Caused by: com.niku.union.utility.MessageKeyException: Invalid unitId value 5008268 given for attribute odf_obs_fin_dept. 
... 70 more

Environment:
In both cases this error occurred after an upgrade from 14.x to 15.4.x
Cause:
Invalid characters in the Department name and/or Description
Resolution:

1.  Run the following query to find out if this is the cause of your problem.  NOTE:  If you are a SAAS customer, you will have to open a support case so the On Demand DBA's can run this query for you.

SELECT * 
FROM PRJ_OBS_UNITS 
WHERE NAME LIKE '%/%' OR 
NAME LIKE '%:%' OR 
NAME LIKE '%"%' OR 
NAME LIKE '%''%' OR 
NAME LIKE '%>%' OR 
NAME LIKE '%<%' 


2.  If there are no results, this is not the cause of your problem.  If results are returned, use those results to determine which departments need to be fixed and proceed with the rest of these instructions.

3.  Change the invalid characters in department name and description to words or remove them.

4.  Save the change(s).

5.  Test to make sure the department can now be assigned to resources.

6.  If that is successful you can test to see if adding the same character back in again will still allow you to assign the department to your resources successfully. If not, you will have to leave the character out.