Upgrade 6.40 to 7.01 Error

Question

Hi,
I am running a SAP Netweaver upgrade from 6.40 to 7.01. I have made the preparation and now running the upgrade part. But I keep getting an error.
The steps that fails is "Deploy_Online". With this error:
Feb 13, 2010 11:19:11... Info: Starting the process server0
Feb 13, 2010 11:48:52... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Feb 13, 2010 11:48:52... Error: Aborted: development component 'bi/mmr/browser_ea'/'sap.com'/'SAP AG'/'7.0103.20081105085346.0000'/'11', grouped by :
SDM could not start the J2EE cluster on the host chpsqld01! The online deployment is terminated.
A timeout has occured while ensuring that process server0 is in final state.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
As I can read from the error, the cluster is not getting started, so I have checked SAP MMC, along with the upgrade and the step that hangs is "STARTING APPS", so I have tried fixing this, but no luck.
I have applied note 891905.
I have changed the MaxApplicationThreadCount to 100.
The first error I got were related to the component ADSSAP, so I tried removing this component from deploy list, and when the upgrade is complete, I will deploy this component. BUT now I am getting error on another component.
Do I have the possibility to set a parameter, saying that the cluster should not start the app?
Or is there another possibility?
BR
Kim Kjelgaard

Answer 1

Hello Kim,
Its by design that SDM either expects the server to be in completely started state ('Running' status) or completely stopped state.
Anything in between, SDM will hang indefinitely for the server to go up. So in a case like yours, you could give it a try to redeploy the offline components first by shutting down the server. For the online deployments, SDM will try to restart the server. If it still hangs in 'Starting applications', the best way is to take threaddumps as per note 710154 and check using the threaddump viewer what is causing the hang. Is it exhaustion of the threads or thread blockage waiting on some action! You can find more info about threaddumpviewer @
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2015bb75-a9da-2910-e0b1-c5ba9fe90012?quicklink=index&overridelayout=true
Also, one tip for SDM redeployment, its always good to select option 3 on the deployment screen which says 'upgrade regardless of sca/sda version'
SafeMode means the applicaitons are not started during the server startup. This is done during the upgrade when the engine is put in the safemode to avoid long startups. So, the application start forbidden is just indicating that the application was not started due to that mode. Doesn't indicate any error with the application as such.
To check for the startup errors, please check std_server* from <j2ee engine>/work & defaultrace file in server<n>log always. You can get hints from here.
Hope the above helps.
Regards,
Snehal Bhaidasna
SAP Labs, Palo Alto, CA(USA)