Regarding Dump Analysis

My select statement is working very fine in Development client, when it is transported to Production client, it is showing dump error because of huge data. how to rectify this error.

Hi Madhav,
If the dump is a time out dump, then it's performance issues and one possible solution is to run the report in background and draw out the report (as long as output is not interactive).
If the dump is not a time out dump, then study the dump more closely, especially if the query is on a Z table because there might be some field/ data element not transported across to Q and hence causing the dump.
Hope this helps!
Cheers,
Aditya

Similar Messages

What is Short Dump Analysis and secendry index ?

Dear Experts .
1.) What is purpose of T-codes SE30 and ST22 ?
What is Short Dump Analysis ?
2.) What is secendry index , How to use it ? How it effects the Performance of a report ?
Please it is urgent ...
Regards : Rajneesh

Hi
A dump analysis is a comprehensive list that should enable you to identify the causes and possible solutions of program errors. The ABAP Workbench generates a short dump whenever a report or transaction terminates due to a serious error. The system enters the error in the system log and writes a snapshot of the program at the moment when it terminated into a special database table called SNAP.
Dump analyses give the user or programmer information about the causes of the error that has caused the program to terminate. Experienced users can use them to identify very quickly where and why this occurred. He or she can them solve the problem.
The snapshot contains the following information:
Why the program has terminated
What caused the program termination
Where in the program code the termination occurred
What you can do to correct the error
The values of the relevant system fields when the program terminated
The calls or events that were active when the program terminated
Any other programs that are affected.
http://help.sap.com/saphelp_nw70/helpdata/en/c6/617d0ce68c11d2b2ab080009b43351/content.htm
Index: Technical key of a database table.
Primary index: The primary index contains the key fields of the table and a pointer to the non-key fields of the table. The primary index is created automatically when the table is created in the database.
Secondary index: Additional indexes could be created considering the most frequently accessed dimensions of the table.
Structure of an Index
An index can be used to speed up the selection of data records from a table.
An index can be considered to be a copy of a database table reduced to certain fields. The data is stored in sorted form in this copy. This sorting permits fast access to the records of the table (for example using a binary search). Not all of the fields of the table are contained in the index. The index also contains a pointer from the index entry to the corresponding table entry to permit all the field contents to be read.
When creating indexes, please note that:
An index can only be used up to the last specified field in the selection! The fields which are specified in the WHERE clause for a large number of selections should be in the first position.
Only those fields whose values significantly restrict the amount of data are meaningful in an index.
When you change a data record of a table, you must adjust the index sorting. Tables whose contents are frequently changed therefore should not have too many indexes.
Make sure that the indexes on a table are as disjunctive as possible.
(That is they should contain as few fields in common as possible. If two indexes on a table have a large number of common fields, this could make it more difficult for the optimizer to choose the most selective index.)
Accessing tables using Indexes
The database optimizer decides which index on the table should be used by the database to access data records.
You must distinguish between the primary index and secondary indexes of a table. The primary index contains the key fields of the table. The primary index is automatically created in the database when the table is activated. If a large table is frequently accessed such that it is not possible to apply primary index sorting, you should create secondary indexes for the table.
The indexes on a table have a three-character index ID. '0' is reserved for the primary index. Customers can create their own indexes on SAP tables; their IDs must begin with Y or Z.
If the index fields have key function, i.e. they already uniquely identify each record of the table, an index can be called a unique index. This ensures that there are no duplicate index fields in the database.
When you define a secondary index in the ABAP Dictionary, you can specify whether it should be created on the database when it is activated. Some indexes only result in a gain in performance for certain database systems. You can therefore specify a list of database systems when you define an index. The index is then only created on the specified database systems when activated

Error in HRPAD31 ( Short dump Analysis )

Hi friends,
When i am changing the existing qualification or adding new qualification it is showing this error in short dump
Pls advise me if there is some relationship i am missing in 031 ?
here is the description of short dump
Runtime Error DBIF_RSQL_SQL_ERROR
Exception        CX_SY_OPEN_SQL_DB
Occurred on     10.09.2008 at   10:48:39
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', wasneither
caught nor passed along using a RAISING clause, in the procedure"ADATA_DB" "FORM)"
Since the caller of the procedure could not have expected this exception to occcur, 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 "ADATA_DB"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-01653: unable to extend table SAPR3.HRPAD31 by 80 in tablespace PSAPSTABD"
Internal call code.........: "RSQL/INSR/HRPAD31"
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
"SAPLRHAP" or "LRHAPF1K"
"ADATA_DB"
System environment
SAP Release.............. "620"
Application server....... "Development"
Network address.......... "200.200.200.10"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "2x IA64 Level 3"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "Development"
Database type............ "ORACLE"
Database name............ "VC3"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Aug 16 2007 23:23:39"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "196"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
User, transaction...
Client.............. 600
User................ "HUSER"
Language key........ "E"
Transaction......... "PP01 "
Program............. "SAPLRHAP"
Screen.............. "MP100100 6000"
Screen line......... 16
Information on where terminated
The termination occurred in the ABAP program "SAPLRHAP" in "ADATA_DB".
The main program was "MP100100 ".
The termination occurred in line 57 of the source code of the (Include) program LRHAPF1K"
of the source code of program "LRHAPF1K" (when calling the editor 570).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the procedure "ADATA_DB" "(FORM)" but was not handled locally, not declared in the RAISING clause of the procedure.
The procedure is in the program "SAPLRHAP ". Its source code starts in line 8 of the (Include) program "LRHAPF1K ".
PLS LET ME KNOW IF I NEED TO CHECK ALL MY CONFIGURATION ?

Hi Ted,
It is working, i just logged off and logged in. Now there is no error.
Thanks for all your support. I am struggling on this isse from 3 days and could not sort it out.
I appreciate on more time for your knowledge.
I have rewarded the points also....
Regards
HR user

ABAP dump analysis

HI all
Pl let me know ABAP Dump analysis .which type of abap dump problems arrived every time. pl explain explain more than two or three examples recently u face abap dumps and solutions hoe u resolved that problems
[removed by moderator]
I really appreciate your feed back on this request
Thanks
Hari

hi
Dump Analysis
A dump analysis is a comprehensive list that should enable you to identify the causes and possible solutions of program errors. The ABAP Workbench generates a short dump whenever a report or transaction terminates due to a serious error. The system enters the error in the system log and writes a snapshot of the program at the moment when it terminated into a special database table called SNAP.
Dump analyses give the user or programmer information about the causes of the error that has caused the program to terminate. Experienced users can use them to identify very quickly where and why this occurred. He or she can them solve the problem.

The snapshot contains the following information:
Why the program has terminated
What caused the program termination
Where in the program code the termination occurred
What you can do to correct the error
The values of the relevant system fields when the program terminated
The calls or events that were active when the program terminated
Any other programs that are affected.
In Basis 6.20, you can also reorganize short dumps from within ST22 via menu option Goto->Reorganize but I'm not sure if that exists in 4.6C. This option allows you to specify a different retention period for the short dumps. You would need to use this manual reorganization process in place of the batch version.
If there is requirement for you to keep some of your ABAP short dumps there is also an option in ST22 to allow you to keep them indefinately. When you see the list of dumps, you simply cursor select the required
dump(s0 and select menu option Short dump->Keep. Kept short dumps are not subject to reorganization until they are released again.
regards
ravish
plz dont forget to reward points if helpful

Crash Dump Analysis, application cannot execute

Welcome,
my question regarding to dump crash. I have problem with application. When I run application, I see first intro, second intro and later application crash and return to the desktop with error stop working. I created dump file of error and paste analyze below.
I must add, that this application works properly on the other computer with Windows Server 2012 Datacenter x64. Could someone tell me, where is the problem, why application crashed with error access violation?
Primary Analysis
Crash Dump Analysis
Windows 8 Version 9600 MP (8 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
kernel32.dll version: 6.3.9600.17415 (winblue_r4.141028-1500)
Machine Name:
Debug session time: Sun Jan 25 04:09:51.000 2015 (UTC - 5:00)
System Uptime: 1 days 1:33:05.076
Process Uptime: 0 days 0:00:14.000
Kernel time: 0 days 0:00:00.000
User time: 0 days 0:00:00.000
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\oca.ini, error 2
TRIAGER: Could not open triage file : e:\dump_analysis\program\winxp\triage.ini, error 2
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\user.ini, error 2
Exception Analysis
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\guids.ini, error 2
*** ERROR: Symbol file could not be found.
Defaulted to export symbols for aticfx32.dll -
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
*** The OS name list needs to be updated! Unknown Windows version: 6.3 ***
FAULTING_IP:
+8afa2
5458455f ??
EXCEPTION_RECORD:
ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 5458455f
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 5458455f
Attempt to read from address 5458455f
DEFAULT_BUCKET_ID:
BAD_INSTRUCTION_PTR
PROCESS_NAME:
game.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx".
The memory could not be "%s".
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx".
The memory could not be "%s".
EXCEPTION_PARAMETER1:
00000000
EXCEPTION_PARAMETER2:
5458455f
READ_ADDRESS:
5458455f
FOLLOWUP_IP:
game+8afa2
0048afa2 eb12
jmp     game+0x8afb6 (0048afb6)
FAILED_INSTRUCTION_ADDRESS:
+8afa2
5458455f ??
NTGLOBALFLAG:
0
APPLICATION_VERIFIER_FLAGS:
0
FAULTING_THREAD:
00001004
PRIMARY_PROBLEM_CLASS:
BAD_INSTRUCTION_PTR
BUGCHECK_STR:
APPLICATION_FAULT_BAD_INSTRUCTION_PTR_INVALID_POINTER_READ
LAST_CONTROL_TRANSFER:
from 0048afa2 to 5458455f
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
0018f678 0048afa2 00000de1 00000000 000083f3 0x5458455f
00000000 00000000 00000000 00000000 00000000 game+0x8afa2
SYMBOL_STACK_INDEX:
1
SYMBOL_NAME:
game+8afa2
FOLLOWUP_NAME:
MachineOwner
MODULE_NAME: game
IMAGE_NAME:
game.exe
DEBUG_FLR_IMAGE_TIMESTAMP:
3f329165
STACK_COMMAND:
dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ~0s; .ecxr ; kb
FAILURE_BUCKET_ID:
BAD_INSTRUCTION_PTR_c0000005_game.exe!Unknown
BUCKET_ID:
APPLICATION_FAULT_BAD_INSTRUCTION_PTR_INVALID_POINTER_READ_BAD_IP_game+8afa2
WATSON_STAGEONE_URL:
http://watson.microsoft.com/StageOne/game_exe/0_0_0_0/3f329165/unknown/0_0_0_0/bbbbbbb4/c0000005/5458455f.htm?Retriage=1
Followup: MachineOwner
Loaded Module List
start
end        module name
00400000 00a50000
game     game.exe
60000000 60028000
ijl10    ijl10.dll
6f580000 70b0f000
atioglxx atioglxx.dll
72960000 729c0000
AudioSes AudioSes.dll
729c0000 72a13000
MMDevAPI MMDevAPI.dll
72a20000 72b30000
aticfx32 aticfx32.dll
72b30000 72b4c000
atigktxx atigktxx.dll
72b50000 72c29000
atiadlxy atiadlxy.dll
72c30000 72c45000
atiglpxx atiglpxx.dll
72c50000 72c90000
powrprof powrprof.dll
72c90000 72d7c000
ddraw    ddraw.dll
72d80000 72da5000
dinput   dinput.dll
72db0000 72e31000
dsound   dsound.dll
72e40000 72e65000
glu32    glu32.dll
72ec0000 72f9e000
opengl32 opengl32.dll
73500000 7350a000
avrt     avrt.dll
73530000 7353f000
wtsapi32 wtsapi32.dll
73540000 73547000
dciman32 dciman32.dll
73680000 736a3000
WINMMBASE WINMMBASE.dll
737c0000 737e3000
winmm    winmm.dll
73800000 7381b000
userenv userenv.dll
73d90000 73db1000
devobj   devobj.dll
73df0000 73f2a000
propsys propsys.dll
73f30000 74136000
comctl32_73f30000 comctl32.dll
74140000 7415a000
dwmapi   dwmapi.dll
74160000 7424d000
uxtheme uxtheme.dll
74250000 742d9000
comctl32 comctl32.dll
74850000 74858000
winnsi   winnsi.dll
74890000 748b0000
IPHLPAPI IPHLPAPI.DLL
74b10000 74b18000
version version.dll
74c70000 74c7f000
profapi profapi.dll
74c80000 74d0b000
SHCore   SHCore.dll
74d80000 74d89000
kernel_appcore kernel.appcore.dll
74e40000 74e94000
bcryptPrimitives bcryptPrimitives.dll
74ea0000 74eaa000
CRYPTBASE CRYPTBASE.dll
74eb0000 74ece000
sspicli sspicli.dll
74f30000 74f3e000
msasn1   msasn1.dll
74f40000 74f7c000
cfgmgr32 cfgmgr32.dll
74f90000 7509e000
gdi32    gdi32.dll
750a0000 751f3000
user32   user32.dll
75200000 7527c000
advapi32 advapi32.dll
75280000 75315000
oleaut32 oleaut32.dll
75320000 753e3000
msvcrt   msvcrt.dll
753f0000 75431000
sechost sechost.dll
75440000 755bd000
combase combase.dll
75620000 75733000
msctf    msctf.dll
75740000 758c8000
crypt32 crypt32.dll
758d0000 7590d000
wintrust wintrust.dll
75910000 7599d000
clbcatq clbcatq.dll
759a0000 75ae0000
kernel32 kernel32.dll
75b00000 76dac000
shell32 shell32.dll
76e40000 76e47000
nsi      nsi.dll
76e50000 76e95000
shlwapi shlwapi.dll
76ea0000 76f5a000
rpcrt4   rpcrt4.dll
76f60000 77088000
ole32    ole32.dll
77090000 77096000
psapi   psapi.dll
770a0000 77177000
KERNELBASE KERNELBASE.dll
77180000 771d0000
ws2_32   ws2_32.dll
771d0000 7726b000
comdlg32 comdlg32.dll
773f0000 775a1000
setupapi setupapi.dll
775b0000 775d7000
imm32    imm32.dll
776b0000 7781e000
ntdll   ntdll.dll
Unloaded modules:
72b30000 72b4c000
atigktxx.dll
Any help would be appreciated,
Pawel

PT
Metropolis software was shut down in 2009 and there is no further support or development for the products. Since their shutdown is prior to win 8 it cannot be compatible. Read about it here http://www.giantbomb.com/metropolis-software-house/3010-107/
The only thing I can suggest for you is to try re-installing the game in compatibility mode.
To install in compatibility mode do the following:
Right click the installer>properties>compatibility>choose OS
http://windows.microsoft.com/en-US/windows-vista/Make-older-programs-run-in-this-version-of-Windows?SignedIn=1
(works in vista, win 7, win 8, and win 10)
Wanikiya and Dyami--Team Zigzag

Upgrade Dump analysis

Hi Gurus
Here is a list of our system dumps in September and October. I would like if any of you would analyze these for any trends or differences.
The reason is that we upgraded from BW 3.1 to 3.5 by the end of September. We need to know if this has lead to a signifiacant change in the types of dumps we are receiving.
Pre Upgrade
Runtime error Count
MESSAGE_TYPE_X 214
DYNPRO_SEND_IN_BACKGROUND 43
STORAGE_PARAMETERS_WRONG_SET 41
CALL_FUNCTION_SEND_ERROR 29
UNCAUGHT_EXCEPTION 17
START_CALL_SICK 14
TIME_OUT 12
RAISE_EXCEPTION 9
TYPELOAD_LOST 8
CALL_FUNCTION_OPEN_ERROR 7
DBIF_RSQL_INVALID_RSQL 5
DBIF_RSQL_SQL_ERROR 5
RFC_ATTACH_GUI_FAILED 4
IMPORT_FORMAT_ERROR 4
DBIF_DSQL2_SQL_ERROR 4
DBIF_SETG_SQL_ERROR 4
LOAD_PROGRAM_LOST 4
TSV_TNEW_PAGE_ALLOC_FAILED 4
RABAX_CALLING_RABAX 3
DBIF_REPO_SQL_ERROR 2
SYSTEM_CORE_DUMPED 2
OBJECTS_OBJREF_NOT_ASSIGNED 2
CONNE_IMPORT_ILL_OBJECT_TYPE 1
ITAB_DUPLICATE_KEY 1
SAPSQL_INVALID_TABLENAME 1
DBIF_RTAB_SQL_ERROR 1
DBIF_DSQL2_OBJ_UNKNOWN 1
SAPSQL_ARRAY_INSERT_DUPREC 1
GETWA_NOT_ASSIGNED 1
Post Upgrade 
Name of runtime error Count
MESSAGE_TYPE_X 211
DBIF_RSQL_SQL_ERROR 16
STORAGE_PARAMETERS_WRONG_SET 11
OBJECTS_OBJREF_NOT_ASSIGNED 10
CALL_FUNCTION_SEND_ERROR 9
SYNTAX_ERROR 9
TIME_OUT 8
TSV_TNEW_PAGE_ALLOC_FAILED 6
TYPELOAD_LOST 5
CALL_FUNCTION_OPEN_ERROR 5
IMPORT_FORMAT_ERROR 5
SYSTEM_CORE_DUMPED 4
DBIF_RSQL_INVALID_RSQL 3
LOAD_PROGRAM_LOST 3
UNCAUGHT_EXCEPTION 3
SAPSQL_CURSOR_ALREADY_OPEN 3
RAISE_EXCEPTION 2
CALL_FUNCTION_NOT_FOUND 2
CALL_FUNCTION_NO_DEST 2
DBIF_SETG_SQL_ERROR 2
RFC_ATTACH_GUI_FAILED 2
ITAB_DUPLICATE_KEY 1
SAPSQL_INVALID_TABLENAME 1
CALL_FUNCTION_ACCEPT_FAILED 1
CONNE_IMPORT_ILL_OBJECT_TYPE 1
SAPSQL_INVALID_FIELDNAME 1
TYPELOAD_NEW_VERSION 1
SYSTEM_CANCELED 1

Hi Jeevi,
You can check Dump using ST22 transaction. Dump analysis is nothing but the analysis as what was the cause of dump, what went on the worng in the program which resulted in dump and such questions and getting there answers.
Reward points if useful.
Regards,
Atish

ST22 Dump Analysis

How to use ST22 to analyse dump analysis in a ABAP program ?

Hi
You can use the function module SUBST_LIST_ABAP_DUMP to get the complete text of the dump and you can use the function module TCC_SHORTDUMP_INFO to get all the short dumps within a date range.
SUBST_LIST_ABAP_DUMP - Get the complete text of the dump
TCC_SHORTDUMP_INFO - Get all the short dumps within a date range
RS_ST22_GET_DUMPS
RS_ST22_GET_DUMPS
to get the dump results.
other related fun modules are:
RS_ST22_GET_DUMPS_CATEGORIES
RS_ST22_GET_DUMP_CATEGORY
RS_ST22_GET_DUMP_CATEGORY_TEXT
Regards
Vasu

About dump analysis

hi guru
please tell me procedure of dump analysis.
how as a programmer i will achieve this.
regards.
subhasis

Hi,
Goto ST22, select dump u want there u will find lot of informatiuon like error descripton, analysis, what to do, memory map and so on with code line where error is there .
u can go to directily on line where dump is given.
u can check analysis why error occured so u will be clear to recify it.
if u want u can check memory status at run time .
Hope this iwll help u.
Jogdand M B

Data_offset_too_large , why this error occurs in dump analysis

HI,
when i tried to execute the report it gives the dump analysis as DATA_OFFSET_TOO_LARGE, on which occasion it gives the erros

Hi,
Kindly check the error dump using ST22 - Runtime error analysis.
In error report look for the followings:
Error analysis: This gives the reason for the error.
How to correct the error: Here you can find the recommended solution for the error.
Source Code Extract: Here you can find the source code in which the error has occured.
In the source code, kindly look for the ">>>>>" mark against the line number.
The error has occured only at that line of the source code.
In your case, the error might have occured while assigning a variable of larger size
to a variable of size relatively smaller than that.
Best regards,
Thangesh

How to do DUMP Analysis ?

How to do DUMP Analysis ?Can anybody explain me the steps to solve the dump step by step ?
thanks
Naresh

Hi
A dump analysis is a comprehensive list that should enable you to identify the causes and possible solutions of program errors. The ABAP Workbench generates a short dump whenever a report or transaction terminates due to a serious error. The system enters the error in the system log and writes a snapshot of the program at the moment when it terminated into a special database table called SNAP.
Dump analyses give the user or programmer information about the causes of the error that has caused the program to terminate. Experienced users can use them to identify very quickly where and why this occurred. He or she can them solve the problem.
The snapshot contains the following information:
Why the program has terminated
What caused the program termination
Where in the program code the termination occurred
What you can do to correct the error
The values of the relevant system fields when the program terminated
The calls or events that were active when the program terminated
Any other programs that are affected.
http://help.sap.com/saphelp_nw70/helpdata/en/c6/617d0ce68c11d2b2ab080009b43351/content.htm
Index: Technical key of a database table.
Primary index: The primary index contains the key fields of the table and a pointer to the non-key fields of the table. The primary index is created automatically when the table is created in the database.
Secondary index: Additional indexes could be created considering the most frequently accessed dimensions of the table.
Structure of an Index
An index can be used to speed up the selection of data records from a table.
An index can be considered to be a copy of a database table reduced to certain fields. The data is stored in sorted form in this copy. This sorting permits fast access to the records of the table (for example using a binary search). Not all of the fields of the table are contained in the index. The index also contains a pointer from the index entry to the corresponding table entry to permit all the field contents to be read.
When creating indexes, please note that:
An index can only be used up to the last specified field in the selection! The fields which are specified in the WHERE clause for a large number of selections should be in the first position.
Only those fields whose values significantly restrict the amount of data are meaningful in an index.
When you change a data record of a table, you must adjust the index sorting. Tables whose contents are frequently changed therefore should not have too many indexes.
Make sure that the indexes on a table are as disjunctive as possible.
(That is they should contain as few fields in common as possible. If two indexes on a table have a large number of common fields, this could make it more difficult for the optimizer to choose the most selective index.)
Accessing tables using Indexes
The database optimizer decides which index on the table should be used by the database to access data records.
You must distinguish between the primary index and secondary indexes of a table. The primary index contains the key fields of the table. The primary index is automatically created in the database when the table is activated. If a large table is frequently accessed such that it is not possible to apply primary index sorting, you should create secondary indexes for the table.
The indexes on a table have a three-character index ID. '0' is reserved for the primary index. Customers can create their own indexes on SAP tables; their IDs must begin with Y or Z.
If the index fields have key function, i.e. they already uniquely identify each record of the table, an index can be called a unique index. This ensures that there are no duplicate index fields in the database.
When you define a secondary index in the ABAP Dictionary, you can specify whether it should be created on the database when it is activated. Some indexes only result in a gain in performance for certain database systems. You can therefore specify a list of database systems when you define an index. The index is then only created on the specified database systems when activated

Regarding dump error in smartforms

hi experts,
 my one driver program along with smartforms is working fine in the development server after transportation to production server it is showing dump error :::
the error is:
Function module " " not found.
What happened?
The function module " " was called, but cannot be
 found in the Function Library.
Error in ABAP application program.
The current ABAP program "ZSD_DELIVERY_ORDER_DRIVER_PREP" 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.
is especially useful if you want to keep a particular message.
Error analysis
An exception occurred. This exception will be dealt with in more detail
 below. The exception, assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
 not caught, which
led to a runtime error. The reason for this exception is:
 The program "ZSD_DELIVERY_ORDER_DRIVER_PREP" contains a CALL FUNCTION
 statement. The name
of the function module to be called is " ".
No function module exists with the name " ".
 All function modules are stored in the Function Library (SE37).
Possible reasons:
a) Wrong name specified. Particular attention should be paid
 to upper/lower case and underscores ("_")
 b) Transport error
c) If an enqueue/dequeue module has been used, the lock object
 may not have been activated (ABAP Dictionary)
 may not have been activated (ABAP Dictionary).
i have checked in the production server but i m not finding " " this thing in the program ..plz help me to solve this.

Hi Ravi,
Can you show me the code where you have called the smart form in driver program.Becaus the FM generated in Development server may differ from the FM generated in Production server.Make sure u r passing the FM which is generated from the function module SSF_FUNCTION_MODULE_NAME.

ST 22 dump analysis

Hi, In ST22 dump analysis, we are getting the following columns...
Date, Time, Host, User,Client, Error ID....Is there any way to get also the program name (which is usually available on double clicking any row) in it...
Because dump analysis report if needed to do program wise it is very difficult to do so....

Hi Soumen,
the reportname is already available in the dump overview.
You can see the information, if you scroll the alv to the right end. If you don't see the column 'Reportname', then you have to adjust the layout of the alv with the layout button. There you have also the possibility to rearrange the sequence of the columns and/or to (un-)hide several columns, which are unnecessary for you.
Save your changes as user-specified layout.
Greetings
Joerg

Template doc regarding Gap analysis of SAP BI -MM

Hi Gurus,
Can any one send a template doc regarding Gap analysis of SAP BI -MM

HI,
Gap Analysis:
In simple terms: Gap means small cracks. In SAP world or in Information Technology world, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be."
Gap Analysis is undertaken as a means of bridging that space. Actual Gap Analysis is time consuming and it plays vital role in Business Blueprintstage.
A through Gap Analysis will identify the gaps between how the business operates and its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned,
1. GAP must be closed and customised software can be developed
2. GAP must be closed but software cannot be written therefore a workaround is required
3. GAP does not need to be closed.
A point worth mentioning here is that at time people confuse between user-exits and Gap Analysis. User exits are standard gate ways provided by SAP to exit the standard code and we can write our own code with the help of ABAP workbench, its not new functionality which we are trying to build in sap but its slight enhancement within the same code.
Gap analysis is start point of Realization and once business Blueprint is finished we have to find the realization of sap system for client requirment and there will be certain gaps when compared to system fit. Those gaps can be closed either by re-engineering of business process to fit with SAP or we have to use USER exits in case of small deviations or complete enhancements with the help of ABAP to fit with the SAP system.
The Gaps can differ from company to company. Most commonly, however, missing functionality is industry-specific.
GAP Analysis
Re: gap analysis
Re: gap analysis
Tarak

Regarding Dump in Smartform

Hi SAP Gurus,
In a customised Smartfrom,
-Running fine in Development ,
But, in production , it is showing the following error
ShrtText
 Field symbol has not yet been assigned.
What happened?
 Error in ABAP application program.
 The current ABAP program "SAPLSTXBC" had to be terminated because one of the
 statements could not be executed.
 This is probably due to an error in the ABAP program.
Error analysis
 You attempted to access an unassigned field symbol
 (data segment 32772).
 This error may occur for any of the following reasons:
 - You address a typed field symbol before it is set using ASSIGN
 - You address a field symbol that points to a line in an internal table
 that has been deleted
 - You address a field symbol that had previously been reset using
 UNASSIGN, or that pointed to a local field that no longer exists
 - You address a global function interface parameter, even
 though the relevant function module is not active,
 that is it is not in the list of active calls. You can get the list
 of active calls from the this short dump.
How to correct the error
 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:
 "GETWA_NOT_ASSIGNED" C
 "SAPLSTXBC" or "LSTXBCTB2"
 "TAB_RESTART_TABLE_NORMAL"
Plz, Help
Thanks and Regards,
Pavan

Thanks Ankur,
This Dump is coming after Print Preview,
here is the place of dump occurance,
1202 * transfer overflow otf to output
1203 perform tab_transfer_overflow.
1204
1205 l_actual_row = tab-actrow.
1206
1207 * modify height in row (and cell) information table
1208 read table tab-trowinfo assigning <l_rowinfo>
1209 with key row = l_actual_row.
>>>> loop at <l_rowinfo>-cellinfo assigning <l_cellinfo>.
1211 read table otfoverflow-overflow into l_over index <l_cellinfo>-col.
1212 <l_cellinfo>-actcheight = l_over-actcheight.
1213 <l_cellinfo>-redheight = l_over-redheight.
1214 endloop.
1215 <l_rowinfo>-rowheight = otfoverflow-rowheight.
1216
1217 * note 562633 for old tables
1218 if tab-definition-comptab = c_false.
1219 * if doubleoverflow is not initial start new row, never end table
1220 if not l_double_overflow is initial.
1221 tab-intcause = c_tab_interrupt_new_row.
1222 endif.
1223 endif.
Thanks and Regards,
Pavan

Regarding dump error in MMBE

hi experts good morning,
                  when i execute tc mmbe it is showing dump error sometimes back it worked fine and now it is showing dump error ,,i m giving the error below plz have a look and help me.....
ShrtText
    Syntax error in program "SAPLMBBS ".
What happened?
    Error in ABAP application program.
    The current ABAP program "RMMMBESTN" had to be terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    In program "SAPLMBBS ", the following syntax error occurred
    in the Include "LMBBSU07 " in line 75:
    "The column name "WAERS" has two meanings. ABAP/4 Open SQL statement."
    Author and last person to change the Include are:
    Author "SAP "
    Last changed by "SAP "
Error analysis
    In program "SAPLMBBS ", the following syntax error occurred:
    "The column name "WAERS" has two meanings. ABAP/4 Open SQL statement."
Trigger Location of Runtime Error
    Program                                 RMMMBESTN
    Module type                             (FORM)
    Module Name                             EKPO_LESEN

Hi,
Please find the SAP notes. There are several notes for this.
Regards,

Regarding Dump Analysis

Similar Messages

Maybe you are looking for