Search this blog for other interesting articles

Monday 13 June 2011

Update got deactivated. What are the reasons for update deactivation. How to activate the update?

This article answers the following queries ?

  • How to check the update status ?
  • What is the reason for update deactivation ?
  • How to activate or deactivate the update ?
  • What parameter to be set to switch off automatic update deactivation ?
  • How to troubleshoot, if update got deactivated ?
  • What happens for the updates that are in progress, if update got deactivated ?

----------------------------------------------------------------------------------------

Update status check :

Update status can be checked in transaction SM13.




Reasons for update deactivation :

Update will get deactivated in cases of serious database problems.

Some of the examples of update deactivation and solutions for those are given below :

 1) Update will get deactivated when oraarch is full

Solution : Trigger archivelog backup and ensure sufficient space is left in oraarch and then activate the update manually

 2) When some critical tablespaces are 100% full and database is not able to perform some operations

Solution : Monitor the database and findout the tablespaces which are 100% full.  Add necessary datafiles and ensure there is enough free space left out in them. Then activate the update manually



 How to activate or deactivate an update in sap ?

Use transaction SM14 and goto update tab. There update status can be viewed with a push button. If it is in deactivated status, click it to activate  and viceversa.




How to switch off automatic update deactivation ?

In RZ10, set the parameter rdisp/vb_stop_active to 1 and activate the profile to switch off automatic update deactivation incase of database problems.



How to troubleshoot, if update got deactivated ?

Please perform the following steps if udpate got deactivated :

  •  Check all the tablespaces and ensure figureout if any tablespace is 100% full. If so, add necessary space and activate the update as mentioned above

  • Check if oraarch is full. Trigger archivelog backup and ensure there is enough space and activate the update again

  • Check SM21 log and ST22 dumps

  • Check workprocess trace for any other issues

  
What happens for the updates that are in progress, if update got deactivated ?

If update got deactivated all the updates that are in progress or waiting to get executed, won't be cancelled. They will be assigned either init or auto status. Once the database issue got fixed and update is activated again, all these updates which are in init or auto status will resume again









7 comments:

Archana said...

Hi.. thanks so much for all your data.
Question- If we switch off automatic update deactivation using that parameter, what happens in the event of oraarch getting full or tablespace getting full? What happens to all updates in this scenario?
Thanks,
Archana

Anonymous said...

Hi.. Basically if oraarch or any important tablespace is full, we will be facing serious performance problem like system gets very slow, nd user log in issues etc.. are there any other reasons why the update will hang?

DurgaPrasad said...

All updates will be in hung status until the issue is resolved. once issue is resolved, updates will resume processing.

DurgaPrasad said...

ThanQ Masood

venky said...

Dear Durga,
In DB02 is it possible to perform complete DB reorganization?.

Anonymous said...

Thanks Durga.Its Very useful....

Anonymous said...

Very useful

Search this blog for other interesting articles

Please subscribe & activate link received to your email id to receive latest articles

Enter your email address:

Delivered by FeedBurner