Oracle database save (either binary or ASCII) failed due to the file size limit

Document ID : KB000023545
Last Modified Date : 14/02/2018
Show Technical Document Details


The Oracle database save fails, due to the file size limit (either binary or ASCII) 

Database save failing with error
database save normally requires the file size to be set unlimited
Error in ASCII database_save.xxxxxx.log: 
"EXP-00015: error on row xxxxx of table NH_STATSX_xxxxxxxxxx, column REBOOTS, datatype 2
EXP-00002: error in writing to export file
EXP-00002: error in writing to export file
error closing export file /<path>/*.tdb/oracle_export/EXPDAT.DMP "
Error in binary  database_save.xxxxxx.log:   
" RMAN-00571: ===========================================================
   RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =====
   RMAN-00571: ===========================================================
   RMAN-03009: failure of backup command on dsk1 channel at 08/05/2005 02:27:41 
   ORA-19502: write error on file  "/oracle/NIBLOG_P/backup/full_NIBLOG_P_22502_8", blockno 401281 (blocksize=8192) 
   ORA-27063: skgfospo: number of bytes read/written is incorrect



       eHealth on Solaris



Solaris is not set to support large file systems



Check to see if what is the file size limit set to, normally the database save requires it set to unlimited because the file size in the .tdb directory, such as expdat.dmp file can easily be over 2 Gigabytes

See Solution TS17330 for details on setting large file support.