Skip Headers

Oracle9i Supplied PL/SQL Packages and Types Reference
Release 2 (9.2)

Part Number A96612-01
Go To Documentation Library
Home
Go To Product List
Book List
Go To Table Of Contents
Contents
Go To Index
Index

Master Index

Feedback

Go to previous page Go to beginning of chapter Go to next page

DBMS_LOGMNR_D , 2 of 2


Summary of DBMS_LOGMNR_D Subprograms

Table 28-1 describes the procedures in the DBMS_LOGMNR_D supplied package.

Table 28-1  DBMS_LOGMNR_D Package Subprograms
Subprogram Description

BUILD Procedure

Extracts the database dictionary to either a flat file or a file in the redo logs.

SET_TABLESPACE Procedure

Re-creates all LogMiner tables in an alternate tablespace.

BUILD Procedure

The syntax for the DBMS_LOGMNR_D.BUILD procedure is as follows:

Syntax

DBMS_LOGMNR_D.BUILD (
dictionary_filename IN VARCHAR2,
dictionary_location IN VARCHAR2,
options IN NUMBER);

Parameters

Table 28-2 describes the parameters for the BUILD procedure.

Table 28-2  BUILD Procedure Parameters
Parameter Description

dictionary_filename

Name of the dictionary file

dictionary_location

Path to file directory

options

Specifies that the dictionary is written to either a flat file (STORE_IN_FLAT_FILE) or the redo logs (STORE_IN_REDO_LOGS) destination

To extract the dictionary to a flat file, you must supply a filename and location.

To extract the dictionary to the redo logs, specify only the STORE_IN_REDO_LOGS option. The size of the dictionary may cause it to be contained in multiple redo logs.

In summary, the combinations of parameters used result in the following behavior:

Exceptions

Usage Notes

Example 1: Extracting the Dictionary to a Flat File

The following example extracts the dictionary file to a flat file named dictionary.ora in a specified path (/oracle/database).

SQL> EXECUTE dbms_logmnr_d.build('dictionary.ora', - 
  2 '/oracle/database/', -
  3 options => dbms_logmnr_d.store_in_flat_file);

Example 2: Extracting the Dictionary to the Redo Logs

The following example extracts the dictionary to the redo logs.

SQL> EXECUTE dbms_logmnr_d.build ( -
  2 options => dbms_logmnr_d.store_in_redo_logs);

SET_TABLESPACE Procedure

By default all LogMiner tables are created to use the SYSTEM tablespace. However, it may be desirable to alter LogMiner tables to employ an alternate tablespace. Use this routine to re-create all LogMiner tables in an alternate tablespace.

Parameters

Table 28-3 describes the parameters for the SET_TABLESPACE procedure.

Table 28-3  SET_TABLESPACE Parameters
Parameter Description

new_tablespace

A string naming a preexistent tablespace. To re-create all LogMiner tables to employ this tablespace, supply only this parameter.

dictionary_tablespace

A string naming a preexistent tablespace. This parameter places LogMiner Dictionary data in a tablespace different from that where LogMiner spill data is to be written. This parameter overrides the new_tablespace parameter with respect to LogMiner Dictionary tables.

spill_tablespace

A string naming a preexistent tablespace. This parameter places LogMiner spill data in a tablespace different from that where LogMiner Dictionary data is to be written. This parameter overrides the new_tablespace parameter with respect to LogMiner spill tables.

Usage Notes

Example: Using the DBMS_LOGMNR_D.SET_TABLESPACE Procedure

The following example shows creation of an alternate tablespace and execution of the DBMS_LOGMNR_D.SET_TABLESPACE procedure.

SQL> CREATE TABLESPACE  logmnrts$ datafile '/usr/oracle/dbs/logmnrts'
  2 SIZE 25 M REUSE AUTOEXTEND ON MAXSIZE UNLIMITED;

SQL> EXECUTE dbms_logmnr_d.set_tablespace('logmnrts$');

Go to previous page Go to beginning of chapter Go to next page
Oracle
Copyright © 2000, 2002 Oracle Corporation.

All Rights Reserved.
Go To Documentation Library
Home
Go To Product List
Book List
Go To Table Of Contents
Contents
Go To Index
Index

Master Index

Feedback