Apex 4.0 EA3 -signup error

Guys,
I am getting the following error on Apex 4.0 EA3 signup page (http://tryapexnow.com/apex/f?p=101:1)
ORA-0000: normal, successful completion
Error Unable to fetch authentication_scheme in application 101.
Thanks
Balaji

ok thanks it worked also.
I use apex listener, and can go to http://localhost:8888/em
and follow the step on PDF "Oracle Application Express Listener Version 1.0 June 2010" , all no error
but now next problem can't go to http://localhost:8888/apex/ListenerConfigure
can anybody help ??

Similar Messages

APEX Listener EA2 Standalone CLOB error

I'm testing the APEX Listener EA2 release in Standalone mode on CentOS against Oracle XE.
My RESTful service calls use the Media Resource type to return a CLOB that I format myself inside a function:
select 'application/json', my_function_that_returns_json_in_a_clob from dual
In the EA2 release, this is generating an error if the function returns more than 4000 bytes (works with 4000, fails with 4001). It is as though the function is getting cast as a varchar2 somewhere. I verified that the function will correctly return a large result to other sources (dbms_output, for instance).
The APEX Listener Log reports the error as:
oracle.dbtools.rt.web.HttpEndpointBase restfulServices
SEVERE: ORA-22922: nonexistent LOB value
Here's a Test Case:
create or replace function test_size(p_cnt in integer) return clob
is
l_clob clob;
begin
for i in 1..p_cnt loop
l_clob:=l_clob||'a';
end loop;
return l_clob;
end;
Then create a RESTful service call:
Method: "GET"
Source Type: "Media Resource"
Source: select 'application/json', test_size(4001) from dual
Thanks,
Tim

Thanks for your thorough reply!
Unfortunately, your workaround doesn't fix the problem with EA2. It encounters the 4000 character limit as well.
I understand your advice regarding using the QUERY type. I chose the Media Resource strategy for two main reasons:
1. These services calls are for our mobile developers. Because they use some predefined frameworks for managing data that comes to the mobile app, they wanted the json to distinguish between data sets (rather than every data set being called "items"). I am able to format the json in such a way that it doesn't confuse their code. Is there another way to customize the format of the default json created by the QUERY type?
2. I need to conduct some other business as part of the call. For instance, the service passes in a user's credentials which I use to authenticate and then retrieve the appropriate results based on who they are. Currently, I have stored procedures that authenticate APEX users or LDAP users.
Perhaps old habits die hard, but I find that if I just do all of this myself in a stored function, I have all of the control I need. If you have other recommended strategies, I'm all ears.
Thanks!
_Tim

Re: BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns

Hello Everyone.
I've run into something quite strange and am hoping you can help me.
I am using Apex 4.0.1 and Oracle version 10.2.0.5. I've created a "classical" report in which the underlying SQL is a very simple:
select * from pvtabThe Oracle table pvtab consists of 419 columns, all of which are varchar2(88) and number type. That's it.
When I run the report, al of the columns show up as expected.
However, when I go into the "Report Attributes" tab and click on one of the fields (any of them, it doesn't matter which one), I immediately get the following error:
ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "598CAA7B68746A66F4B99E1512C36DED" application checksum = "0"If if replace the "*" with a few actual column names, then I am able to access any of these columns without problem.
If I put back the "*", I then encounter this error again.
I have never seen this error with other SQL SELECT statements in which I use the "*" qualifier to retrieve all columns from the table.
And so, I am wondering if the error is caused because of the large number of columns (419) in my table.
I've seen this same error mentioned in connection with forms but never with a report.
So, is there some limit to the number of columns one can have in a "classic" or interactive report?
Any idea why I would be getting this error?
Here is the DDL for my table pvtab:
CREATE TABLE "PVTAB"
   (     "MICRO" VARCHAR2(4),
     "PRIM" VARCHAR2(4),
     "UNIT" NUMBER,
     "SEC_REF_1" NUMBER,
     "SECN_1" VARCHAR2(88),
     "SEC_REF_2" NUMBER,
     "SECN_2" VARCHAR2(88),
     "SEC_REF_3" NUMBER,
     "SECN_3" VARCHAR2(88),
     "SEC_REF_4" NUMBER,
     "SECN_4" VARCHAR2(88),
     "SEC_REF_5" NUMBER,
     "SECN_5" VARCHAR2(88),
     "SEC_REF_6" NUMBER,
     "SECN_6" VARCHAR2(88),
     "SEC_REF_7" NUMBER,
     "SECN_7" VARCHAR2(88),
     "SEC_REF_8" NUMBER,
     "SECN_8" VARCHAR2(88),
     "SEC_REF_9" NUMBER,
     "SECN_9" VARCHAR2(88),
     "SEC_REF_10" NUMBER,
     "SECN_10" VARCHAR2(88),
     "SEC_REF_11" NUMBER,
     "SECN_11" VARCHAR2(88),
     "SEC_REF_12" NUMBER,
     "SECN_12" VARCHAR2(88),
     "SEC_REF_13" NUMBER,
     "SECN_13" VARCHAR2(88),
     "SEC_REF_14" NUMBER,
     "SECN_14" VARCHAR2(88),
     "SEC_REF_15" NUMBER,
     "SECN_15" VARCHAR2(88),
     "SEC_REF_16" NUMBER,
     "SECN_16" VARCHAR2(88),
     "SEC_REF_17" NUMBER,
     "SECN_17" VARCHAR2(88),
     "SEC_REF_18" NUMBER,
     "SECN_18" VARCHAR2(88),
     "SEC_REF_19" NUMBER,
     "SECN_19" VARCHAR2(88),
     "SEC_REF_20" NUMBER,
     "SECN_20" VARCHAR2(88),
     "SEC_REF_21" NUMBER,
     "SECN_21" VARCHAR2(88),
     "SEC_REF_22" NUMBER,
     "SECN_22" VARCHAR2(88),
     "SEC_REF_23" NUMBER,
     "SECN_23" VARCHAR2(88),
     "SEC_REF_24" NUMBER,
     "SECN_24" VARCHAR2(88),
     "SEC_REF_25" NUMBER,
     "SECN_25" VARCHAR2(88),
     "SEC_REF_26" NUMBER,
     "SECN_26" VARCHAR2(88),
     "SEC_REF_27" NUMBER,
     "SECN_27" VARCHAR2(88),
     "SEC_REF_28" NUMBER,
     "SECN_28" VARCHAR2(88),
     "SEC_REF_29" NUMBER,
     "SECN_29" VARCHAR2(88),
     "SEC_REF_30" NUMBER,
     "SECN_30" VARCHAR2(88),
     "SEC_REF_31" NUMBER,
     "SECN_31" VARCHAR2(88),
     "SEC_REF_32" NUMBER,
     "SECN_32" VARCHAR2(88),
     "SEC_REF_33" NUMBER,
     "SECN_33" VARCHAR2(88),
     "SEC_REF_34" NUMBER,
     "SECN_34" VARCHAR2(88),
     "SEC_REF_35" NUMBER,
     "SECN_35" VARCHAR2(88),
     "SEC_REF_36" NUMBER,
     "SECN_36" VARCHAR2(88),
     "SEC_REF_37" NUMBER,
     "SECN_37" VARCHAR2(88),
     "SEC_REF_38" NUMBER,
     "SECN_38" VARCHAR2(88),
     "SEC_REF_39" NUMBER,
     "SECN_39" VARCHAR2(88),
     "SEC_REF_40" NUMBER,
     "SECN_40" VARCHAR2(88),
     "SEC_REF_41" NUMBER,
     "SECN_41" VARCHAR2(88),
     "SEC_REF_42" NUMBER,
     "SECN_42" VARCHAR2(88),
     "SEC_REF_43" NUMBER,
     "SECN_43" VARCHAR2(88),
     "SEC_REF_44" NUMBER,
     "SECN_44" VARCHAR2(88),
     "SEC_REF_45" NUMBER,
     "SECN_45" VARCHAR2(88),
     "SEC_REF_46" NUMBER,
     "SECN_46" VARCHAR2(88),
     "SEC_REF_47" NUMBER,
     "SECN_47" VARCHAR2(88),
     "SEC_REF_48" NUMBER,
     "SECN_48" VARCHAR2(88),
     "SEC_REF_49" NUMBER,
     "SECN_49" VARCHAR2(88),
     "SEC_REF_50" NUMBER,
     "SECN_50" VARCHAR2(88),
     "SEC_REF_51" NUMBER,
     "SECN_51" VARCHAR2(88),
     "SEC_REF_52" NUMBER,
     "SECN_52" VARCHAR2(88),
     "SEC_REF_53" NUMBER,
     "SECN_53" VARCHAR2(88),
     "SEC_REF_54" NUMBER,
     "SECN_54" VARCHAR2(88),
     "SEC_REF_55" NUMBER,
     "SECN_55" VARCHAR2(88),
     "SEC_REF_56" NUMBER,
     "SECN_56" VARCHAR2(88),
     "SEC_REF_57" NUMBER,
     "SECN_57" VARCHAR2(88),
     "SEC_REF_58" NUMBER,
     "SECN_58" VARCHAR2(88),
     "SEC_REF_59" NUMBER,
     "SECN_59" VARCHAR2(88),
     "SEC_REF_60" NUMBER,
     "SECN_60" VARCHAR2(88),
     "SEC_REF_61" NUMBER,
     "SECN_61" VARCHAR2(88),
     "SEC_REF_62" NUMBER,
     "SECN_62" VARCHAR2(88),
     "SEC_REF_63" NUMBER,
     "SECN_63" VARCHAR2(88),
     "SEC_REF_64" NUMBER,
     "SECN_64" VARCHAR2(88),
     "SEC_REF_65" NUMBER,
     "SECN_65" VARCHAR2(88),
     "SEC_REF_66" NUMBER,
     "SECN_66" VARCHAR2(88),
     "SEC_REF_67" NUMBER,
     "SECN_67" VARCHAR2(88),
     "SEC_REF_68" NUMBER,
     "SECN_68" VARCHAR2(88),
     "SEC_REF_69" NUMBER,
     "SECN_69" VARCHAR2(88),
     "SEC_REF_70" NUMBER,
     "SECN_70" VARCHAR2(88),
     "SEC_REF_71" NUMBER,
     "SECN_71" VARCHAR2(88),
     "SEC_REF_72" NUMBER,
     "SECN_72" VARCHAR2(88),
     "SEC_REF_73" NUMBER,
     "SECN_73" VARCHAR2(88),
     "SEC_REF_74" NUMBER,
     "SECN_74" VARCHAR2(88),
     "SEC_REF_75" NUMBER,
     "SECN_75" VARCHAR2(88),
     "SEC_REF_76" NUMBER,
     "SECN_76" VARCHAR2(88),
     "SEC_REF_77" NUMBER,
     "SECN_77" VARCHAR2(88),
     "SEC_REF_78" NUMBER,
     "SECN_78" VARCHAR2(88),
     "SEC_REF_79" NUMBER,
     "SECN_79" VARCHAR2(88),
     "SEC_REF_80" NUMBER,
     "SECN_80" VARCHAR2(88),
     "SEC_REF_81" NUMBER,
     "SECN_81" VARCHAR2(88),
     "SEC_REF_82" NUMBER,
     "SECN_82" VARCHAR2(88),
     "SEC_REF_83" NUMBER,
     "SECN_83" VARCHAR2(88),
     "SEC_REF_84" NUMBER,
     "SECN_84" VARCHAR2(88),
     "SEC_REF_85" NUMBER,
     "SECN_85" VARCHAR2(88),
     "SEC_REF_86" NUMBER,
     "SECN_86" VARCHAR2(88),
     "SEC_REF_87" NUMBER,
     "SECN_87" VARCHAR2(88),
     "SEC_REF_88" NUMBER,
     "SECN_88" VARCHAR2(88),
     "SEC_REF_89" NUMBER,
     "SECN_89" VARCHAR2(88),
     "SEC_REF_90" NUMBER,
     "SECN_90" VARCHAR2(88),
     "SEC_REF_91" NUMBER,
     "SECN_91" VARCHAR2(88),
     "SEC_REF_92" NUMBER,
     "SECN_92" VARCHAR2(88),
     "SEC_REF_93" NUMBER,
     "SECN_93" VARCHAR2(88),
     "SEC_REF_94" NUMBER,
     "SECN_94" VARCHAR2(88),
     "SEC_REF_95" NUMBER,
     "SECN_95" VARCHAR2(88),
     "SEC_REF_96" NUMBER,
     "SECN_96" VARCHAR2(88),
     "SEC_REF_97" NUMBER,
     "SECN_97" VARCHAR2(88),
     "SEC_REF_98" NUMBER,
     "SECN_98" VARCHAR2(88),
     "SEC_REF_99" NUMBER,
     "SECN_99" VARCHAR2(88),
     "SEC_REF_100" NUMBER,
     "SECN_100" VARCHAR2(88),
     "SEC_REF_101" NUMBER,
     "SECN_101" VARCHAR2(88),
     "SEC_REF_102" NUMBER,
     "SECN_102" VARCHAR2(88),
     "SEC_REF_103" NUMBER,
     "SECN_103" VARCHAR2(88),
     "SEC_REF_104" NUMBER,
     "SECN_104" VARCHAR2(88),
     "SEC_REF_105" NUMBER,
     "SECN_105" VARCHAR2(88),
     "SEC_REF_106" NUMBER,
     "SECN_106" VARCHAR2(88),
     "SEC_REF_107" NUMBER,
     "SECN_107" VARCHAR2(88),
     "SEC_REF_108" NUMBER,
     "SECN_108" VARCHAR2(88),
     "SEC_REF_109" NUMBER,
     "SECN_109" VARCHAR2(88),
     "SEC_REF_110" NUMBER,
     "SECN_110" VARCHAR2(88),
     "SEC_REF_111" NUMBER,
     "SECN_111" VARCHAR2(88),
     "SEC_REF_112" NUMBER,
     "SECN_112" VARCHAR2(88),
     "SEC_REF_113" NUMBER,
     "SECN_113" VARCHAR2(88),
     "SEC_REF_114" NUMBER,
     "SECN_114" VARCHAR2(88),
     "SEC_REF_115" NUMBER,
     "SECN_115" VARCHAR2(88),
     "SEC_REF_116" NUMBER,
     "SECN_116" VARCHAR2(88),
     "SEC_REF_117" NUMBER,
     "SECN_117" VARCHAR2(88),
     "SEC_REF_118" NUMBER,
     "SECN_118" VARCHAR2(88),
     "SEC_REF_119" NUMBER,
     "SECN_119" VARCHAR2(88),
     "SEC_REF_120" NUMBER,
     "SECN_120" VARCHAR2(88),
     "SEC_REF_121" NUMBER,
     "SECN_121" VARCHAR2(88),
     "SEC_REF_122" NUMBER,
     "SECN_122" VARCHAR2(88),
     "SEC_REF_123" NUMBER,
     "SECN_123" VARCHAR2(88),
     "SEC_REF_124" NUMBER,
     "SECN_124" VARCHAR2(88),
     "SEC_REF_125" NUMBER,
     "SECN_125" VARCHAR2(88),
     "SEC_REF_126" NUMBER,
     "SECN_126" VARCHAR2(88),
     "SEC_REF_127" NUMBER,
     "SECN_127" VARCHAR2(88),
     "SEC_REF_128" NUMBER,
     "SECN_128" VARCHAR2(88),
     "SEC_REF_129" NUMBER,
     "SECN_129" VARCHAR2(88),
     "SEC_REF_130" NUMBER,
     "SECN_130" VARCHAR2(88),
     "SEC_REF_131" NUMBER,
     "SECN_131" VARCHAR2(88),
     "SEC_REF_132" NUMBER,
     "SECN_132" VARCHAR2(88),
     "SEC_REF_133" NUMBER,
     "SECN_133" VARCHAR2(88),
     "SEC_REF_134" NUMBER,
     "SECN_134" VARCHAR2(88),
     "SEC_REF_135" NUMBER,
     "SECN_135" VARCHAR2(88),
     "SEC_REF_136" NUMBER,
     "SECN_136" VARCHAR2(88),
     "SEC_REF_137" NUMBER,
     "SECN_137" VARCHAR2(88),
     "SEC_REF_138" NUMBER,
     "SECN_138" VARCHAR2(88),
     "SEC_REF_139" NUMBER,
     "SECN_139" VARCHAR2(88),
     "SEC_REF_140" NUMBER,
     "SECN_140" VARCHAR2(88),
     "SEC_REF_141" NUMBER,
     "SECN_141" VARCHAR2(88),
     "SEC_REF_142" NUMBER,
     "SECN_142" VARCHAR2(88),
     "SEC_REF_143" NUMBER,
     "SECN_143" VARCHAR2(88),
     "SEC_REF_144" NUMBER,
     "SECN_144" VARCHAR2(88),
     "SEC_REF_145" NUMBER,
     "SECN_145" VARCHAR2(88),
     "SEC_REF_146" NUMBER,
     "SECN_146" VARCHAR2(88),
     "SEC_REF_147" NUMBER,
     "SECN_147" VARCHAR2(88),
     "SEC_REF_148" NUMBER,
     "SECN_148" VARCHAR2(88),
     "SEC_REF_149" NUMBER,
     "SECN_149" VARCHAR2(88),
     "SEC_REF_150" NUMBER,
     "SECN_150" VARCHAR2(88),
     "SEC_REF_151" NUMBER,
     "SECN_151" VARCHAR2(88),
     "SEC_REF_152" NUMBER,
     "SECN_152" VARCHAR2(88),
     "SEC_REF_153" NUMBER,
     "SECN_153" VARCHAR2(88),
     "SEC_REF_154" NUMBER,
     "SECN_154" VARCHAR2(88),
     "SEC_REF_155" NUMBER,
     "SECN_155" VARCHAR2(88),
     "SEC_REF_156" NUMBER,
     "SECN_156" VARCHAR2(88),
     "SEC_REF_157" NUMBER,
     "SECN_157" VARCHAR2(88),
     "SEC_REF_158" NUMBER,
     "SECN_158" VARCHAR2(88),
     "SEC_REF_159" NUMBER,
     "SECN_159" VARCHAR2(88),
     "SEC_REF_160" NUMBER,
     "SECN_160" VARCHAR2(88),
     "SEC_REF_161" NUMBER,
     "SECN_161" VARCHAR2(88),
     "SEC_REF_162" NUMBER,
     "SECN_162" VARCHAR2(88),
     "SEC_REF_163" NUMBER,
     "SECN_163" VARCHAR2(88),
     "SEC_REF_164" NUMBER,
     "SECN_164" VARCHAR2(88),
     "SEC_REF_165" NUMBER,
     "SECN_165" VARCHAR2(88),
     "SEC_REF_166" NUMBER,
     "SECN_166" VARCHAR2(88),
     "SEC_REF_167" NUMBER,
     "SECN_167" VARCHAR2(88),
     "SEC_REF_168" NUMBER,
     "SECN_168" VARCHAR2(88),
     "SEC_REF_169" NUMBER,
     "SECN_169" VARCHAR2(88),
     "SEC_REF_170" NUMBER,
     "SECN_170" VARCHAR2(88),
     "SEC_REF_171" NUMBER,
     "SECN_171" VARCHAR2(88),
     "SEC_REF_172" NUMBER,
     "SECN_172" VARCHAR2(88),
     "SEC_REF_173" NUMBER,
     "SECN_173" VARCHAR2(88),
     "SEC_REF_174" NUMBER,
     "SECN_174" VARCHAR2(88),
     "SEC_REF_175" NUMBER,
     "SECN_175" VARCHAR2(88),
     "SEC_REF_176" NUMBER,
     "SECN_176" VARCHAR2(88),
     "SEC_REF_177" NUMBER,
     "SECN_177" VARCHAR2(88),
     "SEC_REF_178" NUMBER,
     "SECN_178" VARCHAR2(88),
     "SEC_REF_179" NUMBER,
     "SECN_179" VARCHAR2(88),
     "SEC_REF_180" NUMBER,
     "SECN_180" VARCHAR2(88),
     "SEC_REF_181" NUMBER,
     "SECN_181" VARCHAR2(88),
     "SEC_REF_182" NUMBER,
     "SECN_182" VARCHAR2(88),
     "SEC_REF_183" NUMBER,
     "SECN_183" VARCHAR2(88),
     "SEC_REF_184" NUMBER,
     "SECN_184" VARCHAR2(88),
     "SEC_REF_185" NUMBER,
     "SECN_185" VARCHAR2(88),
     "SEC_REF_186" NUMBER,
     "SECN_186" VARCHAR2(88),
     "SEC_REF_187" NUMBER,
     "SECN_187" VARCHAR2(88),
     "SEC_REF_188" NUMBER,
     "SECN_188" VARCHAR2(88),
     "SEC_REF_189" NUMBER,
     "SECN_189" VARCHAR2(88),
     "SEC_REF_190" NUMBER,
     "SECN_190" VARCHAR2(88),
     "SEC_REF_191" NUMBER,
     "SECN_191" VARCHAR2(88),
     "SEC_REF_192" NUMBER,
     "SECN_192" VARCHAR2(88),
     "SEC_REF_193" NUMBER,
     "SECN_193" VARCHAR2(88),
     "SEC_REF_194" NUMBER,
     "SECN_194" VARCHAR2(88),
     "SEC_REF_195" NUMBER,
     "SECN_195" VARCHAR2(88),
     "SEC_REF_196" NUMBER,
     "SECN_196" VARCHAR2(88),
     "SEC_REF_197" NUMBER,
     "SECN_197" VARCHAR2(88),
     "SEC_REF_198" NUMBER,
     "SECN_198" VARCHAR2(88),
     "SEC_REF_199" NUMBER,
     "SECN_199" VARCHAR2(88),
     "SEC_REF_200" NUMBER,
     "SECN_200" VARCHAR2(88),
     "SEC_REF_201" NUMBER,
     "SECN_201" VARCHAR2(88),
     "SEC_REF_202" NUMBER,
     "SECN_202" VARCHAR2(88),
     "SEC_REF_203" NUMBER,
     "SECN_203" VARCHAR2(88),
     "SEC_REF_204" NUMBER,
     "SECN_204" VARCHAR2(88),
     "SEC_REF_205" NUMBER,
     "SECN_205" VARCHAR2(88),
     "SEC_REF_206" NUMBER,
     "SECN_206" VARCHAR2(88),
     "SEC_REF_207" NUMBER,
     "SECN_207" VARCHAR2(88),
     "SEC_REF_208" NUMBER,
     "SECN_208" VARCHAR2(88)
   );Thank you for any help/advice.
Elie
Edited by: EEG on Jun 12, 2011 2:09 PM

So, is there some limit to the number of columns one can have in a "classic" or interactive report?Yes. See Oracle® Application Express Application Builder User's Guide Release 4.0, Appendix B: Oracle Application Express Limits.
Any idea why I would be getting this error?No, but I've replicated it in APEX 4.0.2.00.07 on 11.2.0.1.0 EE using a table of 420 <tt>varchar2(88)</tt> columns:
>
ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "50C9BDC0AA1AEF0EB272E9158B2117B4" application checksum = "0"
>
Happens whether using <tt>select *</tt> or including all column names in the query. (I know you don't want to type all the column names, but I'd never use <tt>select *</tt> in a production application: always use a proper column list. You can get one without typing by drag-and-drop of a table in most IDEs, or a query from <tt>user_tab_columns</tt>.)
I hit the problem at 274 columns. Such an arbitrary number leads me to think that the problem is not one of the number of columns per se, but is due to some other limit (possibly a 32K VARCHAR2/RAW buffer somewhere).
Workaround:
Updates to the report column attributes are actually being saved, and you can navigate them using the Page Definition tree view as described in Appendix B.
Getting More Help:
This is probably a bug. If you have a support agreement with Oracle raise an SR with Oracle Support.
Also:
<li>Search the forum using the "ORA-20503" code and other possible terms to see if there's anything relevant. I had a quick look but the only thread in this context recommended an upgrade on an Oracle 9 DB version that's not compatible with APEX 4.0.
<li>To get the attention of the Oracle APEX team or anyone else who may know more about this problem than we do, edit your original post and change the Subject to be more specific about the actual nature of the problem: <em>BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns</em>, and include your database version/edition and the definition of the <tt>PVTAB</tt> table.
Finally:
Somebody's bound to ask, so we might as well get started:
<li>Why so many columns?
<li>What requirement is this trying to fulfil?

On Login to Workspace requested URL /pls/apex/f was not found Error

Dear All,
When I log into a workspace I get the following :
The requested URL /pls/apex/f was not found on this server.
Note:
1. The workspace was working fine and while working only this issue started and the problem exists since.
2. I am able to log into Internal Workspace
The Error_Log is as follows:
[Wed Jun 15 12:56:09 2011] [error] [client IP ADDRESS REMOVED] [ecid: 1308131768:IP ADDRESS REMOVED:2320:2580:12,0] mod_plsql: /pls/apex/f HTTP-404 ORA-20867: ORA-01654: unable to extend index APEX_040000.WWV_FLOW_ACTIVITY_LOG2$_IDX2 by 8 in tablespace APEX\nORA-06512: at "APEX_040000.WWV_FLOW_LOG", line 208\nORA-06512: at "APEX_040000.WWV_FLOW", line 12472\nORA-06512: at "APEX_040000.F", line 267\nORA-06512: at "APEX_040000.F", line 294\nORA-06512: at line 22\n
Thanks & Regards
Arif Khadas
Edited by: Arif Khadas on Jun 15, 2011 1:26 PM

Problem Solved.
APEX TABLESPACE Problem.

Integrating Google Maps in Oracle Apex and 404 Not found error page

Currently using APEX version 3.2.0.00.27 installed in OracleXE version 10.2.0.1.0. Have been attempting to recreate some examples of Google Maps within APEX. Found a nice set of examples here that build up to what I'm looking to ultimately do by incorporating google maps into APEX:
http://blog.whitehorses.nl/2009/10/04/integrating-google-maps-in-oracle-apex/
Unfortunatly, I'm getting the "404 Not Found, Not found, The requested URL /apex/wwv_flow.accept was not found on this server" page when I try to recreate the "Map with Search" example. I'd like to see if this really works using the html input and button tags in the body/region source versus creating APEX items to pass the address values to the javascript in the html header of the apex page. I'm thinking it's just an html thing within APEX that you have to do it a certain way, but I haven't managed to hit that magic combination. have gone to the google maps api v2 and looked at the html they use (it's what these examples with apex are based on) and tried that just to see. Same 404 result.
I've seen suggestions at this forum and elsewhere that the 404 error is due to a bug. have been to metalink, and really haven't seen anything that spells out what the bug is and how to patch it or work around it. May be I just haven't found the right note/doc yet. have seen suggestions to change something associated with the Anonymous account that APEX uses. Have turned on authentication in the application to use an APEX user account with a logon page to the application. Still get the 404. Although, I have not adjusted anything elsewhere, like a DADS config file, because the apex/xe configuration is using the plsql gateway. Not sure of any procedure for changing settings on anonymous account when using plsql gateway.
Open to suggestions. APEX 3.2 is customer version, so going to 4 may not be an option yet. XE, on the other hand, can certainly be swapped for an 11g version standard or enterprise edition if need be. I don't think this is a db version problem though. I think it's more on the APEX side of things.
Anyway, any help or suggestions are appreciated.
thanks
rtp
Edited by: RTP on Jun 24, 2011 10:30 AM

Hi I have the same problem.... if you found the solution, please put it here to see it... I need a solution to this its urgent!!
Thanks!!

Upgrade to Apex 4.1 results in "Error processing SSO authentication"

We recently upgraded our Apex environment to 4.1 from 4.0.2. In our previous environment we used SSO authentication. Some how in the new Apex 4.1 we can get to all our applications with the url https://test.home.org/pls/apex put any application which requires SSO authentication gives this message:
Error processing SSO authentication.ORA-06550: line 2, column 1: PLS-00201: identifier 'WWSEC_SSO_ENABLER_PRIVATE.GENERATE_REDIRECT' must be declared ORA-06550: line 1, column 45: PL/SQL: Statement ignored
Has anyone run into a similar issue? Any insights?
Thanks.

After upgrading to APEX release 4.1.0.00.32 we received the following errors when attempt to authenticate to an application setup to use "Oracle Application Server Single Sign-On" as the Scheme Type.
Error message:
Error processing SSO authentication.
ORA-06550: line 2, column 1: PLS-00201: identifier 'WWSEC_SSO_ENABLER_PRIVATE' must be declared ORA-06550: line 1, column 45: PL/SQL: Statement ignored
ORA-06550: line 2, column 1: PLS-00201: identifier 'WWSEC_SSO_ENABLER_PRIVATE.GENERATE_REDIRECT' must be declared ORA-06550: line 1, column 45: PL/SQL: Statement ignored
This has been identified as BUG 12973090 - SSO WITH SPECIFIED PARTNER APPLICATION NAME FAILS WITH PLS-00201
Workaround:
The work around is to leave the “Partner Application Name” field blank in your authentication scheme. To do this go to: Application Builder > Your Application > Shared Components > Authentication Schemes > Click the Edit Icon on your authentication scheme that uses Single Sign-On > set the “Partner Application Name blank as follows > Apply Changes.
Oracle support says development is currently working the issue and the bug will not be fixed until APEX release 4.1.1.
Sean
Edited by: Sean Harris on Nov 2, 2011 7:59 AM

When upgrade to APEX 4.0, an ORA error, Is it bug?

Oracle Database 10g Express Edition Release 10.2.0.1.0, APEX 3.2.1
When it processed on
...PAGE 591: Create / Edit Action
ERROR:
ORA-01756: quoted string not properly terminated
is it aninstallation bug?

Hello,
I met same problem as robinZ when upgrading APEX 3.2.1 to 4.0. Database is 11.2.0.1.0.
Here is a procedure of installation. It's almost same as user12146287 but I use apex_4.0.zip, not apex_4.0_en.zip.
1, unzip apex_4.0.zip
2, create tablespace for APEX 4.0
CREATE BIGFILE TABLESPACE ts_apex4 DATAFILE 'C:\xxx\TS_APEX4.DBF' SIZE 100M AUTOEXTEND ON NEXT 10M MAXSIZE UNLIMITED;
3, move to apex folder
4, login db with SQL*Plus as sysdba
5, run "@apexins ts_apex4 ts_apex4 temp /i/"
6, then I've received ORA-01756 error. Here is a log
VI. I N S T A L L B U I L D E R A P P L I C A T I O N S
define "^" (hex 5e)
APPLICATION 4000 - Oracle APEX AppBuilder
Set Credentials...
Check Compatibility...
API Last Extended:20100513
Your Current Version:20100513
This import is compatible with version: 20100513
COMPATIBLE (You should be able to run this import without issues.)
Set Application ID...
...authorization schemes
...navigation bar entries
...application processes
...application items
...application level computations
...Application Tabs
...Application Parent Tabs
...Shared Lists of values
...Application Trees
...page groups
...PAGE 0: Page Zero
...PAGE 1: Application Builder
...PAGE 2: Supporting Objects
...PAGE 3: Grid Edit Breadcrumbs
...PAGE 4: Define Master Table
...PAGE 584: Copy Template
...PAGE 585: Confirm Create Web Service Reference
...PAGE 586: Breadcrumb Hierarchy
...PAGE 587: Copy Branch
...PAGE 588: Test Web Service
...PAGE 589: View Web Reference
...PAGE 590: Copy Process
...PAGE 591: Create / Edit Action
ERROR:
ORA-01756: 引用符付き文字列が正しく終了していません

APEX 4.0.1 Installation error (WWV_FLOW_4000_UI invalid)

Hi All,
I'm upgrade my APEX from 3.2 to 4.0.1(Oracle 10.2.3 on Solaris, DB character, US7ASCII, I downlad the APEX english version); during the installation scripts, There are some errors regarding package(WWV_FLOW_4000_UI):
Warning: Package Body created with compilation errors.
Errors for PACKAGE BODY WWV_FLOW_4000_UI:
LINE/COL ERROR
1138/22 PL/SQL: SQL Statement ignored
1139/16 PL/SQL: ORA-00942: table or view does not exist
1143/9 PL/SQL: Statement ignored
1146/29 PLS-00364: loop index variable 'L_VERSION' use is invalid
Any one have seen this?
Thanks
Mike
Edited by: user482029 on Oct 13, 2010 1:13 PM

ok thanks it worked also.
I use apex listener, and can go to http://localhost:8888/em
and follow the step on PDF "Oracle Application Express Listener Version 1.0 June 2010" , all no error
but now next problem can't go to http://localhost:8888/apex/ListenerConfigure
can anybody help ??

BUG -- Column filtering bug in Apex 4.1 causing pagination error?

Hi All,
I'm getting a pagination error, when filtering from the column header in an Interactive Report.
Report error:
Invalid set of rows requested, the source data of the report has been modified.
Reset Pagination*
The steps to recreate:
1. Run an Interactive Report
2. Click the next button to go to the second page of data.
3. From the column header select a data element that will return less than 15 rows. Note -- if the there are 15 or more rows of data, the error will not occur.
The Report will fail with the error shown above.
Note that the same error does not occur if you use the filter from the Action menu. This appears to be a bug in the column filtering.
It looks like the pagination needs to be reset after the column filter, but how is this done?
I'm using the canned interactive report with no customizations. Is there a fix for this issue?
Thanks

This «bug» is known for a long time unfortunately...
I never find any solution for IR report filtering.
Maybe you can use some JQuery to change the link when clicking a value in the list, (add a code that will update pagination).
Something like :
$('#apexir_rollover_content').load(function() {
$(this).find('a').click(function(){
gReport.search('SEARCH');
});But I don't think it will work, as they already use JQuery to bind that <a> events.
In case you update your report using a button, you can simply use a "reset pagination" process called on button click.
In case you use column link you simply have to tick the «Reset Pagination» checkbox.
I hope Apex team will fix that one day.
Good luck.
Yann.

Apex reload jquery after validation error

After a validation error has ocured my jquery does not laod. What must i do in order to reload the whole page again after the validation error?

jquery always loads fine. I'm not going into a big what-if-then-what discussion about what might or might not be causing this. You're simply not giving us any information about both your setup and what is happening.
This validation on your text fields, what is it? I suspect it is not the standard apex validation. Are these plain standard text fields? When does the error occur? When you submit the page? Have you tried to debug? Did you take a look at the browser's developer tools console and see if there is any javascript error? Anything special you are not mentioning because you think it might not be relevant? Considered recreating your issue on apex.oracle.com?

Move apex to another http server "Error on Page"

Hi,
I runing apex 2.2 on an oracle http server, but now I have installed collaboration suite on the same server and want to move my apex. Can't get it working the browser says "Error on page", the login button is not working and strange fonts.
I hade moved image directory and created the marvel.conf + included in http.conf.
http error log shows entries:
File does not exist: /oracle/product/ocs_app/Apache/Apache/htdocs/calendar/images/javascript/htmldb_html_elements.js
but my marvel.conf has:
Alias /i/ "/oracle/product/http/Apache/Apache/images/"
Have tried to copy images also to /oracle/product/ocs_app/Apache/Apache/htdocs/calendar/ the errors disappears from log file but browser still shows “Error on Page”
Can anyone help, please?

Hi Praveen,
Looks like a Reverse Proxy solution where you have one HTTP server in DMZ and one behind the firewalls. Please check Apache docs for Reverse Proxy. You can also use Web Cache for this purpose, or use a Hardware Load Balancer.
Regards,
Martin

APEX 3.0 print report error (empty file).

I installed BI 10.1.3.2.0 successfully.
I tested my convert servlet (which comes with BI Publisher)
by trying to go there directly in browser:
http://roman:80/xmlpserver/convert
I get the message in Firefox:
"500 Internal Server Error
Servlet error: An exception occurred. The current application deployment descriptors do not allow for including it in this response. Please consult the application log for details".
The application.log contents:
"07/04/09 16:42:38.928 xmlpserver: Servlet error
javax.servlet.ServletException: XML data or RTF template is null.
     at oracle.apps.xdo.servlet.Converter.doPost(Converter.java:99)
     at oracle.apps.xdo.servlet.Converter.doGet(Converter.java:50)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind[Oracle Containers for J2EE 10g
(10.1.3.1.0) ].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)".
It's mean that servlet is up and running.
I specify the following attributes:
Oracle BI Publisher: Advanced Support
Print Server Protocol: HTTP
Print Server Host Address: roman (the name of my computer)
Print Server Port: the port 80
Print Server Script: /xmlpserver/convert
When i click on link "Print report" in my application i receive the empty pdf file
(file size is zero).
Is it any idea ?
Regards,
Roman

Hi Marc!
I uninstalled BI EE. Then I installed Bi EE again. I selected the Basic setup and BI Publisher only. BI Publisher has been successfully installed on my computer.
The number of port is 9704. (My previous mistake was the port number - 80!!!).
Then I start oc4j.
I tried Application Builder home page built-in report. It's work fine!
But i received some problems with print report in my own application.
If i selected "Use Generic Column Names (parse query at runtime only)" in source settings of my region i received an empty PDF file (0 bytes).
When i selected "English (United-States) en-us in Globalization settings and also
selected "Use Query-Specific Column Names and Validate Query" in source settings of my region i received the fine report.
I am using the "Default report Layout".
But I want to receive the report based on "Query-Specific Column Names and Validate Query". And also I want to have "Russian (ru) Globalization settings in my application.
Do your have any advice ?
Regards,
Roman.

Problem Connection To Apex - Getting a ORA-12705 Error in the Apache Log

Hello,
We are having issues trying to connect to out Apex instance on our gateway server, as we are getting a 503 Server Temporary Unavailable response and looking in the log file we can see its reporting a:
HTTP-503 ORA-12705: invalid or unkown NLS parameter value specifiedAnd we dont know what is causing this at all. Our DBA has tried to re-create the DAD and we have had a look at our NLS settings and there doesn't seem anything to suggest there is a problem. Also our DBA has been able to connect to the database using SQL plus and as the user APEX_PUBLIC_USER. Below is our NLS settings on the database:
NLS_LANGUAGE     AMERICAN
NLS_TERRITORY     AMERICA
NLS_CURRENCY     $
NLS_ISO_CURRENCY     AMERICA
NLS_NUMERIC_CHARACTERS     .,
NLS_CHARACTERSET     WE8MSWIN1252
NLS_CALENDAR     GREGORIAN
NLS_DATE_FORMAT     DD-MON-RR
NLS_DATE_LANGUAGE     AMERICAN
NLS_SORT     BINARY
NLS_TIME_FORMAT     HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT     DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT     HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT     DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY     $
NLS_COMP     BINARY
NLS_LENGTH_SEMANTICS     BYTE
NLS_NCHAR_CONV_EXCP     FALSE
NLS_NCHAR_CHARACTERSET     AL16UTF16
NLS_RDBMS_VERSION     11.2.0.2.0and our dad configuration is:
Alias /i/ "<$ORACLE_HOME>/Apache/images/"
AddType text/xml xbl
AddType text/x-component htc
<Location /pls/apex>
Order deny,allow
PlsqlDocumentPath docs
AllowOverride None
PlsqlDocumentProcedure wwv_flow_file_mgr.process_download
PlsqlDatabaseConnectString <host>:<port>:<service name> ServiceNameFormat
PlsqlNLSLanguage AMERICAN_AMERICA.AL32UTF8
PlsqlAuthenticationMode Basic
SetHandler pls_handler
PlsqlDocumentTablename wwv_flow_file_objects$
PlsqlDatabaseUsername APEX_PUBLIC_USER
PlsqlDefaultPage apex
PlsqlDatabasePassword <apex_public_user password>
PlsqlRequestValidationFunction wwv_flow_epg_include_modules.authorize
Allow from All
</Location>Our database version is: 11.2.0.2 and our application server is 10g release 2.
Any help on this would be greatly appreciated.
Cheers,
Paul.

This is normally an issue related to environment variables.
can you connect from your application server host to your database using sqlplus.
SET NLS_LANG=AMERICAN_AMERICAN.WE8MSWIN1252
sqlplus <username>/<password>@alias

Apex 4.2 forms conversion error when set application defaults

when use migration forms conversion and i want to set application defaults return the next error
Unable to seed values ORA-06550: line 15, column 82: PL/SQL: ORA-00918: column ambiguously defined ORA-06550: line 9, column 3: PL/SQL: SQL Statement ignored
ORA-06550: line 15, column 82: PL/SQL: ORA-00918: column ambiguously defined ORA-06550: line 9, column 3: PL/SQL: SQL Statement ignored

Hi Daniel,
This issue has already been identified, tracked with bug number *14683491*, and has been resolved in development. The fix will be available in our next release. In the meantime, you can still set Application Defaults using the option available in Application Builder. Navigate to Application Builder, and select the Application Builder Defaults option in the Tasks region to the right of the page, pg 4000:1500.
Regards,
Hilary

Problem with APEX 4.0 - "ORA-20001: Error with: GRANT CREATE CLUSTER "

I have a workspace which I've succesfully created with schema A.
However when i try to assign an additional schema to it, schema B, I get the following error message :-
"ORA-20001: Error with: GRANT CREATE CLUSTER TO "BI_SOURCES" ORA-01031: insufficient privileges"
i've tried granting "create cluster with admin option' to users A,B,anonymous AND APEX_040000. FLOWS_030000 already has these privileges.
Anybody any ideas ?
regs
johnnie
Edited by: johnnie d on 31-Aug-2011 10:58

I have experience the similiar problem. The error message: Invalid exist/not exist condition: ORA 2001 Query must begin with Select or With.
I have home page and concept review report page below home page. And Concept review form under the report page. The error is display in all of the three pages. I checked carefully and still not able to find where the error come from. Can you please help? All the report region and form region have the select statement, is it from the LOVs? Home
Concept review report
Concept reveiw Form(for detail info)
Thank you!

Apex 4.0 EA3 -signup error

Similar Messages

Maybe you are looking for