Six Stars

SAP info cube extraction error

Hi Team

 

I am trying to connect to SAP info cube and pull the lager volume of data

I facing the following issue,Can you please guide me how to resolve. 

 

Starting job Extract_SAP_BW at 15:50 13/10/2017.

 

[statistics] connecting to socket on port 3584

[statistics] connected

Exception in component tSAPInfoCubeInput_2 (Extract_SAP_BW)

java.lang.RuntimeException: Next data package could not be requested: SAPException@2f953efd [

   errorCode=40

  ,errorGroup=0

  ,errorKey=null

  ,errorMessage=<BAPIRET2><TYPE>E</TYPE><ID>DBMAN</ID><NUMBER>257</NUMBER><MESSAGE>SQL Error: INVALID_CURSOR</MESSAGE><LOG_NO></LOG_NO><LOG_MSG_NO>000000</LOG_MSG_NO><MESSAGE_V1>INVALID_CURSOR</MESSAGE_V1><MESSAGE_V2></MESSAGE_V2><MESSAGE_V3></MESSAGE_V3><MESSAGE_V4></MESSAGE_V4><PARAMETER></PARAMETER><ROW>0</ROW><FIELD></FIELD><SYSTEM>DB2CLNT100</SYSTEM></BAPIRET2>

  ,bapiName=Z_TALEND_READ_INFOPROV

]

                at org.talend.sap.impl.bw.readable.SAPBWLayoutBasedTableData.nextRow(SAPBWLayoutBasedTableData.java:144)

                at imss.extract_sap_bw_0_1.Extract_SAP_BW.tSAPInfoCubeInput_2Process(Extract_SAP_BW.java:3776)

                at imss.extract_sap_bw_0_1.Extract_SAP_BW.runJobInTOS(Extract_SAP_BW.java:4117)

                at imss.extract_sap_bw_0_1.Extract_SAP_BW.main(Extract_SAP_BW.java:3936)

[FATAL]: imss.extract_sap_bw_0_1.Extract_SAP_BW - tSAPInfoCubeInput_2 Next data package could not be requested: SAPException@2f953efd [

   errorCode=40

  ,errorGroup=0

  ,errorKey=null

  ,errorMessage=<BAPIRET2><TYPE>E</TYPE><ID>DBMAN</ID><NUMBER>257</NUMBER><MESSAGE>SQL Error: INVALID_CURSOR</MESSAGE><LOG_NO></LOG_NO><LOG_MSG_NO>000000</LOG_MSG_NO><MESSAGE_V1>INVALID_CURSOR</MESSAGE_V1><MESSAGE_V2></MESSAGE_V2><MESSAGE_V3></MESSAGE_V3><MESSAGE_V4></MESSAGE_V4><PARAMETER></PARAMETER><ROW>0</ROW><FIELD></FIELD><SYSTEM>DB2CLNT100</SYSTEM></BAPIRET2>

  ,bapiName=Z_TALEND_READ_INFOPROV

]

java.lang.RuntimeException: Next data package could not be requested: SAPException@2f953efd [

   errorCode=40

  ,errorGroup=0

  ,errorKey=null

  ,errorMessage=<BAPIRET2><TYPE>E</TYPE><ID>DBMAN</ID><NUMBER>257</NUMBER><MESSAGE>SQL Error: INVALID_CURSOR</MESSAGE><LOG_NO></LOG_NO><LOG_MSG_NO>000000</LOG_MSG_NO><MESSAGE_V1>INVALID_CURSOR</MESSAGE_V1><MESSAGE_V2></MESSAGE_V2><MESSAGE_V3></MESSAGE_V3><MESSAGE_V4></MESSAGE_V4><PARAMETER></PARAMETER><ROW>0</ROW><FIELD></FIELD><SYSTEM>DB2CLNT100</SYSTEM></BAPIRET2>

  ,bapiName=Z_TALEND_READ_INFOPROV

]

                at org.talend.sap.impl.bw.readable.SAPBWLayoutBasedTableData.nextRow(SAPBWLayoutBasedTableData.java:144)

                at imss.extract_sap_bw_0_1.Extract_SAP_BW.tSAPInfoCubeInput_2Process(Extract_SAP_BW.java:3776)

                at imss.extract_sap_bw_0_1.Extract_SAP_BW.runJobInTOS(Extract_SAP_BW.java:4117)

                at imss.extract_sap_bw_0_1.Extract_SAP_BW.main(Extract_SAP_BW.java:3936)

[statistics] disconnected

Job Extract_SAP_BW ended at 15:53 13/10/2017. [exit code=1]SAP.png

 

 

2 REPLIES
Moderator

Re: SAP info cube extraction error

Hi,

You are pulling the lager volume of data? What's the size (> 1 mio. rows)?

It seems that the current implementation reaches its limits, because all the extracted data is hold in the main memory of the SAP system and client (Talend Job).

Best regards

Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
Employee

Re: SAP info cube extraction error

Hi,

 

What would be the solution to process large amount of data?

 

If it is memory issue then would increasing the JVM parameters of the job resolve this?

 

Or do we have any other workaround?

 

Thanks