User defined tables in System tablespaces [message #636727] |
Thu, 30 April 2015 19:49 |
|
krish96
Messages: 74 Registered: October 2012
|
Member |
|
|
Hello Experts,
I am trying to find in 11g database there are some user defined tables in system tablespaces, please help me how to find these objects with the SQL query.. Need to recreate these tables into a new tablespaces..
Thanks in advance..
|
|
|
|
|
|
|
|
|
|
|
|
Re: User defined tables in System tablespaces [message #636897 is a reply to message #636860] |
Tue, 05 May 2015 04:16 |
Roachcoach
Messages: 1576 Registered: May 2010 Location: UK
|
Senior Member |
|
|
BlackSwan wrote on Mon, 04 May 2015 13:46krish96 wrote on Thu, 30 April 2015 17:49Hello Experts,
I am trying to find in 11g database there are some user defined tables in system tablespaces, please help me how to find these objects with the SQL query.. Need to recreate these tables into a new tablespaces..
Thanks in advance..
"problem" only exists between your ears.
post SQL & results that show I am wrong
Oracle docs specifically advise against this.
http://docs.oracle.com/cd/E11882_01/network.112/e36292/users.htm#DBSEG10200
Quote:he default setting for the default tablespaces of all users is the SYSTEM tablespace. If a user does not create objects, and has no privileges to do so, then this default setting is fine. However, if a user is likely to create any type of object, then you should specifically assign the user a default tablespace, such as the USERS tablespace. Using a tablespace other than SYSTEM reduces contention between data dictionary objects and user objects for the same data files. In general, do not store user data in the SYSTEM tablespace.
You can use the CREATE TABLESPACE SQL statement to create a permanent default tablespace other than SYSTEM at the time of database creation, to be used as the database default for permanent objects. By separating the user data from the system data, you reduce the likelihood of problems with the SYSTEM tablespace, which can in some circumstances cause the entire database to become nonfunctional.
Sure, it is a "guideline", but why would one roll the dice needlessly?
|
|
|
|