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

Similar Messages

  • Error in SSO authentication

    Hi,
    I have an apex application tied up with SSO. I have to make edits to this application now, but when I run the application I am getting following error:
    Error     Error processing SSO authentication.
    ORA-06550: line 1, column 7: PLS-00201: identifier 'WWV_FLOW_CUSTOM_AUTH_SSO.PORTAL_SSO_REDIRECT' must be declared ORA-06550: line 1, column 7: PL/SQL: Statement ignoredAny help to solve this issue is appreciated.
    I am using:
    Application Express 4.1.0.00.32
    DB details - Oracle Database 11g Enterprise Edition Release 11.2.0.1.0
    Web server architecture - APEX listener
    Browser(s) and version(s) used - Chrome version 24/ Firefox version 3.6 and version 18
    Thanks!

    Try searching this forum on WWV_FLOW_CUSTOM_AUTH_SSO.PORTAL_SSO_REDIRECT. You can do that in google as well and will get millions of answers.
    Denes Kubicek
    http://deneskubicek.blogspot.com/
    http://www.apress.com/9781430235125
    http://apex.oracle.com/pls/apex/f?p=31517:1
    http://www.amazon.de/Oracle-APEX-XE-Praxis/dp/3826655494
    -------------------------------------------------------------------

  • 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: 引用符付き文字列が正しく終了していません

  • Upgrade to Apex 4.2 - apex.widget.tabular' is null or not an object

    After upgrading to Apex 4.2 the following error occurrs when loading a page that contains a Group Select List [Plug-in]:
    *'apex.widget.tabular' is null or not an object*
    The error message appears to be related to a Group Select List [Plug-in] item with the following assigned List of Values attributes(options):
    Display Null Value: Yes
    Null Display Value: -
    Null Return Value: NULL
    Note: The application requires a NULL option to be displayed in the list of values (display = '-', value = null). This works fine in Apex 4.1...
    Removing the above values does eliminate the error message. However entering any value into the Null Display Value and Null Return Value item attributes causes the error message to reappear.
    Is this a known Group Select List [Plug-in] issue/bug? Any ideas on how to work around this issue would be greatly appreciated.
    Thx

    Hi,
    http://apex.oracle.com/plugins contains an updated version of the Group Selectlist plug-in (v1.1) which should fix your problem. Just import it into your application and you should be done.
    Regards
    Patrick

  • XML document must have a top level element. Error processing resource

    Hi,
    I am trying to send a XML file to a web browser from a servlet. I read the contents of the XML file into a string and I am sending it to the brower. Before I do this I set the 'Content-type' header of the httpResponse to "application/xml" . Embedded in the XML file is an xml-stylesheet elemetn indicating which *.xsl stylesheet to use to parse the XML content.
    I get the following error:
    The XML page cannot be displayed
    Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
    XML document must have a top level element. Error processing resource 'http://127.0.0.1:8080/testReplyingXML/xml-to-html.xs...
    Now, if I take the stylesheet element out of the XML string I sent, then the browser stores the content into and *.xml file. I manually run the "xml-to-xsl " stylesheet mentioned in the error output above, and there is no problem, the xml content gets successfully transformed in a viewable HTML .
    It is only when I embed the "stylesheet" element into the XML content that I get this error.
    So the browser is receiveing valid XML.
    I am not sure if the above error is complaining about the XML content I send or the stylesshet .
    Does anyone have an idea of what am I doing wrong?
    For your information here are my servlet code and the XML file:
    servlet:-
    package webapps.testReplyingXML;
    import java.io.BufferedReader;
    import java.io.IOException;
    import javax.servlet.ServletException;
    import javax.servlet.http.HttpServlet;
    import javax.servlet.http.HttpServletRequest;
    import javax.servlet.http.HttpServletResponse;
    import java.io.FileReader;
    import java.util.Enumeration;
    import java.util.StringTokenizer;
    import java.io.PrintWriter;
    public class ReplyXML extends HttpServlet {
              static int transactionCount = 0;
              public void doGet(HttpServletRequest req, HttpServletResponse res) throws ServletException ,IOException {
                   String Q_PARAM = "query";
                   String requestString = req.getQueryString();
                   for ( Enumeration en = req.getParameterNames() ; en.hasMoreElements() ; )
         String k = (String)en.nextElement() ;
         String[] x = req.getParameterValues(k) ;
         String s = null;
         String DATA_PARAM= "";
         for(int i = 0 ; i < x.length ; i++ )
         s = x[i] ;
         //System.out.println("s = " + s);
         if (k.equals("query")){
              try {
                             //res.setHeader("Content-Type", "application/xml");
                             //res.setHeader("Transfer-Encoding", "chunked");
                             //res.setHeader("Cache-Control", "no-cache");
                             //res.setHeader("Server", "Jetty/5.1.10");
                             //res.setHeader("Pragma", "no-cache");
                             //res.setHeader("X-Joseki-Server", "Joseki-3.0-dev");
                             res.setStatus(res.SC_OK);
                             StringBuffer fileData = new StringBuffer(1000);
                        BufferedReader reader = new BufferedReader(new FileReader("sparql_results.xml"));
                        char[] buf = new char[1024];
                        int numRead=0;
                        while((numRead=reader.read(buf)) != -1){
                        String readData = String.valueOf(buf, 0, numRead);
                        fileData.append(readData);
                        buf = new char[1024];
                        reader.close();
                        String xmlMsg= fileData.toString();
                        System.out.println("XMLMSG= " + xmlMsg);
                             PrintWriter outresp = res.getWriter();
                             outresp.println(xmlMsg);
                             outresp.close();
              }catch (Exception e) {
                   e.printStackTrace();
              public void doPost(HttpServletRequest req, HttpServletResponse res) throws ServletException, IOException {
                   doGet(req, res);
    XML FILE:
    <?xml version="1.0"?>
    <?xml-stylesheet type="text/xsl" href="xml-to-html.xsl"?>
    <sparql
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:xs="http://www.w3.org/2001/XMLSchema#"
    xmlns="http://www.w3.org/2005/sparql-results#" >
    <head>
    <variable name="book"/>
    <variable name="title"/>
    </head>
    <results ordered="false" distinct="false">
    <result>
    <binding name="book">
    <uri>http://example.org/book/book6</uri>
    </binding>
    <binding name="title">
    <literal>Harry Potter and the Half-Blood Prince</literal>
    </binding>
    </result>
    <result>
    <binding name="book">
    <uri>http://example.org/book/book5</uri>
    </binding>
    <binding name="title">
    <literal>Harry Potter and the Order of the Phoenix</literal>
    </binding>
    </result>
    <result>
    <binding name="book">
    <uri>http://example.org/book/book4</uri>
    </binding>
    <binding name="title">
    <literal>Harry Potter and the Goblet of Fire</literal>
    </binding>
    </result>
    <result>
    <binding name="book">
    <uri>http://example.org/book/book3</uri>
    </binding>
    <binding name="title">
    <literal>Harry Potter and the Prisoner Of Azkaban</literal>
    </binding>
    </result>
    <result>
    <binding name="book">
    <uri>http://example.org/book/book2</uri>
    </binding>
    <binding name="title">
    <literal>Harry Potter and the Chamber of Secrets</literal>
    </binding>
    </result>
    <result>
    <binding name="book">
    <uri>http://example.org/book/book1</uri>
    </binding>
    <binding name="title">
    <literal>Harry Potter and the Philosopher's Stone</literal>
    </binding>
    </result>
    </results>
    </sparql>

    Error processing resource http://127.0.0.1:8080/testReplyingXML/xml-to-html.xs...
    Well, if one more character had been deleted from that message then you would have a problem. But as it is, the error message says there's an error processing a resouce whose name ends with "xml-to-html.xs" followed by something. That would be the stylesheet if I'm not mistaken. Most likely the browser can't find it at the URL mentioned in the error message.

  • After upgrade to Apex 4.2.1, login to old workspace results in 404

    I have made an upgrade to Apex 4.2.1 from Apex 4.1 runtime.
    (Upgrade completed successfully no errors encountered.)
    I had an installed app which I cannot use now.
    Login to apex_admin is possible, so I've created developer users in the existing workspace.
    Developer users get
    404 - Not found error when logging in to the workspace, with
    http://mysrv:8080/apex/wwv_flow.acceptin the address line.
    It is apparent in the DB that the existing application has been copied to apex_040200 DB schema.
    Same error is displayed when navigating to the app's login page, say http://mysrv:8080/apex/f?p=123:1
    I use GlassFish Server Open Source Edition 3.1.1.
    After upgrading Apex Listener to 2.0.1 (from 1.1.3), nothing has changed except that
    404 appears in white over a blue background stripe.
    Under / Monitor Activity / Login Attempts, there are only Incorrect Password entries
    However, after creating a new WS, I can log into it.
    Is there a way to use to WS and APP created in the older Apex version 4.1 ?

    Under apex_admin, among all workspace requests, I first had to deselect status = 1,
    then my workspace has appeared in the list with status "-". After clicking on Adjust,
    status "Terminated" appeared, who knows why.
    Since I changed workspace status to Approved, login is working.
    Questions:
    1/ How comes that status "Terminated" was not shown on the existing workspaces list?
    2/ What leads to the Terminated status, while the app was reachable before upgrade to 4.2.1?
    While App builder is appearing nice, my app has lost its design.
    3/ Where are images looked up? Do I need to reference glassfish docroot/i in i.war for Apex Listener 2.0.1? (I referred to apex install dir as indicated in the installation manual)
    4/ My custom login page starts with this error. Even after I log out of the builder. Is this normal?
    Attempt to save item P101_LANGUAGE in session state during show processing.
    Item protection level indicates "Item may be set when accompanied by a &quot;session&quot; checksum.".
    No checksum was passed in or the checksum passed in would be suitable
    for an item with protection level "Item has no protection.".
    Note: End users get a different error message

  • Upgrade to APEX 4.2.3 apexins_con.sql gets: catconInit: database is not open Unexpected error encountered in catconInit; exiting

    Upgrade to APEX 4.2.3 apexins_con.sql gets Unexpected error encountered in catconInit; exiting
    I am attempting to install/upgrade apex 4.2.3 under Oracle12c in a Multi-Tenant configuration.
    Here are the environmental details
    Windows 7 64 bit
    Apex 4.2.3
    ORCL: CDB$ROOT
    PDBORCL: PDB$SEED
    Here is the current states of the pluggable databases
    SQL> SELECT NAME,OPEN_MODE,TOTAL_SIZE/1024/1024/1024 FROM V$PDBS;
    NAME                           OPEN_MODE  TOTAL_SIZE/1024/1024/1024
    PDB$SEED                       READ ONLY                 .263671875
    PDBORCL                        READ WRITE                .366210938
    SQL>
    This is the command that I am using to re-install/upgrade APEX:
    # remove 4.2.2 installation
    cd M:\apex_4.2.3\apex_4.2.3_en\apex
    sqlplus /@ORCL as sysdba
    @apxremov.sql   <<  this was successful
    quit
    Install 4.2.3 installation
    sqlplus /@ORCL as sysdba
    @apexins_con.sql i10wrk SYSAUX SYSAUX TEMP /i/  << this failed
    The APEX  installation fails immediately with the following message:
    catconInit: database is not open
    Unexpected error encountered in catconInit; exiting
    I cannot determine which database is not open.  Both my CDB$ROOT and PDBORCL are reported as open (READ WRITE Mode).
    Here is my Container database
    SQL>  SELECT SYS_CONTEXT ('USERENV', 'CON_NAME') FROM DUAL;
    SYS_CONTEXT('USERENV','CON_NAME')
    CDB$ROOT
    SQL> select instance_name,status from v$instance;
    INSTANCE_NAME    STATUS
    orcl             OPEN
    SQL>
    Here is the associated Pluggable Database
    sqlplus /@PDBORCL as sysdba
    SQL> select instance_name,status from v$instance;
    INSTANCE_NAME    STATUS
    orcl             OPEN
    SQL> ALTER PLUGGABLE DATABASE PDBORCL OPEN;
    ALTER PLUGGABLE DATABASE PDBORCL OPEN
    ERROR at line 1:
    ORA-65019: pluggable database PDBORCL already open
    I am confused…. Which database is not open?
    The PDB$SEED is open in (READ ONLY) mode, but that is simply the template database.  I don't think that ever needs to be open in (Read Write) mode.

    sbing52,
    I cannot vouch for the specific error that is being returned by catcon.pl, but I would try the following in your situation.
    1. It seems you connect to CDB$ROOT and ran apxremov.sql. This only removed the common APEX option from CDB$ROOT. Your PDB is now in an inconsistent state, since APEX is no longer in the root. I would reconnect to CDB$ROOT and run apxremov_con.sql, make sure you use the one from the 4.2.3 distribution. The one in the ORACLE home will not work.
    2. I would then re-run apexins_con.sql connect to CDB$ROOT. Also, you need to pass the proper parameters. Why are you passing i10wrk? You should be invoking it like:
    @apexins_con.sql SYSAUX SYSAUX TEMP /i/
    Regards,
    Jason

  • Authentication error after upgrade to APEX 4.2

    Hi,
    After the upgrade to Apex 4.2, I started to receive an error when trying to run the application.
    ERROR: "There is no authentication configured for this application. ORA-01403: no data found".
    I checked and double checked the authentication options. Everything seemed fine. Tried several tricks. No success.
    Then I didn't bother much. I just recreated the application (that is - created a copy of the application) and got rid of this error. Then deleted the application that wouldn't run and kept the new one. Everything works fine now.
    Was there an option that I had missed? What would have been a "polite" way to get rid of this error?
    M
    Edited by: user1671420 on 2.09.2012 13:11
    Edited by: user1671420 on 2.09.2012 22:55

    Hi,
    I had the same issue after upgrade, using a Custom Authentication Scheme (LDAP).
    Debugging and adding logs indicated that the session was being processed correctly, but to "nobody", therefore raising the "Invalid Login Crednetials" message.
    At a total loss for ideas, I started changing URL parameters on this authentication scheme (after having deleted the login page, recreating and even re-importing, changing processes etc etc), applied the changes and it worked.
    Not fully understanding why slight changes worked, I reverted the changes, clicked on "Apply Changes" and it worked as well.
    This led me to believe that the actual Authentication Scheme was decompiled, or needed to be re-validated somehow. I tested this on other applications that use the same scheme (but were also inaccessible), and it worked.
    Edit Application --> Edit Application Properties --> Security Tab --> Define Authentication Schemes --> "Edit Current Scheme" --> Don't make any changes, Simply click on "Apply Changes"
    I hope this helps anyone who might be having the same issue.
    Kindly,
    James

  • Importing a page giving errors after upgrade to APEX 4.2.3

    Good afternoon
    We upgraded from APEX 4.2.1.  Now we cannot import a page get error:
    Execution of the statement was unsuccessful. ORA-20001: Error creating page name="Dashboard" id="56" ORA-02291: integrity constraint (APEX_040200.WWV_FLOW_STEP_UI_FK) violated - parent key not found
    Is there anybody that found a workaround?

    There is a patch that is available that fixes exactly this problem.. see this thread for more info
    Apex 4.2.2 via Apex Listener 2 - returns blank screen
    There is no other way to "fix it"

  • Cannot login after upgrading to Apex 3.1.2

    I have installed the oracle-xe-10.2.1-1.0.i386.rpm onto a RedHat server using
    ]# rpm -ivh oracle-xe-10.2.0.1-1.0.i386.rpm
    Then I configure the database
    ]# /etc/init.d/oracle-xe configure
    Then I enable remote access
    EXEC DBMS_XDB.SETLISTENERLOCALACCESS (FALSE);
    This appears to work properly and I can log into the Apex page at http://server:8080/apex/apex_admin
    After this install I'm attempting to upgrade to Apex 3.1.2 and have attempted this several times. Each time, the result is that I can bring up the web page, but cannot authenticate. All that I see is "error on page" at the bottom left of the window. (IE6 or Firefox).
    To complete the upgrade I do the following.
    ]$ sqlplus /nolog
    SQL> @apexins SYSAUX SYSAUX TEMP /i/
    After the install runs the last few lines are
    Upgrade completed successfully no errors encountered.
    -- Upgrade is complete -----------------------------------------
    timing for: Upgrade
    Elapsed: 00:00:34.60
    ...End of install if runtime install
    ...create null.sql
    timing for: Development Installation
    Elapsed: 00:18:18.29
    not spooling currently
    Disconnected from Oracle Database 10g Express Edition Release 10.2.0.1.0 – Production
    I have then stopped and restarted the oracle-xe
    Then I have logged back in with sqlplus / as sysdba
    and run
    @apxxepwd.sql or @apxchpwd (different attempts at the install)
    After all of this appearing to run successfully, I cannot log into either the basic apex screen or the apex admin screen.
    When it has failed, I have uninstalled the RPM and deleted the remanant folder.
    Then re-installed from scratch.
    I'm new to oracle, and any assistance would be appreciated.

    Thank you for your reply. I get the followin errors while trying your suggestions.
    The password change appears to be successful.
    SQL> @apxldimg.sql /opt/oracle-instdir/apex
    PL/SQL procedure successfully completed.
    old 1: create directory APEX_IMAGES as '&1/apex/images'
    new 1: create directory APEX_IMAGES as '/opt/oracle-instdir/apex/apex/images'
    Directory created.
    declare
    ERROR at line 1:
    ORA-22288: file or LOB operation FILEOPEN failed
    No such file or directory
    ORA-06512: at "SYS.DBMS_LOB", line 523
    ORA-06512: at "SYS.XMLTYPE", line 287
    ORA-06512: at line 15
    PL/SQL procedure successfully completed.
    Commit complete.
    timing for: Load Images
    Elapsed: 00:00:00.03
    Directory dropped.
    SQL>

  • 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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Problem Upgrading to Apex 3.1 on XE

    I am running into a problem upgrading Apex to 3.1 on Oracle XE.
    Hardware and Software:
    Database: Oracle Database 10g Express Edition Release 10.2.0.1.0
    PL/SQL Web Toolkit Version: 10.1.2.0.4
    Host O/S: MS Windows XP Professional Version 2002 SP2
    Host Hardware: AMD Athlon 64 Processor, 2.2 GHz, 1.87 GB RAM
    Background:
    This is a lab host. I am working through the full installation process so that I can set up XE and Apex on development and production hosts, the end in mind being to develop a simple application using XE/Apex instead of Access 2003, which is used heavily in this shop.
    It seems to me that upgrading to Apex 3.1 would be a good thing to do up front instead of developing in the version which ships with XE (2.1, I believe) and performing the upgrade later.
    I installed XE going with full defaults. Nothing at all tricky. I was able to connect to http://localhost:8080/apex without any trouble and log in as system.
    I then followed these Apex upgrade instructions, very carefully:
    http://www.oracle.com/technology/products/database/application_express/html/3.1_and_xe.html
    After I ran into trouble (see below), I reviewed this post and used it to double-check my work:
    How to upgrade to Apex 3.1
    I have worked through this a number of times, each time ending up with the same error.
    The Problem...
    After the upgrade, when I navigate to http://localhost:8080/apex, I receive the following error:
    wwv_flow.app_not_found_footer_err
    wwv_flow.err wwv_flow.app_not_found_err
    OK
    I reviewed this posting, which suggests that I upgrade my PL/SQL Web Toolkit:
    apex 3.0 error wwv_flow.app_not_found_footer_err after new installation
    I am perfectly willing to try this, but I am not sure how to obtain the latest correct version of the web toolkit for this particular version of the database. Any tips on where I might find this?
    I also note that the posting says there should be 10 SQL files in the apex/builder directory. I only have 5, but I just downloaded this zip file a few days ago and assume this is the correct number of files. If it isn't, where could I find the correct zip?
    Any other suggestions about the root cause of this issue would be appreciated.
    Thanks!

    Well, like Sherlock Holmes said, "when you have elminated the impossible, whatever remains, no matter how improbable, must be the truth." Or, something like that.
    Thanks Joel, it was the files. I examined the zip file I originally downloaded and, sure enough, there were 10 files. I extracted it again and, for some reason, this time it only pulled one of the SQL files out, not even five as it did the first time. In addition, it also skipped about half the language folders.
    To get it work, I used the windows built-in zip to open the file, navigated to the apex/builder folder, selected all of the SQL files and language folders, then copied and pasted them into c:\apex\builder.
    I then restored the database, ran the install again, and everything worked just fine: I can access http://localhost:8080/apex/apex_admin and log in.
    I'm not sure what the issue is, a problem with the zip file or (ok, more likely) a problem with the built-in windows zip tool. I used 7-zip (www.7-zip.org) to extract the file on my workstation and all 10 files and 9 language folders came out just fine.
    The bottom line is, it works now, thanks again for the help.
    -Tom
    PS - I did not install the web toolkit upgrade.

  • Popup LOV returns not found on this server after upgrading to APEX 3.2

    The Popup Key LOV (Displays description, returns key value) does not work after upgrading to APEX 3.2 from APEX 3.0.
    Don't now if the character set is relevant.
    The database character set on APEX 3.0 was:
    NLS_CHARACTERSET: WE8MSWIN1252
    DAD CHARACTERSET: WINDOWS-1252
    APEX 3.2:
    NLS_CHARACTERSET:     AL32UTF8
    DAD CHARACTERSET:     UTF-8
    When clicking on the popup the message is "The requested URL /pls/apex31mb/wwv_flow_utilities.gen_popup_list was not found on this server.".
    This error applies for both Firefox and IE.

    Can't reproduce the error on apex.oracle.com, the popup works fine.
    The only difference I notice on the environments is the database version (our: 10g, oracle.apex.com: 11g), but I can't see this have any influence.

  • Upgraded from APEX 3.1 to APEX 4.0.2, Interactive reports broken

    I just recently upgraded from APEX 3.1 to APEX 4.0.2.
    Am using IE 8.
    Now whenever I click on a column header in an interactive reports I get a javascript error:
    Message: Expected ')'
    Line: 1
    Char: 40984
    Code: 0
    URI: http://patchx:8080/i/javascript/apex_4_0.js
    Am at my wits end on this one.
    I can't see anybody else who has hit this error.
    The demo application works okay.
    I set up an interactive report with the same properties as the demo app, but i still get the error.
    Any clues?

    AHA, I just figured out what is making this happen.
    I have a custom authorization scheme which calls a PLSQL function.
    I had set the authorization scheme to "Once Per Page View".
    This was causing the error to happen, although I still don't know why.
    Unfortunately it is a problem because I need to authorize on each page.
    This is because my plsql function must allow the login page authorization so we can capture the username to check against permissions. So I autmatically return true on the login page. But that means anybody can get in, because that is the once per session authorization as specified.

  • 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?

Maybe you are looking for