On 10/03/16 07:03, John Dorlon wrote:
I can change it, but it seems that the value in the database is wrong.
That column is supposed to show estimated time remaining in seconds.
The max value that Toad allows in this field is 2147483648, which would
come to about 70 years!
There’s nothing to change John, there are
(always/sometimes/occasionally) problems with V$SESSION_LONGOPS. See here:
The formula for working out TIME_REMAINING is:
(ELAPSED_SECONDS * (TOTALWORK - SOFAR))/SOFAR.
So, if Oracle estimates TOTALWORK incorrectly, which it can do, then
when the session has done more work than the estimate, SOFAR is bigger
than TOTALWORK, so the subtraction goes negative as does the result.
It would be interesting to check those figures when the OP next sees a
negative value. And just to show that “granny can indeed suck eggs”:
ELAPSED_SECONDS is 100,
TOTALWORK is 1,000 and
SOFAR is 1,250
TIME_REMAINING = (100 * (1,000 - 1,250) / 1,250)
= -20 seconds…
There is a lot of interesting information about V$SESSION_LONGOPS in the