Mapping hangs when controlcentre service is down (wb_rt_notify_queue)

Question

Hi,
Running OWB standalone (OWB 10gR2, db 10.2.0.4, IBM AIX), i.e. the db has a control center repository for the runtime, no running control center service (a.k.a. runtime platform service).
Executing mappings using a call to wb_rt_api_exec.run_task().
This used to work fine until last Friday.
However when I execute any mapping today, the mapping runs endlessly, the status in in the WB Browser in the local repository is 'Busy' and in v$session_wait I find one wait event, "Streams AQ: waiting for messages in the queue" and the P1 value of this wait event points via dba_objects to the OWB internal AQ wb_rt_notify_queue.
Also ran a 10046 sql trace on the call to run_task() and that never starts on any business related SQL, the trace file just keeps repeating the wait event.
The AQ Queue table wb_rt_notify_queue_tab holds some 3000 entries, the newest is from last Friday, so nothing from my last run_task() attempts.
I checked the docs and forums, and it is confirmed that running a remote deployment target without a local CCS/RTP is valid (and was working.)
Metalink, OTN forums and Google are quite silent on this issue.
What is going on and how to fix it?
Thanks for your help,
Erik
Edited by: ErikYkema on Oct 13, 2009 10:25 PM - Changed title, was "Streams AQ: Waiting for messages in the queue" on wb_rt_notify_queue

Answer 1

Thanks a lot Oleg,
I now see I got things mixed up...
Here some summary for the benefit of others.
This means that for a standalone target schema without control centre service, wb_rt_api_exec is not possible, nor sqlplus_exec_template.sql nor run_my_owb_stuff.sql. Only calling main on the mapping package will work.
Will either start that remote control center service (See Metalink Note 402401.1 - How to Setup a Remote Contol Center Service or Remote Runtime with OWB 10.2. This note explains how to construct the call to run_service.sh, and also that the password needs to be echoed to that script.)
Or I will call the main procedure. The system parameters and custom parameters are available on the procedure's in parameters.
The runtime tables will be filled when using mapping.main() procedure for a PLSQL type task - however no runtime custom ('user') parameters will be stored in the runtime repository.
I personally prefer the run_task() method (with remote CCS) since the passing of parameters is nicer.
However the availability of the CCS I need to guarantee myself, as the dba_jobs job in the standalone cannot start the service effectively.
Regards,
Erik
Edited by: ErikYkema on Oct 14, 2009 3:31 PM - to reflect Oleg's comments from next message in thread.