UNCAUGHT_EXCEPTION in Aggregate activation
Hi,
We are activating and filling up the aggregate and we got the following error message:
ABAP/4 processor: UNCAUGHT_EXCEPTION
I checked the dump and the meeage is:
Runtime Errors UNCAUGHT_EXCEPTION
Exceptn CX_RSR_X_MESSAGE
ShrtText
An exception that could not be caught occurred.
What happened?
The exception 'CX_RSR_X_MESSAGE' was raised but was not caught at any stage in the call hierarchy.
Since exceptions represent error situations, and since the system could not react adequately to this error, the current program, 'SAPLRRMS', had to be terminated.
Any help would be greatly appreciated.
Regards
Nagendra
Hi,
It is a common memory error. fill the aggregates one at a time.
Also check the system load in SM37, when there are lot of processes running
in the system, trigger after some time when system load is less.
Check whether any dependent rollup or changerun is runnning before refilling.
If there are any running, refill after that.
there may be locks in the system, check for db locks and user locks.
****Don't cancel the job....inconsistency may occur for data.
Warm Regards,
Vijay
Similar Messages
-
Hi Experts
I am trying to create Aggregates on a Info Cube.
Go to t.code: RSDDV
select the IFC
In the Aggregation screen, select the characteristic that will be based on your aggregate (drag and drop)
When i try to Activate the Aggregates it showing me error
No aggregates selected for activation
Please help. You are in the Modeling function area of the Administrator Workbench.In the navigation window, choose InfoProvider.
2. In the InfoProvider tree, navigate to the InfoCube whose queries you want to optimize.
3. In the context menu for the InfoCube, choose Maintain Aggregate.This will bring you to the Maintain Aggregates screen.
If an aggregate was already created for the selected InfoCube, you can also go to the maintenance screen by double-clicking on .
If you create the first aggregate for an InfoCube, you will first go to the Proposals for Aggregates dialog box. You can define whether the system should propose aggregates or whether you want to create them manually.
4. The left side of the screen shows the dimensions, characteristics and navigation attributes of the selected InfoCube in a tree structure as Selection Options for Aggregates.
Select one or more objects to be copied to the aggregate.
Define the granularity you need for the data in the aggregate. Add all the characteristics derived from these characteristics.
For example if you define an aggregate for the month, you should also include the quarter and year in the aggregate.
This enhancement does not increase the data set, but permits
· a year aggregate to be built from this aggregate,
· those who need the annual values can also use queries of this aggregate.
You can only include a characteristic and one of its attributes in an aggregate in expert mode (Extras ® Switch expert mode on/off). Such an aggregate has the same granularity and size as an aggregate that was only built with the characteristic, but is affected by the hierarchy/attribute change run. Compared with the aggregate for the characteristic in which the attribute information is defined by a join with the master data table, the aggregate for the characteristic and the attribute only saves the database join.
We therefore recommend that you either build an aggregate using with the characteristic or you build a much smaller aggregate using the attribute.
5. You have different options for creating an aggregate:
· Transfer the selected object(s) to the Aggregates column on the right side of the screen using Drag&Drop.
· Select Create New Aggregate.
The Enter Description for Aggregate dialog box appears.
6. Enter:
Short Description
Long Description
To change the text at a later time, select Change Description Text from the context menu of the aggregate.
7. Choose Continue. You get to the Maintain Aggregates screen.
The system displays the aggregate at the upper right of the screen. The log is displayed in the lower part of the screen.
For more information see Displaying an Aggregate and its Components.
8. If an aggregate contains a time-dependent component, you must assign a key date to the aggregate.
When you fill the aggregate, the key date behaves like the key date of a query: The time-dependent attributes and hierarchies are evaluated on this key date. For this reason aggregates with a time-dependent component can only be used in a query if the key date of the query is the same as the key date of the aggregate.
In the Select Variable or Fixed Date dialog box select the following as key date:
· a variable that is also used in queries for the key date and can be automatically calculated in the SAP Exit or Customer Exit processing types (see Using Variables),
0CWD Current workday
0DAT Current calendar day
0P_KEYDT Key date of due date
0P_KEYD2 Key date of posting (from key date of due date)
0P_KEYD3 Key date of clearing (from key date of due date)
0P_KEYD4 Key date of posting (posting date)
0P_KEYD5 Key date of clearing (from key date of posting)
Aggregates with a variable key date must be updated regularly. This process must be included in a Process Chain (Further BW processes -> Adjust Time-Dependent Aggregates).
· A certain calendar day
To enter a calendar day, select object CALENDAR in the Select Variable or Fixed Date dialog box (). Choose Transfer selection. This takes you to the Calendar dialog box. You can copy this date to the aggregate definition by double-clicking.
The system displays the technical name of the variable you chose or of the fixed calendar date in the aggregate tree under Properties for node Variables for Key Date.
Once the aggregate has been activated and filled, the system copies the key date computed from the variable when the aggregate should be filled into the line Key Date.
9. You can change the structure of the aggregate by adding further components or deleting existing ones. You can also change the key date.
Inserting components into the aggregate
i. Select one or more objects in Selection Options for Aggregates.
ii. Transfer them to the aggregate to be changed at the right of the screen with Drag&Drop.
iii. As needed, change the Aggregation Level with the associated entry in the context menu:
All Characteristic Values
Hierarchy Level
Fixed Value
Aggregates containing fewer than 14 components are stored on the database in optimized form (see Efficiently Loading Data into Aggregates).
Note that the characteristics that are defined in the InfoCube are also included in the aggregate and thus increase the number of components even though they are not visible on the surface.
Deleting components from the aggregate
i. In the aggregate tree navigate to the characteristic(s) or navigation attributes you want to delete.
ii. Select these components.
iii. To delete the components from the aggregate you can:
- Choose Remove Components in the context menu.
- Copy the components to the left part of the screen with Drag&Drop.
To delete a dimension from an aggregate, you have to delete all the characteristics and navigation attributes of this dimension.
Changing the key date
i. In the aggregate tree under Properties, select node Variable for Key Date and choose Change from the context menu. You get to dialog box Select Variable or Fixed Date.
ii. Select and transfer the required variable or calendar date.
The key date computed from a changed variable is only copied to line Key Date when the Adjust Time-Dependent Aggregates process has been executed.
10. To check the aggregate definition for inconsistencies choose Check Definition.
11. Save the new or changed aggregate.
Edited by: Rama on Sep 24, 2008 12:03 PM -
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 0x100ed2d40HI 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.. -
How to select data from an aggregate in a customer exit for a query?
Hi,
I have written a virtual key figure customer exit for a query. Earlier the selection was from the cube, where there was severe performance issue. So I have created an aggregate, activated and have loaded the data.
Now when I select that data I find that the Key table is different in development and production. How do I resolve this.
My code is attached below. The table in developemnt is KEY_100027 and in production is KEY_100004. This code is activated and running in BW development server.
SELECT
F~KEY_1000041 AS K____035
F~KEY_1000271 AS K____035
F~QUANT_B AS K____051
F~VALUE_LC AS K____052
INTO (xdoc_date, xval1, xqty1)
UP TO 1 ROWS
FROM
FROM
*/BIC/E100004 AS F JOIN
/BIC/E100027 AS F JOIN
/BIC/DZMM_CGRNU AS DU
ON FKEY_ZMM_CGRNU = DUDIMID
JOIN /BI0/SUNIT AS S1
ON DUSID_0BASE_UOM = S1SID
JOIN /BI0/SCURRENCY AS S2
ON DUSID_0LOC_CURRCY = S2SID
JOIN /BI0/SMATERIAL AS S3
*ON FKEY_1000042 = S3SID
ON FKEY_1000272 = S3SID
JOIN /BI0/SMOVETYPE AS S4
*ON FKEY_1000043 = S4SID
ON FKEY_1000273 = S4SID
JOIN /BI0/SPLANT AS S5
*ON FKEY_1000044 = S5SID
ON FKEY_1000274 = S5SID
JOIN /BIC/D100004P AS DP
*ON FKEY_100004P = DPDIMID
ON FKEY_100027P = DPDIMID
WHERE
WHERE
( ( ( ( F~KEY_1000041 BETWEEN 20051230 AND 20060630 ) ) AND ( (
( ( ( ( F~KEY_1000271 BETWEEN 20051230 AND 20060630 ) ) AND ( (
S3~MATERIAL = <l_0material> ) ) AND ( (
s2~movetype BETWEEN '101' AND '102' OR
s4~movetype BETWEEN '921' AND '922' OR
s4~movetype BETWEEN '105' AND '106' OR
s4~movetype BETWEEN '701' AND '701' OR
s4~movetype BETWEEN '632' AND '632' ) ) AND ( (
S5~PLANT = <l_0plant> ) ) AND ( (
DP~SID_0RECORDTP = 0 ) ) ) )
GROUP BY
ORDER BY F~KEY_1000271 DESCENDING.
IF sy-subrc NE 0.
EXIT.
ENDIF.
ENDSELECT.
How do I transport the code and make it work?
Whats the reason that the two key fields are different.
I had transported the aggregate from development to production. Activated it and filled the data.
What is the way out? Please help.
Regards,
Annie.Hi Sonu,
The main task is to move the contents of the one internal table to another with some condition.
First sort and delete the duplicate entries from the First Internal table like below :
sort it_tab by material ascending date_modified descending.
delete adjacent duplicates from it_tab.
Then move that Internal table contents to another internal table.
Define another internal table with the same structure as you have first internal table and then
Second Step :
it_itab1 = it_itab.
If you are using seperate Header line and Body then you can do like below :
it_itab1[] = it_itab[].
This will fix the issue.
Please let me know if you need any further explonation.
Regards,
Kittu
Edited by: Kittu on Apr 24, 2009 12:21 PM -
Problem in Process chain due to Aggregate Roll-up
Hi,
I have a Infocube with Aggregates built on it. I have loaded data in the Infocube from 2000 to 2008, Rolled up & Compressed the aggregates for this.
I have also loaded the 2009 data in the same Infocube using Prior Month & Current Month Infopackage for which i am only Rolling up the aggregate and no Compression of aggregates is done. The Current & Prior month load runs through Process chain on a daily basis at 4 times per day. The Process chain is built in such a way that it deletes the overlapping requests when it is loading for the second/third/fourth time on a day.
The problem here is, when the overlapping requests are deleted, the Process Chain is also taking the Aggregates compressed requests (2000 to 2008 Data), de-compressing it, De-activating the aggregates, Activating the Aggregates again, Re-filling & compressing the aggregates again. This nearly takes 1 hour of time for the Process Chain to run which should take not more than 3 minutes.
So, what could be done to tackle this problem? Any help would be highly appreciated.
Thanks,
MuraliHi all,
Thanks for your reply.
Arun: The problem with the solution you gave is "Untill i roll-up the aggregates for the Current & Prior Month Infopackage the Ready for Reporting symbol is not appearing for the particular request".
Thanks,
Murali -
Hi,
I have an aggregate created about one infocube. This aggegate was working correctly but I have need desactivate it and I have removed the data by other issue already fixed. After resolve the issue, I want activate and fill the aggregate. This aggreate has status green now but in "Filled/switched off" is red and I can't fill this aggregate. I push "Activate and fill (F6)" but the job generated is cancelled in seconds with the following error (ST22):
Termination occurred in the ABAP program "SAPLRSENQ" - in "MIGRATE_IPRO_C".
The main program was "RSAGGR2 ".
Then the aggreate is active but empty...
Please, could you help me?
Thanks in advance.dbenitez wrote:
Hi,
>
> I have desactivate using F8 and the t-code RSATTR is completed succesfully, there are not change run process running. When I execute "Activate and Fill", the aggregate be active but empty.
>
> I will continue checking this issue.
>
> Thanks!
Check if there's any collisions in ACR. Goto SE37 > RSMODSTATEGET > Check if there's any entries; If yes, clear them using RSMODCLOSE*, else no issues. Goto the Maintain Aggregates & deactivate them completely till you see 2 red lights. Before activating them & filling them, check via RSRV. Ensure the data in cube (via manage tab) is complete in all aspects, i.e. no red requests etc. Don't leave any aggregates activated, but not filled. Use the function modules to perform rollup & check if the aggregates are working correctly. This must solve your case. -
RFC_ERROR_SYSTEM_FAILURE error in Planning Sequence in RSPLAN
Hi everyone,
Whenever we run the Planning Modeler in RSPLAN and choose any Planning Sequence either for changing or executing, or just selecting it the system throws the following error:
"An exception occurred that was not caught., error key: RFC_ERROR_SYSTEM_FAILURE", and retrieve a short dump.
This only occurs in all the planning sequences, which were working before without any issues, and this is only happening in BW development not in production.
The short dump goes like this:
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_RSR_X_MESSAGE
Active Calls/Events
No. Ty. Program Include Line
Name
23 FUNCTION SAPLRRMS LRRMSU13 73
RRMS_X_MESSAGE
22 METHOD CL_RS_BASE====================CP CL_RS_BASE====================CM004 7
CL_RS_BASE=>X_MESSAGE_S
21 METHOD CL_RSDRC_PROVRQ_SRVS==========CP CL_RSDRC_PROVRQ_SRVS==========CM004 122
CL_RSDRC_PROVRQ_SRVS=>GET_RQTS_BASIC
20 METHOD CL_RSD_DC_SUPPORT_INFOCUBE====CP CL_RSD_DC_SUPPORT_INFOCUBE====CM006 6
CL_RSD_DC_SUPPORT_INFOCUBE=>IF_RSD_DELTACACHE_SUPPORT~GET_RQTS
19 METHOD CL_RSD_CUBE===================CP CL_RSD_CUBE===================CM02R 26
CL_RSD_CUBE=>IF_RSD_DTA~GET_DATA_TIMESTMP
18 METHOD CL_RSD_DTA====================CP CL_RSD_DTA====================CM01K 3
CL_RSD_DTA=>IF_RSD_DTA~GET_DATA_TIMESTMP
17 METHOD CL_RSPLS_PLAN_BUFFER==========CP CL_RSPLS_PLAN_BUFFER==========CM00H 35
CL_RSPLS_PLAN_BUFFER=>IF_RSD_DELTACACHE_SUPPORT~GET_RQTS
16 METHOD CL_RSR_RRK0_RQTS==============CP CL_RSR_RRK0_RQTS==============CM003 118
CL_RSR_RRK0_RQTS=>APPEND_BUFFER
15 FUNCTION SAPLRRK0 LRRK0U23 33
RRK_BUFFER_NOTIFY
14 METHOD CL_RSR_OLAP===================CP CL_RSR_OLAP===================CM00X 44
CL_RSR_OLAP=>CREATE_BUFFER
13 METHOD CL_RSR_OLAP===================CP CL_RSR_OLAP===================CM002 65
CL_RSR_OLAP=>OPEN_KHANDLE
12 METHOD CL_RSR_OLAP===================CP CL_RSR_OLAP===================CM00M 15
CL_RSR_OLAP=>IF_RSR_OLAP~GET_SELDR
11 METHOD CL_RSBOLAP_SELECTION_OBJECT===CP CL_RSBOLAP_SELECTION_OBJECT===CM007 42
CL_RSBOLAP_SELECTION_OBJECT=>LOAD_DEFINITION
10 METHOD CL_RSBOLAP_SELECTION_OBJECT===CP CL_RSBOLAP_SELECTION_OBJECT===CM009 20
CL_RSBOLAP_SELECTION_OBJECT=>SUBMITTED
CL_RSBOLAP_SELECTION_OBJECT=>SUBMITTED
9 METHOD CL_RSR_OLAP_VAR===============CP CL_RSR_OLAP_VAR===============CM003 283
CL_RSR_OLAP_VAR=>IF_RSR_VAR_RUNTIME~SUBMIT
8 METHOD CL_RSR_VAR_RUNTIME============CP CL_RSR_VAR_RUNTIME============CM00Q 11
CL_RSR_VAR_RUNTIME=>IF_RSR_VAR_RUNTIME~SUBMIT
7 METHOD CL_RSPLFR_VAR_CONT============CP CL_RSPLFR_VAR_CONT============CM003 24
CL_RSPLFR_VAR_CONT=>SUBMIT_OLAP_VAR_CONT
6 METHOD CL_RSPLFR_VAR_CONT============CP CL_RSPLFR_VAR_CONT============CM007 175
CL_RSPLFR_VAR_CONT=>SCREEN_NECESSARY
5 METHOD CL_RSPLFR_CONTROLLER==========CP CL_RSPLFR_CONTROLLER==========CM00T 158
CL_RSPLFR_CONTROLLER=>CHECK_PLSEQ_SCREEN_NECESSARY
4 FUNCTION SAPLRSPLSSE LRSPLSSEU02 46
RSPLSSE_PLSEQ_EXECUTE
3 FORM SAPLRSPLSSE LRSPLSSEU02 1
RSPLSSE_PLSEQ_EXECUTE
2 FORM SAPMSSY1 SAPMSSY1 85
REMOTE_FUNCTION_CALL
1 MODULE (PBO) SAPMSSY1 SAPMSSY1 30
%_RFC_START
Does anyone have any idea what could be the issue here?
Thanks,
Diogo.Hi,
Thanks for the response.
I've already searched for that not but haven't installed it yet. I'm gonna try it to see if it solves it, but the weird thing is that in production the issue doesn't occur, only in development.
Diogo. -
Default order to access data in infocube
Hi all
Lets say we have aggregates activated and filled on infocubes, BIA is implemented and OLAP cache is activated how would the query access the data in the infocube ?
Does anyone know if the default order would be: first OLAP cache, BIA, agreggate and then Infocube ?
Thanks in advance
Rgds,
LBThe default order for the same is :
Query --> OLAP CACHE --> BIA --> Aggregates --> Cube.
If BIA Exists then the query runs completely off BIA and does not go into the next step...
Also you can check the SQl/BIA query generated for the query in RSRT debug mode for details...
Edited by: Arun Varadarajan on Dec 10, 2009 1:51 AM -
What do these background jobs stand for ?
Hello BW Experts,
These are the couple of background jobs prefixes that i need to analyse. Could you please suggest what these stand for ?
BIREQU
BI_AGGR4
BI_BTCH
BI_DELR
BI_HIER
BI_ODSA
BI_PROCESS_ABAP
BI_PROCESS_LOADING
BI_PROCESS_ODSACTIVAT
BI_PROCESS_TRIGGER
BI_PSAD
BI_REQD
BI_STAT
BI_STRU
BI_WRITE_PROT_TO_APPLLOG
RANATL_ACCT_CACHE_WARMUP
Suggestions appreciated.
Thanks,
BWerHi,
BIREQU - Load of a Request/Reconstruction of a request
BI_AGGR4 - Aggregates activation
BI_BTCH - Any batch job like ABAP program run in background
BI_DELR - Deletion of request
BI_HIER - Hierarchy loading/activation
BI_ODSA - ODS activation
BI_PROCESS_ABAP - ABAP program in process chain
BI_PROCESS_LOADING - Data Loading in process chain using nfopackage
BI_PROCESS_ODSACTIVAT - ODS actiavation in Process chain
BI_PROCESS_TRIGGER - Trigger job for process chain
BI_PSAD - probably PSA deletion
BI_STAT - Building statistics
BI_STRU - Change run job
BI_WRITE_PROT_TO_APPLLOG - Application log job
RANATL_ACCT_CACHE_WARMUP
Bye
Dinesh -
How can i create background jobs and link them to the Event so that they will be triggered? I have no clue on this, can anyone explain in a detailed manner with the Transaction codes for each.
Thanks in advance.Hi laitha,
JOB is a program which starts to a determined point of time and executes some standard programs in the system. JOBs can be planed to a determined point of time on the regular basis (every night, for example) or to some discret time moments. So, the JOB can be planed and then will be started automatically without the manual start.
Realtime programs are understood in the most cases as actual program execution which is started by somebody to the actual moment of time.
Typically per JOBs some special processes will be started that should be executed automatically and regularly: for example, IDOC application, some correction reports, statistic updates etc.
Standard jobs are those background jobs that should be run regularly in a production SAP System These jobs are usually jobs that clean up parts of the system, such as by deleting old spool requests.
Use
As of Release 4.6C, the Job Definition transaction ( sm36 ) provides a list of important standard jobs, which you can schedule, monitor, and edit.
Standard jobs are those background jobs that should be run regularly in a production SAP System. These jobs are usually jobs that clean up parts of the system, such as by deleting old spool requests.
for more information you can go thru the following thread:
http://help.sap.com/saphelp_nw70/helpdata/en/24/b884388b81ea55e10000009b38f842/frameset.htm
About Events:
Events have meaning only in the background processing system. You can use events only to start background jobs.
Triggering an event notifies the background processing system that a named condition has been reached. The background processing system reacts by starting any jobs that were waiting for the event.
Types of Events:
There are two types of events:
1.)System events are defined by SAP. These events are triggered automatically when such system changes as the activation of a new operation mode take place.
2.)User events are events that you define yourself. You must trigger these events yourself from ABAP or from external programs. You could, for example, signal the arrival of external data to be read into the SAP system by using an external program to trigger a background processing event.The event scheduler processes an event if the event is defined in the system.
For example, if a system (System 1) receives an event from another system (System 2), the event scheduler of System 1 processes the event only if it is defined in System 1. That event does not need to be defined in System 2 (the sending system).
You define an event by assigning a name (EVENTID) to it. When defining an event, you do not define the event arguments.
for more information you can go thru the following thread:
http://help.sap.com/saphelp_nw04s/helpdata/en/fa/096e2a543b11d1898e0000e8322d00/frameset.htm
When you schedule the process chain or infopackages the jobs associated with it run in the background mode. In case you want to create a job for a specific activity you can do so in SM36. You would be creating jobs that would get executed in any one of the options:
1. Immediate
2. Date & Time
3. After event.
4. After job.
5. At Operation mode.
In case you want to view the job logs go to sm37.
_List of Background Jobs_
BIREQU - Load of a Request/Reconstruction of a request
BI_AGGR4 - Aggregates activation
BI_BTCH - Any batch job like ABAP program run in background
BI_DELR - Deletion of request
BI_HIER - Hierarchy loading/activation
BI_ODSA - ODS activation
BI_PROCESS_ABAP - ABAP program in process chain
BI_PROCESS_LOADING - Data Loading in process chain using nfopackage
BI_PROCESS_ODSACTIVAT - ODS actiavation in Process chain
BI_PROCESS_TRIGGER - Trigger job for process chain
BI_PSAD - probably PSA deletion
BI_STAT - Building statistics
BI_STRU - Change run job
BI_WRITE_PROT_TO_APPLLOG - Application log job
RANATL_ACCT_CACHE_WARMUP
Use tcode SM62 to create User events.
Use tcode SM64 to trigger the event.
Wizards for Event Creation :pls chk this link
http://help.sap.com/saphelp_erp2005vp/helpdata/en/f7/d1c20a02d511d3a6550060087a79ea/frameset.htm
*pls assign points,if info is useful**
Regards
CSM reddy -
Aggregation time ...
Hi
We have one ZCube which is having around130 million records(around 33GB).
No aggregates are created on this cube.Now we are planning to create aggregates .
1)Appoximately, how much time will it take first time to fill up the aggregates(activation and fill up)
2)Before aggregation starts, do we need to stop the jobs that brings data to this cube
3)To what level will the performance of the queries be affected when aggregation starts..
Thanks,
TejaHi,
1)Appoximately, how much time will it take first time to fill up the aggregates(activation and fill up)
It depends on how many aggregates are created on your Infocube. I guess if you follow the hierarchy of the aggregates while doing the intial filling it will not take a max of 12 hrs to fill the aggregates.
2)Before aggregation starts, do we need to stop the jobs that brings data to this cube.
This is not needed. But the aggrgeate filling will create potential lock on the infocube while attribute change run is running. So better see to that you run it once your chnage run finished for the day.
3)To what level will the performance of the queries be affected when aggregation starts.
Reporting will be normal as ususal, as I presume that you were not using any aggregates before on this cube. If there were already aggregates on this then the query performace will be severely affected.
Hope this helps
Regards,
Srini -
Back end activities for Activation & Deactivation of Aggregates
Hi ,
Could any body help me to understand the back-end activites performed at the time of activation and deactivation of aggregates.
Is filling of Agreegate is same as Roll up?
What is the diffrence between de-activation and deletion of Aggregate?
Thanks.
SantanuHi Bose,
Activation:
In order to use an aggregate in the first place, it must be defined activated and filled.When you activate it, the required tables are created in the database from theaggregate definition. Technically speaking, an aggregate is actually a separate BasicCube with its own fact table and dimension tables. Dimension tables that agree with the InfoCube are used together. Upon creation, every aggregate is given a six-digit number that starts with the figure1. The table names that make up the logical object that is the aggregate are then derived in a similar manner, as are the table names of an InfoCube. For example, if the aggregate has the technical name 100001, the fact tables are called: /BIC/E100001 and /BIC/F100001. Its dimensions, which are not the same as those in the InfoCube,have the table names /BIC/D100001P, /BIC/D100001T and so on.
Rollup:
New data packets / requests that are loaded into the InfoCube cannot be used at first for reporting if there are aggregates that are already filled. The new packets must first be written to the aggregates by a so-called “roll-up”. In other words, data that has been recently loaded into an InfoCube is not visible for reporting, from the InfoCube or aggregates, until an aggregate roll-up takes place. During this process you can continue to report using the data that existed prior to the recent data load. The new data is only displayed by queries that are executed after a successful roll-up.
Go for the below link for more information.
http://sapbibw2010.blogspot.in/2010/10/aggregates.html
Naresh -
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. -
Hi Friends,
There are around 25 aggregates on a cube. When rollup was done today, it filled and activated 24 aggregates. One aggregate is showing red status and switched off. When I am trying to activate it manually, it is not activating. Could anybody advise.
Thanks and regards,
BalarajHi Balraj,
1.Deactivate the perticular aggregate.
2.Kill if the rollup job still running.
3.If any change run is using it.wait till it completes or kill it(not recomended)
4.deactivate and try activating again.
Regards,
Jagadeesh -
For direct activation of hierarchy, Aggregates have to be deactivated
Hi,
There are 2 monthly master data hierarchies loaded.
We face some problem while loading the hierarchies.
Now the 2 hierarchies are seen as Modified version.
When I try to activate the hierarchies manually I receive the below message
"For direct activation of hierarchy, 0042 Aggregates have to be deactivated"
with 2 options as:
1 Prebook activation
2 Activate directly
What are these options?
Will affect on aggregates?hi,
Activate directly wlll directly activate the hierarchy....
Prebook for activation will capture it and it will be activated later at the time of the chnage run.
Always prefer Prebook for activation...
hope this helps.
regards,
Mahesh
Edited by: Mony Maheshsingh on Jun 24, 2010 4:22 PM
Maybe you are looking for
-
Is it possible for a user to edit the output of a form before printing?
This might sound odd but the business have requested the ability to edit the text of a Smartform before printing. i.e. a standard form can be printed 'as is' for most employees but certain exceptions may require the wording to be slightly amended. I
-
How to I get my CTV app to work for my ipad
I downloaded the ctv app for my iPad and can get sound but no video display
-
Obsolate statement for function module TABLE_COMPRESS
Hi all, What is the alternate function module for TABLE_COMPRESS? This is going fine in 4.7 version. But in ECC 6.0, if we use this function module we r getting SLIN error (Obsolate statements) . How can we rectify this SLIN error? So we have to use
-
I have a big problem.Can anyoane help me? I had accidentaly delete all my database, i had recover the files with a recover tool but not the control files. Now i whant to recreate the controlfiles with the script: CREATE CONTROLFILE SET DATABASE "TEST
-
Can Outlook 2007 Calendar Appointments sync over the Air
Hi, I have an Iphone 3GS and i wonder if my Outlook 2007 calendar appointments sync over the air as my e-mails do.