on 11-12-2013 4:58 PM
Hi,
The job was stopped due to DBIF_DSQL2_SQL_ERROR error. Please find the error details below
ST22
=====
Runtime Errors | DBIF_DSQL2_SQL_ERROR |
Exception | CX_SY_NATIVE_SQL_ERROR |
Date and Time | 11.11.2013 01:01:08 |
Short text
An SQL error occurred when executing Native SQL. |
What happened?
The error 600 occurred in the current database connection "LCA". |
What can you do?
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. |
How to correct the error
Database error text........: "POS(1) Work rolled back: ERROR 2 in | |
SIM_SIMSESSION_CONTR" | |
Database error code........: 600 | |
Triggering SQL statement...: "EXECUTE PROCEDURE "SIM_SIMSESSION_CONTROL"" | |
Internal call code.........: "[DBDS/NEW DSQL]" | |
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_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR" | |
"/SAPAPO/SAPLOM_CORE" or "/SAPAPO/LOM_COREU07" | |
"SIMSCTRL_EXEC_COM" |
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
"SIMSCTRL_EXEC_COM" "(FORM)", or its possible occurrence must be declared in
the
RAISING clause of the procedure.
To prevent the exception, note the following:
SM21
=====
Database error 600 at EXE
> POS(1) Work rolled back: ERROR 2 in SIM_SIMSESSION_CONTR
Run-time error "DBIF_DSQL2_SQL_ERROR" occurred
> Short dump "131111 005035 ampsv02636prd_PPS_00 BATCH " created
Transaction Canceled 00 671 ( DBIF_DSQL2_SQL_ERROR 20131111005035ampsv02636prd_PPS_00 BATCH 100 )
Database error 600 at EXE
SAP SCM 5.00 ,
MSSQL Server,: MSSQL 9.00.2047
Kernel 721 : 100
Regards
S.Subramani
Hello Sambandam,
Check notes 1476074 - SMQ2: An SQL error occurred when executing Native SQL
1520318 - Runtime error TASIM_REGISTRATION_FAILED in /SAPAPO/RRP3
BR,
K.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.