Runtime Error DBIF_RSQL_SQL_ERROR exception CX_SY_OPEN_SQL_DB
Hi,
i need some guides to solve this problem.
The program works fine in client DEV. However, when it's in QAS, we encounter short dump: Runtime Error DBIF_RSQL_SQL_ERROR exception CX_SY_OPEN_SQL_DB
info from short dump:
An SQL error occurred when accessing a table.
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
"FILL_T_DATA_TABLE" "(FORM)"
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
"FILL_T_DATA_TABLE"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-24371: data would not fit in current prefe
buffer"
Internal call code.........: "[RSQL/FTCH/VBUK ]"
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
"ZSDR_SHIPPING_REPORT" or "ZSDR_SHIPPING_REPORT"
"FILL_T_DATA_TABLE"
If you cannot solve the problem yourself, please send the...
Information on where terminated
The termination occurred in the ABAP program "ZSDR_SHIPPING_REPORT" in
"FILL_T_DATA_TABLE".
The main program was "ZSDR_SHIPPING_REPORT ".
The termination occurred in line 3561 of the source code of the (Include)
program "ZSDR_SHIPPING_REPORT"
of the source code of program "ZSDR_SHIPPING_REPORT" (when calling the editor
35610).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "FILL_T_DATA_TABLE" "(FORM)" but was not handled locally, not
declared in the
RAISING clause of the procedure.
The procedure is in the program "ZSDR_SHIPPING_REPORT ". Its source code starts
in line 3468
of the (Include) program "ZSDR_SHIPPING_REPORT ".
source code:
035490
035500 *get all open sales orders (those that are deemed open at the Sales
035510 *Order "Header" level)
035520 clear open_orders.
035530 refresh open_orders.
035540 select * into corresponding fields of table open_orders
035550 from vbuk
035560 where ( vbtyp = 'C' or vbtyp = 'I' )
035570 and ( gbstk = 'A' or gbstk = 'B' ).
035580
035590 *get all open deliveries(some sales orders may be closed yet the
035600 *associated Delivery is not yet PGI'd)
> clear open_deliveries.
035620 refresh open_deliveries.
035630 select * into corresponding fields of table open_deliveries
035640 from vbuk
035650 where vbtyp = 'J'
035660 and ( wbstk = 'A' or wbstk = 'B' ).
035670
035680 *get sales orders associated with the Open deliveries
Please advice.
Thanks.
Thanks for the response.
Hi Renga,
The error happens in second selection.
this is the souce code:
data: begin of open_orders occurs 0,
vbeln like vbuk-vbeln,
gbstk like vbuk-gbstk,
vbtyp like vbuk-vbtyp,
end of open_orders.
data: begin of open_deliveries occurs 0,
vbeln like vbuk-vbeln,
wbstk like vbuk-wbstk,
vbtyp like vbuk-vbtyp,
end of open_deliveries.
*get all open sales orders (those that are deemed open at the Sales
*Order "Header" level)
clear open_orders.
refresh open_orders.
select * into corresponding fields of table open_orders
from vbuk
where ( vbtyp = 'C' or vbtyp = 'I' )
and ( gbstk = 'A' or gbstk = 'B' ).
*get all open deliveries(some sales orders may be closed yet the
*associated Delivery is not yet PGI'd)
clear open_deliveries.
refresh open_deliveries.
select * into corresponding fields of table open_deliveries
from vbuk
where vbtyp = 'J'
and ( wbstk = 'A' or wbstk = 'B' ).
Hi Prabhu,
how to identify the problem in DB02?
Please advice.
Thanks.
regards.
Similar Messages
-
Hi,
Following code is working fine in Development system and in Production system I am getting a runtime error. Only difference I am finding is in r_lifnr value. In development system I have few lifnr and in Production system it's not so... am I getting error because of it? Is there any restriction to no. of items populated in a range? Or Basis person need to change any parameter? Enclosed the detail dump below the code...
Advance thanks.
Regards,
Balaji Viswanath.
Code:
SELECT bukrs
lifnr
augdt
augbl
zuonr
gjahr
belnr
buzei
waers
dmbtr
wrbtr
zlsch
shkzg
blart
gsber
sgtxt
INTO TABLE t_bsak_tmp
FROM bsak CLIENT SPECIFIED
WHERE mandt = sy-mandt AND
lifnr IN r_lifnr AND
bukrs IN s_bukrs AND
augdt IN s_augdt AND
blart IN s_blart.
IF sy-subrc <> 0.
No data found for selection criteria
MESSAGE i018.
LEAVE LIST-PROCESSING.
ENDIF.
Dump:
Runtime Errors DBIF_RSQL_INVALID_RSQL
Exception CX_SY_OPEN_SQL_DB
Occurred on 14.11.2005 at 14:35:22
Error in the module RSQL accessing the database interface.
What happened?
Error in ABAP application program.
The current ABAP program "/DS1/FI_CR_REPT_PGSR802_VEND_P" had to be terminated
because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
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.
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_CLRD_VEN_DATA" "(FORM)"
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:
The SQL statement generated from the SAP Open SQL Statement violates a
restriction imposed by the database system used in R/3.
Possible errors:
o The maximum size of an SQL statement has been exceeded.
o The statement contains too many input variables.
o The space needed for the input data exceeds the available memory.
o ...
You can usually find details in the system log (SM21) and in the
developer trace of the work process (ST11).
If an error occurs the developer trace often informs you about the
current restrictions.
How to correct the error
The exception must either be prevented, caught within the procedure
"GET_CLRD_VEN_DATA"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
The SAP Open SQL statement must be divided into several smaller units.
If the problem occurred due to the use of an excessively large table
in an IN itab construct, you can use the addition FOR ALL ENTRIES
instead.
When you use this addition, the statement is split into smaller units
according to the restrictions of the database system used.
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_INVALID_RSQL" CX_SY_OPEN_SQL_DBC
"/DS1/FI_CR_REPT_PGSR802_VEND_P" or "/DS1/FI_CR_REPT_PGSR802_VEND_P"
"GET_CLRD_VEN_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 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....... "ztm1003"
Network address.......... "145.26.160.103"
Operating system......... "AIX"
Release.................. "5.3"
Hardware type............ "00C004DC4C00"
Character length......... 16 Bits
Pointer length........... 64 Bits
Work process number...... 6
Short dump setting....... "full"
Database server.......... "ztm1003"
Database type............ "ORACLE"
Database name............ "A94"
Database owner........... "SAPR3K"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Aug 7 2005 20:44:35"
Created in............... "AIX 1 5 00538A4A4C00"
Database version......... "OCI_920 "
Patch level.............. "85"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE
10.1.0.."
SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
User, transaction...
Client.............. 110
User................ "INBVI0"
Language key........ "E"
Transaction......... "SE38 "
Program............. "/DS1/FI_CR_REPT_PGSR802_VEND_P"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "/DS1/FI_CR_REPT_PGSR802_VEND_P"
in "GET_CLRD_VEN_DATA".
The main program was "/DS1/FI_CR_REPT_PGSR802_VEND_P ".
The termination occurred in line 503 of the source code of the (Include)
program "/DS1/FI_CR_REPT_PGSR802_VEND_P"
of the source code of program "/DS1/FI_CR_REPT_PGSR802_VEND_P" (when calling
the editor 5030).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "GET_CLRD_VEN_DATA" "(FORM)" but was not handled locally, not
declared in the
RAISING clause of the procedure.
The procedure is in the program "/DS1/FI_CR_REPT_PGSR802_VEND_P ". Its source
code starts in line 501
of the (Include) program "/DS1/FI_CR_REPT_PGSR802_VEND_P ".
Source code extract
004730 &----
004740 * get country names from t005t
004750 ----
004760 FORM get_country_names.
004770
004780 t_lfa1_land[] = t_lfa1[].
004790 SORT t_lfa1_land BY land1.
004800 DELETE ADJACENT DUPLICATES FROM t_lfa1_land COMPARING land1.
004810
004820 IF NOT t_lfa1_land[] IS INITIAL.
004830 SELECT land1
004840 landx
004850 INTO TABLE t_t005t
004860 FROM t005t
004870 FOR ALL ENTRIES IN t_lfa1_land
004880 WHERE spras = sy-langu AND
004890 land1 = t_lfa1_land-land1.
004900 REFRESH t_lfa1_land.
004910 SORT t_t005t BY land1.
004920 ELSE.
004930 MESSAGE i014 WITH 'No vendor data fetched'(001).
004940 ENDIF.
004950 ENDFORM. " get_country_names
004960 &----
004970 *& Form get_clrd_ven_data
004980 &----
004990 * Cleared vendor data
005000 ----
005010 FORM get_clrd_ven_data .
005020
> SELECT bukrs
005040 lifnr
005050 augdt
005060 augbl
005070 zuonr
005080 gjahr
005090 belnr
005100 buzei
005110 waers
005120 dmbtr
005130 wrbtr
005140 zlsch
005150 shkzg
005160 blart
005170 gsber
005180 sgtxt
005190 INTO TABLE t_bsak_tmp
005200 FROM bsak CLIENT SPECIFIED
005210 * the order of the fields are as in the secondary Index.
005220 WHERE mandt = sy-mandt AND
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 0
SY-TABIX 1 SY-DBCNT 59
SY-FDPOS 0 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY
SY-UCOMM
SY-TITLE Vendor Payment Details for IRD
SY-MSGTY I SY-MSGID SF
SY-MSGNO 616 SY-MSGV1 /DS1/FI_CR_REPT_PGSR802_VEND_P
SY-MSGV2 RE SY-MSGV3 EN
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
2 FORM GET_CLRD_VEN_DATA
/DS1/FI_CR_REPT_PGSR802_VEND_P
/DS1/FI_CR_REPT_PGSR802_VEND_P 503
1 EVENT START-OF-SELECTION
/DS1/FI_CR_REPT_PGSR802_VEND_P
/DS1/FI_CR_REPT_PGSR802_VEND_P 135Hi Balaji,
Here is what the dump said and my answers are right below them.
<i>Possible errors:</i>
o The maximum size of an SQL statement has been exceeded.</i>
This may not be the reason in your case. This usually happens when you use the option FOR ALL ENTRIES
<i>o The statement contains too many input variables.</i>
Most likely this is your issue. I think your r_lifnr is filled with all the vendors in your system and filled as single values. In that case you may be exceeding a limit set on the system. Instead of trying to remove this setting, what I would suggest is to do the following.
Define a select-option for LIFNR on your selection screen. This way users can have the flexibility of specifying certain vendors. If they don't enter anything, it is still ok. Don't fill it with single values.
Use this select-option in your select statement. After the select statement, do a delete from itab where the vendors are not in your r_lifnr as below.
DELETE t_bsak_tmp WHERE NOT lifnr IN r_lifnr.
Also, avoid using client. You don't need that unless you really want to select from a different client other than your logon client. Your select statement is using logon client anyway, so you don't need to specify that.
<i>o The space needed for the input data exceeds the available memory.</i>
If the above changes are made and the problem is still there, then this is the next thing to look at.
Srinivas -
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 -
Hi guru's,
I have a genric data source with function module which feeds data to a genric ods in bw.
But at time of data upload i see quality status in manage of ods green saying (0 of 0 records extracted) but it asks me to check dump in st22 which is as follows
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Occurred on 30.01.2008 at 10:41:31
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
"STORAGE_LOC_GET" "(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
"STORAGE_LOC_GET"
"(METHOD)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-04030: out of process memory when trying to
allocate 1332 bytes (callheap,qkkele)"
Internal call code.........: "[RSQL/READ/T001L ]"
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
"SAPLMIGO" or "########################################"
"STORAGE_LOC_GET"
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....... "TOGR3PRD1"
Network address.......... "10.1.9.9"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "8x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "TOGR3PRD2"
Database type............ "ORACLE"
Database name............ "PRD"
Database owner........... "SAPPRD"
Character set............ "Thai_Thailand.874"
SAP kernel............... "640"
Created on............... "Sep 19 2005 00:05:54"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "91"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE
10.1.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
User, transaction...
Client.............. 900
User................ 0060302
Language key........ "E"
Transaction......... "MIGO "
Program............. "SAPLMIGO"
Screen.............. "SAPLMIGO 0001"
Screen line......... 15
Information on where terminated
The termination occurred in the ABAP program "SAPLMIGO" in "STORAGE_LOC_GET".
The main program was "SAPLMIGO ".
The termination occurred in line 0 of the source code of the (Include)
program "########################################"
of the source code of program "########################################" (when
calling the editor 00).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "STORAGE_LOC_GET" "(METHOD)" but was not handled locally, not
declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLMIGO ". Its source code starts in line 158
of the (Include) program "LMIGOBU2 ".
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 4 SY-INDEX 1
SY-TABIX 0 SY-DBCNT 1
SY-FDPOS 1 SY-LSIND 0
SY-PAGNO 1 SY-LINNO 1
SY-COLNO 1 SY-PFKEY MIGO_STATUS
SY-UCOMM MIGO_OK_TAKE_VALUE
SY-TITLE Goods Issue Others - 0060302 หน.แผนกและจนท.คลังสินค้า,คล
SY-MSGTY E SY-MSGID MICK
SY-MSGNO 004 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
7 METHOD STORAGE_LOC_GET
SAPLMIGO
LMIGOBU2 173
LCL_MIGO_BUFFER
6 METHOD LINE_CHECK
SAPLMIGO
LMIGOKL4 217
LCL_MIGO_KERNEL
5 METHOD LINE_MODIFY
SAPLMIGO
LMIGOKL1 123
LCL_MIGO_KERNEL
4 METHOD VALUECOPY
SAPLMIGO
LMIGOTV3 370
LCL_MIGO_TABLEVIEW
3 METHOD LIF_MIGO_FRAME~OKCODE_HANDLER
SAPLMIGO
LMIGOTV2 174
LCL_MIGO_TABLEVIEW
2 METHOD OKCODE_DISPATCH
SAPLMIGO
LMIGOFR2 171
LCL_MIGO_FRAME
1 MODULE (PAI) PAI_OKCODE_DISPATCH
SAPLMIGO
LMIGOPAI 11
Chosen variables
7 METHOD STORAGE_LOC_GET
SAPLMIGO
LMIGOBU2 173
I_PLANT
2222
0000
I_STORAGE_LOC 2031
3333
2031
E_STORAGE_LOC
222222222222222222
000000000000000000
%_FUN*TV_GOSPLIT <initial>
<initial>
<initial>
GOITEM-KZVBR
2
0
<%_TABLE_T001L> ???
%_SPACE
2
0
%_ARCHIVE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
SYST-REPID SAPLMIGO
5454444422222222222222222222222222222222
310CD97F00000000000000000000000000000000
<%_TABLE_TQSS1> ???
SY-REPID SAPLMIGO
5454444422222222222222222222222222222222
310CD97F00000000000000000000000000000000
%_DUMMY$$
2222
0000
GODYNPRO-DETAIL_ZEILE 0000
3333
0000
LCL_MIGO_GLOBALS=>KERNEL->S_CO WA
54
71
LS_T001L
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
22222222222222222222222222222
00000000000000000000000000000
OREF_DETAIL_MATERIAL
SY-SUBRC 4
0000
4000
GOITEM_TV 0017
3333222222222222222222222222222222222222
0017000000000000000000000000000000000000
... + 40 G152 Wh F SV U65 -025 -050
2222222222222243332562425525332233322333
0000000000000071520780603605650D0250D050
... + 80 X#######
2222222222222250000000222222222222222222
000000000000008000020C000000000000000000
... + 120 4020111650-002-005 9
2222222222233333333332333233322222222223
000000000004020111650D002D00500000000009
... + 160 03 ######
3322222222222222222222222222222222000000
0300000000000000000000000000000000000000
... + 200 # 0
0222222222222222222222222222222222222223
C000000000000000000000000000000000000000
... + 240 000000000000000
333333333333333
000000000000000
SY-XPROG SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
%_FL1*TV_GOFREIGHT 1
0000
1000
SY-XFORM CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
%_FUN*TV_GOSERIAL 1
0000
1000
6 METHOD LINE_CHECK
SAPLMIGO
LMIGOKL4 217
IS_OLD_GOITEM 00000002000000000000 X
2222222222333333333333333333332222252222
0000000000000000020000000000000000080000
... + 40 903H - 1 1 201
2223334222223222322222222233322222222222
0009038000D01000100000000020100000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
CS_GOITEM 00000002000000000000 X
2222222222333333333333333333332222252222
0000000000000000020000000000000000080000
... + 40 903H - 1 1 201
2223334222223222322222222233322222222222
0009038000D01000100000000020100000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
LC_BATCH_CONVERSION_ACTIVE 1
3
1
LCL_MIGO_CURSOR=>VALUE FG Rework
4425676762222222222222222222222222222222
670257F2B0000000000000000000000000000000
... + 40
2222222222
0000000000
%_FL1*TV_GOSPLIT <initial>
<initial>
<initial>
LS_GOPLANT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
22222222222222222222222222222
00000000000000000000000000000
GOITEM-EXVKW #######
0000000
000000C
ME->PS_GOHEAD+746(3) TH
542
480
LS_GOPLANT-LAND1
222
000
LS_GOT001L
222222222222222222
000000000000000000
SY ########################################
0000000000000000000000000000000000000000
1000100000001000000000000000000000000000
... + 40 ########################################
0000000000000000000000000000000000001000
100010001000000010000000000000000000A000
... + 80 ################<#######################
0000000000000000300000000000000000000000
0000000050004000C00000000000000000000000
... + 120 ####################################p###
0000000000000000000000000000000010007000
00000000000000000000000000000000A0000000
... + 160 ####<#######pb## C############# E1 0
0000300000007600240000000000000222432223
0000C00000000200030030000C0000C000510000
... + 200 0010001 ####D$S 900
3333333222220000425222222222222222223332
0010001000001000443000000000000000009000
... + 240 00
222223322222222
000000000000000
OREF_HEADER_GENERAL
LS_GOITEM-WERKS
2222
0000
LS_GOITEM-LGORT 2031
3333
2031
OREF_SPLIT_QUANTITY
ME
LS_GOITEM 00000002000000000000 X
2222222222333333333333333333332222252222
0000000000000000020000000000000000080000
... + 40 903H - 1 1 201
2223334222223222322222222233322222222222
0009038000D01000100000000020100000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
5 METHOD LINE_MODIFY
SAPLMIGO
LMIGOKL1 123
I_LINE 2
0000
2000
I_TABIX 0
0000
0000
I_INSERT
2
0
I_FORCE_CHANGE
2
0
I_AUTHORITY_CHECK
2
0
I_STATUS_DELAYED X
5
8
I_DEPENDENT_TABLES
2
0
IT_GOSERIAL Table[initial]
IT_GOFREIGHT Table[initial]
CS_GOITEM 00000002000000000000 X
2222222222333333333333333333332222252222
0000000000000000020000000000000000080000
... + 40 903H - 1 1 201
2223334222223222322222222233322222222222
0009038000D01000100000000020100000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
ME
LS_OLD_GOITEM 00000002000000000000 X
2222222222333333333333333333332222252222
0000000000000000020000000000000000080000
... + 40 903H - 1 1 201
2223334222223222322222222233322222222222
0009038000D01000100000000020100000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
LS_NEW_GOITEM 00000002000000000000 X
2222222222333333333333333333332222252222
0000000000000000020000000000000000080000
... + 40 903H - 1 1 201
2223334222223222322222222233322222222222
0009038000D01000100000000020100000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
ABAP_FALSE
2
0
GODYNPRO-UMCHA
2222222222
0000000000
ME->PT_GOITEM Table IT_156[20x2752]
L_TABIX 2
0000
2000
4 METHOD VALUECOPY
SAPLMIGO
LMIGOTV3 370
LS_TARGET_GOITEM-GLOBAL_COUNTE 000002
333333
000002
L_CHECKFIELD GOITEM-LGOBE
444544244444222222222222222222
7F945DDC7F25000000000000000000
L_STATUS 1229932294
0
6
G_SUB_TAXES
2222
0000
LCL_MIGO_SCREENMODIFICATION=>C 960038918
0
6
L_FIELD_TARGET LS_TARGET_GOITEM-LGORT
4555454455444544244455222222222222222222
C3F412754F7F945DDC7F24000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
222222222222
000000000000
<L_VALUE_TARGET> 2031
3333
2031
<L_VALUE_SOURCE> 2031
3333
2031
LCL_MIGO_GLOBALS=>KERNEL
L_TARGETLINE 2
0000
2000
ABAP_TRUE X
5
8
LS_TARGET_GOITEM 00000002000000000000 X
2222222222333333333333333333332222252222
0000000000000000020000000000000000080000
... + 40 903H - 1 1 201
2223334222223222322222222233322222222222
0009038000D01000100000000020100000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
%_CX_GRID_ID 1
0000
1000
3 METHOD LIF_MIGO_FRAME~OKCODE_HANDLER
SAPLMIGO
LMIGOTV2 174
I_OKCODE MIGO_OK_TAKE_VALUE
4444544554445544542222222222222222222222
D97FFFBF41B5F61C550000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
GOSPLIT #######
2222222222222222222222222222000000022222
0000000000000000000000000000000000C00000
... + 40
222222222222222222222222222222
000000000000000000000000000000
LCL_MIGO_GLOBALS=>KERNEL
GOSEARCH_PO
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160 0000000000
2222222222222222222222222222223333333333
0000000000000000000000000000000000000000
... + 200 000000
3333332222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240 000000
333333
000000
LS_CONTROL
222222222222222
000000000000000
%_CX_TABSTRIP_VERSION 0
3
0
GOSEARCH_ORD
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
222222222222
000000000000
RSJOBINFO 00000000
2222222222222222222222222222222233333333
0000000000000000000000000000000000000000
... + 40 000000
3333332222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 ####
0000
0000
ME
2 METHOD OKCODE_DISPATCH
SAPLMIGO
LMIGOFR2 171
I_OKCODE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
L_MSG_STRING
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
222222222222222222222222222222
000000000000000000000000000000
LCL_MIGO_GLOBALS=>EXTERNAL_CAL 0000000000
3333333333
0000000000
L_OKCODE MIGO_OK_TAKE_VALUE
4444544554445544542222222222222222222222
D97FFFBF41B5F61C550000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
SCREEN OK_NEW_ITEMS
4454455454452222222222222222222222222222
FBFE57F945D30000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120 00001#10000 ####
2222222222222222222222223333303333320000
0000000000000000000000000000101000000000
1 MODULE (PAI) PAI_OKCODE_DISPATCH
SAPLMIGO
LMIGOPAI 11
LCL_MIGO_FRAME=>TRACE_INFOS
2
0
LCL_MIGO_GLOBALS=>EXTERNAL_CAL 0000000000
3333333333
0000000000
LCL_MIGO_GLOBALS=>EXTERNAL_CAL 0000
3333
0000
LCL_MIGO_GLOBALS=>EXTERNAL_CAL 00000
33333
00000
OKCODE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
Application Calls
No dump information available
Application Information
No dump information available
Internal notes
The termination occurred in the function "HandleRsqlErrors" of the SAP
Basis System, specifically in line 773 of the module
"//bas/640_REL/src/krn/runt/absapsql.c#16".
The internal operation just processed is "SQLS".
The internal session was started at 20080130103952.
Internal call code.........: "[RSQL/READ/T001L ]"
Active calls in SAP kernel
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App : disp+work.EXE (pid=4832)
When : 1/30/2008 10:41:32.722
Threads : 2
Computer Name : TOGR3PRD1
User Name : SAPServicePRD
Number of Processors: 8
Processor Type: x86 Family 15 Model 2 Stepping 6
Windows Version : 5.2 Current Build: 3790
State Dump for Thread Id 14ac
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=003c61d4 edi=003c61a8
eip=7c82ed54 esp=03fedfb4 ebp=03fedfc4 iopl=0 nv up ei pl nz ac po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000216
function : KiFastSystemCallRet
7c82ed54 c3 ret
7c82ed55 8da42400000000 lea esp,[esp] ss:03fedfb4=7c82ed5c
7c82ed5c 8d642400 lea esp,[esp] ss:07fdb4c7=00000000
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
03fedfc4 003c61a8 00000000 00000001 01d40b84 000014ac ntdll!KiFastSystemCallRet
00000000 00000000 00000000 00000000 00000000 00000000 <nosymbols>
State Dump for Thread Id 168c
eax=00000001 ebx=00000103 ecx=fffffffe edx=003c0000 esi=00000000 edi=00000000
eip=7c82ed54 esp=05fefeb0 ebp=05fefef4 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
function : KiFastSystemCallRet
7c82ed54 c3 ret
7c82ed55 8da42400000000 lea esp,[esp] ss:05fefeb0=7c821514
7c82ed5c 8d642400 lea esp,[esp] ss:09fdd3c3=00000000
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
05fefef4 00fede51 00000eb0 00000000 00000000 003c7920 ntdll!KiFastSystemCallRet
05feff84 7c349565 00000000 00000000 00000000 003c79b8 disp+work!SigIMsgFunc >
> [signt.c (563)]
05feffb8 77e6608b 003c79b8 00000000 00000000 003c79b8 MSVCR71!endthreadex
05feffec 00000000 7c3494f6 003c79b8 00000000 00000000 kernel32!GetModuleFileNameA
List of ABAP programs affected
Type
Program
Gen. Date Time
Load Size
Prg
SAPLMIGO
22.09.2005 21:54:56
1226752
Prg
SAPMSSYD
05.06.2002 17:09:33
16384
Prg
SAPFSYSCALLS
14.02.2002 14:22:47
6144
Prg
CL_MMIM_USERDEFAULTS==========CP
06.05.2002 10:42:38
17408
Typ
ESDUS
01.03.1999 13:36:04
2048
Typ
GOHEAD
08.01.2003 16:15:40
9216
Typ
MKPF
08.01.2002 15:13:52
5120
Typ
KBEFU
26.03.1999 14:46:02
5120
Typ
LFA1
11.05.2004 11:32:44
19456
Typ
MIGO_CUST_ACTION
30.11.1999 10:19:14
2048
Typ
MIGO_CUST_REFDOC
30.11.1999 10:19:14
2048
Typ
X031L
15.11.2000 18:03:28
5120
Prg
SAPLSDIFRUNTIME
22.09.2005 21:42:36
81920
Typ
DFIES
09.11.2000 14:07:05
8192
Prg
SAPLSDNT
22.09.2005 21:55:13
201728
Prg
SAPLSUGS
22.09.2005 21:42:36
29696
Prg
SAPLV01D
11.05.2004 11:59:11
25600
Typ
IWRKZ
04.04.1995 15:56:46
1024
Typ
TCUCH
07.01.2002 15:50:54
3072
Typ
TCUBN
07.01.2002 15:50:53
2048
Typ
TCUWS
13.08.1997 13:57:58
2048
Typ
TCUDRV
07.01.2002 15:50:54
2048
Prg
CL_GUI_CFW====================CP
22.09.2005 21:14:53
154624
Prg
CL_GUI_PROPS_CONSUMER=========CP
07.01.2003 18:26:56
26624
Prg
%_CCNTL
14.02.2002 14:22:46
13312
Prg
SAPLTHFB
22.09.2005 22:08:44
304128
Prg
CL_EXITHANDLER================CP
16.06.2004 11:34:41Hello,
the problem is the following error:
>> ORA-04030: out of process memory when trying to allocate 1332 bytes (callheap,qkkele)
Take a look at sapnote #130140 and #335230 and follow the instructions.
Regards
Stefan -
Hi All,
I am getting the below short when i try to load the data into BI system. when I start the Info Package, it is immediately going to this short dump.
Runtime Errors DBIF_RSQL_SQL_ERROR
Except. CX_SY_OPEN_SQL_DB
Date and Time 15.12.2011 02:43:18
Short text
SQL error in the database when accessing a table.
Please find the short dump details below.
Runtime Errors DBIF_RSQL_SQL_ERROR
Except. CX_SY_OPEN_SQL_DB
Date and Time 15.12.2011 02:43:18
Short text
SQL error in the database when accessing a table.
Missing RAISING Clause in Interface
Program SAPLBTCH
Include LBTCHFXX
Row 1.525
Module type (FORM)
Module Name STORE_NEW_STEPLIST_IN_DB
Trigger Location of Exception
Program SAPLBTCH
Include LBTCHFXX
Row 1.652
Module type (FORM)
Module Name STORE_NEW_STEPLIST_IN_DB
Source Code Extract
Line SourceCde
1622 ID 'DATA' FIELD jobinfo_egj.
1623
1624 rc = 1.
EXIT.
ELSE.
db_steplist-priparkey = tmp_key.
ENDIF.
ENDIF.
SEIF new_steplist-typ = btc_xcmd." Step executes external command
db_steplist-extcmd = new_steplist-program.
db_steplist-xpgparams = new_steplist-parameter.
db_steplist-xpgflag = 'X'.
SE. " Step führt ein externes Programm aus
db_steplist-xpgprog = new_steplist-program.
db_steplist-xpgparams = new_steplist-parameter.
db_steplist-xpgflag = 'X'.
DIF.
steplist-sdldate = newjob_head-sdldate.
steplist-sdltime = newjob_head-sdltime.
steplist-sdluname = newjob_head-sdluname.
PEND db_steplist.
ep_count = step_count + 1.
OOP.
liste in DB speichern
RT tbtcp FROM TABLE db_steplist ACCEPTING DUPLICATE KEYS."n952782
y-subrc NE 0.
dialog EQ btc_yes.
MESSAGE s120 WITH new_job_head-jobname.
ENDIF.
CONCATENATE new_job_head-jobname new_job_head-jobcount INTO
jobinfo_egj SEPARATED BY '/'.
CALL 'C_WRITE_SYSLOG_ENTRY' ID 'TYP' FIELD ' '
ID 'KEY' FIELD tbtcp_insert_db_error
ID 'DATA' FIELD jobinfo_egj.
rc = 1.
EXIT.
ENDIF.
rc = 0.
DFORM. " STORE_NEW_STEPLIST_IN_DB
I would like to know where exactly it is getting error. Please help me on this.
Regards,
Venkat.Hi,
Check following
See the OSS Notes:
Note 1379839 - RuntimeError DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB
Note 917927 - Status of transactional requests
Note 863054 - Correction: Missing packages not in the tree
And also check the following things.
1.Connections from BW to ECC and ECC to BW in SM59
2.Check Port,Partner Profiles,and Message Types in WE20 in ECC & BW.
3.Check Dumps in ST22, and SM21.
4.If Idocs are stuck i.e see the OLTP Idoc numbers in RSMO Screen in (BW) detials tab see in bottom, you can see OLTP Idoc number and take the Idoc numbers and then goto to ECC see the status in WE05 or WE02, if error then check the log else goto to BD87 in ECC and give the Idoc numbers and execute manually and see in RSMO and refresh.
5.Check the LUWs struck in SM58,User Name = * (star) and run it and see Strucked LUWs and select our LUW and execute manually and see in RSMO in BW.
There are many threads also on this.
Go through them
Runtime Errors DBIF_RSQL_SQL_ERROR & Exception: CX_SY_OPEN_SQL_DB
Short Dump in SAP BW Sys while extracting data from R/3
Thanks and regards -
Hi,
I am getting following shortdump in my SCM 5.0 system with LiveCache 7.6.03 on AIX 5.3.
Please help me.
Runtime Errors DBIF_DSQL2_SQL_ERROR
Exception CX_SY_NATIVE_SQL_ERROR
Date and Time 01.07.2008 09:20:09
Short text
An SQL error occurred when executing Native SQL.
What happened?
The error "-4016" occurred in the current database connection "LCA".
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
How to correct the error
Database error text........: "POS(1) Unknown procedure
name:SIM_SIMSESSION_GET_ACTIVE"
Database error code........: "-4016"
Triggering SQL statement...: "EXECUTE PROCEDURE "SIM_SIMSESSION_GET_ACTIVE""
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"
"/SAPAPO/SAPLOM_CORE" or "/SAPAPO/LOM_COREU23"
"/SAPAPO/OM_SIMSESSION_GET_ALL"
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
"/SAPAPO/OM_SIMSESSION_GET_ALL" "(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... "dewall43"
Network address...... "10.40.16.43"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "00C912FC4C00"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 14
Shortdump setting.... "full"
Database server... "dewall43"
Database type..... "ORACLE"
Database name..... "APO"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Jan 23 2008 21:25:00"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 144
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory consumption
Roll.... 1117168
EM...... 0
Heap.... 0
Page.... 24576
MM Used. 720672
MM Free. 376056
User and Transaction
Client.............. 100
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Transactions ID..... "48692ABF23D6012AE10080000A28102B"
Program............. "/SAPAPO/SAPLOM_CORE"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "/SAPAPO/SAPLOM_CORE" - in
"/SAPAPO/OM_SIMSESSION_GET_ALL".
The main program was "/SAPAPO/OM_DELETE_OLD_SIMS ".
In the source code you have the termination point in line 39
of the (Include) program "/SAPAPO/LOM_COREU23".
The program "/SAPAPO/SAPLOM_CORE" was started as a background job.
Job Name....... "/SAPAPO/OM_DELETE_OLD_SIMSESS"
Job Initiator.. "DDIC"
Job Number..... 08200801
The termination is caused because exception "CX_SY_NATIVE_SQL_ERROR" occurred
in
procedure "/SAPAPO/OM_SIMSESSION_GET_ALL" "(FUNCTION)", but it was neither
handled locally nor declared
in the RAISING clause of its signature.
The procedure is in program "/SAPAPO/SAPLOM_CORE "; its source code begins in
line
1 of the (Include program "/SAPAPO/LOM_COREU23 ".
Source Code Extract
Line
SourceCde
9
*" REFERENCE(ET_ACTIVE_SIMSESSION) TYPE /SAPAPO/OM_SIMSESSION_TAB
10
*" REFERENCE(ET_RC) TYPE /SAPAPO/OM_LC_RC_TAB
11
*" EXCEPTIONS
12
*" LC_CONNECT_FAILED
13
*" LC_COM_ERROR
14
*" LC_APPL_ERROR
15
16
17
data_def.
18
create_gen_com_params_default.
19
CLEAR ls_gen_com_params-client.
20
21
Verbindung zum liveCache aufbauen
22
start_function 'OM_SIMSESSION_GET_ALL'. "#EC *
23
check_server.
24
connect_to_livecache.
25
IF et_simsession IS REQUESTED.
26
COM-Routine zum Auslesen aller trans. Sim.
27
EXEC SQL.
28
EXECUTE PROCEDURE "SIM_SIMSESSION_GET_ALL" (
29
IN :LS_GEN_COM_PARAMS,
30
OUT :LV_RC,
31
OUT :ET_SIMSESSION)
32
ENDEXEC.
33
Returncodes pruefen und evtl. Exception raisen
34
lv_subrc_sav = sy-subrc.
35
ENDIF.
36
IF et_active_simsession IS REQUESTED.
37
COM-Routine zum Auslesen aller aktiven trans. Sim.
38
EXEC SQL.
>>>>>
EXECUTE PROCEDURE "SIM_SIMSESSION_GET_ACTIVE" (
40
IN :LS_GEN_COM_PARAMS,
41
OUT :LV_RC,
42
OUT :ET_ACTIVE_SIMSESSION)
43
ENDEXEC.
44
Returncodes pruefen und evtl. Exception raisen
45
lv_subrc_sav = sy-subrc.
46
ENDIF.
47
48
end_performance_measure.
49
end_function_no_main om_simsession_get_all.
50
check_returncodes.
51
if iv_get_testguids = gc_false.
52
delete ET_ACTIVE_SIMSESSION where table_line cs '~'.
53
delete ET_SIMSESSION where table_line cs '~'.
54
endif.
55
ENDFUNCTION.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Periodic Deletion of Hanging Simulation Versions
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080701
SY-UZEIT
092008
SY-XPROG
RSDBRUNT
SY-XFORM
%_INIT_PBO_FIRST
Active Calls/Events
No. Ty. Program Include Line
Name
3 FUNCTION /SAPAPO/SAPLOM_CORE /SAPAPO/LOM_COREU23 39
/SAPAPO/OM_SIMSESSION_GET_ALL
2 FUNCTION /SAPAPO/SAPLOM_CORE /SAPAPO/LOM_COREU12 52
/SAPAPO/OM_SIMSESSION_SELECT
1 EVENT /SAPAPO/OM_DELETE_OLD_SIMS /SAPAPO/OM_DELETE_OLD_SIMS 67
START-OF-SELECTION
Chosen variables
Name
Val.
No. 3 Ty. FUNCTION
Name /SAPAPO/OM_SIMSESSION_GET_ALL
IV_GET_TESTGUIDS
X
0
0
5
8
ET_ACTIVE_SIMSESSION
Table IT_9[0x44]
\FUNCTION=/SAPAPO/OM_SIMSESSION_SELECT\DATA=LT_SIMSESSION
Table reference: 2
TABH+ 0(20) = 0000000000000000000000000000000000000000
TABH+ 20(20) = 0000000200000009000000000000002CFFFFFFFF
TABH+ 40(16) = 04000021000026C00010249401800000
store = 0x0000000000000000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 2 (0x00000002)
label = 9 (0x00000009)
fill = 0 (0x00000000)
leng = 44 (0x0000002C)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000192
occu = 16 (0x00000010)
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
ET_RC
Table[initial]
ET_SIMSESSION
Table[initial]
OM_LC_NAME
LCA
000000000000000000000000000000
000000000000000000000000000000
444222222222222222222222222222
C31000000000000000000000000000
GC_OM_SYSUBRC
-16842752
F
E
SY-SUBRC
0
0000
0000
%_SPACE
0
0
2
0
%_VIASELSCR
0
4
OM_LC_APPL_NAME
000000000000000000000000000000
000000000000000000000000000000
222222222222222222222222222222
000000000000000000000000000000
SPACE
0
0
2
0
LS_GEN_COM_PARAMS
DDIC # /SAPAPO/OM_DELETE_OLD_SIMS
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222444422222222222222222222222222222222202254545424454444545444554452222222
0000000000000000000000449300000000000000000000000000000000000F31010FFFDF45C545FFC4F39D30000000
LV_RC
00
00
00
00
GC_OM_SPP_FORECAST_EXT
K
4
B
GC_IMMEDIATE_TRANSFER
65537
0
0
GC_RESOURCE_MULTI
16909060
0
1
GV_SIMSESSION_TYPE
0
0
2
0
OM_MEASURE_PERFORMANCE
0
0
2
0
GC_OM_OBJECT_OUTPUT_NODE
454827294
1
B
OM_AS_KEY
000000000000000000000000000000
000000000000000000000000000000
222222222222222222222222222222
000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
No. 2 Ty. FUNCTION
Name /SAPAPO/OM_SIMSESSION_SELECT
IV_MIN_AGE_IN_HOURS
1
0000
0001
IV_SAVED_INCLUSIVE
0
0
2
0
ET_OMS_VERSION
Table[initial]
ET_SIMSESSION_DELTA
Table[initial]
SCREEN
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GC_OM_RPM_PORD_DEL
2004
000D
0074
GC_OM_OBJECT_UNKNOWN
66051
0
0
GC_OM_OBJECT_ORDER
16909060
0
1
GS_OMS_VERSION
00000000 ########
000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000C
222222222222222222222233333333222222222222222222222200000000
000000000000000000000000000000000000000000000000000000000000
GC_MINTIME
09011000
1700002C
GT_OMS_VERSION
Table[initial]
GC_APPLICATION_BLRG
235868177
0
E
GC_OM_OBJECT_MODE
50595078
0
3
GC_TRUE
X
0
0
5
8
RSJOBINFO
00000000000000 ##
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
GC_OM_OBJECT_RESOURCE
67438087
0
4
LT_SIMSESSION
Table IT_9[0x44]
GC_APPLICATION_CTPE
168496141
0
A
SY-REPID
/SAPAPO/SAPLOM_CORE
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2545454254544454454222222222222222222222
F31010FF310CFDF3F25000000000000000000000
GC_APPLICATION_MATP
185339150
0
B
SYST-REPID
/SAPAPO/SAPLOM_CORE
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2545454254544454454222222222222222222222
F31010FF310CFDF3F25000000000000000000000
GC_ATP_UPD_RPM
R
0
0
5
2
No. 1 Ty. EVENT
Name START-OF-SELECTION
VARI
###00000000000000 ############
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222200033333333333333222222000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST-REPID
/SAPAPO/OM_DELETE_OLD_SIMS
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2545454244544445454445544522222222222222
F31010FFFDF45C545FFC4F39D300000000000000
GC_OM_OBJECT_RPM_GENERIC
791687475
2
F
SY-SUBRC
0
0000
0000
%_VIASELSCR
0
4
SY-REPID
/SAPAPO/OM_DELETE_OLD_SIMS
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2545454244544445454445544522222222222222
F31010FFFDF45C545FFC4F39D300000000000000
SY-MSGID
00000000000000000000
00000000000000000000
22222222222222222222
00000000000000000000
GC_TRANSPORT
y
0
0
7
9
SPACE
0
0
2
0
SY-MSGNO
000
000
000
333
000
SY-MSGV1
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV2
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV3
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV4
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
GC_ITRUE
16777623
0
1
GC_FALSE
0
0
2
0
SYST
###############################################################################T########X ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000E000200
0000000000000000000000000000000000000006000000000000000000000000000000000000010500000001520000
000001010000010000000000010001000000000A00000000000000000000000000000000000006040000000080000C
GC_IFALSE
104192
0
0
GT_OMS_VERSION
Table[initial]
GC_MINTIME
09011000
1700002C
GT_SIMS_DELTA
Table[initial]
SY-XFORM
%_INIT_PBO_FIRST
000000000000000000000000000000
000000000000000000000000000000
254445554454455522222222222222
5F9E94F02FF6923400000000000000
%_DUMMY$$
0000
0000
2222
0000
SCREEN
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Internal notes
The termination was triggered in function "DsqlErrorHandler"
of the SAP kernel, in line 2062 of the module
"//bas/700_REL/src/krn/runt/abexsql.c#2".
The internal operation just processed is "DSQL".
Internal mode was started at 20080701092008.
Internal call code.........: "[DBDS/NEW DSQL]"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit = unlimited
=> Stack limit = unlimited
=> Core limit = 4294965248
=> File size limit = unlimited
=> Heap address = 0x0x1152ede20
=> Stack address = 0xfffffffffff84a0
=> Stack low = 0xfffffffffff84a0
=> Stack high = 0xffffffffffff7a0
=> Stack Trace:
AixStack() at 0x1000c7d94
CTrcStack2() at 0x1000c7e8c
rabax_CStackSave__Fv() at 0x1000b2d70
ab_rabax() at 0x1000af728
ab_dbdserr__FiPCUsT1T2P9DS_HEADERT2T1Pv() at 0x10057efbc
DsqlErrorHandler__Fi() at 0x10135b8e8
ExecuteCall__Fv() at 0x10135b454
ab_jdsql__Fv() at 0x101356b40
ab_extri__Fv() at 0x10040d93c
ab_xevent__FPCUs() at 0x100a9d170
ab_trigg__Fv() at 0x100a9ce5c
ab_run() at 0x1014bee48
N_ab_run() at 0x100d5bca8
dynpmcal() at 0x100d5aa74
dynppai0() at 0x100d58a08
dynprctl() at 0x100d6047c
dynpen00() at 0x100d52364
Thdynpen00() at 0x1000e2410
TskhLoop() at 0x1000e4254
ThStart() at 0x1000fe324
DpMain() at 0x10156c770
nlsui_main() at 0x101a99998
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
/SAPAPO/OM_DELETE_OLD_SIMS
0
28.09.2006
17:13:54
115712
E
1
Prg
SAPMSSY0
1
07.01.2008
17:16:23
92160
E
2
Prg
SAPMSSYD
1
27.09.2006
18:38:20
21504
E
3
Prg
SAPFSYSCALLS
1
03.12.2004
17:45:45
8192
E
4
Prg
RSDBRUNT
0
07.01.2008
17:27:13
254976
E
5
Typ
RSSCR
0
12.10.1999
15:50:05
5120
6
Prg
RSDBSPBL
0
22.02.2005
08:58:45
72704
E
7
Prg
SAPDB__S
0
03.12.2004
17:45:45
19456
E
8
Prg
RSDBSPMC
0
27.09.2006
18:23:16
79872
E
9
Typ
DDSHDESCR
0
28.11.1997
16:26:30
4096
10
Typ
SPPARAMS
0
07.03.1997
14:48:48
2048
11
Prg
SAPLSABE
11
03.12.2004
17:45:46
13312
E
12
Prg
SAPLSECU
12
07.01.2008
17:09:46
87040
E
13
Typ
RSSUBINFO
0
25.02.2000
15:47:23
3072
14
Prg
SAPLSTUP
14
07.01.2008
17:08:20
74752
E
15
Prg
SAPLCNDP
15
13.12.2007
16:41:21
195584
E
16
Prg
SAPLSCNT
16
22.02.2005
08:58:56
30720
E
17
Prg
SAPSHDTV
16
31.01.2005
15:41:11
33792
E
18
Prg
SAPFGUICNTL
1
22.02.2005
08:58:14
24576
E
19
Prg
SAPLOLEA
19
12.12.2007
14:16:36
96256
E
20
Prg
SAPLSGUI
20
07.01.2008
17:16:23
84992
E
21
Prg
SAPLSTTM
21
28.07.2005
11:12:25
69632
E
22
Prg
SAPLSBDC
22
07.01.2008
17:09:02
44032
E
23
Prg
SAPLSFES
23
07.01.2008
17:27:14
260096
E
24
Prg
SAPLTHFB
24
07.01.2008
17:16:23
394240
E
25
Typ
WPINFO
0
08.02.1999
14:18:32
6144
26
Prg
SAPLURFC
26
07.01.2008
17:13:39
22528
E
27
Prg
SAPLSPLUGIN
27
03.12.2004
17:45:46
8192
E
28
Typ
SWCBCONT
0
07.10.1997
12:13:50
3072
29
Typ
OLE_VERBS
0
09.02.1995
13:23:37
2048
30
Typ
OLE_PA
0
13.01.1995
11:06:59
2048
31
Prg
/1BCDWBEN/SAPL/SAPAPO/EN0001
31
08.06.2001
20:33:24
233472
E
32
Prg
SAPLSENA
32
12.12.2007
14:18:37
33792
E
33
Prg
/SAPAPO/SAPLOM_CORE
33
28.07.2005
16:02:32
502784
E
34
Prg
SAPLSAL2
34
07.01.2008
17:15:35
81920
E
35
Typ
/SAPAPO/OM_OMS_VERSIONS_STR
0
16.02.2006
18:01:55
3072
36
Prg
CL_ABAP_CHAR_UTILITIES========CP
36
28.07.2005
11:12:24
13312
E
37
Prg
CX_SY_NATIVE_SQL_ERROR========CP
37
12.12.2007
12:39:14
13312
E
38
Typ
SCX_SRCPOS
0
08.07.2004
09:59:00
2048
39
Prg
CX_SY_SQL_ERROR===============CP
39
28.07.2005
11:12:24
10240
E
40
Prg
CX_DYNAMIC_CHECK==============CP
40
28.07.2005
11:12:24
10240
E
41
Prg
CX_ROOT=======================CP
41
12.12.2007
17:18:15
11264
E
42
Prg
CX_NO_CHECK===================CP
42
28.07.2005
11:12:24
10240
E
43
Prg
CX_SY_NO_HANDLER==============CP
43
28.07.2005
11:12:24
10240
E
44
Prg
%_CSYDES
0
22.02.2005
08:58:46
8192
E
45
Prg
%_CSYDB0
0
22.02.2005
08:58:45
36864
E
46
Typ
RSVAMEMKEY
0
16.12.1996
19:31:50
2048
47
Prg
%_CRSDS
0
22.02.2005
08:58:21
10240
E
48
Prg
%_CSLIS
12
17.02.2006
08:58:39
89088
E
49
Typ
DTC_S_LAYO
0
08.06.2001
15:59:56
6144
50
Typ
CAT_SVARS
0
19.05.2004
16:00:08
3072
51
Typ
SYST
0
03.12.2004
17:45:35
31744
52
Typ
RSJOBINFO
0
09.02.1995
13:25:17
3072
53
Typ
VARI
0
16.12.1996
19:38:11
6144
Directory of Application Tables
Name Date Time Lngth
Val.
Program /SAPAPO/OM_DELETE_OLD_SIMS
SYST 03.12.2004 17:45:35 00004612
\0\0\0\0\0\x0001\0\x0001\0\0\0\0\0\x0001\0\0\0\0\0\0\0\0\0
VARI . . : : 00003052
Program /SAPAPO/SAPLOM_CORE
RSJOBINFO . . : : 00000164As per note 1619720, drop following two tables and then validate by running t-code lca03.
drop table APPSYSNAME
drop table APPSYSPARAM
dbmcli -d LCSID -n hostname -u superdba,sdbapassword -uSQL SAPSID,password
dbmcli on hostname : SID>sql_execute drop table APPSYSPARAM
OK -
Portal Runtime Error : An exception occurred while processing a request
Hello friends,
After upgradation of my portal to the following patch level, SAP J2EE 6.20:
<b>Portal Version :</b> EP 6 SP 2 patch 29 hotfix 0
<b>Content Mgmt and Collaboration version</b> : 6 SP2 patch 5
i faced many performance related issues. Portal seems to be <b>very slow</b>. After logging in, most of the time I get 2 errors:
<b>Either</b>
<b>1></b> Iview remains blank.
<b>Or
2></b> Portal Runtime Error : An exception occurred while processing a request. Portal Runtime exception occured. Please check the System Log.
But when I refresh that particular iview, it works fine.
I went through the portal.log file (/usr/sap/PEP6/j2ee/j2ee_00/cluster/server/managers/log/portal/logs). And found <b>the root cause of most of the exceptions as "com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found."</b>Aug 18, 2005 6:07:42 PM # PRT-Async 2 Fatal Exception ID:06:07_18/08/05_0669
com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/ACCContent/ACCContent.Roles/Company/R.Employee/W.MyWork/P.MyWork.DesktopTools/I.Contacts
Component class : com.sapportals.portal.prt.pom.RootComponentNode
User : tempuser
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:853)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:311)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
at java.lang.Thread.run(Thread.java:479)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: PortalComponentException
at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:153)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
at java.lang.Thread.run(Thread.java:479)
Caused by: com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found.
at com.inqmy.services.servlets_jsp.server.ServletContextFacade.loadServletLocal(ServletContextFacade.java:3660)
at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:81)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:275)
at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.include(RequestDispatcherImpl.java:384)
at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:144)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
at java.lang.Thread.run(Thread.java:479)
<b>Help needed.(</b>as i am helpless now.)
Regards,
NilzAnthony,
I had check it. It was correct. But the thing when I saw in the component Inspector of portal, my iview did not appear.
I created like this
project-> rightclick-> export-> par ->selecting project-> givint protal password-> and finish.
The NW didn't give any error, but the par file didn't appear in the portal componet Inspect.
but the par file is created in the NW studio Navigation bar.
Let me know any help regarding this
thanks
venkat -
Dear All,
I am getting below error in PRD system. We are using ecc6, oracle 10g and windows 2003. The error coming after we have restarted the server. Please suggest how to solve the issues.
SM21 log
09:30:21 DIA 000 000 DDIC AB 0 Run-time error "BCD_FIELD_OVERFLOW" occurred
09:30:21 DIA 000 000 DDIC AB 1 > Short dump "100913 093034 nodeA " generated
ST22
Runtime Errors BCD_FIELD_OVERFLOW
Exception CX_SY_CONVERSION_OVERFLOW
Date and Time 13.09.2010 00:30:19
Short text
A calculation field is defined too small.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_SWNC_RECORD================CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not
caught in
procedure "DO_TRANSFORMATIONS" "(METHOD)", 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:
A value generated during processing is too large for the
field "ME->MAIN_RECORD_STR+1020(7)" of the program
"CL_SWNC_RECORD================CP".
Regards,
KumarDear Friends,
We even got same dump "BCD_FIELD_OVERFLOW" just after system restart. But error was slightly different. Please find below error details and solution:
Error Details:
The current ABAP program "CL_SWNC_RECORD================CP" had to be terminated because it has come across a statement that unfortunately cannot be executed.
Error Analysis:
An exception occurred that is explained in detail below. This exception cannot be caught in the context of the current statement.
The reason for the exception is: A value generated during processing is too large for the field " " of the program "CL_SWNC_RECORD================CP".
"BCD_FIELD_OVERFLOW" " "
"CL_SWNC_RECORD================CP" or "CL_SWNC_RECORD================CM002"
"CALCULATE_PROCESSING_TIME"
SOLUTION:
An OSS Note:
Note 1103295 - BCD_FIELD_OVERFLOW in CALCULATE_PROCESSING_TIME (It solves the problem) -
Portal Runtime error - An exception occured : when accessing the SRM Portal
Dear Consultants,
We are logging onto the SRM Portal using url link. SAP Netweaver 7.0
But when we are trying to access any tabs in the Navigation frame of the portal it is throwing an error.
Error - Portal Runtime error
An exception has occured while processing your request.
Can you please let me know how can I find the correct reason for the error.
regards
ArindamHi Arindam,
Pls check Default Trace log in the NWA tool, path would be NWA --> Monitoring --> Logs and Traces --> Select Default Trace.
Find the log messages with the Exception ID found on your Portal Runtime error. These logs would specify the exact cause of error.
Thanks,
Swapna Priya. -
Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised
Hi All,
I am facing a runtime error, while using transaction DSWP --> Set-up System Monitoring --> Copy Customizing -->
At that time we are getting "Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised
===========================================
Runtime Errors RAISE_EXCEPTION
Date and Time 25.07.2008 08:31:11
Short text
Exception condition "METADATA_MISSING" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
A RAISE statement in the program "SAPLDSVAS_SERV" raised the exception
condition "METADATA_MISSING".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
How to correct 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:
"RAISE_EXCEPTION" " "
"SAPLDSVAS_SERV" or "LDSVAS_SERVC7I"
"MAP_DSVAS_TT_DATA_TO_TT_25"
or
"SAPLDSVAS_SERV" "METADATA_MISSING"
or
"RDSMOP_MAIN " "METADATA_MISSING"
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.
System environment
SAP-Release 700
Application server... "terra"
Network address...... "172.16.1.198"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 2
Shortdump setting.... "full"
Database server... "TERRA"
Database type..... "ORACLE"
Database name..... "DSM"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Oct 23 2007 01:07:18"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.1.0) "
Patch level. 133
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
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.... 8176
EM...... 37628064
Heap.... 0
Page.... 65536
MM Used. 31785376
| MM Free. 1656912
=============================================
Configuration:
OS :Windows 2003 server.
Solution Manager 7.0 SP15
Oracle 10.2
RAM - 2 GB
Its bit urgent, Please help out us.
Thanks in advance.
Best Regards,
PratyushaHi
Check the SP level for ABAP and Basis. Download the latest SP level from SWDC and apply it on the system
This error is related to ABAP program.
Currently the latest available patch level is 16. Please download both ABAP and BASIS SP 16 and apply them on the system. -
Hi,
Could you please tell me "What is difference between Runtime Error and Exceptions"
Thanks & Regards,
Krushna BiswalIf you would like to handle and navigate based on the exception type, this code would help you. btw I'm not familiar with portlet though.
http://sourceforge.net/projects/optionzero
http://sourceforge.net/forum/forum.php?forum_id=666191
You can declare exception type and navigation in faces-config.xml in declarative manner like Struts global exception notion.
Please let me know it's useful or not.
thanks, -
Runtime error: DBIF_RSQL_SQL_ERROR -- when deleting infocube in BWPRD
Dear readers,
When i try to delete the infocube 0IC_C03 from bwprd it gives this error --> Runtime error: DBIF_RSQL_SQL_ERROR ...
Kindly advise.hii
Check the authorization of deletion of cube at BWP
Also chk whether is there any other info provider which is related to 0IC_C03 or used as a source for other Info provider or multi provider.
Check for data availability before deleting Cube.If yes, then delete data first.
Thanks
Neha -
Hi All,
While using leave request service we are getting following dump in abap code , please advice
Runtime Errors DATA_LENGTH_0
Exception CX_SY_RANGE_OUT_OF_BOUNDS
Date and Time 13.01.2012 10:17:48
Invalid partial field access: Length 0
What happened?
Error in the ABAP Application Program
The current ABAP program "ZCL_PT_GEN_REQ================CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_RANGE_OUT_OF_BOUNDS', was not
caught in
procedure "IF_EX_PT_GEN_REQ~SEARCH_FOR_NEXT_PROCESSOR" "(METHOD)", 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:
In the executed program "ZCL_PT_GEN_REQ================CP", the system
attempted to access the field
"IM_SEARCHSTRING" using the length 0.
However, a partial field access with the length specification 0 is not
allowed.
How to correct the error
Use a positive length specification if a part of the field "IM_SEARCHSTRING" is
to be
accessed.
If the error occurred in your own ABAP program or in an SAP
program you modified, try to remove 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:
"DATA_LENGTH_0" "CX_SY_RANGE_OUT_OF_BOUNDS"
"ZCL_PT_GEN_REQ================CP" or "ZCL_PT_GEN_REQ================CM002"
"IF_EX_PT_GEN_REQ~SEARCH_FOR_NEXT_PROCESSOR"
Dump At source code shows as following
LOOP AT ex_persdata_tab INTO wa_ex_perdata.
w_str3 = wa_ex_perdata-user.
IF w_str3 CO im_searchstring.
w_len2 = sy-fdpos.
w_len1 = sy-fdpos + 1.
**Get First name
w_str2 = im_searchstring+w_len1.
**Get last name
---->>> w_str1 = im_searchstring(w_len2). (Point of dump) (Data type String = char25)
IF w_str2 EQ wa_ex_perdata-name.
APPEND wa_ex_perdata TO lt_ex_perdata.
EXIT.
ENDIF.
CLEAR:w_str2,w_str1,w_len2,w_len1.
ENDIF.
ENDLOOP.
CLEAR:wa_ex_perdata.attempted to access the field
"IM_SEARCHSTRING" using the length 0.
However, a partial field access with the length specification 0 is not
allowed.
that w_len2 of yours is having a value 0. you cant access a field with length 0. thats the error -
Hi,
I have tried several times to create a DVD of a movie with several Scene (w/Stop) Markers only to receive 'runtime error: Unknown exception' with 99% completion.
I'm using Adobe Premiere Element 11 ver 11.0 (20120901.B261.425551).
I'm running Windows 7 Ultimate w/SP1 on a Dell XPS M1530 w/4GB Memory
I have created DVDs in the past with little or no problems.
Would appreciate any help with my problem.
Thanks...Harry
Thanks for the additional information.
Typically, if you are doing a multi movie Timeline and you want the viewer to be able to navigate to a specific movie followed by return to main menu, then:
Main Menu Marker at beginning of movie 1 and Stop Marker at end of movie 1....then gap of at least 12 frames...Main Menu Marker at beginning of movie 2 and Stop Marker at end of movie 2....and so on. But for the last, remember no Stop Marker at the end of that last Movie on the Timeline.
With those 25 .mts video clips, are you sure that you want or need all those return to main menu possibilities.... a scene marker at the beginning of each and a stop marker at the end of each for a return to menu after each of the 25 video clips? Especially if these are small video clips.
Large project...
Keep in mind that the DVD disc 4.7 GB/120 minutes is in reality 4.3 GB capacity. So as you can tell my the program's lowering of the Bitrate (8.00 to 7.97 Mbps), the program is trying to make the fit by lowering the bitrate. Depending on how your troubleshooting goes, you may want to start thinking about DVD Double Layer Disc (8.5 GB/240 min) if your project gets much larger. In the case of the DVD double layer, 8.5 GB is in reality 7.3 GB. Typically, lower the Bitrate, the lesser is the Quality of the end product. So you do not want to force the program to lower the Bitrate to low to make the fit.
As for the Timeline - + slider to which I referred...
In the above screenshot, please note in the right side of the Premiere Elements 11 Timeline (Expert view)...from left to right at that location,
the Render Button
the icon named "Fit to Visible Timeline
the icon named Zoom Out ( - ) which is related to the slider to its right
the icon named Zoom In ( +) which is related to the slider to its left
That slider is moved by either of those icons or by moving the circular button of the slider with the mouse curser.
We will be watching for further developments.
Thanks.
ATR -
I'm getting "runtime error: unknown exception" when burning DVDs on PE12
I'm getting "runtime error: unknown exception" when burning DVDs on PE12
Some of this may be for Premiere Pro, but SHOULD also help with Premiere Elements
http://helpx.adobe.com/x-productkb/global/troubleshoot-c-runtime-errors-products.html
Also http://www.microsoft.com/en-us/download/details.aspx?id=14632 for a Microsoft download
Also search http://search.microsoft.com/search.aspx?mkt=en-US&setlang=en-US for Microsoft help articles
Set your Premiere Elements DVD output to a folder on your hard drive and then use the FREE Imgburn to burn the folder to disc for DVD... Premiere Elements does NOT burn to a folder for BluRay (send the author a PayPal donation if you like his program)
Read http://forums.adobe.com/thread/1322583 for notes on installing Imgburn WITHOUT any toolbar add-ons... Set Imgburn to use the slowest burn speed your drive and media will use... I set my burn speed to 1x and let Imgburn adjust to the actual minimum
Maybe you are looking for
-
Server error while communicating to BI server
Hi, There is a run time error while executing the Query in Bex Analyser while the same query is working fine in Portal.. *Cant paste the image here, but the error states -: AN ERROR OCCURED WHILE COMMUNICATING WITH THE BI SERVER As a result of this e
-
Unsuccessful payment wizard run
Hello All, Please help. I have just done a payment wizard run. In the recommendation report stage, 84 cheques/lines had been ticked to pay, but it has only successfully executed 4 cheques. How can I find out why? Thank you very much Regards, Yang Edi
-
I am new to Pages. When I type, why doesn't the software capitalise the first letter of each sentence?
-
Remove Leading zeros from column
How can I remove leading zeros from a column? The data looks like *00-04-071* The output should display 4071
-
KM Document Iview and Horizontal scroll bar
I have a simple KM Doc Iview that displays a image. But I get this annoying hosrizontal scrollbar, it should rather display the whole image without the scrollbar. Have anybody experienced this? Any workarounds please? Thanks!