Cannot Change Status Due to Error "Node XXXXXX Does Not Exist in the Cache. It May Have Been Deleted Already." Due to a Subscriber (From Agile Content Service - ACS) That Does Not Have a Valid Event Associated to It. (Doc ID 1300652.1)

Last updated on AUGUST 08, 2017

Applies to:

Oracle Agile Product Collaboration - Version 9.3.0.1 and later
Oracle Agile PLM Framework - Version 9.3.0.1 and later
Information in this document applies to any platform.
***Checked for relevance on09-Aug-2014***

Symptoms

When attempting to move a change to the next status, the following error occurs.

ERROR
-----------------------
Node XXXXXX does not exist in the cache. It may have been deleted already.

No error in OC4J log ([OASHome]\opmn\logs\default_group~home~default_group~1.log)

Java Console gives:
WARNING: Exception returned by remote server: {0}
com.agile.admin.client.value.AdminException: Node XXXXXX does not exist in the cache. It may have been deleted already.
at com.agile.admin.server.ADictionary.getNodeByID(ADictionary.java:219)
at com.agile.pc.cmserver.base.BaseServiceRoute.checkACSWorkflowEvents(BaseServiceRoute.java:8201)
at com.agile.pc.cmserver.base.BaseServiceRoute.validateOnChangeStatusExtra(BaseServiceRoute.java:3676)
at com.agile.pc.cmserver.base.BaseServiceRoute.doChangeStatus(BaseServiceRoute.java:2030)
at com.agile.pc.cmserver.base.BaseServiceRoute.handleChangeStatus(BaseServiceRoute.java:7487)
at com.agile.pc.cmserver.base.CMRouteSessionBean.handleChangeStatusWithoutAutoPromote(CMRouteSessionBean.java:1163)
...

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Open any existing ECO

or
Create a new ECO and assign a workflow

2. Move to next status

the error appears

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms