Symptom
Disclaimer:
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
- SDM fails with the error "STRING_SIZE_TOO_LARGE".
- The issue occurs during data migration as part of S/4HANA postprocessing in "uptime" silent data migration programs.
- Error message: "STRING_SIZE_TOO_LARGE".
ST22 Dump example:
----------------------------------------------------------------------------------------------------
Category
ABAP programming error
Runtime Errors
STRING_SIZE_TOO_LARGE
Except.
CX_SY_STRING_SIZE_TOO_LARGE
ABAP: Program SAPLSHDB_PFW_FUNCTIONS
Application Component BC-DB-HDB-PFW
Date and Time <timestamp> (UTC)
-------------------------------------------------
----------------------------------------------------
---------------------------------------------------
-----------------------------------------------|Short Text
||Maximum string length exceeded
|-----------------------------------------------------------
-------------------------------------------------------------
------------------------------------------------------------
--------------------|
What happened?
||Error in the ABAP application program. ||
|| The current ABAP program "SAPLSHDB_PFW_FUNCTIONS" had to be terminated because
|| it found a
|| statement that could not be executed.
|-----------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------
------------|
...
Error analysis
|| An exception has occurred in class "CX_SY_STRING_SIZE_TOO_LARGE". This
|| exception was not caught ||
in procedure "SHDB_PFW_RFC_WRAPPER" "(FUNCTION)" or propagated by a RAISING ||
clause. ||
Since the caller of the procedure could not have anticipated this ||
exception, the current program was terminated. ||
The reason for the exception occurring was: ||
The reason for the exception is: ||
An attempt was made create a string of length 2145386962 (bytes). This exceeds ||
the maximum length for a string (2145386496) however. ||
2145386496.
|------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------
---------|
How to correct the error
|| If the exception cannot be prevented, "CX_SY_STRING_SIZE_TOO_LARGE" must be
|| caught within
|| procedure "SHDB_PFW_RFC_WRAPPER" "(FUNCTION)" or declared in the procedure's
|| RAISING clause.
|| To prevent the exception, note the following:
||
|| Do not allow this many strings to be created.
||
|| If the error occurs in a non-modfied SAP program, you might be able to
|| find a solution in the SAP Notes system. If you have access to the SAP
|| Notes system, check there first using the following keywords:
||
|| "STRING_SIZE_TOO_LARGE" CX_SY_STRING_SIZE_TOO_LARGE
|| "SAPLSHDB_PFW_FUNCTIONS" bzw. LSHDB_PFW_FUNCTIONSU01
|| "SHDB_PFW_RFC_WRAPPER"
|| If you cannot solve the problem yourself, please send the following
|| information to SAP:
...
----------------------------------------------------------------------------------------------------
|Chain of Exception Objects |
----------------------------------------------------------------------------------------------------
|Level Class |
|Attrib. Name Value |
----------------------------------------------------------------------------------------------------
|1 CX_SY_STRING_SIZE_TOO_LARGE |
|(Program) SAPLSHDB_PFW_FUNCTIONS |
|(Include) LSHDB_PFW_FUNCTIONSU01 |
|(Row) 217 |
|(Short Text) Maximum string length (2145386496 bytes) exceeded |
|(Long Text) Diagnosis |
| The current statement attempted to modify an ABAP string in such a |
| way that the maximum string length of 2145386496 is exceeded. |
| This situation can occur in all statements that make strings longer|
| (such as CONCATENATE, REPLACE, or SHIFT LEFT), plus in string ex |
| pressions and in CALL TRANSFORMATION. |
| Procedure |
| Once the exception CX_SY_STRING_SIZE_TOO_LARGE is caught, the |
| content of the target string is undefined. The target string may |
| already be modified in parts and have reached this size. For this |
| reason it should be initialized once the exception is caught. |
|T100_MSGID SABP_RUNT |
|T100_MSGNO 001 |
|T100_MSGV1 2145386496 |
|INCREMENT_BYTES 2034 |
|IS_RESUMABLE |
|KERNEL_ERRID |
|MAX_STRING_SIZE_BYTES 2145386496 |
|SIZE_BYTES 2145384928 |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Information on where terminated |
| The termination occurred in ABAP program or include "SAPLSHDB_PFW_FUNCTIONS", |
| in "SHDB_PFW_RFC_WRAPPER". The |
| main program was "SAPMSSY1". |
| |
| In the source code, the termination point is in line 217 of include |
| "LSHDB_PFW_FUNCTIONSU01". |
| include "LSHDB_PFW_FUNCTIONSU01". |
| The termination is due to exception "CX_SY_STRING_SIZE_TOO_LARGE" occurring in |
| procedure "SHDB_PFW_RFC_WRAPPER" "(FUNCTION)", |
| but not being handled locally there or being declared in the RAISING |
| clause. |
| The procedure is in program "SAPLSHDB_PFW_FUNCTIONS". Its source code begins |
| in line 1 of |
| include "LSHDB_PFW_FUNCTIONSU01". |
----------------------------------------------------------------------------------------------------
Read more...
Environment
SAP HANA 2.0, HANA DB Parallelization Framework
Keywords
SDM, silent data migration, STRING_SIZE_TOO_LARGE, CX_SY_STRING_SIZE_TOO_LARGE, SAPLSHDB_PFW_FUNCTIONS, SHDB_PFW_RFC_WRAPPER, SAP S/4HANA, data migration, Dispatcher Timeout, package size adjustment, ABAP runtime error, BC-DB-HDB-PFW. , KBA , FI-GL-GL-F , Value Added Tax (VAT) , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview