Skip to main content

Simple, quick and easy steps to run an Oracle Database in your development environment using Docker without overloading your machine

Introduction

In our development environment, besides being easy and fast to use, above all, we need a lightweight version of it to run locally, right? I have tested different Oracle images and this was the option that best work for me. In this post i will show you how you can run the Oracle Database Express Edition version on your local machine quickly and easily and also how to connect to it using Oracle SQL Developer IDE and SQL*Plus.

How to do it

Basically we just need two simple steps to get our Oracle database running on our local environment. First we need to login to the Oracle Container Registry so we can pull the image from it and then we just need to run it in a container.

You can find more information by going to the Oracle Container Registry, under the "Browse Containers", click into Database and next click in the express Repository for the Oracle Database Express Edition.

I am going to skip the docker pull step, because docker run will do it for us automatically if it can not find the image locally.

Use the following command to login into Oracle Container Registry with your username and password from the Oracle web site:
docker login container-registry.oracle.com

Run the following docker run command with the -e flag, short for --env, to already set your password for Orcale SYS user. This way you do not need to change it or look for it later.
docker run -d --name oracle --shm-size=1gb -p 1521:1521 -p 5500:5500 -e ORACLE_PWD=CHOOSE_YOUR_PASSWORD container-registry.oracle.com/database/express:latest

You can also run the Docker command with the -v flag to save the database files on your local machine so you do not loose all of them when the container is removed, but this will also take much more time to start up. 
docker run -d --name oracle --shm-size=1gb -p 1521:1521 -p 5500:5500 -v ~/Documents/oracle:/opt/oracle/oradata -e ORACLE_PWD=CHOOSE_YOUR_PASSWORD container-registry.oracle.com/database/express:latest

You can run the following commands to find out if the Oracle Database is ready to use:
docker logs oracle
If you want to see more information from your logs, you can also run it like this:
docker logs oracle --detail
If you got the "DATABASE IS READY TO USE" message from your docker logs command you have all you need to connect to the database.

Acessing Enterprise Manager

This image also have configured the Express version of the Oracle Enterprise Manager (OEM). As defined in the Orcale web site, "Oracle Enterprise Manager is Oracle’s on-premise management platform that provides a single dashboard to manage all of your Oracle deployments, in your data center or in the cloud.". To access the OEM Express from your browser go to the following address. Don't forget the https part, otherwise it will not work.
https://localhost:5500/em/

If you got lock up from the browser admin page, just type in your keyboard: thisisunsafe, to get in.

One last step we need to do. Enter the right name for the Oracle v$containers. For our version you can enter CDB$ROOT like is shown in the image below. You can read more about it here.
You should see the following Oracle Enterprise Manager Express web page:


Using SQL*Plus

Using docker exec -it command, we can enter in the database container to run SQL commands directly. You just need to run the following docker command:
docker exec -it oracle sqlplus / as sysdba

Note that I have used oracle here because that is my container name. If you give a different name, just change for the one you gave.

Let's see how to create an user using SQL*Plus. Run the previous command to get access to the SQL CLI.

If you try to run the SQL CREATE USER command now you will get the following error:
To solve that we need to alter our session so we can create our new user: 
ALTER SESSION SET "_ORACLE_SCRIPT"=true;
Before we can connect to Oracle Database Express Edition we need to grant our user the CREATE SESSION, otherwise we will get the following error.

GRANT CREATE SESSION TO YOUR_USERNAME;
Let's grant now permission to our new user to create table, views and sequences: 
GRANT CREATE TABLE, CREATE VIEW, CREATE SEQUENCE TO YOUR_USERNAME;

Using SQL Developer

Let's use Oracle SQL Developer IDE to connect to our new Oracle database.

Since our database server is already running and we have created our user and given the necessary permissions to him, you should now been able to connect to your database server using SQL Developer and receive a success status message back when testing your connection.

Note that we entered xe as our System Identifier - SID. This is needed for the Express Edition.

Conclusion

In this post i tried to address the main difficulties and how to solve some problems that you may encounter and mainly, I tried to show how we can quickly run a local instance with an Oracle database for development.

Additional Commands

If you need to stop and remove your container you can simply run:
docker stop oracle && docker rm oracle

Additional Reference

Oracle Container Registry
Oracle Database Express Edition
Oracle SQL Developer
Labels:

Comments

Post a Comment

Popular posts from this blog

Log Aggregation with ELK stack and Spring Boot

Introduction In order to be able to search our logs based on a key/value pattern, we need to prepare our application to log and send information in a structured way to our log aggregation tool. In this article I am going to show you how to send structured log to ElasticSearch using Logstash as a data pipeline tool and how to visualize and filter log information using Kibana. According to a definition from the Wikipedia website: Elasticsearch is a search engine based on the Lucene library. It provides a distributed, multitenant-capable full-text search engine with an HTTP web interface and schema-free JSON documents. According to Elasticsearch platform website , Elasticsearch is the heart of the Elastic stack, which centrally stores your data for lightning fast search. The use of Elasticsearch, Kibana, Beats and Logstash as a search platform is commonly known as the ELK stack. Next we are going to start up Elasticsearch, Kibana and Logstash using docker so we can better underst...
Post a Comment
Read more

How to create a REST API Pagination in Spring Boot with Spring HATEOAS using MongoDB

Introduction In this post we are going to see how we can create a REST API pagination in Spring Boot with Spring HATEOAS and Spring Data MongoDB . For basic queries, we can interact with MongoDB using the MongoRepository interface which is what we are going to use in this tutorial. For more advanced operations like update and aggregations we can use the MongoTemplate class. With Spring applications we start adding the needed dependencies to our pom file if using Maven as our build tool. For this project we are going to use the following dependencies: Spring Web , Spring Data MongoDB and Spring HATEOAS . To quickly create your Spring Boot project with all your dependencies you can go to the Spring Initializr web page. This is how your project should look like: As with any MVC application like Spring there are some minimal layers that we need to create in our application in order to make it accessible like the Controller , Service , Model and Repository layers . For this...
Post a Comment
Read more

Understanding RabbitMQ

Introduction RabbitMQ is a centralized message broker based on the AMQP (Advanced Message Queuing Protocol) protocol, acting as a Middleware between Producers and Consumers of different systems. In a message system, Publishers sends a message to a message broker where messages are consumed some time later by one or more Subscribers. By introducing a message brokeer between systems we are decoupling the sender application from the receiver. In this case the service that is responsible for sending or publishing the message does not need to know about any other service. All it needs to care about is the message and its format. With a message system you send a message to a message broker first and when the consumers or listeners of it become online they can start consuming from the message queue. This means you can keep sending messages without even care if the other application is online or if they had any failures. RabbitMQ Architecture Exchange, queue and bindings are the ...
Post a Comment
Read more