Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!news.astraweb.com!news-small.astraweb.com!news-out.spamkiller.net!propagator2-maxim!feed-maxim.newsfeeds.com!cyclone.bc.net!newsfeed.stanford.edu!postnews1.google.com!not-for-mail From: yong321@yahoo.com (Yong Huang) Newsgroups: comp.databases.oracle.server Subject: Re: CTIME zero in v$lock Date: 9 Sep 2003 10:11:48 -0700 Organization: http://groups.google.com/ Lines: 18 Message-ID: References: <96f4ae2a.0309050455.7cbecef7@posting.google.com> <3F5CA397.CE86343A@remove_spam.peasland.com> <2687bb95.0309090508.132e2a00@posting.google.com> NNTP-Posting-Host: 155.188.191.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1063127509 28345 127.0.0.1 (9 Sep 2003 17:11:49 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 9 Sep 2003 17:11:49 GMT Xref: newssvr20.news.prodigy.com comp.databases.oracle.server:242704 Mark.Powell@eds.com (Mark D Powell) wrote in message news:<2687bb95.0309090508.132e2a00@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