MID Server time out getting data from SCCM...

[DrewW]

I am using the SCCM plugin and trying to import the software data which is about 4,300,000 rows. The import times out before the data is done being compiled. Does anyone have any ideas on how to get the import to wait for the MID server for more than 300 seconds OR a way to break the data up in such a way that I can get it in smaller chunks?

Any help would be appreciated.

Drew

[john_andersen]

There are two fields on the Data Source form that apply to JDBC: connection_timeout and query_timeout. You may have to personalize the Data Source form to view those fields. See if those help extend your query time beyond 300 on the software packages datasource for the SCCM integration.

Hopefully those do the trick. I haven't tried them myself, so YMMV.

[DrewW]

Thanks for the replay but it turns out the MID server is crashing when I try and get all of the 4,300,000 rows of data. I logged a ticket with support but it basically looks like I need to find a way to get the data in much smaller parts. Not sure how to do that without creating 50 query's or more...


From MID server logs.
03/29/12 14:07:58 (136) Probe: JDBCProbe:94bee16a37001000deeabfc8bcbe5d9f SELECT * FROM v_Add_Remove_Programs WHERE TimeStamp >= '2012-03-27 14:42:14.0' ORDER BY TimeStamp ASC
03/29/12 14:08:00 (292) MIB Initializer Remote MIBs loaded
03/29/12 14:08:25 (370) ECCQueueMonitor.15 SEVERE *** ERROR *** Error or exception in monitor
java.lang.OutOfMemoryError: Java heap space

03/29/12 14:08:15 (526) ECCSender.1 SEVERE *** ERROR *** Error or exception in monitor
java.lang.OutOfMemoryError: Java heap space

03/29/12 14:08:31 (714) Probe: JDBCProbe:94bee16a37001000deeabfc8bcbe5d9f SEVERE *** ERROR *** Java heap space
java.lang.OutOfMemoryError: Java heap space

[john_andersen]

I see...I don't know if this link will help you out or not:
http://wiki.service-now.com/index.php?title=MID_Server_Configuration#Setting_MID_Server_Memory_Size

According to that article, you can increase the default Heap size for the MID server. Since you are using a time stamp and getting deltas with each query, I imagine this is due to the initial load into SCCM. Once you get the 4+ million records in, you shouldn't be running into these problems.

[DrewW]

Oh, missed that in the docs... Will give it a try.