exporting pre-schema procedural objects and actions . exporting foreign function library names for user XZBLOB . exporting PUBLIC type synonyms . exporting private type synonyms . exporting object type definitions for user XZBLOB About to export XZBLOB's objects ... . exporting database links . exporting sequence numbers . exporting cluster definitions . about to export XZBLOB's tables via Conventional Path ... . . exporting table ACF_APP_BOARDFILE_UPLOADED msgcnt 4 vxfs: mesg 001: vx_nospace - /dev/vg00/lvol5 file system full (1 block extent) EXP-00056: ORACLE error 24801 encountered ORA-24801: illegal parameter value in OCI lob function . . exporting table ACF_APP_FILE_UPLOADED EXP-00056: ORACLE error 24801 encountered ORA-24801: illegal parameter value in OCI lob function . . exporting table ACF_APP_QBATTACH EXP-00056: ORACLE error 24801 encountered ORA-24801: illegal parameter value in OCI lob function . . exporting table ACF_APP_WORKFILE_UPLOADED 0 rows exported . . exporting table ACF_APP_XFATTACH EXP-00056: ORACLE error 24801 encountered ORA-24801: illegal parameter value in OCI lob function . . exporting table ACF_SYS_DE_ENTITY EXP-00056: ORACLE error 24801 encountered ORA-24801: illegal parameter value in OCI lob function . . exporting table ACF_SYS_GWATTACH EXP-00056: ORACLE error 24801 encountered ORA-24801: illegal parameter value in OCI lob function . . exporting table ACF_SYS_OPINION_ATTACH EXP-00056: ORACLE error 24801 encountered ORA-24801: illegal parameter value in OCI lob function . . exporting table ACF_SYS_TEMP_FILE EXP-00056: ORACLE error 24801 encountered ORA-24801: illegal parameter value in OCI lob function . . exporting table ARCHIVE_ATTACHMENT 4 rows exported EXP-00002: error in writing to export file EXP-00056: ORACLE error 1403 encountered ORA-01403: no data found . . exporting table XZ_BG_XX_XXATTACH EXP-00056: ORACLE error 24801 encountered ORA-24801: illegal parameter value in OCI lob function . . exporting table XZ_FGZD_DOC EXP-00056: ORACLE error 24801 encountered ORA-24801: illegal parameter value in OCI lob function . exporting synonyms . exporting views . exporting stored procedures . exporting operators . exporting referential integrity constraints . exporting triggers . exporting indextypes . exporting bitmap, functional and extensible indexes . exporting posttables actions . exporting materialized views . exporting snapshot logs . exporting job queues . exporting refresh groups and children . exporting dimensions . exporting post-schema procedural objects and actions . exporting statisticserror closing export file lanwei.dmp Export terminated successfully with warnings.
Requires Free Membership to View
If you are using Oracle 8i and higher, and your OS has been configured to support large files, then the exp utility should have no problem creating a dump file larger than 2 GB. If your OS has not been configured to support large files, then you will not be able to create any file larger than 2 GB, no matter what you do. Verify with your SysAdmin that you can create large files on your server.
We used to employ a trick to create a dump file larger than 2 GB when the exp utility would not support these file sizes. The trick is to create a pipe on your filesystem. The exp utility writes to the pipe which immediately passes the data to another utility (gzip in the example below). To exp, the file never is more than a few KB in size. Follow these steps:
mknod exp.pipe p gzip < exp.pipe > expdat.dmp.gz & exp userid=system file=exp.pipe full=yImporting is similar to the following:
gunzip < exp.dat.dmp.gz > exp.pipe & imp userid=system file=exp.pipe full=y
This was first published in March 2006
Join the conversationComment
Share
Comments
Results
Contribute to the conversation