404 error with wwv_flow.accept on basic Oracle XE form

Question

Hi all,
after some extensive research and head-scratching, I'm stumped with the following situation, and wondered if anyone here had any insights...
I have a colleague who is expermimenting with Apex using Oracle XE 10G (For various tedious reasons, we will not be able to use 11G if this gets beyond an experimental stage, so please don't suggest upgrading - I'd love to if I could, but thats how it is...)
He has constructed a very basic little database of a couple of tables, then created some simple forms to play with the data. On one form (a multiple field, multiple row screen used to update and review data in a single table), he gets intermittent 404 errors referring to wwv_flow.accept
I configured the epg to display debug info, and got a consistent stream of ORA-06550 / PLS-00103 errors all referring to finding FLOWS_020100 where it was expecting an operator, etc. (I've pasted the full debug output below minus the field data)
Installing 10G XE onto another colleague's PC did not reproduce the problem.
Removing and re-installing 10G XE onto the original PC still produced the same errors.
(And fwiw, I installed 11G XE on my PC, and that works just fine)
Does anyone have any ideas please?
many thanks,
Simon
Thu, 29 Mar 2012 15:51:21 GMT
ORA-06550: line 5, column 262:
PLS-00103: Encountered the symbol "FLOWS_020100" when expecting one of the following:
. ( * @ % & = - + ; < / > at in is mod remainder not rem
<an exponent (**)> <> or != or ~= >= <= <> and or like LIKE2_
LIKE4_ LIKEC_ between
ORA-06550: line 5, column 390:
PLS-00103: Encountered the symbol "FLOWS_020100" when expecting one of the following:
. ( * @ % & = - + ; < / > at in is mod remainder not rem
<an exponent (**)> <> or != or ~= >= <= <> and or like LIKE2_
LIKE4_ LIKEC_ between
ORA-06550: line 5, column 518:
PLS-00103: Encountered the symbol "FLOWS_020100" when expecting one of the following:
. ( * @ % & = - + ; < / > at in is mod remainder not rem
<an exponent (**)> <> or != or ~= >= <= <> and or like LIKE2_
LIKE4_ LIKEC_ between
ORA-06550: line 5, column 646:
PLS-00103: Encountered the symbol "FLOWS_020100" when expecting one of the following:
. ( * @ % & = - + ; < / > at in is mod remainder not rem
<an exponent (**)> <> or != or ~= >= <= <> and or like LIKE2_
LIKE4_ LIKEC_ between
ORA-06550: line 5, column 774:
PLS-00103: Encountered the symbol "FLOWS_020100" when expecting one of the following:
. ( * @ % & = - + ; < / > at in is mod remainder not rem
<an exponent (**)> <> or != or ~= >= <= <> and or like LIKE2_
LIKE4_ LIKEC_ between
ORA-06550: line 5, column 902:
PLS-00103: Encountered the symbol "FLOWS_020100" when expecting one of the following:
. ( * @ % & = - + ; < / > at in is mod remainder not rem
<an exponent (**)> <> or != or ~= >= <= <> and or like LIKE2_
LIKE4_ LIKEC_ between
ORA-06550: line 5, column 1030:
PLS-00103: Encountered the symbol "FLOWS_020100" when expecting one of the following:
. ( * @ % & = - + ; < / > at in is mod remainder not rem
<an exponent (**)> <> or != or ~= >= <= <> and or like LIKE2_
LIKE4_ LIKEC_ between
ORA-06550: line 5, column 1158:
PLS-00103: Encoun
DAD name: apex
PROCEDURE : wwv_flow.accept
URL : http://XDB HTTP Server:8080/apex/wwv_flow.accept
PARAMETERS :
===========
P_FLOW_ID:
100
P_FLOW_STEP_ID:
6
P_INSTANCE:
3408023606199096
P_PAGE_SUBMISSION_ID:
8087
P_REQUEST:
SUBMIT
ENVIRONMENT:
============
PLSQL_GATEWAY=WebDb
GATEWAY_IVERSION=2
SERVER_SOFTWARE=Oracle Embedded PL/SQL Gateway/10.2.0.1.0
GATEWAY_INTERFACE=CGI/1.1
SERVER_PORT=8080
SERVER_NAME=XDB HTTP Server
REQUEST_METHOD=POST
QUERY_STRING=
PATH_INFO=/wwv_flow.accept
SCRIPT_NAME=/apex
REMOTE_HOST=
REMOTE_ADDR=127.0.0.1
SERVER_PROTOCOL=HTTP/1.1
REQUEST_PROTOCOL=tcp
REMOTE_USER=ANONYMOUS
ORACLE_SSO_USER=
OSSO_IDLE_TIMEOUT_EXCEEDED=
OSSO_USER_GUID=
HTTP_CONTENT_LENGTH=32393
HTTP_CONTENT_TYPE=application/x-www-form-urlencoded
HTTP_USER_AGENT=Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
HTTP_HOST=127.0.0.1:8080
HTTP_ACCEPT=image/gif
HTTP_ACCEPT_ENCODING=gzip
HTTP_ACCEPT_LANGUAGE=en-ie
HTTP_ACCEPT_CHARSET=
HTTP_COOKIE=WWV_CUSTOM-F_715517672407298_100=B599E605240FC50A968356801BEB7337; WWV_FLOW_USER2=B599E605240FC50A968356801BEB7337; ORA_WWV_REMEMBER_UN=POWER_R:POWER_R; LOGIN_USERNAME_COOKIE=power_r; ISCOOKIE=true
HTTP_IF_MODIFIED_SINCE=
HTTP_REFERER=http://127.0.0.1:8080/apex/f?p=100:6:3408023606199096:::::&success_msg=1 row(s) updated, 0 row(s) inserted./3F535DE29AC2AD2F95C620169B16EB79/
HTTP_SOAPACTION=
HTTP_ORACLE_ECID=
HTTP_ORACLE_CACHE_VERSION=
HTTP_AUTHORIZATION=
WEB_AUTHENT_PREFIX=
DAD_NAME=apex
DOC_ACCESS_PATH=docs
DOCUMENT_TABLE=wwv_flow_file_objects$
PATH_ALIAS=
REQUEST_CHARSET=AL32UTF8
REQUEST_IANA_CHARSET=UTF-8
SCRIPT_PREFIX=
HTTP_IF_MATCH=
HTTP_CACHE_CONTROL=
SOAP_BODY=
HTTP_X_ORACLE_DEVICE_CLASS=
HTTP_X_ORACLE_DEVICE_ORIENTATION=
HTTP_X_ORACLE_DEVICE_MAXDOCSIZE=
HTTP_X_ORACLE_DEVICE=
HTTP_X_ORACLE_ORIG_ACCEPT=
HTTP_X_ORACLE_ORIG_USER_AGENT=
HTTP_X_ORACLE_USER_LOCALE=
HTTP_X_ORACLE_USER_NAME=
HTTP_X_ORACLE_USER_DISPLAYNAME=
HTTP_X_ORACLE_USER_USERKIND=
HTTP_X_ORACLE_USER_AUTHKIND=
HTTP_X_ORACLE_USER_DEVICEID=
HTTP_X_ORACLE_USER_LOCATION_ADDRESSLINE1=
HTTP_X_ORACLE_USER_LOCATION_ADDRESSLINE2=
HTTP_X_ORACLE_USER_LOCATION_ADDRESSLASTLINE=
HTTP_X_ORACLE_USER_LOCATION_BLOCK=
HTTP_X_ORACLE_USER_LOCATION_CITY=
HTTP_X_ORACLE_USER_LOCATION_COMPANYNAME=
HTTP_X_ORACLE_USER_LOCATION_COUNTY=
HTTP_X_ORACLE_USER_LOCATION_STATE=
HTTP_X_ORACLE_USER_LOCATION_POSTALCODE=
HTTP_X_ORACLE_USER_LOCATION_POSTALCODEEXT=
HTTP_X_ORACLE_USER_LOCATION_COUNTRY=
HTTP_X_ORACLE_USER_LOCATION_TYPE=
HTTP_X_ORACLE_USER_LOCATION_X=
HTTP_X_ORACLE_USER_LOCATION_Y=
HTTP_X_ORACLE_SERVICE_HOME_URL=
HTTP_X_ORACLE_SERVICE_PARENT_URL=
HTTP_X_ORACLE_HOME_URL=
HTTP_X_ORACLE_MODULE_CALLBACK_URL=
HTTP_X_ORACLE_MODULE_CALLBACK_LABEL=
HTTP_X_ORACLE_CACHE_USER=
HTTP_X_ORACLE_CACHE_SUBID=
HTTP_X_ORACLE_CACHE_AUTH=
HTTP_X_ORACLE_CACHE_DEVICE=
HTTP_X_ORACLE_CACHE_LANG=
HTTP_X_ORACLE_CACHE_ENCRYPT=
HTTP_X_ORACLE_ASSERT_USER=

Answer 1

No, its a very sensible question... :)
The difficulty I face is that it is required to test this on Oracle 10G XE, so upgrading Apex is out due to it being bundled in.
Any actual deployment would be into an Oracle 10 environment initially, which is why it was desired to use 10G XE as the test before going about configuring anything "for real". I guess I might have to look at actually deploying it into a full test environment - especially as the error only happens on one PC.
It would be nice to know why it does it though, just to generate a bit more confidence in the user base!