Re: CTIME zero in v$lock

From: Yong Huang <yong321_at_yahoo.com>
Date: 9 Sep 2003 10:11:48 -0700
Message-ID: <b3cb12d6.0309090911.32d38d37@posting.google.com>

Mark.Powell_at_eds.com (Mark D Powell) wrote in message news:<2687bb95.0309090508.132e2a00_at_posting.google.com>...

> and always present. I am not sure but I think the CTIME column value
> may be dependent on timed_statistics being set on.

As usual, I tested something obvious before I posted my message. I tested turning on and off timed_statistics, timed_os_statistics, setting fixed_date... Nothing had any effect on ctime for MR and RT locks. It's almost impossible that the instance has been up for too long so ctime ran out of space. Unless the OS timer is messed up, I suspect there's something wrong with his redo logfiles or controlfiles. There may be something unusual in alert.log. Calling Oracle Support is a good idea.

v$lock view can be traced to x$ksqeq. But I don't know where x$ksqeq gets its KSQLKCTIM values.

Yong Huang Received on Tue Sep 09 2003 - 12:11:48 CDT