How to Recreate Oracle Enterprise Manager Database Control Repository (Complete Oracle DBA Guide)

📅 Last Updated: August 2026

This guide has been fully updated for Oracle Database 10g and 11g Enterprise Edition running Oracle Enterprise Manager Database Control (DBConsole). It explains how to safely diagnose, remove, and recreate the Oracle Enterprise Manager Database Control repository using the Enterprise Manager Configuration Assistant (EMCA).

Oracle Enterprise Manager Database Control (commonly called DBConsole) is an integrated web-based administration tool that enables Oracle Database Administrators (DBAs) to monitor, manage, and maintain Oracle databases from a graphical interface.

In some situations, such as Oracle E-Business Suite cloning, database duplication, incomplete upgrades, repository corruption, hostname changes, or configuration failures, the Enterprise Manager Database Control repository may become corrupted or unusable. When this happens, DBConsole may fail to start, monitoring information may disappear, or administrators may be unable to access Enterprise Manager.

One of the most effective solutions is to recreate the Enterprise Manager repository using the Enterprise Manager Configuration Assistant (EMCA). However, before removing the existing repository, administrators should verify that recreation is actually required and back up the existing configuration whenever possible.

This guide explains Oracle Enterprise Manager architecture, the SYSMAN repository, EMCA utility, troubleshooting procedures, security considerations, Oracle E-Business Suite cloning impacts, and enterprise best practices for safely rebuilding the Database Control repository.

Quick Solution

Verify the current Enterprise Manager configuration, confirm the values of ORACLE_HOME and ORACLE_SID, check the status of Database Control, back up the existing repository if possible, remove the corrupted Database Control configuration using EMCA, recreate the SYSMAN repository, secure the repository, restart Database Control, and verify successful web access.

Problem Description

Oracle Enterprise Manager Database Control may fail due to repository corruption or configuration inconsistencies. Administrators commonly encounter one or more of the following symptoms:

Enterprise Manager Database Control does not start.
Database Control web page is inaccessible.
Repository configuration is corrupted.
EMCA configuration fails.
SYSMAN repository objects become invalid.
Hostname changes after cloning prevent Database Control from starting.
Monitoring data is missing or incomplete.
DBConsole service terminates unexpectedly.

When configuration repair is not sufficient, recreating the Enterprise Manager repository becomes the recommended solution.

Applies To

Oracle Database 10g
Oracle Database 11g
Oracle Enterprise Manager Database Control
Oracle Enterprise Manager Configuration Assistant (EMCA)
Oracle Enterprise Edition
Oracle E-Business Suite environments using Database Control
Linux and UNIX operating systems

What is Oracle Enterprise Manager Database Control?

Oracle Enterprise Manager Database Control (DBConsole) is a web-based management interface designed for administering a single Oracle database. It provides an intuitive graphical interface for performing many routine DBA tasks without requiring command-line utilities.

Using Database Control, administrators can:

Monitor database performance.
Manage users and privileges.
Create and monitor backup jobs.
Review alert logs.
Monitor tablespaces and storage.
View Automatic Workload Repository (AWR) reports.
Monitor sessions and SQL performance.
Configure alerts and notifications.

What is the Database Control Repository?

The Database Control repository is a collection of Oracle schema objects that store monitoring information, management metadata, job history, alerts, configuration settings, and performance data required by Enterprise Manager Database Control.

The repository is primarily owned by the SYSMAN user and works together with the DBSNMP monitoring account to collect and display database information.

If the repository becomes corrupted or inconsistent, Enterprise Manager cannot function correctly.

Understanding EMCA (Enterprise Manager Configuration Assistant)

Enterprise Manager Configuration Assistant (EMCA) is the Oracle utility used to create, configure, reconfigure, secure, and remove Enterprise Manager Database Control repositories.

EMCA automates tasks such as:

Creating the SYSMAN repository.
Configuring Database Control.
Securing Enterprise Manager.
Removing existing configurations.
Recreating the management repository.
Updating Database Control configuration files.

Why Repository Corruption Occurs

Several administrative operations can leave the Enterprise Manager repository in an inconsistent state.

Common causes include:

Oracle E-Business Suite cloning.
Database duplication.
Incomplete EMCA execution.
Hostname or IP address changes.
Database upgrades.
Operating system migration.
Interrupted repository creation.
Manual deletion of SYSMAN objects.
Repository schema corruption.

Business Impact

Although the Oracle database continues running normally, Enterprise Manager Database Control becomes unavailable for administration and monitoring.

Possible impacts include:

Loss of graphical administration tools.
Database monitoring unavailable.
Backup jobs cannot be managed through Enterprise Manager.
Alert notifications stop working.
Performance monitoring becomes unavailable.
AWR and ADDM access through Enterprise Manager is interrupted.
Production monitoring capabilities are reduced.

Prerequisites

SYSDBA privileges.
Operating system access as the Oracle software owner.
Correct ORACLE_HOME environment.
Correct ORACLE_SID setting.
Database must be open.
Backup of the database and Enterprise Manager repository if possible.
Maintenance window for production environments.

Enterprise Manager Database Control Architecture

Oracle Enterprise Manager Database Control consists of several integrated components working together to provide monitoring and administration capabilities. These include the Database Control web application, Oracle Management Agent, the SYSMAN repository schema, the DBSNMP monitoring account, and the Oracle database itself.

When a DBA accesses the Database Control web interface, Enterprise Manager retrieves monitoring data from the SYSMAN repository and displays database health, performance metrics, alerts, storage information, backup status, and administrative options through a browser-based interface.

Why Verification Should Come Before Repository Recreation

Many Enterprise Manager problems are caused by incorrect environment variables, hostname changes, listener configuration issues, or stopped services rather than actual repository corruption. Recreating the repository without first diagnosing the environment can result in unnecessary downtime and loss of historical monitoring data.

Before removing the existing configuration, administrators should verify the current Enterprise Manager status, confirm that the repository is genuinely unusable, and back up the existing configuration whenever possible.

Oracle DBA Recommendation

Do not immediately recreate the Enterprise Manager repository after a DBConsole failure. First verify ORACLE_HOME, ORACLE_SID, Enterprise Manager service status, the SYSMAN and DBSNMP accounts, and repository health. Only recreate the repository after confirming that repair is not possible. This approach minimizes downtime, preserves monitoring history where feasible, and follows Oracle enterprise administration best practices.

Step 1 – Verify ORACLE_HOME and ORACLE_SID

Before making any changes, verify that the Oracle environment variables are correctly configured.

Check the Oracle Home:

echo $ORACLE_HOME

Verify the Oracle SID:

echo $ORACLE_SID

Ensure both values correspond to the database whose Enterprise Manager repository will be recreated.

Step 2 – Verify Enterprise Manager Database Control Status

Check whether Database Control is currently running.

emctl status dbconsole

Possible results include:

Database Control is running normally.
Database Control cannot be started.
Repository configuration is invalid.
Configuration files are missing.

If the service cannot start, continue with the remaining diagnostic steps.

Step 3 – Verify Existing Enterprise Manager Configuration

Display the databases currently configured with Enterprise Manager.

emca -listdb

This confirms whether Database Control has already been configured for the current database.

Step 4 – Verify the SYSMAN and DBSNMP Accounts

Connect as SYSDBA and verify the repository accounts.

sqlplus / as sysdba

Run the following query:

SELECT username,
       account_status
FROM   dba_users
WHERE  username IN ('SYSMAN','DBSNMP');

Confirm that both accounts exist and review their status before recreating the repository.

Step 5 – Back Up the Existing Repository

If the repository is still accessible, create a database backup before removing any Enterprise Manager objects.

At a minimum, perform:

RMAN backup.
Database export (if required).
Backup of Oracle Home.
Backup of Enterprise Manager configuration files.

Backing up the repository allows recovery if recreation is unsuccessful or historical monitoring information must be restored.

Step 6 – Remove the Existing Database Control Configuration

After verifying that repository recreation is required, remove the existing Enterprise Manager configuration using EMCA.

emca -deconfig dbcontrol db

EMCA removes the existing Database Control configuration and prepares the environment for repository recreation.

Step 7 – Recreate the Enterprise Manager Repository

Create a new SYSMAN repository using Enterprise Manager Configuration Assistant.

emca -config dbcontrol db

During execution, EMCA prompts for:

SYS password.
DBSNMP password.
SYSMAN password.
Listener information.
SMTP configuration (optional).

After completion, a new Enterprise Manager repository is created.

Step 8 – Secure Enterprise Manager

Oracle recommends securing Database Control after repository creation.

emctl secure dbconsole

This configures secure communication between the Enterprise Manager console and the database.

Step 9 – Start Database Control

Start the Enterprise Manager Database Control service.

emctl start dbconsole

Verify the service status:

emctl status dbconsole

The output should indicate that Database Control is running successfully.

Step 10 – Verify Web Access

Open a browser and access the Enterprise Manager Database Control URL.

Example:

https://hostname:1158/em

Confirm that:

The login page opens successfully.
SYSMAN authentication works.
Database monitoring information is displayed.
Performance pages load correctly.
Backup and recovery pages are accessible.

Troubleshooting Checklist

Verify ORACLE_HOME.
Verify ORACLE_SID.
Check Database Control status.
Confirm SYSMAN and DBSNMP accounts exist.
Back up the repository before making changes.
Remove the existing Database Control configuration using EMCA.
Recreate the repository.
Secure Database Control.
Restart DBConsole.
Verify browser access and monitoring functionality.

Production Case Study

Following an Oracle E-Business Suite database clone to a new server, Database Control failed to start because the Enterprise Manager repository still referenced the original host configuration. The DBA verified the Oracle environment variables, confirmed that the SYSMAN repository configuration was inconsistent, backed up the database, removed the existing Database Control configuration using EMCA, recreated the repository, secured Database Control, and restarted the DBConsole service. After validating browser access and monitoring functionality, Enterprise Manager resumed normal operation with the new server configuration.

Enterprise Manager Best Practices

Oracle Enterprise Manager Database Control is a critical administration and monitoring tool for Oracle Database environments. Following Oracle best practices helps ensure reliable monitoring, simplified administration, and faster recovery from configuration issues.

Regularly monitor the status of the Database Control service.
Keep Enterprise Manager configuration synchronized after database or host changes.
Use strong passwords for the SYSMAN and DBSNMP accounts.
Enable HTTPS to secure administrative access.
Apply Oracle Release Updates (RUs) and recommended patches.
Document Enterprise Manager configuration changes.
Test backup and recovery procedures for the management repository.

Repository Maintenance Recommendations

The Enterprise Manager repository stores valuable monitoring history and management metadata. Proper maintenance helps maintain long-term stability and performance.

Back up the database regularly using RMAN.
Monitor SYSMAN tablespace usage.
Review Enterprise Manager alert history periodically.
Remove obsolete jobs and alerts when appropriate.
Verify repository health after database upgrades.
Check invalid objects within the SYSMAN schema.
Maintain sufficient archive log space for backup operations.

Oracle E-Business Suite Cloning Considerations

Oracle Enterprise Manager Database Control frequently requires reconfiguration after Oracle E-Business Suite cloning because the cloned database contains references to the original server, hostname, and Enterprise Manager repository configuration.

After every clone, Oracle DBAs should verify:

Hostname resolution.
Listener configuration.
ORACLE_HOME and ORACLE_SID settings.
Enterprise Manager repository status.
SYSMAN and DBSNMP accounts.
Database Control URL accessibility.
Monitoring functionality.

Recreating the repository is often the safest approach when the cloned Enterprise Manager configuration cannot be repaired.

Common Administrator Mistakes

Recreating the repository without verifying the actual problem.
Skipping a database backup before removing the repository.
Using incorrect ORACLE_HOME or ORACLE_SID values.
Ignoring Enterprise Manager log files.
Failing to secure Database Control after recreation.
Leaving default passwords unchanged.
Not verifying the listener configuration before running EMCA.
Neglecting to validate monitoring functionality after recreation.

Related Enterprise Manager Errors

Error	Description
EMCA Configuration Failed	Enterprise Manager repository creation or configuration failed.
DBConsole Service Failed to Start	Database Control service cannot be started.
SYSMAN Repository Corruption	Repository schema is damaged or inconsistent.
OMS Configuration Error	Enterprise Manager configuration files are invalid.
DBSNMP Account Locked	Monitoring account is locked or expired.
EMCTL Status Failed	Enterprise Manager control utility cannot determine service status.

Frequently Asked Questions (FAQ)

Will recreating the Enterprise Manager repository affect the database?

No. Recreating the Database Control repository affects only the Enterprise Manager configuration and its management repository. User data and application schemas within the Oracle database remain unchanged.

Will historical monitoring data be preserved?

Generally, no. Recreating the SYSMAN repository creates a new management repository, and historical Enterprise Manager monitoring data is typically lost unless it has been backed up and restored separately.

When should I recreate the repository?

Recreate the repository only after confirming that Enterprise Manager configuration repair is not possible and the existing repository is corrupted or unusable.

Can I use EMCA multiple times?

Yes. EMCA can be used to configure, deconfigure, secure, and recreate Enterprise Manager Database Control whenever administrative maintenance requires it.

Is Database Control available in newer Oracle Database releases?

No. Oracle Enterprise Manager Database Control was available in Oracle Database 10g and 11g. Beginning with Oracle Database 12c, Oracle recommends using Oracle Enterprise Manager Cloud Control instead of Database Control.

About the Author

Rana Abdul Wahid is an Oracle Database and Oracle E-Business Suite Consultant with more than 15 years of experience in Oracle Database Administration, Oracle Enterprise Manager, Oracle E-Business Suite Application DBA, Oracle RAC, Oracle Data Guard, Oracle Cloud Infrastructure (OCI), RMAN Backup & Recovery, Linux/Unix Administration, MySQL, Microsoft SQL Server, PostgreSQL, and enterprise infrastructure management.

His expertise includes Oracle Enterprise Manager administration, database monitoring, Oracle E-Business Suite cloning, backup and recovery, performance tuning, Linux administration, and enterprise production support.

Learn more about the author →

Conclusion

Recreating the Oracle Enterprise Manager Database Control repository is a reliable solution for resolving repository corruption, configuration inconsistencies, and Database Control failures that commonly occur after cloning, database migration, hostname changes, or incomplete Enterprise Manager configuration.

By first verifying the Oracle environment, confirming repository health, backing up the existing configuration, safely removing the old repository with EMCA, recreating the SYSMAN repository, securing Database Control, and validating browser access, administrators can restore full Enterprise Manager functionality while minimizing downtime and preserving a stable administration environment.

Final Oracle DBA Recommendation

Treat Enterprise Manager repository recreation as a controlled maintenance activity rather than a first-response troubleshooting step. Always verify the root cause, back up the database, document the existing configuration, and test Database Control thoroughly after recreation. Following Oracle-supported procedures helps maintain a secure, reliable, and production-ready Enterprise Manager environment.

Found this guide helpful? Visit the Oracle Error Codes Guide for more Oracle Database, Oracle Enterprise Manager, Oracle E-Business Suite, Linux administration, and enterprise troubleshooting articles.

Oracle Database Error Solutions & DBA Knowledge Base