Dbms_datapump - How to ennusre pl/sql only completes when job completes -

Question

Hi,
Calling dbms_datapump via pl/sql - when look at outpurt directory where log and export file are created it seems to take a while but pl/sql comes back saying complete far earlier.
Uisng 11.2.0.3
Want pl/sql to show complete only when actually complete.
Seems tobe running in background.
declare
  -- Local variables here
  i integer;
h1 number; -- Datapump handle
  dir_name varchar2(30); -- Directory Name
v_file_name varchar2(100);
  v_log_name  varchar2(100); 
v_job_status ku$_Status;          -- The status object returned by get_status
    v_job_state VARCHAR2(4000);
    v_status ku$_Status1010;
    v_logs ku$_LogEntry1010;
    v_row PLS_INTEGER;
    v_current_sequence_number archive_audit.aa_etl_run_num_seq%type;
   v_jobState                user_datapump_jobs.state%TYPE;
begin
--execute immediate ('alter tablespace ARCHIVED_PARTITIONS read only');
-- Get last etl_run_num_seq by querying public synonym ARCHIVE_ETL_RUN_NUM_SEQ
-- Need check no caching on etl_run_num_seq
select last_number - 1
into v_current_sequence_number
from ALL_SEQUENCES A
WHERE A.SEQUENCE_NAME = 'ETL_RUN_NUM_SEQ';
v_file_name := 'archiveexppre.'||v_current_sequence_number;
v_log_name  := 'archiveexpprelog.'||v_current_sequence_number;
dbms_output.put_line(v_file_name);
dbms_output.put_line(v_log_name);
-- Create a (user-named) Data Pump job to do a schema export.
  dir_name := 'DATA_EXPORTS_DIR';
  h1 := dbms_datapump.open(operation =>'EXPORT',
  job_mode =>'TRANSPORTABLE',
  remote_link => NULL,
  job_name    => 'ARCHIVEEXP10');--||v_current_sequence_number);
  dbms_datapump.add_file(handle =>h1,
                         filename => v_file_name,
                         directory => dir_name,
                         filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_DUMP_FILE,
                         reusefile => 1); -- value of 1 instructs to overwrite existing file
  dbms_datapump.add_file(handle =>h1,
                         filename => v_log_name,
                         directory => dir_name,
                         filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_LOG_FILE,
                         reusefile => 1); -- value of 1 instructs to overwrite existing file
  dbms_datapump.metadata_filter(     
      handle => h1,
      name   => 'TABLESPACE_EXPR',
     VALUE    => 'IN(''ARCHIVED_PARTITIONS'')'
--dbms_datapump.metadata_filter(handle =>h1,
  --                       name => 'TABLE_FILTER',
  --                       value => 'BATCH_AUDIT');
-- Start the datapump_job
-- dbms_datapump.set_parameter(h1, 'TRANSPORTABLE', 'ALWAYS');
  dbms_datapump.start_job(h1);
  begin
    null;
    -- dbms_datapump.detach(handle => h1);
  end;
dbms_datapump.wait_for_job(h1,v_jobState);
dbms_output.put_line('Job has completed');
exception
    when others then
      dbms_datapump.get_status(handle => h1,
                             mask => dbms_datapump.KU$_STATUS_WIP,
                             timeout=> 0,
                            job_state => v_job_state,
                            status => v_job_status);
               dbms_output.put_line(v_job_state);
     RAISE_APPLICATION_ERROR(-20010,DBMS_UTILITY.format_error_backtrace);
end;causes this.
How do I ensure the pl/sql job only completes when the dbms_daatpump job completes i.e. runs in the foreground.
Tried adding dbms_datapump.wait_for_job(h1,v_jobState);
but get message job is not attached to this session when add this.
Removed dbms_datapump.detach and now wokrs O.K - seems that dbms_datapump.detach + wait for job are mutually exclusive?
Thanks
Edited by: user5716448 on 28-Sep-2012 06:37
Edited by: user5716448 on 28-Sep-2012 06:37
Edited by: user5716448 on 28-Sep-2012 06:38
Edited by: user5716448 on 28-Sep-2012 06:47
Edited by: user5716448 on 28-Sep-2012 06:50

Answer 1

user5716448 wrote:
Removed dbms_datapump.detach and now wokrs O.K - seems that dbms_datapump.detach + wait for job are mutually exclusive?
If you want your block to WAIT till datapump finishes, why are you detaching? detach means you are no longer interested once the job has started. Remove the detach and keep the wait_for_job as you have found out.