If the SYSAUX tablespace is taken offline or otherwise becomes corrupted, only these
components of the Oracle database will be unavailable; the core functionality of the database will
be unaffected. In any case, the SYSAUX tablespace helps to take the load off of the SYSTEM
tablespace during normal operation of the database.
To monitor the usage of the SYSAUX tablespace, you can query the column SPACE_USAGE_
KBYTES on a routine basis, and it can alert the DBA when the space usage grows beyond a certain
level. If the space usage for a particular component requires a dedicated tablespace to be allocated
for the component, such as for the EM Repository, the procedure identified in the MOVE_
PROCEDURE column of the V$SYSAUX_OCCUPANTS view will move the application to
another tablespace:
SQL> select occupant_name, move_procedure from v$sysaux_occupants
2 where occupant_name = 'EM';
OCCUPANT_NAME MOVE_PROCEDURE
--------------- -------------------------------------------------
EM emd_maintenance.move_em_tblspc
In the following scenario, we know that we will be adding several hundred nodes to our
management repository in the near future. Because we want to keep the SYSAUX tablespace from
growing too large, we decide to create a new tablespace to hold only the Enterprise Manager
data. In the following example, we??™ll create a new tablespace and move the Enterprise Manager
schema into the new tablespace:
SQL> create tablespace EM_REP
2> datafile '+DATA' size 250m autoextend on next 100m;
Tablespace created.
Pages:
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335