In Quest SQL Optimizer for Sybase, I noticed the last "Last Execution Date" in the SQL Inspector is showing 12/30/1899.
I have verified my system clock and cross-checked that with today's newspaper to make sure it is indeed not the second last day of the 19th century (see attached screenshot).
The Last Execution Date should directly retrieve from database, and it seems related to the problem of loading it. Our QA also found the same problem from our environment,
WORKAROUND:
None
STATUS:
Waiting for fix in a future release of Quest SQL Optimizer for Sybase.
