Linux: Locate a file by name and then search for a specific word inside

June 30, 2025 Leave a comment

If you’ve ever needed to locate a file by name and then search for a specific word inside it, then this blog is for you.
Linux makes it simple by combining two powerful tools: find and grep:

# find /your/path -type f -name "*.log" -exec grep -i "error" {} +

Explanation:

  • -type f: Filters for files only.
  • -name "*.log": Limits the search to .log files.
  • -exec grep -i "error" {} +: Searches for the word "error" inside each found file, ignoring case sensitivity.

In my case, I was searching for files named flashgrid_node and then wanted to find content containing the keyword “SYNCING“. Here is my command version:

# find ./ -type f -name "flashgrid_node" -exec grep -i "SYNCING" {} +

It searches in the current directory (‘./’).

Useful tip, If you want to show only the file names that contain the word, you can add the -l flag to grep:

# find /your/path -type f -name "*.log" -exec grep -il "error" {} +

This was my output:

$ find ./ -type f -name "flashgrid_node" -exec grep -il "SYNCING" {} +

./rac1/rac1.example.com/flashgrid_node
./rac2/rac2.example.com/flashgrid_node
./racq/racq.example.com/flashgrid_node

Filed under Linux, Oracle Enterprise Linux, OS Tagged with , , , ,

Azure: Find the number of Fault Domains for region

June 26, 2025 Leave a comment

A fault domain is a logical grouping of hardware within a data center that shares a common power source and network switch.

In cloud environments like Microsoft Azure or Oracle Cloud, fault domains help improve high availability by ensuring that resources (like virtual machines) are distributed across isolated hardware. This way, if a failure occurs in one fault domain (e.g., a power outage or hardware failure), it doesn’t affect the other domains.

In clustered environments such as Oracle RAC and others, it is highly recommended to distribute database nodes across different Availability Zones (preferably within close proximity). However, if the selected region does not support Availability Zones, or if the network latency between AZs is too high, you can instead distribute the nodes across different fault domains to ensure fault tolerance at the power and network switch level.

To verify how many fault domains are supported in your chosen region, run the following script from Azure CLI:

az vm list-skus --resource-type availabilitySets --query '[?name==`Aligned`].{Location:locationInfo[0].location, MaximumFaultDomainCount:capabilities[0].value}' -o Table

The output by June 11, 2025, is as follows (subject to change in the future):

Location            MaximumFaultDomainCount
------------------  -------------------------
AustraliaCentral    2
AustraliaCentral2   2
australiaeast       2
australiasoutheast  2
AustriaEast         2
BelgiumCentral      2
brazilsouth         3
BrazilSoutheast     2
CanadaCentral       3
CanadaEast          2
CentralIndia        3
centralus           3
CentralUSEUAP       1
ChileCentral        2
DenmarkEast         2
eastasia            2
eastus              3
eastus2             3
EastUS2EUAP         2
EastUSSTG           1
FranceCentral       3
FranceSouth         2
GermanyNorth        2
GermanyWestCentral  2
IndonesiaCentral    2
IsraelCentral       2
IsraelNorthwest     2
ItalyNorth          2
japaneast           3
japanwest           2
JioIndiaCentral     2
JioIndiaWest        2
KoreaCentral        2
KoreaSouth          2
MalaysiaSouth       2
MalaysiaWest        2
MexicoCentral       2
NewZealandNorth     2
northcentralus      3
northeurope         3
NorwayEast          2
NorwayWest          2
PolandCentral       2
QatarCentral        2
SouthAfricaNorth    2
SouthAfricaWest     2
southcentralus      3
SouthCentralUS2     2
SouthCentralUSSTG   2
southeastasia       2
SoutheastUS         2
SoutheastUS3        2
SoutheastUS5        2
SouthIndia          2
SouthwestUS         2
SpainCentral        2
SwedenCentral       3
SwedenSouth         2
SwitzerlandNorth    2
SwitzerlandWest     2
TaiwanNorth         2
TaiwanNorthwest     2
UAECentral          2
UAENorth            2
uksouth             2
ukwest              2
westcentralus       2
westeurope          3
WestIndia           2
westus              3
westus2             3
WestUS3             3

Filed under Azure Tagged with , , , , , , ,

EM 24ai: Applying Management Agent Release Update (RU) from the EM web interface

June 23, 2025 Leave a comment

Prerequisites

Before installing or uninstalling the RU, ensure that you meet the following requirements:

  1. Apply EM 24ai Release 1 Update 2 Patch 37629905 or it’s later Release Update version patch on the OMS before applying this RU.

    If you have not done this already, you can check my previous post.
  2. Deinstall this RU before deinstalling Enterprise Manager 24ai Release 1 Update 2 Patch 37629905 on OMS.

Installation

1. Login to the Enterprise Manager and navigate to Enterprise -> My Oracle Support -> Patches & Updates:

2. Enter the patch number (e.g. 37629915) in the “Software Library Patch Search” section and click Search:

3. Select the patch and click “Create Plan.” :

4. Enter the plan name and select the target agent:

5. Click the “Patches & Updates” hyperlink in the upper left corner:

6. Click on the plan name:

7. Click Next:

8. Click Next:

9. Deployment options:

In the Stage location, retain the default location (%emd_emstagedir%) available on the target machine, or edit the Stage Location to provide a new location for staging the Management Agent patches.
In the Oracle Home Credentials section, select Oracle Home Preferred Credentials if you have already set them earlier. You can otherwise click Override (like me):

9. Click “Select…” next to “Privileged Credentials,” then choose “New” in the pop-up window:

10. Click Validate Credentials:

11. Click Analyze:

If analysis fails, click Show Detailed Results:

To view the complete log, click on “Download Logs” in the upper right corner. Correct failed components. In my case, I did not have enough swap space; after increasing it, I re-analyzed and it became ready for deployment:

12. Click ‘Next’ and then ‘Deploy’. Select your desired time; I will choose immediately and click ‘Submit’.

13. The deployment status:

The deployment is in progress:

The deployment was successful:

14. You can check the applied patch using agentpatcher as well:

Set the oraclehome to proper agenthome and run lspatches:

$ export ORACLE_HOME=/u03/em24/agent/agent_24.1.0.0.0
$ /u03/em24/agent/agent_24.1.0.0.0/AgentPatcher/agentpatcher lspatches
…
oracle.sysman.si.agent.plugin/24.1.1.0.0          Plugin              37629915            37629956            Oracle Enterprise Manager for Systems Infrastructure 24ai Release 1 Plug-in Update 2 (24.1.1.2) for Oracle Management Agent

Filed under EM Tagged with , , , , , , ,

Linux: Add passwordless sudo permission to user

June 19, 2025 1 Comment

In this blog, I will provide passwordless sudo permission to oracle user for testing purposes. Change the username as needed.

1. As the root user, create a separate group for the purpose of granting sudo privileges. Choose a desired name for the group.

# groupadd oracle_sudoers

2. Use the usermod command to add the oracle user to the group:

# usermod -aG oracle_sudoers oracle

3. Update /etc/sudoers using visudo command

# visudo

Add the following line:

%oracle_sudoers ALL=(ALL) NOPASSWD: ALL

Explanation (read carefully):

PartMeaning
%oracle_sudoersRefers to a Linux user group called oracle_sudoers. The % symbol means “group” and not a specific user. So this applies to all users who are members of this group.
ALL=(ALL)Members can run commands as any user, including root.
The first ALL refers to any host (typically used in multi-host sudo configs).
The (ALL) means as any target user.
NOPASSWD:Allows these users to run sudo commands without being prompted for a password.
ALLThey are allowed to run any command with sudo. You can also restrict the group to execute only the specific commands you designate in this section.

⚠️ Security Note:

This provides full root-level access without password prompts to members of oracle_sudoers, so it should be used with caution and only for trusted administrative users (e.g., DBAs or sysadmins).

Filed under Linux, Oracle Enterprise Linux, OS Tagged with , , , , ,

EM 24ai: Apply RU02 (24.1.0.2) on Oracle Management Service

June 16, 2025 1 Comment

The blog may appear extensive, but most of the content consists of the output from the command. The reason for including the output is to allow for comparison.

1. Ensure that you have OMSPatcher version 13.9.24.4.0

$ $ORACLE_HOME/OMSPatcher/omspatcher version

If the version returned is lower than that, which it most likely is, then you need to update OMSPatcher in the OMS home.

To update OMSPatcher, please follow the steps outlined below:

1.1. Download patch 19999993 for EM 24.1.0.0.0 (for your version) from My Oracle Support

1.2. Backup the current “OMSPatcher” folder

$ mv <MIDDLEWARE_HOME>/OMSPatcher <MIDDLEWARE_HOME>/OMSPatcher_backup

For example:

$ mv /u03/em24/middleware/oms_home/OMSPatcher /u03/em24/middleware/oms_home/OMSPatcher_backup

1.3. Unzip the “p19999993_241000_Generic.zip” under /u03/em24/middleware/oms_home

$ unzip /u03/install/p19999993_241000_Generic.zip -d /u03/em24/middleware/oms_home

1.4. Check the version again and make sure the version is correct

$ export ORACLE_HOME=/u03/em24/middleware/oms_home
$ $ORACLE_HOME/OMSPatcher/omspatcher version

OMSPatcher Version: 13.9.24.4.0
OPlan Version: 12.2.0.1.16
OsysModel build: Tue Apr 28 18:16:31 PDT 2020

2. Analyze the patch before actual application to ensure that all prerequisites are met:

$ /u03/em24/middleware/oms_home/OMSPatcher/omspatcher apply -analyze 37629905/

OMSPatcher Automation Tool
Copyright (c) 2024, Oracle Corporation.  All rights reserved.

OMSPatcher version : 13.9.24.4.0
OUI version        : 13.9.4.0.0
Running from       : /u03/em24/middleware/oms_home
Log file location  : /u03/em24/middleware/oms_home/cfgtoollogs/omspatcher/opatch2025-06-05_02-31-25AM_1.log

OMSPatcher log file: /u03/em24/middleware/oms_home/cfgtoollogs/omspatcher/37629905/omspatcher_2025-06-05_02-31-44AM_analyze.log

Please enter OMS weblogic admin server URL(t3s://mk23ai-b:7102):>
Please enter OMS weblogic admin server username(weblogic):>
Please enter OMS weblogic admin server password:>

Enter SYS or Non-SYS (Admin User) username: sys
Enter 'sys' password :
Checking if current repository database is a supported version
Current repository database version is supported

Prereq "checkComponents" for patch 37616329 passed.
Prereq "checkComponents" for patch 37616365 passed.
Prereq "checkComponents" for patch 37616341 passed.
Prereq "checkComponents" for patch 37616358 passed
Prereq "checkComponents" for patch 37616336 passed.
Prereq "checkComponents" for patch 37616362 passed.
Prereq "checkComponents" for patch 37616375 passed.

Configuration Validation: Success

Running apply prerequisite checks for sub-patch(es) "37616375" and Oracle Home "/u03/em24/middleware/ext_oms_home"...
Sub-patch(es) "37616375" are successfully analyzed for Oracle Home "/u03/em24/middleware/ext_oms_home"

Running apply prerequisite checks for sub-patch(es) "37616362,37616329,37616358,37616341,37616336,37616365" and Oracle Home "/u03/em24/middleware/oms_home"...
Sub-patch(es) "37616362,37616329,37616358,37616341,37616336,37616365" are successfully analyzed for Oracle Home "/u03/em24/middleware/oms_home"

Complete Summary
================

All log file names referenced below can be accessed from the directory "/u03/em24/middleware/oms_home/cfgtoollogs/omspatcher/2025-06-05_02-31-25AM_SystemPatch_37629905_1"

Prerequisites analysis summary:
-------------------------------

The following sub-patch(es) are applicable:

Featureset         Sub-patches  Log file
----------         -----------  --------
  oracle.sysman.top.oms   37616362,37616329,37616358,37616341,37616336,37616365   37616362,37616329,37616358,37616341,37616336,37616365_opatch2025-06-05_02-35-33AM_2.log
  oracle.sysman.top.zdt                                              37616375                                                
37616375_opatch2025-06-05_02-35-19AM_2.log

The following sub-patches are not needed by any component installed in the OMS system:
37465809,37616360,37616345,37616371

Log file location: /u03/em24/middleware/oms_home/cfgtoollogs/omspatcher/37629905/omspatcher_2025-06-05_02-31-44AM_analyze.log

OMSPatcher succeeded.

3. Installing the Release Update using a traditional patching method

3.1. Set the ORACLE_HOME to the location of the OMS home, and ensure the bin directory from the OMS home is included in the PATH environment variable:

$ export ORACLE_HOME=/u03/em24/middleware/oms_home
$ export PATH=$ORACLE_HOME/bin:$PATH

3.2. Shut down the OMS:

$ emctl stop oms

Oracle Enterprise Manager 24ai Release 1
Copyright (c) 1996, 2024 Oracle Corporation.  All rights reserved.
Stopping Oracle Management Server...
Oracle Management Server Successfully Stopped
Oracle Management Server is Down
JVMD Engine is Down

3.3. Navigate to the patch 37629905 directory and run apply

$ cd 37629905
$ /u03/em24/middleware/oms_home/OMSPatcher/omspatcher apply ./

OMSPatcher Automation Tool
Copyright (c) 2024, Oracle Corporation.  All rights reserved.

OMSPatcher version : 13.9.24.4.0
OUI version        : 13.9.4.0.0
Running from       : /u03/em24/middleware/oms_home
Log file location  : /u03/em24/middleware/oms_home/cfgtoollogs/omspatcher/opatch2025-06-05_03-04-16AM_1.log

OMSPatcher log file: /u03/em24/middleware/oms_home/cfgtoollogs/omspatcher/37629905/omspatcher_2025-06-05_03-04-37AM_apply.log

Please enter OMS weblogic admin server URL(t3s://mk23ai-b:7102):>
Please enter OMS weblogic admin server username(weblogic):>
Please enter OMS weblogic admin server password:>

Enter SYS or Non-SYS (Admin User) username: sys
Enter 'sys' password :
Checking if current repository database is a supported version
Current repository database version is supported

Prereq "checkComponents" for patch 37616329 passed.
Prereq "checkComponents" for patch 37616365 passed.
Prereq "checkComponents" for patch 37616341 passed.
Prereq "checkComponents" for patch 37616358 passed.
Prereq "checkComponents" for patch 37616336 passed.
Prereq "checkComponents" for patch 37616362 passed.
Prereq "checkComponents" for patch 37616375 passed.

Configuration Validation: Success

Running apply prerequisite checks for sub-patch(es) "37616375" and Oracle Home "/u03/em24/middleware/ext_oms_home"...
Sub-patch(es) "37616375" are successfully analyzed for Oracle Home "/u03/em24/middleware/ext_oms_home"

Running apply prerequisite checks for sub-patch(es) "37616362,37616329,37616358,37616341,37616336,37616365" and Oracle Home "/u03/em24/middleware/oms_home"...
Sub-patch(es) "37616362,37616329,37616358,37616341,37616336,37616365" are successfully analyzed for Oracle Home "/u03/em24/middleware/oms_home"

To continue, OMSPatcher will do the following:
[Patch and deploy artifacts]   : Apply sub-patch(es) [ 37616329 37616336 37616341 37616358 37616362 37616365 37616375 ]
                                 Apply sub-patch(es) [ 37616329 37616336 37616341 37616358 37616362 37616365 37616375 ]
                                 Apply RCU artifact with patch "/u03/em24/middleware/oms_home/.omspatcher_storage/37616329_May_13_2025_03_57_04/original_patch";
                                 Apply RCU artifact with patch "/u03/em24/middleware/ext_oms_home/.omspatcher_storage/37616375_May_13_2025_05_14_54/original_patch";
                                 Apply RCU artifact with patch "/u03/em24/middleware/oms_home/.omspatcher_storage/37616365_May_13_2025_05_15_38/original_patch";
                                 Apply RCU artifact with patch "/u03/em24/middleware/oms_home/.omspatcher_storage/37616341_May_13_2025_05_15_15/original_patch";
                                 Apply RCU artifact with patch "/u03/em24/middleware/oms_home/.omspatcher_storage/37616358_May_13_2025_05_15_47/original_patch";
                                 Apply RCU artifact with patch "/u03/em24/middleware/oms_home/.omspatcher_storage/37616336_May_13_2025_05_16_05/original_patch";
                                 Apply RCU artifact with patch "/u03/em24/middleware/oms_home/.omspatcher_storage/37616362_May_13_2025_05_16_27/original_patch";
                                 Register MRS artifact "assoc";
                                 Register MRS artifact "procedures";
                                 Register MRS artifact "commands";
                                 Register MRS artifact "omsPropertyDef";
                                 Register MRS artifact "targetType";
                                 Register MRS artifact "default_collection";
                                 Register MRS artifact "jobTypes";
                                 Register MRS artifact "systemStencil";
                                 Register MRS artifact "discovery";
                                 Register MRS artifact "EcmMetadataOnlyRegistration";
                                 Register MRS artifact "namedQuery";
                                 Register MRS artifact "storeTargetType";
                                 Register MRS artifact "swlib";
                                 Register MRS artifact "OracleCertifiedTemplate";
                                 Register MRS artifact "TargetPrivilege";
                                 Register MRS artifact "gccompliance";
                                 Register MRS artifact "runbooks"


Do you want to proceed? [y|n]
y
Could not recognize input. Please re-enter.
y
User Responded with: Y
Stopping all the services on primary OMS.....
Please monitor log file: /u03/em24/middleware/oms_home/cfgtoollogs/omspatcher/2025-06-05_03-29-16AM_SystemPatch_37629905_9/stop_oms_all_2025-06-05_03-29-16AM.log
Stopping the Central agent .....

Applying the one-off patch  .....

Applying sub-patch(es) "37616329,37616336,37616341,37616358,37616362,37616365"
Please monitor log file: /u03/em24/middleware/oms_home/cfgtoollogs/opatch/opatch2025-06-05_03-39-19AM_4.log
Applying sub-patch(es) "37616375"
Please monitor log file: /u03/em24/middleware/ext_oms_home/cfgtoollogs/opatch/opatch2025-06-05_03-46-21AM_5.log

Starting the ADMIN .....
Please monitor log file: /u03/em24/middleware/oms_home/cfgtoollogs/omspatcher/2025-06-05_03-46-50AM_SystemPatch_37629905_14/start_admin_2025-06-05_03-46-50AM.log

Configure API Gateway  .....
Please monitor log file: /u03/em24/middleware/oms_home/cfgtoollogs/omspatcher/2025-06-05_03-48-17AM_SystemPatch_37629905_15/config_apigateway_2025-06-05_03-48-17AM.log

Registering the start OP ......

DB user 'sys' is allowed to perform startOP patching operation.
Update the patching flag .....

Updating repository with RCU reference file "/u03/em24/middleware/oms_home/.omspatcher_storage/37616329_May_13_2025_03_57_04/original_patch"

<This block has been intentionally secluded>

Registering service "jobTypes" with register file "/u03/em24/middleware/oms_home/plugins/oracle.sysman.db.oms.plugin_24.1.1.0.0/metadata/jobTypes/DGFileTransfer.xml" for plugin id as "oracle.sysman.db"...
...
Starting the central agent .....
Resetting the patching flag .....
Resetting the job queue process .....
The job_queue_processes parameter is set to 0 in the repository database. Resetting the job_queue_processes parameter to its original value 248 in the repository database to start the OMS.
Registering the end OP ......

DB user 'sys' is allowed to perform endOP patching operation.
Running the post apply sql .....
Starting the oms
...

Patching summary:
-----------------

Binaries of the following sub-patch(es) have been applied successfully:

Featureset      Sub-patches Log file
----------      ----------- --------
oracle.sysman.top.zdt_24.1.0.0.0  37616375 37616375_opatch2025-06-05_03-46-21AM_5.log
oracle.sysman.top.oms_24.1.0.0.0   37616329,37616336,37616341,37616358,37616362,37616365   37616329,37616336,37616341,37616358,37616362,37616365_opatch2025-06-05_03-39-19AM_4.log

The following sub-patches are not needed by any component installed in the OMS system:
37465809,37616360,37616345,37616371
...
OMSPatcher succeeded

3.4. Make sure that omspatcher started OMS automatically, that is also visible from the above output (3.3 step):

$ export ORACLE_HOME=/u03/em24/middleware/oms_home
$ emctl status oms

WebTier is Up
Oracle Management Server is Up
JVMD Engine is Up

Otherwise, start it manually:

$ emctl start oms

4. Review the inventory to confirm the applied patch

$ export ORACLE_HOME=/u03/em24/middleware/oms_home
$ /u03/em24/middleware/oms_home/OMSPatcher/omspatcher lspatches

Filed under EM Tagged with , , , , , ,

EM 24ai: This version of OMSPatcher is not compatible to apply the given patch

June 12, 2025 Leave a comment

Problem:

While analyzing EM 24ai Release 1 Update 2 (24.1.0.2) for Oracle Management Service patch application, I encountered an error indicating that the OMSPatcher located under the OMS home is outdated and needs to be updated before starting the patching process.:

$ export ORACLE_HOME=/u03/em24/middleware/oms_home
$ /u03/em24/middleware/oms_home/OMSPatcher/omspatcher apply -analyze 37629905/
...
This version of OMSPatcher(13.9.24.1.0) is not compatible to apply the given patch.
Minimum Required Version of OMSPatcher to apply the patch is 13.9.24.4.0
Procure the compatible version from My Oracle Support, and try again.
OMSPatcher failed with error code 255

Solution:

1. Download patch 19999993 for EM 24.1.0.0.0 (for your version) from My Oracle Support

2. Backup the current “OMSPatcher” folder

    $ mv <MIDDLEWARE_HOME>/OMSPatcher <MIDDLEWARE_HOME>/OMSPatcher_backup

    For example:

    mv /u03/em24/middleware/oms_home/OMSPatcher /u03/em24/middleware/oms_home/OMSPatcher_backup

    3. Unzip the “p19999993_241000_Generic.zip” under /u03/em24/middleware/oms_home

      $ unzip /u03/install/p19999993_241000_Generic.zip -d /u03/em24/middleware/oms_home

      4. Check the version again and make sure the version is correct

      $ export ORACLE_HOME=/u03/em24/middleware/oms_home
      $ $ORACLE_HOME/OMSPatcher/omspatcher version

      OMSPatcher Version: 13.9.24.4.0
      OPlan Version: 12.2.0.1.16
      OsysModel build: Tue Apr 28 18:16:31 PDT 2020

      OMSPatcher succeeded.

      5. Retry running the analyze patch

      $ /u03/em24/middleware/oms_home/OMSPatcher/omspatcher apply -analyze 37629905/
      ...
      Checking if current repository database is a supported version
      Current repository database version is supported


      Prereq "checkComponents" for patch 37616329 passed.
      Prereq "checkComponents" for patch 37616365 passed.
      ...

      Filed under EM Tagged with , , , , ,

      EM 24ai: Configure EM agent manually after failure

      June 9, 2025 Leave a comment

      Problem:

      While installing EM 24ai, everything was configured except for the agent which is the last step. It failed with the following vague error:

      ...
      1. state_dir=/u03/em24/agent/agent_inst
      2. agentBaseDir=/u03/em24/agent
      3. oraHome=/u03/em24/agent/agent_24.1.0.0.0
      INFO: oracle.sysman.top.agent:Agent Home is : {0}
      SEVERE: oracle.sysman.top.agent:Agent configuration has failed
      INFO: oracle.sysman.top.agent:AgentConfiguration:agent configuration finished with status = false
      INFO: oracle.sysman.top.agent:AgentConfiguration:agent configuration finished with status = false
      INFO: oracle.sysman.top.agent:The plug-in Agent Configuration Assistant has failed its perform method

      Solution:

      Make sure agent_inst directory is empty, otherwise rename the folder and recreate:

      $ cd /u03/em24/agent
      $ mv agent_inst agent_inst2
      $ mkdir agent_inst; chmod 755 agent_inst

      Make sure libnsl package is installed, otherwise install it using yum:

      $ yum install libnsl

      Reconfigure agent manually:

      $ /u03/em24/middleware/oms_home/oui/bin/runConfig.sh ORACLE_HOME=/u03/em24/middleware/oms_home MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

      Setting the invPtrLoc to /u03/em24/middleware/oms_home/oraInst.loc
      ...
      Setting system property CUSTOM_INVENTORY to {0}
      chain install is :true

      Cloning of agent home completed successfully
      Agent Configuration completed successfully
      The following configuration scripts need to be executed as the "root" user. Root script to run : /u03/em24/agent/agent_24.1.0.0.0/root.sh

      perform - mode finished for action: configure

      Run root.sh script that is requested in the output of the above command: 

      # /u03/em24/agent/agent_24.1.0.0.0/root.sh

      It worked for me and I hope it will work for you as well. The solution was found after a lot of digging, and there might be another solution too.

      Filed under EM Tagged with , , , , ,

      EM 24ai: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory

      June 3, 2025 Leave a comment

      Problem:

      While checking the status of the agent, I received the following error:

      $ /u03/em24/agent/agent_inst/bin/emctl status agent

      Oracle Enterprise Manager 24ai Release 1
      Copyright (c) 1996, 2024 Oracle Corporation.  All rights reserved.
      ---------------------------------------------------------------
      /u03/em24/agent/agent_24.1.0.0.0/bin/emdctl: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory

      Solution:

      As root user, install libnsl package using yum

      # yum install libnsl

      Retry the command:

      $ /u03/em24/agent/agent_inst/bin/emctl status agent

      Oracle Enterprise Manager 24ai Release 1
      Copyright (c) 1996, 2024 Oracle Corporation.  All rights reserved.
      ---------------------------------------------------------------
      Agent is Not Running

      Filed under EM Tagged with , , , , ,