A newer version of this documentation is available.
View Latest (v2.2)

Static Oracle LogMiner Setup (single-instance)

Prerequisites

Before setting up LogMiner with Gluesync, ensure you have:

  • An Oracle Database (version 11g or higher) deployed in single-tenant / non-CDB mode

  • SYSDBA access to the instance you’re targeting

  • Appropriate storage for archived redo logs

Initial Database Setup

Login to the database as sys as sysdba and ensure Archivelog mode is enabled.

-- Enable Archivelog mode if not already enabled
shutdown immediate
startup mount
alter database archivelog;
alter database open;

Verify archive log mode:

archive log list

Enable database-level supplemental logging so LogMiner can capture primary key and column changes.

ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY) COLUMNS;

LogMiner user setup

Create a dedicated LogMiner user in the root database. This user owns no application data but has the privileges required to mine redo logs.

CREATE USER GLUESYNC_LOGMNR IDENTIFIED BY "YOUR_SECURE_PASSWORD"
  DEFAULT TABLESPACE SYSAUX
  TEMPORARY TABLESPACE TEMP
  QUOTA UNLIMITED ON SYSAUX;

GRANT
  CREATE SESSION,
  SELECT ANY TRANSACTION,
  SELECT ANY DICTIONARY,
  EXECUTE_CATALOG_ROLE,
  LOGMINING
TO GLUESYNC_LOGMNR;

Application user setup

Create (or reuse) an application user that Gluesync will leverage for metadata discovery and snapshot operations against your schemas.

CREATE USER GLUESYNCUSER IDENTIFIED BY <password>;
GRANT CONNECT, RESOURCE TO GLUESYNCUSER;
GRANT UNLIMITED TABLESPACE TO GLUESYNCUSER;

Configure tables for CDC

Enable supplemental logging for every table you plan to capture and allow the LogMiner user to read those objects.

-- Replace with your actual tables
ALTER TABLE SCHEMA1.MYFIRSTTABLE ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS;
GRANT SELECT ON SCHEMA1.MYFIRSTTABLE TO GLUESYNC_LOGMNR;

ALTER TABLE SCHEMA1.MYSECONDTABLE ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS;
GRANT SELECT ON SCHEMA1.MYSECONDTABLE TO GLUESYNC_LOGMNR;

Connection Configuration

When configuring the Gluesync agent:

  • Host/Port: Point to the Oracle Listener.

  • Service / SID: Your single-tenant database name (for example, ORCL)

  • Username: GLUESYNCUSER

  • Password: your_password

  • LogMiner Username: GLUESYNC_LOGMNR

  • LogMiner Password: your_password

  • LogMiner Database: same as the service/SID above

Important Notes

  • Privileges: Grant only the permissions listed above; avoid using SYS or schema owners for mining redo.

  • Redo logs: Monitor archived redo log storage to make sure logs remain available until Gluesync consumes them.

  • Resource planning: Supplemental logging increases redo size. Ensure storage and network capacity are sized accordingly.

For Gluesync-specific configuration, see Gluesync Configuration Guide.