"WARNING: too many parse errors" Using OHS with APEX Applications (Doc ID 2541626.1)

Last updated on FEBRUARY 09, 2023

Applies to:

Symptoms

Though this was initially reported with APEX, the problem has also been seen with mod_plsql applications.

1. APEX 5.1.3, OHS 12.1.3, Webgate 12c. DB 12.2.0.1

2. Very poor performance with APEX applications using OHS 12.1.3 configured with webgate.

3. DB alert log shows messages like the following about every five minutes:
=========================================================================================
PARSE ERROR: ospid=18022666, error=6550

WARNING: too many parse errors, count=60424 SQL hash=0x4713af8a
PARSE ERROR: ospid=18022666, error=6550 for statement:
2019-03-13T13:50:28.080274-05:00
declare
rc__ number;
simple_list__ owa_util.vc_arr;
complex_list__ owa_util.vc_arr;
begin
owa.init_cgi_env(:n__,:nm__,:v__);

htp.HTBUF_LEN := 63;
null;
null;
simple_list__(1) := 'sys.%';
simple_list__(2) := 'dbms\_%';
simple_list__(3) := 'utl\_%';
simple_list__(4) := 'owa\_%';
simple_list__(5) := 'owa.%';
simple_list__(6) := 'htp.%';
simple_list__(7) := 'htf.%';
simple_list__(8) := 'wpg_docload.%';
simple_list__(9) := 'ctxsys.%';
simple_list__(10) := 'mdsys.%';
if ((wwv_flow_epg_include_modules.authorize(
'wwv_flow.ajax'
) = false) or (owa_match.match_pattern(p_string =>
'wwv_flow.ajax'
/* */,p_simple_pattern =>
simple_list__
,p_complex_pattern =>
complex_list__
,p_use_special_chars =>
false)))
then
rc__ := 2;
else
null;
null;
wwv_flow.ajax(p_flow_id=>:p_flow_id,p_flow_step_id=>:p_flow_step_id,p_instance=>:p_instance,p_debug=>:p_debug,p_request=>:p_request,p_json=>:p_json);
if (wpg_docload.is_file_download) then
rc__ := 1;
wpg_docload.get_download_file(:doc_info);
null;
null;
null;
commit;
else
rc__ := 0;
null;
null;
null;
commit;
owa.get_page(:data__,:ndata__);
end if;
end if;
:rc__ := rc__;
end;
=========================================================================================

Note that the code in bold is the actual code causing the failure, and not owa.init_cgi_env(:n__,:nm__,:v__);...

4. No custom code involved. Message is related to default APEX download of Interactive Reports/Grids such as Action -> Download

5. Restarting OHS resolves the issue for some period of time.

Note that parse errors can be normal but if they occur too often they can have a negative impact on database performance. See <Note 2320935.1>

Changes

 None known.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.