Initial Allocated
Size (MB)
SYSTEM Permanent Manual 680
SYSAUX Permanent Auto 585
TEMP Temporary Manual 20
UNDOTBS1 Permanent Manual 115
USERS Permanent Auto 16
EXAMPLE Permanent Auto 100
TABLE 3-2 Standard Oracle Installation Tablespaces
Chapter 3: Planning and Managing Tablespaces 73
UNDOTBS1
Even though a database may have more than one undo tablespace, only one undo tablespace can
be active at any given time. If more space is needed for an undo tablespace, and AUTOEXTEND is
not enabled, another datafile can be added. One undo tablespace must be available for each node
in a Real Application Clusters (RAC) environment because each instance manages its own undo.
USERS
The USERS tablespace is intended for miscellaneous segments created by each database user, and
it??™s not appropriate for any production applications. A separate tablespace should be created for
each application and segment type; later in this chapter we??™ll present some additional criteria you
can use to decide when to segregate segments into their own tablespace.
EXAMPLE
In a production environment, the EXAMPLE tablespace should be dropped; it takes up 100MB of
disk space and has examples of all types of Oracle segments and data structures. A separate database
should be created for training purposes with these sample schemas; for an existing training database,
the sample schemas can be installed into the tablespace of your choice by using the scripts in
$ORACLE_HOME/demo/schema.
Pages:
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173