Nothing odd about that

1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User

Welcome to IWETHEY!

Post #253,421 by broomberg 4/25/06 6:55:33 PM Reply	Nothing odd about that You are exporting a large changing table or multiple tables. You told Oracle you want everything to be consistent, which means it need to keep track of all information in all tables that you are exporting, copying changed or deleted data to your rollback segments. Your rollback segment are too small to hold the amount of data. You abort.
Post #253,427 by Meerkat 4/25/06 8:03:45 PM Reply	What he said. If you can't stop people making updates to the table while you're exporting it, here's an idea - but it's not elegant. Use the QUERY= option to cut down the amount of data you're exporting. Run EXP multiple times to create an export in several chunks. I've had to do this before on some large tables, and it works well enough. It's just not as pretty as exporting everything into one file. The other downside is you can't have DIRECT=TRUE if you use the QUERY= option. Good luck! Two out of three people wonder where the other one is.
Post #253,472 by boxley 4/26/06 10:16:46 AM Reply	thanks, time to let the dba's do what their paid for Any opinions expressed by me are mine alone, posted from my home computer, on my own time as a free american and do not reflect the opinions of any person or company that I have had professional relations with in the past 50 years. meep

Oracle: getting a wierd error when doing an export - (boxley) - (3) - April 25, 2006, 03:01:23 AM EDT

Nothing odd about that - (broomberg) - (2) - April 25, 2006, 06:55:33 PM EDT

What he said. - (Meerkat) - April 25, 2006, 08:03:45 PM EDT

thanks, time to let the dba's do what their paid for -NT - (boxley) - April 26, 2006, 10:16:46 AM EDT

Nihil curo de ista tua stulta superstitione.
30 ms