Use of projection in SAP HANA

Hello Team
We use projection in calculation view . What is the actual utility of this projection in calculation view apart from holding the attribute view , analytic view and tables . We can add tables in union also directly and connect it to aggregation . So what is the utility of projection then . Please suggest .
Regards

Hello,
The main aim of projection is to filter out the unwanted fields from the table, e.g. If a table has 100 columns, by using projection we can highlight/ filter 10 columns that we need.
Thanks,
Sathish.

Similar Messages

Use cases for the SAP HANA Appliance for SAP FI-Accts.Payable

Hello SAP HANA friends:
Are there any compelling use cases for the SAP HANA Appliance for SAP FI-AP Accounts Payable module?
CO-PA and CRM have many immediate use cases, but I'm looking for the use case for Accounts Payable,
either from a cash flow perspective or performance.
Any and all comments are appreciated.
Regards,
Joe Gonzales
856 912 1136

Hi,
In SQL console please execute below query .
GRANT SELECT ON SCHEMA <schema Name> TO "_SYS_REPO";
BR
Sumeet

SAP HANA for Control System Application

Hi,
I want to know is there any on going project where SAP HANA is using for the applications of control system (Fuzzy Logic, Predictive control system, modeling etc) for industries like power plant, Oil and gas, aerospace for better results.
Could any one can share information on this.
Posted topic is not relevant to this forum. Kindly suggest me where to post this topic.
Thanks in advance.
Regards,
Siva Prasad N

Hi Sava,
Maybe the link below will be of help. In there you can find lots of useful HANA information.
https://community.wdf.sap.corp/sbs/message/108063#108063
regards,
David

Install of SAP HANA Studio Dev Ed v1.00.80 fails with "Could not create the Java Virtual Machine"

Hello,
Scope: JVM error during initial install of SAP HANA Studio Developer Edition v1.00.80, Win86/32bit
Source: installation files pulled from HANA Studio tab at https://hanadeveditionsapicl.hana.ondemand.com/hanadevedition/, which is a link from the main HANA site of http://scn.sap.com/community/developer-center/hana. zip folder: "sap_hana_win32_studio_rev80"
Targeted O/S: Windows 7, 32-bit, local Java is SE 7, update 67.   Java environment has been confirmed via checks provided at http://www.java.com/en/download/manual.jsp
Actions taken:
Attempted to update the installation's eclipse.ini file by reducing the -Xmx value; see details below.
Read thru postings such as http://scn.sap.com/thread/3390626 and the threads it recommended.
Checked OSS (ie Note 1859686 - HANA Studio does not start)
Description of installation error:
Shortly after executing "hdbinst", it fails with the error "Could not create the Java Virtual Machine". I've verified that there is nearly 3G of memory free. What I did notice, as shown in the attached files, is that Eclipse is part of this installation and it's pre-loaded with the "eclipse.ini". I firmly believe the solution could be to reduce parameter "-Xmx1024m" to "-Xmx512m" but it's a catch-22 because even after updating eclipse.ini (in installation folder C:\Program Files\SAP\hdbstudio\tmp_p2director2014.08.13_13.36.44\director), the install program requires that the "hdbstudio" folder to be empty upon restarting it.
Since the installation is basically a package with a lot of .jar files, there is no eclipse.ini file available in the source install folder; otherwise, updating it there would be the easiest solution if that option were available. The file is only available in the targeted deployment folder above.
If you have encountered this same error and were able to resolve it, I would be grateful to know of your solution. Thanks very much.
FYI: the HANA Client installed with no issues.
Jim Cleek
FYI: the images below reflect the sequence of images produced during the installation.
after clicking OK above, the screen below gets updated (see the "is not empty" msg).
Below is the eclipse.ini file located in the deployed/target folder:
Message was edited by: Jim Cleek
FYI: Using information from the SAP HANA Database - Studio Installation and Update Guide, I tried to override the installation's use of its eclipse.ini file by passing my own modified version (with "-Xmx512m") of that file that was placed in a separate folder. The cmd used via DOS window was "hdbsetup.exe -a studio --configfile=C:\Users\Admin\Downloads\eclipse.ini" and even though it successfully launched the SAP HANA Lifecycle Management gui, it failed on the first step with the same JVM create error as above because it appears to have used its own eclipse.ini file, which has "-Xmx1024m".

Update: a message was opened with SAP but unfortunately they could not provide a resolution for this particular scenario. They admitted that the eclipse.ini file cannot be updated since it is bundled as part of the installation package. One point to make that I did not make before was that this was being attempted on an Oracle VirtualBox (4.3.10); the SAP HANA contact said he assumed that SAP has not tested this particular scenario, thus it could not be supported.
Resolution: the end result was to abort trying to install SAP HANA Client and Studio on the Oracle VirtualBox but to install it locally on my own desktop, which runs on Windows 7 Enterprise 64-bit with 8G of memory. The SAP HANA files below were downloaded, extracted and installed successfully in the order shown.
FYI: the Studio installation detected that a 64-bit version of Java was not installed so I installed that and then adjusted the User environmental variable JAVA_HOME to point to that new path, leaving the System variable still pointing to the pre-existing 32-bit Java path.
SAPCAR 7.20 -> Windows on x64 64bit: SAPCAR_315-20010453.EXE
IMDB_CLIENT100_80_0-10009664.SAR   Revision 80 for SAP HANA CLIENT 1.00
Support Package SAP HANA CLIENT 1.00 Windows on x64 64bit
IMC_STUDIO100_80_0-20007647.SAR   Revision 80 for SAP HANA STUDIO 1.00
Support Package SAP HANA STUDIO 1.00 Windows on x64 64bit
jre-7u67-windows-x64.exe - http://www.oracle.com/technetwork/java/javase/downloads/jre7-downloads-1880261.html
Jim Cleek
HP Enterprise Services

SAP HANA for functional consultants

Hi
I have rich experience of 9+ yrs in SAP MM/WM/SD/SRM (certified in these modules) (and over all 16+ yrs) all through implementations and rollouts.
Now I am feeling stagnated in my career; wanted to make it more techno-functional; SAP HANA is a buzz word.
Wanted to move into it after doing certification; but have the following queries:
Will it be a right decision to move into it without any prior BI/BW experience.
Will I get an entry into new projects of SAP HANA.
Does BI/BW experience preferred over other SAP module/functional experience; in which case it will be a difficult enviro to compete.
I have explored job portals and every one wants prior BI/ABAP/Tech experience.
I am worried will I be loosing by entering into HANA or shall I go further in my logistics area only for explorations.
The market I am working in is US and Australia.
Please suggest;
Thank you.
Kim

It will really be helpful if I can get some insight from the perspective of
a functional consultant as nothing concrete has been said on the approach to be
followed.
The answer were helpful but I am looking for more suggestive help; in that
respect I wrote additionally so that I can reach out to more people for a
career changing decision.
If you still want to restrict the free flow of ideas then it’s against the
forum spirit.
I hope my concerns are justified.

Try now for SAP HANA developer edition 1.0 rev 80 returns error

Hi -
following documents
How to use CAL to create SAP HANA developer edition on AWS - Part 1
to build my first hana environment in the cloud.
created AWS account, SCN account and CAL accounts...
reached the point of selecting the
SAP HANA developer edition 1.0 rev 80 - try now
get an error: Operation Failed. An error occurred; contact your SAP Cloud Appliance Library operator
Tried different approach
followed this document
http://scn.sap.com/docs/DOC-55693
filled out the form with the AWS account info and region.
When submitted, get error
error while processing the request
The declaration for the entity HTML Version must end with '>'
I am using Chrome browser.
Please advise

Hi Diane,
sometimes AWS needs 24 hours to fully enable the AWS account.
How much time did elapse between the time you created the AWS account and the time you entered the credentials in CAL?
Can you try again now?
Regards,
Hannes

SAP Hana implementation project - beginning tasks

Hello,
We want to implement a new SAP landscape running with SAP Hana database. As I understand, the SAP Hana database is a database that runs on a specific server appliance, am I right?
For we can know which SAP Hana server appliance to buy we need first to estimate the sizing about it! We want to implement SAP ERP product (EHP6 or 7) on Hana DB, but we don´t know how to start... this is, we don´t know how to measure this, in order to buy the best solution (server appliance) for our own scenario!
I checked some information in the following areas:
service.sap.com/sizing
and also the Quick Sizer tool (service.sap.com/quicksizer) but this is so much confused tool... I don´t understand it at all.
Can you help me with your experience which SAP Hana server appliance we need to buy for this kind of project?!
Thank you,
samid raif

Hi Dario,
Does the calculation view work without xsodata service? From the URL, your XS project name should be Project_DM, but from the xsodata source, the project name is EricssonItalgas. I'm confused with this. Did you use rewrite_rules or?
Best regards,
Wenjun

SAP HANA Modeling Sample end to end Project

Dear All,
I got trained on SAP HANA Modeling and BODS recently, and in process of learning SAP BO. My core is SAP EP and don't have indepth knowledge on SAP BI and Functional aspects.
I am working on few sample applications but I would like to do a Sample end to end project on real time scenarios/POC's.
Do you have any sample requirement documents that helps to do a end to end project(real time scenarios) . Does SAP store any piolet project requirement specs for public use which help to gain real time experience.
Kindly help me on this.
Thanks & Regards,
Rajeev Bikkani

hi look into this
Role of a Functional Consultant in an End To End Implementation
1. Functional consultant is expected to generate knowledge about the current business process, design current business flows, study current business processes and its complication, in all we can say getting through with current business setup. Flow diagrams and DFD are prepared, most of the time in Vision format, all this forms the part of AS IS document.
2. Everything configured has to be documented as per their categories in the form of predefined templates, these have to be then approved by the team leads or who ever the consultant is reporting to.
3. Mapping and GAP analysis is done for each module, I have seen people defining integration after mapping, gap analysis and configuration is done, but as per my experience in implementation, it is a simultaneous process.
4. Before starting configuring future business processes in SAP, the DFD/ERD are prepared, this documentation is called TO BE, which can be also siad as the result of mapping and gap analysis.
5. Sometimes Functional consultants are also expected to prepare test scripts for testing the configured scenarios.
6. End user manual and user training is also expected from F.Consultants.
The project normally starts off with a Kick off meeting in which the team size, team members, reporting system, responsibilities, duties, methodology, dates and schedules, working hours which have been predicided are formally defined.

SAP HANA Lifecycle Manager Couldn't deploy using credentials

Hello,
After HLM 1.0.7.7 upgrade from 1.0.6 on IBM appliance we could not apply support packages in normal mode. When we launch the Upgrade process from Hana Studio or Command line we recive the following message:
Error Message: Execution of 'Deploys SAP Host Agent configurations using sidadm credentials' failed.
Detailed Message: null or empty argument
Help: http://help.sap.com/hana
We tried to downdgrade and reinstall HLM again with no luck. Users, Parsswords and Certificates was also renewed. We could read this log from HLM.
INFO 2014-05-08 16:05:15 com.sap.lm.hlm.common.wizard.process.WizardProcessExecutor
Submit for subtask with ID [6cd61e09-eb68-4448-86c0-b4319abbdc3f_GetUpdateTypeTask]
INFO 2014-05-08 16:05:15 com.sap.lm.hlm.common.wizard.process.WizardProcessExecutor
Submit for subtask with ID [6cd61e09-eb68-4448-86c0-b4319abbdc3f_GetUpdateTypeTask]
INFO 2014-05-08 16:05:15 com.sap.lm.hlm.common.wizard.process.WizardProcessExecutor
Starting execution of subtask with ID [6cd61e09-eb68-4448-86c0-b4319abbdc3f_DeployConfigWithSidAdmTask]
INFO 2014-05-08 16:05:15 com.sap.lm.hlm.common.wizard.process.WizardProcessExecutor
Starting execution of subtask with ID [6cd61e09-eb68-4448-86c0-b4319abbdc3f_DeployConfigWithSidAdmTask]
INFO 2014-05-08 16:05:15 com.sap.lm.hlm.common.tasks.process.AbstractProcessExecutor
Starting process [Deploys SAP Host Agent configurations using sidadm credentials, com.sap.lm.hana.hlm.update.slpp.task.deployconfig.DeployConfigWithSidAdmTask] ({})...
INFO 2014-05-08 16:05:15 com.sap.lm.hlm.common.tasks.process.AbstractProcessExecutor
Starting process [Deploys SAP Host Agent configurations using sidadm credentials, com.sap.lm.hana.hlm.update.slpp.task.deployconfig.DeployConfigWithSidAdmTask] ({})...
INFO 2014-05-08 16:05:15 com.sap.lm.util.status.StatusTracker
Status tracker initialized using storage file /usr/sap/hlm_bootstraps/HNB/HLM/param/configdeploystatus.properties.
INFO 2014-05-08 16:05:15 com.sap.lm.util.status.StatusTracker
Status tracker initialized using storage file /usr/sap/hlm_bootstraps/HNB/HLM/param/configdeploystatus.properties.
INFO 2014-05-08 16:05:15 com.sap.lm.hana.hlm.update.slpp.context.ProgressObserverAdapter
Progress [ 0%]
INFO 2014-05-08 16:05:15 com.sap.lm.hana.hlm.update.slpp.context.ProgressObserverAdapter
Progress [ 0%]
INFO 2014-05-08 16:05:15 com.sap.lm.hana.hlm.update.slpp.task.deployconfig.AbstractDeployConfigProcessExecutor
Deploying SAP Host Agent configurations on host with sidadm credentials.
INFO 2014-05-08 16:05:15 com.sap.lm.hana.hlm.update.slpp.task.deployconfig.AbstractDeployConfigProcessExecutor
Deploying SAP Host Agent configurations on host with sidadm credentials.
INFO 2014-05-08 16:05:15 com.sap.lm.hana.hlm.update.slpp.context.ProgressObserverAdapter
Process message: Deploying SAP Host Agent configurations on host
INFO 2014-05-08 16:05:15 com.sap.lm.hana.hlm.update.slpp.context.ProgressObserverAdapter
Process message: Deploying SAP Host Agent configurations on host
INFO 2014-05-08 16:05:16 com.sap.lm.services.hostcontrol.SAPHostControlService
Deployed Host Agent configurations [/usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdb-plugin.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-studio-repository.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-sedm-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-repository-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-home-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-client-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-load-controller-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-sda-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdbstudio-deliveryunit.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-studio.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/newdb-studio-repository-postupdate-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-sda-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-server.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-executable.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/newdb-studio-repository-postupdate.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hdb-plugin-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-studio-repository-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-load-controller.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-client-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/change-newdb-client-installation-path-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-studio-repository-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/updatehostagent-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-executable-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-repository.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/updatehostagent.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-load-controller-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/exists-path.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/gen-hdbstudio-deliveryunit.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/change-newdb-studio-repository-installation-path-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server-nzdm.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hdb-plugin.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-installation-number.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-load-controller.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdb-plugin-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-installation-number-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdb-plugin-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-server-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/updatehostagent-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-repository.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-repository-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hostagent-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hostagent.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-hdbeuspack.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-studio-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/chmod-file.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-home.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-sedm.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-repository-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/exists-path-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-client-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-v2.conf] with signature /usr/sap/hlm_bootstraps/HNB/HLM/SIGNATURE.SMF on host .
INFO 2014-05-08 16:05:16 com.sap.lm.services.hostcontrol.SAPHostControlService
Deployed Host Agent configurations [/usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdb-plugin.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-studio-repository.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-sedm-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-repository-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-home-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-client-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-load-controller-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-sda-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdbstudio-deliveryunit.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-studio.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/newdb-studio-repository-postupdate-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-sda-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-server.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-executable.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/newdb-studio-repository-postupdate.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hdb-plugin-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-studio-repository-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-load-controller.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-client-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/change-newdb-client-installation-path-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-studio-repository-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/updatehostagent-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-executable-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-repository.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/updatehostagent.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-load-controller-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/exists-path.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/gen-hdbstudio-deliveryunit.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/change-newdb-studio-repository-installation-path-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server-nzdm.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hdb-plugin.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-installation-number.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-load-controller.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdb-plugin-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-installation-number-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdb-plugin-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-server-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/updatehostagent-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-repository.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-repository-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hostagent-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hostagent.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-hdbeuspack.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-studio-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/chmod-file.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-home.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-sedm.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-repository-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/exists-path-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-client-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-v2.conf] with signature /usr/sap/hlm_bootstraps/HNB/HLM/SIGNATURE.SMF on host .
ERROR 2014-05-08 16:05:16 com.sap.lm.hana.hlm.update.slpp.task.AbstractUpdateProcessExecutor
Process executor failed
java.lang.IllegalArgumentException: null or empty argument
at com.sap.lm.hlm.common.runtime.HlmRuntime.assertNotNullOrEmptyArgumens(HlmRuntime.java:342)
at com.sap.lm.hlm.common.runtime.HlmRuntime.deployHlmExecutableScripts(HlmRuntime.java:74)
at com.sap.lm.hlm.common.runtime.HlmRuntime.deployHlmExecutableScripts(HlmRuntime.java:69)
at com.sap.lm.hana.hlm.update.slpp.task.deployconfig.AbstractDeployConfigProcessExecutor.deployconfigurations(AbstractDeployConfigProcessExecutor.java:114)
at com.sap.lm.hana.hlm.update.slpp.task.deployconfig.DeployConfigWithSidAdmProcessExecutor.executeInternal(DeployConfigWithSidAdmProcessExecutor.java:42)
at com.sap.lm.hlm.common.tasks.process.AbstractProcessExecutor.startInterruptibleExecution(AbstractProcessExecutor.java:128)
at com.sap.lm.hlm.common.tasks.process.AbstractProcessExecutor$1.run(AbstractProcessExecutor.java:108)
ERROR 2014-05-08 16:05:16 com.sap.lm.hana.hlm.update.slpp.task.AbstractUpdateProcessExecutor
Process executor failed
java.lang.IllegalArgumentException: null or empty argument
at com.sap.lm.hlm.common.runtime.HlmRuntime.assertNotNullOrEmptyArgumens(HlmRuntime.java:342)
at com.sap.lm.hlm.common.runtime.HlmRuntime.deployHlmExecutableScripts(HlmRuntime.java:74)
at com.sap.lm.hlm.common.runtime.HlmRuntime.deployHlmExecutableScripts(HlmRuntime.java:69)
at com.sap.lm.hana.hlm.update.slpp.task.deployconfig.AbstractDeployConfigProcessExecutor.deployconfigurations(AbstractDeployConfigProcessExecutor.java:114)
at com.sap.lm.hana.hlm.update.slpp.task.deployconfig.DeployConfigWithSidAdmProcessExecutor.executeInternal(DeployConfigWithSidAdmProcessExecutor.java:42)
at com.sap.lm.hlm.common.tasks.process.AbstractProcessExecutor.startInterruptibleExecution(AbstractProcessExecutor.java:128)
at com.sap.lm.hlm.common.tasks.process.AbstractProcessExecutor$1.run(AbstractProcessExecutor.java:108)
ERROR 2014-05-08 16:05:16 com.sap.lm.hlm.common.wizard.process.WizardProcessExecutor
Execution of subtask with ID [6cd61e09-eb68-4448-86c0-b4319abbdc3f_DeployConfigWithSidAdmTask, Execution of 'Deploys SAP Host Agent configurations using sidadm credentials' failed.] has failed: {}
ERROR 2014-05-08 16:05:16 com.sap.lm.hlm.common.wizard.process.WizardProcessExecutor
Execution of subtask with ID [6cd61e09-eb68-4448-86c0-b4319abbdc3f_DeployConfigWithSidAdmTask, Execution of 'Deploys SAP Host Agent configurations using sidadm credentials' failed.] has failed: {}
Could you please help us with this issue?
Kind Regards,
Message was edited by: Tom Flanagan

Hi Alston,
I'm sorry for the late reply. Are you still experiencing this error?
I've seen this issue before with another customer and the final resolution was to make sure the /etc/hosts file does not have the ipv6 BEFORE ipv4. Here is an example:
>> cat /etc/hosts
# special IPv6 addresses
::1             localhost ipv6-localhost
ipv6-loopback
ff02::3         ipv6-allhosts
192.168.180.31 abceccd01.sap.com abceccd01
192.168.180.34 abceccs01.sap.com abceccs01
192.168.180.35 abccrms01.sap.com abccrms01
192.168.180.30 abceccs01.sap.com abceccs01
10.36.10.5      abceccs01-nfs.sap.com abceccs01-nfs
The resolution would be to change the ordering. So the IPv6 section appears below the IPv4 section.
After that is done, perform the following to "reset" HLM.
1. Stop all browsers that have HLM pages open
2. Stop the Studio
3. Execute /usr/sap/hlm_bootstraps/<SID>/HLM/stop-hlm.sh –f
4. Check that there are no any left HLM processes
5. Go to /usr/sap/hlm_bootstraps/<SID>/HLM/param/
and rename all files except logging.properties
6. go to directory: /usr/sap/hlm_bootstraps/<SID>/HLM
and rename directory persistence
7 restart SAP Host Agent - as root: /usr/sap/hostctrl/exe/saphostexec
-restart
8. open HLM ui via browser:
https://<hostname>:1129/lmsl/HLM/<SID>/ui/
I hope this helps.
Best Regards,
Jimmy

Which programming is used in SAP HANA? confused b/w ABAp or java?

Can anyone just tell me As a programmer in which language i have to work on SAp HANA

Hi Jagaa,
that really depends on what you'd like to do. But a brief answer:
a) If you develop ABAP applications - use ABAP (as for other databases) and Open SQL / CDS, and if additional HANA functionality is needed maybe a bit of native SQL (ADBC or ABAP Managed DB Procedures).
b) If you develop natively on the database please contact the experts on SAP HANA Developer Center.
Cheers,
Jasmin

I want to connect SAP HANA database (Default database) using JDBC connection URL.

I am using trial account .at sap cloud server.
What will be my URL of SAP HANA database for Trail account.
For ex:
java.sql.Connection conn= java.sql.DriverManager.getConnection("jdbc:sap://<YOUR SAP HANA IP>:host","<YOUR SAP HANA USER>","<YOUR PASSWORD>");
I had User and password but what supposed to be used in place of IP and Host ?

Thanks .But iwant to use like this ..and below properties are not working
repliesd as connectin refused -813
please help onthis
<bean id="dataSource"
      class="org.springframework.jdbc.datasource.DriverManagerDataSource">
      <property name="driverClassName" value="com.sap.db.jdbc.Driver"/>
      <property name="url" value="jdbc:sap://localhost:30015/?currrentschema=TestSchema" />
      <property name="username" value="p1940828544"/>
      <property name="password" value="[email protected]"/>
   </bean>

How ADBC connection is benefits by using SAP HANA as secondary database ?

Hi,
I have one more important question.
How ADBC connection is benefits by using SAP HANA as secondary database in terms of performance wise for the access of data from HANA database as a secondary database.
I have 2 options and which is better for the good performance for accessing the data-
1 . In ABAP Reports in the SELECT statements by using CONNECTION (“HDB”) will this improve the
     performance.
      e.g : select * from BSEG into TABLE IT_TAB CONNECTION (“HDB”).
2. Will Create the Stored procedure in HANA studio and Call
   from ABAP as below by using NATIVE SQL–
     EXEC SQL
      SET CONNECTION (‘HDB’).
     ENDEXEC.
    EXEC SQL.
      EXECUTE PROCEDURE proc (IN    p_in1
                             OUT   p_out1   OUT   p_out2 )
   ENDEXEC.
Regards,
Pravin
Message was edited by: Jens Weiler
Branched from http://scn.sap.com/thread/3498161

Hi Pravin,
Option 1: In this case ADBC might even worsen the performance due to the overhead in the ADBC framework. OpenSQL is the method to go here, as OpenSQL - from the ABAP point of view - features the optimal communication with the database while ADBC has overhead like constructor-calls for the statement, parameter binding, etc.
Option 2: In this case ADBC is comparable with EXEC SQL but features more options, e.g. clean concept of multiple connection (connection objects via CL_SQL_CONNECTION), exception handling, etc. So I strongly propose to favour ADBC over EXEC SQL, but not simply for performance reasons. You might have a look at the ABAP Language Help in your system on more information on ADBC and the advantages over Exec SQL.
Cheers,
Jasmin

How to use Variable in SAP HANA Information Modeller?

Hello Folks,
I have created a variable in Information modeller of SAP HANA Studio on top of an Analytical view (Regional Sales). This variable is SingleValue (Multiple Value Selections). This variable should prompt me the name of Country/Regions but somehow this is not working when I am using data preview and Analysis tab of data preview.
Could you please enlight me where I am going wrong? or Let me know if is there any other forum for this.
P.S : I am using SAP HANA studio on Cloud.
Regards
Muffazzal Fani

Hi,
After you created that variable as mentioned above, did you apply this variable on your LAND1 attribute.
How: Open Analytic View --> on right-side you see the attributes,measures etc. >right click on 'LAND1' and select>
'Apply Filter'--> In the drop-down select your created variable and activate.
I assume the above should resolve your issue. Please let me know if it helps.
Revision: I mean the HANA version you are using.
Regards, Rahul

Benefits/ Limitations when we use SAP HANA Extended and Standard products.

Hi All,
We are going to purchase SAP HANA media. Please let me know what are the benefits/ limitations when we use SAP HANA Extended and Standard products.
Thanks in Advance,
Vishall

Hello,
please check Master Guide (page 9 - chapter 1.6 Software Components)
https://service.sap.com/~sapidb/011000358700000604552011
There you can find edition comparison and detailed description.
To extract the short summary:
Platform edition = SAP HANA Database + Studio + Client + Host Agent + Information Composer
Enterprise edition = (Platform edition) + LT Replication Add-on (SLT) + LT Replication Server (SLT) + SAP BO Data Services
Enterprise extended edition = (Enterprise edition) + Sybase Adaptive Server Enterprise + Sybase Replication Server + Sybase Replication Server Agent + SAP HANA load controller
It depends on what licenses you already have and how do you intends to use HANA.
Platform edition = ETL via BO Data Services (you already have license for BO Data Services)
Enterprise edition = SLT and/or BO Data Services (including licenses)
Enterprise extended edition = all replication technologies
Tomas

Is using Sybase Rep Server with SAP HANA a possibility?

We have a customer has system that they are already using Sybase Replication Server. They are asking to add HANA and BusinessObjects BI Platform as a sidecar, to there system and remove the Java applications they are using for reporting. They are wondering if they can use Sybase Rep server to move the data into Hana instead of SLT.

If you have a SAP Business Suite system then SLT is the recommended approach since carries out a application level replication of sorts. However, for non SAP Business Suite systems you do have the option to use Sybase Replication Server for HANA. Ask your customer to speak to their SAP Account Manager and she/he will be able to advice them on the option.
Have a look at the link below for pointers:Replicating data to HANA using SAP Sybase Replication Server.

Use of projection in SAP HANA

Similar Messages

Maybe you are looking for