on 08-12-2010 5:30 PM
Hi All,
Currently, we have been in the process of activating BI Content mostly 3.x flows within our new development system.
including cubes 0FIAP_C02, 0FIAR_C05, 0FIAR_C02, 0FIGL_C01 etc. Activation of content through to source system has been successful though data loading has proved into the cube through the 3.x flow has proved to be an issue.
The problem being when the info package is run to update the specific cube the load remains in yellow pending status before eventually reaching its time-out limit and producing a caller 70 error as below:-
Short dump in the Warehouse
Diagnosis
The data update was not finished. A short dump has probably been logged in BI. This provides information about the error.
System Response
"Caller 70" is missing.
Further analysis:
Search the BI short dump overview for the short dump that belongs to the request. Pay attention to the correct time and date on the selection screen.
You access a short dump list using the wizard or the menu path "Environment -> Short dump -> In the Data Warehouse".
Error handling:
Follow the instructions in the short dump.
After checking ST 22 we obtain a number of exceptions as shown detailed below :-
The exception 'CX_RSR_X_MESSAGE' 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 'SAPLRRMS' has to be
terminated.
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"
75 ELSE.
76 DATA: l_text TYPE string,
77 l_repid TYPE syrepid.
78
79 l_repid = i_program.
80 l_text = i_text.
81
>>>>> RAISE EXCEPTION TYPE cx_rsr_x_message
83 EXPORTING text = l_text
84 program = l_repid.
85 ENDIF.
86
87 ENDFUNCTION.
I have looked through the many articles related the error including notes :- 551464, 850428, 615389
Though to no avail, there are no locked idocs in sm58 and also basis have checked the DB size and all is OK, also reactivating and dropping index's did not work
Just wondering if there could be any further issues to resolve the data loading issues?
Many Thanks
Hi,
Based on the provided details, please take a look at below detail in the short dump:
I_IOBJNM
<Object> (In the most of cases the impacted object is 0REQUEST)
So, check the version of the object: >> tcode RSD5 - <object> -> Display
-> 'Version Comparison' button -> display All Properties -> Active/Content Version
By these steps you can see what is different in the versions (A-Active and D-Delivered)
To solve the issue check the steps provided in note 1157796 (in the first part - Symptom item)
It should helps.
Regards,
Sinara
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.