I am not sure if v$session_longops works in all cases (in 184.108.40.206). Many times I have long process running and nothing appears in v$session_longops... AFIAK database process which takes more than 6 seconds they are considered long by Oracle and they are candidate to be seen in v$session_longops but it does not seem true in all cases... Anyone know why?
TO insert 4 million rows it took me 4 hours with all the indexes dropped and keys enabled. I am creating indexes. Is the time remaining out put from the above query V$SESSION_LONGOPS to create index is correct ? . Time to create one index shows more than 4 hours. How do I know how much time the index creation takes?
Thanks for all your help
You should have minimized your amount of redo/undo generated with that insert-as-select by using direct path insert.
INSERT /*+ APPEND */ INTO .... AS SELECT * FROM ....
That should have greatly reduced the time to populate your table. Similary, for index creation you should use NOLOGGING option. That is of course if there is no explicit and very strong reason why you shouldn't use nologging operations, like if this database is part of dataguard configuration or something simmilar....
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?