Error in Invoking Target 'agent nmhs' of Makefile During Oracle Database 11.2.0.4 Installation on Oracle Linux 7

📅 Last Updated: August 2026

This guide has been fully updated for Oracle Database 11.2.0.4 installations on Oracle Linux 7. It explains the causes of the "Error in invoking target 'agent nmhs' of makefile" installation failure, how to analyze Oracle installation logs, understand the linker error, apply the recommended workaround, and follow Oracle best practices to complete the installation successfully.

Oracle Database 11.2.0.4 remains widely deployed in enterprise environments because of long-term application compatibility and legacy system requirements. During installation on Oracle Linux 7 or Red Hat Enterprise Linux 7, administrators may encounter a compilation failure while Oracle Universal Installer (OUI) attempts to build Enterprise Manager components.

The installation usually stops during the linking phase with the following message:

Error in invoking target 'agent nmhs' of makefile
'$ORACLE_HOME/sysman/lib/ins_emagent.mk'

Although the error appears critical, it is a known Oracle Database 11.2.0.4 issue related to the Enterprise Manager agent build process. In most cases, the database software installation can be completed successfully after applying the documented workaround or Oracle's recommended patch.

Quick Solution

Verify the Oracle Linux version, confirm the Oracle Database release, review the installation logs, locate the ins_emagent.mk makefile, back up the original file, modify the linker command by adding the required -lnnz11 library, retry the failed installation step from Oracle Universal Installer, verify that the linking process completes successfully, and apply the appropriate Oracle patch if available.

Complete Error Message

Oracle Universal Installer may display an error similar to the following:

Error in invoking target 'agent nmhs' of makefile

$ORACLE_HOME/sysman/lib/ins_emagent.mk

Additional linker errors are typically recorded inside the Oracle installation log files and the make log.

Applies To

Oracle Database 11.2.0.4
Oracle Linux 7
Red Hat Enterprise Linux (RHEL) 7
Oracle Enterprise Manager Database Control
Oracle Universal Installer (OUI)
Oracle Grid Infrastructure 11.2.0.4 (related environments)

Symptoms

Administrators commonly observe one or more of the following symptoms during installation:

Oracle Universal Installer stops unexpectedly.
The installer reports Error in invoking target 'agent nmhs'.
Installation pauses during the linking stage.
The Retry button continues to fail.
The Enterprise Manager component cannot be compiled.
Installation logs contain linker-related errors.

What Causes This Error?

This problem occurs because Oracle Database 11.2.0.4 was originally released before Oracle Linux 7 became widely adopted. During installation, Oracle Universal Installer executes several makefiles to compile Oracle binaries and Enterprise Manager components.

One of these makefiles, ins_emagent.mk, attempts to link Enterprise Manager executables. On Oracle Linux 7, the required Oracle security library is not linked correctly, causing the compilation process to fail.

As a result, Oracle Universal Installer reports the makefile failure even though the remainder of the software installation is generally unaffected.

Oracle Bug 19692824 Overview

This installation issue is associated with Oracle Bug 19692824, which affects Oracle Database 11.2.0.4 installations on Oracle Linux 7 and compatible Red Hat Enterprise Linux platforms.

Oracle provides an official patch for this issue. Where the patch is not immediately available, Oracle documents a supported workaround that modifies the Enterprise Manager makefile before retrying the installation.

Why Does the Linker Fail?

During installation, Oracle executes GNU make to build Enterprise Manager binaries. The make process invokes several linker commands that combine Oracle object files and shared libraries into executable programs.

In this specific case, the required Oracle Network Security library (libnnz11) is not linked correctly. Because the linker cannot resolve the required symbols, the build process terminates and Oracle Universal Installer reports the makefile failure.

Oracle Installation Architecture

Understanding the Oracle installation workflow makes troubleshooting significantly easier.

Oracle Universal Installer copies the software.
Oracle inventory is updated.
Oracle libraries are extracted.
Oracle binaries are compiled.
Makefiles build executable files.
Enterprise Manager components are linked.
Configuration assistants complete installation.

The agent nmhs error occurs during the Enterprise Manager linking stage.

Prerequisites

Oracle Linux 7 server.
Oracle Database 11.2.0.4 installation media.
Oracle software owner account.
Root or sudo privileges (when required).
Proper Oracle prerequisite packages installed.
Configured Oracle environment variables.
Sufficient disk space.
Access to Oracle installation log files.

Important Oracle Files Involved

File	Purpose
`ins_emagent.mk`	Enterprise Manager makefile
`make.log`	Compilation and linker log
`installActions*.log`	Oracle Universal Installer log
`libnnz11.so`	Oracle Network Security library

Why Collect Diagnostic Information First?

Many administrators immediately edit the makefile after seeing the installation error. However, the same message can occasionally be triggered by missing prerequisite packages, incomplete Oracle environment configuration, incorrect permissions, or installation media corruption.

Before modifying any Oracle installation files, verify the operating system version, Oracle release, installation logs, OPatch version, and the location of the affected makefile. This approach ensures that the workaround is applied only after confirming the actual cause of the failure.

Oracle DBA Recommendation

Always analyze the Oracle installation logs before applying manual fixes. Back up the original ins_emagent.mk file before making any modifications, document the change for future maintenance, and apply Oracle Patch 19692824 whenever it is available. Following Oracle's recommended installation and patching procedures provides the most reliable long-term solution for enterprise environments.

Step 1 – Verify the Oracle Linux Version

Before troubleshooting the installation failure, verify the Oracle Linux version.

cat /etc/os-release

Example output:

NAME="Oracle Linux Server"
VERSION="7.9"
ID="ol"

This issue is commonly encountered on Oracle Linux 7 and compatible Red Hat Enterprise Linux 7 systems.

Step 2 – Verify the Oracle Database Release

Confirm that you are installing Oracle Database 11.2.0.4.

If the Oracle Home has already been partially created, verify the installed software version:

$ORACLE_HOME/OPatch/opatch version

Also verify the OPatch utility version, as Oracle may require an updated OPatch release before applying patches.

Step 3 – Review Oracle Universal Installer Logs

Before modifying any files, review the Oracle installation logs to identify the exact cause of the failure.

Display the latest Oracle Universal Installer log:

tail -100 $ORACLE_BASE/oraInventory/logs/installActions*.log

Next, review the Oracle make log:

tail -100 $ORACLE_HOME/install/make.log

Look for linker errors related to agent nmhs, ins_emagent.mk, or unresolved references to libnnz11.

Step 4 – Locate the ins_emagent.mk File

Verify the location of the Enterprise Manager makefile.

find $ORACLE_HOME -name ins_emagent.mk

The file is typically located at:

$ORACLE_HOME/sysman/lib/ins_emagent.mk

Step 5 – Back Up the Original Makefile

Before making any modifications, create a backup of the original file.

cd $ORACLE_HOME/sysman/lib

cp ins_emagent.mk ins_emagent.mk.bak

Retaining the original file allows you to restore the Oracle Home if necessary.

Step 6 – Modify the Makefile

Open the makefile using your preferred text editor.

vi ins_emagent.mk

Locate the following linker command:

$(MK_EMAGENT_NMECTL)

Modify it by appending the Oracle Network Security library:

$(MK_EMAGENT_NMECTL) -lnnz11

Save the file and exit the editor.

Why Does This Modification Work?

The additional -lnnz11 parameter explicitly links the Oracle Network Security library during the Enterprise Manager build process. This resolves the missing symbol references that cause the linker to terminate with the agent nmhs error.

After the library is included, Oracle Universal Installer is generally able to complete the Enterprise Manager compilation successfully.

Step 7 – Retry the Installation

Return to the Oracle Universal Installer window.

Click the Retry button.

Oracle Universal Installer re-executes the modified makefile and attempts to rebuild the Enterprise Manager components.

Step 8 – Verify Successful Linking

If the workaround is successful, Oracle Universal Installer continues with the remaining installation steps.

Review the make log again to confirm there are no additional linker failures.

tail -50 $ORACLE_HOME/install/make.log

The log should no longer report the agent nmhs compilation error.

Step 9 – Alternative Solution: Apply Oracle Patch 19692824

Oracle recommends applying Patch 19692824, which permanently resolves this known issue for Oracle Database 11.2.0.4.

Verify the current OPatch version before applying the patch:

$ORACLE_HOME/OPatch/opatch version

If necessary, update OPatch to the required version before installing the Oracle patch.

Step 10 – Validate the Oracle Home

After installation completes successfully, verify that the Oracle binaries exist and that the Oracle Home is functioning correctly.

ls -l $ORACLE_HOME/bin/oracle

You should also verify that Oracle Universal Installer reports a successful installation.

Troubleshooting Checklist

Verify the Oracle Linux version.
Confirm that Oracle Database 11.2.0.4 is being installed.
Review installActions*.log.
Review make.log.
Locate ins_emagent.mk.
Create a backup before editing.
Add -lnnz11 to $(MK_EMAGENT_NMECTL).
Retry the failed installation step.
Verify that the linker completes successfully.
Apply Oracle Patch 19692824 for a permanent fix when available.

Production Case Study

During an Oracle Database 11.2.0.4 deployment on Oracle Linux 7.9, the Oracle Universal Installer stopped during the Enterprise Manager compilation stage with the message "Error in invoking target 'agent nmhs' of makefile". The DBA reviewed the installation logs, confirmed that the failure originated from ins_emagent.mk, created a backup of the makefile, added the -lnnz11 linker option, and clicked Retry in Oracle Universal Installer. The linking process completed successfully, the installation finished without further errors, and Oracle Patch 19692824 was later applied during post-installation maintenance to permanently resolve the issue.

Oracle Installation Best Practices

Successful Oracle Database installations depend on proper operating system preparation, prerequisite verification, and adherence to Oracle's documented installation procedures. Enterprise environments should always validate the software stack before beginning production deployments.

Install Oracle Database only on certified Oracle Linux versions.
Verify all prerequisite operating system packages before installation.
Use the latest supported OPatch utility.
Create a backup before modifying Oracle installation files.
Review Oracle installation logs before applying manual workarounds.
Document every change made during installation.
Perform installations during scheduled maintenance windows.
Apply the latest Oracle Release Updates (RUs) and recommended patches after installation.

Oracle Patch 19692824 Recommendations

The agent nmhs makefile error is associated with Oracle Bug 19692824. Although modifying the ins_emagent.mk file allows the installation to continue, Oracle recommends applying the corresponding patch whenever it is available for your environment.

Benefits of applying the Oracle patch include:

Permanent resolution of the linker issue.
Reduced need for manual modifications.
Improved installation reliability.
Compliance with Oracle support recommendations.
Simplified future maintenance activities.

Oracle Linux Compatibility Notes

Oracle Database 11.2.0.4 was originally released before Oracle Linux 7 became the standard enterprise platform. As a result, some installation components require additional compatibility adjustments during installation.

Component	Status
Oracle Database 11.2.0.4	Supported with required patches
Oracle Linux 7	Supported
Oracle Universal Installer	Supported
Enterprise Manager Components	May require workaround or patch
OPatch	Keep updated

Post-Installation Validation

After Oracle Database installation completes successfully, perform the following validation steps to ensure the Oracle Home is functioning correctly.

$ORACLE_HOME/bin/sqlplus -v

$ORACLE_HOME/OPatch/opatch lsinventory

ls -l $ORACLE_HOME/bin/oracle

Confirm that Oracle binaries exist, OPatch reports a healthy inventory, and no additional installation errors are present in the Oracle logs.

Common Administrator Mistakes

Ignoring Oracle installation log files.
Editing the makefile without creating a backup.
Applying the workaround to the wrong Oracle Home.
Using an outdated OPatch version.
Skipping prerequisite verification.
Ignoring Oracle certification requirements.
Not applying Oracle Patch 19692824 after installation.
Assuming every linker error has the same root cause.

Frequently Asked Questions (FAQ)

Does this error prevent Oracle Database from being installed?

Not necessarily. In most cases, the installation can be completed successfully after applying the documented workaround or Oracle's recommended patch.

Which Oracle versions are affected?

This issue is primarily associated with Oracle Database 11.2.0.4 installations on Oracle Linux 7 and compatible Red Hat Enterprise Linux 7 systems.

Why is the `libnnz11` library required?

The Oracle Network Security library provides required symbols during the Enterprise Manager linking process. Adding -lnnz11 resolves the missing library reference that causes the linker to fail.

Should I edit the makefile permanently?

The makefile modification is an installation workaround. Oracle recommends applying the appropriate Oracle patch for a permanent supported solution whenever possible.

Can this issue occur on newer Oracle Database releases?

The problem is primarily associated with Oracle Database 11.2.0.4. Newer supported Oracle Database releases contain updated installation components and are generally not affected by this specific linker issue.

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 E-Business Suite Application DBA, Oracle Cloud Infrastructure (OCI), Oracle RAC, Oracle Data Guard, RMAN Backup and Recovery, Linux/UNIX administration, MySQL, Microsoft SQL Server, PostgreSQL, and enterprise database infrastructure.

His experience includes Oracle software installation, database migration, patch management, performance tuning, backup and recovery, disaster recovery planning, Oracle Linux administration, and production support for mission-critical enterprise environments.

Learn more about the author →

Conclusion

The "Error in invoking target 'agent nmhs' of makefile" is a well-known Oracle Database 11.2.0.4 installation issue that commonly occurs during Enterprise Manager compilation on Oracle Linux 7. Although the installation stops at the linking stage, the problem can usually be resolved by identifying the root cause, reviewing the installation logs, applying the documented ins_emagent.mk workaround, and then retrying the failed installation step.

For long-term stability and Oracle Support compliance, administrators should update OPatch, apply Oracle Patch 19692824, and validate the Oracle Home after installation. Following Oracle's recommended installation procedures and maintaining detailed documentation helps ensure reliable, repeatable, and production-ready Oracle Database deployments.

Final Oracle DBA Recommendation

Always investigate Oracle installation failures using installActions*.log and make.log before applying manual fixes. Preserve original configuration files, use supported Oracle workarounds only when necessary, keep OPatch current, and apply Oracle Patch 19692824 to permanently resolve this known linker issue. A disciplined installation and patch management process minimizes downtime and ensures a stable, supportable Oracle Database environment.

Found this guide helpful? Visit the Oracle Error Codes Guide for more Oracle Database, Oracle E-Business Suite, Oracle Linux, and Oracle Cloud Infrastructure troubleshooting tutorials.

Oracle Database Error Solutions & DBA Knowledge Base