Re: Datapump export error
From: Frits Hoogland <frits.hoogland_at_gmail.com>
Date: Sat, 9 Mar 2013 16:49:26 +0100
Message-Id: <CE45049F-4D04-478D-9301-03F30B70DF4E_at_gmail.com>
Content-Transfer-Encoding: quoted-printable Content-Type: text/plain;
> PARALLEL=3D8
> FILESIZE=3D10GB
> EXCLUDE=3DTRIGGER
> COMPRESSION=3DMETADATA_ONLY
> METRICS=3DY
> FULL=3DY
> FLASHBACK_TIME=3D"TO_TIMESTAMP('09-03-2013 06:00:00', 'DD-MM-YYYY =
HH24:MI:SS')"
>=20
> Space is tight so the plan was to compress the files after they =
reached their
> 10GB limit. We did that and at a later time, expdp tried to access one =
of them
> again.
>=20
> At what point in time can we guarantee that the export process will =
not try to
> access the file again?
> Below is the error we received.
> Thanks
> Keith
> ORA-31693: Table data object "PWRLINE"."SETTLESHADOWNIDR" failed to
> load/unload and is being skipped due to error:
> ORA-31617: unable to open dump file
> "/DB_EXPORT/expdp_LDSTPRD_2013-03-09_06:00:00_06.dmp" for write
> ORA-19505: failed to identify file
> "/DB_EXPORT/expdp_LDSTPRD_2013-03-09_06:00:00_06.dmp"
> ORA-17503: ksfdopn:4 Failed to open file
> /DB_EXPORT/expdp_LDSTPRD_2013-03-09_06:00:00_06.dmp
> ORA-17500: ODM err:File does not exist
> ORA-00604: error occurred at recursive SQL level 3
> ORA-08180: no snapshot
> --
> http://www.freelists.org/webpage/oracle-l
>=20
>=20
Date: Sat, 9 Mar 2013 16:49:26 +0100
Message-Id: <CE45049F-4D04-478D-9301-03F30B70DF4E_at_gmail.com>
Content-Transfer-Encoding: quoted-printable Content-Type: text/plain;
charset=iso-8859-1
I've encountered a similar situation on a RAC database when trying to do =
IO from a location unique to 1 node. Try CLUSTER=3DN if you are on RAC, =
or use a directory object which is shared with all nodes.
Frits Hoogland
http://fritshoogland.wordpress.com
frits.hoogland_at_gmail.com
+31 6 53569942
On Mar 9, 2013, at 3:46 PM, "Keith Moore" <kmoore_at_zephyrus.com> wrote:
> Hopefully someone has run into a similar issue and can help me out.
>=20
> We are doing a large datapump export to save as a historical archive. =
The
> database is 10.2.0.4. Since this version of expdp will not compress =
and not
> allow compressing to a named pipe, we used the following parameters:
>=20
> PARALLEL=3D8
> FILESIZE=3D10GB
> EXCLUDE=3DTRIGGER
> COMPRESSION=3DMETADATA_ONLY
> METRICS=3DY
> FULL=3DY
> FLASHBACK_TIME=3D"TO_TIMESTAMP('09-03-2013 06:00:00', 'DD-MM-YYYY =
HH24:MI:SS')"
>=20
> Space is tight so the plan was to compress the files after they =
reached their
> 10GB limit. We did that and at a later time, expdp tried to access one =
of them
> again.
>=20
> At what point in time can we guarantee that the export process will =
not try to
> access the file again?
>=20
> Below is the error we received.
>=20
> Thanks
> Keith
>=20
> ORA-31693: Table data object "PWRLINE"."SETTLESHADOWNIDR" failed to
> load/unload and is being skipped due to error:
>=20
> ORA-31617: unable to open dump file
> "/DB_EXPORT/expdp_LDSTPRD_2013-03-09_06:00:00_06.dmp" for write
>=20
> ORA-19505: failed to identify file
> "/DB_EXPORT/expdp_LDSTPRD_2013-03-09_06:00:00_06.dmp"
>=20
> ORA-17503: ksfdopn:4 Failed to open file
> /DB_EXPORT/expdp_LDSTPRD_2013-03-09_06:00:00_06.dmp
>=20
> ORA-17500: ODM err:File does not exist
>=20
> ORA-00604: error occurred at recursive SQL level 3
>=20
> ORA-08180: no snapshot
>=20 >=20 >=20
> --
> http://www.freelists.org/webpage/oracle-l
>=20
>=20
-- http://www.freelists.org/webpage/oracle-lReceived on Sat Mar 09 2013 - 16:49:26 CET