SAP BW: Implementation of NLS with SAP IQ 16.0
This is my first document release in SCN .I am very much interested in Sharing my thoughts and Knowledge.Recently we have implemented Near Line Storage for One of our Major Client.I would like to share the experience and knowledge during implementation.
SAP IQ SERVER:
SAP IQ is a high-performance decision-support server designed specifically for mission-critical business intelligence, analytics, and data warehousing. Component Integration Services within SAP IQ provide direct access to relational and non-relational databases on mainframe, UNIX, or Windows servers.
Supports all options and features. Optional features require additional licenses that are purchased separately.
Supports all options and features available in the Enterprise Edition for a 30-day evaluation period.
Supports all options and features available in the Evaluation Edition. Unlike the Evaluation Edition, the Express Edition does not expire, but does restrict the size of all IQ main dB spaces, permit other incremental license options, and cannot be deployed in a production environment
Implementation SAP-NLS Solution with SAP IQ
- Check for Operating System Patches.
- Increase the Swap Space.
- Install Required Support Packages and Libraries.
- Disable Huge Pages and Transparent Huge Pages.
- Set the Kernel Parameters.
Supported Server on Linux Platforms
- SAP IQ is compatible with these platforms and operating systems in Linux:
- Red Hat Enterprise Linux 6.2 (and later) Linux on POWER; 64-bit
- Red Hat Enterprise Linux 6.2 (and later) x86-64, Advanced Server and Workstation Editions
- Red Hat Enterprise Linux 5.5 (and later) Linux on POWER; 64-bit
- Red Hat Enterprise Linux 5.5 (and later) x86-64, Advanced Server and Workstation Editions
- SuSE Linux Enterprise Server SLES 11/Linux on POWER – minimum patch level SP1
- SuSE Linux Enterprise Server SLES 11/X86_64 64-bit – minimum patch level SP1
- The recommended minimum swap space is at least 1GB. Certain operations may cause the memory usage to grow dynamically. Changing the way Sybase IQ uses buffers can dramatically change the way it uses memory.
Asynchronous I/O (AIO) Kernal Support
- Asynchronous input/output (AIO) applications which use the native AIO interfaces require the libaio package. AIO provides an interface that submits multiple I/O operations and other processing requests in a single system call, and an interface that collects completed I/O operations associated with a given completion group.
Disable HugePages and Transparent Huge Pages
- Allocating large amounts of memory to HugePages can significantly degrade Sybase IQ performance. If the kernel allocates more than just a few MB of memory to HugePages, remove the HugePages options
Set the Kernel Parameters
Set the number of available semaphore identifiers.
- SEMMSL – maximum number of semaphores per set.
- SEMMNS – maximum number of semaphores system–wide.
- SEMOPM – maximum number of operations allowed for one semop call.
- SEMMNI – maximum number of semaphore identifiers (sets).
Check for Operating System Patches
–>Download Required software from SMP.
–>Transfer to Sever location.
–>In MY Next Document we see connection establishment between your SAP IQ and SAP BW System.
–>And how to initiate archiving from BW System to NLS.
- For a general sizing guideline see the following document: http://www.sybase.com/files/Technical_Documents/Sybase_IQ_Sizing_Guide.pdf
I don't want to cool down your enthusiasm about publishing, but there already is a document on this subject in SCN [SAP First Guidance - SAP-NLS Solution with SAP IQ] which is very verbose and already has a long history of improvements and refinements. Also the author (Roland Kramer) is in a close loop with the developers of NLS. If you have included anything in your sequence of steps that's missing in Roland's document, please check back with him. I know him as a very responsive person who is open to improvement suggestions.
Besides that, I wouldn't recommend the approach you've described. This isn't a matter of right or wrong, but maybe more or less appropriate. Whenever I've set up an NLS or an IQ instance in general, I use a set of SQL scripts and execute them in batch mode. This has a couple of advantages
- you can easily reproduce your IQ instance if ever required.
- in a multi- landscape scenario, you may run an identical or adjusted script (depending on the differences in the various systems and the degree to which you want to parametrize the scripts) for the workflow through the landscapes.
- these scripts are minimum system documentation.
- once you've got your set of scripts, you can use them over and over again. If you expect a significant number of instances to be created, you might even use a template / generator approach
- the approach requires minimum infrastructure. Even if all you have is putty access t the IQ server machine (a situation I found not uncommon on customer sites), you can get things going by transferring the scripts to the machine and executing them there.
I have made it a personal guideline to NEVER execute active administration tasks (i.e. change anything on the server) against a production system using a GUI administration tool like SCC. This of course is nothing you have to adopt but I'm sufficiently convinced of this approach to recommend it generally.
I'm looking forward to read more about your experience and hope you'll find my suggestions constructive.
Thanks for your Suggestion.and come up with Script based administration on my next blog.
As already mentioned by Volker
See also the SAP First Guidance Document for the Implementation of the SAP-NLS Solution
and the Blog - https://blogs.sap.com/2016/10/12/sap-nls-solution-sap-bw/
Best Regards Roland