Work Flow Installation Hits OWB RPE-02062 And RPE-2071 (OWB Process Flow In Status "running")

(Doc ID 2108834.1)

Last updated on FEBRUARY 21, 2016

Applies to:

Oracle Life Sciences Data Hub - Version 2.2.0.5 and later
Information in this document applies to any platform.

Symptoms

Work Flow Installation not working. Tested already Partial and Full Installation and nothing works.


ERRORS
----------

Unit Name=WF_APPS_$CREATE_16
RPE-02062: ItemType <ID> cannot be dropped as it has running Processes. You must first abort all the running processes using the Oracle Workflow Monitor.
Unit Name=WF_APPS_$CREATE_16
RPE-02071: Deployment has been aborted due to a previously reported critical error.
fail to complete create deployment
Set install status to $INSTSTATUSES$CREATEACTIVE
set work area status to install failed
OWB deployment ID=<number ID here>

 Before those OWB RPE errors, the following additional ones were displayed, too:

Calling drop deployment
Deploying CDR_W517_9039A7D_$DROP_$DROP_1
Deploying PKG_CDR_W517_9039A7D_1_$DROP_2
Unit Name=PKG_CDR_W517_9039A7D_1_$DROP_2
ORA-04043: object PKG_CREATE_CONTAINER does not exist

Unit Name=PKG_CDR_W517_9039A7D_1_$DROP_2
ORA-04043: object PKG_CREATE_CONTAINER does not exist

Deploying PKG_CDR_W517_9039A7D_1_$DROP_3
Deploying PKG_CDR_W517_9039A7D_2_$DROP_4
Unit Name=PKG_CDR_W517_9039A7D_2_$DROP_4
ORA-04043: object PKG_DATALOAD_EXTENSION does not exist

Unit Name=PKG_CDR_W517_9039A7D_2_$DROP_4
ORA-04043: object PKG_DATAFILELOADING does not exist

Deploying PKG_CDR_W517_9039A7D_3_$DROP_5
Unit Name=PKG_CDR_W517_9039A7D_3_$DROP_5
ORA-04043: object PKG_DQC_CREATOR does not exist

Unit Name=PKG_CDR_W517_9039A7D_3_$DROP_5
ORA-04043: object PKG_LOCK_HELPER does not exist

Unit Name=PKG_CDR_W517_9039A7D_3_$DROP_5
ORA-04043: object PKG_PROGRAM_SUBMITTER does not exist

Setting install status to DROPPED
Set install status to $INSTSTATUSES$DROPPED
Set install status to $INSTSTATUSES$CREATEACTIVE
Calling Create deployment
Deploying CDR_W517_9039A7D_$CREATE_6
Deploying AUX_CDR_W517_9039A7D_0_$CREATE_7
Deploying CDR_W517_9039A7D_0_$CREATE_8
Deploying PKG_CDR_W517_9039A7D_$CREATE_9
Deploying PKG_CDR_W517_9039A7D_$CREATE_10
Deploying PKG_CDR_W517_9039A7D_$CREATE_11
Deploying PKG_CDR_W517_9039A7D_1_$CREATE_12
Deploying PKG_CDR_W517_9039A7D_1_$CREATE_13
Deploying PKG_CDR_W517_9039A7D_2_$CREATE_14
Unit Name=PKG_CDR_W517_9039A7D_2_$CREATE_14
ORA-06550: PACKAGE BODY, line 74, column 6:
PLS-00201: identifier 'PKG_DATAFILELOADING.SP_DEBUGMSG' must be declared
Unit Name=PKG_CDR_W517_9039A7D_2_$CREATE_14
ORA-06550: PACKAGE BODY, line 74, column 6:
PL/SQL: Statement ignored
Unit Name=PKG_CDR_W517_9039A7D_2_$CREATE_14

...
Deploying PKG_CDR_W517_9039A7D_3_$CREATE_15
Unit Name=PKG_CDR_W517_9039A7D_3_$CREATE_15
ORA-06550: PACKAGE BODY, line 112, column 7:
PLS-00201: identifier 'PKG_LOCK_HELPER.PR_GAINLOCK' must be declared
Unit Name=PKG_CDR_W517_9039A7D_3_$CREATE_15
ORA-06550: PACKAGE BODY, line 112, column 7:
PL/SQL: Statement ignored
Unit Name=PKG_CDR_W517_9039A7D_3_$CREATE_15
ORA-06550: PACKAGE BODY, line 127, column 10:
PLS-00201: identifier 'PKG_LOCK_HELPER.PR_RELEASELOCK' must be declared
Unit Name=PKG_CDR_W517_9039A7D_3_$CREATE_15
ORA-06550: PACKAGE BODY, line 127, column 10:
PL/SQL: Statement ignored
...
Unit Name=PKG_CDR_W517_9039A7D_3_$CREATE_15
ORA-06550: PACKAGE BODY, line 112, column 7:
PLS-00201: identifier 'PKG_LOCK_HELPER.PR_GAINLOCK' must be declared
Unit Name=PKG_CDR_W517_9039A7D_3_$CREATE_15
ORA-06550: PACKAGE BODY, line 112, column 7:
PL/SQL: Statement ignored
Unit Name=PKG_CDR_W517_9039A7D_3_$CREATE_15
ORA-06550: PACKAGE BODY, line 127, column 10:
PLS-00201: identifier 'PKG_LOCK_HELPER.PR_RELEASELOCK' must be declared
Unit Name=PKG_CDR_W517_9039A7D_3_$CREATE_15
ORA-06550: PACKAGE BODY, line 127, column 10:
PL/SQL: Statement ignored
...


STEPS TO REPRODUCE
-----------------------
The issue reproduces in this case when doing the Work Flow deployment, when you install the Work Area.

Changes

 RECENT CHANGES: There were a Database restart some hours ago, but there is no issue reported on Database layer. They had a hard reboot and then, the DB instance was started and back to normal. 

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