Primary Database Log Access

Replication Agent may fail if it cannot read the primary database log.

An instance of Replication Agent for Oracle or Replication Agent for Microsoft SQL Server may fail to function properly on Windows if User Account Control (UAC) is enabled and the instance is not started with the Run as administrator option. This problem occurs when Replication Agent does not have permission to read the primary database log on Microsoft Windows Vista, Microsoft Windows Server 2008, Microsoft Windows Server 2008 R2, and Microsoft Windows 7. The Replication Agent system log file may contain messages indicating a problem accessing the primary database log:

Related concepts
Replication Agent Instance Availability Monitoring
Replication Agent Logs
Available Memory
Skipped DDL Commands
JVM Thread Dump
Related tasks
Verifying that a Primary Database Object Is Marked for Replication
Checking the Current Replication Agent Status
Using ra_statistics to Check Replication Agent Operations and Performance
Debugging LTL