Data migration of an existing Microsoft Windows CMS to a new Insight Software 6.3 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

Edit the mxexport.bat/mximport.bat file to increase the memory allocated to the export/import

processes in the Systems Insight Manager installation bin directory. For example, C:\program

files\HP\Systems Insight Manager\bin edit mxexport.bat with any text editor. Change the

line that starts with java and add –Xmx1024m or larger value. The line should look like the

following.

mxexport.bat:

"%JAVA%" –Xmx1024m -cp %MYPT% com.hp.mx.migration.cli.CLIWrapper mxexport

mximport.bat:

"%JAVA%" -Xmx1024m -cp %MYPT% com.hp.mx.migration.cli.CLIWrapper mximport

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. To fix that,

we’ve followed Microsoft advice that says to try the connection again.

So, in case of failures, a customized set of retry values could be configured. To do that, the customer needs to

create a file named ‘dmt_db.properties’ under <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 we will keep trying to get a valid

database connection. The current default value is 10

And

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

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

current default time is 10000 milliseconds.

The customer may want to try higher configuration values, like the following:

MAX_GET_CONNECTION_RETRIES=20