ORA-00904: "THREADIN": invalid identifier error when bpm calculates parent thread family while executing migrated project instance (Doc ID 1386712.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Business Process Management Suite - Version 10.3.2 and later
Information in this document applies to any platform.
***Checked for relevance on 12-November-2013***

Symptoms


After migrating a project from BPM 6.0.x to BPM 10g, the following exception is seen in Engine logs when working on an instance in BPM Workspace.

An error occurred while accesing the database.
Detail:SQL statement: 'SELECT MAX(THREADIN), MIN(THREADIN) FROM PPROCINSTANCE WHERE PROCESSID = 443 AND INSTID = 1638 AND PARENTTHREAD = 0 AND STATE NOT IN (32,544,1056,1568,2080,2592,3104,3616,4128,4640,5152,5664,6176,6688,7200,7712,8224,8736,9248,9760,10272,10784,11296,11808,12320,
12832,13344,13856,14368,14880,15392,15904,16416,16928,17440,17952,18464,18976,19488,20000,20512,21024,21536,22048,22560,23072,
23584,24096,24608,25120,25632,26144,26656,27168,27680,28192,28704,29216,29728,30240,30752,31264,31776,32288,64,576,1088,1600,
2112,2624,3136,3648,4160,4672,5184,5696,6208,6720,7232,7744,8256,8768,9280,9792,10304,10816,11328,11840,12352,12864,13376,
13888,14400,14912,15424,15936,16448,16960,17472,17984,18496,19008,19520,20032,20544,21056,21568,22080,22592,23104,23616,
24128,24640,25152,25664,26176,26688,27200,27712,28224,28736,29248,29760,30272,30784,31296,31808,32320)'

Caused by: ORA-00904: "THREADIN": invalid identifier

fuego.transaction.DatabaseException: An error occurred while accesing the database.
Detail:SQL statement: 'SELECT MAX(THREADIN), MIN(THREADIN) FROM PPROCINSTANCE WHERE PROCESSID = 110 AND INSTID = 1112 AND PARENTTHREAD = 0 AND STATE NOT IN (32,544,1056,1568,2080,2592,3104,3616,4128,4640,5152,5664,6176,6688,7200,7712,8224,8736,9248,9760,10272,10784,11296,11808,12320,
12832,13344,13856,14368,14880,15392,15904,16416,16928,17440,17952,18464,18976,19488,20000,20512,21024,21536,22048,22560,23072,
23584,24096,24608,25120,25632,26144,26656,27168,27680,28192,28704,29216,29728,30240,30752,31264,31776,32288,64,576,1088,1600,
2112,2624,3136,3648,4160,4672,5184,5696,6208,6720,7232,7744,8256,8768,9280,9792,10304,10816,11328,11840,12352,12864,13376,
13888,14400,14912,15424,15936,16448,16960,17472,17984,18496,19008,19520,20032,20544,21056,21568,22080,22592,23104,23616,
24128,24640,25152,25664,26176,26688,27200,27712,28224,28736,29248,29760,30272,30784,31296,31808,32320)'

at fuego.server.persistence.jdbc.JdbcProcessInstancePersMgr.calculateParentThreadFamily(JdbcProcessInstancePersMgr.java:505)
at fuego.server.persistence.Persistence.calculateParentThreadFamily(Persistence.java:300)
at fuego.server.ProcInst.calculateParentThreadFamily(ProcInst.java:2936)
at fuego.server.ProcInstUtils.isInCurrentFamily(ProcInstUtils.java:255)
at fuego.server.ProcInstUtils.isParents(ProcInstUtils.java:266)
at fuego.server.ProcInstUtils.canBeConsolidated(ProcInstUtils.java:244)
at fuego.server.execution.microactivity.EndThreadMicroActivity.execute(EndThreadMicroActivity.java:67)
at fuego.server.execution.microactivity.MicroActivityEngineExecutionHandler.executeActivity(MicroActivityEngineExecutionHandler.java:57)
at fuego.server.execution.ImmediateActivity.execute(ImmediateActivity.java:42)
at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
at fuego.transaction.TransactionAction.startNestedTransaction(TransactionAction.java:527)
at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:548)
at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
at fuego.server.execution.DefaultEngineExecution.executeAutomaticWork(DefaultEngineExecution.java:62)
at fuego.server.execution.EngineExecution.executeAutomaticWork(EngineExecution.java:42)
at fuego.server.execution.ToDoItem.executeAutomaticWork(ToDoItem.java:267)
at fuego.ejbengine.ItemExecutionBean$1.execute(ItemExecutionBean.java:221)
at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
......

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