When submitting a page using After Submit with Automatic Row Processing (DML) and a PL/SQL Anonymous Block process (that also does DML), you sometimes get timeout errors.
Or, when using i.e. Tomcat, errors like "No more data to read from socket".

In the trace logs you find stuff like this:

*** 2014-06-20 17:07:00.257
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x8] [PC:0x25DFBB3, pesl_src_dst_cmp()+691] [flags: 0x0, count: 1]

*** 2014-06-20 17:07:00.786
Incident 5043 created, dump file: /u01/app/oracle/diag/rdbms/staging/staging/incident/incdir_5043/staging_ora_16614_i5043.trc
ORA-07445: exception encountered: core dump [pesl_src_dst_cmp()+691] [SIGSEGV] [ADDR:0x8] [PC:0x25DFBB3] [Address not mapped to object] []

ssexhd: crashing the process...
Shadow_Core_Dump = PARTIAL

Cause: both the Automatic Row Processing (DML) and the PL/SQL Anonymous Block try to manipulate the same row.

Solution: Use either Automatic Row Processing (DML) or the PL/SQL Anonymous Block, not both.

Or (in other browsers): HTTP 400 - Bad Request - The HTTP client sent a request that this server could not understand.
When submitting a form with a lot of arguments (parameters), you may get this error. More info and solutions in the links below.


https://community.oracle.com/thread/2409100
"Sounds like you're submitting too many parameters (15 * 130 = 1950), very close to 2000
Check this post regarding PlsqlMaxParameters:
https://community.oracle.com/thread/272149
One of our developers has used a wizard to create a tabular form with the intent or providing an interface for updating one of our tables. The page runs correctly up until the point when the user clicks the Submit button. The user is then re-directed to a "page cannot be found" error page. I checked the apache error log and I'm seeing this error (ip addresses hidden):
[Wed Oct 13 06:37:59 2004] [error] [client x.xxx.xxx.xxx] [ecid: 1097674679:x.xx.xxx.xx:7286:0:23738,0] mod_plsql: /pls/htmldb/wwv_flow.accept HTTP-400 Too many arguments passed in. Got 2009 parameters. Upper limit is 2000"


http://jk-consult.nl/tag/plsqlmaxparameters/
"To resolve the issue the PlsqlMaxParameter needed to be added to plsql.conf. (We tried to do this in dads.conf to keep most of Oracle HTTP Server unaffected, but got errored out).
We chose the value of 4000, meaning a 100% increase while maintaining a fair and safe limit.

For Oracle HTTP Server, the parameter is set in plsql.conf which can be found in either:
$ORACLE_BASE/Oracle_WT1/instances/instance1/config/OHS/ohs1/moduleconf
$ORACLE_BASE/ohs/Apache/modplsql/conf

For Oracle EPG, the parameter can be set as follows:
dbms_epg.set_global_attribute(‘max-parameters’, ‘100’);"


A workaround using collections by Denes Kubice is described here: https://apex.oracle.com/pls/apex/f?p=31517:294

In Apex (4.2.2) you'll get this error if the pl/sql code of a page validation you edit is longer than 4000 characters.
This will probably happen in other places as well.

When using the Object Browser in Apex ("SQL Workshop -> Object Browser") to edit and compile objects, you may run into this error.
This seems to be caused solely by the size of the object that you try to compile. In my case a view of 3400 bytes had this issue, while a view of 1200 bytes compiled just fine.

A Google search does not give many hits or suggestions. I found the hint about the object size at https://community.oracle.com/thread/1043317?start=15&tstart=0. Note that this post is from 2011, and that the bug still exists in Apex 19.2...

The solution is simple but not very elegant: copy/paste the source into the "SQL Workshop -> SQL Commands" window and run it there.