This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hello: I've been using LightSpeed to construct my model with VS2010 and the Oracle Data Provider for .NET (ODP.NET) however it seems that LightSpeed isn't handling the case where my server explorer connection utilizes OS authentication. After testing that my connection works in both Server Explorer and SQLPlus, LightSpeed throws the exception below when dragging a table onto the model. Exception while processing Server Explorer drag: Mindscape. LightSpeed.Generator.ModelGernationException: Couldn't connect to the database. Check that the connection information is correct. ----> System.Data.OracleClient.OracleException: OracleException: ORA-01005: null password given; logon denied What stands out to me is System.Data.OracleClient.OracleException since that differs from ODP.NET which is in the namespace Oracle.DataAccess I created a second account, one that uses a defined password i.e. matthew/matthew rather than using OS authentication and everything works. |
|
|
Internally, the designer uses System.Data.OracleClient when it needs to connect to the database. It looks like a Server Explorer connection created using ODP with OS authentication has "User Id=/" (a la SQL*Plus) in the connection string, whereas for OracleClient to use OS auth you have to specify "Integrated Security=true" instead. I've added a kludge to recognise when we're getting the "User Id=/" version in the designer and to substitute in "Integrated Security=true". Note that we will of course NOT make this substitution at runtime -- the substitution is ONLY for the designer because the designer always uses OracleClient, whereas the runtime will use ODP.NET if you tell it to and will therefore be able to handle ODP's connection string syntax. So nothing in the runtime behaviour will change. However, do note that if you use the Get Started command, it will show you the post-munging OracleClient connection string -- you will need to edit it back to the ODP syntax after pasting it into your app.config. I hope this makes sense and isn't too confusing! I ran into a minor issue while testing this where it didn't recognise primary keys. I believe this is due to the way our test database is configured rather than to a real issue. However if you see a similar problem then do let us know so we can investigate further. This change will be included in nightly builds dated 21 July 2010 and above, available from about 1500 GMT. |
|
|
Hi Ivan: I'll try to installing the new build after the 21st and let you know if I run into any minor issues. Thanks for the great support! |
|