Цитата:
Динамическая ошибка DBIF_RSQL_INVALID_RSQL
ОсобСит CX_SY_OPEN_SQL_DB
Дата и время 27.05.2009 18:07:44
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Краткий текст |
| Error in module RSQL of the database interface. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Что произошло? |
| Error in the ABAP Application Program |
| |
| The current ABAP program "SAPLABRA" 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 "VIEW_TRIGGER" "(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. |
| Last error logged in SAP kernel |
| |
| Component............ "EM" |
| Version.............. 37 |
| Error code........... 3 |
| Error text........... "invalid Context Handle" |
| Description.......... " " |
| System call.......... " " |
| Module............... "emxx.c" |
| Line................. 1884 |
| |
| The error reported by the operating system is: |
| Error number..... " " |
| Error text....... " " |
| |
| |
| |
| |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Указания по устранению ошибки |
| 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" |
| "SAPLABRA" or "LABRAF10" |
| "VIEW_TRIGGER" |
| |
| |
| |
| The exception must either be prevented, caught within proedure |
| "VIEW_TRIGGER" "(FORM)", or its possible occurrence must be declared in the |
| RAISING clause of the procedure. |
| To prevent the exception, note the following: |
----------------------------------------------------------------------------------------------------
Вход
Регистрация
FAQ пользователя
Поиск
И в SAP обращаться не пробовали?
