Regd: SM13 Errors Update Failure

[Former Member]

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]

Dear All,

is the Same process have to followd for V1 and V2 errors.

In sm13 if i got a V1 Update Error . we have to check with the end user compulsorly or not b'cos V1 Updates are very Critical it might impact on Production

Regards

shankar.

[Former Member]

Hi,

Yes, you have to follow the same process for both updatess and its not recommend to retry the errored updates from SM13. We should always get back to the user. They would rerun the transactions if needed.

" Points encourage to reply "

Regards,

Sandy.

[former_member771067]

Dear Shankar,

If you have got your desired solution, please mark this as answered.

it would be helpful for others.

Best Regards,

Gurugobinda

[Former Member]

Welcome to SDN Mr gurugobinda harichandan parida

@shankar, you must check with the enduser because when the v1 update fails. the failure message will prompt for the user when update failure happens.in that case may be the user try to update the same data again.If that has not happened then you should find out the reason for the update failure and try to repeat the upgrade.

Regards

Ashok Dalai

[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.

[Former Member]

Hi,

Follow the below steps to avoid data inconsistency in production environment,

1. In SM13, check whether the `Update is in active` status , if yes, then the problem is with certain user action. If not, check the table space status. whether any table space has reached 100%. If the table space has reached full , extend the table space and change the update to active. SAP will automatically change the status to inactive if any of the table space reaches 100%, this is to avoid inconsistency.

2. If it is not related to table space problem, check the failed update error. if you double click on that error, you will get the detailed error report..where it got failed and in which transaction it happened etc.

Normally, update errors are to be handled with coordination from Func and end user. Find out which user action has triggered this update error etc. Ask your func team to check if there is any business impact due to this error ( due to missing document etc). if there is any, ask your func team to analyze the situation and repost the failed document.

Once the business impact is fixed, ask your func team to search for any notes available in OSS for that particular transaction which caused the update error. in general, there will be some corrections or SAP will recommend to apply note.

This will solve the problem.

Hope this will help you a bit to analyze the update error situation.

regards,

Vinodh.

[Former Member]

hi,

check the table spaces.check the patces.

regards

ajai