Oracle Listener and Oracle Database discovery issues

Go to solution
devpc
Tera Contributor

‎02-14-2025 09:41 AM

Hi, I have a problem with the discovery of Oracle databases (cmdb_ci_db_ora_instance). In the discovery logs I receive an error message for Oracle Listeners (see image oracle 1) in particular this message here (see image oracle 2). Finding the PID in the Running Process of the server on which the database is, it brings me back to this command (see image oracle 3).
What is the problem in question? the discovery is completed but some pieces are lost along the way (for example, not all databases are found and the reconciliation rules do not work properly).

Thank you

Preview file
83 KB
Preview file
9 KB
Preview file
33 KB
0 Helpfuls
  • 1,680 Views
1 ACCEPTED SOLUTION

Go to solution
Chirag K
Mega Expert
In response to devpc

‎02-17-2025 02:12 AM

Hi @devpc ,

 

The error indicates the right permissions are not set in sudoer's file for this user.

 

I am assuming this is an AIX Server, please see below documentation

https://www.servicenow.com/docs/bundle/yokohama-it-operations-management/page/product/service-mappin...

 

procwdx is mentioned here too. 

 

 

 

There is a KB Article, more or less same error

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1115713

 

I believe when you update your sudoer's file with this command and you will see the results.

 

Hope this will help you resolve your issue.

 

Good Luck. 

 

CK

 

View solution in original post

0 Helpfuls
4 REPLIES 4

Go to solution
Harsh Vardhan
Giga Patron

‎02-14-2025 10:04 AM

@devpc  Can you double check the "process detection" step in pattern log, and confirm which command is failing there ?

if that step failed "Oracle Listener ID" step will auto terminate . 

Adding doc link please validate it by running those command directly on target server.

 

Oracle Listener HD discovery 

 

Thanks,

Harsh

0 Helpfuls

Go to solution
devpc
Tera Contributor
In response to Harsh Vardhan

‎02-17-2025 12:05 AM - edited ‎02-17-2025 12:10 AM

Hello Harsh, this is what I see in the discovery log

 

 

{
  "name" : "Discovery Log",
  "status" : "FAILURE",
  "children" : [ {
    "name" : "Pre Pattern Execution",
    "id" : "pre_pattern_execution_script",
    "status" : "SUCCESS",
    "level" : 2,
    "messages" : [ {
      "message" : "2025-02-17 08:58:03: Getting pre pattern execution data generated by script."
    }, {
      "message" : "2025-02-17 08:58:03: setAttribute(AwsCliToGenerateToken,false)",
      "severity" : "DEBUG"
    }, {
      "message" : "2025-02-17 08:58:03: setAttribute(hostnameCase,Lower case)",
      "severity" : "DEBUG"
    }, {
      "message" : "2025-02-17 08:58:03: setAttribute(fqdnRegex,^([^.]+)\\.((?:[^.]+\\.)+[^.]+)$)",
      "severity" : "DEBUG"
    }, {
      "message" : "2025-02-17 08:58:03: setAttribute(shouldIncludeDomain,false)",
      "severity" : "DEBUG"
    }, {
      "message" : "2025-02-17 08:58:03: setAttribute(useFullManifestID,false)",
      "severity" : "DEBUG"
    }, {
      "message" : "2025-02-17 08:58:03: setAttribute(useFullManifestIDTruncate,false)",
      "severity" : "DEBUG"
    }, {
      "message" : "2025-02-17 08:58:03: setAttribute(pattern_runtime_mode,horizontal)",
      "severity" : "DEBUG"
    } ],
    "type" : "NONE"
  }, {
    "name" : "Selecting Pattern for Execution",
    "id" : "set_pattern_name",
    "status" : "SUCCESS",
    "level" : 2,
    "messages" : [ {
      "message" : "2025-02-17 08:58:03: Pattern: Oracle Listener HD"
    }, {
      "message" : "2025-02-17 08:58:03: setAttribute(pattern,Oracle Listener HD)",
      "severity" : "DEBUG"
    } ],
    "type" : "NONE"
  }, {
    "name" : "Process Detection",
    "status" : "SUCCESS",
    "level" : 2,
    "messages" : [ {
      "message" : "2025-02-17 08:58:03: Executing SSH command: ps -eo user,pid,ppid,comm,args | grep -i '8978594' |  grep -v grep",
      "severity" : "DEBUG"
    }, {
      "message" : "2025-02-17 08:58:03: Executing SSH command: command -v sudo",
      "severity" : "DEBUG"
    }, {
      "message" : "2025-02-17 08:58:05: Command result: /usr/bin/sudo",
      "severity" : "DEBUG"
    }, {
      "message" : "2025-02-17 08:58:05: Command result: oracle  8978594        1 tnslsnr  /sbOraGrid/11.2.0.4/bin/tnslsnr LISTENER -inherit",
      "severity" : "DEBUG"
    }, {
      "message" : "2025-02-17 08:58:05: Executing SSH command as superuser: procwdx 8978594",
      "severity" : "DEBUG"
    }, {
      "message" : "2025-02-17 08:58:07: Command failed with status 1. Command : sudo procwdx 8978594. Host : 10.55.178.1",
      "severity" : "DEBUG"
    }, {
      "message" : "2025-02-17 08:58:07: Failed to find process on port. Failed to execute command using sudo on host 10.zz.xxx.y while using  [code]<a href=\"/nav_to.do?uri=ssh_credentials.do?sys_id=e871cc6d87811294b794fc46cebb352c\" target=\"_blank\"><u>credentilas</u></a>[/code]. Command: sudo procwdx 8978594 Error: sudo: parse error in /etc/sudoers near line -1",
      "severity" : "DEBUG"
    } ],
    "type" : "NONE"
  }, {
    "name" : "Process Detection",
    "status" : "SUCCESS",
    "level" : 2,
    "type" : "NONE"
  }, {
    "name" : "Oracle Listener ID",
    "status" : "TERMINATION",
    "children" : [ {
      "name" : "1 Verify tns listener process and HD",
      "status" : "MIXED",
      "level" : 3,
      "messages" : [ {
        "message" : "2025-02-17 08:58:07: Execution time: 1 ms",
        "severity" : "DEBUG"
      } ],
      "type" : "STEP_TYPE"
    } ],
    "level" : 2,
    "type" : "IDENTIFICATION_SECTION_TYPE"
  }, {
    "name" : "Target Cleanup",
    "id" : "target_cleanup",
    "status" : "SUCCESS",
    "level" : 2,
    "messages" : [ {
      "message" : "2025-02-17 08:58:07: Skipped file cleaning on target. In order to activate this behavior, please set \"mid.sa.cleanup.clean_files_on_target\" MID property",
      "severity" : "DEBUG"
    } ],
    "type" : "NONE"
  }, {
    "name" : "discovery",
    "id" : "discovery",
    "status" : "FAILURE",
    "children" : [ {
      "name" : "Check Processing Success",
      "id" : "Check Processing Success",
      "status" : "FAILURE",
      "level" : 3,
      "messages" : [ {
        "message" : "2025-02-16 23:58:08: Identification Engine: Discovery status is FAILURE, Identification sections in pattern failed: section: Oracle Listener ID, error: Match step predicate is not matched.  Failed Condition(s): [(${process.executable} : value=) CONTAINS \"tnslsnr\"] .  "
      } ],
      "type" : "NONE"
    } ],
    "level" : 2,
    "type" : "NONE"
  } ],
  "level" : 0,
  "messages" : [ {
    "message" : "2025-02-17 08:58:02: Task is running on MID server WPSNOWDISCI01",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(cmdb_ci_db_ora_listener,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(cmdb_ci_oracle_cluster,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(cmdb_ci_db_ora_service,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(cmdb_ci_db_ora_instance,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(cmdb_ci_linux_server,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(cmdb_ci_hpux_server,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(cmdb_ci_aix_server,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(cmdb_ci_solaris_server,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(cmdb_ci_oracle_database,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(cmdb_ci_oracle_cluster_node,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(cmdb_serial_number,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(oracle_table_space,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(oracle_cpu_usage,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(x_qual5_itam_nwapp_open_ports,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(oracle_active_session,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(x_qual5_itam_nwapp_qualys_processors,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(cmdb_print_queue_instance,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(oracle_inactive_sessions,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(x_qual5_itam_nwapp_qualys_asset_tags_relation_details,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(mssql_sqlservice_info,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(oracle_asm_info,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(samp_oracle_options,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(discovery_switch_bridge_port_table,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(cmdb_sam_sw_install,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(x_qual5_itam_nwapp_qualys_asset_details,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(cmdb_ot_entity,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(discovery_switch_spanning_tree_table,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(x_qual5_itam_nwapp_qualys_hardware_details,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(oracle_instance_info,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(subnet_router_m2m,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(mssql_components_info,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(discovery_switch_fwd_table,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(x_qual5_itam_nwapp_qualys_os_details,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(x_qual5_itam_nwapp_missing_software_details,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(cmdb_key_value_v2,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(samp_client_access,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(oracle_nodes_info,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(x_qual5_itam_nwapp_easm_domain,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(oracle_top_10_queries,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(cmdb_key_value,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(oracle_asm_nodes_info,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(x_qual5_itam_nwapp_easm_subdomain,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(cmdb_backup_storage_information,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(cmdb_software_instance,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(discovery_net_arp_table,[{}])",
    "severity" : "DEBUG"
  }, {
    "message" : "2025-02-17 08:58:03: setAttribute(x_qual5_itam_nwapp_easm_whois,[{}])",
    "severity" : "DEBUG"
  } ],
  "type" : "NONE"
}

 

 

I guess this is the error:
Failed to find process on port. Failed to execute command using sudo on host 10.zz.xxx.y while using [code]<a href=\"/nav_to.do?uri=ssh_credentials.do?sys_id=e871cc6d87811294b794fc46cebb352c\" target=\"_blank\"><u>credentilas</u></a>[/code]. Command: sudo procwdx 8978594 Error: sudo: parse error in /etc/sudoers near line -1",

0 Helpfuls

Go to solution
Chirag K
Mega Expert
In response to devpc

‎02-17-2025 02:12 AM

Hi @devpc ,

 

The error indicates the right permissions are not set in sudoer's file for this user.

 

I am assuming this is an AIX Server, please see below documentation

https://www.servicenow.com/docs/bundle/yokohama-it-operations-management/page/product/service-mappin...

 

procwdx is mentioned here too. 

 

 

 

There is a KB Article, more or less same error

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1115713

 

I believe when you update your sudoer's file with this command and you will see the results.

 

Hope this will help you resolve your issue.

 

Good Luck. 

 

CK

 

0 Helpfuls

Go to solution
parthpdeoka
Tera Contributor

‎02-17-2025 12:16 AM

Possible Causes of the Issue:

  1. Incorrect Process Identification:

    • The discovery process expects to find a running process containing "tnslsnr" (which is the Oracle Listener process).
    • However, the process running on the server may have a different name, or the path to the executable may not be correctly recognized.
    • Running the command ps -ef | grep tnslsnr on the target server can help verify if the listener process is running with the expected name.

  2. Custom Oracle Installations:

    • If Oracle was installed in a custom directory or with a different executable name, the default discovery patterns might not match.
    • You may need to modify the identification pattern in the Discovery Configuration to include the actual process name.

  3. Permission Issues:

    • The user account running the discovery might not have sufficient permissions to access the Oracle Listener process details.
    • Try running the discovery with a higher-privileged account or check if the discovery credentials have proper access.

  4. Multiple Oracle Homes:

    • If multiple Oracle Homes are configured, the discovery process may be detecting only one, causing inconsistencies in database identification.

  5. Missing Oracle Listener Process:

    • If the Oracle Listener is not running at the time of discovery, it will not be detected.
    • Check the listener status using lsnrctl status on the Oracle server.

Suggested Fixes:

  1. Verify the Running Process:

    • Log into the database server and run:
      perl
       
      ps -ef | grep tnslsnr
    • If tnslsnr is missing, check if the listener service is running.

  2. Manually Update the Discovery Pattern:

    • If the process name differs from tnslsnr, update the pattern to match the actual process name.
    • Go to ServiceNow Discovery Patterns, locate the Oracle Listener HD pattern, and adjust the Process Detection rule.

  3. Check Discovery Permissions:

    • Ensure that the user credentials used in ServiceNow have sufficient privileges to access process details.
    • Try using root or an Oracle DBA account to validate.

  4. Manually Restart the Listener:

    arduino
    lsnrctl stop lsnrctl start

  5. Re-run Discovery:

    • After verifying the process and listener, re-run ServiceNow Discovery and check if it now correctly identifies Oracle Listeners and databases.
0 Helpfuls