Hi,everybody,I'm new here.
I met a difficulty problem in ECC6.0, one of the background jobs was failed working last week,but it was worked fine lasted few years.
I found any information in ST22 and dev_w(*)
The dev_w(*) says ERROR => dbtran ERROR (set_input_da_spec): statement too big marker count = 10123 > max. marker count = 9999
The ST22 informatiom like below:
Runtime Errors DBIF_RSQL_INVALID_RSQL
Exception CX_SY_OPEN_SQL_DB
Date and Time 2014-08-18 04:29:43
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Short text |
| Error in module RSQL of the database interface. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|发生了什么? |
| Error in the ABAP Application Program |
| |
| The current ABAP program "ZSD48056" had to be terminated because it has |
| come across a statement that unfortunately cannot be executed. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|你能做什么? |
| Note down which actions and inputs caused the error. |
| |
| |
| To process the problem further, contact you SAP system |
| administrator. |
| |
| Using Transaction ST22 for ABAP Dump Analysis, you can look |
| at and manage termination messages, and you can also |
| keep them for a long time. |
| 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. |
| |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|错误分析 |
| An exception occurred that is explained in detail below. |
| The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught |
| in |
| procedure "FRM_GET_DATA" "(FORM)", nor was it propagated by a RAISING clause. |
| Since the caller of the procedure could not have anticipated that the |
| exception would occur, the current program is terminated. |
| The reason for the exception is: |
| The SQL statement generated from the SAP Open SQL statement violates a |
| restriction imposed by the underlying database system of the ABAP |
| system. |
| |
| Possible error causes: |
| o The maximum size of an SQL statement was exceeded. |
| o The statement contains too many input variables. |
| o The input data requires more space than is available. |
| o ... |
| |
| You can generally find details in the system log (SM21) and in the |
| developer trace of the relevant work process (ST11). |
| In the case of an error, current restrictions are frequently displayed |
| in the developer trace. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|如何更正此错误 |
| The SAP Open SQL statement concerned must be divided into several |
| smaller units. |
| If the problem occurred due to the use of an excessively large table |
| in an IN itab construct, you can use FOR ALL ENTRIES instead. |
| When you use this addition, the statement is split into smaller units |
| according to the restrictions of the database system used. |
| |
| |
| 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: |
| |
| "DBIF_RSQL_INVALID_RSQL" "CX_SY_OPEN_SQL_DB" |
| "ZSD48056" or "ZSD48056" |
| "FRM_GET_DATA" |
| |
| 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. |
| |
| |
| The exception must either be prevented, caught within proedure |
| "FRM_GET_DATA" "(FORM)", or its possible occurrence must be declared in the |
| RAISING clause of the procedure. |
| To prevent the exception, note the following: |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|系统环境 |
| SAP-Release 700 |
| |
| Application server... "xxxxxx" |
| Network address...... "10.1.xx.xx" |
| Operating system..... "AIX" |
| Release.............. "6.1" |
| Hardware type........ "00C50E564C00" |
| Character length.... 16 Bits |
| Pointer length....... 64 Bits |
| Work process number.. 21 |
| Shortdump setting.... "full" |
| |
| Database server... "XXXXXX" |
| Database type..... "ORACLE" |
| Database name..... "XXX" |
| Database user ID.. "SAPSR3" |
| |
| Char.set.... "C" |
| |
| SAP kernel....... 700 |
| created (date)... "May 2 2010 21:56:27" |
| create on........ "AIX 2 5 005DD9CD4C00" |
| Database version. "OCI_102 (10.2.0.2.0) " |
| |
| Patch level. 254 |
| Patch text.. " " |
| |
| Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*" |
| SAP database version. 700 |
| Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6" |
| |
| Memory consumption |
| Roll.... 9139904 |
| EM...... 0 |
| Heap.... 1199542352 |
| Page.... 24576 |
| MM Used. 1153298792 |
| MM Free. 52375360 |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|用户，事务... |
| |
| Client.............. 800 |
| User................ "GW-ABAP" |
| Language key........ 1 |
| Transaction......... " " |
| Transactions ID..... "53F1FE2B00BF0FC0E10080000A015231" |
| |
| Program............. "ZSD48056" |
| Screen.............. "SAPMSSY0 1000" |
| Screen line......... 6 |
----------------------------------------------------------------------------------------------------
Now , what can I do.