ORDS WARNING Cannot find the real static path of

Problem description

You’ve just upgraded ORDS and issued the ords serve command. As ORDS is starting up, you see the following warning (or something like it):

WARNING Cannot find the real static path of https://static.oracle.com/cdn/23.2.0/

How to fix

Easy! In this case, I removed the standalone.static.path property of the ORDS Global configuration settings.

WAIT JUST A MINUTE! This approach was successful because I determined that APEX was NOT previously installed in my database. BUT if APEX IS installed in your database, this approach will most likely not work. Also its a good practice, always back up any configuration file you are modifying BEFORE making any changes.

Removing ORDS configuration settings

You can remove/add/update ORDS configuration settings in two ways:

Manipulating the Global settings.xml file directly, or
Using the ORDS CLI

NOTE: Using the ORDS CLI is the preferred method. I cannot stress this enough.

Whenever an ORDS installation or upgrade displays errors or warnings, go straight to the ORDS upgrade logs. Review the associated log for anything out of place and anything relevant to the warning or error you observed. In this case, the error pointed to two clues:

APEX
“static path”

REMEMBER: When you are troublshooting, you are on a fact-finding mission. You're looking for clues that can help you solve a mystery.

Here, I see that APEX isn’t even installed in my target database. Perhaps Chris was trying to do something with/in APEX in the past and got distracted.

Since it looks like I haven’t installed APEX, I feel comfortable ruling out APEX as the culprit.

More than likely, this is pointing toward user error as the culprit. Perhaps it was some setting that I applied incorrectly. Next, I’ll inspect the Global configuration settings for ORDS. I can do this in two ways:

A visual inspection of the settings.xml file
Or using the ORDS CLI

NOTE: In some cases you may need to  inspect the individual database pool.xml configuration settings as well. That wasn't necessary in this case.

Visual inspection

Immediately, you can see the offending configuration property: standalone.static.path. This property “specifies the path to the folder containing static resources required by APEX.”¹ Since I am reasonably sure that APEX doesn’t exist, nor does any APEX metadata exist in my database, I can test my theory by removing the property from the settings.xml file.

I can do this pretty quickly in a text editor. However, if you are skittish about manipulating these files directly (and rightfully so), then use the ORDS CLI (this is the preferred method anyway).

Updating settings with the ORDS CLI

In this case, you’ll see a fictitious standalone.static.path directory, /123456/abcdef.

You can easily remove this, and other settings with the delete option.

The command used in this example:

ords config delete standalone.static.path

Once you’ve made the change, close out your Terminal session and start a new one. Closing out your session and restarting with a new one is good practice to ensure that your Terminal session recognizes any configuration changes you’ve made.

I next issued the ords serve command and ORDS started up with no problem.

And that is how we fixed this warning in this oddly specific scenario. I hope this helped!

And one more thing

You may have noticed I’m on ORDS Version 24.4. That is because I was using a pre-release version that will be available when this post is published. So, if you haven’t done so yet, download the latest ORDS here.

READ the release notes too! This release brings a lot of changes and some fixes too 😍

Follow

And don’t forget to follow, like, subscribe, share, taunt, troll, or stalk me!

See Table C-1 in the ORDS Installation and Configuration Guide. ↩︎