Table of Contents
- 2.1 Official documentation and resources
- 2.2 Oracle Database 19c download
- 2.3 Recommended hardware specifications
- 2.4 Essential environment variables
- 2.5 Considerations for installing on Linux
- 3.1 Installation types: Server Class vs. Desktop Class
- 3.2 Launching the installation wizard (setup.exe)
- 3.3 Windows Service Account Configuration
- 3.4 Typical installation configuration
- 3.5 Common errors and solutions
- 3.6 Saving the response file
- 3.7 Procedure and finalization of the installation
- 4.1 Silent installation syntax
- 4.2 Structure and parameters of the response file
- 4.3 Database configuration settings
- 4.4 Memory management settings
- 4.5 Password and management settings
- 4.6 Recovery and storage settings
- 4.7 ASM (Automatic Storage Management) Settings
- 4.8 Oracle Home Account Settings
- 5.1 Overview of Database Configuration Assistant (DBCA)
- 5.2 Choice of database template
- 5.3 Database identification
- 5.4 Storage configuration
- 5.5 Fast Recovery Area
- 5.6 Listener configuration and advanced security
- 5.7 Memory settings (SGA and PGA)
- 5.8 Process Sizing
- 5.9 Connection Mode
- 5.10 Sample Schemas
- 5.11 Oracle Enterprise Manager Database Express
- 5.12 Administrator account passwords
- 5.13 SQL script creation and generation options
- 6.1 Oracle Net Manager
- 6.2 Naming Methods
- 6.3 Tracing and logging (Logging)
- 6.4 Network Security — Banners and Routing
- 6.5 Advanced network settings
- 6.6 Network authentication (NTS, Kerberos, RADIUS)
- 6.7 Data integrity and network encryption
- 6.8 SSL/TLS Configuration
- 6.9 tnsnames.ora file
- 7.1 Start and stop Oracle Net listener
- 7.2 Windows Services for Oracle 19c
- 7.3 Oracle Enterprise Manager Database Express — Monitoring
- 7.4 RMAN Tool (Recovery Manager)
- 7.5 Activation of ARCHIVELOG mode
- 7.6 Running a full backup with RMAN
1. Introduction and background
Welcome to the Install and Configure Oracle Database 19c course. This hands-on course teaches you how to install, configure, and validate Oracle Database 19c in a step-by-step manner.
Scenario Background: Globomantics, a fictional logistics company, is growing rapidly. To meet demand and ensure system reliability, the company must modernize its database infrastructure to handle this scale efficiently and securely.
This course covers the following topics:
- Preparing the environment and downloading the software
- Installing Oracle Database 19c (graphical and silent interface)
- Creating and configuring an instance via DBCA
- Configuring network connectivity with Oracle Net Manager
- Verification, management and backup of the installed base
2. Preparing the environment for installing Oracle Database 19c
2.1 Official Documentation and Resources
Before starting the installation, it is strongly recommended to consult the official Oracle documentation:
- Oracle Database Upgrade Guide — Available on the official Oracle Documentation website. This guide contains detailed information and best practices.
- Oracle Database 19c Installation Guide — Covers system requirements, supported configurations, and installation steps for Windows and Linux.
Tip: Although the official documentation is very comprehensive, this course simplifies the process and extracts the essential elements for a successful installation.
2.2 Oracle Database 19c Download
To download Oracle Database 19c:
- Perform a Google search with the keywords
Oracle Database 19c download. - Go to the official Oracle download page.
- Accept the license agreement (License Agreement).
- Click on the Download button.
- Log in with an Oracle account (creating an account is free if you don’t have one).
- Download the ZIP file containing the installation files.
The extracted ZIP file contains:
- Multiple folders containing runtime files required by the database.
- The
setup.exeexecutable (visible by scrolling down), which will be used to start the installation.
Note: In this course, the installation is performed on Windows 11.
2.3 Recommended hardware specifications
Oracle is a resource-intensive database. The minimum recommended specifications for a desktop installation on Windows are:
| Resource | Minimum recommended |
|---|---|
| RAM | 2 GB minimum (more recommended to avoid errors) |
| Disk space | Several dozen GB |
| CPU | Multi-core recommended |
Important: If too many applications are running in the background during installation, the installer may report that there is insufficient available memory. It is advisable to close unnecessary applications (especially browsers like Microsoft Edge) before starting the installation.
2.4 Essential environment variables
During installation, Oracle automatically configures three critical environment variables:
| Varies | Description |
|---|---|
ORACLE_HOME | Directory where Oracle software is installed |
ORACLE_SID | System ID (System ID) of the database instance |
PATH | Must include %ORACLE_HOME%\bin so command line tools like sqlplus can be accessed from any directory |
After installation, these variables are visible in Windows system environment variables.
2.5 Considerations for installing on Linux
Although this course covers installation on Windows exclusively, it is useful to know that Oracle provides specific documentation for installation on Linux. This documentation is available on the official Oracle website and describes the prerequisites and steps specific to the Linux environment.
3. Installing Oracle Database 19c Software
3.1 Installation types: Server Class vs. Desktop Class
The Oracle Installation Wizard offers two installation types:
| Criterion | Server Class | Desktop Class |
|---|---|---|
| Material resources | Large amount of memory, multiple CPUs, expanded storage | Limited resources |
| Workloads | Heavy / high volume of transactions | Lightweight / personal use |
| Performance and scalability | Optimized for high performance and scalability | Suitable for light loads |
| Advanced Features | Supports RAC, ASM, Data Guard | Does not support clustering or ASM |
| Use cases | Production, large databases, enterprise applications | Development, testing, single-user use |
| Network | Complex network scenarios, many clients | Basic network, few users |
| Availability | High availability (high-availability) | Low availability, no clustering or failover |
Summary: Use Server Class for production environments. Use Desktop Class for local development, testing and personal learning.
3.2 Launching the installation wizard (setup.exe)
- Extract the installation files into a dedicated folder (eg:
Oracle19c). - Run the
setup.exefile to launch the installation wizard. - The wizard offers two options:
- Create and configure a single instance database — Installs the software AND creates a database.
- Configure Oracle Database software only — Installs the software only, without creating a database. Typically used for upgrades to existing installations.
- Select the first option (Create and configure a single instance database) for installation from scratch.
- The installer verifies the contents of Oracle Home (Oracle home contents verification).
3.3 Windows Service Account Configuration
The installer is asking for the Windows account type under which the Oracle service will run. The options available are:
| Options | Description |
|---|---|
| Virtual user account (recommended default) | Automatically created, most secure and easiest virtual account |
| Existing Windows User | Use a Windows account already present on the system |
| Create a new user | Create a Windows account specifically for the Oracle service |
| Integrated Windows Account | Use a built-in Windows system account |
3.4 Typical installation configuration
In the Typical Install Configuration section, the parameters to define are:
- Oracle base: Oracle base directory (must be a new clean directory, without previous Oracle installation).
- Database file location: Location of the database files.
- Database name: Name of the Oracle database (e.g.:
Oracle19). - Administrator password: Password for the SYS and SYSTEM accounts.
3.5 Common Errors and Solutions
During installation, several errors may occur:
Error 1: Oracle base directory containing existing Oracle inventory
Message: The selected Oracle base already contains an Oracle inventory or central repository of installed Oracle products.
Cause: A previous Oracle installation leaves residue in the directory (including an inventory folder with subfolders).
Solution:
- Navigate to
C:\Program Files\Oracle(or previous Oracle location). - Manually delete the
inventoryfolder and its subfolders. - Choose a new clean directory for the Oracle base in the installer.
Error 2: Insufficient memory available
Message: The current available memory is less than the amount required to create the database.
Cause: Too many applications are using RAM in the background.
Solution:
- Open Windows Task Manager (Task Manager).
- Identify the processes consuming the most memory (e.g.: Microsoft Edge).
- Terminate these processes to free up memory.
- Return to the installer and click Next.
Error 3: Invalid Oracle Base Location
Message: The Oracle base location is invalid because it contains one or more Oracle bases associated with Oracle home.
Solution: Choose a new clean directory for the Oracle base, or remove old Oracle installations and clean the Windows registry (registry) before continuing.
3.6 Saving the response file
Before clicking on Install, it is possible to save the installation parameters in a response file. This file allows you to reproduce exactly the same installation in silent mode (silent installation) from the command line.
Recommended save location: In the Oracle application folder.
3.7 Progress and finalization of the installation
- Click Install to start the installation.
- Open the details window to monitor progress.
- The installation may appear to hang temporarily (eg at 7% progress) — this is normal behavior.
- Once the installation is complete, the URL of the Enterprise Manager is displayed: accessible on
localhost. - Close the installer.
Result: The Oracle 19c database instance is installed successfully.
4. Silent command line installation
4.1 Silent installation syntax
It is possible to perform exactly the same installation without a graphical interface, entirely on the command line (silent mode), using the previously saved response file.
setup.exe -silent -responseFile "C:\chemin\vers\le\fichier.rsp"
Note: The
setup.exefile is located in the Oracle Home directory. The response file (*.rsp) must be specified with its full path.
Warning: If the database is already installed, this command will fail with a message indicating that the database is already registered in the central inventory.
4.2 Structure and parameters of the response file
The response file is a structured text file containing all Oracle installation parameters. Here is its structure and the essential parameters:
Parameter: Schema version
# Définit la version du schéma du fichier de réponse.
# Ne jamais modifier cette ligne.
oracle.install.responseFileVersion=/oracle/install/rspfmt_dbinstall_response_schema_v19.0.0
Parameter: Installation type
# Type d'installation Oracle
# INSTALL_DB_ONLY : Installe uniquement le logiciel (pas de création de BDD)
# INSTALL_DB_AND_CONFIG : Installe le logiciel ET configure une nouvelle instance
oracle.install.option=INSTALL_DB_AND_CONFIG
Parameter: Unix Group (Linux/Unix only)
# Groupe OS propriétaire de l'inventaire Oracle (Linux/Unix obligatoire, ignoré sur Windows)
UNIX_GROUP_NAME=oinstall
4.3 Database configuration parameters
# Section : Database Configuration Options
# Type de base de données à créer
# GENERAL_PURPOSE : Workloads transactionnels ou mixtes
# DATA_WAREHOUSE : Optimisé pour l'analytique et les rapports
oracle.install.db.config.starterdb.type=GENERAL_PURPOSE
# Nom global de la base de données (incluant le nom et le domaine réseau)
# Identifie la BDD de façon unique sur le réseau
oracle.install.db.config.starterdb.globalDBName=ORAHOMEDB
# System ID (SID) — identifie l'instance Oracle sur la machine hôte
# Souvent identique au nom global, mais pas obligatoirement
oracle.install.db.config.starterdb.SID=ORAHOMEDB
# Création d'une Container Database (CDB) supportant des Pluggable Databases (PDB)
# true : Architecture multi-tenant (recommandé avec Oracle 19c)
# false : Architecture classique non-CDB
oracle.install.db.ConfigureAsContainerDB=true
# Encodage des caractères (character set) de la base de données
# AL32UTF8 : Supporte le stockage de texte multilingue (recommandé)
oracle.install.db.config.starterdb.characterSet=AL32UTF8
4.4 Memory management parameters
# Gestion automatique de la mémoire
# false : Allocation manuelle (spécifier les limites exactes de mémoire)
# true : Oracle gère automatiquement la mémoire (moins de tuning manuel)
oracle.install.db.config.starterdb.memoryOption=false
# Mémoire totale allouée à la base de données (en mégaoctets)
# Minimum : 256 MB | Ne pas dépasser la mémoire totale de la machine
# Utilisé uniquement si memoryOption=false
oracle.install.db.config.starterdb.memoryLimit=13312
# Installation des schémas exemples (HR, etc.)
# true : Installe les schémas HR et autres (utile pour apprendre SQL et les tests)
# false : Pas de schémas exemples
oracle.install.db.config.starterdb.installExampleSchemas=true
4.5 Password and management settings
# Section : Mots de passe des comptes administrateurs
# Mot de passe unique pour TOUS les comptes administrateurs (SYS, SYSTEM, etc.)
# Si renseigné, les champs individuels peuvent rester vides
oracle.install.db.config.starterdb.password.ALL=<MotDePasseStrong>
# Mot de passe du compte SYS (super-utilisateur avec tous les privilèges DBA)
oracle.install.db.config.starterdb.password.SYS=
# Mot de passe du compte SYSTEM (utilisé pour les tâches de gestion quotidienne et OEM)
oracle.install.db.config.starterdb.password.SYSTEM=
# Mot de passe du compte utilisé par Oracle Enterprise Manager pour la surveillance
# Applicable uniquement si managementOption=CLOUD_CONTROL
oracle.install.db.config.starterdb.password.DBSNMP=
# Option de gestion de la base de données
# DEFAULT : Aucune gestion externe configurée
# CLOUD_CONTROL: Intégration avec Oracle Enterprise Manager Cloud Control (surveillance centralisée)
oracle.install.db.config.starterdb.managementOption=DEFAULT
# OMS Host — Oracle Management Service
# Requis uniquement si managementOption=CLOUD_CONTROL
oracle.install.db.config.starterdb.omsHost=
# Port de connexion à Cloud Control
# 0 = non utilisé (si managementOption=DEFAULT)
oracle.install.db.config.starterdb.omsPort=0
# Section : Authentification Enterprise Manager Cloud Control
# (utilisé uniquement si managementOption=CLOUD_CONTROL)
# Nom d'utilisateur administrateur Enterprise Manager
# Typiquement un utilisateur WebLogic ou administrateur
oracle.install.db.config.starterdb.emAdminUser=
# Mot de passe de l'utilisateur administrateur EM
# Utilisé pour authentifier l'instance BDD auprès de l'OMS
oracle.install.db.config.starterdb.emAdminPassword=
4.6 Recovery and storage settings
# Section : Options de récupération et stockage
# Activation de la récupération de la base de données
# false : Pas de Flash Recovery Area configurée
# true : Active les sauvegardes automatiques et les options de récupération
oracle.install.db.config.starterdb.enableRecovery=false
# Type de stockage pour les fichiers de la base de données
# FILE_SYSTEM_STORAGE : Stockage sur chemin disque local (défaut pour les setups locaux)
# ASM_STORAGE : Utilise Oracle ASM pour la redondance et la performance avancées
oracle.install.db.config.starterdb.storageType=FILE_SYSTEM_STORAGE
# Répertoire de stockage des fichiers de données, control files et redo logs
# Doit être un chemin valide avec suffisamment d'espace
# Requis si storageType=FILE_SYSTEM_STORAGE
oracle.install.db.config.starterdb.fileSystemStorage.dataLocation=C:\oracle\oradata
# Emplacement des fichiers liés à la récupération (flashback logs, sauvegardes)
# Optionnel — requis uniquement si enableRecovery=true
oracle.install.db.config.starterdb.fileSystemStorage.recoveryLocation=
4.7 ASM (Automatic Storage Management) settings
# Section : Paramètres ASM
# Applicables UNIQUEMENT si storageType=ASM_STORAGE
# Disk group ASM à utiliser pour le stockage des fichiers de la BDD
# Valeurs courantes : DATA, FRA
oracle.install.db.config.starterdb.ASM.diskGroup=
# Mot de passe de l'utilisateur de surveillance ASM
# Requis pour Enterprise Manager / Grid Infrastructure monitoring
oracle.install.db.config.starterdb.ASM.monitorPassword=
4.8 Oracle Home Account Settings
# Section : Oracle Home User Parameters
# Oracle recommande d'exécuter les installations sous un compte à privilèges limités
# Nom du compte Windows utilisateur pour Oracle Home
oracle.install.db.OSDBA_GROUP=
oracle.install.db.OSOPER_GROUP=
5. Creating and configuring an Oracle Database 19c instance with DBCA
5.1 Overview of the Database Configuration Assistant (DBCA)
The Database Configuration Assistant (DBCA) is a very practical graphical tool for managing Oracle 19c instances. It allows you to:
- Create a new database (Create a database)
- Configure an existing database
- Delete a database
- Manage database templates
For this configuration, the Create a database option is selected in order to build a new Oracle 19c instance from scratch.
5.2 Choice of database template
The DBCA offers several predefined templates:
Data Warehouse
Automatically includes a set of components optimized for analytical workloads:
ORACLE_TEXTOLAP TextOLAPSAMPLE_SCHEMAS
These components are optimized for analytical workloads.
Custom Database
Provides full control over components and settings. Only essential features are selected by default. Ideal for adapting the database to specific applications or environments, avoiding unnecessary components.
General Purpose or Transaction Processing (recommended)
Solid template for building a robust and complete database from the start, suitable for transactional or mixed workloads. This is the template used in this course.
5.3 Database identification
| Parameter | Description |
|---|---|
| Global Database Name | Globally unique name of the database (e.g.: ORAHOMEDB) |
| System ID (SID) | Oracle automatically sets it to match the global name |
This setup facilitates resource isolation and simplifies future upgrades or multi-tenant deployments.
5.4 Storage configuration
- Storage type: File system (file system)
- Storage path: Oracle uses default path
- Oracle-Managed Files (OMF): Enabled — Oracle automatically manages file names and file organization. This simplifies administration and ensures consistent file structures.
5.5 Fast Recovery Area
| Parameter | Configured value |
|---|---|
| Allocated space | Just over 12 GB |
| Archiving | Disabled for this demonstration |
The Fast Recovery Area improves database recoverability in the event of a failure.
5.6 Listener configuration and advanced security
- Listener: Allows clients to connect to the database. Configured in this step.
- Oracle Database Vault: Enhanced security for sensitive data — not enabled in this demo.
- Label Security: Label-based access control — not enabled in this demo.
5.7 Memory parameters (SGA and PGA)
In the Memory tab of the DBCA, the configuration uses *Automatic Shared Memory Management:
| Parameter | Description |
|---|---|
| SGA (System Global Area) | Manually set size — memory area shared between all Oracle processes |
| PGA (Program Global Area) | Manually set size — private memory for each server process |
These settings control the amount of memory allocated for essential database operations.
5.8 Process sizing (Sizing)
In the Sizing tab, the maximum number of concurrent user processes is defined:
Processes : 1500
This value includes background processes (background processes) and user connections. It must be adjusted according to the expected load.
5.9 Connection Mode
In the Connection mode tab, the Dedicated Server mode is selected:
| Fashion | Description | Recommended for |
|---|---|---|
| Dedicated Server | Each connection has its own server process | Limited number of users, long or intensive operations |
| SharedServer | Multiple connections share a server process pool | Large number of users with short connections |
Dedicated Server mode is optimal when the number of users is limited or when each connection performs long or resource-intensive operations.
5.10 Sample Schemas
In the Sample schema tab, the option to install sample schemas is enabled. The HR (Human Resources) schema is included, making it easy to learn SQL and test with representative data.
5.11 Oracle Enterprise Manager Database Express
Oracle Enterprise Manager (EM) Database Express can be enabled for database monitoring. For standalone installations, enabling EM Database Express is generally sufficient.
5.12 Administrator account passwords
The configured administrator accounts are:
| Account | Role |
|---|---|
| SYS | Superuser with full DBA privileges |
| SYSTEM | Daily management account, access to OEM |
| PDBADMIN | Pluggable Database (PDB) Administrator |
Two options are available:
- Single password for all accounts — Use the same admin password for all accounts (recommended to simplify setup and testing)
- Separate password per account — More secure for production
Important: The password must be strong and confirmed correctly. Use a single password during installation and testing, but opt for separate passwords in production.
5.13 Options for creating and generating SQL scripts
During the final DBCA configuration step, several options are available:
| Options | Description |
|---|---|
| Create the database immediately | Starts the creation of the database immediately |
| Save as reusable template | Saves the configuration for future deployments. The template is stored with a customizable name and location |
| Generate creation SQL scripts | Generates SQL scripts that can be examined, customized, and subsequently executed by DBAs who prefer command-line execution |
| Save as response file | Useful for automation or to recreate the database silently |
DBA Tip: Generating SQL scripts gives great flexibility and transparency on exactly what the database will create. This is a good practice for traceability.
6. Configuring Oracle Network Connectivity
6.1 Oracle Net Manager
Oracle Net Manager is a graphical tool for visually configuring essential aspects of Oracle network connectivity. It is located under the Oracle installation path.
The tool is organized around the Local node with several sections:
- Profile — Naming methods and general network settings
- Service Naming — Connection alias (tnsnames.ora)
- Listeners — Configuration of network listeners
6.2 Naming Methods
In the Profile > Local section, the naming methods (naming methods) are configured. These are the rules that Oracle uses to resolve server names to actual connection details.
Available methods:
| Method | Description |
|---|---|
TNSNAMES | Resolution via tnsnames.ora file (local method) |
EZCONNECT | Simplified connection format: host:port/service_name |
HOSTNAME | Resolution via network hostname |
LDAP | Resolution via a centralized directory service (eg: Oracle Internet Directory) |
NIS | Network Information Service |
Recommended configuration (Selected Methods):
1. TNSNAMES (priorité 1 — résolution locale via tnsnames.ora)
2. EZCONNECT (priorité 2 — fallback avec format simplifié)
Oracle first attempts to resolve connection strings through entries in the tnsnames.ora file. If this fails, it uses the EZCONNECT method to connect with the format:
hostname:port/service_name
The Promote and Demote buttons allow you to reorder the priority of methods.
6.3 Tracing and logging (Logging)
Tracing Tab
- Automatic Diagnostic Repository (ADR): Can be enabled for centralized logging of Oracle Net diagnostics.
Logging tab
It is possible to specify custom log directories and file names for client and server activities. This makes it easier to track and audit Oracle Net events, especially when debugging connectivity or authentication issues.
6.4 Network security — Banners and Routing
Security tab
Defining custom banner files:
| Banner | Trigger |
|---|---|
| Unauthorized access banner | Displayed during unauthorized access attempts |
| User audit banner | Displayed during user audit actions |
These banners are displayed as part of the Oracle network security policy.
Routing Tab
Controls how client connections are handled:
- Always Use Dedicated Server: Forces each connection to have its own server process.
6.5 Advanced network settings
In the Advanced tab of Oracle Net Manager, low-level network settings can be adjusted:
| Parameter | Description |
|---|---|
| Send timeout | Timeout for sending data |
| Receive timeout | Timeout for receiving data |
| Connection timeout | Timeout for establishing a connection |
| Buffer sizes | Network Buffer Sizes |
| Session parameters | Network Session Settings |
6.6 Network authentication (NTS, Kerberos, RADIUS)
In the Network Security Authentication tab, network authentication methods are configured.
Default selected method (Windows):
NTS (NT Security) — authentification Windows intégrée
Available authentication methods:
| Method | Description |
|---|---|
NTS | NT Security — used in Windows environments |
Kerberos | Kerberos authentication for SSO (Single Sign-On) |
RADIUS | Remote Authentication Dial-In User Service |
To enable Kerberos or RADIUS, move them to the list of selected methods.
Kerberos Parameters (Other Params tab)
| Parameter | Description |
|---|---|
| Kerberos Service Name | Kerberos service name |
| Credential Cache File | Kerberos credentials cache file |
| Configuration File | Kerberos configuration file |
| Realm Translation File | realm translation file |
| Key Table Path | Path to keytab file |
| Clock Skew | Maximum allowable time difference (prevents replay attacks) |
Important: These settings are essential for environments integrating Oracle with Kerberos, particularly for Single Sign-On (SSO).
6.7 Data integrity and network encryption
Data integrity
Integrity Option : SERVER
Checksum Level : ACCEPTED
This configuration guarantees that messages exchanged between the client and the server are not altered in transit (tamper protection).
Network encryption (Encryption tab)
Encryption Option : SERVER
Encryption Type : ACCEPTED (optionnel mais supporté)
Strong encryption algorithms can be selected to protect data in transit (e.g. AES256, AES192, AES128, 3DES168).
6.8 SSL/TLS configuration
SSL Client
To enable client-side SSL:
| Parameter | Description |
|---|---|
| Wallet Directory | Directory containing client certificates (used for authentication and encryption) |
| Cipher Suites | Custom algorithms for authentication, encryption and integrity |
SSL Server
To enable server-side SSL:
| Parameter | Description |
|---|---|
| Wallet Directory | Directory containing server certificates |
| Required Client Authentication | Mutual authentication required — both client AND server must present valid certificates |
Note: Enabling Required Client Authentication enforces mutual authentication (mutual TLS), which is crucial for securing incoming client connections with SSL.
6.9 File tnsnames.ora
The tnsnames.ora file is the main configuration file used by Oracle Net Services. It contains connection aliases (connection descriptors).
Here are typical entries in the tnsnames.ora file after installation:
-- Connexion à la base de données ORAHOMEDB via TCP (localhost:1521), mode dédié
ORAHOMEDB =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ORAHOMEDB)
)
)
-- Communication IPC interne avec le service (pour les procédures locales)
ORACLE_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
)
)
-- Listener TCP de ORAHOMEDB sur localhost:1521
LISTENER_ORAHOMEDB =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
-- Connexion à Oracle 19c via TCP (localhost:1521), mode dédié
Oracle19c =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = Oracle19c)
)
)
-- Adresse réseau pour le listener Oracle 19c (port 1521 par défaut)
LISTENER_ORACLE19c =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
Description of entries:
| Entrance | Description |
|---|---|
ORAHOMEDB | Connection to the ORAHOMEDB database on localhost:1521, dedicated server |
ORACLE_CONNECTION_DATA | Internal IPC communication for external procedures |
LISTENER_ORAHOMEDB | TCP listener for ORAHOMEDB on localhost:1521 |
Oracle19c | Connecting to Oracle19c on localhost:1521, dedicated server |
LISTENER_ORACLE19c | Network address for Oracle19c listener on localhost:1521 |
7. Checking and managing the installed Oracle database
7.1 Start and stop the Oracle Net listener
The Oracle Net Listener listens for incoming client connection requests on the specified network endpoints and registers the database services available to process these connections.
Prerequisites: Open a terminal as administrator (Run as administrator).
Start listener
lsnrctl start
Expected result: The listener starts and begins listening on the configured port (default 1521). If the listener is already running, a message indicates this (“the listener has already been started”*).
Stop listener
lsnrctl stop
Check listener status
lsnrctl status
Result of a started listener:
- Active listening on configured network endpoints
- Database services registered and ready to process connections
7.2 Windows Services for Oracle 19c
Oracle 19c installs several Windows Services (Windows Services). Accessible via services.msc.
Most Important Oracle Services:
| Services | Description |
|---|---|
OracleServiceORACLE19C | Oracle Instance Main Service |
OracleOraDB19Home1TNSListener | Oracle Net Listener Service |
OracleVssWriterORACLE19C | VSS Writer for Windows Backups |
OracleJobSchedulerORACLE19C | Oracle Job Scheduler |
Note: If multiple Oracle instances are installed on the same machine, each instance will have its own set of corresponding services.
Service management from services.msc:
- Restart listener service to restart the Oracle Net listener.
- Restart Oracle Home Services to restart the database and instance.
7.3 Oracle Enterprise Manager Database Express — Monitoring
Oracle Enterprise Manager (EM) Database Express is a monitoring tool accessible from a web browser on localhost.
Login
URL : https://localhost:<port>/em
User : SYS
Role : SYSDBA
Performance Dashboard
Real-time performance graph: Displays database activity metrics:
| Metric | Description |
|---|---|
| CPU Usage | CPU usage compared to available cores |
| I/O | Input/output requests |
| Network | Network performance |
Resource Utilization Section:
| Resource | Indicator |
|---|---|
| CPU Host Load | Host server CPU load (low under normal conditions) |
| Active Sessions | Number of active sessions |
| SGA | System Global Area — shared memory usage |
| PGA | Program Global Area — private process memory |
| Shared Pool | Memory pool for SQL queries and metadata |
| Storage | Use of storage by the PDB (Pluggable Database) |
SQL Monitor: Highlights the most active SQL queries from the last hour. Example display:
| SQLID | Duration | I/O Requests |
|---|---|---|
<sql_id> | 8 seconds | 169 |
This helps identify the most resource-intensive operations.
7.4 RMAN Tool (Recovery Manager)
RMAN (Recovery Manager) is the Oracle tool dedicated to database backups and recovery. It is located in the Oracle bin directory (accessible by searching for rman in the %ORACLE_HOME%\bin folder).
Start RMAN
rman target /
Installed Schemas Report
RMAN can generate a report on the schemas installed in the database, including the locations of permanent and temporary data files:
REPORT SCHEMA;
Result: Shows the locations of permanent and temporary datafiles — useful for knowing where files are physically stored.
7.5 Activation of ARCHIVELOG mode
By default, a new Oracle installation can be in NOARCHIVELOG mode. Full backup with RMAN requires ARCHIVELOG mode.
Error without ARCHIVELOG:
RMAN-06059: expected archived log not found ORA-19566: exceeded limit of 0 corrupt blocks for file
Procedure for activating ARCHIVELOG mode
Step 1 — Connect as SYSDBA in SQL*Plus:
sqlplus / as sysdba
Step 2 — Shut down the Oracle instance:
SHUTDOWN IMMEDIATE;
Step 3 — Start the instance without opening the database (MOUNT mode):
STARTUP MOUNT;
Step 4 — Enable ARCHIVELOG mode:
ALTER DATABASE ARCHIVELOG;
Step 5 — Open Database:
ALTER DATABASE OPEN;
Step 6 — Verify that ARCHIVELOG mode is active:
ARCHIVE LOG LIST;
Expected result:
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence <n>
Next log sequence to archive <n+1>
Current log sequence <n+1>
Step 7 — Exit SQL*Plus:
EXIT;
7.6 Performing a full backup with RMAN
Once ARCHIVELOG mode is activated, a full backup can be performed with RMAN:
Connect to RMAN
rman target /
Start full backup (database + archivelogs)
BACKUP DATABASE PLUS ARCHIVELOG;
Behavior: RMAN backs up all Oracle data files as well as the archive logs. The progress displays the different datafiles being saved.
Example RMAN output:
Starting backup at <date>
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=<n> device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=C:\ORACLE\ORADATA\<SID>\SYSTEM01.DBF
input datafile file number=00003 name=C:\ORACLE\ORADATA\<SID>\SYSAUX01.DBF
...
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:<ss>
Finished backup at <date>
Exit RMAN
EXIT;
8. Appendix: Essential Commands Reference
lsnrctl commands (Oracle Net Listener)
# Démarrer le listener
lsnrctl start
# Arrêter le listener
lsnrctl stop
# Vérifier l'état du listener
lsnrctl status
# Recharger la configuration du listener
lsnrctl reload
SQL Commands*More
# Connexion en tant que SYSDBA depuis le terminal
sqlplus / as sysdba
# Connexion avec un compte spécifique
sqlplus sys/<mot_de_passe> as sysdba
sqlplus system/<mot_de_passe>
-- Gestion de l'instance
STARTUP; -- Démarrer l'instance
STARTUP MOUNT; -- Démarrer sans ouvrir (pour les modifications de configuration)
SHUTDOWN IMMEDIATE; -- Arrêter l'instance immédiatement
SHUTDOWN NORMAL; -- Arrêt normal (attend la fin des sessions)
SHUTDOWN ABORT; -- Arrêt forcé (à éviter sauf urgence)
-- Mode ARCHIVELOG
ALTER DATABASE ARCHIVELOG; -- Activer le mode archive log
ALTER DATABASE NOARCHIVELOG; -- Désactiver le mode archive log
ARCHIVE LOG LIST; -- Vérifier l'état du mode archive log
ALTER DATABASE OPEN; -- Ouvrir la base de données après STARTUP MOUNT
-- Informations sur la base de données
SELECT NAME, DB_UNIQUE_NAME, LOG_MODE FROM V$DATABASE;
SELECT INSTANCE_NAME, STATUS, VERSION FROM V$INSTANCE;
SELECT * FROM V$PARAMETER WHERE NAME IN ('db_name', 'instance_name', 'memory_target');
-- Quitter SQL*Plus
EXIT;
Recovery Manager (RMAN) Commands
# Lancer RMAN connecté à la base de données locale
rman target /
# Lancer RMAN avec un catalogue de récupération
rman target sys/<mot_de_passe> catalog <catalog_user>/<mot_de_passe>@<catalog_service>
-- Rapport sur les schémas (fichiers de données)
REPORT SCHEMA;
-- Sauvegarde complète de la base de données uniquement
BACKUP DATABASE;
-- Sauvegarde complète + archivelogs
BACKUP DATABASE PLUS ARCHIVELOG;
-- Sauvegarde incrémentale de niveau 0
BACKUP INCREMENTAL LEVEL 0 DATABASE;
-- Sauvegarde incrémentale de niveau 1
BACKUP INCREMENTAL LEVEL 1 DATABASE;
-- Vérifier les sauvegardes existantes
LIST BACKUP SUMMARY;
-- Quitter RMAN
EXIT;
Silent installation (command line)
# Depuis le répertoire contenant setup.exe
setup.exe -silent -responseFile "C:\chemin\complet\vers\le\fichier.rsp"
Oracle environment variables
# Afficher les variables d'environnement Oracle dans Windows
echo %ORACLE_HOME%
echo %ORACLE_SID%
echo %PATH%
# Définir manuellement les variables (si nécessaire)
set ORACLE_HOME=C:\app\oracle\product\19.0.0\dbhome_1
set ORACLE_SID=ORAHOMEDB
set PATH=%ORACLE_HOME%\bin;%PATH%
Oracle Enterprise Manager Database Express Connection
URL : https://localhost:<port>/em
Utilisateur : SYS
Rôle : SYSDBA
Mot de passe : <mot_de_passe_maître>
Level: Practical (hands-on)
Search Terms
install · configure · oracle · database · 19c · databases · sql · installation · configuration · listener · manager · network · rman · tab · parameters · settings · recovery · account · commands · data · enterprise · environment · error · express