This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unable to select Oracle as a Target in ARS Sync service

Hello,

I've created a Oracle connection in ARS Sync but wehn i got to create a Sync Workflow it does not let me select it as Target.

Does anyone know how I can make a OLEDB connection a Target in ARS Sync Service?

Thank you,

Lu

  • We too recently encountered this ... disappointing "feature" in 7.X Sync Service
    There is a  <air quotes>   hybrid work-around.

    https://support.oneidentity.com/active-roles/kb/261189/does-quick-connect-support-active-roles-7-3-1-

    Support has confirmed that while it is not listed specifically in the Sync Engine Release Notes documentation,  that it is supported to use ARS 7.3.1 (ADSI Provider) with the latest version of Quick Connect Synchronization Engine 5.5 and Quick Connect for Base Systems 2.4.

    The latest version of Sync Engine is 5.5.

    This give you a work-around if you have an entitlement to the software.

    https://support.oneidentity.com/quick-connect-sync-engine/5.5
    The latest version for the Base Connector is 2.4.
    https://support.oneidentity.com/quick-connect-for-base-systems/2.4
    Using that solution you can continue to use the Oracle connector in Quick Connect for Base Systems 2.4 in parallel with the new-built in synchronization service.

    tested and confirmed.

  • I took a different approach and actually installed the Oracle client on my Sync Service host and use ODBC to get to Oracle.

    There is an ODBC data source setup on my Sync Service host that uses the Oracle driver and points to the MyApplicationName settings described below.

    FWIW, the connection string (configured in an ODBC Connector in the Sync Service) looks like this:

    Driver={Oracle in OraHome1};Dbq=DatabaseName;Uid=ARSQC;Pwd=**********;

    The file TNSNAMES.ORA found in this folder (created by the Oracle client setup):

    D:\app\MySyncServiceAccount\OraHome_1\Network\Admin\Sample

    This file location must be setup in an environment variable TNS_ADMIN

    The TNSNAMES.ORA file contains additional settings required to make the database connection.  In my environment, the internals look like this:

    (I've changed some of the names to protect the innocent):

    MyApplicationName = 

    (Description =

    (Address = (Protocol = TCP)(Host = xxx.xxx.xxx.xxx)(PORT = xxxxx) (CONNECT DATA = 

    (SERVER = DEDICATED)

    (SERVICE_NAME = MyDatabaseName)

    )

    )

    Note that since the Connection string contains credentials, those that exist in the ODBC data source are ignored.

    Is this complicated?  Yep.  But I hope someone finds it helpful. Slight smile

  • Johnny,

    Thanks for the tips I will give this a try. Complicate a bit but, hey as long as it works it works.

    Appreciate your guidance.

    Lu

  • Dynannic,

    Thank you for the information and links.

    I will look into them and see what is my best option.

    I appreciate the guidance.

    Lu

  • I was able to make a Oracle connection and map it to a SQL table.

    Although when I go to create the workflow I choose SQL as the Source and want to choose OLEDB as target  i cannot see the OLEDB as a Target option.

    I can however make OLEDB the source and SQL the target so that is weird. 

  • The Admin guide states that OLEDB connections are read only so any connection of this type can never be selected as a Target system.