Introduction
This is the third post in our OEM series. With the OEM console and target already set up, this article walks through actually using OEM for day-to-day DBA work: monitoring performance, running backups, managing users, exporting schemas, and adjusting tablespaces and parameters, all from the console rather than the command line.
Prerequisites
Below are the minimum requirements for this guide:
- Target database up and running.
- SYS user password of the target database.
Environment Used in This Guide
| Hostname | oem.oraeasy.com |
|---|---|
| OS | OL 7.3 |
| OEM Version | 13c Release 5 (13.5) |
| Hostname | uat.oraeasy.com |
|---|---|
| OS | OL 8.5 |
| Database Name | ORCLDB |
| Database Version | 19c (19.27) |
Summary of Activities
This article covers the following areas of database management in OEM:
Performance
OEM can monitor database performance in real time: active sessions, wait events, and which queries are consuming the most CPU, without needing to run diagnostic queries by hand.
Step 1: View SQL Monitoring for a Database
Click Targets, then Database, then click the database you want to monitor.
Click Performance, then Performance Hub, then SQL Monitoring.
Provide the SYS user credentials for that database.
This shows every SQL statement running at that point in time, along with CPU utilization and User I/O displayed graphically.
Click any SQL ID to view its full execution details.
There's plenty more to explore under Performance Hub beyond SQL Monitoring.
Step 2: Generate an AWR Report
Click Performance, then Performance Hub, then AWR, then AWR Report.
Provide the begin and end snapshot, then click Generate Report.
Report generation is in progress.
Once generated, the report displays inline and can also be downloaded by clicking Save to File.
Backup
OEM can also run or schedule RMAN backups through its console instead of the command line, which is useful for standardizing backup schedules across many databases.
Step 1: Configure and Schedule the Backup Job
Click Availability, then Backup & Recovery, then Schedule Backup.
Select the backup option and host credential details, then click Schedule Customized Backup.
Select the backup type (Full or Incremental) and mode (Online or Offline), then click Next.
Select the backup destination, such as Disk, then click Next.
Schedule the backup timing and interval, then click Next.
Review the script and job details. The RMAN script can be edited directly by clicking Edit RMAN Script, then click Submit Job.
Step 2: Submit and Monitor the Backup Job
The RMAN job has been created. Click View Job to see its progress.
Monitor the progress.
The job can also be cross-checked directly on the target server.
[oracle@uat ~]$ ps -ef|grep rman
oracle 12945 12921 7 21:46 ? 00:00:00 rman app/oracle/product/19c/dbhome_1/bin/rman
oracle 12947 5427 0 21:46 pts/1 00:00:00 grep --color=auto rman
[oracle@uat ~]$
[oracle@uat 2025_09_20]$ ls -lrth
total 823M
-rw-r-----. 1 oracle oinstall 823M Sep 20 21:48 o1_mf_nnndf_BACKUP_ORCLDB_202509_ndxnvf98_.bkp
[oracle@uat 2025_09_20]$
[oracle@uat 2025_09_20]$ pwd
/u01/app/oracle/fast_recovery_area/ORCLDB/3D7F7AEE5DB8A4EEE0650A00273EBB20/backupset/2025_09_20
[oracle@uat 2025_09_20]$ hostname
uat.oraeasy.com
[oracle@uat 2025_09_20]$
The backup has completed successfully.
Users
OEM can also manage database users, including creating new ones, directly from the console.
Step 1: View and Edit an Existing User
Click Security, then Users.
This lists every database user with its details.
Enter a username and click Go to find a particular user, then click View for more details.
Details for the TEST user:
Click Edit to change the user's configuration. Here the account status is changed from Unlocked to Locked.
Click Show SQL to see the underlying SQL command for the change before it runs.
Step 2: Create a New User
On the users list screen, click Create, provide the details, then click OK.
The user TESTOEM has been created successfully.
Schema Export
Export and import jobs can also be driven from OEM. This section covers exporting a schema.
Step 1: Configure the Export Job
Click Schema, then Database Export/Import, then Export to Export Files.
Select Schema as the export type and select credentials for the host, then click Continue.
Provide the schema name, then click Select.
Review the schema name, then click Next.
Provide the directory name, log file name, and other details, then click Next.
Provide the dump file name, then click Next.
Configure the schedule and interval, provide the export job name, then continue.
Review the details, then click Submit.
Step 2: Verify the Export
The export job has been created successfully.
Monitor the progress.
The export can also be verified directly on the target server.
[oracle@uat 3D7F7AEE5DB8A4EEE0650A00273EBB20]$ pwd
/u01/app/oracle/admin/orcldb/dpdump/3D7F7AEE5DB8A4EEE0650A00273EBB20
[oracle@uat 3D7F7AEE5DB8A4EEE0650A00273EBB20]$
[oracle@uat 3D7F7AEE5DB8A4EEE0650A00273EBB20]$ ls -lrth
total 348K
-rw-r-----. 1 oracle oinstall 344K Sep 20 22:55 EXPDAT01.DMP
-rw-r--r--. 1 oracle oinstall 1.2K Sep 20 22:55 EXPDAT.LOG
[oracle@uat 3D7F7AEE5DB8A4EEE0650A00273EBB20]$
[oracle@uat 3D7F7AEE5DB8A4EEE0650A00273EBB20]$ hostname
uat.oraeasy.com
[oracle@uat 3D7F7AEE5DB8A4EEE0650A00273EBB20]$
The schema export has completed.
Tablespace
OEM also handles tablespace and datafile management, from viewing usage to creating new tablespaces and extending existing ones.
Step 1: View Existing Tablespaces
Click Administration, then Storage, then Tablespaces.
This lists every tablespace. Click one, such as Sysaux.
This shows the details of the Sysaux tablespace, including size and usage.
Step 2: Create a New Tablespace
On the tablespace list screen, click Create. Provide a name, such as TESTBS.
Click Add in the datafile section, then provide the datafile details.
Provide the file size and extent details, then click Continue.
Review the details, then click OK.
The tablespace has been created.
The new tablespace's details can be viewed the same way as any other.
Step 3: Add a Datafile to an Existing Tablespace
To extend a tablespace, click Edit.
Click Add in the datafile section.
Provide the datafile details, then click OK.
Review the details, then click Apply.
The datafile has been added.
Parameters
Database initialization parameters can also be reviewed and adjusted directly through OEM.
Step 1: View Initialization Parameters
Click Administration, then Initialization Parameters.
This lists every parameter and its current value.
Step 2: Modify a Dynamic Parameter
Parameters like open_cursors can be changed without restarting the database, since they're modifiable at the session or system level on the fly.
The parameter has been modified.
The updated value is now reflected in the parameter list.
That covers the core of day-to-day database management in OEM. There's a lot more to explore under each of these menus, so if there's a specific area you'd like covered in more depth, let us know in the comments. Stay connected!
See below for other articles related to OEM.
OEM 13.5 Installation on Linux
Thank you for reading!
I hope this content has been helpful to you. Your feedback and suggestions are always welcome. Feel free to leave a comment or reach out with any queries.
Abhishek Shrivastava
Oracle DBA with hands-on experience managing production Data Guard, RAC, GoldenGate, and APEX environments. I write practical, tested installation and troubleshooting guides based on real deployment work.
Comments
Post a Comment