mxexport.bat : export doesn't work, CLI error

[OlivierV]

Yes, I saw the zip file. I have copied it to an other place before the end of the script because at the end it deletes all the content of the folder configdata-export.
I tried to import it but the process failed.

I'm going to increase the memory in the command line. I did it a few days ago but it has generated some errors tha tdisappeared when I removed the option. I will try 512, it was 1024.

Thank you.

[Change_happens · Accepted solution]

curious to know what happened? i will see tomorrow. good night

[OlivierV]

You're the winner.

Using -Xmx512m solved the problem. I can now understand what hapenned.

In the HP document about migrating the CMS, the command line (page 11) uses â Xmx1024. The above line uses Xmx512m. I stupidly copied and pasted the line in mxexport.bat but without the trailing 'm' (I admit that my knowledge of Java is near null), I think java understood to use 1024 bytes of memory instead of 1024 Mb, and crashed. I decided not to use this switch then.

For information, during the export, Java.exe used a maximum of 130 Mb of ram and it took about 3 hours for exporting the base with 800+ devices. The result file size makes 75 Mb.

Thank you very, very much for your time and replies.

Best regards.

[pirate_2]

cheers :)
glad your problem was solved

[Change_happens]

Cool. good news and you have discovered one more issue this was with HP document. :)

[OlivierV]

erroneous parameter in the java command line, see comment above.