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

apex_application.g_f0x array processing in Oracle 12

By
If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one: then you disable the " Escape special characters " property and the result is an updatable multirecord form. That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for
Post a Comment
Read more

Filtering in the APEX Interactive Grid

By
Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good old Employ
1 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