AnsweredAssumed Answered

How to translate Node id:s in FulfillmentHandler

Question asked by David Horwath on Jun 21, 2018
Latest reply on Jun 28, 2018 by David Horwath

Like • Show 0 Likes0
Comment • 2

This is getting me mad, and I do not have the time to wait 8 weeks for support to give me an answer.

I have a node somewhere in a workflow that is causing an ORA-12899.

DEBUG (com.aveksa.server.workflow.scripts.nodes.FulfillmentHandlerNode) says: "Fulfilling changes for node id=7159689:WPDS"

How can I translate that node id to show me which workflow is executing?

An ORA-12899 means that something is trying to add data that is "to big" for a column, so in a way I know this will NEVER fix itself. Something is queued up for creating a request, and it will never be successful. I need to delete whatever request/rule/whatever, that is trying to add this data that is to big.

Tried to quickly look through all tables starting with T_AV_WF for the column name NODE_ID, but NONE of those node ids are having values higher than 2 000 000, and my node id is 7 159 689

All my searches for more tables that are using a column called NODE_ID has failed. Had a sql query that is supposed to find this, but it doesn't seem to work anymore:

SELECT atc.OWNER, atc.TABLE_NAME, atc.COLUMN_NAME, atc.DATA_TYPE FROM ALL_TAB_COLUMNS atc 
WHERE OWNER='AVUSER' AND atc.COLUMN_NAME LIKE 'NODE_ID';

So giving up due to long weekend coming up. But need to fix this as soon as possible. Patch for 7.1 is incoming, and do not want to run a patch with these kind of database errors.

Oh and by the way: Anyone having an SQL that shows the grants on the AVUSER, would be highly appreciated. Because I am pretty sure I have used the above SQL to show me the tables with the specified column name...

I know a lot, but not enough apparently

David Horwath Jun 28, 2018 11:11 AM

Correct Answer

Not sure if I solved anything, but found a SQL query which probably (not confirmed) gets me closer to the job that caused the:

"ORA-12899: value too large for column "AVUSER"."T_AV_CHANGE_REQUEST_DETAILS"."DESCRIPTION" (actual: 4078, maximum: 4000)"

SELECT cr.name, crd.CHANGE_REQUEST_ID, crd.TYPE, crd.CHANGE_DATA_DESCRIPTION, u.USER_ID, crid.ACTIVITY_INSTANCE_ID, crid.ACTIVITY_INSTANCE_DATABASE, crid.WORKFLOW_INSTANCE_ITERATION FROM PV_CHANGE_REQUEST_ITEM_DETAIL crid 
JOIN PV_CHANGE_REQUEST_DETAIL crd ON crd.id=crid.CHANGE_REQUEST_DETAIL_ID
JOIN T_AV_CHANGE_REQUESTS cr on cr.id=crd.CHANGE_REQUEST_ID
JOIN PV_USERS u ON u.id=crd.AFFECTED_USER_ID
WHERE crid.WORKITEM_ID LIKE '4512494%';

The above SQL searches for the "node id=4512494:WPDS" that you can get if you activate debug on com.aveksa.server.workflow.scripts.nodes.FulfillmentHandlerNode

Hope it helps someone.

We will open a case to get a proper help with this, but just thought I could find it myself

See the reply in context

No one else had this question

Outcomes

SELECT cr.name, crd.CHANGE_REQUEST_ID, crd.TYPE, crd.CHANGE_DATA_DESCRIPTION, u.USER_ID, crid.ACTIVITY_INSTANCE_ID, crid.ACTIVITY_INSTANCE_DATABASE, crid.WORKFLOW_INSTANCE_ITERATION FROM PV_CHANGE_REQUEST_ITEM_DETAIL crid JOIN PV_CHANGE_REQUEST_DETAIL crd ON crd.id=crid.CHANGE_REQUEST_DETAIL_ID JOIN T_AV_CHANGE_REQUESTS cr on cr.id=crd.CHANGE_REQUEST_ID JOIN PV_USERS u ON u.id=crd.AFFECTED_USER_ID WHERE crid.WORKITEM_ID LIKE '4512494%';

2 Replies

Christopher Smith Jun 21, 2018 9:53 AM
Mark Correct
Correct Answer
Hello,
I am questioning whether that error is phrased "Fulfilling changes for node, id=7159689:WPDS" or "Fulfilling changes for, node id=7159689:WPDS".

The id provided looks suspiciously like a Workitem_ID from the PV_Change_Request_Work_Item view (also referenced in a few other Change_Request views/table. Example WorkItem_ID from our environment: "17432804:WPDS:1" Generated by concatenating the activity_instance_ID and the Activity_instance_database columns from the same view. Still not entirely sure what the :1 is at the end. Try either searching the view in the above column with a like statement for your specific id, or try searching your UI for the activity "7159689"

Hope this helps
Like • Show 0 Likes0
Actions
- David Horwath @ Christopher Smith on Jun 28, 2018 11:11 AM
  Unmark Correct
  Correct Answer
  Not sure if I solved anything, but found a SQL query which probably (not confirmed) gets me closer to the job that caused the:
  "ORA-12899: value too large for column "AVUSER"."T_AV_CHANGE_REQUEST_DETAILS"."DESCRIPTION" (actual: 4078, maximum: 4000)"
  
  SELECT cr.name, crd.CHANGE_REQUEST_ID, crd.TYPE, crd.CHANGE_DATA_DESCRIPTION, u.USER_ID, crid.ACTIVITY_INSTANCE_ID, crid.ACTIVITY_INSTANCE_DATABASE, crid.WORKFLOW_INSTANCE_ITERATION FROM PV_CHANGE_REQUEST_ITEM_DETAIL crid JOIN PV_CHANGE_REQUEST_DETAIL crd ON crd.id=crid.CHANGE_REQUEST_DETAIL_ID JOIN T_AV_CHANGE_REQUESTS cr on cr.id=crd.CHANGE_REQUEST_ID JOIN PV_USERS u ON u.id=crd.AFFECTED_USER_ID WHERE crid.WORKITEM_ID LIKE '4512494%';
  
  The above SQL searches for the "node id=4512494:WPDS" that you can get if you activate debug on com.aveksa.server.workflow.scripts.nodes.FulfillmentHandlerNode
  
  Hope it helps someone.
  We will open a case to get a proper help with this, but just thought I could find it myself
  Like • Show 0 Likes0
  Actions

How to translate Node id:s in FulfillmentHandler

Outcomes

Related Content

Recommended Content