Oracle problems were reported by several countries using a Oracle DB when installing the latest SU-U40-3 Core.
We found out that the problem occurs when using a connectionstring with a tnsnames.ora alias in combination with the newly used Entity Framework.
(When using a direct server name in the connectionstring the problem does not happen).
We found out that there are a number of solutions to this problem where the easiest is adding a system variable of name: TNS_ADMIN to your system variables with the location of your tnsnames.ora path
Assuming your Oracle installation is on D:\Programs\Oracle
The path would be: D:\Programs\Oracle\product\18.0.0\dbhomeXE\network\admin
(assuming Oracle version 18)
Please check that the path location contains your (correct) tnsnames.ora file !
One of the countries did not have any problems and did not set the variable by hand. This might have to do with their Oracle version (19). We however can reproduce the incident on Oracle version 18.
Please restart your services after the adjustment, but this will also be done by the configuration tool after installation of SU-U40-3
If it still doen not work, please also check the following:
– The Connection string for Entity Framework won’t allow the keyword ‘pwd’, please change it to ‘Password’.
– Sometimes a restart of your machine is necessary for the TNS_ADMIN variable to work.
– We use some scripts which aren’t compatible with Oracle versions older dan version 11. Please upgrade.
Oracle problems were reported by one country after SU-U57-2, ORA-02391 (too many session).
For now we see that a 100 session limit is not enough since this release. Please use at least 200 when setting a limit.