Data migration of an existing Microsoft Windows CMS to a new Insight Management 7.0 system

Troubleshooting

Scenario 1: Out of memory error

When does this happen?

In rare occasions, CMSs with a large amount of data, you may observe an Out of Memory error.

Solution

To increase the export\import process memory, edit the globalsettings.props file in the

Systems Insight Manager installation config directorywith any text editor (for example,

C:\program files\HP\Systems Insight Manager

\config\globalsettings.props). Change the property DMTMAXHEAP=1024m to an increased

value like DMTMAXHEAP=1536m. Increase the value by increments of 128 and make sure that value

ends with m.

Scenario 2: An export error for one or more plugins occurs with a

message like “No database connection returned for”

c:\mxexport

- No database connection returned for lsm

- Error occurred during the execution of lsmmigration

- No database connection returned for capad

- No database connectino returned for capad

- Error occurred during the execution of Capacity Advisor

- No database connection returned for amgr

- No database connectino returned for amgr

- Error occurred during the execution of ApplicationDiscovery

Solution

This issue happens because those products try to get a database connection at the same time.

Microsoft advises to try the connection again.

In case of failures, a customized set of retry values can be configured. Create a file named

dmt_db.properties under the <VSE_INSTALL_DIR> and add the following properties:

MAX_GET_CONNECTION_RETRIES

SLEEP_TIME_BETWEEN_RETRIES

Where

MAX_GET_CONNECTION_RETRIES = maximum number of attempts to get a valid database

connection. The current default value is 10.

SLEEP_TIME_BETWEEN_RETRIES = maximum amount of time to wait between attempts. In other

words, the program randomly waits from 0 to SLEEP_TIME_BETWEEN_RETRIES milliseconds. The

current default time is 10000 milliseconds.