[11g] Datapump Export "job_state" comes back "STOPPED" but no error in log.

Question

Hello,
First of all, here are the SQL statements that I'm executing:
BEGIN :JobId := Dbms_DataPump.Open(operation => 'EXPORT', job_mode => 'TABLE'); END;
BEGIN
  Dbms_DataPump.Add_File(handle => :JobId, filename => 'MYORACLEBACKUP1', directory => 'ABAT_DUMP_DIR', filetype => 1, reusefile => 1); --DMP
  Dbms_DataPump.Add_File(handle => :JobId, filename => 'MYORACLEBACKUP.log', directory => 'ABAT_DUMP_DIR', filetype => 3); --LOG
  Dbms_DataPump.Metadata_Filter(handle => :JobId, name => 'SCHEMA_LIST', value => '''PRTO9A''');
  Dbms_DataPump.Metadata_Filter(handle => :JobId, name => 'NAME_LIST', value => '''ALERTS''');
  Dbms_DataPump.Set_Parallel(handle => :JobId, degree => 1);
  Dbms_DataPump.Start_Job(handle => :JobId);
  Dbms_DataPump.Wait_For_Job(handle => :JobId, job_state => :JobState);
END;Now, I actually construct this using C#, so "PRTO9A" and "ALERTS" are dynamically queried for. This means that they are definitely valid schemas / tables. Also, a consequence of using C# is that the two variables :JobId and :JobState come from the .NET implementation of this DB stuff (in other words, I specify "JobId" and "JobState" as input or output variables in the C# code before I run the query... JobId is an output variable in the first statement, but an input variable in the second one).
The result is that "JobState" comes back "STOPPED," which is documented as an error:
When WAIT_FOR_JOB returns, the job will no longer be executing. If the job completed normally, the final status will be Completed. If the job stopped executing because of a STOP_JOB request or an internal error, the final status will be Stopped.OK, so I get a "STOPPED" back, which means there's an error. Let me check the log file (MYORACLEBACKUP.log)...
Starting "SYSTEM"."SYS_EXPORT_TABLE_01": 
Estimate in progress using BLOCKS method...
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 448 KB
Processing object type TABLE_EXPORT/TABLE/TABLE
Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
. . exported "PRTO9A"."ALERTS"                           250.6 KB     316 rows
Master table "SYSTEM"."SYS_EXPORT_TABLE_01" successfully loaded/unloaded
Dump file set for SYSTEM.SYS_EXPORT_TABLE_01 is:
  C:\TMP\MYORACLEBACKUP1.DMP
Job "SYSTEM"."SYS_EXPORT_TABLE_01" successfully completed at 12:30:03What the..? "... successfully completed at 12:30:03?" But I thought there was supposed to be an error?
Any ideas?
Thanks!
EDIT: By the way, the "MYORACLEBACKUP1.DMP" file is actually created, and at a glance it looks valid. I haven't tried importing it yet.
Edited by: bdzevel on Feb 11, 2013 9:38 AM

Answer 1

OK I finally got around to trying "GET_STATUS." This issue looks deep.
So, my original issue was that my "JOB_STATE" was coming back "Stopped" instead of "Completed." I did a "GET_STATUS" of a "Stopped" (but successful) job, and, as I expected, I got error_count 0, and the error table is null. Fine, so I will check the "GET_STATUS" if I get a "Stopped..."
So I tried the complementary case, where I have a job that will fail. In this case, it's expected to get a "Stopped" status back (even though it's 'faulty' in the sense that it's ALWAYS "Stopped"). Checking the error_count, I get 0 back. WHAT!? AND the error table is STILL null! What the heck is going on?
Here's my new SQL:
DECLARE
  state VARCHAR2(15);
  output KU$_STATUS1010;
  errorTable KU$_LogEntry1010;
BEGIN
  Dbms_DataPump.Add_File(handle => :JobId, filename => 'MYORACLEBACKUP_bdzevel1.dmp', directory => 'ABAT_DUMP_DIR', filetype => 1, reusefile => 1); --DMP
  Dbms_DataPump.Add_File(handle => :JobId, filename => 'MYORACLEBACKUP_bdzevel2.dmp', directory => 'ABAT_DUMP_DIR', filetype => 1, reusefile => 1); --DMP
  Dbms_DataPump.Add_File(handle => :JobId, filename => 'MYORACLEBACKUP_bdzevel.log', directory => 'ABAT_DUMP_DIR', filetype => 3); --LOG
  Dbms_DataPump.Metadata_Filter(handle => :JobId, name => 'SCHEMA_LIST', value => '''DATAPUMPUSER''');
  Dbms_DataPump.Metadata_Filter(handle => :JobId, name => 'NAME_LIST', value => '''MYTESTTABLE_FAKEEEE''');
  Dbms_DataPump.Set_Parallel(handle => :JobId, degree => 2);
  Dbms_DataPump.Start_Job(handle => :JobId);
  Dbms_DataPump.Wait_For_Job(handle => :JobId, job_state => :JobState);
  :ErrorMessage := '';
  IF upper(:JobState) = 'STOPPED' THEN
    Dbms_DataPump.Get_Status(handle => :JobId, mask => 15, timeout => NULL, job_state => state, status => output);
    errorTable := output.ERROR;
    IF errorTable IS NOT NULL AND errorTable.COUNT > 0 THEN
      FOR element in 1 .. errorTable.COUNT LOOP
        IF :ErrorMessage = '' THEN
          :ErrorMessage := :ErrorMessage || CHR(13) || CHR(10);
        END IF;
        :ErrorMessage := :ErrorMessage || TO_CHAR(errorTable(element).LOGLINENUMBER) || ': ORA' || TO_CHAR(errorTable(element).ERRORNUMBER) || ' - ' || errorTable(element).LOGTEXT;
      END LOOP;
    END IF;
    :ErrorMessage := :ErrorMessage || output.JOB_STATUS.JOB_NAME || ' ' || output.JOB_STATUS.ERROR_COUNT || ' ' || output.JOB_STATUS.STATE;
  END IF;
END;The error I get back in both cases reads "SYS_TEXPORT_TABLE_04 0 COMPLETED" (which is in the format JOB_NAME ERROR_COUNT STATE, as you can see above), but in the latter case (a FAILED job... as you can see above, I have "MYTESTTABLE_FAKEEEE" as my table, which doesn't exist, and a consequence, the .log properly logs a failure.) I SHOULD be getting back something in output.ERROR or AT LEAST output.JOB_STATUS.ERROR_COUNT..... BUT output.ERROR is NULL and ERROR_COUNT is 0! What gives?
P.S.> I logged an SR about this, since it looks like a pretty big issue, but maybe you guys can see something that I'm not seeing faster than the support rep.
Edited by: bdzevel on Feb 21, 2013 1:18 PM