ABAP dump DBIF_DSQL2_SQL_ERROR in report /SAPAPO/OM_LC_UPGRADE_70 during up
We are in the process of Upgrade of SCM APO system from version 5.0 to 7.0.
Also we are upgrading livecache to version 7.7.
While running report /SAPAPO/OM_LC_UPGRADE_70 in se38 to perform the steps under section 3, we are getting following ABAP dump:
DBIF_DSQL2_SQL_ERROR
Please find ataached the entire abap dump for your reference. We have successfully executed sections A & B of report /SAPAPO/OM_LC_UPGRADE_70 at the appropriate time during the upgrade.
Kindly look into the issue and revert ASAP.
Thanks & Regards,
Virendra
+919619498381
Hello Virendra , Hello Pavan,
the SAP MaxDB/liveCache is forum and NOT hotline of the support, it's NOT ASAP support.
We shared the knowledge or expierence on the posted in the forum questions/issues when we have time voluntarily.
1.
As you are SAP customer =>
I recommend to create the SAP message with the high priority and esculate it if it's ASAP case.
Then your phone number will be used by SAP support to call you and help with issue.
2.
Please find ataached the entire abap dump for your reference. We have successfully executed sections A & B of report /SAPAPO/OM_LC_UPGRADE_70 at the appropriate time during the upgrade."
This part is looking that the SAP message was already created, the ABAP dump was already attached to the message and
now the SAP message's issue copied to this forum with hope to get the solution.
Am I correct?
Then first check what database error you got in ABAP dump & post this info.
Regards, Natalia Khlopina
Similar Messages
-
Hi All,
We are facing an issue and want to check if you have seen it in past and can help us in resolving it. Any input will be greatly appreciated.
Issue:
While executing product heuristic on few product/location combinations in product view, we encounter native SQL ABAP dump “DBIF_DSQL2_SQL_ERROR” on
procedure “APS_ORDER_CHANGE”.
We were debugging for one particular product/location combination, this combination has 2 planned orders, and the Internal order number of these planned orders are
given as input to this procedure “APS_ORDER_CHANGE”. These 2 internal order numbers are the only inputs given to this procedure.
When we try to delete those planned orders we again encounter same ABAP dump. There are many product/location having the same issue.
We also checked variable duration maintained on the PPM of this product/location, and was fine.
For more deatils : Please check the attached document of downloaded ABAP Dump.
Thanks and Regards,
Pritesh JainHi Pritesh.
What liveCache version/build/patch are you on? What is the database error text shown in this dump?
If it is exactly the one below
Database error text........: "POS(1) Work rolled back: tExcept 30730 in
APS_ORDER_CHAN"
You can try running report SLCA_EMERGENCY_SWITCH, then turning off the option "Verify that all input table records have been read" and saving the results. If that solves the issue, you can use this as a workaround until the next time you upgrade your liveCache build.
To get a clear root cause, you may need to create an OSS incident under BC-DB-LCA component providing a reproducible example.
Regards,
Tiago -
Regarding ABAP dump in ALV reports
hi all,
we are migrating the report programs from 4.7 to ECC...some of the reports am getting ABAP dump like this.....INCORRECT VALUE IN THE DYNAMIC TABLE.....if i comment the sort portion in grid display or list display function module..output is coming please guided me in this...we are not upgrading..just migrating all the reports to ECC server..hi ,
Error in the ABAP Application Program
The current ABAP program "SAPLKKBL" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYN_TABLE_ILL_COMP_VAL',
not caught in
procedure "FB_OUTTAB_SORT2" "(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 table "\FUNCTION-POOL=KKBL\FORM=FB_OUTTAB_SORT2\DATA=LT_SORTBYTAB" con
an incorrect value in row 1 in the
component with the name "NAME".
In this particular case, the condition mentioned below was violated:
(" ") The addition AS TEXT can only be used for character-type fields.
IF RT_SORT-DOWN = 'X'.
ls_sortbytab-descending = 'X'.
ENDIF.
append ls_sortbytab to lt_sortbytab.
ENDLOOP.
if RFLG_STABLE eq 'X'.
sort rt_outtab stable by (lt_sortbytab).*******here dump is coming
else.
sort rt_outtab by (lt_sortbytab).
endif. -
We are upgrading from SCM 5.0 to SCM 7.0. We have tried to run step C3. Load master data but it keeps displaying a red light with "Jobs for creating master data terminated". Messages in the job log are as follows:
Message text Message class Message no. Message type
Job started 00 516 S
Step 001 started (program /SAPAPO/RESOURCES_LC_CREATE,
variant &0000000000011, user ID #######) 00 550 S
Prepare data 00 001 S
Create Resources 00 001 S
Create Resources with setup matrix 00 001 S
Wrap Up 00 001 S
Error creating resources in liveCache 00 001 E
Job cancelled after system exception ERROR_MESSAGE 00 564 A
There are no dumps in st22 or messages in the system log sm21. We have tried numeorus searches on SDN, Marketplace, and Google and have found nothing.
Any suggestions or help would be greatly appreciated.Hello George Woods,
1. For the reported error itu2019s not good idea to search the solution in SDN.
2. Please check, that the notes recommended in SAP note 1292734 were applied
before you run C section steps.
3. I recommend you to create the SAP ticket to the component u201CSCM-APO-MD-REu201D.
Thank you and best regards, Natalia Khlopina -
ABAP dump when running an ALV report in a portal
Hi,
I have an ABAP report created in SAP R/3 4.7. Am using the ALV function module REUSE_ALV_GRID_DISPLAY to display the output. The programs runs correctly when run in R/3 using the SAP GUI.
When the report is run in the portal, I get a runtime error 'MESSAGE_TYPE_X'.
Please let me know if anybody has faced such issues.
I checked the OSS note 702732 which talks about increasing the threshold value of the start parameter. But this is not agreed by the BASIS team.
Thanks,
Best regards,
Ajith
The ST22 error log is as follows:
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
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
Short text of error message:
Data volume (84.550.400 bytes) is too large. (abap/alvgrid/size_nodod_mb
Technical information about the message:
Diagnosis
You tried to send a data record to the front-end that contains
84.550.400 bytes. However, the data volume is restricted to
52.428.800 bytes.
System Response
The running application program was terminated with a runtime
error.
Procedure
Restrict the data selection if possible or contact your system
administrator.
Procedure for System Administration
You can set the maximum size of these data volumes using the kernel
parameter 'abap/alvgrid/size_nodod_mb' (in megabytes).
Message classe...... "S>"
Number.............. 890
Variable 1.......... "84.550.400"
Variable 2.......... "52.428.800"
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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:
"MESSAGE_TYPE_X" C
"SAPLAWRT" or "LAWRTU22"
"ITS_CHECK_ALV_DATA_SIZE"
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.
Information on where terminated
The termination occurred in the ABAP program "SAPLAWRT" in
"ITS_CHECK_ALV_DATA_SIZE".
The main program was "Z_BW_RECON_INV_RPT ".
The termination occurred in line 25 of the source code of the (Include)
program "LAWRTU22"
of the source code of program "LAWRTU22" (when calling the editor 250).
Source code extract
000010 FUNCTION ITS_CHECK_ALV_DATA_SIZE.
000020 *"
000030 ""Lokale Schnittstelle:
000040 *" IMPORTING
000050 *" REFERENCE(DATA_TABLE) TYPE TABLE
000060 *"
000070
000080 data n type i.
000090 data currsize type i.
000100 statics maxsize type i.
000110 data par_value(56).
000120 if maxsize is initial.
000130 sy-subrc = 0.
000140 CALL 'C_SAPGPARAM' ID 'NAME' FIELD 'abap/alvgrid/size_nodod_MB'
000150 id 'VALUE' field par_value.
000160 if sy-subrc ne 0.
000170 maxsize = 52428800. " Default 50 MB
000180 else.
000190 maxsize = 1048576 * par_value.
000200 endif.
000210 endif.
000220 describe table data_table lines n.
000230 currsize = sy-tfill * sy-tleng.
000240 if currsize gt maxsize.
> message x890(s>) with currsize maxsize.
000260 endif.
000270 ENDFUNCTION.HI,
This is a Memory problem.
System is allocated with a Max Memory of 50 MB,(see the dump code, in the last it is hardcoded in the std code)
The data of your report is coming around 83 MB.
Restrict your selection criteria of the Object and run the same report and see. it will work.
Regards,
Anji -
Hello,
I'm working on issue where I have two users who are executing the same transaction but getting back different results. One users gets back the output of the report another gets back an abap run time errror.
The run time error for short text reads, " Time limit exceeded"
I thought this was due to missing authorization however I ruled this out when I tried running this report under my profile that has sap_all & sap_new and got an abap dump error indicating time limit exceeded.
The transaction i'm running is GR55, once there I choose the report group. Next screen i enter in the year and period. I using period 1 which is one month of data and I still get the dump. The user who can run this report goes up to 9 periods and gets an output every time.
I can run this same report in our Q/A without any issues. I pulled the dump in ST22 and from reading it appears the paremeter for rdisp/max_wprun_time is set to 1200 secs and when I run this report i'm exceeding 1200secs which triggers the dump.
This all make sense however I don't understand how one user doesn't run into the same issue and one does.GR55 is not performance optimized coding. It is only "best guess coding"...
Your production system might have more data (or even other config, if there are inconsistencies...).
Additionally, the load balancing is might be different (with the server instances having different instance profiles)?
If the user has the ability to schedule jobs with different priorities in PRD, then this can also have an effect.
I dont think this is security related (does not make sense, unless the ABAPers did something stupid...) so I take the liberty of moving it to the NW Admin forum...
Cheers,
Julius -
ABAP dump during workstatus chaning in SAP BPC 7.5
Hi, Experts
We are working with SAP BPC 7.5 Ramp-up version. We faced a problem - during changing workstatus the system generates ABAP Dump.
We checked ST22 with ABAP Dumps. It contains the following:
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_UJW_WORK_STATUS_DAO========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
ABAP errors are created in the following code:
FIELD-SYMBOLS:
<fs_line> TYPE ANY.
CREATE DATA lr_line TYPE (i_tabname).
ASSIGN lr_line->* to <fs_line>.
l_where = 'APPSET = i_appset'. "#EC NOTEXT
LOOP AT it_dim_mem INTO ls_dim_mem.
CONCATENATE
l_where ' AND ' ls_dim_mem-dimension ' = ''' ls_dim_mem-member ''''
INTO l_where RESPECTING BLANKS.
ENDLOOP.
*SELECT SINGLE * INTO CORRESPONDING FIELDS OF es_lock_info FROM (i_tabname) WHERE (l_where).*
* fill lock information
CLEAR ls_ujw_statcode.
CALL METHOD me->read_status_code(
EXPORTING i_appset = i_appset
i_status = es_lock_info-status
i_spras = 'E'
IMPORTING es_ujw_statcode = ls_ujw_statcode ).
ABAP dump says that in "SELECT SINGLE * INTO CORRESPONDING FIELDS OF es_lock_info FROM (i_tabname) WHERE (l_where).*" exist a dynamically specified column name which is unknown.
Does somebody have the same problems?
Regards,
PavelHi Pavel,
This is obviously a bug and it looks like from the code block you copied into the forum that there is an issue with the actual select statements dynamic where clause. I haven't specifically seen this bug but I recommend you do an SAP Note search on the following component EPM-BPC-NW-WS (for work status) in your search criteria put the class name that you found in the dump. This should help you find whether or not a correction has been created (i.e. an SAP note) that solves your issue.
Cheers, Scott -
ABAP Dump during GRN posting with excise
Hi Gurus,
We are using TAXINN procedure. We have created a taxcode V2 and have done all assigenments & condition recordes. We have created a PO with V2 tax code . Now while doing the GRN in MIGO, after excecise capture , its throwing runtime error (ABAP Dump) during Posting. Message is "Tax code V0 does not exist in Taxinn" . But we have not maintained V0 in PO. We have used V2.
Answers will be rewarded. Thanks in advance..
Regards
BasabCheck for your condition record
may be in condition record for plant , material combination you have mantain there V0 tax code. -
Regarding ABAP dump during time ticket confirmation.
Hi PP Gurus,
I'm getting an ABAP dump while doing time ticket confirmation for a process order using COR6N. The dump is coming only for one plant and all the plants are working fine.
The reason for dump is
The current application program detected a situation which really should not occur. Therefore, a termination with a short dump was triggered on purpose by the key word MESSAGE (type X).
I tried to analyze the dump and got OSS# 385830. But this note only talking about the conversion of message from A to X type. What should be the reason (configuration/product error) behind that?
If anybody came across the same, please comment on this
Thanks & Regards,
Abu ArbabHi,
Since this dump is happening only for a particular plant, compare the config set of this plant with the other plant which is working fine, you should be able to resolve it.
Alternatively, ask your abaper to analyze the dump in ST22 & he / she should be able to let you know the exact reason why the dump is occurring.
Regards,
Vivek -
Hello Friends,
After upgradation Solman 7.01 to 7.1, During EWA Alert management configuration in step 3 --> Check Software component level phase, we receiving below error.
Also Syntax error in program "/SSF/SLIB " Dump is occurring inST22. Please find the Abap dump details attachment.
Please help me to resolve this issue.
Regards,
Farkath C/SSF/SLIB comes from SP A/PI, if there were issues in old version then they should have been reported.
Upgrading may be a solution.
However, there references of ADD_CCDB_ABAP_EXTRACTOR
Execute RFC |
|>>>>>| CASE LS_OPT-RFC_CALLTYPE. |
| 1640| WHEN 'SYNC'. |
| 1641| CALL FUNCTION '/SSF/CALL_SUBROUTINE_RFC' |
| 1642| DESTINATION LS_OPT-DESTINATION
That's why I am asking for the latest dump after the run of RTCCTOOL.
Regards -
Hi Guys,
We are getting ABAP Dumps in our systems very frequently. We are currently using 4.6C (DB2, AIX). We are gettting the dumps in many programs, is this because of some error in application. We currently have kernel patch level 2307.
We have already increased the value of "rdisp/max_wprun_time" from 900 to 2500.
I was suggested by SAP to add a new parameter "rdisp/hold_keeps_time_slice"
which we dont have in our systems. Can anybody pls suggest in this case.
I am attaching the dump:
ABAP runtime errors TIME_OUT
Occurred on 10/17/2007 at 20:57:15
Time limit exceeded.
What happened?
The program "SAPLBDMON " has exceeded the maximum permitted runtime
and has therefore been terminated.
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
After a certain time, the program terminates to free the work process
for other users who are waiting.
This is to stop work processes being blocked for too long by
- Endless loops (DO, WHILE, ...),
- Database acceses with large result sets,
- Database accesses without an apporpriate index (full table scan)
- database accesses producing an excessively large result set,
The maximum runtime of a program is set by the profile parameter
"rdisp/max_wprun_time".
The current setting is 2500 seconds. After this, the system gives the
program a second chance. During the first half (>= 2500 seconds), a
call that is blocking the work process (such as a long-running SQL
statement) can occur. While the statement is being processed, the
database layer will not allow it to be interrupted. However, to
stop the program terminating immediately after the statement has been
successfully processed, the system gives it another 2500 seconds.
Hence the maximum runtime of a program is at least twice the value of
the system profile parameter "rdisp/max_wprun_time".
How to correct the error
Long-running programs should be started as background jobs. If
this is not possible, you can increase the value of the system
profile parameter "rdisp/max_wprun_time".
One or more of the following may also be useful:
following measures:
- Endless loops: Correct in program;
- Database access with large result set:
Use "SELECT * INTO itab" instead of "SELECT ... ENDSELECT";
- Database access without suitable index: Check the index generation.
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"TIME_OUT"
"SAPLBDMON " or "LBDMONU15 "
"ALE_CCMS_EVALUATE_GRP"
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.
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.
Thank you.
Irshad Mohammedhi
use function module progress_indicator. it resets the run time value.
use this where ever extraction of data is more were program needs much time, just call this function module it works.
check this code,
This program uploads material number from excel sheet and does
******modifications to material number if required by the user
******and updates the table zmatnr with new material against the old material number
REPORT zmat_no message-id zebg.
TYPE-POOLS truxs.
TABLES:zmatnr.
DATA : itab LIKE alsmex_tabline OCCURS 0 WITH HEADER LINE.
DATA row LIKE alsmex_tabline-row.
data : g_matnr like mara-matnr.
data : count type i.
data : itab_count type i.
data : gi_final like zmatnr occurs 0 with header line.
*data : begin of gi_final occurs 0,
mat_old like mara-matnr,
mat_new like mara-matnr,
end of gi_final.
***********************Selection Screen*************************
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
PARAMETER : pfname LIKE rlgrap-filename OBLIGATORY.
select-options : records for count.
SELECTION-SCREEN END OF BLOCK b1.
*********************At Selection Screen*************************
AT SELECTION-SCREEN ON VALUE-REQUEST FOR pfname.
PERFORM search.
START-OF-SELECTION.
perform process.
form process.
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
EXPORTING
filename = pfname
i_begin_col = 1
i_begin_row = 2
i_end_col = 12
i_end_row = 65000
TABLES
intern = itab
EXCEPTIONS
inconsistent_parameters = 1
upload_ole = 2
OTHERS = 3.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
describe table itab lines itab_count.
row = 1.
loop at itab.
if itab-row <> row.
append gi_final.
clear gi_final.
endif.
case itab-col.
when '1'.
CLEAR G_MATNR.
gi_final-OLD_MATNR = itab-value.
CONCATENATE 'NEW' gi_final-old_matnr INTO itab-value.
gi_final-new_MATNR = itab-value.
endcase.
row = itab-row.
endloop.
append gi_final.
clear gi_final.
CALL FUNCTION 'PROGRESS_INDICATOR'
EXPORTING
I_TEXT = 'File Has Been Successfully Uploaded from Workstation ' .
if not gi_final[] is initial.
if not records-low is initial .
if not records-high is initial.
records-high = records-high + 1.
DESCRIBE TABLE gi_final LINES count.
IF records-high < count.
DELETE gi_final FROM records-high TO count.
ENDIF.
IF records-low <> 1.
IF records-low <> 0.
DELETE gi_final FROM 1 TO records-low.
ENDIF.
ENDIF.
endif.
endif.
endif.
IF NOT GI_FINAL[] IS INITIAL.
CALL FUNCTION 'PROGRESS_INDICATOR'
EXPORTING
I_TEXT = 'Processing zmatnr table'
I_OUTPUT_IMMEDIATELY = 'X'.
if itab_count <> count.
message i000 with 'records are not matching'.
exit.
else.
modify zmatnr from table gi_final.
message i000 with 'data base table modified successfully'.
endif.
endif.
endform.
*& Form search
text
--> p1 text
<-- p2 text
FORM search .
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
EXPORTING
static = 'X'
CHANGING
file_name = pfname.
ENDFORM. " search
regards
siva -
Issue with /SAPAPO/OM_LC_UPGRADE_70 in SCM 7.0 prepare
Hi,
We are running an SCM upgrade from 5.1-> 7.0
We upgraded our dev system fine. We are now in QA and running the prepare at phase PREP_CNVCHECKS/REQ_APOUPG0.
Option # 3 of section A of /SAPAPO/OM_LC_UPGRADE_70 runs job name SYNC_LC_DB_DP, program /SAPAPO/OM_SYNC_LC_DB. Most planning versions run ok, but for ZDP01, this one has been running for over 30,000 seconds and it looks like it is not doing anything in liveCache or the SCM database.
Is there some way to determine what is going on with this job? We'd like to move on with the prepare...
Thanks,
MargaretHi Natalia,
thanks for your response.
1. We have opened message 35265
2. the job is running in sm37 start time 01-13-2011, 14:51:42
a. sm50 information shows program /SAPAPO/SAPLOM_SYNC in DB-PROC SAPTS_OBJECTS_GET_ALL
b. liveCache IO operations do not show any significant change since start of this job
c. There are liveCache SQL locks for the application server PID that is running the background job
521 10158214 us6qa1a02.na.cokecce.com row_share
521 10158214 us6qa1a02.na.cokecce.com row_share
521 10158214 us6qa1a02.na.cokecce.com tab_share
521 10158214 us6qa1a02.na.cokecce.com tab_share
521 10158214 us6qa1a02.na.cokecce.com tab_share
521 10158214 us6qa1a02.na.cokecce.com tab_share
521 10158214 us6qa1a02.na.cokecce.com tab_share
521 10158214 us6qa1a02.na.cokecce.com tab_share
521 10158214 us6qa1a02.na.cokecce.com tab_share
d There is a task in liveCache
521 10,158,214 us6qa1a02.na.cokecce.com share 00018AE98905 17,152,861 01-13-2011 14:51:42
e. The dec_w36 file is contains information just from the initial connection u2013 no errors
A Thu Jan 13 14:51:42 2011
A **GENER Trace switched off ***
M SosICreateNewAnchorArray: sos_search_anchor_semantics = 1
E Profile-Parameter: enque/deque_wait_answer = FALSE
E Profile-Parameter: enque/sync_dequeall = 0
B dbtran INFO (init_connection '<DEFAULT>' [DB2:700.08]):
B max_blocking_factor = 10, max_in_blocking_factor = 35,
B min_blocking_factor = 3, min_in_blocking_factor = 6,
B prefer_union_all = 1, prefer_join = 0,
B prefer_fix_blocking = 1, prefer_in_itab_opt = 1,
B convert AVG = 1, alias table FUPD = 0,
B escape_as_literal = 0, opt GE LE to BETWEEN = 0,
B select * =0x0b, character encoding =SBCS / <none>:-,
B use_hints = abap->1, dbif->0x3, upto->2147483647, rule_in->0,
B rule_fae->0, concat_fae->0, concat_fae_or->0
M SecAudit(RsauShmInit): WP attached to existing shared memory.
M SecAudit(RsauShmInit): addr of SCSA........... = 700000040000000
M SecAudit(RsauShmInit): addr of RSAUSHM........ = 700000040000450
M SecAudit(RsauShmInit): addr of RSAUSLOTINFO... = 700000040000488
M SecAudit(RsauShmInit): addr of RSAUSLOTS...... = 700000040000494
B create_con (con_name=LCA)
B Loading DB library '/usr/sap/QA1/SYS/exe/run/dbsdbslib.o' ...
B Library '/usr/sap/QA1/SYS/exe/run/dbsdbslib.o' loaded
B Version of '/usr/sap/QA1/SYS/exe/run/dbsdbslib.o' is "700.08", patchlevel (0.247)
B New connection 1 created
B Connect to LCA as SAPPL1 with us6pa1d02.na.cokecce.com-PL1
C
C DBSDBSLIB : version 700.08, patch 0.247 (Make PL 0.254)
C MAXDB shared library (dbsdbslib) patchlevels (last 10)
C (0.247) Use SCHEMANAME instead of OWNER for MaxDB 7.8 (note 1353266)
C (0.211) MVCC support for MaxDB (note 1332203)
C (0.204) Sapinst on windows/maxdb stop with error (note 1323436)
C (0.202) NUMC conversion corrected (note 1288313)
C (0.189) Default value for max. input variables is 2000 (note 655018)
C (0.189) Profile parameter to define max. input variables (note 655018)
C (0.188) Switch SQLMODE after CREATE INDEX SERIAL (note 1267841)
etc....
3. the user reports that the program was run with repair option. We will also submit one to do just checking, no repair. -
LCA03 generates short dump: DBIF_DSQL2_SQL_ERROR
This dump occurs in procedure "/SAPAPO/OM_SIMSESSION_GET_ALL".
If I look at the logs in LC10, it says:
SIM_SIMSESSION_GET_ALL
Invalid app server: SCX
expected: SCP
We recently completed (or thought we did - seems like we missed a step) a refresh of our sandbox SCM and livecache systems from production.
SCX is the sandbox system and SCP is the production system. This message makes me think that the new sandbox livecache copy is still trying to point to the production SCM system. Has anyone seen this before? Is there something I need to change within the livecache database?
I found a note (877203) that mentions changing the logical system name in /SAPAPO/PRDMAP to the target system, but when I run through the steps to do that, the command: select LOGSYS, count(*) from "SAPR3"."/SAPAPO/PRDMAP" group by logsys returns zero results - thus I didn't think I had to change anything.
I appreciate any feedback.
~TJHello TJ Wilkinson,
-> You are SAP customer. Please create the OSS ticket to the component 'BC-DB-LCA',
therefore we could logon & take a look closer on the reported issue.
-> Please review the SAP Note No. 1015489 with 'Reason and Prerequisites':
"You want to access the liveCache from the application server. However, the system name does not match the one specified in the liveCache. This may happen after a homogeneous system copy."
Did you run the homogeneous system copy?
What is the version of your system?
What is the version/build of the liveCache and LCA on the system?
What LCA/database error reported in the ABAP dump?
Thank you and best regards, Natalia Khlopina -
hi ...
one of my daily avtivity is to monitor abap dumps ...
am aware of using st22 ...
dbl click on each dump and analysing it....
in addition to that i need to know some more valuable inputs from other SAP users.....
so that i can able organize well.. and give suggestions to core members/end users...
if possible mention any of the methods u people following in ur concern for dump analysis...
regards
prasHi ,
Short dumps generally arises due to diff. diff circumstance, there is no single way to resolve it.
Short dumps mainly occur due to
u2022 table space issues ,
u2022 program termination due to long wait,
u2022 background dialog processess running reports for long lime,
u2022 Data packet size, etc which relates to basis.
Common dumps & how to handle it
Many time it appear because of lack of memory. At that time consult your Basis Team to increase the memory size.
TIME_OUT: this happens due to longer dialog execution time for a user compared to the parameter settings. We can ask the user to run the report in batch jobs instead of dialog. we can ask the user to reduce the search criteria if he is using one.
RAISE_EXCEPTION: This is due to error in exception handling of the abap program. If its a customer report we can ask the developer to modify code or if its a sap report we can raise issue with sap
DBIF_SQL_ERROR: this happens due to various problems with database.
Suppose user is trying to write duplicate entries to the tables then it occurs, if there is problem with the datafile then also it occurs. you have to read the details of the error.
TSV_NEW_PAGE_ALLOCATION_FAILED: Error due to not enough extended memory to run the report. This happens during high memory usage time, We can ask the user to run the report during less load and also to reduce the input criteria which will in turn reduce the processing memory required for the internal table.
or we need to increase the extended memory parameters.
MEMORY_NO_MORE_PAGING: happens due to not enough space in paging area. Can be solved by increasing the paging file parameter value.
LOAD_PROGRAM_ERROR: this error happens if during runtime any of the repository objects are changed by means of transport. We can ask the user to rerun the program
check your dumps in transaction code ST22 or choose Tools -- Administration -- Monitoring -- Dump analysis. in a shortdump you can find the exact line of code where the currently running program dumped. it also will give you a (clear) reason why it dumped. and above all it will give you an error message number and some additional keywords that permit you to search for a solution on oss or sdn site.Definitely refer to Transaction Code ST22 for viewing short dump and in 90% cases it gets resolved by carefully reading it .
For more analysis check the below link
http://help.sap.com/saphelp_nw70/helpdata/EN/46/ff01540bb921bee10000000a114a6b/frameset.htm -
Dear All Gurrus
i am facing an Abap Dump when user send cheque Printing .other document printing are Ok .please see this error
Runtime errors LOAD_PROGRAM_NOT_FOUND
Occurred on 04.06.2007 at 16:18:50
Program " " not found.
What happened?
There are several possible reasons for the error:
or
The current ABAP program had to be terminated because the
ABAP processor detected an internal system error.
The current ABAP program "SAPLF028" had to be terminated because the ABAP
processor discovered an invalid system state.
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
On account of a branch in the program
(CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
or a transaction call, another ABAP/4 program
is to be loaded, namely " ".
However, program " " does not exist in the library.
Possible reasons:
a) Wrong program name specified in an external PERFORM or
SUBMIT or, when defining a new transaction, a new
dialog module or a new function module.
b) Transport error
b) Transport error
How to correct the error
Check the last transports to the R/3 System.
Are changes currently being made to the program "SAPLF028"?
Has the correct program been entered in table TSTC for Transaction "FBZ4 "?
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:
"LOAD_PROGRAM_NOT_FOUND" C
"SAPLF028" or "LF028U06"
"PAYMENT_FORM_PRINT"
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....... "PKSAPT10"
Network address.......... "184.208.96.235"
Operating system......... "Windows NT"
Release.................. "5.0"
Hardware type............ "4x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "PKSAPT10"
Database type............ "MSSQL"
Database name............ "T10"
Database owner........... "t10"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Oct 29 2006 23:44:46"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "155"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
User, transaction...
Client.............. 210
User................ "AGHAZNAVI"
Language key........ "E"
Transaction......... "FBZ4 "
Program............. "SAPLF028"
Screen.............. "SAPMF05A 0700"
Screen line......... 43
Information on where terminated
The termination occurred in the ABAP program "SAPLF028" in
"PAYMENT_FORM_PRINT".
The main program was "SAPMF05A ".
The termination occurred in line 332 of the source code of the (Include)
program "LF028U06"
of the source code of program "LF028U06" (when calling the editor 3320).
Source code extract
003020 IF sy-subrc NE 0 "bei nicht in PAYR vorhandenen o.
003030 AND payr-vblnr EQ reguh-vblnr. "durch FCH7 (Scheck neu drucken)
003040 opayf-pstap = 0. "in Auftrag gegebene Schecks wird
003050 ELSE. "der Stapel mitgegeben, sonst die
003060 CLEAR payr. "Restart-Schecknummer aus PAYR
003070 ENDIF.
003080
003090 IF t042z-formi IS INITIAL. "alte Zahlungsträger (nur Scheck)
003100 SUBMIT (t042z-progn) WITH zw_laufd = reguh-laufd
003110 WITH zw_laufi = reguh-laufi
003120 WITH zw_zbukr = reguh-zbukr
003130 WITH zw_xvorl = space
003140 WITH sel_zawe = i_opayf-rzawe
003150 WITH par_zdru = 'X'
003160 WITH par_priz = i_opayf-ppriz
003170 WITH par_zfor = i_opayf-pzfor
003180 WITH par_avis = i_opayf-pavis
003190 WITH par_pria = i_opayf-ppria
003200 WITH par_stap = i_opayf-pstap
003210 WITH par_rchk = payr-chect
003220 WITH par_begl = space
003230 WITH sel_hbki = reguh-hbkid
003240 WITH sel_hkti = reguh-hktid
003250 WITH par_anzp = par_anzp
003260 WITH par_fill = i_opayf-pfill
003270 WITH par_espr = i_opayf-pespr
003280 WITH par_isoc = i_opayf-pisoc
003290 WITH par_sofo = i_opayf-psofo
003300 WITH par_novo = i_opayf-xnovo
003310 AND RETURN.
ELSE. "neue Zahlungsträger (z.Zt. nur OFX)
003330 CALL FUNCTION 'PAYMENT_MEDIUM_ONLINE'
003340 EXPORTING
003350 im_formi = t042z-formi
003360 im_reguh = reguh
003370 im_opayf = i_opayf
003380 TABLES
003390 tb_regup = xregup.
003400 ENDIF.
003410
003420 ENDFUNCTION.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 4 SY-INDEX 0
SY-TABIX 1 SY-DBCNT 1
SY-FDPOS 0 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY UAN
SY-UCOMM BU
SY-TITLE Payment with Printout: Display Overview
SY-MSGTY I SY-MSGID F5
SY-MSGNO 312 SY-MSGV1 1500000011
SY-MSGV2 KOPK SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
4 FUNCTION PAYMENT_FORM_PRINT
SAPLF028
LF028U06 332
3 FORM FCODE_BEARBEITUNG
SAPMF05A
MF05AFF0_FCODE_BEARBEITUNG 2333
2 FORM FUSSZEILE_VERARBEITEN
SAPMF05A
MF05AFF0_FUSSZEILE_VERARBEITEN 148
1 MODULE (PAI) FUSSZEILE_BEARBEITEN
SAPMF05A
MF05AI00_FUSSZEILE_BEARBEITEN 46
Chosen variables
4 FUNCTION PAYMENT_FORM_PRINT
SAPLF028
LF028U06 332
I_CC_CURR PKR
54522
0B200
I_OPAYF KOPKLOCL 0002 XCCIT
4454444422222222222222222222233332254445
BF0BCF3C00000000000000000000000020083394
... + 40 IH X 0001000005
4422522222222222333333333322222222222222
9800800000000000000100000500000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120 00000000000000
2222222222222222222222233333333333333
0000000000000000000000000000000000000
I_REPRI
2
0
I_VBLNR 1500000011
3333333333
1500000011
I_WWERT 20070604
33333333
20070604
REGUH-LAUFI 00001*
333332
00001A
<%_TABLE_LFA1> ???
REGUH-ZBUKR KOPK
4454
BF0B
I_OPAYF-RZAWE C
4
3
I_OPAYF-PPRIZ LOCL
4444
CF3C
I_OPAYF-PZFOR
2222222222222222
0000000000000000
I_OPAYF-PAVIS
2
0
I_OPAYF-PPRIA
2222
0000
I_OPAYF-PSTAP 0002
3333
0002
PAYR-CHECT
2222222222222
0000000000000
REGUH-HBKID CITIH
44544
39498
REGUH-HKTID CTOLH
45444
34FC8
PAR_ANZP 0
3
0
I_OPAYF-PFILL
2
0
I_OPAYF-PESPR
2
0
I_OPAYF-PISOC
2
0
I_OPAYF-PSOFO X
5
8
I_OPAYF-XNOVO
2
0
%_PRINT 000
2222333222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 0 ########
2222222222320000000022222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160 0 ####
222222222222223222222222222222220000
000000000000000000000000000000000000
KNBK-KOINH
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
22222222222222222222
00000000000000000000
T042Z-FORMI
222222222222222222222222222222
000000000000000000000000000000
<%_TABLE_T012> ???
REGUH 2007060400001* KOPK0001000005
2223333333333333224454333333333322222222
0002007060400001A0BF0B000100000500000000
... + 40 1500000011 PKR LHP1Co
2222222222222222223333333333254522445346
000000000000000000150000001100B200C8013F
... + 80 mpany Supreme Gas Ind. Pvt. Ltd
6766722222222577766624672466225772247622
D01E90000000035025D5071309E4E0064E0C4400
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240 Lahore
222466676222222
000C18F25000000
SYST-REPID SAPLF028
5454433322222222222222222222222222222222
310C602800000000000000000000000000000000
T042I-HBKID CITIH
44544
39498
XREGUP[] Table IT_1065[1x1184]
3 FORM FCODE_BEARBEITUNG
SAPMF05A
MF05AFF0_FCODE_BEARBEITUNG 2333
%_SPACE
2
0
RC 0
0000
0000
SYST-REPID SAPMF05A
5454433422222222222222222222222222222222
310D605100000000000000000000000000000000
SY-REPID SAPMF05A
5454433422222222222222222222222222222222
310D605100000000000000000000000000000000
VORSCHL_GRIRG
222
000
XBKPF-BELNR 1500000011
3333333333
1500000011
%_DUMMY$$
2222
0000
VAKTAB
222222222222222222222222222222
000000000000000000000000000000
XBKPF-BUKRS KOPK
4454
BF0B
VORSCHL_GITYP
22
00
XBKPF-GJAHR 2007
3333
2007
C_INFO_LINK 100
333
100
BKPF 210KOPK15000000112007KZ20070604200706040
3334454333333333333334533333333333333333
210BF0B15000000112007BA20070604200706040
... + 40 620070604161846000000000000000020070604A
3333333333333333333333333333333333333334
6200706041618460000000000000000200706041
... + 80 GHAZNAVI FBZ4
4445445422244532222222222222222222222222
781AE16900062A40000000000000000000000000
... + 120 12345
2222222333332222222222222222222222222222
0000000123450000000000000000000000000000
... + 160 0000 PKR ###
2223333222222222222222222222222254522000
000000000000000000000000000000000B200000
... + 200 ## ##### ####### RFBU
0022222000002200000002544522222222222222
0C000000000C00000000C0262500000000000000
... + 240
222222222222222
000000000000000
BSEG 210KOPK15000000112007002 000000000000000
3334454333333333333333332333333333333333
210BF0B150000001120070020000000000000000
... + 40 0 25K SLHP1 ##########
3222222222233422254453222222220001000000
0000000000025B0003C80100000000000000C000
... + 80 ##################PKR #################
1000000000000010005452200000000000000000
000C000000C000000C0B200000000C000000C000
... + 120 #######################################
0000000000000000000000000000000000000002
000C000000C000000C000000C000000C000000C0
... + 160 000 ###############################
2223332220000000000000000000000000000000
000000000000000C0000C000000C000000C00000
... + 200 ##0000000020070427
0033333333333333332222222222222222222222
0C00000000200704270000000000000000000000
... + 240
222222222222222
000000000000000
SY-SUBRC 4
0000
4000
%_ARCHIVE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
SAPOS-GITYP
22
00
T001-WAERS PKR
54522
0B200
SAPOS-GRICD
22
00
OPAYF KOPKLOCL 0002 XCCIT
4454444422222222222222222222233332254445
BF0BCF3C00000000000000000000000020083394
... + 40 IH X 0001000005
4422522222222222333333333322222222222222
9800800000000000000100000500000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120 00000000000000
2222222222222222222222233333333333333
0000000000000000000000000000000000000
SAPOS-GRIRG
222
000
RF05A-KOATX
222222222222
000000000000
BKPF-WWERT 20070604
33333333
20070604
SY-XFORM CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
SY-MSGID F5
43222222222222222222
65000000000000000000
ANL_HKONT
2222222222
0000000000
T001W
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240 #
222222222222220
000000000000000
SPACE
2
0
SY-MSGNO 312
333Specification of form is missing in pmnt method C for comp.code KOPK
In the include program RFFORI01 the query "SELECT * FROM t042z WHERE land1 EQ t001-land1 AND zlsch IN sel_zawe AND progn EQ sy-repid" is returning a null value for progn. This null value is passed to "003100 SUBMIT (t042z-progn) WITH zw_laufd = reguh-laufd" (Refer to the short dump).
Refer to IMG for adding specification of form.
Regards,
Khalid Mustafa
Development Consultant Netweaver-ABAP
Maybe you are looking for
-
Lenovo Services/P​rogram takes a long time to start after bootup
It seems like Lenovo services take a long time to start after boot up is completely done. My Bootup time is less than a minute (0:51s), but my lenovo services (Power Manager Gauage, Lenovo Services in the Sidebar, have th ThinkVanatage Button work, a
-
I can not create an email account for my client
I have created an email account ([email protected]) and it is sending snd recieving messages. However when I try to create an address ([email protected]) me client could not log in to the webmail. I deleted the account and re-created the address with
-
HOW to create a function module ..... in abap
pls lemme know ............the steps and procedure in creating a function module
-
How can I take aout the virus coupondropdown from my mac?
I need to know how to remove a coupondropdown from my mac? It is in all the blogs that I open
-
Batch changing iPhoto photo dates.
I've imported several thousand scanned photos into iPhoto 7.1.3, and changed the dates to the dates they was taken either by modifying the information window, or by using batch date change. My intention was to modify the original files so that export