After upgrading can´t access to my Oracle Data Repository

[amenedo]

After upgrading EA13 release we can´t access our projects stored in Oracle 11g repository. (with EA12.1 and previous releases everything was fine)

Some facts:

- Error message is "ORA-01005: null password given; logon denied"

- We can open projects stored in Oracle 9i perfectly and full functional.

- We always use "Oracle Provider for OLE DB" as connections provider (SQORA32.DLL V 9.2.0.80). Testing the connection string with this driver is always OK (with OLEDB tools (UDL) or similar)

- Our Oracle version is: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production

I guess the problem is how EA13 uses this driver (since the connection tests are correct with other tools) but I do not understand that in version 12 everything is correct and now stops working suddenly.

I appreciate any suggestion, we are actually blocked with projects in Oracle 11g repository.
Best Regards.

Juanjo

[hd]

Maybe you are using a 64-bit Oracle client.  EA only works with 32-bit clients.

[amenedo]

Thanks for your interest!!!

Oracle client is 32 bits.

Please consider that with EA12.1 version everything works OK (same Oracle client, OLEDB provider, OS ...)

And the same connection is OK if checked with UDL tools (see image -http://pasteboard.co/PdgOZhfmu.png- )



Regards,

[amenedo]

Hi everybody!

After reporting this issue to Sparx Support Staff, they kindly answered me with the solution:

The message ORA-01005 is prompting the user to re-enter their Oracle password, because the "Allow saving password" checkbox on the previous Connection dialog was not enabled.  Whenever that happens, the use can click OK on ORA-01005 message and the user's can re-enter their Oracle password in the next prompt.  Enabling the "Allow saving password" checkbox on the Connection dialog will stop this message appearing.  This behavior is the same as in version 12, the only difference is that the ORA-01005 message is displayed before the second prompt appears as an indication of what went wrong.  The connection string can be encrypted on the "Connection Name & Type" dialog if the password should not be available.

So, remember to check the "Allow saving password" checkbox.


Regards form Spain!

juanjo.

[Geert Bellekens]

Thanks for posting the solution Juanjo

Geert