Skip to main content

Startup your ORDS container after your Oracle DB container is ready

By
If you are using multiple containers to set up your Oracle Development (or Test or Production) environment - as I described here - you probably ran into the issue that your ORDS container was started before the Database was started up. This results in an ORDS container that is not working - at least not as you need to.

Using Docker Compose you can specify a depends_on option, for instance in the ORDS container configuration you specify (where "oracle" refers to the container that holds the Oracle database) :
depends_on : - oracle
but this only means the ORDS container will start after the "oracle" container has been started. That does not mean the Oracle database inside the container is started and available!

So how do we tell the ORDS to configure itself in one container to wait for the database in another container is ready to use?
Step 1:
Start the Oracle database (container), connect to it and enable a port - in this example 8080 - in the Oracle database 

begin 
 dbms_xdb_config.sethttpport( 8080 ); 
end;
/

This port will become available when the database is up and running.

Step 2:
Get the "wait-for-it" shell script from https://github.com/vishnubob/wait-for-it. In your ORDS Dockerfile copy this in the root of your container and change the Entrypoint from just /config_ords_and_run_catalina.sh to a call to /wait-for-it.sh specifying the Oracle port from step 1. You don't need to use port forwarding as both containers run on the same Docker network and can access each others ports. The example below will wait for max 2 minutes for the Oracle database to start up (if it isn't ready, the rest of the script will not run as it won't make any sense).
COPY ./wait-for-it.sh / RUN chmod +x /*.sh ENTRYPOINT ["/wait-for-it.sh","oracle:8080","--timeout=120","-s","--","/config_ords_and_run_catalina.sh"]
After recreating the image with these changes to the Dockerfile and using Docker Compose to start it all up, the logging of the ORDS container will show the following before proceeding with the configuration:

wait-for-it.sh: waiting 120 seconds for oracle:8080
wait-for-it.sh: oracle:8080 is available after 42 seconds

And that is exactly what we want! Now we defined a proper dependency between our database to be available and our ORDS service.

Note: This will only work properly if your database is already created. If you want this to work when the database has to be created first, you need to add step 1 into your database creation script and need to set the timeout parameter in step 3 to a higher value.

Comments

Post a Comment

Popular posts from this blog

Refresh selected row(s) in an Interactive Grid

By
In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...
Post a Comment
Read more

Stop using validations for checking constraints !

By
 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function ...
Post a Comment
Read more

Caution when using Suppress Change Event on an Interactive Grid Column

By
There are some, maybe rare, use case when you want to set the " Suppress Change Event " switch of a Dynamic Action to " Yes ". Usually that's only necessary when the Dynamic Action is fired On Change  and executes a Set Value  with the same field as a target. There might be a chain of events leading to this or just one. If you forget to set it you'll end up in an endless loop and your browser will choke. That works all fine and as expected with regular Page Items. However ... when you apply this to a column in an Interactive Grid something unexpected happens. When you set the Suppress Change Event of a Dynamic Action that fires on change of a column to Yes , the value of that item seems empty when you leave that field (column)! If you navigate back into that field, the (new) value does show up... You can call it a feature, you can call it a bug, but bottom line it is unexpected and undesired behaviour. The solution is to call the Grid method SetActiv...
Post a Comment
Read more