SDN-BW_Data Load Errors - Basic Checks

8/8/2019 SDN-BW_Data Load Errors - Basic Checks

http://slidepdf.com/reader/full/sdn-bwdata-load-errors-basic-checks 1/5

Subscribe

Print

Permalink

Share

Blogs

Data load errors - basic checksSiegfried Szameitat

Business CardCompany: axantis-solutions GmbH & Co.KG

Posted on Jul. 28, 2005 12:40 PM in BusinessIntelligence (BI)

Problems during the data load occur more or less frequently. The cause is differently.Sometimes it is an issue with disk space, sometimes there is no memory available, sometimesthere are timeouts;.Here some examples for the error messages:

data loadData loading error - Urgent

As we are all dealing with BW, we only see the monitor entries, and mostly it is giving us theimpression, the load is still running, but in fact the load already terminated for whatever reason.Here I will describe some things to check and the resulting action to fix the issue.Of course, the dataflow has to be set up correctly. The datasource has to be active and

replicated. The mapping from datasource to infosource has to be maintained and activatedand/or the update rules to the datatargets as well.

Loading from R/ 3:Here it depends on how you load your data. If you load it using the PSA, you have to check inthe SourceSystem if the data doesn't arrive in the PSA. If it is already posted to the PSA, you

have to check your BW itself.If you don't use PSA for your loads, well then you have to check both sides. R/3 for the

extractor related issues and BW for the transfer or update rules related issues.1. Actions in the SourceSystem:a) goto transaction sm37 and check for a job named BI_REQU....(REQU.... will be the requestnumber in BW) for your communication user (usually it will be ALEREMOTE). If the job doesn't

exist, check with your basis. There might be a delay time until the job will be created. If it

exists, check whether it is running or not. If it is running goto b), if not, your load just finishedor terminated. Check the job log. If it finished successfully ok, if not, goto c)b) goto transaction sm50 (may be better sm51 if you have more than one application server) tocheck for running processes for your communication user. Here it is also possible to check whata process is doing at the moment and you can start debugging the process. If there is no

process, the load just finished or you need to goto c)c) goto transaction sm21 and choose 'System-Log->Choose->All remote system logs' to display

the log entries for all servers and not only for the one you are currently logged on to. Check forentries related to your communication user in the relevant time. If there are errors, check with

AP Network Blog: Data load errors - basic checks http://weblogs.sdn.sap.com/pub/wlg/

of 5 10/14/2010 5:34

http://weblogs.sdn.sap.com/pub/wlg/2076




your basis. Additionally goto d)d) goto transaction st22 to check for dumps for your communication user in the relevant time.

Analyze the dumps. There might be a program error -> check with a developer to fix theprogram error, there might be disc space, memory or other parameter errors -> check with yourbasis and/or a developer to get the issue fixed.2. Actions in BW :

The actions here are almost the same as described for R/3, but just for completion, here thesteps once again.

The difference here is the user you have to check. If you scheduled the load in background it isagain the communication user (mostly ALEREMOTE). If you scheduled the load directly, thecommunication user is your user name.a) goto transaction sm50 (may be better sm51 if you have more than one application server) to

check for running processes for your communication user. Here it is also possible to check whata process is doing at the moment and you can start debugging the process. If there is no

process, the load just finished or you need to goto b)b) goto transaction sm21 and choose 'System-Log->Choose->All remote system logs' to displaythe log entries for all servers and not only for the one you are currently logged on to. Check for

entries related to your communication user in the relevant time. If there are errors, check withyour basis. Additionally goto c)c) goto transaction st22 to check for dumps for your communication user in the relevant time.

Analyze the dumps. There might be a program error -> check with a developer to fix theprogram error, there might be disc space, memory or other parameter errors -> check with yourbasis and/or a developer to get the issue fixed.

Loading from BW itself:

If you are loading data within BW, eg. from ods to cube, things are mostly a bit easier exceptyou have lots of coding in all the routines in the transfer or update rules. Without the coding

you normally get a message in the monitor for the error.The checks to do are again the same as described before in 'Actions in BW' and I will not repeat

them here.

Loading from Flatfiles/ Legacy systems: As there is no control over the legacy system while loading data, we also need to concentrateon checking BW for errors. The actions in the legacy system or the file (system) will be more orless concentrated on checking the authorities on files, tables or views. For other errors, there is

a error message available in the monitor and if not, goto 'Actions in BW'.

Possible actions to solve the issues:If you are dealing with program errors, ok, it is pretty easy, talk to a developer and correct theerror. Additionally it might be necessary to increase the performance of the program by usinganother logic.

If you are dealing with system error, talk to your basis. In this case you might need to addsome disk space, enhance table spaces, increase the size of some system parameters (for

program runtime, for memory management ...). The basis needs to do some fixes.If nothing solves your issue, then open a new thread or search for a thread in SDN or open orsearch for a note in the


of 5 10/14/2010 5:34





OSS

Siegfried Szameitat is a BW consultant for and a partner of axantis-solutions GmbH & Co.KG (www.axantis-solutions.de) .

Comment on this weblog

Showing messages 1 through 8 of 8.

Titles Only Main Topics Oldest First

Very good

2007-09-26 10:35:42 BW/ BI Business Card [Reply]

Thx for such a nice blog and it is very useful for beginners like me...

Very Nice

2007-08-19 23:26:14 Rajasekhar Chinthala Business Card [Reply]

it is really very helpful

Informative for beginners

2007-03-23 05:20:25 Minaxi shah Business Card [Reply]

Thanks a lot for this kind of stuff.

Minaxi shah

SM58

2006-07-06 08:02:10 Prakash Holalkere Business Card [Reply]

Hi Siggi

Thanks for this excelent post. Had one question: Does SM58 transaction in R/3 hold any

relevance to such data load issues? I have noticed that the tRFC queue here gets blocked in

case of loads with yellow status in BW? please enlighten.

thanks


of 5 10/14/2010 5:34

http://www.axantis-solutions.de%29/



http://www.axantis-solutions.de%29/



Prakash

This is inspiring

2006-05-08 17:13:48 Sudheer B Business Card [Reply]

I am amazed at the interest these developers show in sharing their immense knowledge. It is

truly inspring. Thanks a lot for this kind of stuff.

practical and brief

2006-01-12 06:14:39 BWer BWer Business Card [Reply]

As always i like your blogs and suggestions at sdn. This blog is pretty practical and brief,

thanks,,

Nice

2005-10-24 05:33:21 Bhima Chandra Sekhar Guntla Business Card [Reply]

Good and Nice and it is very usefull

Thanks for contributing to the collective... :)

2005-07-29 06:35:29 John Skrabak Business Card [Reply]

Good stuff.

Think this kind of "How BW works in the real world" stuff like what are the typical problems,

solutions, and things to keep an eye on are in your system is one iof the biggest missing

pieces.

Your blog inspired me to post to the SDN Suggestion forum. I thin kwe nned to find a way to

collect or index this kind of content, be it blogs, or forum threads that are instructional, insome way. Maybe a shared blog, or a wiki. So much go info is on SDN, just need to be able

to pull it together.

Showing messages 1 through 8 of 8.


of 5 10/14/2010 5:34






of 5 10/14/2010 5:34



SDN-BW_Data Load Errors - Basic Checks

Documents

Transcript of SDN-BW_Data Load Errors - Basic Checks