The function leads to a HOLD situation on Oracle databases and the WP log files contain many instances of messages like:
U00003434 Server routine 'UCGENX_R/QUITT' required '10' minutes and '40,891' seconds for processing.
The responsible SQL statement for the HOLD situation is:
select max(cloblengthb(case when OVW_Value1 is Null then to_clob('0') else OVW_Value1 end)),
max(cloblengthb(case when OVW_Value2 is Null then to_clob('0') else OVW_Value2 end)),
max(cloblengthb(case when OVW_Value3 is Null then to_clob('0') else OVW_Value3 end)),
max(cloblengthb(case when OVW_Value4 is Null then to_clob('0') else OVW_Value4 end)),
max(cloblengthb(case when OVW_Value5 is Null then to_clob('0') else OVW_Value5 end))
FROM OVW WHERE OVW_OH_Idnr = :A0001
Automic Automation Engine 24.X
Database: Oracle
DE174853
Update to a fix version listed below or a newer version if available.
Fix version:
Component(s): Automation.Engine
Automation.Engine 24.4.2 - Available
Defect Desc: An issue has been solved where, under heavy workload and only on Oracle database, one of our internal database functions performed poorly and caused time critical database calls.