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!

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

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!

Top Replies

Parents

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.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Reply

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.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Children

0 xd 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.
Cancel
Up +1 Down

Reply

Verify Answer

Cancel
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.
Cancel
Up 0 Down

Reply

Verify Answer

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

Hello there,

Is the DSI to stand for Data Source Integration?

With the Support assistance, we are able to resolve the issue using Oracle Database Extended mode within Wizard. Thanks for your feedbacks!
Cancel
Up 0 Down

Reply

Verify Answer

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

Hi xd,
Cancel
Up 0 Down

Reply

Verify Answer

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

Hi xd, thanks again.

DSI stands for Database System Integrations, the module provided by OneIdentity to connect to different database systems, including Oracle.

We've raised a Support Assistance Case , still open. Could you please detail which settings did you use in the Database Extended mode? Thanks!
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 CVU over 3 years ago in reply to xd

Hi. My former account was banned off the forum. Still wonder why.

DSI stands for Database Systems Integration, the actual connector that handles db endpoints such as Oracle , Mysql...

Could you please tell us which extended options were modified to have it working?
Thanks!
Cancel
Up +1 Down

Reply

Verify Answer

Cancel
0 xd over 3 years ago in reply to CVU

Hello CVU,

We did the following based on the Support suggestion. In Generic Database Connector Wizard, we choose Oracle Database and selected the Extended checkbox. In the pop-up console for Oracle Connection we define Data source as below. Please note there should not have the line break (all is in one line). It works well for us to sync or provision data with Oracle Database. HTH

(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp) (HOST=viper.oracleebsdb.com) (PORT=1522)) (CONNECT_DATA=(SERVICE_NAME=EBSDB)));
Cancel
Up +1 Down

Reply

Verify Answer

Cancel
0 Former Member over 2 years ago in reply to CVU

Good day Former Member CVU can you confirm your account is still banned? if so, please send me a Private Message so I can assist you with your issue promptly

Thank you

Jorge Carrasco
Community Manager
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 Former Member over 2 years ago in reply to Former Member

Hi Jorge! It's all fixed now, thanks a lot !!
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 Former Member over 2 years ago in reply to Former Member

Hi Jorge! It's all fixed now, thanks a lot !!
Cancel
Up 0 Down

Reply

Verify Answer

Cancel