Q
Evaluate Weigh the pros and cons of technologies, products and projects you are considering.

Objects in system tablespace not owned by system

I ran a report and found the objects (indexes and tables) in system tablespace not owned by system. How critical is that?
Most DBAs would tell you that this is a very critical situation that you will want to fix as soon as possible. But it is not so critical that your system has probably crashed. Yet. The problem with non-SYS or SYSTEM objects in the SYSTEM tablespace is that you can potentially interfere with the data dictionary. If non-SYS and SYSTEM objects use up all of the space, then there will be no room for the data dictionary to grow. If this is the case, then certain critical operations can't complete and your instance can crash. So it is important to move these objects as soon as possible.

Dig Deeper on Oracle database design and architecture

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide.com

SearchDataCenter

SearchContentManagement

SearchHRSoftware

Close