Inroads into SAP HANA led me to take a deep dive into how Enterprise software can some day turn into an appliance like the ones we own in our houses for everyday lives - Refrigerator, Microwave and others. The software comes bundled with the hardware, you can't buy it separately. [Bean in mind that HANA costs a lot more than the other appliance mentioned!]. With Bumps on it's way, the road has been interesting. This blog captures the learning, the findings, the games, the puzzles and all the fun that came along with the trip to HANA - the In Memory Database by SAP.
The Objects of this blog is to capture my learning of SAP HANA in the following Categories :
The Objects of this blog is to capture my learning of SAP HANA in the following Categories :
- Installation
- Data Modelling
- General Maintenance
- Monitoring
- Best Practices
- Root Cause Analysis
- Tips and Tricks along the way
- BI(SAP BusinessObjects) 4.x with HANA
First Installation : I started with working on a VMWare Workstation machine hosted on a Lenovo T520, hosting SUSE Linux 11 SP1 Operating System. The configuration details were as follows:
Hardware : VMWare workstation machine hosted on Lenovo T520 laptop with 4 CPU's and 8 GB RAM.
CPU : Virtual CPU running on a Intel Core i5 vPro hosted on Lenovo T520
Memory : 4 GB allocated to the Virtual Machine
OS : SUSE Linux Enterprise Server 11 SP1
Softwarwe : SAP HANA Platform Edition 1.0 SPS 5
Result : *NOT GOOD*
The Installation went through successful, however the creation of HANA instance
failed due to lack of memory.
The configuration above would certainly beg the question if 4 GB RAM is good for hosting an enterprise In-Memory Database, even if it is for experimental purpose. My curiousity got better of logic, so the answer was - lets try it out!
For those thinking ahead, the configuration above or the hardware used, as far as i know, is not supported by SAP. The configuration is for self-learning and developers who are researching and exploring possibilities that SAP HANA offers as a premier in-memory database.
Second Installation : The second installation was with a more sane hardware, although still well below the minimum hardware requirements. For learning purposes, it was good!
Hardware : VMWare ESX Server hosting SUSE Linux 11 SP1
CPU : Virtual CPU (Don't have additional details)
Memory : 24 GB allocated to the Virtual Machine
OS : SUSE Linux Enterprise Server 11 SP1
Software : SAP HANA Platform Edition 1.0 SPS 5
RESULT : *GOOD*
The installation was successful and i now have a mini working SAP HANA In-Memory
database to play around with.
The list of supported hardware for installing HANA is a fairly big list available from 'http://server.sap.com/pam' (The acronym PAM stands for Platform Availability Matrix). A valid support userid and password to SAP support portal is required to be able to access the PAM. As of the writing of this blog post the PAM had about 7 pages with 50+ hardware configuration supported from multiple hardware vendors.
The PAM contains supported hardware configuration for both Scale Out and Standalone HANA deployments. A Scale Out HANA deployment ranges across multiple physical machines, while a standalone HANA deployment is built on a single machine. The successfull installation mentioned earlier in this blog post related to a standalone HANA deployment.
Hardware : VMWare workstation machine hosted on Lenovo T520 laptop with 4 CPU's and 8 GB RAM.
CPU : Virtual CPU running on a Intel Core i5 vPro hosted on Lenovo T520
Memory : 4 GB allocated to the Virtual Machine
OS : SUSE Linux Enterprise Server 11 SP1
Softwarwe : SAP HANA Platform Edition 1.0 SPS 5
Result : *NOT GOOD*
The Installation went through successful, however the creation of HANA instance
failed due to lack of memory.
The configuration above would certainly beg the question if 4 GB RAM is good for hosting an enterprise In-Memory Database, even if it is for experimental purpose. My curiousity got better of logic, so the answer was - lets try it out!
For those thinking ahead, the configuration above or the hardware used, as far as i know, is not supported by SAP. The configuration is for self-learning and developers who are researching and exploring possibilities that SAP HANA offers as a premier in-memory database.
Second Installation : The second installation was with a more sane hardware, although still well below the minimum hardware requirements. For learning purposes, it was good!
Hardware : VMWare ESX Server hosting SUSE Linux 11 SP1
CPU : Virtual CPU (Don't have additional details)
Memory : 24 GB allocated to the Virtual Machine
OS : SUSE Linux Enterprise Server 11 SP1
Software : SAP HANA Platform Edition 1.0 SPS 5
RESULT : *GOOD*
The installation was successful and i now have a mini working SAP HANA In-Memory
database to play around with.
The list of supported hardware for installing HANA is a fairly big list available from 'http://server.sap.com/pam' (The acronym PAM stands for Platform Availability Matrix). A valid support userid and password to SAP support portal is required to be able to access the PAM. As of the writing of this blog post the PAM had about 7 pages with 50+ hardware configuration supported from multiple hardware vendors.
The PAM contains supported hardware configuration for both Scale Out and Standalone HANA deployments. A Scale Out HANA deployment ranges across multiple physical machines, while a standalone HANA deployment is built on a single machine. The successfull installation mentioned earlier in this blog post related to a standalone HANA deployment.
No comments:
Post a Comment