cancel
Showing results for 
Search instead for 
Did you mean: 

NW04 - Upgrade J2EE to SP14

HenrikD
Participant
0 Kudos

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

Accepted Solutions (1)

Accepted Solutions (1)

gregorw
Active Contributor
0 Kudos

Hello Henrik,

how is your DISPLAY enviroment variable set? Have you tried to do the upgrade directly on the nw4host?

Regards

Gregor

HenrikD
Participant
0 Kudos

Hi Gregor,

I'm not sure what the DISPLAY variable has to do with this? I'm running sapinst via VNC.

How can i connect directly to nw4host?

Best regards,

Henrik

gregorw
Active Contributor
0 Kudos

Hello Henrik,

VNC is excelent. That should be like working on the Machine directly. Can you please provide us your /etc/hosts file?

Regards

Gregor

HenrikD
Participant
0 Kudos

Hi Gregor,

Here is the host file:

127.0.0.1 localhost

  1. special IPv6 addresses

::1 localhost ipv6-localhost ipv6-loopback

fe00::0 ipv6-localnet

ff00::0 ipv6-mcastprefix

ff02::1 ipv6-allnodes

ff02::2 ipv6-allrouters

ff02::3 ipv6-allhosts

127.0.0.2 linux.site linux

192.168.1.10 nw.tetasoft.local

192.168.1.9 nw.tetasoft.local nw

192.168.1.6 main.tetasoft.local main

195.155.155.1 nw4host

I'm running on Suse 9.2.

Best regards,

Henrik

Former Member
0 Kudos

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.

gregorw
Active Contributor
0 Kudos

Hello Stuart, Hi Henrik,

I think this time there is no other way as to send an OSS message.

Regards

Gregor

Former Member
0 Kudos

Did so.

In my case Sap Note 883943 was the solution.

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello all

We encountered the same problem when patching our XI on HP-UX IA64 from SP10 to SP14 last sunday. As mentioned before by Stuart, Note 883943 was the solution. Stuart, thank you for your entry, I did not find the solution in the SAP Support Portal, but by google here! I was stuck while patching as you were!

Unfortunately the problem only occurred on our production site, the development and quality system were patched wihtout this problem.

I assume that the difference is our cluster envrionment on the production site where logical hostname is not the same as the underlying physical hostname.

Regards

Patrick

Former Member
0 Kudos

I have this very same problem, and cannot solve it.

Can anybody tell me what 's in Note 883943?

(I have no access to the Notes)

Former Member
0 Kudos

Henrik,

see sap Note 783965.