|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
Get inside! Sample the range of functionality easily built with JMSL Library for Time Series Data Analysis, Heat Maps, Portfolio Optimization, Monte Carlo Simulation, Stock Price Charting and more. Download Now! |
|
#1
|
|||
|
|||
|
My question is about the size of the Undo table space needed.
I have a merge statemnet that will update/ insert a/into a table with 160 millions rows 65 Gig. The run will have an input of 130 millions and from these 25 millions will be new (inserts) rows and the rest of 100 millions will be updates. Suppose I'll be the only user what should be the size of the Undo table space to let this run without any space problem ? |
|
#2
|
|||
|
|||
|
Hard to estimate. If possible, I would commit frequently.
__________________
El éxito consiste en una serie de pequeñas victorias día a día MySQL, MS SQL, MS ACCESS, Oracle Database Manager - http://victorpendleton.net/products/psdviewer.html |
|
#3
|
|||
|
|||
|
Just a comment. Read Tom Kyte's book
'expert one-on-one Oracle' Then come back and say 'commit frequently' When updating or inserting we commit about every 10000 inserts/updates. Really frequent commits can have serious performance considerations. YMMV. |
|
#4
|
|||
|
|||
|
Another comment. 160 million rows is muder on a redo log and can wreck havoc on applications sharing that drive space. Your every 10000 for 160 million is pretty frequent.
|
|
#5
|
|||
|
|||
|
For his app - ours seldom get to 10K
![]() |
![]() |
| Viewing: Dev Shed Forums > Databases > Oracle Development > Oracle Undo table Space |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|