SYSTEM
As mentioned previously in this chapter, no user segments should ever be stored in the SYSTEM
tablespace. The new clause default tablespace in the create database command helps to prevent
this occurrence by automatically assigning a permanent tablespace for all users that have not
explicitly been assigned a permanent tablespace. An Oracle installation performed using the
Oracle Universal Installer will automatically assign the USERS tablespace as the default
permanent tablespace.
The SYSTEM tablespace will grow more quickly the more you use procedural objects such as
functions, procedures, triggers, and so forth, because these objects must reside in the data dictionary.
This also applies to abstract datatypes and Oracle??™s other object-oriented features.
SYSAUX
As with the SYSTEM tablespace, user segments should never be stored in the SYSAUX tablespace.
If one particular occupant of the SYSAUX tablespace takes up too much of the available space or
significantly affects the performance of other applications that use the SYSAUX tablespace, you
should consider moving the occupant to another tablespace.
TEMP
Instead of one very large temporary tablespace, consider using several smaller temporary
tablespaces and creating a temporary tablespace group to hold them. As you found out earlier
in this chapter, this can improve the response time for applications that create many sessions
with the same username.
Tablespace Type Segment Space Management Approx.
Pages:
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172