APEX Package WWV_FLOW.ACCEPT Errors with ORA-06502: PL/SQL: numeric or value error: character string buffer too small When Using OHS / Mod_plsql
(Doc ID 2439946.1)
Last updated on FEBRUARY 18, 2021
Applies to:Oracle Application Express (APEX) - Version 5.0.4.00.12 and later
Oracle HTTP Server - Version 184.108.40.206.0 to 220.127.116.11.0 [Release Oracle11g to 12c]
Oracle REST Data Services - Version 3.0 and later
Information in this document applies to any platform.
APEX has been upgraded, and a new 18.104.22.168 Oracle HTTP Server (OHS) has been created. The APEX applications are all running successfully, however some actions within the APEX tool are failing with:
The requested URL /pls/apex/wwv.flow.accept NOT found
This error occurs when editing a region's source for an application page, and when editing the page alias and page name for an application.
The corresponding error in the OHS error log (ohs1.log) are:
[2018-07-17T10:43:44.4753-05:00] [OHS] [ERROR:32] [OHS-9999] [core.c] [client_id: xx.xxx.xx.xxx] [host_id: dtemwb02] [host_addr: xxx.xx.xx.xxx] [tid: 26] [user: root] [ecid: <ECID>] [rid: 0] [VirtualHost: main] MODPLSQL-00261: mod_plsql: /pls/apex/wwv_flow.accept HTTP-404 Failed to execute target procedure ORA-00604: error occurred at recursive SQL level 1\nORA-06502: PL/SQL: numeric or value error: character string buffer too small\nORA-06512: at line 27\nORA-06550: line 33, column 3:\nPLS-00306: wrong number or types of arguments in call to 'ACCEPT'\nORA-06550: line 33, column 3:\nPL/SQL: Statement ignored\n, referer: http://<HOSTNAME>/pls/apex/f?p=4000:4301:2740162577671:::4301:F4000_P4301_ID,FB_FLOW_ID,FB_FLOW_PAGE_ID:1,105,1
A standalone ORDS instance was created for diagnostic testing. The problem does not reproduce when using Oracle REST Data Services (ORDS) as the front end web server for APEX.
- The actual APEX applications run without error. This includes the vendor applications and the home grown applications.
- The problem could not be reproduced internally with either 22.214.171.124 or with 126.96.36.199 version of OHS.
- Multiple databases and multiple OHS environments were tested at the customer site. The failure occurs consistently with OHS / mod_plsql regardless of environment.
- All third party software (load balancers, firewalls, etc.) was disabled / turned off. The problem still reproduces.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Option 1 (Recommended) Use ORDS as the web server for APEX, instead of OHS / mod_plsql|
|Option 2 Modify the database trigger so that the integrity of the parameters passed to the APEX engine is retained|
|Option 3 Disable the database level trigger|