Re: KOTTD$ and KOTTB$
- From: Rajesh.Rao@xxxxxxxxxxxx
- To: "Jared Still" <jkstill@xxxxxxxxx>
- Date: Thu, 6 Nov 2008 09:19:30 -0500
Thanks Jared, Mark for your replies. We are investigating an increase in
CPU usage with no apparent change in execution plans. The analyst on the
SR (and Tim Hopkins from this list) came back saying that these objects
will experience high logical reads while making heavy use of user defined
datatypes, which we do. As per the analyst, this is nothing to be
concerned about, especially under heavy load. So, this line of
investigation is off the table for now. Will dig into it later, but will
be interested in any observations from this team.
Thanks
Raj
"Jared Still" <jkstill@xxxxxxxxx>
11/05/2008 05:40 PM
To
Rajesh.Rao@xxxxxxxxxxxx
cc
oracle-l@xxxxxxxxxxxxx
Subject
Re: KOTTD$ and KOTTB$
On Wed, Nov 5, 2008 at 6:33 AM, <Rajesh.Rao@xxxxxxxxxxxx> wrote:
On one of our databases (3 node RAC 10.2.0.3 on Solaris 10), I see that
indexes on the above 2 objects belonging to sys consume about 15% of the
logical reads that happen, and are the top 2 segments experiencing the
most logical reads. Can someone shed light on what these objects are?
As per ML Note 175982.1 I would suspect it has something to do with
objects used in the data dictionary. You may have noticed there is a
corresponding type for each table.
You'll probably need to open an SR to pursue this further:
select * from kottd$
*
ERROR at line 1:
ORA-30732: table contains no user-visible columns
ORA-30732: table contains no user-visible columns
Cause: An attempt was made to query on a system table which has no
user-visible columns.
Action: Do not query on a system table that has no user-visible columns.
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
-----------------------------------------
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.
Other related posts:
