Deploy controller is not ready to serve yet. Probably a un/deploy operation after offline phase is in progress at the moment

While performing the upgrade on SAP AS JAVA environment, below error comes out,

The following problem has occurred during step execution: com.sap.sdt.jspm.service.JspmServiceException: Could not update components.
Deployment of queue Queue_2020.10.08 at 05:08:05 completed with error Deployment error. See log F:\SUMQ\sdt\log\SUM\deploy_api.0.log for details.
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1023] DCNotAvailableException.
Reason: [ERROR CODE DPL.DC.3218] Deploy controller is not ready to serve yet. Probably a un/deploy operation after offline phase is in progress at the moment. DC state is Deploying
com.sap.engine.services.dc.cm.DCNotAvailableException: [ERROR CODE DPL.DC.3218] Deploy controller is not ready to serve yet. Probably a un/deploy operation after offline phase is in progress at the moment. DC state is Deploying

Solution

Referring to both SAP Notes below,

2706235 – Deployment is hanging – ConfigurationException – The ConfigurationManager must be initialized before usage
1884294 – Deployment fails due to a locking issue
2125707 – How to enable/disable AS Java Safe Mode

Note: We did not stop the SUM and executing below steps directly.

Taking on example in Windows operating system environment, login to the operating system and jump to the configtool directory.

\usr\sap\SID\Jxx\j2ee\configtool

Double click on the configtool. Click Yes on the dialog prompt, “Do you want to use the default DB settings”

From File, click on Safe Mode.

Change the Safe Mode Enabled to NO. Click on OK and restart the cluster to apply the changes.

Resume your upgrade.

If you happen to get the below error message on locking.

Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception while [registering [update] of [sap.com/com.sap.portal.ur.preview].
Reason: com.sap.engine.services.deploy.server.utils.concurrent.LockSetNotAcquiredException: The thread DeployThread[sap.com_com.sap.portal.ur.preview]
	id:      177
	task:    [Deploy Controller] - performing [deploy] operation of component [sap.com/com.sap.portal.ur.preview]
	subtask:  {
	creator:DeployThread[sap.com_com.sap.portal.ur.preview]
	id:      177
	task:    [Deploy Controller] - performing [deploy] operation of component [sap.com/com.sap.portal.ur.preview]
	subtask: 	
}

timed out while trying to get the locks for operation [update : sap.com/com.sap.portal.ur.preview]
Has been waiting for exclusive lock for the node [sap.com/com.sap.portal.ur.preview],
which is held shared by the following threads:
	DeployThread[sap.com_com.sap.portal.design.urdesigndata]
	id:      2802
	task:    [Deploy Controller] - performing [deploy] operation of component [sap.com/com.sap.portal.design.urdesigndata]
	subtask: null {
	creator:DeployThread[sap.com_com.sap.portal.design.urdesigndata]
	id:      2802
	task:    [Deploy Controller] - performing [deploy] operation of component [sap.com/com.sap.portal.design.urdesigndata]
	subtask: null
	Active operations:	
	update : sap.com/com.sap.portal.design.urdesigndata
}

Refer to SAP Note 2303980 – SUM fails in the step DEPLOY-COMPONENTS :Could not update components.-timed out while trying to get the locks for operation. According to the logs, the deployment is not proceeding due to lock conflicts when trying to use a parallel approach to deploy the files.

You can do the following to avoid lock conflicts:

In NWA -> Configuration -> Infrastructure -> Java system properties, search for the “Deploy Controller” service in the list of services.
Under this deploy controller service, modify the value of deploy_threads property to “1”. Refer to the KBA 1884294 – Deployment fails due to a locking issue
Restart the whole SAP system, including the SCS instance.
Retry the deployment