ABAP/4 processor: UNCAUGHT_EXCEPTION - Activation job cancelled short dump

Hi All,
I loaded data to the new table of ODS successfully. But the data is not available for reporting.
When i try to activate the request,it shows no error bt neither does data *** to active table .I checkd in sm37 for logs, it shows ABAP/4 processor: UNCAUGHT_EXCEPTION error. It shows that CX_SDB_ORA_PROGRAM_ERROR exception was raised.
I also checked in table RSODSACTREQ in SE16 and found that status was 0 (means activation successful) n operation was U (means updating) .........
The same problem persists for activation job for any ODS.......The support package has been upgraded from 11 to 14 recently.......
Please help me resolve this issue.
Regards,

Prithi,
Check out for invalid char's in the PSA.....
Check monitoring for invalid char's .. some time it will reach up to New data table and while activation it may get struc...
hope there is some prob with invalid char's aor length of char.... Special char..like @__ in PSA .
Cheer's
HVR.

Similar Messages

ABAP/4 processor: UNCAUGHT_EXCEPTION while activation

Hi All,
I am getting this error "ABAP/4 processor: UNCAUGHT_EXCEPTION" while the activation of DSO. I am attaching the dump
Runtime Errors         UNCAUGHT_EXCEPTION
Exception              CX_SDB_ORA_PROGRAM_ERROR
Date and Time          19.12.2008 03:02:53
Short text
An exception occurred that was not caught.
What happened?
The exception 'CX_SDB_ORA_PROGRAM_ERROR' was raised, but it was not caught
anywhere along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CL_SDB_ORA_UPDATE_STATS=======CP' has to be
terminated.
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 which is explained in detail below.
The exception, which is assigned to class 'CX_SDB_ORA_PROGRAM_ERROR', was not
caught and
therefore caused a runtime error.
The reason for the exception is:
An error occurred in the program:
The occurrence of the exception is closely related to the occurrence of
a previous exception "CX_SQL_EXCEPTION", which was raised in the program
"CL_SQL_STATEMENT==============CP",
specifically in line 31 of the (include) program
"CL_SQL_STATEMENT==============CM002".
The cause of the exception was:
ORA-04031: unable to allocate 62208 bytes of shared memory ("shared
pool","DBMS_STATS","PL/SQL MPCODE","BAMIMA: Bam Buffer")
ORA-06508: PL/SQL:
could not find program unit being called: "SYS.DBMS_STATS"
ORA-06512: at line 1
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:
"UNCAUGHT_EXCEPTION" "CX_SDB_ORA_PROGRAM_ERROR"
"CL_SDB_ORA_UPDATE_STATS=======CP" or "CL_SDB_ORA_UPDATE_STATS=======CM00I"
"UPDATE_STATS"
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... "gwpsapci"
Network address...... "10.220.136.60"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "0005E935D600"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 30
Shortdump setting.... "full"
Database server... "de08u1642"
Database type..... "ORACLE"
Database name..... "GWP"
Database user ID.. "SAPR3"
Char.set.... "en_US.ISO8859-1"
SAP kernel....... 700
created (date)... "Aug 24 2008 21:05:40"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 175
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.... 16128
EM...... 25139520
Heap.... 0
Page.... 24576
MM Used. 12500304
MM Free. 4256248
User and Transaction
Client.............. 950
User................ "ZZSUPPORT"
Language key........ "E"
Transaction......... " "
Transactions ID..... "494AFB8FEB5A00D6E10080000ADC883C"
Program............. "CL_SDB_ORA_UPDATE_STATS=======CP"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "CL_SDB_ORA_UPDATE_STATS=======CP" -
in "UPDATE_STATS".
The main program was "RSPROCESS ".
In the source code you have the termination point in line 40
of the (Include) program "CL_SDB_ORA_UPDATE_STATS=======CM00I".
The program "CL_SDB_ORA_UPDATE_STATS=======CP" was started as a background job.
Job Name....... "BI_PROCESS_ODSACTIVAT"
Job Initiator.. "E442207"
Job Number..... 03030600
Source Code Extract
Line
SourceCde
10
i_tablnm      = i_tablnm
11
i_signi       = i_signi
12
i_thresh_mod = i_thresh_mod
13
i_degree      = i_degree
14
i_histo       = i_histo
15
i_granularity = i_granularity
16
i_cascade     = i_cascade
17
i_force       = i_force
18
i_flush       = i_flush
19
i_connection = i_connection.
20
21
    Update Statistics
22
IF l_r_upd_stats->p_skip_upd IS initial.
23
CASE l_r_upd_stats->p_granularity.
24
WHEN 0. " DEFT
25
IF l_r_upd_stats->global_update_stats( ) = 'NO'.
26
l_r_upd_stats->part_update_stats( ).
27
ENDIF.
28
WHEN 1. " ALL
29
l_r_upd_stats->global_update_stats( ).
30
WHEN 2. " GLOBAL
31
l_r_upd_stats->global_update_stats( ).
32
WHEN 3. " PART
33
l_r_upd_stats->part_update_stats( ).
34
WHEN OTHERS. " AUTO
35
l_r_upd_stats->global_update_stats( ).
36
ENDCASE.
37
ENDIF.
38
39
CATCH cx_sql_exception INTO l_r_exception.
>>>>>
RAISE EXCEPTION TYPE cx_sdb_ora_program_error
41
EXPORTING previous = l_r_exception.
42
CLEANUP.
43
TRY.
44
CATCH cx_sql_exception INTO l_r_exception.
45
RAISE EXCEPTION TYPE cx_sdb_ora_program_error
46
EXPORTING previous = l_r_exception.
47
ENDTRY.
48
ENDTRY.
49
50
ENDMETHOD.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
0
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Process Variant Run
SY-MSGTY
E
SY-MSGID
DA
SY-MSGNO
300
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20081219
SY-UZEIT
030252
SY-XPROG
SAPCNVE
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
6 METHOD       CL_SDB_ORA_UPDATE_STATS=======CP    CL_SDB_ORA_UPDATE_STATS=======CM00I    40
CL_SDB_ORA_UPDATE_STATS=>UPDATE_STATS
5 FUNCTION     SAPLRSDU_UTIL_ORA                   LRSDU_UTIL_ORAU01                      86
RSDU_ANALYZE_TABLE_ORA
4 FUNCTION     SAPLRSDU_UTIL                       LRSDU_UTILU01                          38
RSDU_ANALYZE_TABLE
3 FUNCTION     SAPLRSSM_PROCESS                    LRSSM_PROCESSU30                     1476
RSSM_PROCESS_ODSACTIVATE
2 METHOD       CL_RSSM_ODSACTIVATE===========CP    CL_RSSM_ODSACTIVATE===========CM007   117
CL_RSSM_ODSACTIVATE=>IF_RSPC_EXECUTE~EXECUTE
1 EVENT        RSPROCESS                           RSPROCESS                             144
START-OF-SELECTION
Chosen variables
Name
Val.
No.       6 Ty.          METHOD
Name CL_SDB_ORA_UPDATE_STATS=>UPDATE_STATS
I_TABLNM
/BIC/AOD13ITM340
244424443345433322222222222222
F293F1F41394D34000000000000000
I_SIGNI
5775488
0
0
I_THRESH_MOD
0
0000
0000
I_DEGREE
3
0000
0003
I_HISTO
2
0
I_GRANULARITY
0
0000
0000
I_CASCADE
0
0000
0000
I_FORCE
2
0
I_FLUSH
X
5
8
I_CONNECTION
222222222222222222222222222222
000000000000000000000000000000
SPACE
2
0
L_R_UPD_STATS
|
| 0000000F |
| 80000027 |
| %_DUMMY$$ |
| |
| 2222 |
| 0000 |
| SY-REPID |
| CL_SDB_ORA_UPDATE_STATS=======CP |
| 4455445454555445455545533333334522222222 |
| 3CF342FF21F504145F34143DDDDDDD3000000000 |
| SY-XFORM |
| CONVERSION_EXIT |
| 444545544454545222222222222222 |
| 3FE65239FEF5894000000000000000 |
| L_R_EXCEPTION |
|
E0000001
80000037
SYST
#######################################################A#######ÿ###############(##############
000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
SY
#######################################################A#######ÿ###############(##############
000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
%_EXCP
E0000001
70000038
%_SPACE
2
0
SYST-REPID
CL_SDB_ORA_UPDATE_STATS=======CP
4455445454555445455545533333334522222222
3CF342FF21F504145F34143DDDDDDD3000000000
No.       5 Ty.          FUNCTION
Name RSDU_ANALYZE_TABLE_ORA
I_ALL_COLUMNS
2
0
I_FORCE_ESTIMATE
X
5
8
I_FORCE_STATISTICS
2
0
I_PERCENTAGE
1
0000
0001
I_PERCENTAGE_SPECIFIED
X
5
8
I_TABLNM
/BIC/AOD13ITM340
244424443345433322222222222222
F293F1F41394D34000000000000000
I_TEMP_TABLE
2
0
I_T_TABLNM
Table[initial]
C_PROCESSED
2
0
SY-REPID
SAPLRSDU_UTIL_ORA
5454554555544545422222222222222222222222
310C2345F549CFF2100000000000000000000000
<L_TABLNM>
/BIC/AOD13ITM340
244424443345433322222222222222
F293F1F41394D34000000000000000
SYST-REPID
SAPLRSDU_UTIL_ORA
5454554555544545422222222222222222222222
310C2345F549CFF2100000000000000000000000
%_SPACE
2
0
SY
#######################################################A#######ÿ###############(##############
000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
%_DUMMY$$
2222
0000
L_SIGNI
5775488
0
0
L_PARALLEL_DEGREE
3
0000
0003
L_HISTO
2
0
L_FLUSH
X
5
8
SY-ONCOM
S
5
3
No.       4 Ty.          FUNCTION
Name RSDU_ANALYZE_TABLE
I_FORCE_ESTIMATE
X
5
8
I_FORCE_STATISTICS
2
0
I_PERCENTAGE
1
0000
0001
I_TABLNM
/BIC/AOD13ITM340
244424443345433322222222222222
F293F1F41394D34000000000000000
I_TEMP_TABLE
2
0
I_T_TABLNM
Table[initial]
SYST-REPID
SAPLRSDU_UTIL
5454554555544222222222222222222222222222
310C2345F549C000000000000000000000000000
RSDU_C_OBJTYPE-VIEW
VIEW
5445
6957
L_DBFUNC
RSDU_ANALYZE_TABLE_ORA
554554444554554444545422222222
2345F1E1C9A5F412C5FF2100000000
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
L_PERCENTAGE_SPECIFIED
X
5
8
%_VIASELSCR
0
4
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
L_PROCESSED
2
0
RS_C_FALSE
2
0
SY-SUBRC
0
0000
0000
SCREEN
%_17NNS0000194530_%_%_%_%_%_%_
2533445333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
5F17EE30000194530F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
SY-REPID
SAPLRSDU_UTIL
5454554555544222222222222222222222222222
310C2345F549C000000000000000000000000000
L_MESSAGE
222222222222222222222222222222222222222222222222222222222222222222222222
000000000000000000000000000000000000000000000000000000000000000000000000
No.       3 Ty.          FUNCTION
Name RSSM_PROCESS_ODSACTIVATE
I_CRT_ACTIVATION
2
0
I_DROP_CREA_SEC_IND
2
0
I_INSTANCE
ODSA_4C7HUKHW8WV06KLJFFYZP95BW
445453434544535533444445553345
F431F43785B8787606BCA669A09527
I_JOBNAME
BI_PROCESS_ODSACTIVAT
44555444555445445454522222222222
29F02F3533FF43134961400000000000
I_LOG_ID
4C7HSJQKN58AR2DG5NSOGNB5O
3434545443345344345444434
43783A1BE58122475E3F7E25F
I_NO_CONDENSE
2
0
I_ODSOBJECT
OD13ITM3
443345432222222222222222222222
F41394D30000000000000000000000
I_PARENT_BATCH_ID
222222222222222222222222222222
000000000000000000000000000000
I_SERIALIZE
2
0
I_T_REQUEST_SEL
Table[initial]
I_VARIANT
OD13ITM3_ACTIVATE
443345435445454542222222222222
F41394D3F134961450000000000000
I_WITH_COMMIT
X
5
8
E_ERROR
2
0
E_RNR
ODSR_4C7HULKAVPVJRPAS8MAP3IYWS
445553434544455545545344534555
F432F43785CB1606A20138D1039973
E_T_ACTIVATE_RNR
Table[initial]
E_T_ERROR_RNR
Table[initial]
E_T_MSG
Table IT_18345[3x704]
CLASS=CL_RSSM_ODSACTIVATEMETHOD=IF_RSPC_EXECUTE~EXECUTEDATA=L_T_MSG_PROC
Table reference: 123
TABH+ 0(20) = 07000000A05FD4B0000000000000000000000000
TABH+ 20(20) = 0000007B000047A900000003000002C0FFFFFFFF
TABH+ 40(16) = 0400012500000D40001024C401800000
store        = 0x07000000A05FD4B0
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 123   (0x0000007B)
label        = 18345 (0x000047A9)
fill         = 3     (0x00000003)
leng         = 704   (0x000002C0)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000050
occu         = 16    (0x00000010)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
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         = 0x07000000A05750F0
pgHook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 10517 (0x00002915)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x00000010)
lineAlloc    = 16    (0x00000010)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x00000001)
>>>>> 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
E_T_ODSR_RNR
Table[initial]
L_LINES
0
0000
0000
%_DUMMY$$
2222
0000
SCREEN
%_17NNS0000194530_%_%_%_%_%_%_
2533445333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
5F17EE30000194530F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
SY-REPID
SAPLRSSM_PROCESS
5454555455544455222222222222222222222222
310C233DF02F3533000000000000000000000000
SY-MSGID
DA
44222222222222222222
41000000000000000000
G_CHANGED
2
0
SPACE
2
0
SY-MSGNO
300
333
300
SY-MSGV1
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV3
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
L_PERFORMED_ANALYZE
2
0
G_R_ALV_GRID
F0000000
F0000000
RS_C_TRUE
X
5
8
L_S_ODSTABNAME-M_TAB
/BIC/AOD13ITM340
244424443345433322222222222222
F293F1F41394D34000000000000000
SYST
#######################################################A#######ÿ###############(##############
000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
<%_TABLE_RSDS>
RSAU_C_PROTCLASS
1234
3333
1234
SYST-REPID
SAPLRSSM_PROCESS
5454555455544455222222222222222222222222
310C233DF02F3533000000000000000000000000
G_BUTTON_REQUDEL
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_SPACE
2
0
No.       2 Ty.          METHOD
Name CL_RSSM_ODSACTIVATE=>IF_RSPC_EXECUTE~EXECUTE
I_VARIANT
OD13ITM3_ACTIVATE
443345435445454542222222222222
F41394D3F134961450000000000000
I_EVENT_START
RSPROCESS
55554445522222222222222222222222
2302F353300000000000000000000000
I_EVENTP_START
4BO77YTX6F8UVLQ22AEHHYIPO
3443355534355453344445454222222222222222222222222222222222222222
42F7794866856C1221588990F000000000000000000000000000000000000000
I_JOBCOUNT
03030600
33333333
03030600
I_BATCHDATE
20081218
33333333
20081218
I_BATCHTIME
030306
333333
030306
I_T_PROCESSLIST
Table IT_123[18x528]
PROGRAM=RSPROCESSDATA=G_T_PROCESSLIST
Table reference: 37
TABH+ 0(20) = 07000000A02596D8000000000000000000000000
TABH+ 20(20) = 000000250000007B0000001200000210FFFFFFFF
TABH+ 40(16) = 040000740000116800102CC421800000
store        = 0x07000000A02596D8
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 37    (0x00000025)
label        = 123   (0x0000007B)
fill         = 18    (0x00000012)
leng         = 528   (0x00000210)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000069
occu         = 16    (0x00000010)
access       = 1     (ItAccessStandard)
idxKind      = 1     (ItIndexLinear)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x07000000A0262CF0
pgHook       = 0x07000000A0258600
idxPtr       = 0x07000000A0259788
shmTabhSet   = 0x0000000000000000
id           = 93    (0x0000005D)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 32    (0x00000020)
lineAlloc    = 32    (0x00000020)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x00000001)
>>>>> 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
I_LOGID
4C7HSJQKN58AR2DG5NSOGNB5O
3434545443345344345444434
43783A1BE58122475E3F7E25F
I_T_VARIABLES
Table[initial]
I_SYNCHRONOUS
2
0
I_SIMULATE
2
0
I_REPAIR
222222222222222222222222222222
000000000000000000000000000000
I_BATCHID
222222222222222222222222222222
000000000000000000000000000000
E_INSTANCE
ODSA_4C7HUKHW8WV06KLJFFYZP95BW
445453434544535533444445553345
F431F43785B8787606BCA669A09527
E_STATE
2
0
E_EVENTNO
00
33
00
E_HOLD
2
0
SY-REPID
CL_RSSM_ODSACTIVATE===========CP
4455554544544545454333333333334522222222
3CF233DFF4313496145DDDDDDDDDDD3000000000
<%_L003>-RNR
L_T_REQUESTS
Table[initial]
L_S_REQUESTS
222222222222222222222222222222
000000000000000000000000000000
SY-SUBRC
0
0000
0000
SYST-REPID
CL_RSSM_ODSACTIVATE===========CP
4455554544544545454333333333334522222222
3CF233DFF4313496145DDDDDDDDDDD3000000000
ICON_GREEN_LIGHT
@08@
4334
0080
L_JOBNAME
BI_PROCESS_ODSACTIVAT
44555444555445445454522222222222
29F02F3533FF43134961400000000000
L_S_SELE-NO_CONDENSE
2
0
L_S_ODS-OBJECT
OD13ITM3
443345432222222222222222222222
F41394D30000000000000000000000
L_S_SELE-ODSACTSERIAL
2
0
L_ERROR_PROC
2
0
L_T_MSG_PROC
Table IT_18345[3x704]
L_T_MSG
Table[initial]
No.       1 Ty.          EVENT
Name START-OF-SELECTION
G_VARIANT
OD13ITM3_ACTIVATE
443345435445454542222222222222
F41394D3F134961450000000000000
G_TYPE
ODSACTIVAT
4454454545
F431349614
%_DUMMY$$
2222
0000
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
G_OBJECT
CL_RSSM_ODSACTIVATE
445555454454454545422222222222
3CF233DFF431349614500000000000
G_INSTANCE
222222222222222222222222222222
000000000000000000000000000000
SY
#######################################################A#######ÿ###############(##############
000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
%_SPACE
2
0
%_REPAIR_%_APP_%
222222222222222222222222222222
000000000000000000000000000000
G_STATE
2
0
G_EVENTID
RSPROCESS
55554445522222222222222222222222
2302F353300000000000000000000000
G_HOLD
2
0
G_EVENTPARM
4BO77YTX6F8UVLQ22AEHHYIPO
3443355534355453344445454222222222222222222222222222222222222222
42F7794866856C1221588990F000000000000000000000000000000000000000
G_JOBCOUNT
03030600
33333333
03030600
G_BATCHDATE
20081218
33333333
20081218
G_EVENTNO
00
33
00
G_BATCHTIME
030306
333333
030306
G_T_VARIABLES
Table[initial]
G_T_PROCESSLIST
Table IT_123[18x528]
%F007017_1000
Log ID (Internal Use Only)
46624422467676662576246672222222222222222222222222222222222222222222222222222222222
CF7094089E452E1C05350FEC99000000000000000000000000000000000000000000000000000000000
G_LOGID
4C7HSJQKN58AR2DG5NSOGNB5O
3434545443345344345444434
43783A1BE58122475E3F7E25F
G_CHAIN
ZLIS_13_VDITM
5445533554454222222222222
AC93F13F6494D000000000000
G_REPAIR
222222222222222222222222222222
000000000000000000000000000000
G_BATCHID
INFO_4C7HUKA7PY9ANY239LWNF76M4
444453434544355344533345443343
9E6FF43785B170991E9239C7E676D4
Internal notes
The termination was triggered in function "raiseExcp"
of the SAP kernel, in line 2099 of the module
"//bas/700_REL/src/krn/runt/abexcp.c#7".
The internal operation just processed is "EXCP".
Internal mode was started at 20081219030246.
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      = 1073741312
=> File size limit = unlimited
=> Heap address = 0x1154fc6a0
=> Stack address = 0xfffffffffffb080
=> Stack low     = 0xfffffffffffb080
=> Stack high    = 0xffffffffffff880
=> Stack Trace:
     AixStack() at 0x1000a2474
     CTrcStack2() at 0x1000a256c
     rabax_CStackSave__Fv() at 0x1000d0e3c
     ab_rabax() at 0x1000cd81c
     raiseExcp__F6HeadId() at 0x100429ba0
     ab_jexcp__Fv() at 0x100428d30
     ab_extri__Fv() at 0x10038e6dc
     ab_xevent__FPCc() at 0x100ab5cc4
     ab_trigg__Fv() at 0x100ab59b0
     ab_run() at 0x1014d42dc
     N_ab_run() at 0x100ed3f4c
     dynpmcal() at 0x100ed2d40

HI karthik..
The Error Msg is due to insufficient memory while storing the Data in Database(i,e ODS) and this error UNCAUGH EXCEPTION will come due to " like there is an exception raised but no code to catch it(to activate the ODS)".
so chk the problem with the Basis People... those guys can give clear info pertaining to this kind of problems...
Genereally in our case we raise ticket to Basis people..
hope useful....
cheers
Sukhai..

BC Activation Jobs Cancelled

I had a couple of BC activation jobs fail overnight because the server was shut down.
In the Admin Workbench all of the objects are active (green lights).
Any advice on what I should do? I'm tempted to start the activation again but if all of the objects are active do I need to?

Hi,
My advice is restarting. Because the job was failed , few objects would have not been activated properly. So it is better to do it again.
With rgds,
Anil Kumar Sharma .P

Job SAP_COLLECTOR_FOR_PERFMONITOR - short dump (DBIF_SETG_SQL_ERROR)

Hi gurus,
Good day.
I would like to ask for your help with regard to the short dump that we experienced with Job SAP_COLLECTOR_FOR_PERFMONITOR (program RSCOLL00). The error is DBIF_SETG_SQL_ERROR.
Date       Time     Message text
24.11.2008 02:30:39 Job started
24.11.2008 02:30:39 Step 001 started (program RSCOLL00)
24.11.2008 02:30:44 ABAP/4 processor: DBIF_SETG_SQL_ERROR
24.11.2008 02:30:44 Job cancelled
ORA-01455 is said to be the reason why we encountered DBIF_SETG_SQL_ERROR.
Database error text........: "ORA-01455: converting column overflows integer datatype"
Can you advise an OSS Note or certain solution that can fix this issue? Thank you very much!

This looks like an SAP Upgrade ECC 6 Problem, right?
Do you have any idea where I can check the date when the ECC 6 upgrade or patch has been made?
I'm an ABAPer and to be honest, currentlly, I don't have any idea if the client really did an ECC 6 upgrade --- when they did it. I will just check the table that you sent.
I just had the impression that it might be due to an ECC 6 Upgrade since I saw this case over the Internet:
"DBIF_SETG_SQL_ERROR" and "ORA-03106: fatal two-task communication protocol error" after ERP 6.0 Upgrade ( http://sap.ittoolbox.com/groups/technical-functional/sap-basis/dbif_setg_sql_error-and-ora-03106-fatal-two-task-communication-protocol-error-after-erp-60-upgrade-1640408 ).
Yes, we are also experiencing DBIF_SETG_SQL_ERROR (ORA-03106). But, I'm taking care of DBIF_SETG_SQL_ERROR (ORA-01455).
By the way, I saw that jobs EU_PUT and EU_REORG are being executed in background every morning at around 1 AM. And we are receiving the error DBIF_SETG_SQL_ERROR (ORA-01455) at around 2 AM - 3 AM, and a few at around 3 AM - 5 AM.
With these I have two questions:
(1) Do you think we still need to rerun EU_PUT and EU_REORG? Perhaps before 2 AM ?
(2) Do you think this is a Basis Issue and nothing to do with ABAP anymore?
Thank you very much!

DSO Activation Job cancelled.

Hi ,
I loaded data to DSO and activated.
It took lot of time for activation so i cancelled the job of activation (Partially activated )and also started the deletion of the request.
Now deletion request also takes lot of time?
What is the best way to delete the request and what to do with existing deletion request?
Thanks and Regards,
MuraliManohar

Hello ,
if u want to delete previus request.........
create a process chain...... to load data from source system to PSA and then TO ODS...........in this process chain you can include process type "Delete previous request from PSA.............so that you dont store much data in PSA.........if you are doing full load on ODS ...u can delete the contents of ODS with process type Delete Contents of InfoProvider(for small data) ......
Another Method :
Dirctly from DSO you can delete particular request or at the table level also you can delete the request from the any data target.
Goto SE16 -> RSICCONT - > Provide the DSO Name and execute -> List of reuests in the DSO will be displayed->select u r request and delete it.
Hope it helps.
Regards
Vikas Sharma
Robert Bosch

Short dump Error-ABAP/4 Run time Error

Hi Expert,
Dump:ABAP/4 Processor:MESSAGE_TYPE_X Why this error came,I would like to Investigation on Perticular error,Please Some body give me an Exact answer,so that i closed the ticket.
Regards,
Raju.

Hi Suresh,
What is the actual issue?
When did you get this error.
To know about this type of error, check below link...
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=dump%3aABAP%2F4Processor%3A+MESSAGE_TYPE_X&adv=false&sortby=cm_rnd_rankvalue
Also check this:
Note 1016317 - SP13:PC: Start type 'Date & time' gets scheduled wrong
"Process chain scheduling results in dump- ABAP/4 processor: MESSAGE_TYPE_X"
Solution:
In the short dump analysis, the process fails at function module
RSS2_PSA_NEW_OLD_DS
call function 'RSDS_DATASOURCE_SINGLE_GET'
Regards,
KK.

Error when executing APD-Job cancelled after system exception ERROR_MESSAGE

Hi,
We have a process chain which executes a APD using an ABAP program RSAN_PROCESS_EXECUTE.
It was executing successfully until few days back but now a days frequently once in 3 days roughly it is getting cancelled during execution of ABAP Program with the message 'Job cancelled after system exception ERROR_MESSAGE'
checked st22 and sm21 but didn't get any clue.But if we execute the same process chain manually(Immediate load) it is working fine all the times.
What may be the reason for the cancellation of the chain sometimes and the same chain working fine some other time and working very much fine when ran manually.
Regards,
Vishnu

Hi Vishnu,
Can you check if there are any other process which is triggering the abap program RSAN_PROCESS_EXECUTE at the same time as the execution of this process in the chain. You can check in which other chains this process is being used. You can compare the time when this failed in the chain you mentioned with the same being run in other chains at the same time.
Sasi

Short Dump Error while loading master data.

Hello All,
I am trying to load data from PSA to Info Object (0Material_Attr) via DTP, I am getting error and itu2019s giving the short dump.
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_RSR_X_MESSAGE.
"UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
"SAPLRRMS" or "LRRMSU13"
"RRMS_X_MESSAGE".
In Job overview, job is getting cancelled, with error message
"The object name is not allowed to be empty".
ABAP/4 processor: UNCAUGHT_EXCEPTION.
We have done the following steps, even then error persist.
Transaction RSRV > All Elementary Tests > Master Data > Compare Number Range and Maximum SID for the characteristic 0REQUID.
If the system reports an error here, correct the error using the "Correct Error" function.
Kindly suggest.
Thanks in Advance .

Error analysis from ST22
An exception occurred which is explained in The exception, which is assigned to class ' and therefore caused a runtime error.
The reason for the exception is: No text available for this exception
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:
"UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
"SAPLRRMS" or "LRRMSU13"
"RRMS_X_MESSAGE"

Short Dumps - How to find out in which process it occured.

Hi,
I see quiet a bunch of short dumps in ST22. Like "Message Type X". I wanted to find out in which job/process short dumps have occured?
Please help me out...
Thanks in Advance....:)
Regards,
Habeeb

Hi ,
The simplest way is to double click on a particluar dump in st22 and go in details like -What happened? ,What can you do?,How to correct the error etc .
there were plenty of options available according ot that u can dig out the error and find out the cause
(tip-usually job were failed due to some Z programs ,so better way is to search for Z* ,it will give the related object or program in most of the cases.)
hope it helps....
Regards,
Chetan R

Short Dump : ABAP/4 Processor:Syntax_Error

Hello All,
I scheduled one chain and while activating the ODS it gave the Short Dump
ABAP/4 Processor:Syntax_Error.
Then i tried to change the delete the request freom ODS after changing its status to RED.
But while deleting also it is giving the same dump.
I am unable to delete the request also.
In sm37 following messeges were there in logs.
Job started
Step 001 started (program RSODSACT1, variant &0000000005515, us
Activation is running: Data target MPU09O74, from 19.886 to 19.
Data to be activated successfully checked against archiving obj
SQL: 20.11.2007 09:02:49 PJAIN
ANALYZE TABLE "/BIC/AMPU09O7440" DELETE
STATISTICS
SQL-END: 20.11.2007 09:02:49 00:00:00
SQL: 20.11.2007 09:02:49 PJAIN
BEGIN DBMS_STATS.GATHER_TABLE_STATS ( OWNNAME =>
'SAPEBF', TABNAME => '"/BIC/AMPU09O7440"',
ESTIMATE_PERCENT => 1 , METHOD_OPT => 'FOR ALL
INDEXED COLUMNS SIZE 75', DEGREE => 1 ,
GRANULARITY => 'ALL', CASCADE => TRUE ); END;
SQL-END: 20.11.2007 09:02:51 00:00:02
SQL: 20.11.2007 09:02:51 PJAIN
ANALYZE TABLE "/BIC/AMPU09O7400" DELETE
STATISTICS
SQL-END: 20.11.2007 09:02:51 00:00:00
SQL: 20.11.2007 09:02:51 PJAIN
BEGIN DBMS_STATS.GATHER_TABLE_STATS ( OWNNAME =>
'SAPEBF', TABNAME => '"/BIC/AMPU09O7400"',
ESTIMATE_PERCENT => 1 , METHOD_OPT => 'FOR ALL
INDEXED COLUMNS SIZE 75', DEGREE => 1 ,
GRANULARITY => 'ALL', CASCADE => TRUE ); END;
SQL-END: 20.11.2007 09:02:51 00:00:00
ABAP/4 processor: SYNTAX_ERROR
Job cancelled

See the dump in ST22 for details.

ABAP Dump and JOb cancelled in BW

Hi to all,
I do have one job cancelled in BW:
BI_SAGR45WPN8MGGSB8EPABT8U5K3B6B
Job Log:
DROP INDEX "/BIC/F100300~090"
SQL-END: 01.06.2007 05:02:07 00:00:00
ABAP/4 processor: SAPSQL_INVALID_TABLENAME
Job cancelled
I think this is an aggregation job. Also, I see a dump in ST22:
Runtime Error SAPSQL_INVALID_TABLENAME
Exception CX_SY_DYNAMIC_OSQL_SEMANTICS
These two scenario are somehow related.
I've checked on RSA1 - Monitoring, everything seems to be fine.
Can anyone suggest on possible further checks needed on this scenario. Thanks.

HI,
I think the issue is with one of the aggregates which you have defined in the post as F10****, go in the aggregates maintainence and you have to deactivate the particular aggregate and then run the aggregate job or the change run job what ever is required.
This issue basically happens when there are large number of change in the aggregates and because of this they are nor able to be completed in the maximum runtime of the WP.
Hope this help,
Samved

ABAP/4 processor: SPOOL_I/O_ERROR in job RVV05IVB

Hi
I was getting error ABAP/4 processor: SPOOL_I/O_ERROR in job RVV05IVB which ran for almost for 10 days in our production system. That job if i am not wrong is used for the reorganization of index in SD document. But in the end it got canceled with ABAP/4 processor: SPOOL_I/O_ERROR . I try to search this but did not get anything.
Is that related to the spool (Temse object).
Please suggest
Thanks
Rishab

Hi,
Check SAP Note 1336 - Spooler reports data base I/O error.
In addition to that as said earlier check Temse consistency check.
Thanks
Sunny

How to Fetch Cancelled Jobs info along with the Short Dump Text

Hi Gurus,
I need to develop a report to fetch the cancelled jobs information for the given period. I also need to display the "Error Analysis" part of the Short Dump if it exists.
I am able to fetch the Failed Jobs information and the Job log details using the FM "BP_JOBLOG_READ". But I need to show the "Error Analysis Text" on the report , if there is any Short Dump Exists for the Dump.
Please give me your ideas to fetch the Error Analysis part of the short dump for a given Batch Job Name.
Thanks in Advance.
Best Regards,
Sumalatha

The dump information is in table SNAP. You could identify which dump you want by the date & time of the failed job - let's hope you don't have more than one dump with the same time. If it is ambiguous you could also compare the program name of the failed step with the program name in the SNAP data.
The error analysis texts are in table SNAPT keyed according to which error occurred (which is data element code FC right at the start of the first record in the SNAP data). You will have to expand out the includes, and substitute the variable codes using values from the SNAP data. There is standard code to do this that you could copy - see program SAPMS380.
To find out the details of the SAP process you could run transaction ST22 via the debugger and use the same mechanism.
best wishes
Ed
PS Note these details apply to recent systems I think there may be differences if you go back to before ?2004, but I don't have such a system so can't check. You didn't say what release you have.

Data Load Short Dump (ABAP/4 processor: ASSIGN_TYPE_CONFLICT)

Hi Experts,
I made few changes to the exisisting data target and transported it to Test system...
Today when i loaded test data i got Dump: ABAP/4 processor: ASSIGN_TYPE_CONFLICT error
Now i need to reactivate the Transformations and DTP's that will fix the error
What is the reason for this error
Thanks

Yes, you are correct, you need to activate your transformation and then DTP to get rid of this error.
The reason for this error is inconsistency b/w transformation and DTP.If you have made any changes to trasforamtion and activated it, then you need to activate the DTP also. If you are loading the data without DTP activation, you will get this error. This is because the DTP is build on transformation.
Thanks...
Shambhu

Background jobs failing with ABAP/4 processor: RFC_CONVERSION_FIELD

Hi Guru's,
Below are the backgroud jobs failing with runtime Error " ABAP/4 processor: RFC_CONVERSION_FIELD" in solution manager system (solution manager 3.0,SR2). Not sure why all these jobs failing with this dump on of sudden. i haven't made any changes to the system in the recent past.
BTC_CMS_COLLECTOR
SAP_APPLICATION_STAT_COLLECTOR
SESS_Y000001806_COLL_TRANS
ABAp Dump says that
Conversion error between two character sets
What happened?
Conversion error "ab_rfccon" from character set 4103 to character set 1100.
When executing a remote function call a conversion error occurred. This
occurred when receiving or sending the data. The conversion error can
only appear, when the data is transferred from a Unicode system to a
non-Unicode system.
Could some one please share some information if any one experienced the issue. Please note that all of our ECC systems are uni-code systems.
Thanks & Regards,
Vinod.

Hi Vinod
Just try to understand the purpose of these jobs and may be these Notes will help you
Note 814707 - Troubleshooting for RFC connections Unicode/non-Unicode
Note 647495 - RFC for Unicode ./. non-Unicode Connections
Note 1361970 - Conversion problems during RFC communication

ABAP/4 processor: UNCAUGHT_EXCEPTION - Activation job cancelled short dump

Similar Messages

Maybe you are looking for