#1
|
|||
|
|||
error de tiempo ejec DBIF_RSQL_SQL_ERROR
Hola soy nuevo en el tema sap y necesito ayuda a este tema,
La pltafrma donde esta montado sap es windows 2003 servers SQL 2005 SAP 6.0 Este error afecta a las transacciones st04, db02, st03 ya que no corre el programa que recolecta la informacion agradeceria su ayuda EL DUMPS ES Errores tiempo ejec. DBIF_RSQL_SQL_ERROR Excepción CX_SY_OPEN_SQL_DB Texto breve SQL error in the database when accessing a table. ¿Qué puede hacer? 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. Notas para corregir errores Database error text........: "[468] Cannot resolve the collation conflict between "SQL_Latin1_General_CP850_BIN" and "SQL_Latin1_General_CP850_BIN2" in the equal to operation." Internal call code.........: "[RSQL/OPEN/SRT_MONLOG_DATA2 ]" Please check the entries in the system log (Transaction SM21). 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_SQL_ERROR" "CX_SY_OPEN_SQL_DB" "CL_SOAP_MONI_DB_ADAPTER=======CP" or "CL_SOAP_MONI_DB_ADAPTER=======CM001" "READ_DATA" "READ_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 "READ_DATA" "(METHOD)", or its possible occurrence must be declared in the RAISING clause of the procedure. To prevent the exception, note the following: Info posición de cancelación Termination occurred in the ABAP program "CL_SOAP_MONI_DB_ADAPTER=======CP" - in "READ_DATA". The main program was "SRT_COLLECTOR_FOR_MONITORING ". In the source code you have the termination point in line 88 of the (Include) program "CL_SOAP_MONI_DB_ADAPTER=======CM001". The program "CL_SOAP_MONI_DB_ADAPTER=======CP" was started as a background job. Job Name....... "SAP_SRT_COLLECTOR_FOR_MONITORING" Job Initiator.. "DDIC" Job Number..... 06593100 The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in procedure "READ_DATA" "(METHOD)", but it was neither handled locally nor declared in the RAISING clause of its signature. The procedure is in program "CL_SOAP_MONI_DB_ADAPTER=======CP "; its source code begins in line 1 of the (Include program "CL_SOAP_MONI_DB_ADAPTER=======CM001 ". |
Herramientas | Buscar en Tema |
Desplegado | |
|
|