You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When gfix is running in big/corrupted databases, it would be good to "see" something happening to be sure that it is actually "doing" something, and not got stuck at some phase, or just entered an infinite loop (due to corruption).
As the possibility of adding progress bars, etc seems to be improbably, some basic information would help, ie:
Object name being analyzed
Incremental number of pages accessed for that object
Starting Time for that object (end time when job finishes)
Maybe some alert if a specific page was read more than 100 times (possible infinite loop detected)
Anyway, anything more than a black "silent" screen would be welcome. Maybe the same info can be shown when sweep is being done.
The text was updated successfully, but these errors were encountered:
This requires relatively serious changes in engine and (sooner of all) public API. The reason for it is that gfix utility itself does almost nothing - it converts switches to appropriate DPB parameters, and teh rest of the job is done by engine, at server side. May be technique, similiar to one used by monitoring tabkes can be used here... This should be carefully thought before doing something, therefore I do not assigned planned version to this issue.
Submitted by: @WarmBooter
When gfix is running in big/corrupted databases, it would be good to "see" something happening to be sure that it is actually "doing" something, and not got stuck at some phase, or just entered an infinite loop (due to corruption).
As the possibility of adding progress bars, etc seems to be improbably, some basic information would help, ie:
Object name being analyzed
Incremental number of pages accessed for that object
Starting Time for that object (end time when job finishes)
Maybe some alert if a specific page was read more than 100 times (possible infinite loop detected)
Anyway, anything more than a black "silent" screen would be welcome. Maybe the same info can be shown when sweep is being done.
The text was updated successfully, but these errors were encountered: