Get Data Moving 1
Results 1 to 3 of 3

Thread: Status goes from "Idle" to "LOGGER" with errors: ORACDC514E, ORACDC511E

  1. #1
    TSC
    TSC is offline Junior Member
    Join Date
    Apr 2018
    Posts
    2
    Rep Power
    0

    Status goes from "Idle" to "LOGGER" with errors: ORACDC514E, ORACDC511E

    Source system:
    Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
    With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options


    Destination System:
    Windows Server 2012 R2
    SQL Server 2017 x64 Developer Edition (cumulative update 5)
    Oracle Instant Client 12.2.0.1 x64 (ODAC used for installation)
    Oracle Instant Client 12.1.0.2 x32 (ODAC xcopy used for installation)
    Microsoft Connector for Oracle by Attunity 5.0
    Attunity Oracle CDC Designer (from SQL Server 2017 feature pack)
    Attunity Oracle CDC Service (from SQL Server 2017 feature pack)
    Hi,

    I have setup a CDC Service and I have setup/configured a CDC Instance to the Oracle database where all steps were passed / green (no indication of errors)


    I can access the oracle database using sqlplus and query the tables.


    User running the CDC service is part of sysadm (during testing periode) and is also granted full permissions on the Oracle client directory.


    Problem appears as soon as I start the Oracle CDC Instance, then it goes from "Idle" to LOGGER
    (I have read all the forum threads similar do my problem, but without finding a solution)


    I have asked the dba to clear the redo log, but didn't do anything.


    This is really a showstopper for us atm, so all help will be highliy appreciated.


    Here are the log:
    Attached Files Attached Files

  2. #2
    EdVogue is offline Junior Member
    Join Date
    Oct 2017
    Posts
    1
    Rep Power
    0
    It looks like you haven't set up the Oracle database in ARCHIVELOG mode with Minimal Supplemental Logging enabled.
    There is also a 'Oracle logging script' (right side under Actions in the designer) that needs to be run by a DBA login.

    The user that connects to the Oracle instance to read the log must have at least these priveleges on 12c:
    GRANT SELECT ANY TABLE TO <USER>;
    GRANT SELECT ANY TRANSACTION TO <USER>;
    GRANT SELECT ON V_$LOGMNR_CONTENTS TO <USER>;
    GRANT SELECT ON V_$ARCHIVED_LOG TO <USER>;
    GRANT SELECT ON V_$LOGMNR_LOGS TO <USER>;
    GRANT SELECT ON V_$LOG TO <USER>;
    GRANT SELECT ON V_$LOGFILE TO <USER>;
    GRANT SELECT ON V_$DATABASE TO <USER>;
    GRANT SELECT ON V_$INSTANCE TO <USER>;
    GRANT EXECUTE_CATALOG_ROLE TO <USER>;
    GRANT LOGMINING TO <USER>;

    Make sure to set a certain period (1 day maybe) as log retention period for the redo logs, otherwise the CDC will go to LOGGER when the redo log switches.

  3. #3
    TSC
    TSC is offline Junior Member
    Join Date
    Apr 2018
    Posts
    2
    Rep Power
    0
    Hi again, thanks for you reply... Please see my reply :


    ARCHIVELOG mode with Minimal Supplemental Logging enabled.
    Answer: I ran the following query: SELECT * FROM OPENQUERY (MyOracle, 'select log_mode from v$database')
    Result: LOG_MODE = ARCHIVELOG

    There is also a 'Oracle logging script' (right side under Actions in the designer) that needs to be run by a DBA login.
    Answer: I ran this from the designer and it completed successfully, so I assume it has been done on the oracle db side... Is there any way to confirm this using eg. select statement ?

    The user that connects to the Oracle instance to read the log must have at least these priveleges on 12c:
    Answer: I will ask the DBA about this, however I have a question to some of these.
    GRANT SELECT ANY TABLE TO <USER>; - confirmed
    GRANT SELECT ANY TRANSACTION TO <USER>; - How to confirm this?
    GRANT SELECT ON V_$LOGMNR_CONTENTS TO <USER>; - returns: "ORA-01306: dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents". ??
    GRANT SELECT ON V_$ARCHIVED_LOG TO <USER>; - confirmed
    GRANT SELECT ON V_$LOGMNR_LOGS TO <USER>; - confirmed: note: this table was empty !!
    GRANT SELECT ON V_$LOG TO <USER>; - confirmed
    GRANT SELECT ON V_$LOGFILE TO <USER>; - confirmed
    GRANT SELECT ON V_$DATABASE TO <USER>; - confimed
    GRANT SELECT ON V_$INSTANCE TO <USER>; - confirmed
    GRANT EXECUTE_CATALOG_ROLE TO <USER>; - possible to check this by looking in a table ?
    GRANT LOGMINING TO <USER>; - possible to check this by looking in a table ?

    Make sure to set a certain period (1 day maybe) as log retention period for the redo logs, otherwise the CDC will go to LOGGER when the redo log switches.[/QUOTE]
    Answer: I have asked the DBA and the retension is 28 days, so not an issue

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •