SIM 6.0 migration

[Fick]

I imported data using mximport to a new SIM 6.0 install. The collections are empty after the import. When I search for a device in the left hand pane, I find it. Only seems to be the Sytem collections that are empty. Any ideas?

[Marco Tavares AU]

I am having the exact same issue. Trying a data collection job to see if this fixes it. Will let you know.

[Change_happens]

was mximport successful? if yes then data is gone to some different database.
you can try again mximport with logs enabled that will tell you what n where went wrong.

how to enable log: http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1276686624535+28353475&threadId=1425183

[pirate_2]

Try looking at mx.log(at [SIM]\logs) to see if there is some authorization issue.

[Fick]

mximport was successful, will run the import again with logging enabled. tx

[pirate_2]

since the import was successful, i do not think you have to run it again.
log into SIM after doing an import and then when you click on the collection, then have a look at the mx.log
You do not have to enable anything for this

[Fick]

I just clicked on the "All Systems Collection" which is still empty. There is alot of activity in the mx.log file, here some of the text:

@!@,2010-06-18 11:53:50 IST,CONFIG,SUCCESS,MODIFY,NODE,usadc-vsinf02 : Identifier = 0000000802b2e6e80000000300000820 : DnsName = usadc-vsinf02.quintiles.net : ChangeFlags = 128,SUMMARY,ieedc-vsmon01\mxadmin,0,83501,
@!@,2010-06-18 11:53:52 IST,CONFIG,SUCCESS,MODIFY,NODE,usadc-svs05 : Identifier = 0000000802b2e6e80000000300000133 : DnsName = usadc-svs05.quintiles.net : ChangeFlags = 128,SUMMARY,ieedc-vsmon01\mxadmin,0,83504,
@!@,2010-06-18 11:54:11 IST,CONFIG,SUCCESS,ADD,JOB,Tool Name: Hardware Status Polling Task Name: Hardware Status Polling for Systems no Longer Disabled Job ID: 225972_ieedc-vsmon01.quintiles.net,SUMMARY,ieedc-vsmon01\mxadmin,0,83625,
@!@,2010-06-18 11:54:11 IST,CONFIG,SUCCESS,START,TASK,Hardware Status Polling - 225972_ieedc-vsmon01.quintiles.net,SUMMARY,ieedc-vsmon01\mxadmin,0,83623,
@!@,2010-06-18 11:54:11 IST,CONFIG,SUCCESS,ADD,JOB,Tool Name: Software Status Polling Task Name: Software Version Status Polling for Systems no Longer Disabled Job ID: 225973_ieedc-vsmon01.quintiles.net,SUMMARY,ieedc-vsmon01\mxadmin,0,83633,
@!@,2010-06-18 11:54:11 IST,CONFIG,SUCCESS,START,TASK,Software Status Polling - 225973_ieedc-vsmon01.quintiles.net,SUMMARY,ieedc-vsmon01\mxadmin,0,83631,
@!@,2010-06-18 11:54:12 IST,CONFIG,SUCCESS,DELETE,JOB,Tool Name: Hardware Status Polling Task Name: Hardware Status Polling for Systems no Longer Disabled Job ID: 225972_ieedc-vsmon01.quintiles.net,SUMMARY,ieedc-vsmon01\mxadmin,0,83642,
@!@,2010-06-18 11:54:13 IST,CONFIG,SUCCESS,DELETE,JOB,Tool Name: Software Status Polling Task Name: Software Version Status Polling for Systems no Longer Disabled Job ID: 225973_ieedc-vsmon01.quintiles.net,SUMMARY,ieedc-vsmon01\mxadmin,0,83653,
@!@,2010-06-18 11:54:17 IST,CONFIG,SUCCESS,MODIFY,NODE,usadc-smbxc02 : Identifier = 0000000802b2e6e800000003000012f9 : DnsName = usadc-smbxc02.quintiles.net : ChangeFlags = 8,SUMMARY,ieedc-vsmon01\mxadmin,0,83720,


Makes any sense why the collections are still empty?

[Marco Tavares AU]

I ended up giving up and just manually discovered the devices and entered everything again from scratch. All working beautifully now.

[Fick]

Seems the migration tool only supports SQL 2005 SP3 / 2008 SP1 DBs. Otherwise, your collections is going to end up EMPTY.

[Hemant S.]

Its surprising why HP is supporting just SQL DB but not oracle DB.

[Darrin Rawls]

Fick,
Were you running an Oracle db? Yes, only SQL supported right now.

[Fick]

Hi Darrin, Running a remote SQL 2005 SP1 Db.
I think the problem is with the mxexport. There are a couple of errors during the export process. Maybe the collection data is not exported at all, or the source CMS system is too screwed up to complete a successful export. Please have a look at the attached. Cheers Henri.

[Darrin Rawls]

Did you follow the white paper for DMT?

That out of memory issue on SIM export looks like it could be the root issue.
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02080248/c02080248.pdf

_________________
Step 8: Configure the mxexport batch file for larger CMS installs

Edit the mxexport.bat file to increase the memory allocated to the export processes. In the Systems Insight Manager installation bin directory...