Short Dump

[Former Member]

Hi

While i was loading data to an ODS object we had a short dump..

going detail in to the error :

Status

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.

Details Tab

Requests (messages): Everything OK

Extraction (messages): Errors occurred

---25086 Records sent ( 25086 Records received )

Transfer (IDocs and TRFC): Errors occurred

---Data Package 1 : arrived in BW ; Processing : Data packet not yet processed

Processing (data packet): Errors occurred

Up to PSA there was some data 25086 records, and there's a start routine in update rules i believe that's fine..

<b>MESSAGE_TYPE_X i s the name of the runtime error in ST22</b>

Appriciate your assumptions for the above issue

[Former Member · Accepted solution]

Hi Yeddulapalli,

I have faced this kind of dump no of times. However, mentioned by Dhanya, as data is already available in PSA, try to load it manually--> right click on the data package which is left out and select manually update.

If this doesn't work then check for free table space in db02.

Regards,

Vij

[former_member228339]

Hi..

i am sure that this may help

also refer to RM2312421

identify the unnecessary records in ROOSPRMSC & ROOSPRMSF

Check the contents of RSSDLINIT

Check the contents of ROOSPRMSC

Check the contents of ROOSPRMSF

Do not schedule Delta Infopackages until you have the successful init on the place.

Delete wrong Init flag immediately after you get the result. Please use normal SAP func-tionality via Initialisation Option for Source System.

Make sure that the previous Init flag has been deleted before start the new one.

[Former Member]

Hi,

If the system could not detect the valid reason,it throws MESSAGE_TYPE_X ( generalised error)

please check the following :

Is extraction finished?

if yes, investigate exactly where you are getting the error in processing (is it at update rules?)

As a workaround,

try to make the request red,delete it from all the targets

and repeat the load

please let me know if you need help!!!!!!!!!!!

Regards,

Swapna.G

[Former Member]

Hi,

There are zillions of threads here on Caller70 and tips to fix it. You can also try any of these (some of them refer to Oracle database):

- Note 860475.

- Note 631668. Check ST22 for dumps, ST12 for locks.

- Go to the target infoprovider in RSA1, right click, "Manage", go to "Performance" tab, "Check index", then "Repair index".

- Check Oracle tablespace in transaction DB02.

- Add the below entries to table TSORA:

PSAPDSX PSAPDSX

PSAPDSX620 PSAPDSX620

PSAPDSXDIM PSAPDSXDIM

PSAPDSXFACT PSAPDSXFACT

PSAPDSXODS PSAPDSXODS

PSAPDSXUSR PSAPDSXUSR

- Extend the system buffer memory (ask your Basis team to do that).

- Change the size of the datapackage in your loading: go to the infopackage, click on "Scheduler", "DataS. Default Data Transfer", then change the datapacket size to a considerably smaller number.

- You might get Caller70 even if the allowed runtime is not enough for the infopackage to finish loading.

And there are many other possibilities. I am not saying any of these will fix your problem but may be worth having a look.

Please let us know when and how you manage to fix the issue. That information could be useful for others in the future.

Regards,

Csaba

[Former Member]

HI,

MESSAGE_TYPE_X is just the name of the dump..

if u click on that for display you will see the detailed analysis..

ther they will give correct analysis paste that text here...the error analysis text..

tehn only i can provide input on the exact error...

if still u have no clue, u can try manually updating that data packet by right clicking the packet and slecting manual update.

Regards,

dhanya

[Former Member]

Hi Dhanya

this is the message available in short dump

Probably the only way to eliminate the error is to correct the program.

-

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:

"MESSAGE_TYPE_X" " "

"SAPLRSSM_PROCESS" or "LRSSM_PROCESSU19"

"RSSM_PROCESS_REQUDEL_ODSO"

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.

[Former Member]

try replicating the datasource it will work ... there has been some modification in the source system and there is a timestamp mismatch in source and BI system...

Thanks

Amit