SecureAnyCloud
Deployment guide

Oracle DB 11g Enterprise on Linux

Overview

Oracle Database 11g Enterprise Edition is a full-featured relational database management system for enterprise workloads. It offers advanced capabilities such as partitioning, OLAP, data mining and Real Application Testing. This guide covers deploying and configuring the SecureAnyCloud Oracle Database 11g Enterprise Edition AMI from AWS Marketplace on Linux.

What you get:

  • Oracle Database 11g Enterprise Edition 11.2.0.4 (64-bit) installed at /u01
  • A preconfigured ORCL sample database, ready to start
  • Oracle Listener preconfigured on port 1521
  • A dedicated oracle OS user with environment scripts
  • Helper scripts for starting and stopping the database and listener
  • Randomly generated SYSTEM user credentials
  • An OS package update script that keeps the system current
  • AWS CLI v2 for AWS service integration
  • Systems Manager Agent (SSM) for remote management
  • CloudWatch Agent for monitoring
  • Latest security patches applied at build time
  • 24/7 SecureAnyCloud support with a guaranteed 24-hour response SLA

Prerequisites

Before you launch this AMI, make sure you have:

  • An active AWS account
  • An active subscription to the Oracle Database 11g Enterprise listing on AWS Marketplace
  • An EC2 key pair for SSH access
  • Familiarity with EC2 instance management and SSH

Recommended instance type: m5.large (2 vCPU, 8 GB RAM) or larger. The minimum requirements are 1 vCPU, 1 GB RAM and 20 GB disk space. Oracle Database benefits significantly from additional memory for production workloads.

1

Launch the AMI

  • Go to AWS Marketplace and search for "Oracle Database 11g Enterprise SecureAnyCloud".
  • Click Continue to Subscribe, accept the terms, then click Continue to Configuration.
  • Select your preferred Region and Software Version.
  • Click Continue to Launch.
  • Choose Launch through EC2 for full control over the instance configuration.
  • Select your instance type (m5.large is recommended).
  • Configure storage with a minimum of 20 GB gp3 for the root volume, plus the dedicated /u01 Oracle volume.
  • Configure your Security Group with these inbound rules:
    • Port 22, protocol TCP, source your IP, for SSH access
    • Port 1521, protocol TCP, source your IP, for the Oracle Database Listener
  • Select your EC2 key pair and launch the instance.

Important: Restrict port 1521 to trusted application servers or your IP only. Do not open the Oracle Listener port to the public internet.

2

Connect via SSH

When your instance is running and has passed both status checks (2/2), connect over SSH:

ssh -i your-key.pem ec2-user@<public-ip-address>

To switch to the root user, run:

sudo su -

Important: Wait for the EC2 instance to reach 2/2 successful status checks before you connect. Early connection attempts can return permission denied errors while the instance is still initialising.

3

Switch to the Oracle User

The dedicated oracle OS user owns the Oracle software. Switch to this user to manage the database. Type this command rather than pasting it:

sudo su - oracle

Three scripts are available in the home directory of the oracle user:

  • setEnv.sh sets the Oracle environment variables that utilities such as sqlplus need.
  • start_all.sh starts the ORCL sample database and its associated Oracle Listener.
  • stop_all.sh stops the ORCL sample database and its associated Oracle Listener.
4

Start the Oracle Database and Listener

Run these commands as the oracle user to start the sample database and listener:

cd $HOME . ./start_all.sh

The output looks like this:

LSNRCTL for Linux: Version 11.2.0.4.0 - Production Starting /u01/app/oracle/product/bin/tnslsnr: please wait... TNSLSNR for Linux: Version 11.2.0.4.0 - Production Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ip-x-x-x-x.ec2.internal)(PORT=1521))) The command completed successfully SQL*Plus: Release 11.2.0.4.0 Production Connected to an idle instance. SQL> ORACLE instance started. Database mounted. Database opened.
5

Connect with SQL*Plus

Set the Oracle environment variables, then start SQL*Plus:

cd $HOME . ./setEnv.sh sqlplus / as sysdba

The output looks like this:

SQL*Plus: Release 11.2.0.4.0 Production Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL>

Type EXIT to leave the SQL*Plus session.

6

Connect Remotely with SQL Developer

To connect to the database from an external tool such as SQL Developer, use these connection settings:

  • Database Type: Oracle
  • Authentication Type: Default
  • Username: SYSTEM
  • Password: see the credentials file in the note below
  • Connection Type: Basic
  • Hostname: your instance public IP
  • Port: 1521
  • Service Name: orcl.us.oracle.com

Note: To retrieve the SYSTEM user password, read the randomly generated credentials file at /stage/scripts/oracle-database-credentials.log.

Server Components

  • Oracle Database 11g Enterprise: version 11.2.0.4, installed at /u01

Note: The automatic OS package update script can update component versions on first boot.

Filesystem Layout

  • / (38 GB): root filesystem
  • /boot (2.0 GB): operating system kernel files
  • /u01 (20 GB): Oracle software installation directory

Key Oracle directories:

  • /u01/app/oracle: Oracle base directory
  • /u01/app/oracle/product: Oracle software home
  • /u01/app/oracle/product/network/admin: listener and TNS configuration files
  • /u01/app/oracle/diag: Oracle diagnostic and alert log files

Managing the Oracle Database

You manage the Oracle Database with the shell scripts in the home directory of the oracle user. The database does not use systemd services.

Start the database and listener:

sudo su - oracle cd $HOME . ./start_all.sh

Stop the database and listener:

sudo su - oracle cd $HOME . ./stop_all.sh

Check the listener status:

sudo su - oracle cd $HOME . ./setEnv.sh lsnrctl status

Scripts and Log Files

  • initial_boot_update.sh in /stage/scripts: updates the OS with the latest packages on first boot
  • initial_boot_update.log in /stage/scripts: output log for the boot update script
  • oracle-database-credentials.log in /stage/scripts: Oracle Database SYSTEM user credentials
  • setEnv.sh in /home/oracle: sets the Oracle environment variables for sqlplus and other tools
  • start_all.sh in /home/oracle: starts the ORCL database and Oracle Listener
  • stop_all.sh in /home/oracle: stops the ORCL database and Oracle Listener

On Startup

An OS package update script runs on first boot to bring the image fully up to date. To disable it, remove the script and its crontab entry:

rm -f /stage/scripts/initial_boot_update.sh crontab -e
# Delete the following line, save and exit: @reboot /stage/scripts/initial_boot_update.sh

Troubleshooting

Cannot connect via SSH

  • Verify that the instance has reached 2/2 status checks in the EC2 console.
  • Confirm that your security group allows inbound TCP port 22 from your IP.
  • Make sure you use the correct key pair and connect as ec2-user.

Oracle Listener fails to start

  • Switch to the oracle user with sudo su - oracle.
  • Source the environment with . ./setEnv.sh.
  • Check the listener status with lsnrctl status.
  • Review the listener log at /u01/app/oracle/diag/tnslsnr/<hostname>/listener/alert/log.xml.
  • Verify that no other process uses port 1521 with netstat -tlnp | grep 1521.

Database fails to start

  • Switch to the oracle user and source the environment.
  • Connect to SQL*Plus with sqlplus / as sysdba.
  • Check the instance status with SELECT STATUS FROM V$INSTANCE;.
  • Try starting the database manually with STARTUP;.
  • Review the alert log at /u01/app/oracle/diag/rdbms/orcl/ORCL/trace/alert_ORCL.log.

Cannot connect remotely on port 1521

  • Verify that the Oracle Listener is running with lsnrctl status.
  • Confirm that your security group allows inbound TCP port 1521 from your IP.
  • Test connectivity with telnet <instance-ip> 1521.
  • Check that the listener.ora file references the correct hostname.

Security notes

  • Restrict port access. Allow port 1521 only from trusted application servers or specific IP addresses.
  • Change default passwords. Update the SYSTEM and SYS user passwords immediately after first login.
  • Use strong passwords. Make sure all database user passwords meet complexity requirements.
  • Enable auditing. Configure Oracle Database auditing to track access and changes.
  • Encrypt connections. Configure Oracle Net Services to use SSL/TLS encryption for client connections.
  • Limit OS access. Restrict SSH access to authorised administrators only.
  • Review user privileges. Remove unnecessary grants and follow the principle of least privilege.
  • Keep the system updated. Apply Oracle Critical Patch Updates and OS security patches regularly.

Support

If you have any issues with this product, contact SecureAnyCloud support:

  • Email: sales@secureanycloud.com
  • Website: secureanycloud.com
  • Support hours: 24/7 with a guaranteed 24-hour response SLA

Deploy on AWS

Launch Oracle Database 11g Enterprise with 24/7 support from SecureAnyCloud.

View on Marketplace

Need Help?

Our support team is available 24/7.

sales@secureanycloud.com

Deploy on AWS

Launch Oracle DB 11g Enterprise on Linux with 24/7 support from SecureAnyCloud.

View this image

Need Help?

Our support team is available 24/7.

sales@secureanycloud.com