Regd: SM13 Errors Update Failure

[#1]

Dear All,

If an Update Error Occurs What are the Necessary Steps a Basis Consultant have to follow to rectify the Problem.

Is Basis person will Handle Indexing. if so what is the process?

Regards

SNB.

[Former Member]

Hi,

Please follow the below steps during update errors:

1) Firstcheck if the UPDATE service is active via SM13. If its deactivated, activate it.

2) If update is active, check for the abap dumps generated for the error update records. They will give you the necessary information to identify whether its a basis related issue or have to be solved by sap technical(dev)/functional guys.

3) Check for tablespaces allocated % and if any of those are full add space accordingly. the updates would resume after that.

4) Lots of update records can get stuck - pending updation to database. In such cases Check for update work processes via SM50/SM66 and identify their status whether running/stopped/waiting.

5) If they are stopped, start those. If you can see any errors then check the developer trace files.

6) I have seen few times that all the update work processes getting stuck ie. in running status. In such cases, all the update records would get stuck. Immediately check DB01/SM12 for oracle and sap locks respectively. If there are locks then take actions accordingly either by killing those locks/corresponding processes or waiting them to be finished. Once the locks are released, all the update work processes would get freed completing the pending update records.

7) Also, update work processes can get stuck trying to do database updates due to some problem with dialog / background job causing error. In such cases, cancel the corresponding work process. It would free the update work processes for continuing with other updates.

" Points for solution "

Regards,

Sandy.