Oracle AI Database 26ai RMAN is a course in using Oracle Recovery Manager (RMAN) to back up and recover Oracle databases on the CDB and PDB architecture, including automated scripts, complete and point-in-time recovery, and backups to disk, tape and the cloud. It suits database administrators and system engineers who already look after Oracle Database.
The data in an Oracle database is often the heart of an organisation's systems, yet many sites still have backups that have never been test-restored, do not know whether they can roll data back to before a mistake, and have no clear procedure for when a disk fails or a whole server is lost. Oracle Recovery Manager (RMAN) is the main tool for this work. It works directly with the database, detects block-level corruption during backup and restore, and turns backup and recovery into a planned, repeatable task.
This course is updated for Oracle AI Database 26ai, the current release that succeeds 23ai and uses the CDB and PDB architecture. It starts with a strategy based on RPO and RTO, setting up ARCHIVELOG mode, the fast recovery area and RMAN, backing up whole databases and parts of them, using a recovery catalog and writing scripts that run automatically. Learners then practise complete recovery, point-in-time recovery, Flashback and repairing corrupt blocks, before moving on to backups to disk, tape and the cloud, restoring to new disks or a new server, and a closing workshop that writes a backup plan and rehearses a full system recovery. (3 days, 6 hours per day, 18 hours in total, Intermediate level.)
Course Details
This course is the 2026 edition of Oracle Database 21c RMAN, updated for Oracle AI Database 26ai, the current release that succeeds 23ai and is built on the CDB and PDB architecture. It runs for 3 days, 6 hours per day (18 hours in total, 09:00-16:00), as lectures with labs on a database VM that learners use throughout. Intermediate level. It covers strategy, configuration, full and incremental backups, complete and point-in-time recovery, Flashback, backups to tape and the cloud, and restoring to a new server, and most of the content also applies to Oracle Database 19c. Learners take home a lab guide, RMAN and shell scripts, a backup policy template and a recovery runbook.
Section 1: Lab: Backup Strategy and the 26ai Environment
Section 2: RMAN Architecture and Backup Types
Section 3: Lab: Configuring RMAN Parameters
Section 4: Lab: Backing Up Whole Databases and Parts of Them
Section 5: Recovery Catalog and Automated RMAN Scripts
Section 6: Restore and Recovery Concepts
Section 7: Lab: Complete Recovery
Section 8: Lab: Point-in-Time Recovery
Section 9: Flashback Technologies
Section 10: Detecting and Repairing Corrupt Blocks
Section 11: Backing Up to and Restoring from Disk and Tape
Section 12: Cloud Backups and Immutable Backups
Section 13: Lab: Restoring to New Disks or a New Server
Section 14: Tuning and Monitoring Backup Jobs
Section 15: Workshop: Backup Plan and Recovery Drill
No public rounds are open right now. Join the waiting list and we will contact you first when the next round opens, or ask us on LINE. Or call 02-570-8449 or 088-807-9770
RMAN (Recovery Manager) is the backup and recovery tool that ships with Oracle Database and works directly with it. It can back up an open database, check blocks for corruption during the backup, take incremental backups, keep track of which backups exist and where, and pick the files needed for a restore automatically. Copying files yourself means handling backup mode, tracking files and checking integrity by hand, which is far more error-prone.
Complete recovery restores the damaged files and applies all the redo so the data comes back to the present with nothing lost. It is used when files or disks are lost. Point-in-time recovery rolls data back to a chosen time, SCN or log sequence, and is used after data is deleted or changed by mistake, so anything after that point is lost. In 26ai it works at CDB, PDB and tablespace level, and RECOVER TABLE can recover a single table.
First set the standing RMAN settings with CONFIGURE, such as the retention policy and control file autobackup. Then write an RMAN command file, for example BACKUP DATABASE PLUS ARCHIVELOG followed by DELETE OBSOLETE, and call it from a shell script or batch file that sets the environment and keeps a log. Schedule it with cron, Task Scheduler or DBMS_SCHEDULER, and check the result in the log or V$RMAN_BACKUP_JOB_DETAILS, with an alert when it fails.
It suits DBAs, system engineers and anyone responsible for backing up and recovering Oracle databases, including teams moving from older Oracle releases. You should already know Oracle Database administration, understand Oracle's file structure and be able to use basic Linux commands, as the labs run on Oracle Linux in a VM.
You will be able to plan a backup strategy around RPO and RTO, configure RMAN, run full and incremental backups with automated scripts, perform complete and point-in-time recovery at CDB, PDB, tablespace and table level, use Flashback, repair corrupt blocks, back up to disk, tape and the cloud, and restore to new disks or a new server when hardware fails. Participants who complete the training receive a Certificate of Completion with its own number, which can be verified online.
Yes. It can be run in-house for your team, with examples adapted to your own work, such as planning backups and rehearsing recovery for the Oracle releases and database layout your team already runs. You can request a quotation from this page, or contact us on LINE @itgenius or by phone on 02-570-8449.
Articles are published in Thai.
Much of the work in organisations that run Oracle Database involves multi-step data processing, such as payroll calculations, end-of-day closing or moving data between tables. Written as one SQL statement at a time from the application side, this work is…
Many problems in business systems start with the database structure: duplicated data that is changed in one place but not another, reports that pull figures that do not match, or systems where new features are hard to add because the tables were related…
