8 Feature De-activation Execution Overview

The procedures shown in the following table are executed inside a maintenance window. Deactivation procedure times are only estimates as the reason to execute a deactivation has a direct impact on any additional deactivation preparation that must be done. Times may vary due to differences in database size, network configuration and loading, user experience, and user preparation.

Table 8-1 DCA Application Deactivation Overview

Procedure	Elapsed Time (Hours:Minutes)		Activity Feature Activation Preparation	Impact
	This Step	Cum.
De-activation set up.	0:10-0:30	0:10-0:30	The reason to deactivate has a direct impact on any additional backout preparation that must be done. Since all possible reasons cannot be predicted ahead of time, only estimates are given here. Execution time varies.	None.
DCA Application Deactivation	00:10-00:20	0:20-0:50	Log out of active NOAM GUI. SSH into active NO. Change directory. Execute the feature de-activation script. Log into active NOAM and SOAM GUI. Verify the DCA application folder. Close SSH connections to both the NOAMs.	DCA application is de-activated on DSR.

Table 8-2 DCA Framework Deactivation Overview

Procedure	Elapsed Time (Hours:Minutes)		Activity Feature Activation Preparation	Impact
	This Step	Cum.
De-activation set up.	0:10-0:30	0:10-0:30	The reason to deactivate has a direct impact on any additional back out preparation that must be done. Since all possible reasons cannot be predicted ahead of time, only estimates are given here. Execution time varies.	None.
DCA Framework Deactivation	00:10-00:20	0:20-0:50	Log out of active NOAM GUI. SSH into active NO. Change directory. Execute the feature de-activation script. Log into active NOAM and SOAM GUI. Verify the DCA folder. Close SSH connections to both the NOAMs.	DCA framework is de-activated on the DSR.