Non error in DBMS_DATAPUMP log...can I get rid of it?

Question

I am running an import from a dump file and I'm getting a non error in my log. I'm wondering if there is something I can add to my DBMS_DATAPUMP proc to prevent it. First off, here is the log:
Master table "TEST"."CAMPUS_EXP_09102009_1013" successfully loaded/unloaded
Starting "TEST"."CAMPUS_EXP_09102009_1013":
Processing object type SCHEMA_EXPORT/TABLE/TABLE
ORA-39152: Table "TEST"."COMMENT_CODES" exists. Data will be appended to existing table but all dependent metadata will be skipped due to table_exists_action of append
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
+. . imported "TEST"."COMMENT_CODES" 6.625 KB 2 out of 8 rows+
Processing object type SCHEMA_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
*** Job percent done = 100
Job "TEST"."CAMPUS_EXP_09102009_1013" completed with 1 error(s) at 10:13:33
Job has completed
Final job state = COMPLETED
I understand the error, the table already exists. But I am not trying to import the table, all I want to do is append data given my subquery to the table. Here is my code:
     /* OPEN THE DATA PUMP PROCEDURE */
     v_dp_job_handle := DBMS_DATAPUMP.OPEN (
          OPERATION     => 'IMPORT',
          JOB_MODE     => 'TABLE',
          REMOTE_LINK => v_source_server_name,
          JOB_NAME     => v_project||'_EXP_'||v_date,
          VERSION          => 'LATEST') ;
  DBMS_OUTPUT.PUT_LINE(v_dp_job_handle) ;
     /* IF THIS IS AN EXPORT, ADD THE EXPORT .DMP FILE TO THE DATA PUMP PROCEDURE */
          DBMS_DATAPUMP.ADD_FILE (
               HANDLE          => v_dp_job_handle,
               FILENAME     => 'TEST_EXP_09092009_0144.DMP',
               DIRECTORY     => 'DATAPUMP',
               FILETYPE     => DBMS_DATAPUMP.KU$_FILE_TYPE_DUMP_FILE) ;
     /* ADD THE EXPORT LOG FILE TO THE DATA PUMP PROCEDURE */
     DBMS_DATAPUMP.ADD_FILE (
          HANDLE          => v_dp_job_handle,
          FILENAME     => v_project||'_IMP_'||v_date||'.LOG',
          DIRECTORY     => 'DATAPUMP',
          FILETYPE     => DBMS_DATAPUMP.KU$_FILE_TYPE_LOG_FILE) ;
     DBMS_DATAPUMP.METADATA_FILTER (
          HANDLE          => v_dp_job_handle,
          NAME          => 'INCLUDE_NAME_EXPR',
          VALUE          => 'IN (''COMMENT_CODES'')') ;
     DBMS_DATAPUMP.SET_PARAMETER (
          HANDLE          => v_dp_job_handle,
          NAME          => 'TABLE_EXISTS_ACTION',
          VALUE          => 'APPEND') ;
    DBMS_DATAPUMP.DATA_FILTER (
      HANDLE          => v_dp_job_handle,
      NAME          => 'SUBQUERY',
      VALUE          => 'WHERE code_group NOT IN (SELECT code_group FROM test.comment_codes)') ;
     /* START THE EXPORT */
     DBMS_DATAPUMP.START_JOB(v_dp_job_handle) ;I'd rather not release this proc into production if it has an error in the log that I tell people to just ignore...that's not very professional.
Thanks for anyone's help on this,
ivalum21
Edited by: ivalum21 on Sep 10, 2009 10:22 AM

Answer 1

I ran your code and got an error saying that CONTENT is an invalid parameter or something.
But you did put me on the right path, I did find another SET_PARAMETER option called INCLUDE_METADATA. When set to zero, it does not try to import the metadata. For anyone visiting this post, here is the code I found, I added it to my code block I posted above and it worked great:
  DBMS_DATAPUMP.SET_PARAMETER (
    HANDLE          => v_dp_job_handle,
    NAME          => 'INCLUDE_METADATA',
    VALUE          => 0) ;