10gR2 Datapump EXPORT error

Oracle 10gR2 and Solaris10.

Iam trying to take a datapump back up of a schema 'DSS', and i get this error message..here are the details..I have about 25GB space left on that file system.

====================================
SQL> SELECT * FROM dba_directories;

OWNER DIRECTORY_NAME DIRECTORY_PATH
----------------------------------------------------------
SYS DPUMP_DIR1 /tmp/dump_dir
SYS WORK_DIR /ade/aime_ship_10gR2_050630/oracle/work
SYS DATA_PUMP_DIR /u10/app/ORACLE/product/10.2.0.1/rdbms/log/
SYS ADMIN_DIR /ade/aime_ship_10gR2_050630/oracle/md/admin


$expdp system/password@dss DIRECTORY=DATA_PUMP_DIR dumpfile=dssdp.dmp schema=dss

Export: Release 10.2.0.1.0 - 64bit Production on Thursday, 19 April, 2007 11:02:34

Copyright (c) 2003, 2005, Oracle. All rights reserved.
;;;
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
Starting "SYSTEM"."SYS_EXPORT_SCHEMA_02": system/********@dss DIRECTORY=DATA_PUMP_DIR dumpfile=dssdp.dmp schemas=dss
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 9.202 GB
Processing object type SCHEMA_EXPORT/USER
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
....
....
ORA-31694: master table "SYSTEM"."SYS_EXPORT_SCHEMA_02" failed to load/unload
ORA-31644: unable to position to block number 1 in dump file "/u10/app/ORACLE/product/10.2.0.1/rdbms/log/dssdp.dmp"
ORA-19502: write error on file "/u10/app/ORACLE/product/10.2.0.1/rdbms/log/dssdp.dmp", blockno 892675 (blocksize=4096)
ORA-27063: number of bytes read/written is incorrect
SVR4 Error: 28: No space left on device
Additional information: -1
Additional information: 262144
ORA-19502: write error on file "/u10/app/ORACLE/product/10.2.0.1/rdbms/log/dssdp.dmp", blockno 892483 (blocksize=4096)
ORA-27063: number of bytes read/written is incorrect
SVR4 Error: 28: No space left on device
Additional information: -1
Additional information: 262144

==============================

I am trying to export DSS schema using System account, and the DIRECTORY _NAME is DATA_PUMP_DIR


any help is appreciated..

Thanks
Ron

From the error you are getting, there is no space on the device. Free up space and then repeat the process. Please let us know how you get on.

Thanks

Naa

Have you checked permissions on this file?

No space left on the device to write the file dssdp.dmp. Check again for space when it fails.

Please check the space available again.

here is my df -h commnad

[oraosc:/u10/app/ORACLE/admin/dss]df -h
Filesystem size used avail capacity Mounted on
/ 12G 11G 282M 98% /
/dev 12G 11G 282M 98% /dev
/lib 12G 11G 282M 98% /lib
/opt/emc 12G 11G 282M 98% /opt/emc
/platform 12G 11G 282M 98% /platform
/sbin 12G 11G 282M 98% /sbin
/syshome 3.9G 357M 3.6G 9% /syshome
/u10/app/ORACLE/oradata
25G 1.7G 23G 7% /u10/app/ORACLE/oradata
/u100/app/ORACLE/oradata
9.8G 2.2G 7.5G 23% /u100/app/ORACLE/oradata
/u110/app/ORACLE/oradata
9.8G 1.6G 8.1G 17% /u110/app/ORACLE/oradata
/u120/app/ORACLE/oradata
9.8G 2.6G 7.1G 28% /u120/app/ORACLE/oradata
/u20/app/ORACLE/oradata
9.8G 3.8G 6.0G 39% /u20/app/ORACLE/oradata
/u30/app/ORACLE/oradata
9.8G 2.5G 7.2G 26% /u30/app/ORACLE/oradata
/u40/app/ORACLE/oradata
9.8G 3.0G 6.7G 32% /u40/app/ORACLE/oradata
/u50/app/ORACLE/oradata
9.8G 3.6G 6.1G 38% /u50/app/ORACLE/oradata
/u60/app/ORACLE/oradata
9.8G 3.3G 6.4G 34% /u60/app/ORACLE/oradata
/u70/app/ORACLE/oradata
9.8G 2.5G 7.2G 26% /u70/app/ORACLE/oradata
/u80/app/ORACLE/oradata
9.8G 2.4G 7.3G 25% /u80/app/ORACLE/oradata
/u90/app/ORACLE/oradata
9.8G 3.0G 6.7G 31% /u90/app/ORACLE/oradata

===================================

Obviously, i have allocated 25 GB for '/u10/app/ORACLE/oradata' file system and the dump file is writing at 'u10/app/ORACLE/product/10.2.0.1/rdbms/log/' directory..

So i dont think, space is an issue. As far as Permissions, it has already written like 3 GB of data before it throws this error..so, Permissions are not an issue.

any ideas ?

thanks
Ron

What about dropping the data_dump_dir and recreating it?

I mean recreate using create directory as '....'

Data_DUMP_DIR is created by default during DBCA installation of the DB..not sure, how can delete it thru SQL statements..

It seems to be that the server has problem in async I/O on the file system.
Did you enable large file system on this mount point?

You can check this using mount command.

thanks TamilSelvan..

How do we find that out ?..can you describe more in detail ?

thanks
Ron

Run
$mount

To get the mount options

here is the command i just ran..,does that mean that "large file system" is not activated ?

=============================================
[:/usr/inform/scripts]mount
/ on / read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=1540064 on Sun Apr 15 13:55:48 2007
/dev on /dev read/write/setuid/devices/zonedevfs/dev=5640001 on Sun Apr 15 13:56:28 2007
/lib on /lib read only/setuid/nodevices/nosub/dev=1540064 on Sun Apr 15 13:56:28 2007
/opt/emc on /opt/emc read/write/setuid/nodevices/dev=1540064 on Sun Apr 15 13:56:28 2007
/platform on /platform read only/setuid/nodevices/nosub/dev=1540064 on Sun Apr 15 13:56:28 2007
/sbin on /sbin read only/setuid/nodevices/nosub/dev=1540064 on Sun Apr 15 13:56:28 2007
/syshome on /syshome read/write/setuid/devices/dev=1540082 on Sun Apr 15 13:56:28 2007
/u10/app/ORACLE/oradata on /u10/app/ORACLE/oradata read/write/setuid/devices/dev=15420c8 on Sun Apr 15 13:56:28 2007
/u100/app/ORACLE/oradata on /u100/app/ORACLE/oradata read/write/setuid/devices/dev=15420d1 on Sun Apr 15 13:56:28 2007
/u110/app/ORACLE/oradata on /u110/app/ORACLE/oradata read/write/setuid/devices/dev=15420d2 on Sun Apr 15 13:56:28 2007
/u120/app/ORACLE/oradata on /u120/app/ORACLE/oradata read/write/setuid/devices/dev=15420d3 on Sun Apr 15 13:56:28 2007
/u20/app/ORACLE/oradata on /u20/app/ORACLE/oradata read/write/setuid/devices/dev=15420c9 on Sun Apr 15 13:56:28 2007
/u30/app/ORACLE/oradata on /u30/app/ORACLE/oradata read/write/setuid/devices/dev=15420ca on Sun Apr 15 13:56:28 2007
/u40/app/ORACLE/oradata on /u40/app/ORACLE/oradata read/write/setuid/devices/dev=15420cb on Sun Apr 15 13:56:28 2007
/u50/app/ORACLE/oradata on /u50/app/ORACLE/oradata read/write/setuid/devices/dev=15420cc on Sun Apr 15 13:56:28 2007
/u60/app/ORACLE/oradata on /u60/app/ORACLE/oradata read/write/setuid/devices/dev=15420cd on Sun Apr 15 13:56:28 2007
/u70/app/ORACLE/oradata on /u70/app/ORACLE/oradata read/write/setuid/devices/dev=15420ce on Sun Apr 15 13:56:29 2007
/u80/app/ORACLE/oradata on /u80/app/ORACLE/oradata read/write/setuid/devices/dev=15420cf on Sun Apr 15 13:56:29 2007
/u90/app/ORACLE/oradata on /u90/app/ORACLE/oradata read/write/setuid/devices/dev=15420d0 on Sun Apr 15 13:56:29 2007
/usr on /usr read only/setuid/nodevices/nosub/dev=1540064 on Sun Apr 15 13:56:29 2007
/usr/emc on /usr/emc read/write/setuid/nodevices/dev=1540064 on Sun Apr 15 13:56:29 2007
/usr/inform on /usr/inform read/write/setuid/devices/dev=154212c on Sun Apr 15 13:56:29 2007
/usr/inform/cache on /usr/inform/cache read/write/setuid/devices/dev=15420d5 on Sun Apr 15 13:56:29 2007
/usr/inform/data on /usr/inform/data read/write/setuid/devices/dev=154215e on Sun Apr 15 13:56:29 2007
/usr/inform/payments on /usr/inform/payments read/write/setuid/devices/dev=154212d on Sun Apr 15 13:56:29 2007
/usr/oraosc on /usr/oraosc read/write/setuid/devices/dev=15420d4 on Sun Apr 15 13:56:29 2007
/usr/oraosc/oradmp on /usr/oraosc/oradmp read/write/setuid/devices/dev=1542168 on Sun Apr 15 13:56:29 2007
/proc on proc read/write/setuid/nodevices/zone=oscora01z/dev=5400001 on Sun Apr 15 13:56:42 2007
/system/contract on ctfs read/write/setuid/nodevices/zone=oscora01z/dev=53c0002 on Sun Apr 15 13:56:42 2007
/etc/svc/volatile on swap read/write/setuid/nodevices/xattr/zone=oscora01z/dev=5480004 on Sun Apr 15 13:56:42 2007
/etc/mnttab on mnttab read/write/setuid/nodevices/zone=oscora01z/dev=5440002 on Sun Apr 15 13:56:42 2007
/platform/sun4u-us3/lib/libc_psr.so.1 on /platform/sun4u-us3/lib/libc_psr/libc_psr_hwcap2.so.1 read/write/setuid/devices/zone=oscora01z/dev=1540064 on Sun Apr 15 13:56:44 2007
/platform/sun4u-us3/lib/sparcv9/libc_psr.so.1 on /platform/sun4u-us3/lib/sparcv9/libc_psr/libc_psr_hwcap2.so.1 read/write/setuid/devices/zone=oscora01z/dev=1540064 on Sun Apr 15 13:56:44 2007
/dev/fd on fd read/write/setuid/nodevices/zone=oscora01z/dev=5680002 on Sun Apr 15 13:56:45 2007
/tmp on swap read/write/setuid/nodevices/xattr/zone=oscora01z/dev=5480005 on Sun Apr 15 13:56:45 2007
/var/run on swap read/write/setuid/nodevices/xattr/zone=oscora01z/dev=5480006 on Sun Apr 15 13:56:45 2007
===========================================

Code:

---

/ on / read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=1540064 on Sun Apr 15 13:55:48 2007

---

Only the root file system is mounted with largefiles option.
So the expdp is hitting max file size of 4GB.
You can ask the system admin to mount all file system with largefiles options.

Or
in expdp use filesize parameter say 2 GB.

I did not mean recreating the directory object data_pump_dir. I meant associating the object to a path. This might not be the issue but I thought it was worth trying.

Try the previous suggestion made by Tamil and see if this helps.

Thanks

Naa

Quote:

---

Originally Posted by vr76413

Data_DUMP_DIR is created by default during DBCA installation of the DB..not sure, how can delete it thru SQL statements..

---

Why don't you expressly create your own and point it to where you want it to be?