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@xxxxxxxxx> 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@xxxxxxxxx> 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
