Parallel PL/SQL with DBMS_PARALLEL_EXECUTE

October 17, 2013 4 Comments


My blog has moved, the article you are looking for can be found here:
https://seanstuber.com/2013/10/17/parallel-plsql-with-dbms_parallel_execute/

Filed under Oracle

About Sean D. Stuber
Developer, DBA, Oracle ACE

4 Responses to Parallel PL/SQL with DBMS_PARALLEL_EXECUTE

  1. Janardhana Reddy says:
    March 10, 2016 at 2:23 am

    Hi Sean,

    Your blog about the topic (Parallel PL/SQL with DBMS_PARALLEL_EXECUTE) was what i was looking for to implement. It was very helpful example

    Calling a procedure multiple times with different parameters (Parallel processing)

    Topic : Parallel PL/SQL with DBMS_PARALLEL_EXECUTE

    URL : https://seanstuber.wordpress.com/2013/10/17/parallel-plsql-with-dbms_parallel_execute/

    I am just using the same code what was written by you and compiled it.

    I am able to compile the code but when executing the procedure i am getting the below error :

    Command user for execution : EXEC parallel_exec_test_proc

    Error Message :

    [Error] Execution (2: 1): ORA-29497: duplicate task name
    ORA-06512: at “SYS.DBMS_PARALLEL_EXECUTE_INTERNAL”, line 170
    ORA-00001: unique constraint (SYS.PK_DBMS_PARALLEL_EXECUTE_1) violated
    ORA-06512: at “SYS.DBMS_PARALLEL_EXECUTE”, line 86
    ORA-06512: at “NDS.PARALLEL_EXEC_TEST_PROC”, line 8
    ORA-06512: at line 1

    Your help regarding this issue will be much appreciated..

    Like

    Reply
    • Sean D. Stuber says:
      March 13, 2016 at 3:57 pm

      The test procedures create and execute the tasks but do not remove them.
      I did that intentionally for the tests to leave objects around to investigate after execution.

      You can see yours with

      SELECT task_name, status FROM user_parallel_execute_tasks;

      Then to clean them up, assuming you ran both tests cases…

      BEGIN
      DBMS_PARALLEL_EXECUTE.drop_task(‘parallel_test1’);
      DBMS_PARALLEL_EXECUTE.drop_task(‘parallel_test2’);
      END;

      It would be ok to add these to the test procedures yourself so they do their own cleanup, but then you lose the status tracking.

      Alternately, change the code to create a unique task name each time and then you can compare multiple runs over time and do clean up later when you no longer need them.

      Like

      Reply
  2. waseem says:
    March 18, 2019 at 9:58 am

    Hi Sean – I cannot access the link, please help

    Like

    Reply
    • Sean D. Stuber says:
      March 18, 2019 at 7:07 pm

      I just tested the link, it worked.
      You should also be able to simply copy the url into your browser.

      If that doesn’t work, you can reply back here, but please provide some details about exactly what you tried and what the error is.

      Like

      Reply

Questions and Comments always welcome