This content has been marked as final. Show 7 replies
This error comes when u do not have sufficient value for undo_retention parameter and undo tablespace size.
Pl post the complete expdp command. Does this table have any LOB columns ? If so, this may be a bug1 person found this helpful
ORA-01555 And Other Errors while Exporting Table With LOBs, How To Detect Lob Corruption. (Doc ID 452341.1)
Export Fails With ORA-02354 ORA-01555 ORA-22924 and How To Confirm LOB Segment Corruption Using Export Utility? (Doc ID 833635.1)
H:\ORACLE_EXPORT>expdp SYSTEM/password FULL=y DUMPFILE=dbname.dmp DIRECTORY=HEXPORT LOGFILE=dbname.log
Yes, there are lots of binary waveform file chunks in this table, thus "yes" in answer to LOB.
I'll see what I can find in the way of answers on corruption.
You're right. I had increased unto_retention from 900 to 9000. This time I increased it to 90000. That did it. The backup completed successfully. I don't have metalink access, so I don't know how to check for LOB corruption, but I'm assuming that everything is fine since this time around I have a 333gb file, and the .log file contains no error.
One thing that was strange was that the table that failed each time (WAVEFORM2) was slightly smaller than the one right before it which succeeded (not larger as I had been led to believe from the SQL I used to get me the size). Here's the expdp log excerpt:
. . exported "USERNAME"."WAVEFORM0" 64.64 GB 1811611 rows
. . exported "USERNAME"."WAVEFORM2" 63.99 GB 1768224 rows
. . exported "USERNAME"."WAVEFORM3" 50.94 GB 4606522 rows
. . exported "USERNAME"."WAVEFORM1" 53.72 GB 1425423 rows
. . exported "USERNAME"."WAVEFORM4" 44.16 GB 3400018 rows
Nice it works
and if this question is answered, please mark appropriate posts as correct/helpful and the thread as closed. Thanks
I marked "correct" and "helpful". My problem is resolved, but I'm still curious about answers to the questions in my two posts from May 4...