hi, i want to run this insert..select query. now since the result set is huge, i am running into spool space problems. is there any way by which i can avoid this. some way by which the result set may be partitioned into smaller sets???
I'd venture to guess you will not need to "partition" your results once you tune the SQL. Suggest you run an EXPLAIN on the INSERT..SELECT and determine where the bottle-neck is in you SQL. This should be your first step in performance tuning.