Skip to Main Content
  • Questions
  • Data Pump API to refresh top 10 partitions


Question and Answer

Chris Saxon

Thanks for the question, NISHANT.

Asked: March 25, 2020 - 6:22 pm UTC

Answered by: Chris Saxon - Last updated: March 27, 2020 - 8:40 am UTC

Category: PL/SQL - Version: 12.1

Viewed 100+ times

You Asked

I have a requirement where I have to refresh tables from PROD to DEV. But refresh needs to be done in such a manner that partitioned table should be refreshed with its latest top 10 partitions and non partitioned table should be refreshed full

I am using DBPUMP API to do this over network link. I was able to pull 2 partitions successfully for a single table but when I specify multiple data_filter lines second table never gets refreshed. And also where will I incorporate non partioned tables?

Request you to please have a look at the pattern of code I am using. For detecting partitions I have planned that I will write a code to fetch partition names and then append them in a code but if you have a better suggestion then please shoot that to me.

set scan off
set serveroutput on
set escape off
h1 number;
errorvarchar varchar2(100):= 'ERROR';
tryGetStatus number := 0;
l_ku$status ku$_status1020;
l_job_state varchar2(4000);

percent_done NUMBER; -- Percentage of job complete
job_state VARCHAR2(30); -- To keep track of job state
le ku$_LogEntry; -- For WIP and error messages
js ku$_JobStatus; -- The job status from get_status
jd ku$_JobDesc; -- The job description from get_status
sts ku$_Status; -- The status object returned by get_status
h1 := (operation => 'IMPORT', job_mode => 'TABLE', version => 'COMPATIBLE', remote_link =>'DBPUMP_TEST_LINK' );

tryGetStatus := 1;
dbms_datapump.set_parallel(handle => h1, degree => 1);

dbms_datapump.add_file(handle => h1, filename => 'POC-'||to_char(sysdate,'yyyy-mm-dd-hh24_mi_ss')||'.LOG', directory => 'DATAPUMP', filetype => 3);

dbms_datapump.set_parameter(handle => h1, name => 'KEEP_MASTER', value => 1);

--dbms_datapump.metadata_filter(handle => h1, name => 'SCHEMA_LIST', value =>'''FDW_PUMP_TEST''');

dbms_datapump.data_filter(handle => h1, name => 'PARTITION_LIST', value =>'SYS_P26447,SYS_P27786', TABLE_NAME => 'TAB1');

dbms_datapump.data_filter(handle => h1, name => 'PARTITION_LIST', value =>'SYS_P34155,SYS_P34666', TABLE_NAME => 'TAB2');

dbms_datapump.set_parameter(handle => h1, name => 'INCLUDE_METADATA', value => 0);

dbms_datapump.set_parameter(handle => h1, name => 'ESTIMATE', value => 'BLOCKS');


dbms_datapump.start_job(handle => h1, skip_current => 0, abort_step => 0);

errorvarchar := 'NO_ERROR';

percent_done := 0;
job_state := 'UNDEFINED';
while (job_state != 'COMPLETED') and (job_state != 'STOPPED') loop
dbms_datapump.ku$_status_job_error +
dbms_datapump.ku$_status_job_status +
js := sts.job_status;

-- If the percentage done changed, display the new value.

if js.percent_done != percent_done
dbms_output.put_line('*** Job percent done = ' ||
percent_done := js.percent_done;
end if;
end loop;
IF ((errorvarchar = 'ERROR')AND(tryGetStatus=1)) THEN
   END IF;




and we said...

Are you getting any errors? If so what exactly?

I see you have system-generated names for the partitions (SYS_Pnnnn). Are the partition names the same in both environments? If not this could be the cause of the problem...

You don't need to do anything special to get the non-partitioned tables.

and you rated our response

  (1 rating)


Here is the answer with another question

March 27, 2020 - 6:19 am UTC

Reviewer: Nishant Kariya from India

Thanks Team for responding quickly. To answer your question:

-> No I don't get any error, code runs fine.
-> TAB1 has same partition names on both environments and it fetches data successfully.
-> Wheras, TAB2 has same partition names in both env but it doesn't pulls any data.

Let me brief what I did as a pre-requisite of my POC. I created a blank schema on lower environment i.e. on DEV and first imported all metadata from PROD . So all structure was copied exactly same. Requirement is to refresh database each month but only keep limited data on DEV. so this means every time refresh is initiated, tables in DEV, should be truncated and latest 10 partitioned along with dimensions should be refreshed from PROD without touching any code.
No I understand when I go live with this, and operate on true data schema's, system partition names will never be same in both environments. But here I am doing a POC and thus have same partition names on both env(because I imported blank structure first)

Also one question on my way of designing this code -
One PLSQL block for incorporating all partitioned and non partioned tables, OR it should be a cursor loop in which this PLSQL block should be executed for each table.

I have used DBPUMP lot but via command line EXPDP and IMPDP. And by that experience I can say that I should write a code once to incorporate everything.

Note that I have given TAB1 and TAB2 in DATA_FILTER without specifying NAME_LIST or NAME_EXPR separately. So when we say we can incorporate other non partitioned tables also in this code (lets say TAB3 ) then where it should be mentioned?

Should it be like multiple DATA_FILTERS lines for partitioned tables and NAME_LIST for non-partitioned table?

Chris Saxon


March 27, 2020 - 8:40 am UTC

Have you got a log file for the export? What does that show?

If you want to specify a list of tables, use NAME_EXPR, e.g.:

dbms_datapump.metadata_filter(handle => h1, name => 'NAME_EXPR', value => 'IN(''T1'',''T2'',...)'); 

One PLSQL block for incorporating all partitioned and non partioned tables, OR it should be a cursor loop in which this PLSQL block should be executed for each table.

I'm not sure what you're getting at here?