Description:
If the sequences are not created in the TIBCO InConcert database, you will see the IC processes (Event/Action Daemon and IC Notifier) do not start, rather the processes are shown as defunct and the error in the log resembles the following.

***********************************************
2007 May 02 16:28:32:000 GMT +0200 WorkflowServer Error 3 15 1 13062 2 55 55 0 Event/Action Daemon Initialization failed
2007 May 02 16:28:32:000 GMT +0200 WorkflowServer Error 3 5 -2289 13061 2 55 55 0 Event/Action Daemon Undefined status code -2289 for DBMS facility.
2007 May 02 16:28:32:000 GMT +0200 WorkflowServer Error 3 15 1 13060 2 124 124 0 Notifier Daemon Initialization failed
***********************************************
Symptoms:
If the sequences are not created in the TIBCO InConcert (IC) database, you will see the IC processes shown as defunct. Debug enabled log would show something like the following.

***********************************************
16:28:28 (wrkr) 13054 t001: debug: InConcert Worker Startup
16:28:28 (wrkr) 13054 t001: debug: svdbinit before openDatabase syCodeSet='ascii_7'
16:28:28 (wrkr) 13054 t001: debug: svdbinit after openDatabase
16:28:28 (wrkr) 13054 t001: debug: svdbinit after initDatabaseSession
16:28:28 (wrkr) 13054 t001: debug: Oracle Message: -2289 - ORA-02289: sequence does not exist

16:28:28 (wrkr) 13054 t001: debug: Oracle Message: sql - select ID_SEQUENCE.nextval  into :b0  from DUA
L  
16:28:28 (wrkr) 13054 t001: debug: svdbinit Id initialize failed -- <Error, DBMS, -2289>: Undefined status code -2289 for DBMS facility
***********************************************
Cause:
If the sequences are not created in the TIBCO InConcert (IC) database then the IC processes (Event Action Daemon and IC Notifier) does not start successfully and the IC processes is shown as defunct.