dbf'
SIZE 200M REUSE AUTOEXTEND ON MAXSIZE UNLIMITED;
As of Oracle 10g, the SYSTEM tablespace is locally managed by default; in other words,
all space usage is managed by a bitmap segment in the first part of the first datafile for the
tablespace. In a database where the SYSTEM tablespace is locally managed, the other tablespaces
in the database must also be locally managed or they must be read-only. Using locally managed
tablespaces takes some of the contention off the SYSTEM tablespace because space allocation and
deallocation operations for a tablespace do not need to use data dictionary tables. More details
on locally managed tablespaces can be found in Chapter 6.
SYSAUX Tablespace Like the SYSTEM tablespace, the SYSAUX tablespace should not have any
user segments. The contents of the SYSAUX tablespace, broken down by application, can be
reviewed using EM Database Control. You can edit the SYSAUX tablespace by clicking the
Tablespaces link under the Server tab and clicking the SYSAUX link. Figure 3-1 shows a graphical
representation of the space usage within SYSAUX.
64 Oracle Database 11g DBA Handbook
If the space usage for a particular application that resides in the SYSAUX tablespace becomes
too high or creates an I/O bottleneck through high contention with other applications that use the
SYSAUX tablespace, you can move one or more of these applications to a different tablespace.
Below the pie chart in Figure 3-1, we can click the Change Tablespace link of a SYSAUX occupant
and move it to another tablespace, as shown in Figure 3-2.
Pages:
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161