Basis Errors and Solutions

Virtual host name not delivered to SLD

July 8, 2009 at 9:12 pm

[(SLD)] [Data] [Directory] [gethostname] [host] [hostname] [invalid hostname] [Landscape] [linux hostname] [name] [SAPLOCALHOST] [Supplier] [System] [virtualization]

RZ70: ABAP system name in SLD variesSymptom The system name of an AS ABAP in SLD is not unique. The name component “SystemHome” varies across the different application servers. Other terms Technical systems in the System Landscape Directory...
ABAP Dump CX_SY_CONVERSION_NO_NUMBER in MOPs trans DSWPSymptom Transaction: DSWP -> Support Packages and Patches [MOPs]) When you call the Maintenance Optimizer (MOP) in transaction DSWP under -> Operations -> Change Management -> Support Package Stacks and expand the...
DB2-z/OS: Support of Logical Hostname in connect.iniSymptom Logical hostname in connect.ini Other terms CLI Reason and Prerequisites You want to use a logical/virtual hostname for your application server in the connection profile connect.ini. You have installed your application...

Symptom

A virtual host name established by the SAPLOCALHOST profile parameter is not correctly delivered to the SLD by the J2EE SLD Data Supplier.
Other terms

SLD, System Landscape Directory, SLD Data Supplier, Host name virtualization, SAPLOCALHOST
Reason and Prerequisites

The reporting AS Java is on SAP Netweaver 6.40 SP 24 or lower.
Solution

If you are on a SAP Netweaver Support Package lower than SP 23, upgrade the reporting system (software component SAP_JTECHF) to SAP NetWeaver 6.40 Support Package 25
In case your system is already running on SAP NetWeaver 6.40 Support Package 24, download the attached archive file NW04_SP24.zip, unpack it to the filesystem, and deploy the contained sldserv.sda file using the SDM (Software Deployment Manager) tool. This is an offline deployment and will force an engine restart.
In case your system is already running on SAP NetWeaver 6.40 Support Package 23, download the attached archive file NW04_SP23.zip, unpack it to the filesystem, and deploy the contained sldserv.sda file using the SDM (Software Deployment Manager) tool. This is an offline deployment and will force an engine restart.