Load Ingest Data
Results 1 to 3 of 3

Thread: Oracle BACKGROUND Processors are created when xdbcdcsvc.exe is invoked

  1. #1
    bperera is offline Junior Member
    Join Date
    Jun 2013
    Posts
    2
    Rep Power
    0

    Oracle BACKGROUND Processors are created when xdbcdcsvc.exe is invoked

    I have observed a strange behavior when a connection is made from OracleCDCService service. The user name that we are using to connect to the Oracle Database is CDCUSER. Oracle environment that we are testing this out is a 2 node RAC.

    Right now I have one OracleCDCService running on this database. If I query the GV$SESSION table for the USERNAME ‘CDCUSER’ this is what I see.

    INST_ID SID SERIAL# USER# USERNAME STATUS MACHINE TERMINAL PROGRAM TYPE
    2
    9
    2071
    302
    CDCUSER INACTIVE HOOPP\VDV1OPS03 VDV1OPS03 xdbcdcsvc.exe USER
    2
    129
    1663
    302
    CDCUSER ACTIVE HOOPP\VDV1OPS03 VDV1OPS03 xdbcdcsvc.exe USER
    2
    139
    19929
    302
    CDCUSER ACTIVE VDV1ORA2A VDV1ORA2A ORACLE.EXE (O000) BACKGROUND
    2
    259
    563
    302
    CDCUSER ACTIVE VDV1ORA2A VDV1ORA2A ORACLE.EXE (O001) BACKGROUND
    2
    365
    1857
    302
    CDCUSER INACTIVE HOOPP\VDV1OPS03 VDV1OPS03 xdbcdcsvc.exe USER
    1
    20
    28887
    302
    CDCUSER INACTIVE HOOPP\VDV1OPS03 VDV1OPS03 xdbcdcsvc.exe USER
    1
    371
    11471
    302
    CDCUSER INACTIVE HOOPP\VDV1OPS03 VDV1OPS03 xdbcdcsvc.exe USER
    The highlighted connections are the once that I would expect the OracleCDCService to make to connect to the Oracle database. As you can see there are additional connections made to the database as BACKGROUND processors. It was my initial thought that when OracleCDCService service is turned off these background processes will also be terminated. It is not so.

    Given below is the output after I stoped the OracleCDCService service.

    INST_ID SID SERIAL# USER# USERNAME STATUS MACHINE TERMINAL PROGRAM TYPE
    2
    139
    19929
    302
    CDCUSER ACTIVE VDV1ORA2A VDV1ORA2A ORACLE.EXE (O000) BACKGROUND
    2
    259
    563
    302
    CDCUSER ACTIVE VDV1ORA2A VDV1ORA2A ORACLE.EXE (O001) BACKGROUND


    Just to make sure I killed the above two processors while OracleCDCService service was not running. The processors were killed successfully and the query did not give me any results.

    Then I started up the OracleCDCService service and ran the same query. Given below is the outcome.

    INST_ID SID SERIAL# USER# USERNAME STATUS MACHINE TERMINAL PROGRAM TYPE
    2
    9
    2077
    302
    CDCUSER INACTIVE HOOPP\VDV1OPS03 VDV1OPS03 xdbcdcsvc.exe USER
    2
    129
    1667
    302
    CDCUSER ACTIVE VDV1ORA2A VDV1ORA2A ORACLE.EXE (O000) BACKGROUND
    2
    139
    19931
    302
    CDCUSER INACTIVE HOOPP\VDV1OPS03 VDV1OPS03 xdbcdcsvc.exe USER
    2
    259
    565
    302
    CDCUSER ACTIVE VDV1ORA2A VDV1ORA2A ORACLE.EXE (O001) BACKGROUND
    2
    365
    1859
    302
    CDCUSER INACTIVE HOOPP\VDV1OPS03 VDV1OPS03 xdbcdcsvc.exe USER
    1
    138
    58819
    302
    CDCUSER INACTIVE HOOPP\VDV1OPS03 VDV1OPS03 xdbcdcsvc.exe USER
    1
    371
    11661
    302
    CDCUSER INACTIVE HOOPP\VDV1OPS03 VDV1OPS03 xdbcdcsvc.exe USER

    This tells me that the ORACLE BACKGROUND processors are created by OracleCDCService service and it does not clear out once the OracleCDCService service is shout down. In addition I have observed that in some other test environments there are more than 2 BACKGROUND processors being created although there is only one OracleCDCService service running. My concern is that over time there will be a number of BACKGROUND processors created in the database that will cause problems.

  2. #2
    Join Date
    Sep 2006
    Posts
    233
    Rep Power
    10
    Likely those are background Oracle servers used by the Oracle Log Miner infrastructure and not directly under the direct control of the CDC service (see Background Processes).
    By Dror Harari

    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

  3. #3
    bperera is offline Junior Member
    Join Date
    Jun 2013
    Posts
    2
    Rep Power
    0
    Yes this is a backgroud process created by ASM Connection Pool Process. My testing proves that this is created as a result of starting the CDC process. My question is why is it not killed when the CDC process is stopped. Why do I see an incressed number of Onnn processors in the database.

Posting Permissions

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