ECC6 EHP 8 - Linux with Oracle

Basis (Basis Technology Modules: Basis Component/System Administration, GUIs)

Moderators: Snowy, thx4allthefish

Post Reply
msssr
Posts: 42
Joined: Mon Jul 07, 2003 9:13 am

ECC6 EHP 8 - Linux with Oracle

Post by msssr » Sat Oct 19, 2019 10:20 am

Hi Experts,

I am trying to install ECC6 EHP8 on SUSE Linux - 11 sp4.
I have installed LInux under VM.
While startting sapinst, installer has produced the following and stuck there only.
It is not moving beyond this stage.

INFO 2019-10-19 10:28:59.671 (root/sapinst) (SLPCommunicator) [SLPMonitoringStatemachine.cpp:1402]
********************************************************************************
Open your browser and paste the following URL address to access the GUI
https://sapecc.chandra.com:4237/sapinst/docs/index.html
Logon users: [root]
********************************************************************************

=>sapparam(1c): No Profile used.
=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
load resource pool /saptemp/resourcepool.xml
=======================

Sainstdev_log not producing any error logs. I have checked sap support and various forums, but I couldnot get clue for this.
I felt something related to host resolution? I have referred note 2591258 and 962955, but not helped me resolve this.
Anyone encountered with this?


TRACE 2019-10-19 10:29:06.225 (root/sapinst) (startInstallation) [CSiManagerInterfaces.cpp:3614] CSiMangerInterfaces::matchesSAPinstVersion()
sapinstVersion: 749, make platform: LINUXX86_64, OS version: 3.0.101, Distro: SLES11

TRACE 2019-10-19 10:29:06.225 (root/sapinst) (eventLoop) [SLPMonitoringStatemachine.cpp:218]
Entering state Running

TRACE 2019-10-19 10:29:06.225 (root/sapinst) (eventLoop) [SLPMonitoringStatemachine.cpp:257]
Entering state SLMP

TRACE 2019-10-19 10:29:06.225 (root/sapinst) (eventLoop) [SLPMonitoringStatemachine.cpp:267]
Entering state SLMPDisplayCatalog

msssr
Posts: 42
Joined: Mon Jul 07, 2003 9:13 am

Re: ECC6 EHP 8 - Linux with Oracle

Post by msssr » Mon Oct 21, 2019 3:41 am

I could resolve this issue due to DNS hostname resolution was cuased due to incorrect FQDN in settings.

Post Reply