---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# IBM Db2 on Linux database

# IBM Db2 on Linux database discovery {#ariaid-title1}

* Release version: Yokohama
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

ServiceNow
Discovery uses the Db2 on Linux discovery pattern to find IBM Db2 instances on Linux servers.
Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).

Discovery uses this pattern to run horizontal discovery. The pattern is triggered automatically by classification using these Db2 identifiers: tcp_port, name, installed_dir.

## Prerequisites {#ibm-db2-linux-discovery__section_ybt_bn4_xkb}

Configure SSH credentials for the Linux server.

In addition, ensure that the user has the permissions to run the following commands:

Identification for Db2 UDB entry point types
:   ". /" + $process.environmentVariables.HOME.value + "/sqllib/db2profile; " + $process.environmentVariables.HOME.value + "/sqllib/bin/db2level"
:   "source " + $installed_dir + "db2profile"
:   "db2 list database directory \| grep \\"Database name\\" \| grep -i \\"" + $entry_point.instance + "\\" \| head -1"
:   "db2level \| grep \\"DB2 v\\""

Identification for Db2 UDB entry point types - NONE
:   "cat " + $installed_dir + "/db2dump/db2diag.log \| grep \\"INSTANCE:\\" \| grep " + $entry_point.instance + " \| head -1"
:   "db2level \| grep \\"DB2 v\\""

Identification for Db2 on z/OS
:   "netstat -a \| grep " + $entry_point.port
:   "ls -d /\*/\* \|grep " + $id

## Data collected by Discovery during horizontal discovery {#ibm-db2-linux-discovery__section_o5m_x2k_jnb}

The Identification for Db2 UDB entry point types and Identification for Db2 UDB entry point types -- NONE sections collect the following tables and fields:{#ibm-db2-linux-discovery__table_q1z_jkp_jnb__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | The Db2 instance name. |
| TCP port(s) \[tcp_port\] | TCP port. |
| Install Directory \[installed_dir\] | Installation directory. |
| Version \[version\] | Db2 version. |
[Table 1. DB2 Subsystem \[cmdb_ci_db_db2_instance\]]

{#ibm-db2-linux-discovery__table_q1z_jkp_jnb}  
The Identification for Db2 on Z/OS section collects the following tables and fields:{#ibm-db2-linux-discovery__table_eg3_xlp_jnb__entry__2}

| Table and field | Description |
|-|-|
| Name \[name\] | The Db2 instance name. |
| TCP port(s) \[tcp_port\] | TCP port. |
| Install Directory \[installed_dir\] | Installation directory. |
[Table 2. DB2 Subsystem \[cmdb_ci_db_db2_instance\]]

{#ibm-db2-linux-discovery__table_eg3_xlp_jnb}  
The Dependency Views map shows all discovered IBM Db2 instances in your organization and the relationships between them.  

## CI relationships {#ibm-db2-linux-discovery__section_v4y_nkp_jnb}

The IBM Db2 on Linux pattern does not create any CI relationships.