Data migration of an existing Microsoft Windows CMS to a new Insight Software 6.1 system

33
Troubleshooting
Scenario
1: Out of memory error
When does this happen
In rare
occa
sions
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
processes. In the Systems Insight Manager installation bin directory,
for exam
ple
C:
\
program
files
\
HP
\
Systems Insight Manager
\
bin
, edit
mxexport.bat
with any text editor
change
the line that starts with java and add
–
Xmx
1
0
24
m
or larger value
. For example the line
should look like the following.
mxexport.bat:
"%JAVA%"
–
Xmx
1
0
24
m
-
Dor
a.home=%ORA_HOME%
-
cp %MYPT%
com.hp.mx.migration.cli.CLIWrapper mxexport %*
mximport.bat:
"%JAVA%"
-
Xmx
1
0
24
m
-
Dora.home=%ORA_HOME%
-
cp %MYPT%
com.hp.mx.migration.cli.CLIWrapper mximport %*
Scenario
2
:
I
f a
n
export of some plugins fails:
c:
\
mxexport
Warning! Export is not completely successful. Some errors are bypassed
forcibly.
The exported data file is C:/Program Files/HP/Systems Insight
Manager/data/conf
igdata
-
export
\
Products.zip.
Solution:
Save the console output to a
*.txt
file and
c
all support
.
Scenario
3
:
In Application Discovery the results of template is not the
same on the target CMS as was on the source CMS.
When does this happen
Templates on source CMS are defined to use a wild card (Any) for any of the
System Scope
fields
(Arch, OSver
, OS type)
.
Solution
When the user perform DMT of AD and when the template does not provide the desired results the
following needs to be performed for all
System Scope (Arch, OSver, OS type)
templates
.