SecureAnyCloud
Deployment guide

Oracle Database 19c Standard CentOS 7.9

Overview

Oracle Database 19c is the long-term support release of Oracle Database. The Standard Edition provides core relational database functionality for workgroup and departmental applications.

This guide covers the deployment and configuration of the SecureAnyCloud Oracle Database 19c Standard Edition AMI on CentOS 7.9, available on AWS Marketplace. The database is installed at /u01 with a preconfigured sample database, so you can start it as soon as you connect.

What you get:

  • Oracle Database 19c Standard Edition 19.3.0.0.0 (64-bit) on CentOS 7.9, 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 to keep the system current
  • AWS CLI v2 for AWS service integration
  • Systems Manager Agent (SSM) for remote management
  • CloudWatch Agent for monitoring
  • The 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 19c Standard on CentOS 7.9 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 of disk space. Production workloads benefit significantly from additional memory.

1

Launch the AMI

  • Open the AWS Marketplace and search for "Oracle Database 19c Standard CentOS SecureAnyCloud".
  • Choose Continue to Subscribe, accept the terms, then choose Continue to Configuration.
  • Select your preferred Region and Software Version.
  • Choose Continue to Launch.
  • Choose Launch through EC2 for full control over the instance configuration.
  • Select your instance type (m5.large 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, TCP, source: your IP. SSH access.
  • Port 1521, TCP, source: your IP. Oracle Database Listener port.

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

Select your EC2 key pair and launch the instance.

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 produce permission-denied errors while the instance is still initializing.

3

Switch to the Oracle User

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

sudo su - oracle

Three scripts are available in the oracle user's home directory:

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

Start the Oracle Database and Listener

As the oracle user, run these commands to start the sample database and the listener:

cd $HOME . ./start_all.sh

Expected output:

LSNRCTL for Linux: Version 19.0.0.0.0 - Production Starting /u01/app/oracle/product/bin/tnslsnr: please wait... TNSLSNR for Linux: Version 19.0.0.0.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 19.0.0.0.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 and launch SQL*Plus:

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

Expected output:

SQL*Plus: Release 19.0.0.0.0 Production Copyright (c) 1982, 2019, Oracle. All rights reserved. Connected to: Oracle Database 19c Standard Release 19.3.0.0.0 - 64bit Production 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 noted below
  • Connection Type: Basic
  • Hostname: your instance public IP
  • Port: 1521
  • Service Name: orcl.us.oracle.com

Note: The SYSTEM user password is in the randomly generated credentials file at /stage/scripts/oracle-database-credentials.log.

Server Components

  • Oracle Database 19c Standard: version 19.3.0.0.0, installed at /u01

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

Filesystem Layout

Mount points:

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

Key Oracle directories:

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

Managing the Oracle Database

You manage the Oracle Database with the shell scripts in the oracle user's home directory. 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

In /stage/scripts:

  • initial_boot_update.sh: updates the OS with the latest packages on first boot
  • initial_boot_update.log: the output log for the boot update script
  • oracle-database-credentials.log: the Oracle Database SYSTEM user credentials

In /home/oracle:

  • setEnv.sh: sets the Oracle environment variables for sqlplus and other tools
  • start_all.sh: starts the ORCL database and the Oracle Listener
  • stop_all.sh: stops the ORCL database and the Oracle Listener

On Startup

An OS package update script runs on first boot to make sure the image is 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 are using the correct key pair and connecting as ec2-user.

Oracle Listener fails to start

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

Database fails to start

  • Switch to the oracle user and source the environment.
  • Connect with sqlplus: sqlplus / as sysdba
  • Check the instance status: SELECT STATUS FROM V\$INSTANCE;
  • Try starting the database manually: 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: lsnrctl status
  • Confirm that your security group allows inbound TCP port 1521 from your IP.
  • Test connectivity: telnet <instance-ip> 1521
  • Check that the listener.ora file references the correct hostname.

Security Recommendations

  • Restrict port access. Allow port 1521 only from trusted application servers or specific IP addresses.
  • Change the default passwords. Update the SYSTEM and SYS user passwords immediately after your 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 authorized 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 run into an issue 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 19c Standard on CentOS 7.9 with 24/7 support from SecureAnyCloud.

View on Marketplace

Need Help?

Our support team is available 24/7.

sales@secureanycloud.com