We have a version 12 database that is exhibiting some very weird behavior. If I run the sa_conn_info procedure, it shows all the connections with a LastRequestTime of September 1st 2012. The times are changing on the last request but even the times are way off. what would cause the internal date to be off by so much? We have a nearly identical setup and it reads correctly? Do you think a DB shutdown and refire is in order? It is has been running for about 2 years without a restart and we are noticing some slow times to do basic queries.
Any help is appreciated.
First, congratulations for keeping your server running for two years. (Let me guess that this is not running on Windows :-)
The time used within the SQL Anywhere server to generate the last request time is not directly obtained from the system time - calls to the system to get the time of day are expensive - so a the server uses CPU tics to keep track of the time. Doing the time calculation this way can cause the reported times to drift from the "real" time (even the system clock drifts over time). The server tries to make adjustments to accommodate the time drift but its not perfect.
An issue related to time drift was recently fixed in SA 12 build 3829
Since you are using a two year old server I am pretty sure you don't have this fix. :-)
Regarding your slow queries: You have not given us sufficient information to determine what would be causing the slow down - it could be any number of issues including memory fragmentation, disk fragmentation, file fragmentation, etc. A restart may resolve the issues or it may not?