cancel
Showing results for 
Search instead for 
Did you mean: 

HANA One SP6 without HLM installed??

woutdejong
Participant
0 Kudos

Hi experts,

Just trying to install the OPInt addon onto SAP HANA One 1.0 SP6 (rev 68). However, the upgrade guide mentions HLM, which is supposed to be installed with all HANA SP6 instances. I don't see it. So is HANA Lifecycle Manager NOT installed with HANA One?

Cheers, Wout

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello All,

As of now, we do not include HLM as part of HANA One offering. We will consider it for next releases. We use Addons to support compatible upgrades.

thanks,

Dhruman

Jacques-Antoine
Active Participant
0 Kudos

Hello Dhruman,

Thank you for your quick reply.

So if I understand well, with SAP HANA One we need to upgrade our instance through the Add On manager, then manually download the new Studio corresponding and install it.

So we cannot launch the Lifecycle Manager from HANA Studio for a HANA One instance.

Correct me if I am wrong.

Thank you for your attention.

Jacques-Antoine

swapan_saha
Employee
Employee
0 Kudos

Hi Wout,

In HANA One, you get HANA server (same software of appliance), AFL and HANA client installed. So, they should be exactly the same as of HANA appliance.

Thanks,

Swapan

woutdejong
Participant
0 Kudos

Hi Swapan,

We are still on rev68, that we upgraded from the Rev54 AWS AMI.

When trying to start Lifecycle Manager from HANA Studio, I get "Error occurred while trying to start lifecycle management for SAP HANA remotely." and by checking other logs "Error occurred while trying to start SAP HANA lifecycle manager. Check log file for details."

I don't know what log file the error is refering to. Do you?

So OPInt requires Hana Lifecycle Manager (HLM) to be installed.

From "SAP Operational Process Intelligence Installation and Upgrade Guide" I copied the lines below. Looking at piont 2, I logged on with SSH but couldn't see any HLM directory below /usr/sap/HDB . Should there be one in HANA One as well? Just like the normal SP6 appliance instances?

1. Download the delivery units from SAP Service Marketplace using the following substeps:

a) Open the SAP Software Download Center on SAP Service Marketplace.

b) Navigate to Installations and Upgrades A - Z Index .

c) Click O and then click OPERAT. PROCESS INTELLIGENCE.

d) Select the required service pack and select Installation.

e) Download the delivery units from the ZIP file.

2. Start the HLM server by performing the following substeps:

a) Log on to the SAP HANA server machine.

b) Navigate to the HLM directory under <hanamnt>/<SID>/HLM folder.

c) If not logged in with <sid>adm user, change to <sid>adm user by executing the command, su <sid>adm.

d) Start the HLM server by executing the command, ./hlm.sh &.

3. Launch the SAP HANA studio.

4. Open the Lifecycle Management perspective.

5. From the SAP HANA Systems view, select the system where you need to deploy the SAP OPInt delivery units.

6. From the context menu of the selected system, choose Lifecycle Management.

7. Choose Deploy HANA Content.

8. Enter the SAP HANA system details.

woutdejong
Participant
0 Kudos

All, it's getting worse.

Trying to install the HLM (SAPHANALM06_0-10012745.SAR) manually, as it is NOT part of HANA One (AFAICS).

Unfortunately running the hdbinst installer ends with an error that the SAP Host Agent is not installed. So apparently the Agent is also NOT installed by default on HANA One. So now looking for the manuel installation of SAP Host Agent...

hanaserver:~/hlminst # ./hdbinst

SAP HANA Lifecycle Manager installation kit detected.

SAP HANA Database Installation Manager - SAP HANA HLM Installation 1.50.00.00000               0

********************************************************************************               *

Options:

  SAP HANA system ID | Description

  ---------------------------------------------------------

  HDB                | SAP HANA Database HDB 1.00.68.384084

Enter SAP HANA system ID [HDB]: HDB

Root user password (SSH connectivity):

Root user SSH key passphrase (SSH connectivity):

Checking installation...

Preparing package "SAP HANA lifecycle manager"...

  Installation failed

    Error checking installation

      hanaserver: Executing pre-installation checks failed. Installation will no               t proceed.

        Details: /usr/sap/HDB/trans/hlm_install_1390917075/hanaserver/checks/Min               PatchNumberCheck.sh failed to execute Details:

MinPatchNumberCheck.sh: SAP Host Agent is not installed

Log file written to '/var/tmp/hdb_HLM_2014-01-28_13.51.01/hdbinst_HLM.log'.

hanaserver:~/hlminst #

woutdejong
Participant
0 Kudos

OK, so now SAP HOst Agent has been installed as well, and with that HLM installation went fine.

I ran the HLM script "./hlm.sh &" and that creates a nice OS (Java) process.

However, HANA Studio still spawns errors when trying to open Lifecycle Manager.

Do you have a clue what's going on? What log file??

Thanks for helping out.

This is the error in HANA studio.

"Error occurred while trying to start lifecycle management for SAP HANA remotely."

java.lang.Exception: Error occurred while trying to start SAP HANA lifecycle manager. Check log file for details.

  at com.sap.ndb.studio.lcm.upd.ui.internal.editors.web.WebUpdatePage.validateConnectionToHLM(WebUpdatePage.java:226)

  at com.sap.ndb.studio.lcm.upd.ui.internal.editors.web.WebUpdatePage.createContent(WebUpdatePage.java:253)

  at com.sap.ndb.studio.lcm.upd.ui.internal.editors.web.WebUpdatePage.createFormContent(WebUpdatePage.java:135)

  at org.eclipse.ui.forms.editor.FormPage$1.run(FormPage.java:152)

  at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)

  at org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:150)

  at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:243)

  at org.eclipse.ui.forms.editor.FormEditor.addPage(FormEditor.java:325)

  at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:213)

  at org.eclipse.ui.forms.editor.FormEditor.addPage(FormEditor.java:308)

  at com.sap.ndb.studio.lcm.upd.ui.internal.editors.LCMEditor.addPages(LCMEditor.java:104)

  at org.eclipse.ui.forms.editor.FormEditor.createPages(FormEditor.java:138)

  at org.eclipse.ui.forms.editor.SharedHeaderFormEditor.createPages(SharedHeaderFormEditor.java:98)

  at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:358)

  at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:138)

  at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:96)

  at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:313)

  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

  at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

  at java.lang.reflect.Method.invoke(Unknown Source)

  at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)

  at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:861)

  at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:841)

  at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:113)

  at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:321)

  at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:242)

  at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:161)

  at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:102)

  at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:71)

  at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:53)

  at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:141)

  at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:894)

  at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:629)

  at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:731)

  at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:702)

  at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:696)

  at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

  at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:681)

  at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1115)

  at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer$1.handleEvent(LazyStackRenderer.java:67)

  at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:41)

  at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:180)

  at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150)

  at org.eclipse.swt.widgets.Display.syncExec(Display.java:4687)

  at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:187)

  at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:38)

  at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)

  at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)

  at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)

  at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)

  at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)

  at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)

  at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)

  at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)

  at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:80)

  at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:58)

  at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)

  at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:171)

  at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:422)

  at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:389)

  at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:606)

  at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:332)

  at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1029)

  at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3047)

  at org.eclipse.ui.internal.WorkbenchPage.access$22(WorkbenchPage.java:2969)

  at org.eclipse.ui.internal.WorkbenchPage$8.run(WorkbenchPage.java:2951)

  at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)

  at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2947)

  at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2911)

  at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2894)

  at com.sap.ndb.studio.lcm.upd.ui.internal.commands.LCMEditorHandler.execute(LCMEditorHandler.java:74)

  at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)

  at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:76)

  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

  at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

  at java.lang.reflect.Method.invoke(Unknown Source)

  at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)

  at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:231)

  at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:212)

  at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:131)

  at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:171)

  at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:831)

  at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:724)

  at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:708)

  at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:647)

  at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)

  at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)

  at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)

  at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)

  at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1053)

  at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)

  at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:942)

  at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)

  at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)

  at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)

  at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)

  at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)

  at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)

  at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)

  at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)

  at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)

  at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)

  at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)

  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

  at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

  at java.lang.reflect.Method.invoke(Unknown Source)

  at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)

  at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)

  at org.eclipse.equinox.launcher.Main.run(Main.java:1438)

  at org.eclipse.equinox.launcher.Main.main(Main.java:1414)

swapan_saha
Employee
Employee
0 Kudos

Hi Wout,

If you upgrade to Rev 69, you will see a message like

...

Checking upgrade...

Checking installation...

Extracting software...

Installing package 'Saphostagent' ...

Updating package 'Python Support' ...

Updating package 'Python Runtime' ...

Updating package 'Product Manifest' ...

Updating package 'Binaries' ...

Updating package 'Installer' ...

Updating package 'Ini Files' ...

....

I am not sharing the exact location of the log file for security reasons. So, Rev 69 installs SAP Hostagent in HANA One.

In HANA One, we strongly recommend not to manually instal/upgrade HANA version which will block any future automatic upgrade and it will not be supported. For any reason, if your use case does not work with the latest version/configuration of HANA One, please report your use case and results after you stop your instance as we don't want you keep paying unless HANA One addresses your use case(s).

Thanks,

Swapan

jackson_john
Explorer
0 Kudos

Hi,

To check the Error log from HANA Studio go to Window -> Show View -> Error Log and that will show you the errors. Let me know what errors you see.

Thanks,

Jackson

woutdejong
Participant
0 Kudos

Thanks for trying to help out, but I published the eclipse Error Log in my previous post.

(So the term Error Log is pretty overloaded as it definitely means something other than the eclipse Error Log.)

woutdejong
Participant
0 Kudos

Swapan, I skipped the Rev69 installation, and went straight for the Rev70 one. Just like I did beforehand by skipping Rev56. Are you saying we need to incrementally upgrade? We are now trying to upgrade to SP7 Rev70 which is not working out... Perhaps we should have instlaled Rev69 first.

Thanks for the warning about not installing extra HANA components. However, we really want to use OPInt, so followed note "1892537 - Release of SAP Operational Process Intelligence 1.0 SP01" which says Rev63 as minimum release. I would expect that SAP HANA One Rev68 includes everything that is in the regular HANA Appliance software (with the corresponding Rev number, Rev68 in this case). So I was unpleasantly surprised that HLM and SAPHostAgent were not installed by default (on Rev68).

Anyway, so I did install the HLM and SAPHostAgent manually. Have I now broken the HANA One system? Or is my HANA Studio more of a problem?

jackson_john
Explorer
0 Kudos

Hi Jong,

I tried starting HLM on one of my instances where HLM is NOT installed. The error logs in the Studio looks exactly the same as yours. Hence can you confirm if HLM is properly installed? To my best knowledge if it's installed properly then you should see a directory called HLM under /usr/sap/<SID>

Also if HLM is installed then you should look out for the most recent logs under /usr/sap/hlm_bootstrap/<SID>/log

Also check if ports 1129 and 1128 are open in your server by the commands:

netstat -apn|grep 1129

netstat -apn|grep 1128

Thanks,

Jackson

swapan_saha
Employee
Employee
0 Kudos

Wout,

As I mentioned in we can go to HANA One Rev 70 from any previous HANA version supported in HANA One. So, to go to Rev70, you don't need an intermediate step Rev 69.

If your question is about Rev 70 upgrade, we like to work with directly to see why it does not work. Please send me a direct message so that we can ask more information which we can publish here once the issue is resolved for the community.

In case if to make HLM work, if we need additional ports, we can open from EC2 management console for the security group you are using.

Thanks,

Swapan

woutdejong
Participant
0 Kudos

I noticed with netstat that both ports 1128, 1129 were being listened to (tcp), when HANA One was started.

However, I couldn't find any HLM process running (with ps ax | grep hlm. So I started /usr/sap/HDB/HLM/hlm.sh & . Apparently it was not running, as it started some Java processes. Interestingly this worked out fine, even though port 1128 and 1129 were already being used.

Trying to stop HLM does not work.

hanaserver:/usr/sap/HDB/HLM> ./stop-hlm.sh

Checking for running HLM...

The HLM is running in process with pid: 31317 on host: hanaserver.

Checking for running HLM tasks...

Warning: Cannot check for running LM operations.

Do you want to perform force stop (yes/no) [no]:yes

Force stop will be performed!

Searching for java process in HLM process tree with root pid: 31317 on host: hanaserver.

Found java process started by HLM has pid: 31555.

Killing HLM java process with pid: 31555...

Waiting...

Still waiting...

The HLM process tree with root pid: 31317 on host: hanaserver was killed.

Error: Invalid state. The lock file '/usr/sap/HDB/HLM/hlm.sh.lock' was not deleted.

It seems that the hlm.sh process was not killed.

hanaserver:/usr/sap/HDB/HLM>

woutdejong
Participant
0 Kudos

Swapan, thanks for the offer; I will contact you about the Rev70 upgrade. Basically this thread deals with the installation of Operational Process Intelligence on HANA One.

Thread is more oriented towards getting Rev70 (SP7) of HANA in place for the geospatial stuff, etc.

So, yes, we're doing some things in parallel now. (Assuming that Opint 1.0 SP1 also runs on HANA 1.0 SP7.)

Former Member
0 Kudos

Hi Jong,

Please try performing the steps mentioned in note 1896320 for this.

Regards,

Ram.

woutdejong
Participant
0 Kudos

Thanks, Ram. This is useful for the HLM question in the header of this thread.

On a sidenote, we managed with SAP's help to install OPInt on HANA One Rev68.

Jacques-Antoine
Active Participant
0 Kudos

Hi Swapan,

I am facing a problem similar to M. De Jong.

I did the automatic update through the HANA One Management console to the SPS07, as I did before for the previous stacks.

I never took care of HLM or the Host agent. Nevertheless, I wanted to do the update process today and so I updated my instance to SPS07 and wanted to try to update automatically my Studio.

I tried to launch the lifecycle manager for my instance, from the Studio, but it gives me an error: "Error occurred while trying to start lifecycle management for SAP HANA remotely" and "com.sap.ndb.studio.lcm.upd.ui.hostcontrol.SAPHostControlNotAccessibleException: Could not connect to SAP Host Agent on host xxx.xxx.xxx.xx. Check that it is running."

So I tried to follow the SAP Notes 1896320 steps but I cannot even find the  <your_shared_directory>/<SID>/HLM/hlm.sh.lock. It tells me No Such directory exists.

Finally, when I try to go and download the HLM from SAP it just doesn't give me any results, so I cannot download it.


What can I do to install HLM and the Host Agent properly in this situation?

And if they are preconfigured in HANA One, where are they???