It seems that querying oracle dba_types/all_types data-dictionary table with connect by in 11g can cause some performance and stability issues.
The code of ut_runner.get_reporters_list needs to be rewritten to provide better performance and stability.
Also, to avoid round trips to DB from client, the function should expose additional info.
Today it returns:
reporter_object_name varchar2(250), -- full reporter name in format: owner.name
is_output_reporter varchar2(1), -- Y/N indication of reporter providing output for API
Should now return:
reporter_object_name varchar2(250), -- full reporter name in format: owner.name
is_output_reporter varchar2(1), -- Y/N indication of reporter providing output for API
owner varchar2(128), -- reporter owner (ut3 owner name)
name varchar2(128), -- reporter name
description varchar2(4000), -- reporter description
That way, the result-set is backward-compatible but client can consume the data in new format too.
References: utPLSQL/utPLSQL-cli#98
It seems that querying oracle
dba_types/all_typesdata-dictionary table withconnect byin 11g can cause some performance and stability issues.The code of
ut_runner.get_reporters_listneeds to be rewritten to provide better performance and stability.Also, to avoid round trips to DB from client, the function should expose additional info.
Today it returns:
Should now return:
That way, the result-set is backward-compatible but client can consume the data in new format too.
References: utPLSQL/utPLSQL-cli#98