One piece of feedback I received on my previous blog article was that it would have been even better with a section about Oracle XE. Since that article was already too long, I decided to write a new one.
Table Of Contents
Environment and podman version
I'm running this on Fedora 35 with podman version 3.4.4 with no other modifications than what is described in the next section. Your mileage may vary on other platforms and older versions.
To allow podman to run rootless we need to make a few one-off configuration changes. We can use the same configuration as in the previous article, except for Oracle XE we need somewhat wider ranges of subuids and subgids:
sudo usermod --add-subuids 200000-265535 --add-subgids 200000-265535 $YOUR_USER
(Without this, podman will spit out strange error messages already while pulling the image.)
Based on my own still limited experience with rootless podman, if you have
previously added smaller ranges of subuids and/or subgids for your user, I would
also suggest editing your
/etc/subgid files to remove the
old entries. Just make sure you have subid ranges of 64K.
cat /proc/sys/user/max_user_namespaces sysctl user.max_user_namespaces=15000
Prepare example data
If you want to play with some data, then, as last time, let's use the Sakila schema from JOOQ:
git clone https://github.com/jOOQ/sakila
There is a small issue with the
oracle-sakila-schema.sql file: It contains
forward slash characters ("/") following some of the DDL statements which makes
sqlplus repeat the previously executed statement. This will obviously result
So, let's remove those forward slashes, but keep the ones following PL/SQL
BEGIN ... END; and the ones in
/* ... /* comments:
sed -i 's#^/# #g;s#END;#END;\n/#g;s#^ \*#/*#g' \ sakila/oracle-sakila-db/oracle-sakila-schema.sql
Also, let's make our lives a little easier and add an exit command at the end of those scripts:
echo " exit;" | tee -a sakila/oracle-sakila-db/*.sql
(Yes, this is intentioally on two lines!)
Let's try the "regular" 21c image and mount our example data directory. Beware that some of these are rather large images - e.g. 21 is 3.2GB whereas 11-slim is only 600MB.
podman create -p 1521:1521 --name ora-xe-21 -e ORACLE_PASSWORD=mypass \ -v $(pwd)/sakila/oracle-sakila-db:/mnt/sakila \ docker.io/gvenzl/oracle-xe:21 podman start ora-xe-21
Before you continue, give this a little time to start up properly. You can check
the start-up progres with
podman logs ora-xe-21 which should output 'DATABASE
IS READY TO USE!' and 'Completed: ALTER DATABASE OPEN' after which you should be
able to connect.)
By the way, the above ORACLE_PASSWORD is for the sys and system users. You change this with:
podman exec ora-xe-21 resetPassword some_new_and_better_password
Let's now create a user and grant the necessary privileges:
podman exec -it ora-xe-21 sqlplus system/mypass
ALTER SESSION SET CONTAINER=XEPDB1; CREATE USER SAKILA IDENTIFIED BY SAKILA QUOTA UNLIMITED ON USERS; GRANT CONNECT, RESOURCE, CREATE VIEW TO SAKILA;
exit;or ctrl-D to exit.
ALTER SESSION SET CONTAINERwas introduced in 12c. So, for the 11 images just skip this line, and also leave out "@//localhost/XEPDB1" when connecting through sqlplus.
Finally, to import the sakila schema and data, run these two commands - the
latter redirects its output to
/dev/null as there is quite a lot and printing
it to the terminal will slow down the process:
podman exec -it ora-xe-21 sqlplus -s sakila/SAKILA@//localhost/XEPDB1 \ @/mnt/sakila/oracle-sakila-schema.sql podman exec -it ora-xe-21 /bin/sh -c 'sqlplus -s sakila/SAKILA@//localhost/XEPDB1 \ @/mnt/sakila/oracle-sakila-insert-data.sql > /dev/null 2>&1'
A few example commands to get started (assumes user
help index select table_name from user_tables; connect system/mypass desc actor;
There are other Oracle XE repositories on DockerHub, but the 'gvenzl/oracle-xe' repo seems to have the most downloads (> 1 million) out of the ones that offer versions newer than 11g, and it's also recently updated. I have not tested any of the others.