• State Not Answered
  • Replies 14 replies
  • Subscribers 94 subscribers
  • Views 3678 views
  • Users 0 members are here
Options
Related

Migrating Oracle database connector from Devart (ADO.NET) to DSI

Former Member
Former Member over 3 years ago

Hi,

We're preparing our migration to 8.2 from 8.1.3 . Our Oracle integration is handled by the ADO.Net Oracle connector based on Devart. As Devart is no longer supported in 8.2 we're replacing this connection with DSI, but we're facing serious issues when configuring a database connection with the native module.

  • Same target, same user connection in 8.1.3 with Devart loads the schema really fast. In fact, this is our current, working setup.
  • Same target, same user connection in 8.1.3 with DSI takes ages to load the schema and most times it ends up with a timeout due to expiration of the temporary caches (snapshot) used. Same happens if we tried this in 8.2. We're unable to end the config wizard at all. 

Has anyone experience in this issue/scenario? Another option for 8.2 would be ODP.Net , but we have no documentation at all based on this , and despite it all, we would like to stick to the standard and hang to DSI.

Thanks in advance!

Parents
  • Former Member
    0 Former Member over 3 years ago

    Nope, nothing to do with the config file , after some thorough testing. So I'm back to the beginning. Still cant figure out why with devart the schema loading is immediate whereas using DSI takes ages and ends up with an error. Stuck here.

  • 0 over 3 years ago in reply to Former Member

    Do you resolve the issue?

    We have the issue to connect Oracle database after upgrade to 8.2 with Direct Access, and were told that ODP.NET has to be used to connect Oracle DB.

  • Former Member
    0 Former Member over 3 years ago in reply to xd

    Hi xd, thanks

    For Synchronization purposes, you had two choices in 8.1.3:  Either use ADO.Net + Devart  (our choice), or  DSI, which appeared as an option long after we started working with Devart.

    As Devart is no longer supported in 8.2 we would like to make a transition to DSI which seems to be the final choice in OneIdentity. And that's when the problem arised.

    We've raised a support case.

Reply
  • Former Member
    0 Former Member over 3 years ago in reply to xd

    Hi xd, thanks

    For Synchronization purposes, you had two choices in 8.1.3:  Either use ADO.Net + Devart  (our choice), or  DSI, which appeared as an option long after we started working with Devart.

    As Devart is no longer supported in 8.2 we would like to make a transition to DSI which seems to be the final choice in OneIdentity. And that's when the problem arised.

    We've raised a support case.

Children