Skip to content

FAQ

Why uc-local-apex-dev instead of other docker-compose files?

Section titled “Why uc-local-apex-dev instead of other docker-compose files?”

There are many docker-compose files available for running Oracle Database with APEX and ORDS. However, these two factors set uc-local-apex-dev apart:

  • Upgrades: if new versions of APEX, ORDS or the DB are released, I provide migration guides to help you upgrade your environment.
  • Scripts: This project includes many scripts to help you with common tasks like creating users, backing up the database, testing install scripts, etc. These scripts are designed to be easy to use and automate common development tasks.

Yes. A folder named ords-config will be created in the root directory. You can modify the config files there. The changes will be applied on the next restart of the ORDS container.

This is a bit tricky. In the past datafiles were not compatible between versions. This is the reason I added the backup scripts. For the future I want to add a script that will then import everything again.

You can modify the docker-compose.yml file to use a different ORDS version. You can find the available versions in the Oracle container registry.

I will also update the github repository with the latest version of ORDS.

  • You need a valid Oracle support account
  • Go to the APEX Downloads Page
  • Click on Patch Set Bundle
  • Login with your Oracle account and download the zip file
  • Unzip the file
  • Start a terminal in the directory
  • Run the following command:
Terminal window
sql -name local-23ai-sys @catpatch.sql

To update the APEX images (assets):

Terminal window
# make sure you are in the directory of the unzipped patch directory
cp ./images {path_to_your_cloned_repo}/apex-images