RE: OEM Agent Alert History Graph
- From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
- To: <charlottejanehammond@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 5 Nov 2007 14:42:13 -0700
Sounds like you could probably get by with the more focused approach of
just setting _gby_hash_aggregation_enabled=false and this will also have
the bonus of saving you from a "wrong results" bug. See Metalink
387958.1 and 345048.1 for more info.
Regards,
Brandon
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Charlotte Hammond
. . .
I then guessed that this lack of ordering was the problem, and so set
OPTIMIZER_FEATURE_ENABLE = 9.2.0 and flushed the shared pool. Doing
this caused the GROUP BY to also do an implicit ordering and return the
data in chronological order.
. . .
Privileged/Confidential Information may be contained in this message or
attachments hereto. Please advise immediately if you or your employer do not
consent to Internet email for messages of this kind. Opinions, conclusions and
other information in this message that do not relate to the official business
of this company shall be understood as neither given nor endorsed by it.
--
//www.freelists.org/webpage/oracle-l
Other related posts:
