Data Management Portal problems

This information covers common problems that occur with the Data Management Portal.

Fix Pack

The Grouping Patterns pane not displayed

When you go to Analytics in Data Management Portal, the Grouping Patterns pane is not displayed.
To display the Grouping Patterns pane with its content, you must have the Update permission granted for the DefaultAccessCollection.
Fix Pack

No grouping patterns displayed

When you try to display grouping patterns in the Grouping Patterns pane in Analytics in Data Management Portal, there are no grouping patterns. The following error is displayed:
Sorry, an error occurred
You must have the Discover permission to display grouping patterns.

An error occurs when you log on

When you log on to the Data Management Portal in your browser, the following error message is displayed:
file:/C:/ibm/taddm/dist/lib/guiserver-dep.jar: Size mismatch, found 
28,420,460 bytes, 1599 was expected.
To resolve this problem, clear your browser cache and Java™ plug-in cache:
  1. Clear the browser cache by using the appropriate method for your browser:
    • In Internet Explorer, click Tools > Internet Options. On the General tab, click Delete.
    • In Firefox, click Tools > Clear Recent History.
    For more information, see the documentation for your browser.
  2. Use the Java control panel to clear the Java plug-in cache. The steps for clearing the Java plug-in cache vary depending on which operating system and JRE you are using. See the documentation for your JRE, for more information.
  3. Restart the browser and log on.
    Note: The first logon attempt after clearing the cache might take longer than usual, because the required JAR files must be downloaded again.

An error occurs when you change the administrator password

Each time you access the TADDM server from the Data Management Portal session, you must use the user ID and password credentials. Therefore, after you have changed the administrator password, you can no longer access the TADDM server.
The following steps describe how this problem occurs:
  1. Log on as administrator to the Data Management Portal.
  2. Change the administrator password.
  3. Click Change password.
After changing the administrator password, you get the following results:
  • A window with [object][object] is displayed.
  • When you click the Users icon, an Error loading '/cdm/' (500 Internal Server Error) message is displayed.
Log off from the Data Management Portal and log on again using the new password. The user ID and password credentials are now valid and you can access the TADDM server.
Note: To prevent this problem from occurring, you must not modify the password of the user who has logged on to the Data Management Portal. For example, assume that there are two administrators, named admin1 and admin2, for TADDM. If admin1 is logged on to the Data Management Portal, admin1 must not change their own password, but instead, admin1 can change the password of admin2.

You get logged off

You get logged off from the Data Management Portal. The use of the Backspace key might cause you to get logged off if the cursor focus is not on an input field that you are manipulating.
If you press the Backspace key, ensure that the cursor focus is on an input field that you are manipulating.

Display problems in Internet Explorer browser following upgrade of synchronization server

After you upgrade a synchronization server from one TADDM release to another, the Data Management Portal does not display properly when viewing it in a Microsoft Internet Explorer browser.
Clear your Microsoft Internet Explorer browser cache by completing the following steps:
  1. Click Tools > Internet Options > General.
  2. In the Temporary Internet files section click Delete files.
  3. In the Delete files window, select Delete all off-line content.
  4. Click OK.
  5. Close the Microsoft Internet Explorer browser before logging back on to the TADDM Data Management Portal.

Display problems in Firefox browser

If you view the Data Management Portal in the Firefox browser, the layout might be displayed incorrectly, or the margins might be misaligned.
Disable unnecessary Firefox plug-ins. Alternatively, and if possible, disable individual plug-ins when connecting to the TADDM server.

Error message is shown when viewing Application Infrastructure topology graph

When you view the Application Infrastructure topology graph, the following error message is displayed:
The requested graph has exceeded the number of allowed nodes.
This problem can occur when running several types of built-in reports. One way to resolve the problem is to create business applications for your data center. Use the business applications to drill through to the software topology. For more information, see the topic on creating business applications in the TADDM information center.

You can also create smaller groups of configuration items to view the topologies.

DB2 license information not found during discovery

After performing a discovery, under the License tab, the Details panel for a discovered DB2® server running on UNIX and Linux® operating systems can be blank. No error message is returned.
On UNIX and Linux operating systems, the db2licm program must have correct permissions for the user specified in the Discovery Management Console that is designated to connect to the databases.

Specifically, to get the license information, the discovery user must have the primary group of the DB2 instance owner in the group list.

Unknown servers not displayed

You do not see unknown servers listed in the Data Management Portal.
The report unknown servers is a pop-up menu option on Computer Systems in the Data Management Portal. The report can be used in a synchronization server deployment or streaming server deployment.

After exporting a report to a PDF file, the first line of the report shows an error message

After you export a report to a PDF file, the following error message is displayed at the start of the report:
Number of rows to be exported to a PDF file exceeded maximum value
 supported for a PDF export.
Only first 1000 rows have been exported.
Try to export partial data or choose other export format such as CSV or XML
 to get all data exported.
This problem can occur when exporting any analytical report that has a table containing more than 1000 rows. This limitation does not apply to BIRT reports. To resolve the problem, export the information in sections to a PDF file or select a different file format for example, CSV or XML file.

When creating a custom query, the comparison criteria are in reverse order in non-English locales

In non-English locales, when you create a custom query and select Match all criteria or Match any criteria, the description of the comparison criteria can be displayed in reverse order. These criteria specify a logical AND or logical OR for multiple comparison criteria.
To correct this problem in non-English locales, select the reverse order to what is displayed. The Match any criteria (logical OR) is the rightmost criteria.

An icon defined in the Discovery Management Console is displayed differently in the Data Management Portal

An icon set up in a custom template might be displayed differently when shown in the Discovered Components pane of the Data Management Portal.
Because the technology used in the Data Management Portal differs from that of the Discovery Management Console, an icon in one user interface (UI) might be displayed differently to the same icon in the other UI. This effect is cosmetic and does not affect the operation of the TADDM deployment.

Cannot connect to a selected discovery server from the TADDM Servers Summary pane

Server not found message is displayed when you try to connect to a selected discovery server from the TADDM Servers Summary pane.
The primary storage server must resolve the fully qualified domain name (FQDN) for each secondary storage server and discovery server. You can configure the host name resolution order for your system to use DNS resolution. Alternatively, you can edit the /etc/hosts file on primary storage server. Include the IP address and host name for each discovered secondary storage server and discovery server to this file. The client running the Data Management Portal must also be able to resolve the FQDN and host names.

Tooltip is visible even after the window that contains it is closed

You still see a tooltip even after you close the window that contains the tooltip.
Reopen the respective window, and move the cursor over the area where the tooltip was first shown.

Viewing a very large configuration file fails with an error

When attempting to view the contents of a very large configuration file (typically 1MB, or larger), an error with the following text is displayed:
Script stack space quota is exhausted
Because of a quota on the script stack space imposed by the web browser, very large configuration files cannot be viewed in the Data Management Portal. The maximum sized file that you can successfully view is dependent on the browser that you are using, and different browsers might have different quotas.

Data displayed in one view does not match data displayed in other views

In some cases, data displayed in connection with a group of discovered configuration items in one view of the Data Management Portal might not match data displayed for the same group of discovered configuration items in another view of the Data Management Portal.

TADDM uses different kinds of graphs to display statistics for identical groupings of discovered configuration items, depending on how the graphs are accessed from the Data Management Portal, and these graphs may appear to display different data for the same group of discovered configuration items. For example, if you view a graph of network switches in a discovery, and you access the graph by selecting Physical Infrastructure in the Discovered Components pane, the resulting tree graph might display x switches. However, when you view a graph of those same network switches by first selecting the Topology tab, and then choosing Physical Infrastructure, the resulting topology graph might display y switches.

This is because the Physical Infrastructure topology, as viewed by means of the Topology tab, is not meant to show all devices. As a Layer 3 topology, it displays only IP network clouds and devices with ipForwarding enabled. It will show the subnets (IpNetworks) and their interconnecting devices and provide a quick drilldown to the subnet topology which shows every single device on that subnet. Interconnecting devices are defined as:
  • Firewalls: ComputerSystem with type set to Firewall
  • Load balancers: ComputerSystem with type set to LoadBalancer
  • Any device other than a firewall or a load balancer that is performing a routing function: ComputerSystem that has the router function and has forwarding on the router function set to true
  • Manually-defined router: GenericRouter
  • Manually-defined firewall: GenericFirewall
  • Manually-defined load balancer: GenericLoadBalancer

Changes made to the members of custom collections are not displayed in the Change History report

Change History report for groups of type custom collection (business applications, collections, or access collections) contains changes made only to the custom collections and their structure. For example, the report contains entries for adding or removing a node. However, the changes made to the members of such collections are not displayed.
To view the changes made to the custom collections members, complete the following steps:
  1. Display the topology of a custom collection.
  2. Select all elements on the topology by using Select Rectangle tool.
  3. Choose the Add to cart option from the context menu.
  4. In the Discovered Components pane, click the Cart button to see its content.
  5. Select all elements in the cart.
  6. From the Actions drop down menu, click the Change History option.