Title: RE: c_USER#
No, it'll be the same whether it's locally or dictionary
managed tablespace.
Igor Neyman, OCP DBA[EMAIL PROTECTED]
- Original Message -
From:
BigP
To: Multiple recipients of list ORACLE-L
Sent: Wednesday, August 14, 2002 3:53
PM
Subject: Re
Title: RE: c_USER#
So do you guys think , locally managed tablespace
can get rid of this contention , at present it's dictionary managed tablespace
.
-bp
- Original Message -
From:
Jacques Kilchoer
To: '[EMAIL PROTECTED]'
Cc: '[EMAIL PROTECTED]'
Sent: Tuesday
Title: RE: c_USER#
-Original Message-
From: BigP [mailto:[EMAIL PROTECTED]]
I am finding SYS.C_USER# as one of the hot blocks .
I dont find any documentation about it , can somebody shed
some light on it . why it is contention ?
SYS.C_USER# is the name of the cluster
Title: RE: c_USER#
Good
point!
If the
cluster contains also thecurrentdisk usage as part of table TSQ$
then this meansthat Oracle has to keep updating the cluster everytime a
user adds or releases disk space, right?
Waleed
-Original Message-From: Jacques Kilchoer
[mailto
Title: RE: c_USER#
Good catch! I guess that might be another reason for heavy use of c_user#. If user X has a quota on tablespace Y, then anytime user X allocates/deallocates extents in tablespace Y, sys.tsq$ will be updated to reflect user X's usage in tablespace Y.
-Original Message
