jobs are hanging in running status
547817Jan 17 2008 — edited Jan 20 2008Hey ,
I have some overnight jobs that refresh materialized views over a dblink from a remote db. I came this morning and noticed that some of the jobs where hanging in RUNNING state with "more data from dblink" event but there was no corresponding sessions in the remote db. It seems like the refresh process was already done (by the size of the mviews). Tracing the session is useless (i've tried) since no actual job is being done. The alert log gave no clue.
any ideas on what the problem is or what to do in order to find it?
could it be a locking issue ?
Thanks