Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Bolo.

Table of Contents

Search

  1. Introducing Mass Ingestion
  2. Getting Started with Mass Ingestion
  3. Connectors and Connections
  4. Mass Ingestion Applications
  5. Mass Ingestion Databases
  6. Mass Ingestion Files
  7. Mass Ingestion Streaming
  8. Monitoring Mass Ingestion Jobs
  9. Asset Management
  10. Troubleshooting

Mass Ingestion

Mass Ingestion

Configuring BFILE access to Oracle redo logs in the Oracle file system

Configuring BFILE access to Oracle redo logs in the Oracle file system

If you store redo logs in the local Oracle server file system and want to access the logs by using Oracle directory objects with BFILEs, perform the following configuration tasks:
Perform the following usual Oracle source preparation tasks, which are not specific to BFILE access:
  • Define the ORACLE_HOME environment variable on the Linux or Windows system where the Secure Agent runs for
    Mass Ingestion Databases
    to use the Oracle Call Interface (OCI) to communicate with the Oracle source database.
  • Make sure the
    Mass Ingestion Databases
    user has the Oracle privileges that are required for the database ingestion incremental load processing. For more information, see Oracle privileges.
  • Enable ARCHIVELOG mode for the Oracle database.
  • Define an archive log destination.
  • Enable Oracle minimal global supplemental logging on the source database.
  • If your Oracle source tables have primary keys, ensure that supplemental logging is enabled for all primary key columns. For source tables that do not have primary keys, ensure that supplemental logging is enabled for all columns from which change data will be captured.
    When you create a database ingestion task, you have the option of generating a script that implements supplemental logging for all columns or only primary key columns for the selected source tables.
  • Ensure that the Oracle MAX_STRING_SIZE initialization parameter is
    not
    set to EXTENDED. If it is set to EXTENDED, Mass Ingestion Databases will not be able to replicate inserts and updates for tables containing columns defined with large (extended size) VARCHAR2, NVARCHAR2, or RAW columns.
Additionally, for BFILE access, perform the following steps:
  1. Query the Oracle database for the online and archived redo log locations in the Oracle server file system. You can use the following example queries:
    To get location of the online redo logs:
    select * from v$logfile;
    To get the archive log destination:
    select dest_id, dest_name, destination, status from V$ARCHIVE_DEST;
  2. Create the ONLINELOG_DIR and ARCHIVELOG_DIR directory objects that point to the locations of log files from step 1. An Oracle directory object specifies a logical alias name for a physical directory on the Oracle server file system under which the log files to be accessed are located. For example:
    CREATE DIRECTORY ONLINELOG_DIR AS '/u01/oracle/data'; CREATE DIRECTORY ARCHIVELOG_DIR AS '/u01/oracle/archivedata';
    The Oracle database does not verify that the directories you specify exist. Make sure you specify valid directories that exist in the Oracle file system.
  3. To verify that the directory objects were created with the correct file system paths for the redo logs, issue a select statement such as:
    select * from all_directories; OWNER DIRECTORY_NAME DIRECTORY_PATH -------- ------------------- ---------------------------------- SYS ARCHIVELOG_DIR /u01/oracle/data/JO112DTL SYS ONLINELOG_DIR /u01/oracle/data/JO112DTL
  4. Grant read and write access on the ONLINELOG_DIR and ARCHIVELOG_DIR directory objects to the Mass Ingestion Databases user who is specified in the Oracle Database Ingestion connection properties. For example:
    grant read, write on directory "ARCHIVELOG_DIR" to "
    cmid_user
    "; grant read, write on directory "ONLINELOG_DIR" to "
    cmid_user
    ";
  5. In the Oracle Database Ingestion connection properties, select the
    BFILE Access
    check box.

0 COMMENTS

We’d like to hear from you!