-
Originally posted by TimHall
It works! I now have a 9i instance with a Locally Managed System Tablespace.
Hm, this is new to me. Are you sure about your results? I know you can specify EXTENT MANAGEMENT LOCAL, but only in the "default temporary tablespace" part of the CREATE DATABASE command. And of course, LMT then applies only to the default TEMP tablespace, not to SYSTEM tablespace itself.
Also, on "9i New Features for Administrators" ILT we were explicitely told that system TS can not be LMT. And the "9i Database Administration" manual explicitely states:
"The SYSTEM tablespace is always dictionary managed."
http://download-west.oracle.com/otnd...aces.htm#19132
So once again: are you sure you sucessfully created SYSTEM TS as LMT? Have you verified that it really *is* a LMT and not perhaps that some of the utilities/tools simply erroneously report it as being LMT, while in fact it is normal dictionary managed TS?
Jurij Modic
ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
-
Well aren't I the arse! I replied rather prematurely.
I created the new instance using the Database Configuration Assistant (Win2000 & 9.0.1.1.0) which allowed the LOCAL option to be selected for the SYSTEM tablespace. I started the creation and no errors were produced when the system tablespace was created. So I replied and left for home.
I've now logged in from home and the rest of the instance creation has finished. Turns out the DBCA ended up making it as dictionary managed SYSTEM tablespace anyway!
I've saved the creation script and it doesn't put the EXTENT MANAGEMENT LOCAL for the SYSTEM tablespace, regardless of your selection. I've repeated the process and added the EXTENT MANAGEMENT LOCAL in myself.
The result is it definitely fails!
Should have stuck with my first answer
Sorry guys & girls!
-
Since SYSTEM Tablespace is where the Dictionary is, wouldn't SYSTEM tablespace BE Locally managed in the sense that the dictionary is local to it. I realize this is not the same concept of local management, but in essence wouldn't it be about the same?
I thought that the point of the Locally managed tablespace is so that the Tablespace does not have to refer back to the dictionary in the System tablespace to manage itself.
So...I guess what I want to know is, what is the benefit of making SYSTEM tablespace local?
-
Originally posted by TimHall
Should have stuck with my first answer
Gotta hate that. You think you are wrong, but you are wrong about being wrong.
Jeff Hunter
-
It's possible that, if it were possible, it might be more efficient using the bitmap rather than rows in a table???
As you say, the contention aspect isn't really an issue here.
-
-
-
Tim found a undocumented feature . . .
Why would Oracle say not to have SYSTEM as a LMT?
hmm let us think . . . maybe just maybe Oracle like to have one tablespace under their complete control?
I don't know thinking out loud . . .
or maybe other Oracle tools are expecting the SYSTEM tablespace to be untouched by mere mortals like us?
hmmm . . .
or make up your own reason . . . I going try this LMT on SYSTEM to see what happens.
E. Yen
OCP 8, 8i, 9i
-
Thank you very much guys. i guess ill have to make my system tablespace as Dictionary Managed for now. ill be recreating our production database next week (bec of block corruption in the system tablespace) =(
Anyway, how can i prevent block corruption?
Another question (actually i have already posted it on another thread) - Will you use LMT for your RBS? and why?
Thanks =)
The Maverick
Oracle Certified DBA - 8i
-
There were some pretty cool animations in this thread, especially the one from Jeff.
Would really like to learn how to create and post these.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|