Re: Expdp Dump File Infomation

Great yes but it all depends on the dump piece missing is having master table or not .

• say if total 10 dumps were generated during expdp EXP_DP_01 to EXP_DP_10.
• Assume that master table is stored in dump number 10 (EXP_DP_10)
• And unfortunately dump 10 is only missing at the target side .
• In this case if you try SQLFILE option with keep_master it will fail with ORA- error and datapump will not find master table in any of the dumps from 1-9.

To see if a particular dump piece contains master table we have datapump_info under dbms_datapump api.

On Mon, Apr 6, 2020, 17:34 Mikhail Velikikh <mvelikikh_at_gmail.com> wrote:

>
> I experimented with it a little bit. I was running impdp using an
> incomplete set of files:
>
> impdp userid=test_user dumpfile=df1 directory=my_tmp
> table_exists_action=skip keep_master=yes job_name=test_incomplete
>
> Import: Release 12.2.0.1.0 - Production on Mon Apr 6 07:34:53 2020
>
> Copyright (c) 1982, 2017, Oracle and/or its affiliates. All rights
> reserved.
> Password:
>
> Connected to: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 -
> 64bit Production
> ORA-39002: invalid operation
> ORA-39059: dump file set is incomplete
>
> After adding the trace parameter (trace=480300) to the command, I got the
> following in the trace file:
>
> KUPM:07:41:01.217: ORA-39245: import job requires export dump file
> "df2.dmp"
>
> The important part is this is happening *after *the data pump creates the
> master table.
> Thus, I am intended to think that this kind of information can be obtained
> only when the master table is imported. I do not know a way to get that
> information from the dump file itself but you can easily get the master
> table using a simple sqlfile job:
>
> impdp userid=test_user dumpfile=df1 directory=my_Tmp
> job_name=test_incomplete keep_master=yes sqlfile=test01
>
> Once the master table is created, I obtained the list of files using the
> following query:
>
> SQL> select distinct file_name from test_incomplete where file_name is not
> null;
>
> FILE_NAME
> ------------------------------------------------------------
> /tmp/df2.dmp
> /tmp/df1.dmp
>
> I would rather run a sqlfile import in your scenario to validate that a
> dumpset is self-contained.
>
>
> On Sun, 5 Apr 2020 at 05:38, Vanita Sharma Tyagi <
> dba.vanitasharma_at_gmail.com> wrote:
>
>> There is no error this is a genric scenario , we have our end users
>> starting import process (self service from an tool we have provided them )
>> without copying the dump files completely some time and impdp obviously
>> fails with "dumpfile set is not complete" which is correct .
>> Wanted to check if we can validate somehow if a dumpset is comete of not
>> without running the actual import so that we can restrict them from running
>> the impdp if dumpset is not complete.
>>
>>
>> On Sun, Apr 5, 2020, 02:16 Al B. <albert.y.balbekov_at_gmail.com> wrote:
>>
>>> I would ask for accompanying export log file and for parameter file and
>>> command line used. Having export log and export parameters will help in
>>> potential troubleshooting.
>>>
>>> thx,
>>> Albert
>>>
>>>
>>> On Sat, Apr 4, 2020, 2:30 AM Vanita Sharma Tyagi <
>>> dba.vanitasharma_at_gmail.com> wrote:
>>>
>>>> Hi Experts ,
>>>>
>>>> Need some help in validating the dump files in a expdp dump set . I
>>>> followed oracle metalink 462488.1 but no where i can see any information
>>>> about how many files are present in my dumpset .
>>>>
>>>> If someone has given a dumpset to you and before import itself we want
>>>> to make sure that dumpset is complete . [ Without using impdp sqlfile
>>>> option ] We have access via sqlplus only to system views/packages to check
>>>> .
>>>>
>>>>
>>>> BR
>>>> Vanita
>>>>
>>>

--
http://www.freelists.org/webpage/oracle-l