NW04 - Upgrade J2EE to SP14

Question

Hi,
I have a strange problem when I try upgrade my Linux TestDrive from SP12 to SP14.
Hostname: NW
The installation is working on SP12. I’m able to deploy both from NWDS and SDM.
The sapinst is executed with the remotehost parameter: sapinst SAPINST_USE_HOSTNAME=nw4host
The upgrade goes smooth until ‘Deploy via SDM/J”EE’ where I get a ‘Error: Unable to compare host[nw4host] and host[tetasoft-002] Throwable: java.net.UnknownHostException Throwable message: tetasoft-002: tetasoft-002’
The strange thing is that my laptop is called tetasoft-002.
Any idea how to solve this? Is there a parameter I should use?
callSdmViaSapinst.log:
Nov 1, 2005 1:09:39 PM   Info: The deployment prerequisites finished without any errors. All items are correct.
Nov 1, 2005 1:10:00 PM   Error: Unable to compare host[nw4host] and host[tetasoft-002] Throwable: java.net.UnknownHostException Throwable message: tetasoft-002: tetasoft-002
Nov 1, 2005 1:10:00 PM   Info: Saved current Engine state.
Nov 1, 2005 1:10:00 PM   Info: Error handling strategy: OnErrorStop
Nov 1, 2005 1:10:00 PM   Info: Update strategy: UpdateLowerVersions
Nov 1, 2005 1:10:00 PM   Info: Starting: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050818152214.0000' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4012.00.0000.20050331133103.0000'.
Nov 1, 2005 1:10:00 PM   Info: SDA to be deployed: /usr/sap/NW4/DVEBMGS00/SDM/root/origin/sap.com/SQLTrace/SAP AG/6.4014.00.0000.20050818152214.0000/SQLTrace.ear
Nov 1, 2005 1:10:00 PM   Info: Software type of SDA: J2EE
Nov 1, 2005 1:10:00 PM   Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Nov 1, 2005 1:10:00 PM   Error: Unable to compare host[nw4host] and host[tetasoft-002] Throwable: java.net.UnknownHostException Throwable message: tetasoft-002
Nov 1, 2005 1:10:01 PM   Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Nov 1, 2005 1:10:01 PM   Error: Aborted: development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050818152214.0000':
CPO data could not be get.
com.sap.sdm.apiint.serverext.servertype.deployment.DeploymentActionException: Error: Caught the following error or exception: "com.sap.sdm.apiint.serverext.servertype.deployment.DeploymentActionException"
Additional error message is:
Caught exception from deploy service of SAP J2EE Engine. Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [nw4host] with user name: [J2EE_ADMIN]
                                                  Check your login information.
                                                  Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext instance.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.checkLoginCredentials.DMEXC)
Additional error message is:
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [nw4host] with user name: [J2EE_ADMIN]
                                                  Check your login information.
                                                  Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext instance.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).NO_CPO)
Nov 1, 2005 1:10:02 PM   Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Nov 1, 2005 1:10:02 PM   Info: -
Deployment was successful -
Nov 1, 2005 1:10:02 PM   Info: Summarizing the deployment results:
Nov 1, 2005 1:10:02 PM   Error: Admitted: /home/hda/SAP Download (Linux)/test/J2EE-RUNT-CD/J2EE-ENG/ONLINE/SAPJTECHS14_0.SCA
Nov 1, 2005 1:10:02 PM   Error: Processing error. Return code: 4
Best regards
Henrik

Answer 1

Gregor,
I have exactly the same symptom in SP9 --> SP13 on clustered Solaris WebAS/EP installation. I am curious as to why you think it's to do with DISPLAY variable - though I wouldnt be at all surprised by some of the imaginings that sapinst has.
In my case, I get the RemoteLoginContext problem, but no 'comapre host' message. Simply that the J2EE administrator credential check failed. At this time, thye J2EE is up and running, all services and apps are in the started/running state; the SDM is stopped (but gets started by the deploy task of sapinst). There is no corruption of the secure store password so far as I can gather.
My installation sounds somewhat similar to Henrik's:
Physical Host : spvcs53prod
Virtual SCS IP (on same host): spscs50prod
Virtuaal CI IP (on same host):  spci50prod
..\sapinst SAPINST_USE_HOSTNAME=spci50prod SAPINST_START_GUI=false
The CI is on a virtual host too, for system admin and monitoring reasons, though it is not in a switchable cluster group. I have had some problems for example with the delivered startsap and stopsap scripts. These cannot locate the required hostnames accurately on network adapters as the output of the ping command varies depending on the physical/virtual setup. (start.sopsap parse the ping result to verify hostnames). Maybe sapinst is doing something similar in these installation situations?
Any help appreciated, as we are now stuck delivering a production cluster !
Thanks.