APEX Static Files not served, ORDS returns 404 or why reading logfiles help

On a recent installation we had problems serving APEX static files (application and workspace), they would always report a 404 not found back from ORDS.

Of course I checked all required DB users and the ORDS config files, but couldn’t find anything obvious. Also no REST service defined in APEX would work.

By looking into the tomcat logfile I found a strange error:

WARNING: ORA-04063: view "ORDS_METADATA.UNIFIED_POOL_CONFIG" has errors

with a whole Java Exception stack behind it.

At some other place in the logfile ORDS actually recommends what to do:

Please run the following command and restart Oracle REST Data Services:
java -jar ords.war validate --database apex

And then I realized what happened: I had APEX 18.1 and ORDS 18.2 installed on this server, but then reverted back to APEX 5.1.4. Of course we need to tell ORDS that something changed.

So after running java -jar ords.war validate –database apex and restarting tomcat everything worked just fine.

This just shows how important it is to actually read logfiles.

 

6 thoughts on “APEX Static Files not served, ORDS returns 404 or why reading logfiles help

  1. May i add me two cents?
    We should run java -jar ords.war after every upgrade of ords.war
    It will renew DB scheme of ords.

  2. Great,
    Thank you, I met this issue with APEX19 and it solved with this command.

  3. Thank you very much, I have been looking for how to solve the issue with the static work files not showing after install ords. Your solution works !!

  4. I had the same issue but could not execute the ords.war with the option because I don’t have access to the SYS account. I found that the root cause of my problem was in the ORDS installation rather than on the database side. We use APEX so I did not configure ORDS for REST when i installed it. I only had apex.xml in webapps/ords/conf, which contains the APEX_PUBLIC_USER credentials. REST requires APEX_REST_PUBLIC_USER and possibly APEX_LISTENER. The credentials for those are in apex_rt.xml and apex_al.xml, respectively. After adding these xml files, the static workspace and application files became accessible in APEX.

    Note: the APEX static files are not the same thing as workspace/application static files. The former are a standard part of the APEX installation and must be copied under ORDS during the installation. The latter are custom files that are uploaded for use by APEX apps by app developers such as custom images and JavaScript. Web search results tend to mix the two issues.

  5. It solved my issue on when downgrade form 19.2 to 19.1,
    Thank you very much.

Leave a Reply

Your email address will not be published. Required fields are marked *