Skip to main content

[SKP Scanner] SAP scan using too much memory

Ben Bauer
  • Updated

Issue

After an SAP System Scan fails from the SKP Catalog, the scanning logs in the SKP Connector (/var/syniti-agent/scanner/logs) show a memory error like this:

{java.lang.Exception}: {java.lang.Exception: Exception in thread "main" com.sap.conn.jco.JCoException: (1*****4)
JCO_ERROR_SYSTEM_FAILURE: No more memory available to add rows to an internal table.
                at com.sap.conn.jco.rt.AbstractConnection.generateJCoException(AbstractConnection.java:616)
                at com.sap.conn.jco.rt.ClientConnection.executeInternal(ClientConnection.java:2*****9)
                at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:2196)
                at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:2*****63)
                at com.sap.conn.jco.rt.RfcDestination.execute(RfcDestination.java:2*****14)
                at com.sap.conn.jco.rt.RfcDestination.execute(RfcDestination.java:1978)
                at com.sap.conn.jco.rt.AbapFunction.execute(AbapFunction.java:3*****5)
                at com.syniti.catalog.scanner.netweaver.RFCReadTableHelper.execute(RFCReadTableHelper.java:57)
                at com.syniti.catalog.scanner.netweaver.NetWeaverScanner.readFields(NetWeaverScanner.java:285)
                at com.syniti.catalog.scanner.netweaver.SapScanner.main(SapScanner.java:42)

 

Resolution

Provide the attached document to a member of the SAP BASIS team to assist them with analyzing the memory issue and determining the amount of memory that needs to be configured for the scan.

Related articles