The act_inst_history table is not necessarily always enabled, since it is mainly used to track state change information used for example to calculate actual work times (duration without considering any wait times).
The information you are looking can also be gathered from activity_instance table by using the SQL statement below ...
to_char(to_date('01-JAN-1970','DD-MM-YYYY')+(ai.starttime / (1000 * 60 * 60 * 24)),
'YYYY-MM-DD HH24:MI:SS') "STARTTIME",
to_char(to_date('01-JAN-1970','DD-MM-YYYY')+(ai.lastmodificationtime / (1000 * 60 * 60 * 24)),
'YYYY-MM-DD HH24:MI:SS') "LAST MODIFICATION",
(ai.lastmodificationtime - ai.starttime) "DURATION (ms)"
inner join activity a on (ai.activity = a.oid and ai.model = a.model)
currentuserperformer = 0 and
currentperformer = 0 or
performedby = 0;
If no currentuserperformer or currentperformer is set, the activity instance is not assigned to any user or role work list. If no performedby information is available, the activity instance was never assigned to either a user or role work list. In these cases the activity instance can be considered as a non-interactive one.
[Updated on: Thu, 20 October 2011 11:45] by Moderator
Report message to a moderator