Release Notes > Known Issues

Known Issues

Content Pack 26 has the following known issues and limitations. This is a cumulative list of known issues and limitations in Content Pack, including those that are already documented in previous release notes.

ID

 Issue
Content Pack Installation

QCCR1H104758

 PROBLEM: If you deploy CP26 in UCMDB before you upgrade UCMDB to 10.22 (or later), the parent of the ConsumerProvider relationship does not change to Usage but remains as Dependency.

Workaround To resolve this issue, follow these steps:

  1. Extract the ASM_Enhanced.zip package from the CP26 package.
  2. Log in to UCMDB, and then go to Administration > Package Manager.

  3. Deploy the ASM_Enhanced.zip package that you just extracted.
Content Pack Upgrade

QCCR1H112667

 PROBLEM:
  • When upgrading the Content Pack to CP26 in UCMDB 10.22, you may see the following error messages: "CM1030PolicyAdapter.zip: Unsupported CMDB version" and "CM1030KpiAdapter.zip: Unsupported CMDB version".
  • When upgrading the Content Pack to CP26 in UCMDB version 10.33, you may see the following error messages: "CMPolicyAdapter.zip: Unsupported CMDB version" and "CMKpiAdapter.zip: Unsupported CMDB version".

Cause: Starting with CP23, two new CM adapters CM1030KpiAdapter and CM1030PolicyAdapter are added to CP. These two new adapters can be deployed with CP only from UCMDB 10.30 or later. The old adapters CMKpiAdapter and CMPolicyAdapter can be deployed with CP only from UCMDB 10.22 or earlier.

Workaround You can just ignore the error messages.

QCCR1H102405

 PROBLEM: When upgrading the Content Pack (CP), if the old CIM driver is not removed, the new CIM driver that is introduced in the new CP will not take effect, causing the Storage Management Initiative Specification (SMI-S) discovery jobs that need the new driver to fail.

Workaround Manually remove the sblim-cim-client.jar file from the <DataFlowProbe_Home>\content\lib directory.
N/A PROBLEM: After you upgrade from UCMDB 10.20 to 10.21, 10.22, 10.30, 10.31, or 10.32, the following jobs are moved to the <<No module>> group in the Discovery Modules tree.
  • DB2 Dependencies
  • F5 BIG0IP LTM Tunnel Job
  • IIS Application dependencies via URL
  • IIS Application dependencies via WebService
  • J2EE Application Dependencies via Context Root
  • J2EE Application Dependencies via JNDI
  • J2EE Application Dependencies via WebService
  • JEE WebSphere Connections by JMX for Top-down
  • JMS Destination Dependencies via JNDI
  • MessageQueue Dependencies via JNDI
  • Next-Hop Provider for Running Software
  • Next-Hop Provider
  • Oracle Access Management Dependencies
  • Oracle Dependencies
  • Oracle Schema Dependencies
  • Running Software Dependencies via TCP Connection
  • Running Software Dependencies via URL
  • SQL Server Dependencies
  • Tomcat Application dependencies via URL
  • URL Resolver
  • Web Server Dependencies via URL

These jobs are not used any longer.

Workaround You can either delete them manually or leave them in the Discovery Modules tree.
Universal Discovery - General
N/A PROBLEM: If deploying the Universal Discovery agents from CP26 with a third-party tool, the UD agents may fail to communicate with Data Flow Probe if UCMDB is deployed with CP22 or an earlier Content Pack.

Workaround None.

QCCR1H115484

 PROBLEM: (Upgrade only) After upgrading UCMDB from 10.30 to 10.31, 10.32, or 10.33, when running the JEE Weblogic by JMX job, all the CIs are reported normally; however, in the end an error message occurs to the job: "Failed to connect to remote process".

Workaround To resolve the issue,

  1. On the Data Flow Probe machine, open the java.policy file (in the <DataFlowProbe>\bin\jre\lib\security directory) using a text editor.

  2. Add the following permission:

    javax.management.MBeanTrustPermission "register"
  3. Save the file.
  4. Restart the Data Flow Probe.
Universal Discovery - Content
N/A PROBLEM: The OracleLMS.zip package version in Package Manager is incorrectly displayed as 26, which should be 1.31.1.
N/A LIMITATION: In UCMDB 10.30 and earlier versions, using multiple threads in the event-based discovery may cause the missing of events.

Workaround It is recommended to upgrade UCMDB to 10.31 or a later version. For UCMDB 10.30 and earlier versions, setting useMultiThreadForEventHub to false in globalsetting.xml; however, this operation may affect the performance of event-base discovery jobs. For details about this setting, see globalSettings.xml File.
N/A

LIMITATION: When running the Microsoft SQL Server Always On Failover Cluster Instances discovery on both real IP addresses and cluster IP addresses, duplicate Microsoft SQL instances are reported.

Workaround Exclude the cluster IP addresses of Microsoft SQL AlwaysOn Cluster from the discovery range.
N/A LIMITATION: ASM does not support multiple domains in UCMDB 10.31 or later.

Workaround None.
N/A LIMITATION: ASM does not support discovering the running software and its related ConsumerProvider relationships on a Solaris Local zone.

Workaround None.

QCCR1H99802

 PROBLEM: (db2_ipse_only trigger query only) The DB2 Universal Database Connection by SQL job returns "No credentials defined for the triggered IP" error. The triggered CIs that are triggered by the db2_ipse_only trigger query have no associated database instance, which is required to establish a connection. Then the job will get a database name from the DB2 credential. When no database name is defined in the DB2 credential, the job returns the error.

Workaround When using the db2_ipse_only trigger query, it requires a database name in the DB2 credential. Make sure you define a database name in the DB2 credential.

QCCR1H97603

 PROBLEM: When running the Mainframe topology by SNMP job and the Mainframe by EView discovery jobs, the zOS and Mainframe Logical Partition CI types that are discovered get merged.

Workaround Do not use the Mainframe topology by SNMP job when you run the Mainframe by EView discovery jobs. If you have run the Mainframe topology by SNMP discovery before installing the EView mainframe agent, it is recommended to deactivate this discovery and delete any CIs that are created by this discovery.

QCCR1H89922

LIMITATION: Child CIs are no longer included in reconciliation rules when considering identification for Business Applications. An optional identifier based on the ID (App_ID) can be used to uniquely identify each Business Application CI. Business Applications that are synced from external sources must have a unique name or ID in order to be included during data synchronization. Note that multiple Business Applications with the same name and no ID will not be synchronized.

Additional CI types for which child CIs are no longer included in reconciliation rules are Business Process, Business Service, CI Collection, Business Transaction Flow, and Dynamic Node Group. No optional identifier can be specified for these CI types.

Workaround None.

QCCR1H91943

 LIMITATION: The vCloud Director by vCloud API and vCloud Director URL by vCloud API jobs do not automatically discover VMware vCloud, because the httpcore.jar and httpclient.jar files no longer exist in the <Probe>/content/lib folder.

Workaround To fix this issue, copy the httpcore.jar and httpclient.jar files from the <Probe>/discoveryResources/http folder to the <Probe>/content/lib folder.
Micro Focus Integrations
N/A PROBLEM: On the first synchronization from Service Anywhere to UCMDB, you may see an error message displayed similar to the following:
Integration Point doesn't exist. No adapter for given target.

Workaround To remedy this, do the following:

  1. Log in to the UCMDB instance.
  2. Go to Data Flow Management > Integration Studio.
  3. Right-click the integration point: <endpoint name>_<tenant id>, and click Edit. The Edit Integration Point dialog box is displayed.
  4. Deselect Is Integration Activated.
  5. Click OK.
  6. Reselect Is Integration Activated.
  7. Click OK.
  8. Go to the job in UCMDB and run a full synchronization.
Third Party Integrations
N/A PROBLEM: In UCMDB 10.22 (or later), after deploying the ServiceNow_pull_integration_patch.zip patch, the ServiceNow integration does not work anymore.

Workaround When deploying the ServiceNow_pull_integration_patch.zip patch on UCMDB 10.22 (or later), do not overwrite the existing files httplib.py and urllib2.py in the <DataFlowProbe_Home>/jython/lib directory. This is because Jython is upgraded to version 2.7 in UCMDB version 10.22.

QCCR1H93029

 LIMITATION: Data population into UCMDB using ServiceNow integration jobs fail because a package called "suds" is missing.

Workaround To fix this issue, download and install a patch on the Data Flow Probe to supply the missing package as follows:

  1. Download the ServiceNow_pull_integration_patch.zip file from the <UCMDB_Server_Home>\DataFlowProbe\runtime\probeManager\discoveryResources\Service-Now-Pull folder.
  2. Extract the patch archive into the Data Flow Probe's installation folder. As a result, the <DataFlowProbe_Home>/jython/suds folder is created, and two files (<DataFlowProbe_Home>/jython/httplib.py and <DataFlowProbe_Home>/jython/urllib2.py) are updated. You do not need to restart the Data Flow Probe.
FIPS Mode

QCCR1H100684

 LIMITATION: When the FIPS mode is on, the Universal Discovery Agent cannot start on the non-FIPS compliant HP-UX HPPA platform. Therefore, the FIPS mode for the Universal Discovery Agent is turned off in order to run the Universal Discovery Agent on the HP-UX HPPA platform.

Workaround None.
Inventory Discovery

QCCR1H100769

PROBLEM: When setting the enableSSHSharedHomeDir parameter to true, running the agentless Inventory Discovery by Scanner job fails on Linux platforms.

Workaround To run the agentless Inventory Discovery by Scanner job successfully on Linux platforms,

  1. On your Linux instance, locate and open the /etc/exports file.

  2. Add the no_root_squash parameter to the shared directory information.

    For example, if you have the following line in the file:

    /home *(rw)

    where /home is shared directory, * means that everyone has access to it.

    Then, add no_root_squash into the line as follows:

    /home *(rw,no_root_squash)
  3. Save the change.
Service Manager Integration

QCCR1E118141

PROBLEM: Cannot disable a field that does not have a mapping entry configured in the federation configuration file (smFedConf.xml).

Workaround None.

QCCR1E119726

PROBLEM: Structure fields are not supported for pushing CIs from UCMDB to Service Manager.

Workaround None.

QCCR1E119141

PROBLEM: The Ignore on null option is not supported for data push from UCMDB to Service Manager.

Workaround None.

QCCR1E117760

PROBLEM: The Visual Mapping tool is not disabled for some out-of-the-box XML mapping scripts in which the external class cannot be displayed in the External Class Model pane.

Such out-of-the-box mapping scripts include:

  • CLIP Downtime Population mapping script
  • Relationship push and population mapping scripts
  • Federation mapping scripts

Workaround None.

QCCR1E118871

PROBLEM: If a TQL query has different exposed fields for the child CI types of the root, the Visual Mapping tool cannot display all of the exposed fields. As a result, you cannot configure mapping for fields that are not displayed by using a drag and drop in the Visual Mapping interface.

Workaround Configure mapping for the fields directly in the XML editor. Alternatively, split the query into multiple ones and then use the Visual Mapping tool.

QCCR1E119548

PROBLEM: CI relationship deletions cannot be synchronized to UCMDB through population.

Workaround None.

Send Help Center feedback