DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
I got dump in production system,can you please advice how to sort it out.
Database error text........: "[207] Invalid column name 'PAGENO'.#[8180]
Statement(s) could not be prepared."
Internal call code.........: "[RSQL/INSR/REGUP ]"
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"
"SAPF110S" or "F110SFR0_REGUH_AUSGEBEN"
"REGUH_AUSGEBEN"
Hi,
We get similar dumps with name as DBIF_RSQL_SQL_ERROR
As per my investigation in the past, this seemed to be some error in the database extracting data
This has occured for me only for the Z reports
Please let me know if this is a Z report or SAP report
Similar Messages
-
hi friends...
i am posting fico document using bapi BAPI_ACC_GL_POSTING_POST.
after that i am updating the document number to my custom table.
but in some cases while updating the document in my custom table i am getting the fallowing dump..
in ST22
How to correct the error:
Database error text........: "[1205] Transaction (Process ID 66) was deadlocked
on lock resources with another process and has been chosen as the deadlock
victim. Rerun the transaction."
Internal call code.........: "[RSQL/UPDT/ZIF004_PKT ]"
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"
"ZFI_01_MONTHLY_RESULT_FRM_PKT" or "ZFI_01_MONTHLY_RESULT_FRM_PKT"
"UPLOAD_SAP"
Source Code Extract
LOOP AT i_zif004_pkt_sum .
UPDATE zif004_pkt SET xblnr = i_zif004_pkt_sum-xblnr ---> i am getting DUMP here
gjahr = i_zif004_pkt_sum-gjahr
sap_flag_posting = i_zif004_pkt_sum-sap_flag_posting
WHERE compcode = i_zif004_pkt_sum-compcode
AND ccode = i_zif004_pkt_sum-ccode
AND wbselement = i_zif004_pkt_sum-wbselement
AND kostl = i_zif004_pkt_sum-kostl
AND code = i_zif004_pkt_sum-code
AND month1 = l_ltx
AND year1 = p_year.
IF sy-subrc = 0.
WRITE :/ 'Document ', i_zif004_pkt_sum-xblnr, 'is posted for ', i_zif004_pkt_sum-code.
ENDIF.
ENDLOOP.
kindly give some inputs..
regards
SelvaHi,
You will face this issue if your oracle data base is lack of work processes. try to check the work processes and increase them if possible with the helps basis guys.
check the below thread.
DI job failed ORA-12537: TNS:connection closed.
Regards,
Venkatesh -
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB" error
Hello All,
I went through a lot of threads and was not able to find this.
We have BI 7.0 environment but our all objects are in 3.5 flow. We have only done technical upgrade. I get this error while activating the data in ODS. This is COPA actual line items ODS which has 42 Mil records and record size is big too. While doing the data load from ECC 5.0 this activation failed. After that we have increased space in PSAPTEMP table 16 fold. We tried to activate the ODS by buffering also. Everytime it fails within 1500 seconds. We have all the data properly in BW except the activation fails. I have tried this several times and same following error.
Following is the error. Please suggest the solution and marks will be assigned generously.
Database error text........: "ORA-12801: error signaled in parallel query
server P000#ORA-01652: unable to extend temp segment by 128 in tablespace
PSAPTEMP"
Internal call code.........: "[RSQL/FTCH//BIC/AZBTR_O1040 ]"
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_RSODSO_ACTIVATE_REQUESTS===CP" or "CL_RSODSO_ACTIVATE_REQUESTS===CM00D"
"ACTIVATE_DATA_FROM_QUEUE"
Thanks,Hi,
I can understand the problem as i use to face this problem when i loaded some huge data in my BW.
This is basically a Data base related error where actually you can't help.
What you can do is that please increase the number of process assigned for your system and make sure that no other loads are going on at the time of the loading.
I loaded the data at the time when no other loading or any process were running in the system.
Hope this helps you.
Regards,
Soumyadeep. -
Reg DBIF_RSQL_SQL_ERROR - CX_SY_OPEN_SQL_DB
We are getting lot of below run time error while querying on TVARVC table in production system.
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Database error text........: "SQL0911N The current transaction has been rolled
back because of a deadlock or timeout. Reason code "68". SQLSTATE=40001"
code where the error is generating
Select Query:
SELECT SINGLE low FROM tvarvc
INTO variable
WHERE name = xx AND
type = yy AND
numb = zz
or
SELECT SINGLE low FROM tvarvc
CLIEN SPECIFIED
INTO variable
WHERE
mandt = sy-mandt
name = xx AND
type = yy AND
numb = zz
I have looked into SCN but couldnt find any info specific to my scenario.
Kindly provide your inputs.IBM help says Reason code 68 is for lock timeout - was the program "hanging" for some time, could it be someone (or something) is locking the Variant?
If you have authorization, you can see deadlocks and lock waits in ST04 -
Hi All,
I am loading a COPA cube from a DSO.
There are about 15million records to be loaded. every time i try loading the data, 1 or 2 Data packages gets stuck and finally it leads to a runtime error DBIF_RSQL_SQL_ERROR with exception CX_SY_OPEN_SQL_DB.
When i checked in SM21 transaction code, i got the following message
10:41:52 BTC 018 500 AMRUKV BY O Deadlock occurred
10:41:53 BTC 018 500 AMRUKV BY 4 Database error 60 at INS access to table /BIC/FCSDV
10:41:53 BTC 018 500 AMRUKV BY 0 > ORA-00060: deadlock detected while waiting for resource
10:41:54 BTC 018 500 AMRUKV AB 0 Run-time error "DBIF_RSQL_SQL_ERROR" occurred
10:41:58 BTC 018 500 AMRUKV AB 1 > Short dump "080818 104154 s0173bel PB100 " generated
10:41:58 BTC 018 500 AMRUKV D0 1 Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20080818104154s0173bel_PB1_00 AMRUKV 500 )
In transaction code ST22 i got the following message:
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Date and Time 18.08.2008 10:41:54
Short text
SQL error in the database when accessing a table.
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.
Error analysis
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 "WRITE_ICFACT" "(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 database system recognized that your last operation on the database
would have led to a deadlock.
Therefore, your transaction was rolled back
to avoid this.
ORACLE always terminates any transaction that would result in deadlock.
The other transactions involved in this potential deadlock
are not affected by the termination.
How to correct the error
Database error text........: "ORA-00060: deadlock detected while waiting for
resource"
Internal call code.........: "[RSQL/INSR//BIC/FCSDVD_C02 ]"
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"
"GPD3UMZD6V4YAKZAIWAOCYLV07Y" or "GPD3UMZD6V4YAKZAIWAOCYLV07Y"
"WRITE_ICFACT"
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
"WRITE_ICFACT" "(FORM)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
Can anybody suggest on what can be done?
Thanks in Advance,
Regards
A.THi ,
This is a table space issue....
u will be getting a Dump...as DBIF_RSQL_SQL_ERROR check in ST22. in this DUMP if u scroll down u will find the table for which this is failing. Actually this is like some of the table related to the DSO is not having sufficient space to cary out the transaction. hence it is failing.
U can also see in DB02--> Deadlock....u will see that there is a deadlock for this table. So find the table from ST22 and ask ur basis team to increase the space for this table....
This can be solved only by increasing the space of the table...no other solution....ask help from ur basis team.
Thanks
Sandeep -
CX_SY_OPEN_SQL_DB Need Help !
Hi I'm Getting this Dump
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Date and Time 01/25/2008 05:30:05
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........: "POS(4477) Too complicated SQL statement (too much
data)"
Internal call code.........: "[RSQL/OPEN/ZBBP_CONF_VIEW ]"
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"
"SAPLZ3P_CLC_FG01" or "LZ3P_CLC_FG01U01"
"Z3P_CLC_CONFIRMATION_DETAILS"
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
"Z3P_CLC_CONFIRMATION_DETAILS" "(FUNCTION)", or its possible occurrence must be
declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "pwdf1918"
Network address...... "10.17.99.25"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "pwdf4324"
Database type..... "ADABAS D"
Database name..... "IBP"
Database user ID.. "SAPR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Oct 1 2007 00:34:30"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQLDBC 7.6.1.015 CL 147649 "
Patch level. 130
Patch text.. " "
Database............. "MaxDB 7.6, MaxDB 7.7"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 4189840
Heap.... 0
Page.... 0
MM Used. 1496416
MM Free. 2690800
User and Transaction
Client.............. 001
User................ "EBP_ISP"
Language Key........ "E"
Transaction......... " "
Transactions ID..... "FCF9CADCE4F4F16DB8ED0017A44BD489"
Program............. "SAPLZ3P_CLC_FG01"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "ISP"
Database Release.... 700
Kernel Release...... 700
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchron and non-transactional (emode 0, imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........." "
Outbound Queue Name.." "
Client.............. 001
User................ "I802084"
Transaction......... "SE38"
Call Program........."Z3P_CLC_MAIN01"
Function Module..... "Z3P_CLC_CONFIRMATION_DETAILS"
Call Destination.... "EBP_IBPCLNT001"
Source Server....... "pwdf4106_ISP_33"
Source IP Address... "10.21.24.140"
Additional information on RFC logon:
Trusted Relationship " "
Logon Return Code... 0
Trusted Return Code. 0
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
Information on where terminated
Termination occurred in the ABAP program "SAPLZ3P_CLC_FG01" - in
"Z3P_CLC_CONFIRMATION_DETAILS".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 410
of the (Include) program "LZ3P_CLC_FG01U01".
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "Z3P_CLC_CONFIRMATION_DETAILS" "(FUNCTION)", but it was neither
handled locally nor declared
in the RAISING clause of its signature.
The procedure is in program "SAPLZ3P_CLC_FG01 "; its source code begins in line
307 of the (Include program "LZ3P_CLC_FG01U01 ".
Source Code Extract
Line
SourceCde
380
END OF TAB1 .
381
DATA DAT1 TYPE STANDARD TABLE OF ZBBP_WF_STRUC WITH HEADER LINE .
382
DATA OUT_DATES2 TYPE STANDARD TABLE OF Z3P_STR03 WITH HEADER LINE .
383
384
DATA : TAB2 LIKE TAB1 OCCURS 10 WITH HEADER LINE.
385
DATA : TAB3 LIKE TAB1 OCCURS 10 WITH HEADER LINE.
386
387
RANGES : REF_DOC FOR BBPD_PD_INDEX_H-REF_DOC_NO.
388
389
CHECK NOT IN_TAB IS INITIAL.
390
*Appending the range
391
LOOP AT IN_TAB INTO WA_IN.
392
*out_dates-dedat = '19791003'.
393
*Append out_dates.
394
395
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
396
EXPORTING
397
INPUT = WA_IN-CONFIRMATION
398
IMPORTING
399
OUTPUT = WA_IN-CONFIRMATION
400
401
402
REF_DOC-SIGN = 'I'.
403
REF_DOC-LOW(10) = WA_IN-CONFIRMATION.
404
REF_DOC-OPTION = 'EQ'.
405
APPEND REF_DOC.
406
ENDLOOP.
407
408
*Select Query
409
>>>>>
SELECT REF_DOC_NO itm_vper_start Z_VPER_START Z_VPER_END itm_product_type zexpensetype zinvo
411
OBJECT_TYPE
412
OBJECT_ID
413
V~GUID
414
FROM zbbp_conf_view AS v "
415
LEFT OUTER JOIN bbp_pdisc AS b
416
ON vclient = bclient
417
AND vitm_guid = bguid
418
INTO CORRESPONDING FIELDS OF TABLE TAB1
419
WHERE
420
object_type = 'BUS2203'
421
AND
422
itm_itm_type ne 'HIER'
423
and
424
ref_doc_no IN REF_DOC.
425
426
*LOOP AT REF_DOC.
427
*SELECT REF_DOC_NO itm_vper_start Z_VPER_START Z_VPER_END itm_product_type zexpensetype zinv
428
*OBJECT_TYPE
429
*OBJECT_ID
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
1
SY-TABIX
0
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
CPIC and RFC Control
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080125
SY-UZEIT
053005
SY-XPROG
SAPLZ3P_CLC_FG01
SY-XFORM
Z3P_CLC_CONFIRMATION_DETAILS
Active Calls/Events
No. Ty. Program Include Line
Name
4 FUNCTION SAPLZ3P_CLC_FG01 LZ3P_CLC_FG01U01 410
Z3P_CLC_CONFIRMATION_DETAILS
3 FORM SAPLZ3P_CLC_FG01 LZ3P_CLC_FG01U01 307
Z3P_CLC_CONFIRMATION_DETAILS
2 FORM SAPMSSY1 SAPMSSY1 85
REMOTE_FUNCTION_CALL
1 MODULE (PBO) SAPMSSY1 SAPMSSY1 30
%_RFC_START
Chosen variables
Name
Val.
No. 4 Ty. FUNCTION
Name Z3P_CLC_CONFIRMATION_DETAILS
IN_TAB[]
Table IT_0[1019x146]
\FUNCTION-POOL=Z3P_CLC_FG01\FORM=Z3P_CLC_CONFIRMATION_DETAILS\DATA=%_%_IN_TAB
Table reference: 0
TABH+ 0(20) = 70292557FE07000070252557FE07000000000000
TABH+ 20(20) = 0000000000000000FB03000092000000FFFFFFFF
TABH+ 40(16) = 04010000E003000010000000C1248101
store = 0x70292557FE070000
ext1 = 0x70252557FE070000
shmId = 0 (0x00000000)
id = 0 (0x00000000)
label = 0 (0x00000000)
fill = 1019 (0xFB030000)
leng = 146 (0x92000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000006
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 1
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xC0493757FE070000
pgHook = 0xB08C3957FE070000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 4 (0x04000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 2032 (0xF0070000)
lineAlloc = 1072 (0x30040000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = 0x0000000000000000
collHook = 0x0000000000000000
ext2 = 0x00252557FE070000
>>>>> 2nd level extension part <<<<<
tabhBack = 0xA0242557FE070000
delta_head = 0100000001000000CE0000000100000004010000100400009200000001000000000000000500000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
OUT_DATES[]
Table IT_1[0x54]
\FUNCTION-POOL=Z3P_CLC_FG01\FORM=Z3P_CLC_CONFIRMATION_DETAILS\DATA=%_%_OUT_DATES
Table reference: 1
TABH+ 0(20) = 000000000000000000533757FE07000000000000
TABH+ 20(20) = 01000000010000000000000036000000FFFFFFFF
TABH+ 40(16) = 04010000A004000010000000C1248101
store = 0x0000000000000000
ext1 = 0x00533757FE070000
shmId = 0 (0x00000000)
id = 1 (0x01000000)
label = 1 (0x01000000)
fill = 0 (0x00000000)
leng = 54 (0x36000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000010
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 1
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
shmTabhSet = Not allocated
id = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
shmVersId = Not allocated
shmRefCount = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = 0x0000000000000000
collHook = 0x0000000000000000
ext2 = 0x00673857FE070000
>>>>> 2nd level extension part <<<<<
tabhBack = 0x10D43757FE070000
delta_head = 0100000002000000CD0000000200000004010000D00400003600000001000000000000000500000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
OUT_DETAILS[]
Table IT_2[0x244]
\FUNCTION-POOL=Z3P_CLC_FG01\FORM=Z3P_CLC_CONFIRMATION_DETAILS\DATA=%_%_OUT_DETAILS
Table reference: 2
TABH+ 0(20) = 000000000000000070673857FE07000000000000
TABH+ 20(20) = 020000000200000000000000F4000000FFFFFFFF
TABH+ 40(16) = 040100004004000010000000C1248101
store = 0x0000000000000000
ext1 = 0x70673857FE070000
shmId = 0 (0x00000000)
id = 2 (0x02000000)
label = 2 (0x02000000)
fill = 0 (0x00000000)
leng = 244 (0xF4000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000008
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 1
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
shmTabhSet = Not allocated
id = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
shmVersId = Not allocated
shmRefCount = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = 0x0000000000000000
collHook = 0x0000000000000000
ext2 = 0xE0B23957FE070000
>>>>> 2nd level extension part <<<<<
tabhBack = 0x80B23957FE070000
delta_head = 0100000003000000CC000000030000000401000070040000F400000001000000000000000500000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
%_DUMMY$$
2222
0000
0000
0000
SYST-REPID
SAPLZ3P_CLC_FG01
5454535544454433222222222222222222222222
310CA30F3C3F6701000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY-XPROG
SAPLZ3P_CLC_FG01
5454535544454433222222222222222222222222
310CA30F3C3F6701000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY-TABIX
0
0000
0000
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY
##############################################################################T######### ####
000000F000000000000000000000000000000090000000000000000000000000000000000000105000000010220000
100000B000000000000000001000100000000020000000000000000000000000000000000000604000000000000500
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
00000030000000000000000000000000000000000000000000000000000000000000000000000000000000E000000C
<%_TABLE_BBP_PDHGP>
%_SPACE
2
0
0
0
SY-MANDT
001
333
001
000
000
<%_TABLE_BBP_PDISC>
REF_DOC[]
Table IT_3[1019x70]
\FUNCTION=Z3P_CLC_CONFIRMATION_DETAILS\DATA=REF_DOC[]
Table reference: 3
TABH+ 0(20) = 50FE3957FE070000000000000000000000000000
TABH+ 20(20) = 0300000003000000FB03000046000000FFFFFFFF
TABH+ 40(16) = 04010000100D00000A000000C1048001
store = 0x50FE3957FE070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 3 (0x03000000)
label = 3 (0x03000000)
fill = 1019 (0xFB030000)
leng = 70 (0x46000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000055
occu = 10 (0x0A000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x70FB3957FE070000
pgHook = 0x30FB3A57FE070000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 5 (0x05000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 1950 (0x9E070000)
lineAlloc = 1054 (0x1E040000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
TAB1[]
Table IT_4[0x256]
\FUNCTION=Z3P_CLC_CONFIRMATION_DETAILS\DATA=TAB1[]
Table reference: 4
TABH+ 0(20) = 0000000000000000000000000000000000000000
TABH+ 20(20) = 04000000040000000000000000010000FFFFFFFF
TABH+ 40(16) = 04010000700A000010000000C1248001
store = 0x0000000000000000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 4 (0x04000000)
label = 4 (0x04000000)
fill = 0 (0x00000000)
leng = 256 (0x00010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000041
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
shmTabhSet = Not allocated
id = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
shmVersId = Not allocated
shmRefCount = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
TAB1
000000000000000000000000 00
2222222222222222222222222233333333333333333333333322222222222222222222222222222222222222222233
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
DAT1-GUID
2222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
TAB1-GUID
0000000000000000
0000000000000000
No. 3 Ty. FORM
Name Z3P_CLC_CONFIRMATION_DETAILS
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_%_IN_TAB
Table IT_0[1019x146]
%_%_OUT_DATES
Table IT_1[0x54]
%_VIASELSCR
0
4
%_%_OUT_DETAILS
Table IT_2[0x244]
No. 2 Ty. FORM
Name REMOTE_FUNCTION_CALL
HEADER
000000000000
000000000000
TYPE
3
0000
3000
SY-XPROG
SAPLZ3P_CLC_FG01
5454535544454433222222222222222222222222
310CA30F3C3F6701000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
RC
0
0000
0000
SY-XFORM
Z3P_CLC_CONFIRMATION_DETAILS
535544454444454454445445444522
A30F3C3F3FE692D149FEF45419C300
000000000000000000000000000000
000000000000000000000000000000
%_SPACE
2
0
0
0
No. 1 Ty. MODULE (PBO)
Name %_RFC_START
%_PRINT
000 0###
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
RFCTYPE_INTERNAL
3
0000
3000
Internal notes
The termination was triggered in function "HandleRsqlErrors"
of the SAP kernel, in line 764 of the module
"//bas/700_REL/src/krn/runt/absapsql.c#8".
The internal operation just processed is "SQLS".
Internal mode was started at 20080125053005.
Internal call code.........: "[RSQL/OPEN/ZBBP_CONF_VIEW ]"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App : disp+work.EXE (pid=1568)
When : 1/25/2008 5:30:5.129
Threads : 2
Computer Name : PWDF1918
User Name : ibpadm
Number of Processors: 4
Processor Type: AMD64 Family 15 Model 33 Stepping 2
Windows Version : 5.2 Current Build: 3790
State Dump for Thread Id 2238
FramePtr ReturnAd Param#1 Function Name
0000000007ccb730 0000000077d7047f 0000000056355570 ntdll!NtWaitForSingleObject
0000000007ccb7d0 0000000001722861 00000000000002a0 kernel32!WaitForSingleObjectEx
0000000007ccba20 0000000000610ec5 0000000000000001 disp+work!NTDebugProcess [ntstcdbg.c (501)]
0000000007ccba50 0000000000afbbec 0000000000000001 disp+work!CTrcStack [dptstack.c (182)]
0000000007ccbaa0 0000000000b00e10 0000000000000001 disp+work!rabax_CStackSave [abrabax.c (7091)]
0000000007ccc480 0000000000a1153c 0000000001c934c0 disp+work!ab_rabax [abrabax.c (1231)]
0000000007ccc520 00000000009e2656 0000000000000000 disp+work!ab_rsqlerr [abdberr.c (787)]
0000000007ccc630 00000000009e4761 0000000000000003 disp+work!HandleRsqlErrors [absapsql.c (765)]
0000000007ccc820 00000000009f5543 000000000000003b disp+work!SqlsExecuteCall [absapsql.c (7466)]
0000000007ccc8d0 00000000008339b2 0000000000000001 disp+work!ab_jsqls [absapsql.c (1414)]
0000000007ccca50 0000000000a0e8b7 0000000000000008 disp+work!ab_extri [abextri.c (554)]
0000000007cccaa0 0000000000acb06c 0000000000000008 disp+work!ab_xevent [abrunt1.c (281)]
0000000007cccb30 000000000066f0a8 0000000000000008 disp+work!ab_dstep [abdynpro.c (492)]
0000000007ccccb0 0000000000672c7d 000007fe5730c890 disp+work!dynpmcal [dymainstp.c (2403)]
0000000007cccd40 000000000067267a 000007fe572514a0 disp+work!dynppbo0 [dymainstp.c (543)]
0000000007cccdf0 0000000000631ed5 0000000000000000 disp+work!dynprctl [dymainstp.c (360)]
0000000007ccfc30 00000000004d71d3 0000000000000003 disp+work!dynpen00 [dymain.c (1629)]
0000000007ccfeb0 000000000042d5a6 0000000007d58600 disp+work!TskhLoop [thxxhead.c (4467)]
0000000007ccfee0 000000000040108d ffffffff00000003 disp+work!DpMain [dpxxdisp.c (1121)]
0000000007ccff10 00000000019c7781 0000000000000000 disp+work!nlsui_main [thxxanf.c (84)]
0000000007ccff70 0000000077d5966c 0000000000000000 disp+work!wmainCRTStartup [crtexe.c (498)]
0000000007ccffa0 0000000000000000 00000000019c7610 kernel32!BaseProcessStart
State Dump for Thread Id 374c
FramePtr ReturnAd Param#1 Function Name
000000000de0fe40 0000000077d5f651 0000000000000000 ntdll!NtFsControlFile
000000000de0feb0 00000000018ad9af fffffffffffffffe kernel32!ConnectNamedPipe
000000000de0ff40 000007ff7fc411c4 0000000000000000 disp+work!SigIMsgFunc [signt.c (679)]
000000000de0ff70 0000000077d6b69a 0000000077d6b660 msvcrt!endthreadex
000000000de0ffa0 0000000000000000 0000000000000000 kernel32!BaseThreadStart
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
SAPMSSY1
0
05/27/2005
16:45:10
22528
E
1
Prg
SAPLZ3P_CLC_FG01
1
01/25/2008
02:47:42
33792
E
2
Typ
Z3P_STR01
0
11/03/2007
07:50:03
3072
3
Typ
Z3P_STR03
0
11/03/2007
07:50:03
2048
4
Typ
Z3P_STR02
0
01/25/2008
02:47:42
4096
5
Prg
SAPLALFA
5
02/08/2005
13:13:24
8192
E
6
Typ
ZBBP_CONF_VIEW
0
09/07/2007
05:21:21
10240
7
Typ
BBP_PDISC
0
12/06/2007
04:04:51
12288
8
Prg
CX_SY_OPEN_SQL_DB=============CP
8
07/01/2005
18:22:20
12288
E
9
Typ
SCX_SRCPOS
0
02/08/2005
13:13:15
2048
10
Prg
CX_SY_OPEN_SQL_ERROR==========CP
10
07/01/2005
18:22:20
10240
E
11
Prg
CX_SY_SQL_ERROR===============CP
11
07/01/2005
18:22:20
10240
E
12
Prg
CX_DYNAMIC_CHECK==============CP
12
07/01/2005
18:22:20
10240
E
13
Prg
CX_ROOT=======================CP
13
11/03/2007
02:55:47
11264
E
14
Prg
CX_NO_CHECK===================CP
14
07/01/2005
18:22:20
10240
E
15
Prg
CX_SY_NO_HANDLER==============CP
15
07/01/2005
18:22:20
10240
E
16
Typ
SYST
0
01/23/2005
00:05:42
31744
17
Typ
ZBBP_WF_STRUC
0
09/07/2007
05:21:20
2048
Directory of Application Tables
Name Date Time Lngth
Val.
Program SAPMSSY1
SYST / / : : 00004612
\0\0\0\0\0\0#\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0\0
ABAP Control Blocks (CONT)What is your database/livecache version?
Check note 1001257 - SQL error -1105 Too complicated SQL statement
Markus -
dear all,
i have done a system copy from production server into quality server. quality was scrapped and freshly installed with SAP then used the DB flush method to carry out the system copy. i had to change the DBS_ORA_SCHEMA in environment variables to SAP<SOURCE SID> from SAPSR3. the sap version is ECC6.0,DB is ORACLE10.2 on WIN NT.
after MMC opened, i get "SQL error in the database when accessing a table" error is coming. in SM21, I am getting "Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20081018130339sibqty_QTY_00 SAPSYS 000 )
Database error 8103 at SEL access to table TBTCO
Run-time error "DBIF_RSQL_SQL_ERROR" occurred
Database error 8103 at FET access to table TBTCP
Run-time error "DBIF_RSQL_SQL_ERROR" occurred
> Short dump "081018 130339 sibqty_Q TY_00 " generated
Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20081018130339sibqty_QTY_00 SAPSYS 000
> Short dump "081018 130339 sibqty_Q TY_00 " generated
Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20081018130339sibqty_QTY_00 SAPSYS 000
Delete session 001 after error 023
Database error 8103 at DEL access to table TMSALOGAR
Run-time error "DBIF_RSQL_SQL_ERROR" occurred
> Short dump "081018 130432 sibqty_Q TY_00 " generated
Database error 8103 at FET access to table SNAP
Run-time error "DBIF_RSQL_SQL_ERROR" occurred
> Short dump "081018 130432 sibqty_Q TY_00 " generated
Transaction Canceled SY 002 ( SQL error in the database when accessing a table. )
Database error 8103 at FET access to table TSP02"
please find the st22 DUMP:
ow to correct the error |
Database error text........: "ORA-08103: object no longer exists"
Internal call code.........: "[RSQL/READ/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"
"SAPMSSY2" or "SAPMSSY2"
"INITIATE_JOB_START"
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
"INITIATE_JOB_START" "(FORM)", or its possible occurrence must be declared in
the
RAISING clause of the procedure.
|
please do me this favor if you know to avoid this problem..
thanks a lot..Hello Anuj,
This is because the COUNT(*) is returning a value which is longer than the INT4 data type it is expecting. If you restrict the selection by introducing a WHERE clause, then you won't get the dump:
DATA: dyn_from TYPE string,
dyn_where TYPE string,
gx_sql_err TYPE REF TO cx_sy_open_sql_error,
gv_text TYPE string.
dyn_from = `DD01L INNER JOIN DD02L ON DD02L~AS4LOCAL = DD01L~AS4LOCAL AND DD02L~AS4VERS = DD01L~AS4VERS`.
dyn_where = `DOMNAME LIKE 'Z%'`.
TRY .
SELECT COUNT(*) FROM (dyn_from) WHERE (dyn_where).
WRITE: / sy-dbcnt NO-GROUPING.
CATCH: cx_sy_open_sql_db INTO gx_sql_err,
cx_sy_dynamic_osql_semantics INTO gx_sql_err,
cx_sy_dynamic_osql_syntax INTO gx_sql_err.
ENDTRY.
IF gx_sql_err IS BOUND.
gv_text = gx_sql_err->get_text( ).
WRITE: / gv_text.
ENDIF.
BR,
Suhas -
Run time Error DBIF_RSQL_SQL_ERROR while logging and executing some tcodes
Hi all,
Hi all,
When i try to login into my system (ECC 6.0 with Oracle DB), i have been directed to dump -->
Runtime Errors DBIF_RSQL_SQL_ERROR
Except. CX_SY_OPEN_SQL_DB
Short text
SQL error in the database when accessing a table.
Missing RAISING Clause in Interface
Program SAPFSDS1
Include FSDS1E01
Row 365
Module type (FORM)
Module Name TRANSFORM_NEW_OLD
Trigger Location of Exception
Program SAPFSDS1
Include FSDS1E01
Row 380
Module type (FORM)
Module Name TRANSFORM_NEW_OLD
In the source code the the cause for the error is shown in the below line"
SELECT SINGLE * FROM TDCLD
WHERE DOKCLASS EQ DOKCLASS.
"How to correct the error"
Database error text........: "ORA-32255: Message 32255 not found;
product=RDBMS; facility=ORA#"
Internal call code.........: "RSQL/READ/TDCLD "
Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be abl
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the follo
keywords:
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
"SAPFSDS1" or "FSDS1E01"
"TRANSFORM_NEW_OLD"
When i tried to look for the error ORA-32255, i am unable to get any information regarding this?
Could you please suggest me..
I have made the following changes trying to solve the error:
shared_pool_size = 401832601 and
i have executed sql command --> alter system set "_object_statistics"=false scope=spfile;
Message from Alert Log file:
Incremental checkpoint up to RBA [0x1076.10c61.0], current log tail at RBA [0x1076.10e4d.0]
Message from dev_w0 file:
OCI-call failed with -1=OCI_ERROR
C SQL error 32255: 'ORA-32255: Message 32255 not found; product=RDBMS; facility=ORA
C '
C *** ERROR => Error 32255 in stmt_fetch() from oci_execute_stmt(), orpc=0
[dbsloci.c 12720]
C *** ERROR => ORA-32255 occurred when executing SQL stmt (parse error offset=0)
[dbsloci.c 12739]
C sc_p&H05B11F10,no&H110,idc_p&H00000000,con=0,act=1,sle n&H103,smax&H256,#vars=2,stmt
8718D8,table=ATAB
C SELECT "TABNAME" , "VARKEY" , "DATALN" , "VARDATA" FROM "ATAB" WHERE "TABNAME" = :A0 AND "VARKEY" = \
C :A1;
C sc_p&H05B11F10,no&H110,idc_p&H00000000,con=0,act=1,sle n&H103,smax&H256,#vars=2,stmt
8718D8,table=ATAB
C prep=0,lit=0,nsql=0,lobret=0,#exec=1,dbcnt=0,upsh_p &H00000000,ocistmth_p
872784
C IN : cols=2,rmax=1,xcnt=0,rpc=0,rowi=0,rtot=0,upto=-1,rs ize&H28,vmax&H32,bound=1,iobuf_p&H05BF4F28,vda_p
873CA8
C lobs=0,lmax=0,lpcnt=0,larr&H00000000,lcurr_p&H0000000 0,rret=0
C OUT: cols=4,rmax=1,xcnt=1,rpc=0,rowi=0,rtot=0,upto=-1,rs ize&H124,vmax&H32,bound=1,iobuf_p&H05BEBAF8,vda_p
874118
C lobs=0,lmax=0,lpcnt=0,larr&H00000000,lcurr_p&H0000000 0,rret=0
C SELECT "TABNAME" , "VARKEY" , "DATALN" , "VARDATA" FROM "ATAB" WHERE "TABNAME" = :A0 AND "VARKEY" = \
C :A1;
B ***LOG BY4=> sql error 32255 performing SEL on table ATAB [dbtran#11 @ 7512] [dbtran 7512 ]
B ***LOG BY0=> ORA-32255: Message 32255 not found; product=RDBMS; facility=ORA
[dbtran#11 @ 7512] [dbtran 7512 ]
B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'SEL'
B RSLT: {dbsl=99, tran=1}
B FHDR: {tab='ATAB', fcode&H17, mode=2, bpb=0, dbcnt=0, crsr=0,
B hold=0, keep=0, xfer=0, pkg=0, upto=0, init:b=0,
B init:p&H00000000, init:#=0, wa:p=0X031902F0, wa:#&H15000}
B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'SEL'
B STMT:
B CRSR: {tab='', id=0, hold=0, prop=0x80000, max.in@0=1, fae:blk=0,
B con:id=0, con:vndr=5, val=2,
B key:#=2, xfer=0, xin:#=1, row:#=0, upto=1, wa:p=0X031902F0}
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
A ** RABAX: level LEV_RX_ROLLBACK completed.
A ** RABAX: level LEV_RX_DB_ALIVE entered.
A ** RABAX: level LEV_RX_DB_ALIVE completed.
A ** RABAX: level LEV_RX_HOOKS entered.
A ** RABAX: level LEV_RX_HOOKS completed.
A ** RABAX: level LEV_RX_STANDARD entered.
A ** RABAX: level LEV_RX_STANDARD completed.
A ** RABAX: level LEV_RX_STOR_VALUES entered.
A ** RABAX: level LEV_RX_STOR_VALUES completed.
A ** RABAX: level LEV_RX_C_STACK entered.
A ** RABAX: level LEV_RX_C_STACK completed.
A ** RABAX: level LEV_RX_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_INTERFACES entered.
A ** RABAX: level LEV_RX_INTERFACES completed.
A ** RABAX: level LEV_RX_GET_MESS entered.
A ** RABAX: level LEV_RX_GET_MESS completed.
A ** RABAX: level LEV_RX_INIT_SNAP entered.
A ** RABAX: level LEV_RX_INIT_SNAP completed.
A ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
A ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_SN_END completed.
A ** RABAX: level LEV_RX_SET_ALERT entered.
A ** RABAX: level LEV_RX_SET_ALERT completed.
A ** RABAX: level LEV_RX_COMMIT entered.
A ** RABAX: level LEV_RX_COMMIT completed.
A ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
A ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
A ** RABAX: level LEV_RX_RESET_PROGS entered.
A ** RABAX: level LEV_RX_RESET_PROGS completed.
A ** RABAX: level LEV_RX_STDERR entered.
A Sun Apr 05 22:38:04 2009
A
A ABAP Program SAPFSDS1 .
A Source FSDS1E01 Line 380.
A Error Code DBIF_RSQL_SQL_ERROR.
A Module $Id: //bas/700_REL/src/krn/runt/absapsql.c#9 $ SAP.
A Function HandleRsqlErrors Line 778.
A ** RABAX: level LEV_RX_STDERR completed.
A ** RABAX: level LEV_RX_RFC_ERROR entered.
A ** RABAX: level LEV_RX_RFC_ERROR completed.
A ** RABAX: level LEV_RX_RFC_CLOSE entered.
A ** RABAX: level LEV_RX_RFC_CLOSE completed.
A ** RABAX: level LEV_RX_IMC_ERROR entered.
A ** RABAX: level LEV_RX_IMC_ERROR completed.
A ** RABAX: level LEV_RX_DATASET_CLOSE entered.
A ** RABAX: level LEV_RX_DATASET_CLOSE completed.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
A ** RABAX: level LEV_RX_ERROR_SAVE entered.
A ** RABAX: level LEV_RX_ERROR_SAVE completed.
A ** RABAX: level LEV_RX_ERROR_TPDA entered.
A ** RABAX: level LEV_RX_ERROR_TPDA completed.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
A ** RABAX: level LEV_RX_END entered.
A ** RABAX: level LEV_RX_END completed.
A ** RABAX: end no http/smtp
A ** RABAX: end RX_BTCHLOG|RX_VBLOG
A SQL error in the database when accessing a table..
A
I have started the local client copy and have stopped it in the middle. i have logged off and tried to login again, this is the start of the dump.
I am unable to resolve it. PLEASE give a solution
Thanks & Regards,
Subbu.Hi Subbu,
We were in touch when you previously posted this, but somehow I got an error when I tried to access the thread. I remember that your DB was still 10.2.0.1 and that this may have caused a corruption. The only explanation for ORA-32255 that looks remotely interesting is that it may occur with the OCI (Oracle Call Interface) accessing a NULL LOB (and ATAB does contain a LOB field). Do you have any chance of upgrading the database where you have the problem to 10.2.0.4?
I don't know whether we'll learn anything useful from this (you might just get an ORA-32255 again) but could you execute the following statement in SQLPLUS:
select count(*) from <sapuser>.ATAB where VARDATA IS NULL;
(replace <sapuser> with the name of the SAP schema owner)
Regards,
Mark -
DBIF_RSQL_SQL_ERROR - while dataloading from PSA to InfoCube!
Hi Friends,
I know this topic has been posted before too and i have gone through almost all the threads related to this topic but could not find the solution for this issue. Here is the details:
I am in Production and loading data to one the cube through PSA. Data comes fine till PSA (arround 1 million records). But when I am updating data to Infocube through DTP I am getting the following error:
Dump: ABAP/4 processor: DBIF_RSQL_SQL_ERROR
when i click on the error it says the following:
DBIF_RSQL_SQL_ERROR
CX_SY_OPEN_SQL_DB
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB'
According the previous threads on this issue its a Table space issue in Database. But I am sure its not table space issue as my other loads are successfull with much more number of records. I checked in DB02 too and see no problem with the table space.
I tried selective loading through DTP and my data load was successfull. But this is not the way we want to load the data. we dont want to give any selections in InfoPacakge.
I tried to see in ST22 and see the following dumps:
CONNE_IMPORT_WRONG_COMP_TYPE CX_SY_IMPORT_MISMATCH_ERROR
OBJECTS_OBJREF_NOT_ASSIGNED
CX_SY_REF_IS_INITIAL
DBIF_RSQL_SQL_ERROR
CX_SY_OPEN_SQL_DB
DBIF_RSQL_SQL_ERROR
CX_SY_OPEN_SQL_DB
I tried to delete infocube index first before load from PSA. but it did not work for me.
i would highly appriciate any help from ur side and will awarded with points.
Thanks,
ManmitThanks Srinivas. I can not reduce the package size because i am loading data from PSA to InfoCube through DTP. This DTP is created upon a data source which is a genereted export datasource i.e. <b>8XYZABC</b> which does not allow me to change the package size and this is decided at run time. I can see the following under the Extraction Tab of DTP :
<b>The package size corresponds to package size in source.
It is determined dynamically at runtime.</b>
Any idea how to solve this prob? -
DBIF_RSQL_SQL_ERROR while creating planned order in ECC
Hi ,
Recently we have done the ECC6.0 migration. Migration in the sense
Server A ECC6.0 Maxdb to Server B ECC6.0 Sqlserver.
we took the database export from server A and imported to Server B.
After completing the migration we are facing a problem.
Using Trx code MD11 I am creating Planned order. It is giving Planned order XXXXX will be created.But when I go MD13 and try to retrive the same planned order it says the order XXXXX doesn't exists.
when I try to go back from MD13 it shows Express document "update was terminated" received from Author ************.
I am seeing a dump in ST22.
Error 22.04.2010 DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB
Cann't insert NULL into column "ADCODE" Table "RESB"
Column doesn't allow NULLS . Insert Fails.
Any Help is Appreciated.
Regards,
Guru.Hi Srini,
Please kindly review and evaluate note 686357 for possible solution.
686357 able pool nametab length incorrect after Unicode
The following pools may be affected: ATAB, GLSP, GLTP, DVPOOLTEXT, KAPOL
Please kindly run report RATPONTC to reset the dictionary and nametab length in the note.
Regards,
Mauro -
"CX_SY_OPEN_SQL_DB" ERROR when modifying a custom table
Dear friends,
I get this runtime error "DBIF_RSQL_SQL_ERROR"
"CX_SY_OPEN_SQL_DB" excpetion raised while am trying to modify a custome table . says deadlock detected while waiting for resourcebelow is the code snippet please suggest solution on how to avoid the error. thanks for the help in advance.
kathy
*Get all packspec levels
lt_levels = iv_packspec_content-levels.
loop at lt_levels into ls_levels.
if ls_levels-hutyp is not initial.
ls_zpackspec-guid = ls_levels-guid.
ls_zpackspec-aennr = ls_levels-aennr.
ls_zpackspec-total_quan = ls_levels-total_quan.
ls_zpackspec-level_type = ls_levels-level_type.
ls_zpackspec-/cfscmx/nest_fc = ls_levels-/cfscmx/nest_fc.
ls_zpackspec-maxstack = ls_levels-maxstack.
ls_zpackspec-unit_tw = ls_levels-unit_tw.
ls_zpackspec-g_weight = ls_levels-g_weight.
ls_zpackspec-unit_tv = ls_levels-unit_tv.
ls_zpackspec-g_volume = ls_levels-g_volume.
ls_zpackspec-trgqty = ls_levels-trgqty.
ls_zpackspec-flg_minimum_ps = ls_levels-flg_minimum_ps.
ls_zpackspec-creadat = sy-datum.
ls_zpackspec-matid = iv_packspec_content-content-matid.
ls_zpackspec-hu_create = ls_levels-hu_create.
ls_zpackspec-unit_gw = ls_levels-unit_gw.
ls_zpackspec-g_capa = ls_levels-g_capa.
ls_zpackspec-unit_gv = ls_levels-unit_gv.
ls_zpackspec-hutyp = ls_levels-hutyp.
ls_zpackspec-block = ls_levels-block.
ls_zpackspec-length = ls_levels-length.
ls_zpackspec-width = ls_levels-width.
ls_zpackspec-height = ls_levels-height.
ls_zpackspec-unit_lwh = ls_levels-unit_lwh.
ls_zpackspec-nest_ftr = ls_levels-nest_ftr.
if not ls_elementgroup is initial.
sort ls_elementgroup by guid.
read table ls_elementgroup assigning <ps_el_group>
with key guid = ls_levels-elementgroup
binary search.
if <ps_el_group> is assigned.
ls_elemgroup = <ps_el_group>-elements.
endif.
sort ls_elemgroup by hurelevant.
read table ls_elemgroup assigning <ps_elem>
with key hurelevant = 1
binary search.
if sy-subrc eq 0.
ls_zpackspec-hurelevant = <ps_elem>-hurelevant.
endif.
endif.
append ls_zpackspec to lt_zpackspec.
clear ls_zpackspec.
endif.
endloop.
**Update Packspec data for each level in the table ZPACKSPEC.*
*if not lt_zpackspec is initial.*
*modify zpackspec from table lt_zpackspec.*
*ev_zpackspec = lt_zpackspec.*
*endif.*Kathy - do you have duplicate entries for the same key fields in the internal table you are using for the update?
Rob -
Planned order creation - DBIF_RSQL_SQL_ERROR
Hi ,
Recently we have done the ECC6.0 migration. Migration in the sense
Server A ECC6.0 Maxdb to Server B ECC6.0 Sqlserver.
we took the database export from server A and imported to Server B.
After completing the migration we are facing a problem.
Using Trx code MD11 I am creating Planned order. It is giving Planned order XXXXX will be created.
when I try to go back it shows Express document "update was terminated" received from Author ************.
Also when I go MD13 and try to retrive the same planned order it says the order XXXXX doesn't exists.
I am seeing a dump in ST22.Runtime error.
Error 22.04.2010 DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB
Cann't insert NULL into column "ADCODE" Table "RESB"
Column doesn't allow NULLS . Insert Fails.
But for server A with MaxDB I am able to create planned order.There it is not giving this error.After Migration only I am getting this error.
Any Help is Appreciated.
Regards,
Guru.Please check note 1377270.
There was a known problem with the R3load creating NOT NULL columns without defaults. For large tables with more than 28 columns, NOT NULL columns beyond the 28th column could be missing the default binding.
If you now run an INSERT against such a table you'll get the mentioned error.
Regards,
Guenther
Edited by: Guenther Drach on Apr 29, 2010 4:41 PM -
DBIF_RSQL_SQL_ERROR: SQL error in the database when accessing a table
Hi Gurus,
Im getting DBIF_RSQL_SQL_ERROR: SQL error in the database when accessing a table error while I was importing support pack in the system. This is ERP 6.0 with EHP4 with MS SQL in back ground and I was applying the BASIS SP 04. It was in the TEST scenario and in the SPDD_SPAU_CHECK phase it threw the error.
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/E071 ]"
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"
"SAPLSVRT" or "LSVRTU01"
"TR_LAST_IMPORT_OF_OBJECT"
SPAM is ending with the above short dump. I have checked the space availability and it is OK.
Kindly help.
Renju Aravind.Hi,
this error is very often seen in case of a database corruptions. Please follow note 142731 and perform a complete database check. Send the results when they show errors.
Best regards
Clas -
Hi to all,
I am loading the data from PSA to DSO, while running DTP, after some records load a run time error coming DBIF_RSQL_SQL_ERROR or DBIF_REPO_SQL_ERROR .
Also i tried the Number of Processes reduce from 3 to 1 in DTP, but still same error .
i have searched the SDN and found that it is due to table space problem.
if it is due to table space , how i will find it and how to correct it.
Please can any one tell we why it is coming and what is the solution for that.
i shall be thankful to you for this.
Regards
Pavneet RanaThanks for reply,
i have checked ST22 . and found the error text for 2 runtime error .
first for DBIF_RSQL_SQL_ERROR
second for DBIF_REPO_SQL_ERROR
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Date and Time 14.03.2011 22:00:21
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........: "SQL30081N A communication error has been
detected. Communication protocol being used: "TCP/IP". Communication API being
used: "SOCKETS". Location where the error was detected: "200.1.1.66".
Communication function detecting the error: "recv". Protoco"
Internal call code.........: "[RSQL/FTCH/RSBMONMESS ]"
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_RSBM_LOG_REQUEST_ROOT======CP" or "CL_RSBM_LOG_REQUEST_ROOT======CM00F"
"GET_STATIC_BUFFER"
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
"GET_STATIC_BUFFER" "(METHOD)", or its possible occurrence must be declared in
the
RAISING clause of the procedure.
To prevent the exception, note the following:
Information on where terminated
Termination occurred in the ABAP program "CL_RSBM_LOG_REQUEST_ROOT======CP" -
in "GET_STATIC_BUFFER".
The main program was "RSBATCH_EXECUTE_PROZESS ".
In the source code you have the termination point in line 29
of the (Include) program "CL_RSBM_LOG_REQUEST_ROOT======CM00F".
The program "CL_RSBM_LOG_REQUEST_ROOT======CP" was started as a background job.
Job Name....... "BIDTPR_2256_1"
Job Initiator.. " a"
Job Number..... 18254200
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "GET_STATIC_BUFFER" "(METHOD)", but it was neither handled locally
nor declared
in the RAISING clause of its signature.
The procedure is in program "CL_RSBM_LOG_REQUEST_ROOT======CP "; its source
code begins in line
1 of the (Include program "CL_RSBM_LOG_REQUEST_ROOT======CM00F ".
Source Code Extract
Line SourceCde
1 method get_static_buffer.
2 data l_s_storage type rsbm_s_storage.
3 l_s_storage = get_s_storage( ).
4 check l_s_storage-type = rsbm_c_storagetype-database..
5 delete o_th_nodes_static where logid = n_logid.
6 delete o_t_msg_static where logid = n_logid.
7 delete o_t_logpar_static where logid = n_logid.
8 select *
9 from rsbmnodes connection (l_s_storage-id)
10 appending corresponding fields of table o_th_nodes_static
11 where logid = n_logid.
12
13 data l_count_monmess type sytabix.
14 select count( * ) from rsbmonmess
15 into l_count_monmess
16 where logid = n_logid.
17 if l_count_monmess > 50000.
18 select * from rsbmonmess up to 50000 rows connection (l_s
19 appending corresponding fields of table o_t_msg_static
20 where logid = n_logid
21 and posit < 50
22 order by node posit.
23 else.
24 select * from rsbmonmess connection (l_s_storage-id)
25 appending corresponding fields of table o_t_msg_static
26 where logid = n_logid
27 order by node posit.
28 endif.
>>>>> select * from rsbmlogpar
30 appending corresponding fields of table o_t_logpar_static
31 where logid = n_logid.
32 field-symbols: <l_s_nodes> type rsbmnodes,
33 <l_s_log> type s_log.
34 read table o_th_log assigning <l_s_log>
35 with table key logid = n_logid.
36 if sy-subrc <> 0.
37 break hoeferf. "
38 endif.
39 loop at o_th_nodes_static assigning <l_s_nodes>.
40 if <l_s_nodes>-node > <l_s_log>-maxnode.
41 <l_s_log>-maxnode = <l_s_nodes>-node.
42 endif.
43 endloop.
44 * --- set datapackage buffer
45 cl_rsbk_dp_state=>free_buffer( n_requid ).
46 cl_rsbk_dp_state=>fill_buffer( n_requid ).
47 endmethod.
Runtime Errors DBIF_REPO_SQL_ERROR
Date and Time 14.03.2011 15:34:32
Short text
SQL error "-99999" occurred when accessing program
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrato
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........: "CLI0108E Communication link failure.
SQLSTATE=40003"
Triggering SQL statement...: "CX_SY_NATIVE_SQL_ERROR========CP "
Internal call code.........: "[REPO/*/43/LOAD/CX_SY_NATIVE_SQL_ERROR===
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_REPO_SQL_ERROR" " "
"SAPLSYDB" or "LSYDBU27"
"DB_COMMIT"
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.
Information on where terminated
Termination occurred in the ABAP program "SAPLSYDB" - in "DB_COMMIT".
The main program was "RSBATCH_EXECUTE_PROZESS ".
In the source code you have the termination point in line 7
of the (Include) program "LSYDBU27".
The program "SAPLSYDB" was started as a background job.
Job Name....... "BIDTPR_2252_1"
Job Initiator.. "A"
Job Number..... 12541100
Source Code Extract
Line SourceCde
1 FUNCTION DB_COMMIT.
2 *"----------------------------------------------------------------------
3 *"*"Lokale Schnittstelle:
4 *"----------------------------------------------------------------------
5
6 EXEC SQL.
>>>>> COMMIT WORK
8 ENDEXEC.
9
10 ENDFUNCTION
please can any one tell me cause for runtime error.
i shall be thankful to you for this.
regards
pavneet rana
Edited by: pavneet rana on Mar 15, 2011 1:29 PM -
DBIF_RSQL_SQL_ERROR which are related to BW ods Activation
Hi friends,
I dont know whether this is the right thread i am posting or not. But technical people can definately help me.
Recently we have upgraded patch from SP 22 to SP 25 for BI 7.0. From that time onwards i am facing issues like anything.
Here is the impact.
1. Data loads not triggering for process Chains as per schedules. we are running emegency chains manually. We have raised an issue to SAP, waiting for reply.
Short Dumps:
b)
DBIF_REPO_SQL_ERROR
Short text
SQL error 3114 occurred when accessing program "SAPLRS_EXCEPTION " part "LOAD".
What happened?
The system is no longer linked to an ORACLE instance.
No further operations can be performed on the database.
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...: "SAPLRS_EXCEPTION "
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" " "
"SAPLRRMS" or "LRRMSU14"
"RRMS_EXCEPTION_HANDLING"
c)
DBIF_RSQL_SQL_ERROR
CX_SY_OPEN_SQL_DB
How to correct the error
Database error text........: "ORA-03135: connection lost contact"
Internal call code.........: "[RSQL/RDUP/TADIR ]"
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"
"SAPLSDI0" or "LSDI0U01"
"TRINT_TADIR_UPDATE"
2. Especially ODS activation (through process chains) failing in every process Chain. if you run maual activation , then its ok.
All Batch are got struck when accessing table TADIR. Dump C which is mensioned above impact is very high on the system.
Anyone know about to resolve the above dumps, Please help me.
If you want to analyze more detailed level, please let me know
Thanks in Advance.
VenkatHi Mark,
Please gothrough below details.
Filename......: sqlnet.ora
Created.......: created by SAP AG, R/3 Rel. >= 6.10 # Name..........:
Date..........:
@(#) $Id: //bc/640-2/src/ins/SAPINST/impl/tpls/ora/ind/SQLNET.ORA#4 $ ################
AUTOMATIC_IPC = ON
TRACE_LEVEL_CLIENT = OFF
NAMES.DEFAULT_DOMAIN = WORLD
NAME.DEFAULT_ZONE = WORLD
SQLNET.EXPIRE_TIME = 0
TCP.NODELAY=YES
TADIR file got struck during this stament:
Last SQL statement
SELECT
/*+
FIRST_ROWS (1)
FROM
"TADIR"
WHERE
"PGMID" = :A0 AND "OBJECT" = :A1 AND "OBJ_NAME" = :A2
FOR UPDATE
Database Number Time (usec) Recs.
Direct Read 1,017 172,733 232
Sequential Read 1,815 471729 10,454
Insert 20 31,223 306
Update 25 9,621 17
Delete 25 115,827 291
Sources 3,069,427 (Bytes)
RSQL 2,265,032 (Bytes)
Commit 0
DB Procedure Calls 0 0
Thanks and reagards
Venkat
Maybe you are looking for
-
Select option in modular programming...?
Hi Abapers, I have a problem where in i want to use select options in modullar programming..... and one more thing that when ever i am using an EXECUTE button which has been defined manually by me.. the report show the output but we
-
Adobe PDF Writer (v5.0) won't install; can't find LPT1 port
I've searched extensively for an answer on this question, and the most common answer is no answer or use a newer PDF creator. The department I support uses database software that was never programmed to support any PDF creator past PDF Writer, so all
-
Utility or trick to get screenshots from USB-Adapter-driven monitor?
My main computer is a G5Quad, but this post relates to my MacBook. Recently, I acquired a USB-(display card)Adapter ( http://eshop.macsales.com/item/NewerTech/VIDU2DVIA/ ) to run the second one of my dual external monitors with my Ma
-
We removed some distributions from eDir and now the distributor keeps displaying the following error msg [TED: Event Processing] Distribution directory for 004-application.DISTRIBUTIONS.ZFS.SERVICES.SRC does not exist Is there a way I can get rid of
-
Question on VO bind variable ?
Hi, In one of my VO query's Select part, Im calling a function which accepts a parameter that comes from the pageContext eg: select abc(:1) from xyz; Any ideas on how to set the bind variable in the select clause of the VO query? Thanks!!