SQL> execute sysman.emd_maintenance.move_em_tblspc('EM_REP');
PL/SQL procedure successfully completed.
SQL> select occupant_name, occupant_desc, space_usage_kbytes
2> from v$sysaux_occupants
184 Oracle Database 11g DBA Handbook
3> where occupant_name = 'EM';
OCCUPANT_NAME OCCUPANT_DESC SPACE_USAGE_KBYTES
-------------- ---------------------------------------- -------------------
EM Enterprise Manager Repository 0
1 row selected.
Since the current space allocation for the EM tools is about 150MB, a tablespace starting at a
size of 250MB with additional extents of 100MB each should be sufficient for most environments.
Note that the row for Enterprise Manager is still in V$SYSAUX_OCCUPANTS; even though it is
not taking up any space in the SYSAUX tablespace, we may want to move its metadata back into
SYSAUX at some point in the future. Therefore, we may need to query V$SYSAUX_OCCUPANTS
again to retrieve the move procedure. We use the same procedure for moving the application into
and out of SYSAUX:
SQL> execute sysman.emd_maintenance.move_em_tblspc('SYSAUX');
PL/SQL procedure successfully completed.
If a component is not being used in the database at all, such as Ultra Search, a negligible
amount of space is used in the SYSAUX tablespace.
Archived Redo Log File Management
It is important to consider space management for objects that exist outside of the database, such as
archived redo log files. In ARCHIVELOG mode, an online redo log file is copied to the destination(s)
specified by LOG_ARCHIVE_DEST_n (where n is a number from 1 to 10) or by DB_RECOVERY_
FILE_DEST (the flash recovery area) if none of the LOG_ARCHIVE_DEST_n values are set.
Pages:
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336