Databases Azure

Oracle Database Client 19c on Oracle Linux 8 on Azure User Guide

| Product: Oracle Database Client 19c on Oracle Linux 8 on Azure

Overview

This guide covers the deployment and configuration of Oracle Database Client 19c on Oracle Linux 8 on Microsoft Azure using cloudimg's pre configured virtual machine image from the Azure Marketplace. Oracle Database Client 19c provides the tools and libraries needed to connect to and manage remote Oracle 19c and earlier database instances. It includes SQL*Plus, Oracle Net, JDBC and OCI drivers, and the full Administrator install set without requiring a database server on the same VM.

What's included in this VM image:

  • Oracle Database Client 19c 19.3.0.0.0 (Administrator install) installed at /u01
  • Dedicated oracle OS user with environment script (setEnv.sh)
  • SQL*Plus, sqlldr, tnsping, expdp, impdp, and the full Oracle Net client utility set
  • Pre seeded tnsnames.ora and sqlnet.ora ready for customer entries
  • System wide /etc/profile.d hook so any future user picks up the client tools
  • OS package update script for keeping the system current
  • Azure Linux Agent (waagent) for Azure integration
  • Cloud init for automated provisioning
  • Latest security patches applied at build time
  • 24/7 cloudimg support with guaranteed 24 hour response SLA

Platform: Microsoft Azure (Gen2 Hyper V) Default user: azureuser Oracle Home: /u01/app/oracle/product/19.3.0/client_1 TNS Admin: /u01/app/oracle/product/19.3.0/client_1/network/admin

Prerequisites

Before deploying this image, ensure you have:

  1. An active Microsoft Azure subscription
  2. Access to the Azure Portal or Azure CLI
  3. An SSH key pair for Linux VM access
  4. The hostname, port, and service name of the Oracle Database you want to connect to
  5. Network connectivity from the new VM to the target Oracle Database (typically TCP 1521 outbound)

Recommended VM Size: Standard_B2s (2 vCPU, 4 GB RAM) or larger. The Oracle Client is a set of libraries and tools rather than a running service, so the minimum requirements are modest: 1 vCPU, 1 GB RAM, and 20 GB disk space.

Step 1: Deploy the Virtual Machine

Option A: Azure Portal

  1. Navigate to the Azure Marketplace and search for "Oracle Database Client 19c Oracle Linux 8 cloudimg"
  2. Select the image and click Create
  3. Configure the basics:
  4. Subscription: Select your Azure subscription
  5. Resource Group: Create new or select existing
  6. Virtual Machine Name: Enter a name for your VM
  7. Region: Select your preferred Azure region
  8. Size: Standard_B2s recommended
  9. Under Administrator Account, select SSH public key and enter your key
  10. Under Inbound Port Rules, allow SSH (port 22) from your trusted IP only
  11. Click Review + Create, then Create

Option B: Azure CLI

az vm create \
  --resource-group myResourceGroup \
  --name my-oracle-client-19c-vm \
  --image cloudimg:oracle-db-19c-client-oel8:default:latest \
  --size Standard_B2s \
  --admin-username azureuser \
  --generate-ssh-keys \
  --public-ip-sku Standard

Important: The Oracle Client makes outbound connections to remote databases on port 1521. You do not need to open port 1521 inbound on this VM. Review your Network Security Group and route table to confirm the VM can reach your target Oracle Database server on the listener port.

Step 2: Connect via SSH

Once your VM is running, connect using SSH:

ssh azureuser@<public-ip-address>

To find your VM's public IP:

az vm show --resource-group myResourceGroup --name my-oracle-client-19c-vm --show-details --query publicIps -o tsv

To switch to the root user:

sudo su -

Important: Wait for the VM to reach a running state before connecting. Early connection attempts may produce permission denied errors while cloud init completes initial provisioning.

Step 3: Switch to the Oracle User and Set Environment

The Oracle Client software is owned by the dedicated oracle OS user. Switch to this user and source the environment. Please type this command rather than copying and pasting:

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

The setEnv.sh script sets the Oracle environment variables required for utilities such as sqlplus:

ORACLE_BASE=/u01/app/oracle
ORACLE_HOME=/u01/app/oracle/product/19.3.0/client_1
TNS_ADMIN=$ORACLE_HOME/network/admin
PATH=$ORACLE_HOME/bin:$PATH
LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH
NLS_LANG=AMERICAN_AMERICA.AL32UTF8

A system wide hook is also installed at /etc/profile.d/oracle-client.sh so any future Linux user on the VM picks up the same environment automatically on login.

Step 4: Configure tnsnames.ora

Before connecting to a remote Oracle Database, add an entry for it to tnsnames.ora. Run the following commands as the oracle user, replacing the placeholder values with your target database details:

cd $HOME
. ./setEnv.sh

cat >> "$ORACLE_HOME/network/admin/tnsnames.ora" << 'TNS'
MY_DATABASE =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = YOUR_DB_HOSTNAME)(PORT = 1521))
    )
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = YOUR_SERVICE_NAME)
    )
  )
TNS

Replace the following values:

  • YOUR_DB_HOSTNAME with the IP address or DNS name of your Oracle Database server
  • 1521 with the port number if different from the default
  • YOUR_SERVICE_NAME with the service name of the target database

Verify that Oracle Net can resolve the alias:

tnsping MY_DATABASE

Expected output (common prefix):

TNS Ping Utility for Linux: Version 19.0.0.0.0 - Production

Used parameter files:
/u01/app/oracle/product/19.3.0/client_1/network/admin/sqlnet.ora

Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = YOUR_DB_HOSTNAME)(PORT = 1521))) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = YOUR_SERVICE_NAME)))

followed by one of:

  • OK (n msec) if YOUR_DB_HOSTNAME resolves and the remote listener accepts the connection. This is what you want to see.
  • TNS-12545: Connect failed because target host or object does not exist if YOUR_DB_HOSTNAME is still the placeholder or is otherwise unresolvable. This proves the TNS layer is loading correctly and you simply need to replace the placeholder host with a real Oracle database server you can reach.
  • TNS-12541: TNS:no listener if the hostname resolves but nothing is listening on port 1521 at that address. Check the target database listener is up and reachable from this VM.

Seeing any of the three means tnsping is wired correctly. Only the first means the full round-trip to your target database works.

Step 5: Connect to a Remote Database via SQL*Plus

With the environment sourced and tnsnames.ora populated, connect to your remote database. The simplest form uses the TNS alias you just created:

cd $HOME
. ./setEnv.sh
sqlplus system/your_password@MY_DATABASE

You can also use the EZCONNECT syntax without editing tnsnames.ora at all:

sqlplus 'system/your_password@//your-db-host:1521/your-service-name'

Expected output:

SQL*Plus: Release 19.0.0.0.0 Production

Copyright (c) 1982, 2019, Oracle. All rights reserved.

Connected to:
Oracle Database ...

SQL>

Type EXIT to leave the SQL*Plus session.

Server Components

Component Version Install Path
Oracle Database Client 19c (Administrator) 19.3.0.0.0 /u01/app/oracle/product/19.3.0/client_1
Oracle Linux 8 /

Note: Component versions may be updated on first boot by the automatic OS package update script.

Filesystem Layout

The image uses LVM on a single OS disk. The root filesystem hosts the Oracle Client software under /u01; there is no separate /u01 mount point to manage or resize independently.

Mount Point Size Description
/ 37 GB Root filesystem (LVM logical volume) — hosts the Oracle Client software under /u01
/boot 2 GB Operating system kernel files
/boot/efi 100 MB UEFI boot partition (Gen2 Hyper V)
/var/crash 10 GB Reserved for kernel crash dumps (LVM logical volume)
/mnt varies Azure temporary resource disk (not persistent across stop/deallocate)

Key Oracle directories:

Directory Purpose
/u01/app/oracle Oracle base directory
/u01/app/oracle/product/19.3.0/client_1 Oracle Client home directory
/u01/app/oracle/product/19.3.0/client_1/bin Client binaries (sqlplus, sqlldr, tnsping, expdp, impdp)
/u01/app/oracle/product/19.3.0/client_1/lib Oracle Net libraries (libclntsh.so)
/u01/app/oracle/product/19.3.0/client_1/network/admin TNS configuration files (tnsnames.ora, sqlnet.ora)
/u01/app/oraInventory Oracle Universal Installer inventory

Managing the Oracle Client

The Oracle Client is a set of tools and libraries, not a running service. There are no services to start or stop. Simply switch to the oracle user and source the environment to use the client tools:

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

Verify the client is ready:

sqlplus -V
which sqlplus

Expected output:

SQL*Plus: Release 19.0.0.0.0 - Production
Version 19.3.0.0.0

/u01/app/oracle/product/19.3.0/client_1/bin/sqlplus

Scripts and Log Files

Script/Log Path Description
initial_boot_update.sh /stage/scripts Updates the OS with the latest packages on first boot
initial_boot_update.log /stage/scripts Output log for the boot update script
setEnv.sh /home/oracle Sets Oracle environment variables for sqlplus and other tools
oracle-client.sh /etc/profile.d System wide environment hook for any logged in user

On Startup

An OS package update script runs on first boot to ensure the image is fully up to date. You can disable this by removing the script and its crontab entry:

sudo rm -f /stage/scripts/initial_boot_update.sh

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

Troubleshooting

Cannot connect via SSH

  1. Verify the VM is in Running state in the Azure Portal
  2. Check that port 22 is allowed in the Network Security Group
  3. Ensure you are using the correct username: azureuser
  4. Verify your SSH key matches the one configured during deployment

sqlplus: command not found

  1. Confirm you switched to the oracle user: sudo su - oracle
  2. Source the environment script: . ~/setEnv.sh
  3. Verify the install path exists: ls /u01/app/oracle/product/19.3.0/client_1/bin/sqlplus
  4. Confirm $ORACLE_HOME/bin is on your PATH: echo $PATH

ORA-12154: TNS:could not resolve the connect identifier specified

  1. Check that your alias is defined in tnsnames.ora: cat $ORACLE_HOME/network/admin/tnsnames.ora
  2. Confirm TNS_ADMIN points at the network/admin directory: echo $TNS_ADMIN
  3. Validate the alias resolves: tnsping MY_DATABASE
  4. Watch for typos and case sensitivity in the alias name

ORA-12170: TNS:Connect timeout occurred

  1. Confirm the target database hostname and port are reachable from the VM: nc -vz YOUR_DB_HOSTNAME 1521
  2. Check the Network Security Group on the target database side allows inbound from your VM
  3. Verify route tables, peering, or VPN from this Azure VM to the target database network
  4. If the target is on premises, confirm Azure ExpressRoute or Site to Site VPN connectivity

ORA-12541: TNS:no listener

  1. The remote database listener may be down. Check with the DBA managing the target database
  2. Confirm you are using the correct port number in your tnsnames.ora entry
  3. Run tnsping MY_DATABASE to confirm the listener responds at the protocol layer

Security Recommendations

  • Restrict outbound access: Only allow outbound TCP 1521 from this VM to the specific Oracle Database servers it needs to reach
  • Protect tnsnames.ora: The TNS configuration file may reveal hostnames and service names of internal databases. Keep file permissions tight and avoid leaking it
  • Use wallets for credentials: Configure Oracle Wallet so passwords are not stored in plain text in scripts or shell history
  • Encrypt connections: Configure Oracle Net Services to use SSL/TLS encryption for client to database traffic
  • Limit OS access: Restrict SSH access to authorised administrators only
  • Enable auditing: Forward shell history and OS audit logs to a central log store
  • Keep the system updated: Apply Oracle Critical Patch Updates and OS security patches regularly

Support

If you encounter any issues with this product, contact cloudimg support:

cloudimg provides Oracle expertise and platform engineering support across AWS, Microsoft Azure, and Alibaba Cloud. For Oracle licensing questions, contact your Oracle account manager.

Oracle and Oracle Database are registered trademarks of Oracle Corporation. cloudimg is an independent provider and is not affiliated with or endorsed by Oracle Corporation.