I am trying to use Talend to extract the database tables from SAP, but extracting the CDPOS table gives me an error. I have been trying to change different memory parameters but so far without luck. Any suggestions?
TALEND error message:
[FATAL]: local_project.cdpos_0_1.CDPOS - tSAPTableInput_2 null
Exception in component tSAPTableInput_2
SAPException@71a8adcf [
errorCode=1
,errorGroup=104
,errorKey=JCO_ERROR_SYSTEM_FAILURE
,errorMessage=No more storage space available for extending an internal table.
,errorMessageText=
,bapiName=Z_TALEND_READ_TABLE
,tableName=CDPOS
]
at org.talend.sap.exception.SAPException$Builder.<init>(SAPException.java:269)
at org.talend.sap.exception.SAPException$Builder.<init>(SAPException.java:264)
at org.talend.sap.exception.SAPException.newBuilder(SAPException.java:74)
at org.talend.sap.impl.SAPUtil.createExceptionBuilder(SAPUtil.java:106)
at org.talend.sap.impl.service.SAPTableDataService.getTableData(SAPTableDataService.java:123)
at local_project.cdpos_0_1.CDPOS.tSAPTableInput_2Process(CDPOS.java:1068)
at local_project.cdpos_0_1.CDPOS.runJobInTOS(CDPOS.java:2046)
at local_project.cdpos_0_1.CDPOS.main(CDPOS.java:1880)
SAP dump:
|What happened? |
| You attempted to extend an internal table, but the required space was |
| not available. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What can you do? |
| Note which actions and input led to the error. |
| |
| For further help in handling the problem, contact your SAP administrator |
| . |
| |
| You can use the ABAP dump analysis transaction ST22 to view and manage |
| termination messages, in particular for long term reference. |
| |
| Try to find out (e.g. by targetted data selection) whether the |
| transaction will run with less main memory. |
| |
| If there is a temporary bottleneck, execute the transaction again. |
| - |
| |
| If the error persists, ask your system administrator to check the |
| following profile parameters: |
| |
| o ztta/roll_area (1.000.000 - 15.000.000) |
| Classic roll area per user and internal mode |
| usual amount of roll area per user and internal mode |
| o ztta/roll_extension (10.000.000 - 500.000.000) |
| Amount of memory per user in extended memory (EM) |
| o abap/heap_area_total (100.000.000 - 1.500.000.000) |
| Amount of memory (malloc) for all users of an application |
| server. If several background processes are running on |
| one server, temporary bottlenecks may occur. |
| Of course, the amount of memory (in bytes) must also be |
| available on the machine (main memory or file system swap). |
| Caution: |
| The operating system must be set up so that there is also |
| enough memory for each process. Usually, the maximum address |
| space is too small. |
| Ask your hardware manufacturer or your competence center |
| about this. |
| In this case, consult your hardware vendor |
| abap/heap_area_dia: (10.000.000 - 1.000.000.000) |
| Restriction of memory allocated to the heap with malloc |
| for each dialog process. |
| Parameters for background processes: |
| abap/heap_area_nondia: (10.000.000 - 1.000.000.000) |
| Restriction of memory allocated to the heap with malloc |
| for each background process. |
| Other memory-relevant parameters are: |
| em/initial_size_MB: (35-1200) |
| Extended memory area from which all users of an |
| application server can satisfy their memory requirement. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Error analysis |
| The internal table "{A:6*\TYPE=%_T00003S00000283O0000005748}" could not be |
| further extended. To enable |
| error handling, the table had to be delete before this log was written. |
| As a result, the table is displayed further down or, if you branch to |
| the ABAP Debugger, with 0 rows. |
| |
| At the time of the termination, the following data was determined for |
| the relevant internal table: |
| |
| Memory location: "Session memory" |
| Row width: 1548 |
| Number of rows: 2566440 |
| Allocated rows: 2566440 |
| Newly requested rows: 8 (in 1 blocks) |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|How to correct the error |
| The amount of storage space (in bytes) filled at termination time was: |
| |
| Roll area...................... 2718352 |
| Extended memory (EM)........... 2002743520 |
| Assigned memory (HEAP)......... 2000050368 |
| Short area..................... " " |
| Paging area.................... 0 |
| Maximum address space.......... " " |
| |
| If the error occures in a non-modified SAP program, you may be able to |
| find an interim solution in an SAP Note. |
| If you have access to SAP Notes, carry out a search with the following |
| keywords: |
| |
| "TSV_TNEW_PAGE_ALLOC_FAILED" " " |
| "SAPLZ_TALEND" or "LZ_TALENDU01" |
| "Z_TALEND_READ_TABLE" |
| |
| If you cannot solve the problem yourself and want to send an error |
| notification to SAP, include the following information: |
| |
| 1. The description of the current problem (short dump) |
| |
| To save the description, choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 2. Corresponding system log |
| |
| Display the system log by calling transaction SM21. |
| Restrict the time interval to 10 minutes before and five minutes |
| after the short dump. Then choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 3. If the problem occurs in a problem of your own or a modified SAP |
| program: The source code of the program |
| In the editor, choose "Utilities->More |
| Utilities->Upload/Download->Download". |
| |
| 4. Details about the conditions under which the error occurred or which |
| actions and input led to the error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.