Originally posted by desmondliu some one said option 2 performs better than option 1, but i have some doubts on it. this is the first question,
and another one, let's assume the problem is with the temp ts, if there are soring logic involved somewhere, will the option 2 better than option 1?
Over DB link, i wud prefer to have segment created and then use COPY cmd to copy data...rather than go for Select Insert or Create Select.
In that respect, i meant 2 betters.
But in ur scnerio..ur Tablespace ( target ) is unable to extend as its reached the size specifed during creation.
WRT this, u may have to add datafile, or use AUTOEXTEND with MAXSIZE limited.
If sorting logic is there, then there lies problem with ur TEMP tablespace defined for the USER, if its throwing error as to it cant extend space. It may have to be given some more sapce to do sorting.
"I Dont Want To Follow A Path, I would Rather Go Where There Is No Path And Leave A Trail."
"Ego is the worst thing many have, try to overcome it & you will be the best, if not good, person on this earth"
thanks. but, i am a little bit confused. if we have a view defined in remote database, In the local database, we going to use the "create as select" statement to create a table which in fact copy all data in the remote view over. will the local temporary tablespace used or the remote temporary tablespace used for those sorting alike operations defined with the remote view itself when the "create as select" running.