Waited for parent session to complete

Hi ,
i have a situation , where i have to put run scenarios in a ODI Package
let me explain
package1 --- scen1-----> scen2------> scen3
package2 ---- scen4-----> scen5--------> scen6
package3 ----- scen7----> scen8--------> scen9
now i have to build a main package , where i have to call above all packages
like
MAIN PACKAGE :
package1_scen-------> package2_scen---------> package3_scen
now , i have to wait for pacakge 1 and all scenarios inside package1 to complete before package2 started and same thing for package3
i tried with odiwaitforchild session , and running packag21_scen, package2_scen, package3_scen in synchronous mode
but when i started the main package all scenarios executed simultaneously.
can any one suggest how to achive this .
Edited by: 916710 on Mar 1, 2012 1:30 AM

i tried , but no help
my requirement is
i have to load first stage(pkg) -----------> diemnsion(pkg)------------> fact(pkg)
and in stage i have multiple files to be loaded into stage tables , which we created as separate packages
so let stage_pkg have 10 scenarios , so i have to wait all 10 Scenarios of stage(pkg) to complete before diemnsion(pkg) will start execution.

Similar Messages

  • Javascript: Wait for a redirect to complete - creating multiple PDF's

    Hi!
    Here is the code that I am using to try to generate multiple reports from javascript. how do I wait for the redirect to complete (ie. generate the PDF) before redirecting to generate the next PDF?
    In the code the "F106_" are application level items.
    I get have been able to get the very first or the very last PDF but none of the other PDF's.
    <script type="text/javascript">
    function f_DoReport() {
      for (i = 2; i <= 3; i++)
         for (j = 1; j <= 4; j++)
             var rgn = '0' + i;
             var dst = '0' + j;
             var vurl = 'f?p=&APP_ID.:30:&SESSION.:FLOW_XMLP_OUTPUT_R27022113101536736_en-us:&DEBUG.::';
             vurl += 'F106_RPT_REGION,F106_RPT_DISTRICT:' + rgn + ',' + dst;
             redirect(vurl);
             alert('rgn: ' + rgn + ' dst: ' + dst);
    </script>Please let me know if I am going down the wrong path here. :D
    As always thanks for your time and help!
    Dave Venus

    A few questions…
    Do you want a script that works with just the active document and you are going to run 300+ times? If so then this may do…
    #target illustrator
    function artboardsToPDFs() {
         if (app.documents.length = 0) {
              reurn;
         } else {
              var docRef = app.activeDocument;
              var docName = docRef.name;
              var baseName = docName.replace(/.ai$/,'');
              var dF = docRef.path.fsName;
              var aB = docRef.artboards;
              var pdfOpts = new PDFSaveOptions();
              pdfOpts.pDFPreset = '[Press Quality]';
              for (var i = 0; i < aB.length; i++) {
                   var numb = (i+1).toString();
                   pdfOpts.artboardRange = numb;
                   var pad = aB.length.toString().length;
                   numb = zeroPad(i+1, pad);
                   var pdfFile = File(dF + '/' + baseName + '_' + numb + '.pdf');
                   if (!pdfFile.exists) {
                        docRef.saveAs(pdfFile, pdfOpts);
                   } else {
                        var rPDF = confirm('File: "' + pdfFile.name + '" already exists…\rDo you wish to replace?',false);
                        if (rPDF) {
                             docRef.saveAs(pdfFile, pdfOpts);
                        } else {
                             continue;
    artboardsToPDFs();
    function zeroPad(n, p) {
      var t = n.toString();
         while (t.length < p) {t = '0' + t};
      return t;
    Do you want to pick a folder of all the illustrator files? If this is the case I would need more info and it would take longer…

  • SHUTDOWN: waiting for active calls to complete.

    Hello,
    environment is HPUX 11.23, Oracle Version is 9.2.0.5
    We had an ORA-600 error yesterday. We reported that error to the support and were suggested to install patch 9.2.0.8.
    However i have one question. As you can see from the output in the alert-logfile it took a very long time to shutdown the instance using the immediate option:
    Sun Nov 9 17:33:58 2008
    Shutting down instance: further logons disabled
    Shutting down instance (immediate)
    License high water mark = 454
    Sun Nov 9 17:39:07 2008
    Active call for process 3991 user 'oracle' program 'oracle@xyz (TNS V1-V3)'
    SHUTDOWN: waiting for active calls to complete.
    Sun Nov 9 17:50:36 2008
    ALTER DATABASE CLOSE NORMAL
    Is there anything one can do in such a situation to speed up the shutdown of the instance ?

    Rajabaskar Thangaraj,
    Oracle database has a job facility and a streams/advanced queuing facility.
    These facilities are possible by setting up a few ancillary processes.
    Those parameters govern the number of processes.
    Setting them to 0 will disable the facility completely.
    As you alter the parameter in memory, as you as you have bounced the database, it will be back to the value in the spfile and the facilities will work again.
    Disabling them is especially useful when you the facilities are frequently used, ie you have a job running every 30 seconds.
    In the past, on several databases, this was the only way to allow a shutdown immediate.
    Hope this helps,
    Sybrand Bakker
    Senior Oracle DBA

  • I tried to import 2 photos from an email. The photos are now on iPhoto, however, when I try to close iPhoto or turn off my computer, I get a notice that says, "Photos are being imported to the photo library. Please wait for the import to complete."

    I tried to import 2 photos from an email to iphoto. The photos now appear in iphoto as the latest imports, However, when I try to close iphoto or log off of my computer, I get a message box that says, " Photos are being imported to the photo library. Please wait for the import to complete."
    I can't get out of iphoto or log off of my computer, or turn the computer off. How do I stop the import or log out of iphoto???

    Try Force-quit from the Apple-menu to close iPhoto.

  • Trying to download a program and get "Waiting for other installations to complete"

    Trying to download a program and get "Waiting for other installations to complete"
    there are no other instalations going on that I know of Please help

    That is for your and your Mac's protection; you need your administrator password to download/install things.

  • Microsoft Excel is waiting for another application to complete an Ole actio

    When I access Data Manager, I get the error message: "Microsoft Excel is waiting for another application to complete an Ole action."  When I click OK, I get another error: "Cannot download the dimension list from server.  Timeout expired.  The timeout period elapsed prior to obtaining a connection from the pool.  This may have occurred because all pooled connections were in use and max pool size was reached."  It never used to happen until recently.  I don't know what to tell the IT guys to do.  Thanks.

    This is a known error in V5. I have had this error at almost every V5 customer.
    The following solution (got it from support) solves it permanently.
    Changes have to be made to the outlooksoft.config file and the connectionstrings in tblappsetinfo. Be sure to restart the server(s) after applying these changes.
    1. In outlooksoft.config file of x:\OutlookSoft\Websrvr\bin folder on the web server change the following line:
    <add key="Database_AppServerDBConn" value="Server=<servername>;Database=AppServer;Trusted_Connection=True;"/>
    to
    <add key="Database_AppServerDBConn" value="Server=<servername>;Database=AppServer;Trusted_Connection=True;pooling=false"/>
    Please note that where I have <servername> you should put the name of your server ****
    Also, add the pooling=false; to every connection string in tblappsetinfo.
    I am sure this helps,
    Regards,
    Alwin Berkhout

  • Waiting for scheduling job to complete. Job ID...and it never completes

    I have created my first Publication. It's a pretty basic single source document, single Dynamic Recipients list publication.
    When I run it in Test mode (I haven't tried it in non-Test mode yet), the document(s) are never delivered.
    When I view the Log File, everything looks fine. The second and last entry in the log says
    "- The global delivery rule for this publication was met; publication processing will now begin."
    The Status Message I see in the Publication History is:
    "Waiting for scheduling job to complete. Job ID:3,879, name:Unviewed Invoices Report (Copy), kind:CrystalReport in Pending state (FBE 60509) [0 recipients processed.] "  and it never changes. I've tried this several times, creating new publications with the same source documents, and the same thing always happens.
    Any help would be appreciated.

    All of the servers were configured correctly.
    It turned out to be my source document, a report, had some field in it that BOE didn't like.
    I removed a bunch of fields and added them back, one by one, and couldn't make the error occur again.
    Go figure.

  • Installer keeps waiting for other installations to complete my downloads.  is this normal?

    I downloaded a microsoft remote desktop application and tried to download my office mac and the installer keeps saying waiting for other installations to complete.  So i thought i needed a restart and the installer won't shut down either.  is this normal?

    Immediate problem solved. After force quitting the Software Update app., iPhoto 9.2 appears to have been successfully installed and functional.  Unable to say if future S/W updates will encounter any problems. Thanks for all consideration. Item closed.
    Aubrey

  • Does WPF waits for GPU present to complete?

    I'm testing how frequently WPF display can change when I have one window per monitor. My frame rate isn't amazing, and using xperf and GPUView it looks like WPF prepares both windows and then calls "Present packet" on both at the same time, and
    waits for both to complete before moving on to send the next frames to the video card. I think my frame rate could have been faster if WPF didn't wait for the present to complete on both displays. When I run two WPF processes, each with one window on
    one monitor, the present packets are independent, so parallel processing is more efficient and the frame rate is higher.
    Did anyone observe the same behavior? Is there a flag I can set to make the WPF windows of one process more independent? 

    Hello Shir Oren,
    I'm confused about those monitors, do you mean you have a computer with a few monitors?
    Then "When I run two WPF processes" can you briefly introduce it here? Different applications on different monitor? Do you actually mean thread but not process here?
    Actually WPF can take advantage of both Hardware and Software Rendering Pipeline, for details please refer to MSDN article:
    https://msdn.microsoft.com/en-us/library/bb613578(v=vs.110).aspx
    I'm not sure whether there is a flag you metioned but I haven't found it at this time. So I recommend you focus on the exist WPF render tiers from here
    https://msdn.microsoft.com/en-us/library/ms742196(v=vs.110).aspx to consider raise your performance.
    Best regards,
    Barry
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Query "Stuck" in CXPacket wait with no other waits for that session id in the blocking session id of sys.dm_os_waiting_tasks

    So I have a query that is running with a large number of CXPacket waits.  There are no other tasks in the sys.dm_os_waiting_tasks that are blocking this session id with a wait other than CXPacket Wait.  This is taking place on a SQL Server 2008
    R2 machine.  My question is there something else to look at?  I've gone ahead and posted the output of the entire sys.dm_os_waiting_tasks.  Any thoughts?
    waiting_task_address    session_id    exec_context_id    wait_duration_ms    wait_type    resource_address    blocking_task_address    blocking_session_id  
     blocking_exec_context_id    resource_description
    0x0000000004E88988    NULL    NULL    13525    FT_IFTS_SCHEDULER_IDLE_WAIT    NULL    NULL    NULL    NULL    NULL
    0x0000000004E89288    NULL    NULL    64128606    DISPATCHER_QUEUE_SEMAPHORE    NULL    NULL    NULL    NULL    NULL
    0x0000000004ED6748    2    0    19502    XE_TIMER_EVENT    NULL    NULL    NULL    NULL    NULL
    0x0000000004450508    3    0    2779501    XE_DISPATCHER_WAIT    NULL    NULL    NULL    NULL    NULL
    0x000000000446A748    4    0    838    LAZYWRITER_SLEEP    NULL    NULL    NULL    NULL    NULL
    0x000000000448E508    5    0    438    REQUEST_FOR_DEADLOCK_SEARCH    0x000000000B9301F8    NULL    NULL    NULL    NULL
    0x0000000004E88508    6    0    1304946379    KSOURCE_WAKEUP    NULL    NULL    NULL    NULL    NULL
    0x0000000004484508    7    0    146961    LOGMGR_QUEUE    0x0000000003597248    NULL    NULL    NULL    NULL
    0x00000000804942C8    9    0    3366    SQLTRACE_INCREMENTAL_FLUSH_SLEEP    NULL    NULL    NULL    NULL    NULL
    0x000000000448E748    10    0    929    SLEEP_TASK    NULL    NULL    NULL    NULL    NULL
    0x0000000004450988    11    0    26214727    BROKER_EVENTHANDLER    NULL    NULL    NULL    NULL    NULL
    0x0000000004EBC508    12    0    1304959888    ONDEMAND_TASK_QUEUE    0x0000000003575508    NULL    NULL    NULL    NULL
    0x0000000004EA2508    13    0    146959    CHECKPOINT_QUEUE    0x0000000003590C70    NULL    NULL    NULL    NULL
    0x0000000004EA2748    14    0    1304947282    BROKER_TRANSMITTER    NULL    NULL    NULL    NULL    NULL
    0x0000000004484988    16    0    1304947282    BROKER_TRANSMITTER    NULL    NULL    NULL    NULL    NULL
    0x000000000446AE08    154    0    19974433    CXPACKET    0x0000000804ECC1D0    0x0000000255EFEBC8    154    19    exchangeEvent
    id=Port80263100 WaitType=e_waitPortOpen nodeId=4
    0x000000000446AE08    154    0    19974433    CXPACKET    0x0000000804ECC1D0    0x0000000258D26748    154    17    exchangeEvent
    id=Port80263100 WaitType=e_waitPortOpen nodeId=4
    0x000000000446AE08    154    0    19974433    CXPACKET    0x0000000804ECC1D0    0x0000000258DB0E08    154    18    exchangeEvent
    id=Port80263100 WaitType=e_waitPortOpen nodeId=4
    0x000000000446AE08    154    0    19974433    CXPACKET    0x0000000804ECC1D0    0x000000025A392748    154    21    exchangeEvent
    id=Port80263100 WaitType=e_waitPortOpen nodeId=4
    0x000000000446AE08    154    0    19974433    CXPACKET    0x0000000804ECC1D0    0x0000000258DB2E08    154    20    exchangeEvent
    id=Port80263100 WaitType=e_waitPortOpen nodeId=4
    0x000000000446AE08    154    0    19974433    CXPACKET    0x0000000804ECC1D0    0x000000025C694508    154    23    exchangeEvent
    id=Port80263100 WaitType=e_waitPortOpen nodeId=4
    0x000000000446AE08    154    0    19974433    CXPACKET    0x0000000804ECC1D0    0x000000025A675708    154    24    exchangeEvent
    id=Port80263100 WaitType=e_waitPortOpen nodeId=4
    0x000000000446AE08    154    0    19974433    CXPACKET    0x0000000804ECC1D0    0x00000001D3F902C8    154    22    exchangeEvent
    id=Port80263100 WaitType=e_waitPortOpen nodeId=4
    0x0000000004EBCE08    154    1    18269246    CXPACKET    0x000000080C705200    0x000000000448FB88    154    13    exchangeEvent
    id=Pipe2f6220e00 WaitType=e_waitPipeGetRow nodeId=33
    0x0000000004485288    154    2    18269246    CXPACKET    0x000000080CD4F200    0x000000000448FB88    154    13    exchangeEvent
    id=Pipe2f6220f00 WaitType=e_waitPipeGetRow nodeId=33
    0x0000000004EA3B88    154    3    18269246    CXPACKET    0x000000080CCDD200    0x000000000448FB88    154    13    exchangeEvent
    id=Pipe2f6221000 WaitType=e_waitPipeGetRow nodeId=33
    0x0000000004ED7948    154    4    18269246    CXPACKET    0x000000080CC8B200    0x000000000448FB88    154    13    exchangeEvent
    id=Pipe2f6220f80 WaitType=e_waitPipeGetRow nodeId=33
    0x000000000448F708    154    5    18269242    CXPACKET    0x000000080CD41200    0x000000000448FB88    154    13    exchangeEvent
    id=Pipe2f6220e80 WaitType=e_waitPipeGetRow nodeId=33
    0x0000000004451B88    154    6    18269245    CXPACKET    0x000000080CE31200    0x000000000448FB88    154    13    exchangeEvent
    id=Pipe2f6221080 WaitType=e_waitPipeGetRow nodeId=33
    0x0000000004E89048    154    7    18269246    CXPACKET    0x000000080D12B200    0x000000000448FB88    154    13    exchangeEvent
    id=Pipe2f6221100 WaitType=e_waitPipeGetRow nodeId=33
    0x000000000446ABC8    154    8    18269243    CXPACKET    0x000000080CE7D200    0x000000000448FB88    154    13    exchangeEvent
    id=Pipe2f6221200 WaitType=e_waitPipeGetRow nodeId=33
    0x0000000258D26748    154    17    18270546    CXPACKET    0x000000025C763020    0x0000000004EBCE08    154    1    exchangeEvent
    id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258D26748    154    17    18270546    CXPACKET    0x000000025C763020    0x000000000448F708    154    5    exchangeEvent
    id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258D26748    154    17    18270546    CXPACKET    0x000000025C763020    0x0000000004485288    154    2    exchangeEvent
    id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258D26748    154    17    18270546    CXPACKET    0x000000025C763020    0x0000000004ED7948    154    4    exchangeEvent
    id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258D26748    154    17    18270546    CXPACKET    0x000000025C763020    0x0000000004EA3B88    154    3    exchangeEvent
    id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258D26748    154    17    18270546    CXPACKET    0x000000025C763020    0x0000000004451B88    154    6    exchangeEvent
    id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258D26748    154    17    18270546    CXPACKET    0x000000025C763020    0x0000000004E89048    154    7    exchangeEvent
    id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258D26748    154    17    18270546    CXPACKET    0x000000025C763020    0x000000000446ABC8    154    8    exchangeEvent
    id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB0E08    154    18    19974425    CXPACKET    0x00000008064DD020    0x0000000004EBCE08    154    1    exchangeEvent
    id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB0E08    154    18    19974425    CXPACKET    0x00000008064DD020    0x000000000448F708    154    5    exchangeEvent
    id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB0E08    154    18    19974425    CXPACKET    0x00000008064DD020    0x0000000004485288    154    2    exchangeEvent
    id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB0E08    154    18    19974425    CXPACKET    0x00000008064DD020    0x0000000004ED7948    154    4    exchangeEvent
    id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB0E08    154    18    19974425    CXPACKET    0x00000008064DD020    0x0000000004EA3B88    154    3    exchangeEvent
    id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB0E08    154    18    19974425    CXPACKET    0x00000008064DD020    0x0000000004451B88    154    6    exchangeEvent
    id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB0E08    154    18    19974425    CXPACKET    0x00000008064DD020    0x0000000004E89048    154    7    exchangeEvent
    id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB0E08    154    18    19974425    CXPACKET    0x00000008064DD020    0x000000000446ABC8    154    8    exchangeEvent
    id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000255EFEBC8    154    19    18269474    CXPACKET    0x0000000806355020    0x0000000004EBCE08    154    1    exchangeEvent
    id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000255EFEBC8    154    19    18269474    CXPACKET    0x0000000806355020    0x000000000448F708    154    5    exchangeEvent
    id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000255EFEBC8    154    19    18269474    CXPACKET    0x0000000806355020    0x0000000004485288    154    2    exchangeEvent
    id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000255EFEBC8    154    19    18269474    CXPACKET    0x0000000806355020    0x0000000004ED7948    154    4    exchangeEvent
    id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000255EFEBC8    154    19    18269474    CXPACKET    0x0000000806355020    0x0000000004EA3B88    154    3    exchangeEvent
    id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000255EFEBC8    154    19    18269474    CXPACKET    0x0000000806355020    0x0000000004451B88    154    6    exchangeEvent
    id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000255EFEBC8    154    19    18269474    CXPACKET    0x0000000806355020    0x0000000004E89048    154    7    exchangeEvent
    id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000255EFEBC8    154    19    18269474    CXPACKET    0x0000000806355020    0x000000000446ABC8    154    8    exchangeEvent
    id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB2E08    154    20    18270502    CXPACKET    0x0000000805CC1020    0x0000000004EBCE08    154    1    exchangeEvent
    id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB2E08    154    20    18270502    CXPACKET    0x0000000805CC1020    0x000000000448F708    154    5    exchangeEvent
    id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB2E08    154    20    18270502    CXPACKET    0x0000000805CC1020    0x0000000004485288    154    2    exchangeEvent
    id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB2E08    154    20    18270502    CXPACKET    0x0000000805CC1020    0x0000000004ED7948    154    4    exchangeEvent
    id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB2E08    154    20    18270502    CXPACKET    0x0000000805CC1020    0x0000000004EA3B88    154    3    exchangeEvent
    id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB2E08    154    20    18270502    CXPACKET    0x0000000805CC1020    0x0000000004451B88    154    6    exchangeEvent
    id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB2E08    154    20    18270502    CXPACKET    0x0000000805CC1020    0x0000000004E89048    154    7    exchangeEvent
    id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB2E08    154    20    18270502    CXPACKET    0x0000000805CC1020    0x000000000446ABC8    154    8    exchangeEvent
    id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A392748    154    21    18322346    CXPACKET    0x0000000806395020    0x0000000004EBCE08    154    1    exchangeEvent
    id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A392748    154    21    18322347    CXPACKET    0x0000000806395020    0x000000000448F708    154    5    exchangeEvent
    id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A392748    154    21    18322347    CXPACKET    0x0000000806395020    0x0000000004485288    154    2    exchangeEvent
    id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A392748    154    21    18322347    CXPACKET    0x0000000806395020    0x0000000004ED7948    154    4    exchangeEvent
    id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A392748    154    21    18322347    CXPACKET    0x0000000806395020    0x0000000004EA3B88    154    3    exchangeEvent
    id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A392748    154    21    18322347    CXPACKET    0x0000000806395020    0x0000000004451B88    154    6    exchangeEvent
    id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A392748    154    21    18322347    CXPACKET    0x0000000806395020    0x0000000004E89048    154    7    exchangeEvent
    id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A392748    154    21    18322347    CXPACKET    0x0000000806395020    0x000000000446ABC8    154    8    exchangeEvent
    id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
    0x00000001D3F902C8    154    22    18270621    CXPACKET    0x000000025CE67020    0x0000000004EBCE08    154    1    exchangeEvent
    id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
    0x00000001D3F902C8    154    22    18270621    CXPACKET    0x000000025CE67020    0x000000000448F708    154    5    exchangeEvent
    id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
    0x00000001D3F902C8    154    22    18270621    CXPACKET    0x000000025CE67020    0x0000000004485288    154    2    exchangeEvent
    id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
    0x00000001D3F902C8    154    22    18270621    CXPACKET    0x000000025CE67020    0x0000000004ED7948    154    4    exchangeEvent
    id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
    0x00000001D3F902C8    154    22    18270621    CXPACKET    0x000000025CE67020    0x0000000004EA3B88    154    3    exchangeEvent
    id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
    0x00000001D3F902C8    154    22    18270621    CXPACKET    0x000000025CE67020    0x0000000004451B88    154    6    exchangeEvent
    id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
    0x00000001D3F902C8    154    22    18270621    CXPACKET    0x000000025CE67020    0x0000000004E89048    154    7    exchangeEvent
    id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
    0x00000001D3F902C8    154    22    18270621    CXPACKET    0x000000025CE67020    0x000000000446ABC8    154    8    exchangeEvent
    id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025C694508    154    23    18270541    CXPACKET    0x000000025C75D020    0x0000000004EBCE08    154    1    exchangeEvent
    id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025C694508    154    23    18270541    CXPACKET    0x000000025C75D020    0x000000000448F708    154    5    exchangeEvent
    id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025C694508    154    23    18270541    CXPACKET    0x000000025C75D020    0x0000000004485288    154    2    exchangeEvent
    id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025C694508    154    23    18270541    CXPACKET    0x000000025C75D020    0x0000000004ED7948    154    4    exchangeEvent
    id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025C694508    154    23    18270541    CXPACKET    0x000000025C75D020    0x0000000004EA3B88    154    3    exchangeEvent
    id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025C694508    154    23    18270541    CXPACKET    0x000000025C75D020    0x0000000004451B88    154    6    exchangeEvent
    id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025C694508    154    23    18270541    CXPACKET    0x000000025C75D020    0x0000000004E89048    154    7    exchangeEvent
    id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025C694508    154    23    18270541    CXPACKET    0x000000025C75D020    0x000000000446ABC8    154    8    exchangeEvent
    id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A675708    154    24    18269840    CXPACKET    0x000000025C767020    0x0000000004EBCE08    154    1    exchangeEvent
    id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A675708    154    24    18269840    CXPACKET    0x000000025C767020    0x000000000448F708    154    5    exchangeEvent
    id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A675708    154    24    18269840    CXPACKET    0x000000025C767020    0x0000000004485288    154    2    exchangeEvent
    id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A675708    154    24    18269840    CXPACKET    0x000000025C767020    0x0000000004ED7948    154    4    exchangeEvent
    id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A675708    154    24    18269840    CXPACKET    0x000000025C767020    0x0000000004EA3B88    154    3    exchangeEvent
    id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A675708    154    24    18269840    CXPACKET    0x000000025C767020    0x0000000004451B88    154    6    exchangeEvent
    id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A675708    154    24    18269840    CXPACKET    0x000000025C767020    0x0000000004E89048    154    7    exchangeEvent
    id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A675708    154    24    18269840    CXPACKET    0x000000025C767020    0x000000000446ABC8    154    8    exchangeEvent
    id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17

    Hello,
    First, I would take a look at what your MAXDOP setting is, that's seems a bit high unless you have around 80 processors - stick to multiples of the number of processors in a single numa node and don't go over half of the numa nodes if this is for an OLTP
    system. If it's for a DSS or DW system then having a very high maxdop should be fine.
    When dealing with CXPACKET the wait means that it's waiting for all of the parallel threads to complete before it can merge the results and move on. If any single thread has to process more than any other (or waits longer for data) the whole process has
    to wait. I would investigate to see if there is a large skew in statistics and one thread is processing much more than another. I'd also try creating an extended events session to grab all of the waitinfo for that session.
    Sean Gallardy | Blog |
    Twitter

  • How to get OIM workflow waiting for a task successfully completed?

    The requirement is to get OIM provisiong workflow pending and wait for a external status ready. When the external status not ready, I return "REJECTED" which mapped to "P" in "Task->Reponse" tab. Meanwhile, in the "Task->General" tab, I set the "Retry Count" to 5 and "Retry Period in Minutes" to 1.
    I have hoped that once the task return "REJECTED", the workflow enter status "Pending". One minute later, the task re-instanced by OIM to have another check for whether the external status ready. If ready, return "COMPLETED". If not yet, return "REJECTED" and workflow re-enter pending. And on and on, until to max to 5 times attempt. But in fact, OIM workflow never attempt to re-enter the task again after the 1st time "REJECTED" returned.
    How to do with this?

    Use the code snippet below to get the task status. Based on this you can filter rejected tasks.
    userintf = (tcUserOperationsIntf) ioUtilityFactory.getUtility("Thor.API.Operations.tcUserOperationsIntf");
    provintf = (tcProvisioningOperationsIntf)ioUtilityFactory.getUtility("Thor.API.Operations.tcProvisioningOperationsIntf");
    long userKey=100;
    tcResultSet userresultSet = userintf.getObjects(userKey);
    for(int i=0;i<userresultSet.getRowCount();i++)
         userresultSet.goToRow(i);
         long processKey = userresultSet.getLongValue("Process Instance.Key");
         tcResultSet provresultSet = provintf.getProcessDetail(processKey);
         for(int j=0; i<provresultSet.getRowCount();j++)
              provresultSet.goToRow(j);
              String taskName = provresultSet.getStringValue("Process Definition.Tasks.Task Name");
              String taskStatus = provresultSet.getStringValue("Process Instance.Task Details.Status");
    Let me know if you have any queries...

  • Patched Deployments issue: "waiting for another installation to complete"

    I have some percent of computers which runs into above state in monthly patch deployments. I could minimal information from execmgmr, udpatesdeployment.log,
    CliSpy and Client Center etc tools but that doesn’t offer much help to nail down the issue completely. Have any of you dealt to resolve such issue successfully ? Is there any efficient way to handle this ?
    It seems I have
    DeploymentA, waiting for the completion of DeploymentB, which in turn waiting for the completion of
    DeploymentC. Is there any better approach I could take to nail down and resolve the issue. One of my finding is,  KB articles installs (SCCM R3, SCCM Asset Intelligence) causes these issue as they restart (upgrade sort of execution) the
    agent during the execution, I need to confirm these
    Vasu

    Hi Vasu,
    This issue can be caused by a deployment was previously deployed and was now deleted. This was because the clients finished installation
    and wanted to notify the Server that it is done, but since the deployment was deleted, it couldn’t Notify its progress to the site server and the CCM_DeploymentTaskEx1 got stuck.
    Please use the following scripts to delete the instance to test this issue.
    strService = "CcmExec"
    strComputer = "."
    Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\CCM\SoftwareUpdates\DeploymentAgent")
    Set colWMISettings = objWMIService.ExecQuery("Select * from CCM_DeploymentTaskEx1")
    For Each objWMISetting in colWMISettings
    objWMISetting.AssignmentId = ""
    objWMISetting.JobId = "{00000000-0000-0000-0000-000000000000}"
    objWMISetting.Put_
    Next
    'Stop service
    Set objWMI = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")
    Set objService = objWMI.Get("Win32_Service.Name='" & strService & "'")
    objService.StopService()
    WScript.Sleep 10000 ' Pause to allow service to stop
    'Start service
    Set objService = objWMI.Get("Win32_Service.Name='" & strService & "'")
    objService.StartService()
    WScript.Sleep 10000 ' Pause to allow service to start
    Regards,
    Sabrina
    This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.
    This can be beneficial to other community members reading the thread.

  • Waiting for a Job to Complete

    Hi,
    How would people suggest waiting for a background process (a job submitted using APEX_PLSQL_JOB) to complete.
    I'm thinking of having an On Demand that can query the job status and then calling this from a piece of JavaScript which polls periodically (e.g. every 30 seconds using the setTimeout function).
    Does anyone have any pointers to something more elegant?
    Many thanks,
    Gareth.

    Hi
    Interesting one this, check out this link [http://www.oraclequirks.com/]
    Half way down the page on the left there's a link titled 'Yocoya's Flash Progress Bar Indicator Live Demo' that you might find useful.
    Cheers
    Ben

  • Publish action waits for request to get completed in OSB11g

    Hi all,
    I am using OSB 11g. Following is my scenario:
    1) ProxyService1(wsdl based Proxy) publishes to ProxyService2(local Proxy)
    2) ProxyService2 routes to an MQ Posting BusinessService
    In ProxyService1 Response Pipeline, I have configured a dummy response irrespective of the Request.
    When I keep the Retry Count of BusinessService as 3 and Retry Iteration Interval as 120, and test ProxyService1 by keeping the Queue down, it waits for 6 minutes to give the dummy response.
    I do not want the ProxyService1 to get held up for such a long time. It should fire-and-forget the request and give response immediately. I even tried to Publish to the BusinessService. Still the same problem. Can anyone guide me?
    Thanks in advance!
    Regards,
    Karthik
    Edited by: Karthik Krishnamurthy on May 13, 2011 2:32 AM

    I know this might be late, but just wanted to mention that you can publish to a Proxy/Business Service asynchronously using the Routing Options (Quality of Service: Best Effort) with the publish action.
    This will ensure that the Calling proxy does not wait for a response from the provider (be it Proxy/Business Service). If we use this OSB will try its best to publish it, but does not guarantee that the message be delivered. But as long as the provider is available, the message is processed separately and does not block the main calling proxy.
    We use this scenarios frequently in our project. So just wanted to pass it on :)
    You can find a snap shot @ http://dl.dropbox.com/u/19901533/OSB_Publish_Action.JPG
    Refer to http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageflow.html#wp1134375 for more information.
    Thanks,
    Patrick

  • Waiting for Sub Process to complete

    Hi,
    Below mentioned is my requirement:
    1. Main process begins
    2. Copy a tar file from a source directory to target directory.
    3. Call a sub-process to untar the file (using MKS tool kit utility from command prompt).
    4. sub-process ends
    5. Work on the folders (untared) by applying rules.
    6. Main process ends.
    When I call sub-process like
    main() // main method
    // calling sub-process
    Process p = Runtime.getRuntime().exec(tar -xvf C:\\Source\\ -C C:\\Target);
    p.waitFor();
    // calling rules
    rule("C:\\Target"); // private method to perform validation on the untared files located in Target folder.
    //main method ends
    The program gets stuck up here.
    The file size to untar is small (1MB). But, after some time, when I kill the main process, I could see sub-process completing its task.
    Can you any one suggest me to know the sub-process completion, so that I could call my rules()

    I f you read the documentation for exec() and Process carefully you will find that when you an exec() a process, pipes are created back to the main process for the stdout and sterr of the sub-process. Those pipes have a finite size and when full the sub-process will block, hence waitFor() will wait forever.
    You need to create threads to drain stdout/stderr of the sub-process, or else re-direct the subprocess output (start a shell to run the actual command) so that the pipes won't get full and block.

Maybe you are looking for

  • HP 530 notebook PC - hard drive and RAM upgrade

    Hello, I'm using HP 530 and I want to upgrade it's hard drive. In documentation specified that my notebook supports only 80/120Gb hard drives and up to 2Gb RAM. Is it true? Can't i use more capacious HDD or RAM. And what type of HDD i should by? Is i

  • How do I get to speak to a management level executive to resolve a denial of 3-$100 / line credits

    In March of this year I signed up for 3 new lines and was assured by the sales representative Mr. Christopher (removed) that each line would receive a $100 credit.  Over the past 5 months each time I contacted customer service about the credits, I wa

  • Authentication and authorization done by different LDAP servers

    Is this possible with iPlanet LDAP Authenticator I want authentication to be done against LDAPServer A but authorization [ role assignment ] done by another LDAP Server B ? the authenticator only permits me to enter one server name would I need to wr

  • Possible no  of lines of rows in webdynpro table

    Hi Friends, is there any number of lines of records restriction in webdynpro application? Is it that if more number of record, then we should go for HTMB controls/JSPPage/JSPDynPage? Thanks Nav Message was edited by: Nav

  • WHEN is the red pureview coming out???

    Seriously want to get a pureview, but in red only. Anyone knows when it is coming out? Are they trying to do what Samsung did with their Galaxy S2 (white) which came out months later to boost the sales? I'm not sure if I can last till then as I might