Thanks Raj,
I knew about dbms_system.ksdwrt to write to trace files or the alert log
or both but not these two. I have see from google that kcfrms allows the
resetting of IO counters in v$session_event and v$filestat. And KSDFLS
is part of the suite of functions to write to the alert log or
Thanks very much Gopal, I have just replied to Raj's post on the same
subject.
kind regards
Pete
In article [EMAIL PROTECTED], K Gopalakrishnan
[EMAIL PROTECTED] writes
Pete:
Sorry for the delay. I was traveling back to Bangalore from San Francisco
when you sent the message. There is a
Pete:
Sorry for the delay. I was traveling back to Bangalore from San Francisco
when you sent the message. There is a procedure in the DBMS_SYSTEM package
called KCFRMS which resets certain timing information from the X$KCFIO
(which is exposed as V$FILESTAT).
And also there is an event which can
Hi Gopal,
I have followed this thread with interest and i was waiting for you to
elaborate on the following statement, specifically what undocumented
procedures ?
kind regards
Pete
code and you can not create/update/delete them. However there are some
undocumented procudures , thru which you
Title: RE: x$ constructs and memory
dbms_system.KCFRMS|KSDFLS (not sure about this one).
Raj
Rajendra dot Jamadagni at nospamespn dot com
All Views expressed in this email are strictly personal.
QOTD: Any clod
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Tanel Poder
Sent: Monday, September 29, 2003 1:45 PM
To: Multiple recipients of list ORACLE-L
Subject: Re: x$ constructs and memory
What I have not checked so far is how an ALTER SYSTEM
increasing
Hi Steve and welcome back,
Thanks for that detailed answer BUT... A practical question from the
original post remains: What happens when these x$constructs begin to
consume large amounts of memory? From your explanation I'm assuming
that, beyond monitoring the SGA and PGA, memory consumption of
:
Subject:RE: x$ constructs and memory
Hi Steve and welcome back,
Thanks for that detailed answer BUT... A practical question from the
original post remains: What happens when these x$constructs begin to
consume large amounts of memory? From your explanation I'm assuming
that, beyond monitoring
happen to
be transient.
Jared
Orr, Steve
[EMAIL PROTECTED]
Sent by:
[EMAIL PROTECTED]
09/30/2003 07:49 AM
Please respond to
ORACLE-L
To:
Multiple recipients of
list ORACLE-L
[EMAIL PROTECTED]
cc:
Subject:
RE: x$ constructs
Hi Steve,
The X$ interfaces do not use memory persistently, and the memory usage of
the X$ tables is fixed and necessary to an instance. Thus memory growth is
not possible.
Memory growth is possible for the segmented arrays, which some of the X$
interfaces expose. However, it is very unusual,
]
09/30/2003 07:49 AM
Please respond to
ORACLE-L
To:
Multiple recipients of
list ORACLE-L
[EMAIL PROTECTED]
cc:
Subject:
RE: x$ constructs and
memory
Hi Steve and welcome back,
Thanks for that detailed answer
I was sitting on a mountain here in Colorado, pondering Oracle
optimization and an interesting scenario crossed my feeble mind.
As I began to ponder this (I asked the resident marmot, but he
must be a SQL*Server expert...), I came up with several
questions.
Where in memory (sga or other) do the
PROTECTED]
Sent: Monday, September 29, 2003 4:10 PM
To: Multiple recipients of list ORACLE-L
Subject: x$ constructs and memory
I was sitting on a mountain here in Colorado, pondering Oracle
optimization and an interesting scenario crossed my feeble mind.
As I began to ponder this (I asked
As I understand it, the X$ information is largely a window onto the control
structures in shared memory rather than a summary, aggregation or
abstraction. I may be wrong here but that's the way I've always understood
it to work. So the structures 'occupy' the same space as the data they're
recipients of list ORACLE-L Subject: x$ constructs and
memory I was sitting on a mountain here in Colorado,
pondering Oracle optimization and an interesting scenario crossed
my feeble mind. As I began to ponder this (I asked the resident
marmot, but he must be a SQL*Server expert...), I came up wi
I was sitting on a mountain here in Colorado, pondering Oracle...
You are one twisted individual! :-) Here's some SQL for ya:
ALTER brain RECOVER STANDBY consciousness CONTINUE UNTIL CANCEL;
-Original Message-
Sent: Monday, September 29, 2003 9:10 AM
To: Multiple recipients of list
I was sitting on a mountain here in Colorado,
pondering Oracle
optimization and an interesting scenario crossed my
feeble mind.
As I began to ponder this (I asked the resident
marmot, but he
must be a SQL*Server expert...), I came up with
several
questions.
Where in memory (sga or other) do the
Hi!
X$ fixed tables are just interfaces to Oracle database and instance memory
structures. In my understanding, there are no separate memory structures
built only for serving x$ tables, x$ tables just help humans to read
existing instance memory and physical structures more easily. Selecting from
source2708
--
Mladen Gogala
Oracle DBA
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Daniel Fink
Sent: Monday, September 29, 2003 11:10 AM
To: Multiple recipients of list ORACLE-L
Subject: x$ constructs and memory
I
Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Orr, Steve
Sent: Monday, September 29, 2003 12:45 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: x$ constructs and memory
What happens when these x$constructs begin to consume large
amounts of memory
A lot of memory structures x$ tables reflect are located in SGA fixed
area,
for example x$ktuxe which a transaction entry table is located there and
controlled by init parameter transactions
Sorry, I was talking about x$ktcxb here, this is the transaction object
table in SGA fixed area.
What I have not checked so far is how an ALTER SYSTEM increasing a
parameter affects the SGA. In practice it's a realloc() (functionally
speaking). It would seem reasonable to me to have a shared memory segment to
hold all parameters which can by dynamically changed. I wouldn't touch it if
get back to bears?
--
Mladen Gogala
Oracle DBA
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Tanel Poder
Sent: Monday, September 29, 2003 1:45 PM
To: Multiple recipients of list ORACLE-L
Subject: Re: x$ constructs and memory
What I
To: Multiple recipients of list ORACLE-L
Subject: Re: x$ constructs and memory
What I have not checked so far is how an ALTER SYSTEM
increasing a
parameter affects the SGA. In practice it's a realloc()
(functionally speaking). It would seem reasonable to me to
have a shared memory segment
]
Subject: RE: x$ constructs and memory
With all due respect, I don't believe that it is a fixed area.
You can create X$ tables by running certain catalog scripts. I believe
that the description of X$ tables is located logically close to the
description of the data dictionary, which would mean
:[EMAIL PROTECTED] On
Behalf Of K Gopalakrishnan
Sent: Monday, September 29, 2003 3:30 PM
To: Multiple recipients of list ORACLE-L
Subject: Re: x$ constructs and memory
Mladen:
I hope you are not kidding.. X$ table (!) definitions are
defined in the source code and you can not
create
Hi Daniel and list,
There are two types of X$ row sources. X$ tables export in-memory data
structures that are inherently tabular, and X$ interfaces that call
functions to return data is non-tabular, or not memory resident.
For example, the array of structs in the SGA representing processes is
Hi Steve,
Thank you for your explanation, but I got few additional questions ig you
got a chance to answer:
(There are similar X$ interfaces for other memory heaps). As you may know,
heaps are implemented as a heap descriptor and linked list of extents, and
within each extent there is a
Hi Tanel,
Answers inline ...
As you may know,
heaps are implemented as a heap descriptor and linked list of extents,
and within each extent there is a linked list of chunks.
Is there a linked list for *all* chunks in a heap as well, regardless of
their type, or is there only a list for each
29 matches
Mail list logo
