ABAP SQL error!
Hi,
I had installed ABAP on application server WAS 6.4 to enable ABAP engine along with the J2EE engine. but when i started the the server it is giving me the error " an sql error occured when accessing the table" in SAP management console.it is in the current status and the color has turned red on the current status.i had actually restarted the system after installing ABAP on WAS.
any remedy to the posted problem?
Hi Ravi,
May I ask how you solved this issue,I have the same problem.
Thanks,
Maryam
Similar Messages
-
DbSl Trace: CONNECT failed with sql error '12518' at IMPORT ABAP
Hi
We are trying to install ECC 6.0 on windows 2008 SP2 and oracle 10.2.0.4. We get an error at IMPORT ABAP phase.
content of import_monitor.java :
java version "1.4.2_26"
Java(TM) Platform, Standard Edition for Business (build 1.4.2_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_26-b03, mixed mode)
Import Monitor jobs: running 1, waiting 1, completed 26, failed 0, total 28.
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.
content of SAPSLOAD.log:
E:\usr\sap\UED\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100705173108
E:\usr\sap\UED\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#5 $ SAP
E:\usr\sap\UED\SYS\exe\uc\NTAMD64\R3load.exe: version R7.01/V1.4 [UNICODE]
Compiled Feb 24 2009 23:41:07
E:\usr\sap\UED\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -stop_on_error
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12518
DbSl Trace: CONNECT failed with sql error '12518'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12518
DbSl Trace: CONNECT failed with sql error '12518'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12518
DbSl Trace: CONNECT failed with sql error '12518'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12518
DbSl Trace: CONNECT failed with sql error '12518'
(DB) ERROR: DbSlErrorMsg rc = 99
E:\usr\sap\UED\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
E:\usr\sap\UED\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100705173108
content of sqlnet.log file:
Fatal NI connect error 12560, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleUED)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=(SID=UED)(CID=(PROGRAM=E:\oracle\UED\102\bin\sqlplus.exe)(HOST=U34SSAPUED)(USER=uedadm))))
VERSION INFORMATION:
TNS for 64-bit Windows: Version 10.2.0.4.0 - Production
Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 10.2.0.4.0 - Production
Time: 05-JUL-2010 16:19:39
Tracing not turned on.
Tns error struct:
ns main err code: 12560
TNS-12560: TNS:protocol adapter error
ns secondary err code: 0
nt main err code: 530
TNS-00530: Protocol adapter error
nt secondary err code: 2
nt OS err code: 0
Fatal NI connect error 12518, connecting to:
(DESCRIPTION=(ADDRESS=(COMMUNITY=SAP.WORLD)(PROTOCOL=TCP)(HOST=u34ssapued)(PORT=1527))(CONNECT_DATA=(SID=UED)(GLOBAL_NAME=UED.WORLD)(CID=(PROGRAM=E:\usr\sap\UED\SYS\exe\uc\NTAMD64\R3load.exe)(HOST=U34SSAPUED)(USER=uedadm))))
VERSION INFORMATION:
TNS for 64-bit Windows: Version 10.2.0.2.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 10.2.0.2.0 - Production
Time: 05-JUL-2010 17:28:38
Tracing not turned on.
Tns error struct:
ns main err code: 12564
TNS-12564: TNS:connection refused
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Best Regards...,Hi,
TNS-12560: TNS:protocol adapter error
Probably your listener or database is down...
If both are running, just stop the installation and reboot the server.
Then again start listener and database and continue SAP installation with "Continue old installation" option..
Also make sure that below environment variables are set properly...
ORACLE_HOME
ORACLE_SID
DBSID
Regards.
Rajesh Narkhede -
SAP installation stopped at ABAP load error: sql error '12537'
Hi ,
I am installing SAP ECC 6.0 with EHP4 and ABAP with Oracle 11G on AIX 6.1 load ended up with the error as below, please help
Import Monitor jobs: running 3, waiting 13, completed 9, failed 3, total 28.
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 10, failed 3, total 28.
Import Monitor jobs: running 3, waiting 12, completed 10, failed 3, total 28.
Loading of 'SAPPOOL' import package: ERROR
Import Monitor jobs: running 2, waiting 12, completed 10, failed 4, total 28.
Loading of 'E071K' import package: OK
Import Monitor jobs: running 1, waiting 12, completed 11, failed 4, total 28.
Import Monitor jobs: running 2, waiting 11, completed 11, failed 4, total 28.
Import Monitor jobs: running 3, waiting 10, completed 11, failed 4, total 28.
Loading of 'SAPSDOCU' import package: ERROR
Import Monitor jobs: running 2, waiting 10, completed 11, failed 5, total 28.
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 1, waiting 10, completed 12, failed 5, total 28.
Import Monitor jobs: running 2, waiting 9, completed 12, failed 5, total 28.
Import Monitor jobs: running 3, waiting 8, completed 12, failed 5, total 28.
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 2, waiting 8, completed 12, failed 6, total 28.
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 1, waiting 8, completed 13, failed 6, total 28.
Import Monitor jobs: running 2, waiting 7, completed 13, failed 6, total 28.
Import Monitor jobs: running 3, waiting 6, completed 13, failed 6, total 28.
Loading of 'SAPUSER' import package: ERROR
Import Monitor jobs: running 2, waiting 6, completed 13, failed 7, total 28.
tail -20 SAPSSRC.log
DbSl Trace: CONNECT failed with sql error '12537'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12537
DbSl Trace: CONNECT failed with sql error '12537'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12537
DbSl Trace: CONNECT failed with sql error '12537'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12537
DbSl Trace: CONNECT failed with sql error '12537'
(DB) ERROR: DbSlErrorMsg rc = 99
/usr/sap/HRQ/SYS/exe/uc/rs6000_64/R3load: job finished with 1 error(s)
/usr/sap/HRQ/SYS/exe/uc/rs6000_64/R3load: END OF LOG: 20111105170542
tail -20 FUPARAREF.log
DbSl Trace: CONNECT failed with sql error '12537'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12537
DbSl Trace: CONNECT failed with sql error '12537'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12537
DbSl Trace: CONNECT failed with sql error '12537'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12537
DbSl Trace: CONNECT failed with sql error '12537'
(DB) ERROR: DbSlErrorMsg rc = 99
/usr/sap/HRQ/SYS/exe/uc/rs6000_64/R3load: job finished with 1 error(s)
/usr/sap/HRQ/SYS/exe/uc/rs6000_64/R3load: END OF LOG: 20111105170611Reasons can be many, you please check whether oracle and listener are up or not. Check 'R3trans -d' and trans.log
Similar problem thread -
error when applying PI_BASIS patch SAPKIPYM03 on ECC 6
Thanks -
HI EXPERTS!
CAN ANYBODY TELL ME HOW TO RESOLVE THIS RUNTIME ERROR ON EXECUTING TRANSACTION PC00_M40_CALC.
Runtime errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Occurred on 07.08.2007 at 14:13:06
An SQL error occurred when accessing a table.
What happened?
What can you do?
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"GET_SLAB_RATE" "(METHOD)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
How to correct the error
The exception must either be prevented, caught within the procedure
"GET_SLAB_RATE"
"(METHOD)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-04031: unable to allocate 4200 bytes of
shared memory ("shared pool","SELECT * FROM "T7INT1" WHERE...","library
cache","kkslpkp - literal info.")"
Internal call code.........: "[RSQL/FTCH/T7INT1 ]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"CL_HRPAYIN_SLABRATES==========CP " or "CL_HRPAYIN_SLABRATES==========CM002 "
"GET_SLAB_RATE"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "hmsidev01"
Network address.......... "10.249.16.150"
Operating system......... "Windows NT"
Release.................. "5.0"
Hardware type............ "2x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "HMSIDEV01"
Database type............ "ORACLE"
Database name............ "DEV"
Database owner........... "SAPDEV"
Character set............ "English_United State"
SAP kernel............... "620"
Created on............... "Jun 13 2004 22:06:10"
Created in............... "NT 5.0 2195 Service Pack 2 x86 MS VC++ 12.00"
Database version......... "OCI_817_SHARE "
Patch level.............. "1511"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.."
SAP database version..... "620"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
User, transaction...
Client.............. 100
User................ "IR1"
Language key........ "E"
Transaction......... "PC00_M40_CALC "
Program............. "CL_HRPAYIN_SLABRATES==========CP "
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "CL_HRPAYIN_SLABRATES==========CP
" in "GET_SLAB_RATE".
The main program was "HINCALC0 ".
The termination occurred in line 12 of the source code of the (Include)
program "CL_HRPAYIN_SLABRATES==========CM002 "
of the source code of program "CL_HRPAYIN_SLABRATES==========CM002 " (when
calling the editor 120).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "GET_SLAB_RATE" "(METHOD)" but was not handled locally, not declared
in the
RAISING clause of the procedure.
The procedure is in the program "CL_HRPAYIN_SLABRATES==========CP ". Its source
code starts in line 1
of the (Include) program "CL_HRPAYIN_SLABRATES==========CM002 ".
Source code extract
000010 METHOD get_slab_rate .
000020
000030 DATA: wa_t7int1 TYPE t7int1,
000040 wa_t7int3 TYPE t7int3,
000050 slab_code TYPE t7int1-slcod.
000060 CLEAR: wa_t7int1 ,
000070 wa_t7int3 ,
000080 slab_code .
000090
000100
000110 * Select slab code from t7int1.
SELECT * FROM t7int1 INTO wa_t7int1
000130 WHERE sltyp = slab_type
000140 AND begda LT ref_date
000150 AND endda GE ref_date.
000160 MOVE wa_t7int1-slcod TO slab_code.
000170 ENDSELECT.
000180
000190 * Find out the rate for the salb code in which the income falls.
000200 SELECT * FROM t7int3 INTO wa_t7int3 WHERE slcod = slab_code ORDER BY
000210 hirge.
000220 IF wa_t7int3-hirge GE income.
000230 EXIT.
000240 ENDIF.
000250 ENDSELECT.
000260
000270 slab_rate = wa_t7int3-txval.
000280
000290
000300 ENDMETHOD.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 215
SY-TABIX 63 SY-DBCNT 1
SY-FDPOS 1 SY-LSIND 0
SY-PAGNO 1 SY-LINNO 1
SY-COLNO 1 SY-PFKEY
SY-UCOMM SY-TITLE Payroll Driver, India
SY-MSGTY SY-MSGID
SY-MSGNO 000 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
16 METHOD GET_SLAB_RATE
CL_HRPAYIN_SLABRATES==========CP
CL_HRPAYIN_SLABRATES==========CM002 12
CL_HRPAYIN_SLABRATES
15 FORM STDDED03
HINCALC0
PCTAXIN0 564
14 FORM CALC_STANDARD_DEDUCTION
HINCALC0
PCTAXIN0 466
13 FORM FUINTAX
HINCALC0
PCTAXIN0 253
12 FORM AS-FUNKTION
HINCALC0
PCASFIN0 13
11 FORM ASLOOP
HINCALC0
RPCHRT09_ASLOOP 58
10 FORM MONATSABRECHNUNG
HINCALC0
RPCHRT09_MONATSABRECHNUNG 48
9 FORM RUECKRECHNUNG
HINCALC0
RPCHRT09_RUECKRECHNUNG 136
8 FORM MAIN
HINCALC0
RPCHRT09_MAIN 134
7 FORM %_GET_PERNR
HINCALC0
RPCHRT09 762
6 FORM FILL_INFOTYPE_TABLES_AND_PUT
SAPDBPNP
DBPNPF03 542
5 FORM PUTPERN
SAPDBPNP
DBPNPF03 470
4 FORM LOOP_AT_INDEX_AND_PUT
SAPDBPNP
DBPNPF01 996
3 FORM PUT_PERNR
SAPDBPNP
DBPNPF01 194
2 FORM %_ROOT
SAPDBPNP
SAPDBPNP 151
1 EVENT SYSTEM-EXIT
HINCALC0
20
Chosen variables
16 METHOD GET_SLAB_RATE
CL_HRPAYIN_SLABRATES==========CP
CL_HRPAYIN_SLABRATES==========CM002 12
SLAB_TYPE D
4
4
REF_DATE 20070331
33333333
20070331
INCOME ####Q#
00005991
0001153C
SLAB_RATE ########
00000000
0000000C
WA_T7INT1 0000000000000000
222233333333333333332
000000000000000000000
WA_T7INT3 ####### #######
222222000000022222220000000
000000000000C0000000000000C
SLAB_CODE
2222
0000
%_VIASELSCR #
0
4
<%_TABLE_T7INT1> ???
%_SPACE
2
0
SYST-REPID CL_HRPAYIN_SLABRATES==========CP
4454554544554445454533333333334522222222
3CF820199EF3C1221453DDDDDDDDDD3000000000
SY-XPROG SAPDBPNP
5454454522222222222222222222222222222222
310420E000000000000000000000000000000000
SY-REPID CL_HRPAYIN_SLABRATES==========CP
4454554544554445454533333333334522222222
3CF820199EF3C1221453DDDDDDDDDD3000000000
SY-XFORM %_ROOT
255445222222222222222222222222
5F2FF4000000000000000000000000
%_DUMMY$$
2222
0000
<%_TABLE_T7INT3> ???
15 FORM STDDED03
HINCALC0
PCTAXIN0 564
STD_DED_TAB Table[initial]
0000FFFD
0000FFFF
SY-TABIX 63
3000
F000
STD_PERCENT #####
00000
0000C
%_SPACE
2
0
SYST-REPID HINCALC0
4444444322222222222222222222222222222222
89E31C3000000000000000000000000000000000
SPACE
2
0
%_DUMMY$$
2222
0000
$ENDDATE 20070331
33333333
20070331
$PRE_DEDN_AMOUNT ####Q#
00005991
0001153C
$CALC_DEDN ########
00000000
0000000C
SY-REPID HINCALC0
4444444322222222222222222222222222222222
89E31C3000000000000000000000000000000000
SY ×#######?###?###########################
D000000030003000000000000000000000000000
70001000F000F000000000000000000000000000
... + 40 ###################################5###
0000000000000000000080000000000000003000
1000100010000000100040000000000000005000
... + 80 ########################################
0000000000000000000000000000000000000000
0000000000000000400000000000000000000000
... + 120 ################################%######
0000000000000000000000000000000020008000
000000000000000000000000000000005000E000
... + 160 ############XM## P############# E0 1
0000000000005400250000000000000222432223
0000700040008D00000020000C0000C000500001
... + 200 000 ####PNP 100
3332222222220000545222222222222222223332
00000000000000000E0000000000000000001000
... + 240 00
222223322222222
000000000000000
NO_OF_ROWS
2
0
SY-TFILL 63
3000
F000
14 FORM CALC_STANDARD_DEDUCTION
HINCALC0
PCTAXIN0 466
P0015[] Table IT_204[12x147]
F7D4DED48000C000000090000000FFFF00004500
871900998000C000C00030000000FFFF40000F00
... + 40
0000C020
20001E80
SW_AUFROLLUNG X
5
8
%BX03242_BLOCK_1000 Log
4662222222222222222222222222222222222222
CF70000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
222
000
SNAME 40INDED
33444442
409E4540
T559A-WTIME 000000
333333
000000
OGRT[] Table IT_299[0x53]
00000000C0002000000030000000FFFF0000E300
000000003000B100000050000000FFFF40000310
... + 40
1000C200
00001E00
ENDDATE 20070331
33333333
20070331
T596F-PGMNA HINCALC0
4444444322222222222222222222222222222222
89E31C3000000000000000000000000000000000
T596F-MODNA STDDED03
55444433
34445403
P_PRE_DEDUCTION_BALANCE ####Q#
00005991
0001153C
STANDARD_DEDUCTION ########
00000000
0000000C
P2006[] Table IT_460[37x168]
9ED40000E000C0002000A0000000FFFF00008500
877900006000C100500080000000FFFF40000600
... + 40
0000C020
20001E00
13 FORM FUINTAX
HINCALC0
PCTAXIN0 253
ANNUAL_IRREGULAR_INCOME ####3#%L
00003124
0000365C
%_SET_VOID_%_APP_%
222222222222222222222222222222
000000000000000000000000000000
ANNUAL_PERK ########
00000000
0000000C
SET_ODC
2
0
%_SET_ODC_%_APP_%
222222222222222222222222222222
000000000000000000000000000000
SET_REVR
2
0
P%2007 00000000 000000000000000000000
3333333322222222222333333333333333333333
0000000000000000000000000000000000000000
... + 40 000000 00
3333332222222222222222222222222222222233
0000000000000000000000000000000000000000
... + 80 0000000000 00###### ###### 00000000000
3333333333233000000200000022233333333333
000000000000000000C000000C00000000000000
... + 120 0000000000000000000000000
3333333333333333333333333222222222222222
0000000000000000000000000000000000000000
... + 160
222222222222
000000000000
PRE_DEDUCTION_BALANCE ####Q#
00005991
0001153C
OCRSN
2222
0000
APER-PAPER-PABRJ 2006
3333
2006
APER-IAPER-PABRJ 2007
3333
2007
SW_INTIM
2
0
APER-PAPER 200612
333333
200612
ANN_PTAX_AMT ########
00000000
0000000C
12 FORM AS-FUNKTION
HINCALC0
PCASFIN0 13
P0584 00000000 000000000000000000000
3333333322222222222333333333333333333333
0000000000000000000000000000000000000000
... + 40 000000 #
3333332222222222222222222222222222222220
0000000000000000000000000000000000000000
... + 80 ########################################
0000000000000000000000000000000000000000
00000C0000C0000C0000C0000C000000C000000C
... + 120 ####################################
0000000000000000000000000000000000002222
000000C000000C0000C0000C000000C0000C0000
... + 160 0000
22222222222333322222
00000000000000000000
ORGDIR 00000 0000000000000000 00 0
3333322222222333333333333333322332222223
0000000000000000000000000000000000000000
... + 40 0000000 0000000000000000000000000
3333333222222223333333333333333333333333
0000000000000000000000000000000000000000
... + 80 0000000000000 00000000
3333333333333223333333322222222222222222
0000000000000000000000000000000000000000
... + 120 00000000000000 000000000000000000000
3333333333333323333333333333333333332222
0000000000000000000000000000000000000000
RP-IMP-CD-SUBRC 0
0000
0000
CD-SUBRC 0
0000
0000
CD-INDEX 0
0000
0000
IT[] Table IT_490[63x53]
EFC47AC4F000E000300030000000FFFF00005100
0AB903399000A100F00050000000FFFF40000810
... + 40
2000C000
B0009E00
IT */418######### # ####################Q
2233300000000020222000000000000000000005
AF418000000000000000000000C0000000C00011
... + 40 #
9912222222222
53C0000000000
RGDIR_CA[] Table IT_383[0x156]
00003ED4E0007000000090000000FFFF0000C100
000086791000F1000000C0000000FFFF40000810
... + 40
4000C000
00001400
RGDIR_CA 00000 0000000000000000 00 0
3333322222222333333333333333322332222223
0000000000000000000000000000000000000000
... + 40 0000000 0000000000000000000000000
3333333222222223333333333333333333333333
0000000000000000000000000000000000000000
... + 80 0000000000000 00000000
3333333333333223333333322222222222222222
0000000000000000000000000000000000000000
... + 120 00000000000000 000000000000000000000
333333333333332333333333333333333333
000000000000000000000000000000000000
%%_DIR2[] Table IT_218[0x54]
000000009000D000000030000000FFFF0000D100
000000006000A000000060000000FFFF40008210
... + 40
6000C000
40001400
<%_TABLE_T599B> ???
PY_PM_CONTAINER 00000000
2222222222222222222222222222222233333333
0000000000000000000000000000000000000000
... + 40 0
3222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
PNPSTATU-LOW
222
000
SET_LCW 010
333
010
11 FORM ASLOOP
HINCALC0
RPCHRT09_ASLOOP 58
P_WITH_LOG X
5
8
SW_EXPORT_ES
2
0
ASNUM 215
D000
7000
APER_NUMB 15
0000
F000
NEXT_AS_ENTRY 244
F000
4000
SW_REPETITION X
5
8
SW_P0005_CHANGED
2
0
PNPSACHZ
222222222
000000000
PTEXT[] Table IT_139[0x548]
0000CCC460008000000020000000FFFF00004300
00000D79C000B000000042000000FFFF40000500
... + 40
1000C200
00001400
SW_VOID
2
0
SCREEN %_17SNS0000177553_%_%_%_%_%_%_
2533545333333333352525252525252222222222
5F173E30000177553F5F5F5F5F5F5F0000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120 SRI00001#00000 ####
2222222222222222222225543333303333320000
0000000000000000000003290000100000000000
SW_PROT
2
0
PNPSBMOD-LOW
2222
0000
PTEXT_LINES 0
0000
0000
10 FORM MONATSABRECHNUNG
HINCALC0
RPCHRT09_MONATSABRECHNUNG 48
CALC_CURRENCY INR
44522
9E200
SY-SUBRC 0
0000
0000
CALC_CURR_DEC 1380862210
0
2
TCURX-CURRDEC 0
0
0
PNPPERSK-LOW
22
00
PNPKOSTL
22222222222222222222222
00000000000000000000000
SL_BRUTTO
2
0
FC-SL_B_N
2
0
%_PNPSNAME_%_APP_% PNPSNAMEEE name can be sorted to
5455444444266662666266276776622222222276
0E03E1D5550E1D5031E02503F24540000000004F
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 @1FQMultiple selection@
2224345547676766276666766642222222222222
000016C1D5C490C5035C5349FE00000000000000
... + 120
222
000
APER-CALCD X
5
8
DT /AEA00200612 00000000########
24443333333322333333330000000022222
F1510020061200000000000000000C00000
DT[] Table IT_1916[4x35]
F8F40000E0007000000020000000FFFF0000E400
06090000A100C700400030000000FFFF40008610
... + 40
1000C220
00001E00
9 FORM RUECKRECHNUNG
HINCALC0
RPCHRT09_RUECKRECHNUNG 136
APER-PAYTY
2
0
SY-XPROG SAPDBPNP
5454454522222222222222222222222222222222
310420E000000000000000000000000000000000
PYCT 0<>
0000FFFF
0000FFFF
PNP-SW-AUTH-SKIPPED-RECORD 0
3
0
P0007[] Table IT_201[4x138]
CBC47DD48000C000000080000000FFFF00005400
80390F99500090004000A0000000FFFF40008B00
... + 40
0000C020
20001E80
PNPKOKRS[] Table IT_52[0x11]
0000000020003000000000000000FFFF04007200
00000000A00040000000B0000000FFFF44008700
... + 40
0000C000
A0001400
PNPBLCKT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
222
000
FC-NT_BEGIN 0
0000
0000
PNP-SW-IGNORELOCKEDRECORDS Y
5
9
FROM_DATE 00000000
33333333
00000000
%_SET_LCW_%_APP_%
222222222222222222222222222222
000000000000000000000000000000
8 FORM MAIN
HINCALC0
RPCHRT09_MAIN 134
%_PNPFKBER_%_APP_% PNPFKBERFunctional Area to
5454444547667666662476622222222222222276
0E06B25265E349FE1C012510000000000000004F
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 @1FQMultiple selection@
2224345547676766276666766642222222222222
000016C1D5C490C5035C5349FE00000000000000
... + 120
222
000
PERNR-PERNR 00003015
33333333
00003015
Table IT_235[0x178]
000045D4A000E0000000B0000000FFFF00003400
000080390000B000000020000000FFFF40008110
... + 40
1000C200
00001400
P0027[] Table IT_234[0x1851]
0000A4D49000E000000030000000FFFF0000DE00
00008F39F000A0000000B7000000FFFF40000610
... + 40
0000C200
80001E00
PNPENAME
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
222
000
INFTY[] Table IT_116[34x4]
8EC4000050007000200000000000FFFF0D008000
0E790000A0004000200040000000FFFF43000900
... + 40
2000C000
20001400
INFTY 0078
3333
0078
PNPBLCKP Payroll period
5677666276766622222222222222222222222222
0192FCC00529F400000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
222
000
SY-MSGNO 000
333
000
FC-PGM_TYP ABR
4452
1220
PY12W_MEM_ID_BUFFER T512W_BUFFER
533355454445
45127F256652
RSJOBINFO 00000000
2222222222222222222222222222222233333333
0000000000000000000000000000000000000000
... + 40 000000
3333332222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 ####
0000
0000
P0032 00000000 000000000000000000000
3333333322222222222333333333333333333333
0000000000000000000000000000000000000000
... + 40 000000
3333332222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 #####
2222222222222222222222200000222222222222
000000000000000000000000000C000000000000
... + 120
2222222222222222222222222222222222222222
Hello,
strange, you have the same message in SQL Server forum, but we can see Oracle DB here:
SQL ERROR
Without developer traces it would be difficult to say. But it looks bad enough because of kernel 6.20 patch level 1511 (definitely dboraslib.dll has similar patch level) and Oracle 8.1.7 are out of support since years.
best regards -
SQL error 3113 occurred when executing EXEC SQL.
Hi,
We are facing one typical problem, One background is failing regularly with
below dump. as we now got all notes giving information, if database restarted
taking backup, these type of failures occur, but our database is only down for backup once in a week, but it is failing with frequenly.
in this two servers are located in different place, in this job tries to connect
another server to get material statistics.
It is giving some error message in sm21 with
SQL error 3113 occurred when executing EXEC SQL.
work procees in reconnect mode.
all notes saying these types of dump occur when database restared, but this dump
even though database is up.
below is short dump, please can anyone help me from this problem.
ABAP runtime errors DBIF_DSQL2_SQL_ERROR
Occurred on 08.01.2007 at 00:30:28
>> Short dump has not been completely stored. It is too big.
SQL error 3113 occurred when executing EXEC SQL.
What happened?
The error occurred in the current database connection "AZ1".
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
How to correct the error
Database error text........: "ORA-03113: end-of-file on communication channel#"
Triggering SQL statement...: "select mara.groes, mara.brgew, mara.ntgew,
mara.gewei, mara.volum, mara.voleh, mara.mstae, mara.mstde, mara.prdha,
marc.matnr, marc.werks, marc.mmsta, marc.mmstd from sapr3.mara, sapr3.m
where sapr3.mara.mandt = sapr3.marc.mandt and sapr3.mara.matnr =
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"DBIF_DSQL2_SQL_ERROR"
"ZM2431216 " or "ZM2431216 "
"EXTRACT_GENERAL_DATA"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in th
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error o
or which actions and input led to the error.
System environment
SAP Release.............. "46C"
Application server....... "essceu3"
Network address.......... "172.19.119.198"
Operating system......... "AIX"
Release.................. "5.3"
Hardware type............ "00C7ADBD4C00"
Database server.......... "ukblx176"
Database type............ "ORACLE"
Database name............ "EU3"
Database owner........... "SAPR3"
Character set............ "es_ES.ISO8859-1"
SAP kernel............... "46D"
Created on............... "Jul 9 2006 20:26:33"
Created in............... "AIX 1 5 00447C4A4C00"
Database version......... "OCI_920__OCI_7_API "
Patch level.............. "2257"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.0.5.., ORACLE 8.0.6.., ORACLE
8.1.6.., ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE 10.2.0.."
SAP database version..... "46D"
Operating system......... "AIX 1 4, AIX 2 4, AIX 3 4, AIX 1 5, AIX 2 5, AIX 3
5, , System build information:, , LCHN :
841480"
User, transaction...
Client.............. 600
User................ "MPZMMES"
Language key........ "S"
Transaction......... " "
Program............. "ZM2431216 "
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where termination occurred
The termination occurred in the ABAP/4 program "ZM2431216 " in
"EXTRACT_GENERAL_DATA".
The main program was "ZM2431216 ".
The termination occurred in line 980
of the source code of program "ZM2431216 " (when callin
The program "ZM2431216 " was started as a background jo
Source code extract
009500 mara.ntgew,
009510 mara.gewei,
009520 mara.volum,
009530 mara.voleh,
009540 mara.mstae,
009550 mara.mstde,
009560 mara.prdha,
009570 marc.matnr,
009580 marc.werks,
009590 marc.mmsta,
009600 marc.mmstd
009610 into :w_ops-groes,
009620 :w_ops-brgew,
009630 :w_ops-ntgew,
009640 :w_ops-gewei,
009650 :w_ops-volum,
009660 :w_ops-voleh,
009670 :w_ops-mstae,
009680 :w_ops-mstde,
009690 :w_ops-prdha,
009700 :w_ops-matnr,
009710 :w_ops-werks,
009720 :w_ops-mmsta,
009730 :w_ops-mmstd
009740 from sapr3.mara, sapr3.marc
009750 where sapr3.mara.mandt = sapr3.marc.mandt
009760 and sapr3.mara.matnr = sapr3.marc.matnr
009770 and sapr3.mara.mandt = :p_mandt
009780 and sapr3.mara.matnr = :w_ebs-matnr
009790 and sapr3.marc.werks = :p_owerks
> ENDEXEC.
009810 endform. " extract_general_data
009820 *&
009830 *& Form append_i_ops
009840 *&
009850 * Appends W_OPS to I_OPS
009860 *
009870 form append_i_ops.
009880 append w_ops to i_ops.
009890 endform. " append_i_ops
009900 *&
009910 *& Form extract_material_description
009920 *&
009930 * Extracts a Material Description from the remote database an
009940 * modifies the current record in I_OPS.
009950 *
009960 * >P_SPRAS Language Key
009970 *
009980 form extract_material_description using p_spras.
009990 EXEC sql performing set_langauge.
Contents of system fields
SY field contents..................... SY field contents............
SY-SUBRC 0 SY-INDEX 0
SY-TABIX 1 SY-DBCNT 1
SY-FDPOS 18 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1
Chosen variables
Name.......................... Contents.1........2........3....+..
W_EBS-PRAT4
2
0
W_OPS-GROES
22222222222222222222222222222222
00000000000000000000000000000000
W_OPS-BRGEW #######
0000000
000000C
W_OPS-NTGEW #######
0000000
000000C
regards,
krishnaiah.Hi,
This is usually a SERVER SIDE DATABASE PROBLEM or SQLNET LISTENER (server side) PROBLEM. The client side should initially be ignored and instead the server should be investigated. In rare cases, this can be caused by client
side memory or other resource problem, or a DLL version mismatch, but this is
unlikely.
Enlist the assistance of your DBA. Then reproduce the ORA-3113 error on your
client application. Ask your DBA to look at the database side Alert.log and
trace files and look for ANY activity. Any activity that coincides with your
ORA-3113 will be a clue.
REgards
Vinod -
While running the livecache server test a native sql error occures
We are using scm4.1 livecache 7.5.0 And every time we are running the livecache test program he is dumping
whith the following dump
patch level scm & scm_basis is 8
Runtime Errors DBIF_DSQL2_SQL_ERROR
Except. CX_SY_NATIVE_SQL_ERROR
Date and Time 31.10.2005 16:50:55
ShrtText
An SQL error occurred when executing Native SQL.
What happened?
Error 600 occurred in the current database connection "LCA".
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
How to correct the error
Database error text........: "Work rolled back: DbpError -28814 in
APS_ORDER_CH"
Database error code .......: 600
Triggering SQL statement...: " ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
? ? ? ? ? ? ? or'"
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_DSQL2_SQL_ERROR" CX_SY_NATIVE_SQL_ERRORC
"/SAPAPO/SAPLOM_PLANNING" or "/SAPAPO/LOM_PLANNINGU08"
"/SAPAPO/OM_ORDER_CHANGE"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
The exception must either be prevented, caught within the procedure
"/SAPAPO/OM_ORDER_CHANGE"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "bebruap2"
Network address.......... "195.213.49.227"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 801586"
Character length......... 16 Bits
Pointer length........... 32 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "BEBRUAP2"
Database type............ "MSSQL"
Database name............ "APD"
Database owner........... "apd"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Aug 23 2005 00:00:49"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "87"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory usage.............
Roll..................... 8176
EM....................... 24040336
Heap..................... 0
Page..................... 1687552
MM Used.................. 1516920
MM Free.................. 572032
SAP Release.............. "640"
User and Transaction
Client.............. 000
User................ "CGRAULS"
Language key........ "E"
Transaction......... "/SAPAPO/OM03 "
Program............. "/SAPAPO/SAPLOM_PLANNING"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "/SAPAPO/SAPLOM_PLANNING" in
"/SAPAPO/OM_ORDER_CHANGE".
The main program was "/SAPAPO/OM_TB_FLOW_QUANTITY ".
The termination occurred in line 91 of the source code of the (Include)
program "/SAPAPO/LOM_PLANNINGU08"
of the source code of program "/SAPAPO/LOM_PLANNINGU08" (when calling the
editor 910).
Processing was terminated because the exception "CX_SY_NATIVE_SQL_ERROR"
occurred in the
procedure "/SAPAPO/OM_ORDER_CHANGE" "(FUNCTION)" but was not handled locally,
not declared in the
RAISING clause of the procedure.
The procedure is in the program "/SAPAPO/SAPLOM_PLANNING ". Its source code
starts in line 5
of the (Include) program "/SAPAPO/LOM_PLANNING$08 ".
Source Code Extract
Line
SourceCde
61
is_gen_params-simversion
62
is_gen_params-dont_set_netchg_flag
63
space.
64
65
Kontrollstruktur IS_GET_CHANGED_OPTIONS anpassen.
66
IF NOT et_changed_orders IS REQUESTED.
67
is_get_changed_options-send_chg_top_order = gc_false.
68
ENDIF.
69
IF NOT et_changed_cap_reqs IS REQUESTED.
70
is_get_changed_options-send_chg_cap_req = gc_false.
71
ENDIF.
72
IF NOT et_changed_io_nodes IS REQUESTED.
73
is_get_changed_options-send_chg_ionode = gc_false.
74
ENDIF.
75
IF NOT et_changed_io_pp_nodes IS REQUESTED.
76
is_get_changed_options-send_chg_io_pp = gc_false.
77
ENDIF.
78
IF NOT et_changed_pegids IS REQUESTED.
79
is_get_changed_options-send_chg_pegid = gc_false.
80
ENDIF.
81
IF NOT et_deleted_fix_pegging IS REQUESTED.
82
is_get_changed_options-send_del_fix_peg = gc_false.
83
ENDIF.
84
start_function 'OM_ORDER_CHANGE'. "#EC *
85
Verbindung zum liveCache aufbauen
86
check_server.
87
connect_to_livecache.
88
COM-Routine zum Anlegen bzw. Überschreiben eines Zeitstrahls
89
90
EXEC sql.
>>>>>
execute procedure "APS_ORDER_CHANGE" (
92
in :ls_gen_com_params,
93
out :lv_rc,
94
in :et_rc,
95
in :it_order_method,
96
in :it_ordkeys,
97
in :it_ordmaps,
98
in :it_orders,
99
in :it_activities,
100
in :it_mode,
101
in :it_cap_reqs,
102
in :it_positions,
103
in :it_inputs,
104
in :it_outputs,
105
in :it_prodflow,
106
in :it_intern_constraints,
107
in :it_extern_constraints,
108
in :it_charact_val_acts,
109
in :it_charact_req_inpnode,
110
in :it_charact_val_outnode,
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Flow Quantity Test
SY-MSGTY
S
SY-MSGID
/SAPAPO/OM_TEST
SY-MSGNO
001
SY-MSGV1
Create transSim
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No. Ty. Program Include Line
Name
3 FUNCTION /SAPAPO/SAPLOM_PLANNING /SAPAPO/LOM_PLANNINGU08 91
/SAPAPO/OM_ORDER_CHANGE
2 FORM /SAPAPO/OM_TB_FLOW_QUANTITY /SAPAPO/OM_TB_FLOW_QUANTITY 802
CHANGE_DATA
1 EVENT /SAPAPO/OM_TB_FLOW_QUANTITY /SAPAPO/OM_TB_FLOW_QUANTITY 11
START-OF-SELECTION
Chosen variables
Name
Val.
No. 3 Ty. FUNCTION
Name /SAPAPO/OM_ORDER_CHANGE
IS_ATP_INFO
01ATP0000001~CGRAULSXX##
334553333333744545455500
011400000001E37215C38800
000000000000000000000000
000000000000000000000000
IS_CONTROLPARAMETERS
霁က#ం̂⍱㔒鲔#####
2222222222222222222222001007190000022
0000000000000000000000100221240000100
0000000000000000000000910002390000000
0000000000000000000000700C335C000C000
IS_GEN_PARAMS
01PLV0000001~CGRAULS
3354533333337445454522222
010C60000001E37215C300000
0000000000000000000000000
0000000000000000000000000
IS_GET_CHANGED_OPTIONS
2222222
0000000
0000000
0000000
IT_ACTIVITIES
Table IT_274[1x256]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_ACTIVITIES
Table reference: 41
TABH+ 0(20) = 5087FFDF00000000000000002900000012010000
TABH+ 20(20) = 0100000000010000FFFFFFFF0487000000290000
TABH+ 40( 8) = 10000000C1308000
store = 0x5087FFDF
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 41 (0x29000000)
label = 274 (0x12010000)
fill = 1 (0x01000000)
leng = 256 (0x00010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000205
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x180112E0
pghook = 0x00000000
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
store_id = 126 (0x7E000000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_CAP_REQS
Table IT_276[1x112]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_CAP_REQS
Table reference: 39
TABH+ 0(20) = 48BB06E000000000000000002700000014010000
TABH+ 20(20) = 0100000070000000FFFFFFFF04870000C0290000
TABH+ 40( 8) = 10000000C1308000
store = 0x48BB06E0
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 39 (0x27000000)
label = 276 (0x14010000)
fill = 1 (0x01000000)
leng = 112 (0x70000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000209
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x188D04E0
pghook = 0x00000000
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
store_id = 124 (0x7C000000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_CHARACT_REQ_INPNODE
Table IT_418[0x140]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_CHARACT_REQ_INPNODE
Table reference: 32
TABH+ 0(20) = 00000000000000000000000020000000A2010000
TABH+ 20(20) = 000000008C000000FFFFFFFF04870000301D0000
TABH+ 40( 8) = 10000000C1308000
store = 0x00000000
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 32 (0x20000000)
label = 418 (0xA2010000)
fill = 0 (0x00000000)
leng = 140 (0x8C000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000142
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
store_id = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_CHARACT_VAL_ACTS
Table IT_417[0x156]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_CHARACT_VAL_ACTS
Table reference: 50
TABH+ 0(20) = 00000000000000000000000032000000A1010000
TABH+ 20(20) = 000000009C000000FFFFFFFF04870000901D0000
TABH+ 40( 8) = 10000000C1308000
store = 0x00000000
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 50 (0x32000000)
label = 417 (0xA1010000)
fill = 0 (0x00000000)
leng = 156 (0x9C000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000144
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
store_id = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_CHARACT_VAL_OUTNODE
Table IT_419[0x156]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_CHARACT_VAL_OUTNODE
Table reference: 60
TABH+ 0(20) = 0000000000000000000000003C000000A3010000
TABH+ 20(20) = 000000009C000000FFFFFFFF04870000901D0000
TABH+ 40( 8) = 10000000C1308000
store = 0x00000000
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 60 (0x3C000000)
label = 419 (0xA3010000)
fill = 0 (0x00000000)
leng = 156 (0x9C000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000144
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
store_id = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_EXTERN_CONSTRAINTS
Table IT_416[0x124]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_EXTERN_CONSTRAINTS
Table reference: 71
TABH+ 0(20) = 00000000000000000000000047000000A0010000
TABH+ 20(20) = 000000007C000000FFFFFFFF04870000E02A0000
TABH+ 40( 8) = 10000000C1308000
store = 0x00000000
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 71 (0x47000000)
label = 416 (0xA0010000)
fill = 0 (0x00000000)
leng = 124 (0x7C000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000215
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
store_id = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_INPUTS
Table IT_278[1x420]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_INPUTS
Table reference: 63
TABH+ 0(20) = 087400E0C0E303E0000000003F00000016010000
TABH+ 20(20) = 01000000A4010000FFFFFFFF04870000202A0000
TABH+ 40( 8) = 10000000C1308000
store = 0x087400E0
ext1 = 0xC0E303E0
shmId = 0 (0x00000000)
id = 63 (0x3F000000)
label = 278 (0x16010000)
fill = 1 (0x01000000)
leng = 420 (0xA4010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000211
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x78DC11E0
pghook = 0x00000000
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
store_id = 123 (0x7B000000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = 0x2029FFDF
hsdir = 0x00000000
ext2 = 0x00000000
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_INTERN_CONSTRAINTS
Table IT_415[0x124]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_INTERN_CONSTRAINTS
Table reference: 49
TABH+ 0(20) = 000000000000000000000000310000009F010000
TABH+ 20(20) = 000000007C000000FFFFFFFF04870000E02A0000
TABH+ 40( 8) = 10000000C1308000
store = 0x00000000
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 49 (0x31000000)
label = 415 (0x9F010000)
fill = 0 (0x00000000)
leng = 124 (0x7C000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000215
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
store_id = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_MODE
Table IT_275[1x164]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_MODES
Table reference: 52
TABH+ 0(20) = A03C00E000000000000000003400000013010000
TABH+ 20(20) = 01000000A4000000FFFFFFFF0487000060290000
TABH+ 40( 8) = 10000000C1308000
store = 0xA03C00E0
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 52 (0x34000000)
label = 275 (0x13010000)
fill = 1 (0x01000000)
leng = 164 (0xA4000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000207
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xC8F611E0
pghook = 0x00000000
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
store_id = 125 (0x7D000000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_ORDERS
Table IT_293[1x320]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_ORDERS1
Table reference: 47
TABH+ 0(20) = 20B403E000000000000000002F00000025010000
TABH+ 20(20) = 0100000040010000FFFFFFFF0400000030380000
TABH+ 40( 8) = 01000000C1308000
store = 0x20B403E0
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 47 (0x2F000000)
label = 293 (0x25010000)
fill = 1 (0x01000000)
leng = 320 (0x40010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000286
occu = 1 (0x01000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x9080FFDF
pghook = 0x00000000
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 1 (0x01000000)
lineAlloc = 1 (0x01000000)
store_id = 130 (0x82000000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_ORDER_METHOD
Table IT_268[2x62]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_ORDER_METHOD
Table reference: 51
TABH+ 0(20) = 8882FFDF0000000000000000330000000C010000
TABH+ 20(20) = 020000003E000000FFFFFFFF04000000B0360000
TABH+ 40( 8) = 10000000C1248000
store = 0x8882FFDF
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 51 (0x33000000)
label = 268 (0x0C010000)
fill = 2 (0x02000000)
leng = 62 (0x3E000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000278
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x0868FFDF
pghook = 0x00000000
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
store_id = 122 (0x7A000000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_ORDKEYS
Table IT_271[1x332]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_ORDKEYS
Table reference: 29
TABH+ 0(20) = 80E303E000000000000000001D0000000F010000
TABH+ 20(20) = 010000004C010000FFFFFFFF04870000E0270000
TABH+ 40( 8) = 10000000C1308000
store = 0x80E303E0
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 29 (0x1D000000)
label = 271 (0x0F010000)
fill = 1 (0x01000000)
leng = 332 (0x4C010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000199
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0Hi,
the error DbpError -28814 denotes that an object cannot be found.
Can you maybe tell me your exact liveCache version (incl. Build level) and LCA Build?
Additionally, please copy the relevant error information from the file (/sapdb/data/wrk/<SID>/)knldiag.err into this thread.
Which exact 'liveCache test program' are your referring to (which of the /SAPAPO/... transactions)?
Kind regards,
Roland -
Reg SDCCN and USMM - Abap runtime error
Dear Friends,
Runtime Errors : DBIF_RSQL_SQL_ERROR
Exception : CX_SY_OPEN_SQL_DB
When I run a T.Code SDCCN and USMM, got abap run time error
"SQL error in the database when accessing a table" that errors are below.
Internal Call code is ..........[RSQL/OPEN/TBTCO]
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
"SAPLBTCH" or "LBTCHF19"
"EXECUTE_BP_JOB_SELECT"
The exception must either be prevented, caught within proedure
"EXECUTE_BP_JOB_SELECT" "(FORM)", or its possible occurrence must be declared
in the RAISING clause of the procedure.
This kind of errors found.
what can i do ? Pls give me advice
Regards
keshavhi,
please share the solution how you solve the Question.
Because of some times i got the same dump.
Regards,
Ananth -
ABAP Runtime error in FM BBP_VENDOR_GET_DATA2 in R/3
Hi Gurus
We are receiving nearly 1000 ABAP runtime error in the Functional Module BBP_VENDOR_GET_DATA2 in the user ID as RFCPROD in the ST22 and in the dump details as soon below.
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.
And this is happening in this place.
48| IF NOT LRT_ADDRNR[] IS INITIAL. |
|>>>>>| SELECT * APPENDING TABLE ITAB_ADRC FROM ADRC .
We enter the T-code XK01, XK02 and XK03 , then enter the details of vendor , press enter immediately one count is increasing in the ST22.
Please any one can suggest .
Thanks & Regards
SadaHi Sadasivam Soliyappan,
Could you please share the SAP Note number with us urgently?
We have been encountered with the same problem unfortunately.
Thanks in advance.
Dolunay. -
SQL error in the database when accessing a table.
Hi,
I got below error at production server. Please suggest how to reslove this error.
<br>
<br>
<br>
Runtime Errors DBIF_RSQL_SQL_ERROR
<br>
Exception CX_SY_OPEN_SQL_DB
<br>
Date and Time 02.01.2011 15:55:06
<br>
<br>
<br>
<br>
<br>
Short text
<br>
SQL error in the database when accessing a table.
<br>
<br>
<br>
How to correct the error
<br>
Database error text........: "[10054] TCP Provider: An existing connection was
<br>
forcibly closed by the remote host.
<br>
[10054] Communication link failure"
<br>
Internal call code.........: "[RSQL/INSR/SWFCNTBUF ]"
<br>
Please check the entries in the system log (Transaction SM21).
<br>
<br>
If the error occures in a non-modified SAP program, you may be able to
<br>
find an interim solution in an SAP Note.
<br>
If you have access to SAP Notes, carry out a search with the following
<br>
keywords:
<br>
<br>
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
<br>
"CL_SWF_CNT_FACTORY_SHMEM======CP" or "CL_SWF_CNT_FACTORY_SHMEM======CM001"
<br>
| "ADD_INSTANCE"
<br>
<br>
<br>
Information on where terminated
<br>
Termination occurred in the ABAP program "CL_SWF_CNT_FACTORY_SHMEM======CP" -
<br>
in "ADD_INSTANCE".
<br>
The main program was "SAPMSSY1 ".
<br>
<br>
In the source code you have the termination point in line 16
<br>
of the (Include) program "CL_SWF_CNT_FACTORY_SHMEM======CM001".
<br>
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
<br>
procedure "ADD_INSTANCE" "(METHOD)", but it was neither handled locally nor
<br>
declared
<br>
in the RAISING clause of its signature.
<br>
<br>
The procedure is in program "CL_SWF_CNT_FACTORY_SHMEM======CP "; its source
<br>
code begins in line
<br>
1 of the (Include program "CL_SWF_CNT_FACTORY_SHMEM======CM001 ".
<br>
<br>
<br>
<br>
Source Code Extract
<br>
<br>
Line
SourceCde
<br>
<br>
1
METHOD add_instance .
<br>
2
<br>
3
data: ls_id type swfcntbuf.
<br>
4
<br>
5
check buffer method - store in local buffer if necessary
<br>
6
retcode = cl_swf_cnt_factory=>add_instance( ibf_por = ibf_por instance = instance ).
<br>
7
<br>
8
CHECK m_buffer_method EQ mc_buffer_shared.
<br>
9
<br>
10
append key to list of tasks to add stored in database table SWFCNTBUF
<br>
11
will be evaluated by build process for shared memory area (UPDATE_BUFFER method)
<br>
12
<br>
13
ls_id-mandt = sy-mandt.
<br>
14
ls_id-id = ibf_por.
<br>
15
<br>
>>>>>
INSERT swfcntbuf CONNECTION r/3*wfcontainer
<br>
17
FROM ls_id.
<br>
18
<br>
19
IF sy-subrc EQ 0.
<br>
20
Commit seems to be necessary always, even if INSERT has failed, to get rid of
<br>
21
database locks
<br>
22
COMMIT CONNECTION r/3*wfcontainer.
<br>
23
ENDIF.
<br>
24
<br>
25
ENDMETHOD.
<br>duplicate here SQL error in the database when accessing a table.
Do not post the same question in more than on forum. -
SQL error while activating DSO and loading Mater Data
Hello Experts,
we are having process chains which include process activating DSO and loading to Master data,
while executing achai, we are getting error:
An error occurred during confirmation of process 000008. See long text
Message no. RSODSO_PROCESSING024
Diagnosis
Note the detailed system message:
An SQL error occurred when executing Native SQL.
when i go to T-Code: ST22
the diagnosis is below:
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Date and Time 20.05.2010 22:18:02
What happened?
The database system detected a deadlock and avoided it by rolling back
your transaction.
What can you do?
If possible (and necessary), repeat the last database transaction in the
hope that locking the object will not result in another deadlock.
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.
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.
Could you please help me out how can i deal with this issue, .
Regards
Sinu Reddyit seems that the target you're loading to is already locked by another load...if it concerns a master data is also possible that the master data is locked by a change run. check your scheduling and make sure you don't load the same target at the same moment...
M. -
SQL error "-601" occurred when accessing table "SMEN_BUFFC
Hi Guys
I am getting the above error at tiem when i am logging on.
The actual error message in the st22 dump is
Database error text........: "SMEN_BUFH5 in R3EPT32000 type *SQLPKG already
exists. Job=018343/EPT01/WP00"
The termination occurred in the ABAP/4 program "SAPLSMTR_NAVIGATION_MODULES "
in
"SMTR_STRU_PROCESS_STRUCTURE".
The main program was "SAPLSMTR_NAVIGATION ".
This seems to happen when some users log on to the system and then tries to change their password. If I stop sap and start it again, the rror goes away.
I have actually deleted the sql package with the command
DLTSQLPKG R3EPT32000\SMEN_BUFH5.
This seem to work but after a while the erro comes back againDear Christian,
at the moment in our Productive system we have hundreds of Dumps: nearly at every log on user get a DUMP with the well known message.
Analyzing develoepr trace we find following information:
C Wed Mar 14 09:54:35 2007
C Concurrent prepare happened for SIPID
C Library name: R3S1132000
C Package name: SMEN_BUFH5
C Statement name: "QL1YQAAAAAFC"
C SQL Error: -601
C *** ERROR => Error -601 in function prep_cached_op [dbsldb4.cpp 7057]
C Library name: R3S1132000
C Package name: SMEN_BUFH5
C Statement name: "QL1YQAAAAAFC"
C Failing statement is:
C , SELECT * FROM R3S11DATA/"SMEN_BUFFC" WHERE "MANDT" = ? AND "UNAME" = ? WITH UR
B ***LOG BY4=> sql error -601 performing PRE on table SMEN_BUFFC [dbtran 7009 ]
B ***LOG BY0=> SMEN_BUFH5 in R3S1132000 tipo *SQLPKG esiste gi{. Job=251690/S1100/WP12 [dbtran 7009 ]
B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'PRE'
B FHDR: {tab='SMEN_BUFFC ',
fcode=53, mode=2, bpb=0, dbcnt=0, crsr=1,
B hold=0, keep=1, xfer=2, pkg=0, upto=0, init:b=0,
B init:p=0000000000000000, init:#=278, wa:p=0000000000000000, wa:#=278}
B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'PRE'
B STMT:
B CRSR: {tab='SMEN_BUFFC ', id=-1, hold=0, prop=0x10000, max.in@0=1, fae:blk=10,
B con:nm='R/3', con:id=0, con:vndr=2, val=2,
B key:1=0, key:#=6, xfer=2, xin:#=0, xout:#=0, upto=0,
B wa:p=000000800440C380, init:p=00000090D4CF4DF8, init:#=15, init:b=0}
Additionaly we also tried to delete only mentioned SQL package (while system was running), but without succes.
What do you think?
Giuseppe -
Hi
I generated a report and I found that it is syntactically correct
also execution is successful but when I executed the same
program after 10 minutes a blank screen appears stating that
[Abap Runtime Error Error Code -
SQL error in the database when accessing table.]
I dont understand where is the problem and what I should do in the next step inorder to eliminate this.Any solution plz
answer...Hi,
Guess the fields in the internal table order and while fetching data through select may not be in same order just check once.
and
guess the size of the records in the table may be exceeds the limit(huge amount of data).
Manjula its just a guess.
Check once.
also check the length of each field .
Thanks
Naveed -
Runtime error SQL error 3114 occurred when accessing program CX_ w
Hi Friends,
Iam in a big mess . I have one query based on one my Zinfocube.This query ia attached in the workbook .. Previuolsy all was fine , but now whever iam executing this query it is throwing me the exception
Query 0: Runtime error SQL error 3114 occurred when accessing program CX_ with parallel processing via RFC.
and
Beim Lesen der Daten sind Fehler aufgetreten. Navigation ist möglich
I am not able to get the cause of error ..
Can anybody help me in this regrd as its a bit urgent.
Thanks in advance..Hi , thanks for replying ,
I have tried running query through RSRT also , its not working still it is giving me the same error .
In st22 it is showing me the follwing dump.
DBIF_REPO_SQL_ERROR
Short text
SQL error 3114 occurred when accessing program
What happened?
The system is no longer linked to an ORACLE instance.
No further operations can be performed on the database.
What can you do?
You cannot eliminate this error yourself.
Please inform your database administrator.
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.
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.
Error analysis
The system attempted to access an ORACLE instance to which
it is no longer linked.
This situation may arise because the ORACLE instance
has been stopped due to an error or an external operation.
How to correct the error
Database error text........: "ORA-03114: not connected to ORACLE"
Triggering SQL statement...: "CX_SQL_EXCEPTION==============CP "
The current status of the ORACLE instance cannot be determined.
It may be still inactive or the database administrator may have
restarted it.
In any case, all systems that have accessed the ORACLE instance
must be restarted after the ORACLE instance has been restarted.
If you were working on a central system, inform
your system administrator.
If you were working on an external local system, inform
the person responsible for this system.
If you were working on your own local system, restart
the system yourself.
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_REPO_SQL_ERROR" " "
"CL_SQL_RESULT_SET=============CP" or "CL_SQL_RESULT_SET=============CM006"
"NEXT_PACKAGE"
If you cannot solve the problem yourself and want to send an errornotification 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.
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_REPO_SQL_ERROR" " "
"CL_SQL_RESULT_SET=============CP" or "CL_SQL_RESULT_SET=============CM006"
"NEXT_PACKAGE"
Thanks in Advance.. -
Reg : Daily i got 120 ABAP Runtime Error with in 40 Mins(Early Morning)
Dear Friends,
I got following errors regularly. when i run t.code RSBTCDEL and RSSNAPDL. what can i do? then Regularly morning i got same morethan 120 Error. User is SAPSYS 000 Client. How can avoid this type of ABAP Runtime Error.
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Date and Time 10.06.2009 15:04:23
Short text
SQL error in the database when accessing a table.
What can you do?
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.
How to correct the error
Database error text........: "[601] Could not continue scan with NOLOCK due to
data movement."
Internal call code.........: "[RSQL/FTCH/TBTCO ]"
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"
"SAPLBTCH" or "LBTCHF19"
"EXECUTE_BP_JOB_SELECT"
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 u2192 List u2192 Save u2192 Local File u2192 (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
"EXECUTE_BP_JOB_SELECT" "(FORM)", or its possible occurrence must be declared
in the RAISING clause of the procedure. To prevent the exception, note the following:
Client.............. 400
User................ "BASIS"
Language key........ "E"
Transaction......... "SE38 "
Transactions ID..... "D7A155DEA42EF1EEB52A000423BF7C3A"
Program............. "SAPLBTCH" ( Run a Sap Standard Report RSBTCDEL)
Screen.............. "SAPMSSY0 1000"
Regards
keshavHi Juan,
My System is
ECC 6.0
Database : MS SQL Server 2005
OS - Windows 2003 server
SAP Patches level is Basis - SAPKB70016
ABAP - SAPKA70016
Kernel patch level - 185
when i has update the kernel patches after only i got this error morethan 120 like early morning 4.40 AM to 5.18 AM regularly. what can i do?
Regards
keshav -
UNCAUGHT_EXCEPTION is the ABAP Runtime error
Hi all,
Our Production System BI7.0 with oracle 10g running on Unix . The UNCAUGHT_EXCEPTION is the ABAP Runtime error exists in ST22.
Please find the Error analysis from ABAP Dump of UNCAUGHT_EXCEPTION.
Error analysis
An exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_SDB_ORA_PROGRAM_ERROR', was not
caught and
therefore caused a runtime error.
The reason for the exception is:
An error occurred in the program:
The occurrence of the exception is closely related to the occurrence of
a previous exception "CX_SQL_EXCEPTION", which was raised in the program
"CL_SQL_STATEMENT==============CP",
specifically in line 31 of the (include) program
"CL_SQL_STATEMENT==============CM002".
The cause of the exception was:
ORA-04031: unable to allocate 62208 bytes of shared memory ("shared
pool","DBMS_STATS","PL/SQL MPCODE","BAMIMA: Bam Buffer")#ORA-06508: PL/SQL:
could not find program unit being called: "SYS.DBMS_STATS"#ORA-06512: at line 1
Thanx,
PeterHi Peter,
You shared pool might be too small
Read,
SAP Note 869006 - Composite SAP note: ORA-04031
Regards
Juan
Maybe you are looking for
-
Difference between AP PO Reconciliation Report and GL
I have followed the following - R12 Accrual Balance Mismatch Between Accrual Reconciliation Report and GL - Troubleshooting (Doc ID 1107953.1) My SLA and GL Balances match as per the doc. However I have a difference of around 3 million in the AP PO R
-
Time machine backup not usable
Hello, My hard drive died on me a few months back so I bought a new one and have been trying to use my time machine backup (on an external drive) and my computer won't recognize it and won't read it. I upgraded from Snow Leopard to Lion when it came
-
Photosmart 6515 prints in any color but black
I replaced all the ink cartridges and I don't get any black ink. I have tried removing and reinstalling the black cartridge, installing another black replacement and running the clean heads process. Is it likely that the problem will be solved by rep
-
Calculate Date and Provide Static Date
I have Office 365 SharePoint 2013 and my site contains two lists: 1. Annual List (containing all repetitive tasks done yearly). 2. Task List (containing current and past actions). Each year I copy the annual list to the bottom of the Task List, fix
-
Hi, I have used the Stored Command procedure in CS3 but recieve an error message about the invalid charcter @, it seems that this was a bug - is there a fix for this?