RE: Grid Control (Rel 2) Question
- From: "Taylor, Chris David" <Chris.Taylor@xxxxxxxxxxxxxxx>
- To: <chupit@xxxxxxxxx>, "oracle-l" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 8 Nov 2007 07:27:37 -0600
Here's the suggested fix from Oracle:
Bug 6162079 duplicate of 5880921
Bug 5880921 fixed in 10.2.0.3 Patch 10:
5880921 - TIME INCONSISTENCY BETWEEN V$SYSMETRIC_HISTORY AND SYSDATE
FROM DUAL
So, looks like I'll be applying Patch 10 shortly *sigh*
Chris Taylor
Sr. Oracle DBA
Ingram Barge Company
Nashville, TN 37205
Office: 615-517-3355
Cell: 615-354-4799
Email: chris.taylor@xxxxxxxxxxxxxxx
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Edgar Chupit
Sent: Thursday, November 08, 2007 4:09 AM
To: oracle-l
Subject: Re: Grid Control (Rel 2) Question
Dear Chris,
I have had (still have) similar issues. Basically in our case it's due
to the Bug: 6162079 V$SYSMETRIC_HISTORY HAS FUTURE TIMESTAMP (Or very
similar to this bug)
Oracle Support is still working on fixing this issue.
In our case the situation is as follows on some of the instances
timestamp in V$%METRIC views shows completely incorrect time (+1 year
and some days).
Oracle EM Agent is using data from this view and tries to upload it to
EM Repository, because timestamp is in future partition for that
timestamp is not created and it reports error ORA-14400
If you want I can provide you with more details.
I have fixed issue with ORA-14400 by adding additional partition
manually, but issue with V$%METRIC views is still unresolved.
On Nov 7, 2007 5:18 PM, Taylor, Chris David
<Chris.Taylor@xxxxxxxxxxxxxxx> wrote:
>
>
>
>
> Be aware, that the date that is off is not an hour....Its 2 years+
> (2009-01-27)
>
--
Best regards,
Edgar Chupit
callto://edgar.chupit
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
