[12C questions] OCP 1z0-060 Question 3: managing the sysaux tablespace

Question 3

Which two statements are true about the use of the procedures listed in the V $ sysaux_occupants.move_procedure column?

A. The procedure maybe used for some component store locate component data to the sysaux tablespace from its current tablespace.

B. The procedure may be used for some component store locate component data from the sysaux tablespace to another tablespace.

C. All the components may be moved into sysaux tablespace.

D. All the components may be moved from the sysaux tablespace.

[Question description]

Measure the test taker's knowledge about how to manage the sysaux tablespace.

[Resolution]

When a database is created, the sysaux tablespace is installed as the auxiliary tablespace of the system. Database components that have been installed and used independent tablespace can be placed in the sysaux tablespace. If the sysaux tablespace is unavailable, the database kernel function will still run. Using the features of the sysaux tablespace will fail or the functional availability will be limited.

You can use the V $ sysaux_occupants view to monitor the content in the sysaux tablespace. The view lists the following content:

• Occupied name

• Usage description

• Solution name

• Mobile Stored Procedure

• Current space usage

During component installation, you can choose not to place it in the sysaux tablespace. If you decide to move the component from the sysaux tablespace to the specified tablespace, you can use the stored procedure of moving the component in the V $ sysaux_occupants view. The stored procedure for moving can also move components from other tablespaces to the sysaux tablespace.

[Experiment]

1. view the V $ sysaux_occupants view and find the move procedure of the audit function:

[email protected]> select OCCUPANT_NAME,SCHEMA_NAME,MOVE_PROCEDURE,SPACE_USAGE_KBYTES from v$sysaux_occupants where OCCUPANT_NAME=‘AUDIT_TABLES‘;OCCUPANT_NAME  SCHEMA_NAME  MOVE_PROCEDURE                      SPACE_USAGE_KBYTES-------------- ------------ ----------------------------------- ------------------AUDIT_TABLES   SYS          DBMS_AUDIT_MGMT.move_dbaudit_tables                  0

2. Move procedure to the OCP tablespace using the move procedure mobile audit function:

[email protected]> exec DBMS_AUDIT_MGMT.move_dbaudit_tables(‘OCP‘);PL/SQL procedure successfully completed.

3. Enable audit:

[email protected]> audit select table;Audit succeeded.

4. view the tablespace of the audit table:

[email protected]> select segment_name,segment_type from dba_segments where TABLESPACE_NAME=‘OCP‘ and segment_type=‘TABLE‘;SEGMENT_NAME    SEGMENT_TYPE--------------- -------------FGA_LOG$        TABLEAUD$            TABLE

We can see that the table with audit records is already in the OCP tablespace.

In 12C, the content in V $ sysaux_occupants shows that some components do not move procedure.

[email protected]> select OCCUPANT_NAME,SCHEMA_NAME,MOVE_PROCEDURE from v$sysaux_occupants;OCCUPANT_NAME             SCHEMA_NAME          MOVE_PROCEDURE------------------------- -------------------- -----------------------------LOGMNR                    SYSTEM               SYS.DBMS_LOGMNR_D.SET_TABLESPACELOGSTDBY                  SYSTEM               SYS.DBMS_LOGSTDBY.SET_TABLESPACESMON_SCN_TIME             SYSPL/SCOPE                  SYSSTREAMS                   SYSAUDIT_TABLES              SYS                  DBMS_AUDIT_MGMT.move_dbaudit_tablesXDB                       XDB                  XDB.DBMS_XDB.MOVEXDB_TABLESPACEAO                        SYS                  DBMS_AW.MOVE_AWMETAXSOQHIST                  SYS                  DBMS_XSOQ.OlapiMoveProcXSAMD                     OLAPSYS              DBMS_AMD.Move_OLAP_CatalogSM/AWR                    SYSSM/ADVISOR                SYSSM/OPTSTAT                SYSSM/OTHER                  SYSSTATSPACK                 PERFSTATSDO                       MDSYS                MDSYS.MOVE_SDOWM                        WMSYS                DBMS_WM.move_procORDIM                     ORDSYS               ordsys.ord_admin.move_ordim_tblspcORDIM/ORDDATA             ORDDATA              ordsys.ord_admin.move_ordim_tblspcORDIM/ORDPLUGINS          ORDPLUGINS           ordsys.ord_admin.move_ordim_tblspcORDIM/SI_INFORMTN_SCHEMA  SI_INFORMTN_SCHEMA   ordsys.ord_admin.move_ordim_tblspcEM                        SYSMAN               emd_maintenance.move_em_tblspcTEXT                      CTXSYS               DRI_MOVE_CTXSYSULTRASEARCH               WKSYS                MOVE_WKULTRASEARCH_DEMO_USER     WK_TEST              MOVE_WKEXPRESSION_FILTER         EXFSYSEM_MONITORING_USER        DBSNMPTSM                       TSMSYSSQL_MANAGEMENT_BASE       SYSAUTO_TASK                 SYSJOB_SCHEDULER             SYS31 rows selected.

[Summary]

V $ sysaux_occupants.move_procedure can move the tablespace where the component is located. It can move the component either to the sysaux tablespace or from the sysaux tablespace, but not all components can be moved, therefore, option A and option B are relatively accurate, and option C and option D range is too large.

[Answer] a, B

References

Http://docs.oracle.com/database/121/ADMIN/tspaces.htm#ADMIN11384

Http://docs.oracle.com/database/121/ADMIN/create.htm#ADMIN00203 

For more articles, visit the author's personal blog: www.dbstyle.net.

This article is from the "into the Oracle" blog, please be sure to keep this source http://dbstyle.blog.51cto.com/8619508/1537026