Vision crashes due to Oracle account logout

[emaddocks]

We have recently implemented some cyber security controls on our Oracle RDB and as a result we set the IDLE_TIME to be 4 hours. However we started to get Vision crashes and we have narrowed down the cause to be this IDLE_TIME setting.

To reproduce the issue we reduced the IDLE_TIME setting to 1 minute and the Vision crashes when it attempts to re-query the RDB after Oracle has timed out the session. The following messages are output to the log viewer when the crash occurs:

Code: Select all

WCCOAui      (2), 2025.02.03 10:53:40.787, CTRL, INFO,        0, , The Database Connection has been lost! , ORA-01012: not logged on
Process ID: 0
Session ID: 29 Serial number: 19889
WCCOAui      (2), 2025.02.03 10:53:40.787, CTRL, INFO,        0, , Try connect to available data base orpss_sid
WCCOAui2:WCCOAui: /work/WinCCOA/ExternLibs/SQLAPI/unix/src/oraClient.cpp:613: virtual void Iora8Connection::Connect(const SAString&, const SAString&, const SAString&): Assertion `m_handles.m_pOCIEnv == NULL' failed.

We are running WinCC OA 3.18 Patch 24 on RHEL 8.8 with Oracle 19c. We have the config entry '[ui] queryRDBdirect = 1' on the workstations so they open their own connection to the RDB.

Is this a known issue or is there a way to configure the Vision to just re-connect to the RDB when it receives this "ORA-01012: not logged on" message?

Cheers
Eric

[hpuchegger]

We had a similar issue (with exactly the same location in the code /work/WinCCOA/ExternLibs/SQLAPI/unix/src/oraClient.cpp:613) which was fixed for WinCC OA 3.20.2. Can you please check on a test system if this issue still occurs with the new WinCC OA 3.20.x?

If it is related to WinCC OA version 3.18, please create a support ticket and provide your log and config folder.

Br, Herbert

[emaddocks]

As v3.18 is still a supported version shouldn't the bug have also been fixed in a recent v3.18 patch?

[leoknipp]

If a bug is found in a specific version it is mostly fixed in this version.
Not all bugs found in a newer version are also fixed in all other mainline versions.

Best Regards
Leopold Knipp
Senior Support Specialist