This document will keep an up to date version of my personal Oracle dockerized development environment. The main goal is to have one Oracle database with multiple versions of APEX installed.
This is achieved using Oracle 12c containers (not to be confused with Docker containers). If you're not too familiar with Oracle 12c containers I highly recommend reading this article which covers Container Databases (CDB) and Pluggable Databases (PDB).
- Known Issues and Future Improvements
- References
- Background
- Setup
- Docker Containers
- Useful Commands
- Common Problems
- Use Oracle's official ORDS image from the Container Registry
The following articles and all my scripts are a result of a combination of the code found in the links.
- APEX and ORDS up and running in....2 steps! by Joel Kallman
- Dockerize your APEX development environment by Roel Hartman
- Oracle Database 12c now available on Docker by Maria Colgan
- All my scripts are Linux / MacOS focused. If you use a Windows machine you'll need to translate
- I specifically made reference to "your laptop" to emphasize what was run "on your machine" vs "in a docker container"
- I use SQLcl instead of SQLplus on my laptop. I've also renamed the default command
sql
tosqlcl
. You can usesqlplus
or follow my sqlcl install instructions.
The following port mapping will be used. To help remember the DB version, the database port ends in its version number 122
for 12.2
. Likewise, the ORDS ports end in the APEX version they link to ex: 514
for 5.1.4
, 1810
for 18.1.0
.
Container | Container Port | Laptop Port | Description |
---|---|---|---|
oracle |
1521 |
32122 |
TNS listener for Oracle 12.2 |
ords-504 |
8080 |
32504 |
ORDS for APEX 5.0.4 |
ords-514 |
8080 |
32514 |
ORDS for APEX 5.1.4 |
ords-1810 |
8080 |
31810 |
ORDS for APEX 18.1.0 |
Since this setup is for my own development environment (and to keep things simple) the following passwords will be used for the setup
Container | Username | Password | Description |
---|---|---|---|
oracle |
sys |
Oradoc_db1 |
All sys passwords for all PDBs will be the same |
oracle |
admin |
Oradoc_db1 |
Workspace Internal for all APEX admin |
Due to licensing restrictions I can't host/provide these files in Github or elsewhere. As such you'll need to download them manually. Download the following files and store them in your ~/Downloads
folder:
Application | Description |
---|---|
APEX 18.1 | At the time of writing, 18.1 is the most recent version. |
APEX 5.1.4 | Find it in the APEX archive page. |
APEX 5.0.4 | Find it in the APEX archive page. |
ORDS 18.1.1 | At the time of writing ORDS 18.1.1 was the most recent version. |
We'll assume that the folder structure below is setup. A script is provided later on to create this.
Path | Description |
---|---|
~/docker |
root |
~/docker/apex |
APEX installation files and images for each version. 2 versions of APEX are included in this example but more can easily be added |
~/docker/apex/18.1.0 |
APEX 18.1.0 installation files |
~/docker/apex/5.1.4 |
APEX 5.1.4 installation files |
~/docker/apex/5.0.4 |
APEX 5.0.4 installation files |
~/docker/oracle |
Oracle 12.2 data files |
~/docker/ords |
ORDS Dockerfile (to build ORDS image) |
~/docker/tmp |
Temp folder |
To work with Oracle's licensing for docker (and to avoid manually building images yourself) you'll need to login to the container-registry.oracle.com and use your Oracle Technology Network (OTN) login and register.
One logged in go to Database > Enterprise
and read the license agreement. If you agree to the Terms and Conditions click the Accept button.
The following steps only ever need to be done once.
The following script will create the directory structure as mentioned above
mkdir ~/docker
cd ~/docker
mkdir apex
mkdir oracle
mkdir ords
Copy the files from the ~/Downloads
folder to the appropriate ~/docker
folder and unzip
# *** APEX ***
cd ~/docker/apex
cp ~/Downloads/apex*.zip .
# Unzip
unzip apex_18.1.zip
mv apex 18.1.0
unzip apex_5.1.4.zip
mv apex 5.1.4
unzip apex_5.0.4.zip
mv apex 5.0.4
# ORDS will be dealt in the ORDS image section
In order for the containers to “talk” to each other we need to setup a Docker network and associate all the containers on this network. Containers can reference each other by their respective container names. When referencing another container on the same Docker network the port used is the container’s native port not the mapped port on your laptop.
docker network create oracle_network
# Other docker network commands (don't need to run them as part of install)
# Connect and existing container to a docker network
# docker network connect <network name> <container name>
# View a network and connected containers
# In this example "oracle_network" is the network we're interested in
docker network inspect oracle_network
Two images are required to get the setup working: Oracle and ORDS.
If you haven't already done so already read above about the container-registry.oracle.com
. You won't be able to pull the container until you agree to the Terms and Conditions.
# *** NOTE: container-register.oracle.com is slow
# Instead you can try the following URLs in its place:
# container-registry-phx.oracle.com
# container-registry-ash.oracle.com
#
# Login to Oracle's container registry
docker login container-registry.oracle.com
# They're various docker 12c images. To help reduce the number (and size) of images on my laptop I only needed the 12.2 version
# This will take a while to run as the image size is around 3.5 GB
# Note currently the registry server is slow so you may have to wait a while for the image to download
docker pull container-registry.oracle.com/database/enterprise:12.2.0.1
Oracle has scripts available to build an ORDS image. At the time of writing (11-Nov-2017) there's an issue with the script (Issue #646) that prevents me from using it. I suspect that Oracle will include a pre-built image on their container registry in the future so I'll update the section with their image when/if it becomes available. In the mean time the image will be built using another script.
Important: I've created a separate ORDS Docker Image repo. Since it's being actively updated and to avoid duplication of documentation please refer to the repo to build your ORDS Docker image. Go through it now to create your ORDS Docker image.
At this point you should see the following (or similar) output when running docker images
docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
ords 18.1.1 a735271f7bf5 17 seconds ago 537MB
container-registry.oracle.com/database/enterprise 12.2.0.1 12a359cd0528 2 months ago 3.44GB
Now that the setup is complete we can create all the Docker containers
Adding the -e TZ
option will set the appropriate timezone for the OS and the database. A full list of timezones can be found here. If excluded it will default to UTC.
docker run -d -it \
--name oracle \
-p 32122:1521 \
-e TZ=America/Edmonton \
--network=oracle_network \
-v ~/docker/oracle:/ORCL \
-v ~/docker/apex:/tmp/apex \
container-registry.oracle.com/database/enterprise:12.2.0.1
# Running docker ps will result in:
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
6b4d96d63cf5 container-registry.oracle.com/database/enterprise:12.2.0.1 "/bin/sh -c '/bin/..." 4 seconds ago Up 5 seconds (health: starting) 5500/tcp, 0.0.0.0:32112->1521/tcp oracle
# More specifically if you need to create a script around this
# docker inspect --format="{{.State.Health.Status}}" oracle
# Will give you precise information about the status
You'll need to run docker ps
several times until the status is (healthy)
. Before you see (healthy)
, the status will be (unhealthy)
. This is normal. You will be able to monitor the ~/docker/oracle
directory increases in size.
You can follow the install by running docker logs oracle
Starting in Oracle 12.2 the database should not come pre-installed with APEX. Joel Kallman wrote an article about why this. For some reason the container from Oracle comes with APEX 5.0.4 installed in the CDB. It must first be removed.
# On your laptop:
docker exec -it oracle bash -c "source /home/oracle/.bashrc; bash"
# You should now be in the Oracle Docker container
cd /tmp/apex/5.0.4
sqlplus sys/Oradoc_db1@localhost/orclcdb.localdomain as sysdba
@apxremov.sql
-- Exit sqlplus
exit
# Exit bash
exit
The Oracle container database will come with a default PDB (ORCLPDB1
). We'll leave it alone and create new PDBs for each version of APEX.
Note I've included the APEX installs in these sections since they're required for the ORDS containers.
On your laptop connect to the database: sqlcl sys/Oradoc_db1@localhost:32122:orclcdb as sysdba
-- Create 18.1.0 PDB
create pluggable database orclpdb1810 admin user pdb_adm identified by Oradoc_db1
file_name_convert=('/u02/app/oracle/oradata/ORCL/pdbseed/','/u02/app/oracle/oradata/ORCL/ORCLPDB1810/');
-- Create 5.1.4 PDB
create pluggable database orclpdb514 admin user pdb_adm identified by Oradoc_db1
file_name_convert=('/u02/app/oracle/oradata/ORCL/pdbseed/','/u02/app/oracle/oradata/ORCL/ORCLPDB514/');
-- Create 5.0.4 PDB
create pluggable database orclpdb504 admin user pdb_adm identified by Oradoc_db1
file_name_convert=('/u02/app/oracle/oradata/ORCL/pdbseed/','/u02/app/oracle/oradata/ORCL/ORCLPDB504/');
-- Running the following query will show the newly created PDBs but they are not open for Read Write:
select vp.name, vp.open_mode
from v$pdbs vp;
NAME OPEN_MODE
PDB$SEED READ WRITE
ORCLPDB1 READ WRITE
ORCLPDB514 MOUNTED
ORCLPDB504 MOUNTED
ORCLPDB1810 MOUNTED
-- Open the PDB
alter pluggable database orclpdb1810 open read write;
alter pluggable database orclpdb514 open read write;
alter pluggable database orclpdb504 open read write;
-- If nothing is changed the PDBs won't be loaded on boot.
-- They're a few ways to do this
-- See for reference https://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:9531671900346425939
-- alter pluggable database pdb_name save state;
-- alter pluggable database all save state;
-- alter pluggable database all except pdb$seed open read write
alter pluggable database all save state;
-- Exit sqlcl
exit
# On your laptop
docker exec -it oracle bash -c "source /home/oracle/.bashrc; bash"
# You should now be in the Oracle Docker container
cd /tmp/apex/18.1.0
sqlplus sys/Oradoc_db1@localhost/orclpdb1810.localdomain as sysdba
@apexins.sql SYSAUX SYSAUX TEMP /i/
-- APEX REST configuration
@apex_rest_config_core.sql oracle oracle
-- Required for ORDS install
alter user apex_public_user identified by oracle account unlock;
-- From Joels blog: http://joelkallman.blogspot.ca/2017/05/apex-and-ords-up-and-running-in2-steps.html
declare
l_acl_path varchar2(4000);
l_apex_schema varchar2(100);
begin
for c1 in (select schema
from sys.dba_registry
where comp_id = 'APEX') loop
l_apex_schema := c1.schema;
end loop;
sys.dbms_network_acl_admin.append_host_ace(
host => '*',
ace => xs$ace_type(privilege_list => xs$name_list('connect'),
principal_name => l_apex_schema,
principal_type => xs_acl.ptype_db));
commit;
end;
/
-- Setup APEX Admin password
begin
apex_util.set_security_group_id( 10 );
apex_util.create_user(
p_user_name => 'ADMIN',
p_email_address => '[email protected]',
p_web_password => 'Oradoc_db1',
p_developer_privs => 'ADMIN',
p_change_password_on_first_use => 'N');
apex_util.set_security_group_id( null );
commit;
end;
/
-- Exit SQL
exit
# You can now exit bash on the container
exit
# On your laptop
docker exec -it oracle bash -c "source /home/oracle/.bashrc; bash"
# You should now be in the Oracle Docker container
cd /tmp/apex/5.1.4
sqlplus sys/Oradoc_db1@localhost/orclpdb514.localdomain as sysdba
@apexins.sql SYSAUX SYSAUX TEMP /i/
-- APEX REST configuration
@apex_rest_config_core.sql oracle oracle
-- Required for ORDS install
alter user apex_public_user identified by oracle account unlock;
-- From Joels blog: http://joelkallman.blogspot.ca/2017/05/apex-and-ords-up-and-running-in2-steps.html
declare
l_acl_path varchar2(4000);
l_apex_schema varchar2(100);
begin
for c1 in (select schema
from sys.dba_registry
where comp_id = 'APEX') loop
l_apex_schema := c1.schema;
end loop;
sys.dbms_network_acl_admin.append_host_ace(
host => '*',
ace => xs$ace_type(privilege_list => xs$name_list('connect'),
principal_name => l_apex_schema,
principal_type => xs_acl.ptype_db));
commit;
end;
/
-- Setup APEX Admin password
begin
apex_util.set_security_group_id( 10 );
apex_util.create_user(
p_user_name => 'ADMIN',
p_email_address => '[email protected]',
p_web_password => 'Oradoc_db1',
p_developer_privs => 'ADMIN',
p_change_password_on_first_use => 'N');
apex_util.set_security_group_id( null );
commit;
end;
/
-- Exit SQL
exit
# You can now exit bash on the container
exit
# On your laptop
docker exec -it oracle bash -c "source /home/oracle/.bashrc; bash"
# You should now be in the Oracle Docker container
cd /tmp/apex/5.0.4
sqlplus sys/Oradoc_db1@localhost/orclpdb504.localdomain as sysdba
@apexins.sql SYSAUX SYSAUX TEMP /i/
-- APEX REST configuration
-- For APEX 5.0.4 I get an error when running the statement below
-- Just login and re-run
@apex_rest_config_core.sql oracle oracle
-- Required for ORDS install
alter user apex_public_user identified by oracle account unlock;
-- From Joels blog: http://joelkallman.blogspot.ca/2017/05/apex-and-ords-up-and-running-in2-steps.html
declare
l_acl_path varchar2(4000);
l_apex_schema varchar2(100);
begin
for c1 in (select schema
from sys.dba_registry
where comp_id = 'APEX') loop
l_apex_schema := c1.schema;
end loop;
sys.dbms_network_acl_admin.append_host_ace(
host => '*',
ace => xs$ace_type(privilege_list => xs$name_list('connect'),
principal_name => l_apex_schema,
principal_type => xs_acl.ptype_db));
commit;
end;
/
-- Setup APEX Admin password
begin
apex_util.set_security_group_id( 10 );
apex_util.create_user(
p_user_name => 'ADMIN',
p_email_address => '[email protected]',
p_web_password => 'Oradoc_db1',
p_developer_privs => 'ADMIN',
p_change_password_on_first_use => 'N');
apex_util.set_security_group_id( null );
commit;
end;
/
-- Exit SQL
exit
# You can now exit bash on the container
exit
Each APEX PDB should have an associated ORDS container. A few notes about each ORDS container:
- Instead of naming the ORDS containers with their version number, they'll be named to reference the corresponding APEX version (example
ords-504
will be used to reference the PDB hosing APEX5.0.4
). You may want to alter your naming scheme if you plan to test with multiple versions of ORDS. - Important: Refer to Docker ORDS documentation on how to run each ORDS setup. Only modifications will be mentioned in each section below.
-- Note: THIS IS NOT A COMPLETE docker run command
-- Please reference https://github.com/martindsouza/docker-ords for full docker run commands
-- The purpose of this is to highlight the passwords and connection strings to use for each PDB
docker run ...
--name ords-1810 \
--network=oracle_network \
-e TZ=America/Edmonton \
-e DB_HOSTNAME=oracle \
-e DB_PORT=1521 \
-e DB_SERVICENAME=orclpdb1810.localdomain \
-e APEX_PUBLIC_USER_PASS=oracle \
-e APEX_LISTENER_PASS=oracle \
-e APEX_REST_PASS=oracle \
-e ORDS_PASS=oracle \
-e SYS_PASS=Oradoc_db1 \
...
You should now be able to go to APEX via http://localhost:31810/ords
-- Note: THIS IS NOT A COMPLETE docker run command
-- Please reference https://github.com/martindsouza/docker-ords for full docker run commands
-- The purpose of this is to highlight the passwords and connection strings to use for each PDB
docker run ...
--name ords-514 \
--network=oracle_network \
-e TZ=America/Edmonton \
-e DB_HOSTNAME=oracle \
-e DB_PORT=1521 \
-e DB_SERVICENAME=orclpdb514.localdomain \
-e APEX_PUBLIC_USER_PASS=oracle \
-e APEX_LISTENER_PASS=oracle \
-e APEX_REST_PASS=oracle \
-e ORDS_PASS=oracle \
-e SYS_PASS=Oradoc_db1 \
...
You should now be able to go to APEX via http://localhost:32514/ords
-- Note: THIS IS NOT A COMPLETE docker run command
-- Please reference https://github.com/martindsouza/docker-ords for full docker run commands
-- The purpose of this is to highlight the passwords and connection strings to use for each PDB
docker run ...
--name ords-504 \
...
--network=oracle_network \
-e TZ=America/Edmonton \
-e DB_HOSTNAME=oracle \
-e DB_PORT=1521 \
-e DB_SERVICENAME=orclpdb504.localdomain \
-e APEX_PUBLIC_USER_PASS=oracle \
-e APEX_LISTENER_PASS=oracle \
-e APEX_REST_PASS=oracle \
-e ORDS_PASS=oracle \
-e SYS_PASS=Oradoc_db1 \
...
You should now be able to go to APEX via http://localhost:32504/ords
When running ORDS containers for the first time they'll run in the foreground as the -d
(detached
) option was not provided (see Docker documentation for more info on this option). It's good to have it run in the foreground as it's easy to spot any issues with ORDS connecting to the database.
To stop stop the container hit ctrl+c
. To restart the ORDS container run docker start ords-1810
.
This section covers some useful commands for Docker and managing Oracle CDB and PDBs.
To quickly start and stop the docker containers:
# Start
docker start oracle
docker start ords-504
docker start ords-514
docker start ords-1810
# Stop
docker stop -t 200 oracle
docker stop -t 200 ords-504
docker stop -t 200 ords-514
docker stop -t 200 ords-1810
# Docker stop conainer with timeout (for Oracle to shutdown properly)
docker stop -t 200 oracle
# Docker stop all containers
docker stop -t 200 $(docker ps)
# Delete all containers
docker rm $(docker ps -aq)
# Delete all images
docker rmi $(docker images -aq)
# View docker logs as run is happening where <name> is the name of the container that is running
docker logs <name>
# Docker Network
# List
docker network ls
# See containers on network
docker network inspect oracle_network
sqlcl sys/Oradoc_db1@localhost:32122:orclcdb as sysdba
sqlcl sys/Oradoc_db1@localhost:32122/orclpdb1.localdomain as sysdba
sqlcl sys/Oradoc_db1@localhost:32122/orclpdb504.localdomain as sysdba
sqlcl sys/Oradoc_db1@localhost:32122/orclpdb514.localdomain as sysdba
sqlcl sys/Oradoc_db1@localhost:32122/orclpdb1810.localdomain as sysdba
# Drop PDB
drop pluggable database orclpdb1810 including datafiles;
drop pluggable database orclpdb514 including datafiles;
drop pluggable database orclpdb504 including datafiles;
# Create tablespace (as PDB DBA)
create tablespace users
datafile 'users-1810.dat'
size 100m
autoextend on
next 20m
online
;
# Create user (as sys)
-- Create account to develop with
define new_user = 'martin'
create user &new_user. identified by &new_user. container = current;
grant connect, resource, create job, create view, create any context to &new_user;
alter user &new_user quota unlimited on users;
alter user &new_user default tablespace users;
Using SQLcl you can create the dept
and emp
table your schema using the following script:
@https://raw.githubusercontent.com/OraOpenSource/OXAR/master/oracle/emp_dept.sql
If you get issues from the docker logs oracle
command such as:
ls: cannot open directory /ORCL: Permission denied
# or
mkdir: cannot create directory '/ORCL/u01': Permission denied
It could be due to SE Linux. The following worked for me to get around this:
- Disable SE Linux
- Set
SELINUX=disabled
in/etc/selinux/config
- Reboot host OS (i.e. laptop)
- Running
getenforce
should returnDisabled
orPermissive
- Set
- Change permission on
~/docker/oracle
and~/docker/apex
folders
chmod 777 ~/docker/oracle
chmod 777 ~/docker/apex
- Optional Disable SE Linux on specific folders
chcon -Rt svirt_sandbox_file_t ~/docker/oracle
chcon -Rt svirt_sandbox_file_t ~/docker/apex