| V$SESSION_LONGOPS - Looking for more than last 16 ops [message #457754] |
Tue, 25 May 2010 18:55  |
rleishman
Messages: 3728
Registered: October 2005
Location: Melbourne, Australia
|
Senior Member |
|
|
Doing some data conversion at the moment and using V$SESSION_LONGOPS to help predict when the current task will be finished so I can run the next one.
V$SESSION_LONGOPS seems to have only the last 16 long operations for the session. Older operations are automatically purged. My bigger tables have 32 partitions, so after the first 16 are processed, I cannot tell which partition I am up to.
Googling "old longops" and "longops history" didn't help, nor did the same searches on this site. The Oracle Reference manual section on V$SESSION_LONGOPS did not mention that older entries are purged.
Any suggestions on seeing older operations?
Ross Leishman
|
|
|
|
|
|
| Re: V$SESSION_LONGOPS - Looking for more than last 16 ops [message #457876 is a reply to message #457832] |
Wed, 26 May 2010 04:43  |
rleishman
Messages: 3728
Registered: October 2005
Location: Melbourne, Australia
|
Senior Member |
|
|
Actually, I'm not certain it is per session, but per SQL_ADDRESS / SQL_HASH_VALUE. I don't have direct access to X$KSULOP, so I cannot tell what it is doing.
Another interesting characteristic is that it will purge history SOMETIMES at each step of the plan. e.g. If it full scans 32 partitions and then joins to another partitioned table, then a few partitions into the new table it will clear the LONGOPS history of the first table - even though the total operations retained is less than 16.
Ross Leishman
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
