SAP First Guidance - BW on HANA 1

SAP First Guidance

SAP BW 7.X

SAP Realtime Database Platform

Applicable Releases:

SAP BW 7.0x

SAP BW 7.3x/7.40

SAP IQ Version 15.4/16.0

and higher

External Use

With this solution, the data volume of the frequently accessed online database can be kept

relatively low. Less frequently accessed data is archived in time partitions on the SAP near-line

storage solution. Data in near-line storage resides in a highly compressed state in cost-efficient

storage with fewer backups to reduce operational costs. As the technical installation steps are the same this “SAP First Guidance” document should

make an own created customer specific documentation obsolete. It is the complementary

documentation to the existing Notes and Installation Guides.

Please Note that the SAP-NLS Solution can be used with all supported Database Versions

supported by SAP NetWeaver BW 7.3x and onwards. The Existence of SAP HANA is not

necessary.

The document is “work in progress” and not intended to be exhaustive, but it contains

everything to successfully implement the SAP-NLS Solution and more with SAP IQ.

For more Information please contact [email protected]

SAP First Guidance... SAP BW: Implementation SAP-NLS/SDA with SAP IQ 16.0

mailto:[email protected]

SAP First Guidance

SAP BW 7.X

SAP Realtime Database Platform

Version 1.93

December 2015

© Copyright 2016 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP AG. The

information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p,

System p5, System x, System z, System z10, System z9, z10, z9, iSeries,

pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390,

OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power

Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,

OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS,

HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex,

MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and

Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other

countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either

trademarks or registered trademarks of Adobe Systems Incorporated in

the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open

Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame,

and MultiWin are trademarks or registered trademarks of Citrix Systems,

Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks

of W3C®, World Wide Web Consortium, Massachusetts Institute of

Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used

under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP

BusinessObjects Explorer, StreamWork, and other SAP products and

services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in Germany and other

countries.

Business Objects and the Business Objects logo, BusinessObjects,

Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other

Business Objects products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of Business

Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere,

and other Sybase products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of Sybase, Inc.

Sybase is an SAP company.

All other product and service names mentioned are the trademarks of

their respective companies. Data contained in this document serves

informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this

document may be reproduced, copied, or transmitted in any form or for

any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license

agreement or any other agreement with SAP. This document contains

only intended strategies, developments, and functionalities of the SAP®

product and is not intended to be binding upon SAP to any particular

course of business, product strategy, and/or development. Please note

that this document is subject to change and may be changed by SAP at

any time without notice.

SAP assumes no responsibility for errors or omissions in this document.

SAP does not warrant the accuracy or completeness of the information,

text, graphics, links, or other items contained within this material. This

document is provided without a warranty of any kind, either express or

implied, including but not limited to the implied warranties of

merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without

limitation direct, spe<SID>l, indirect, or consequential damages that may

result from the use of these materials. This limitation shall not apply in

cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not

affected. SAP has no control over the information that you may access

through the use of hot links contained in these materials and does not

endorse your use of third-party Web pages nor provide any warranty

whatsoever relating to third-party Web pages.

SAP “How-to” Guides are intended to simplify the product implement-

tation. While specific product features and procedures typically are

explained in a practical business context, it is not implied that those

features and procedures are the only approach in solving a specific

business problem using SAP NetWeaver. Should you wish to receive

additional information, clarification or support, please refer to SAP

Consulting.

Any software coding and/or code lines / strings (“Code”) included in this

documentation are only examples and are not intended to be used in a

productive system environment. The Code is only intended better explain

and visualize the syntax and phrasing rules of certain coding. SAP does

not warrant the correctness and completeness of the Code given herein,

and SAP shall not be liable for errors or damages caused by the usage of

the Code, except if such damages were caused by SAP intentionally or

grossly negligent.

Disclaimer

Some components of this product are based on Java™. Any code change

in these components may cause unpredictable and severe malfunctions

and is therefore expressively prohibited, as is any decompilation of these

components.

Any Java™ Source Code delivered with this product is only to be used by

SAP’s Support Services and may not be modified or altered in any way.

Document History

Document Version Description

1.00 First official release

1.10 SAP IQ 15.4#ESD3, further SAP adaption, SAP IQ fine tuning

1.20 Optimized DB layout, SCC adaption, corrections

1.21 Software updates, one-off patch instructions, corrections

1.30 Adding smart data storage access IQ-HANA

1.31 Updates SAP IQ 16.0, SAP-NLS Backup, corrections/additions

1.32 Update IQ 16.0 SP03, IQ Agent and SCC additions

1.40 Adding HANA Extended Table Support IQ-HANA, DBACOCKPIT

1.42 Update IQ 16.0 SP04.02-05

1.81 Update IQ 16.0 SP08.01, COCKPIT adaption, corrections

1.83 Update IQ 16.0 SP08.03, SP04.06, corrections

1.84 Exchange SAP IQ Documentation, SAP HANA dynamic tiering change

1.85 Corrections/additions after SAP-NLS Workshop 09/2014

1.86 Corrections 01/2015, DBACOCKPIT corrections, DT section removed

1.87 Corrections 03/2015, adding load stripping, latest SP08.xx updates

1.88 SAP IQ SSL support, Example SAP IQ DB copy

1.90 IQ 16.0 SP10 updates, Corrections 07/2015

1.91 IQ 16.0 SP08, SP10 updates, Corrections 09/2015

1.92 Update SDA location for IQ, SP08/SP10 updates

1.93 Updates/Corrections 12/2015

Typographic Conventions

Type Style Description

Example Text Words or characters quoted

from the screen. These

include field names, screen

titles, pushbuttons labels,

menu names, menu paths,

and menu options.

Cross-references to other

documentation

Example text Emphasized words or

phrases in body text, graphic

titles, and table titles

Example text File and directory names and

their paths, messages,

names of variables and

parameters, source text, and

names of installation,

upgrade and database tools.

Example text User entry texts. These are

words or characters that you

enter in the system exactly

as they appear in the

documentation.

<Example

text>

Variable user entry. Angle

brackets indicate that you

replace these words and

characters with appropriate

entries to make entries in the

system.

EXAMPLE TEXT Keys on the keyboard, for

example, F2 or ENTER.

Icons

Icon Description

Caution

Note or Important

Example

Recommendation or Tip

SAP First Guidance … SAP NetWeaver BW-NLS Implementation with SAP IQ

February 2016 1

Table of Contents

1. Implementation SAP-NLS Solution with SAP IQ ................................................................. 3

1.1 Solution Overview........................................................................................................... 3

1.2 Checking the Pre Requisites .......................................................................................... 3

1.2.1 Relevant Notes/Information ............................................................................ 3

1.2.2 Default file system layout on the SAP IQ server .............................................. 4

1.2.3 Software Components for the SAP-NLS Implementation ............................. 6

1.2.4 SAP IQ Database Server under Linux .............................................................. 9

1.2.5 SAP IQ Database Server under Windows ...................................................... 10

2. Installation of the Components ........................................................................................... 11

2.1 Installation/Configuration of the SAP IQ database .................................................... 11

2.1.1 Sizing/Architecture/Scalability Overview ...................................................... 11

2.1.2 Installation SAP IQ 15.4 Software ................................................................... 12

2.1.2.1 Add the SAP IQ ODBC driver 15.4 to the kernel ........ 12

2.1.3 Installation SAP IQ 16.0 Software .................................................................. 13

2.1.4 Apply a Service Pack (SP) to the IQ 16.0 software ...................................... 24

2.1.4.1 Apply Patches for SAP IQ 16.0 SP04 ....................... 24

2.1.4.2 Apply SP04 for SAP IQ 16.0 (full) ..............................25

2.1.4.3 Apply one off Patch SP04.05 on top of SP04.......... 34

2.1.4.4 Apply one off Patch SP04.06 on top of SP04 ......... 34

2.1.5 Apply Patches for SAP IQ 16.0 SP08 ............................................................ 34

2.1.5.1 Apply SP08.01 for SAP IQ 16.0 ................................. 34

2.1.5.2 Apply one off Patch SP08.02 for SAP IQ 16.0 ......... 34

2.1.5.3 Apply one off Patch SP08.03 for SAP IQ 16.0 ..........35

2.1.5.4 Apply SP08.20 for SAP IQ 16.0 (full) ........................35



2.1.5.7 Apply SP08.27 for SAP IQ 16.0 (full) ........................ 36


2.1.5.9 Apply SP08.32 for SAP IQ 16.0 (full) ......................... 37



2.1.6 Apply Patches for SAP IQ 16.0 SP10 ............................................................. 38




2.1.7 Upgrade from SAP IQ from Version 15.4 to 16.0 .......................................... 40

2.1.8 Upgrade SAP IQ from Version 16.0 SP04.0x to SP08.0x ............................ 41

2.1.9 Upgrade SAP IQ to SP10.0x........................................................................... 43

2.1.11 Build and configure a new SAP IQ 15.4/16.0 database ............................... 44

2.1.11.1 Create the SAP IQ database for NLS ........................ 44

2.1.11.2 The SAPIQDB configuration file ................................ 46

2.1.11.3 start/stop the SAP IQ database ................................ 47


February 2016 2

2.1.11.4 The SAP Control Center (SCC) ................................. 48

2.1.11.5 The SAP IQ COCKPIT (successor of SCC) ................52

2.1.11.6 Create a technical user for the IQ COCKPIT ............. 55

2.1.11.7 Pluggable Authentication Module (PAM) for UNIX .. 55

2.1.11.8 Apply the DB Options for the SAP IQ database ....... 56

2.1.11.9 Extend the SAP IQ database (datafiles/temp) ......... 57

2.1.11.10 Check the status of the SAP IQ database ................ 58

2.2 Install the SAP components for SAP IQ ..................................................................... 59

2.2.1 Add the ODBC IQ driver to the SAP Instance ............................................... 59

2.2.2 Add the IQ LibDBSL to the SAP Kernel ......................................................... 60

2.2.3 Configure unixODBC ...................................................................................... 60

2.3 Configure Smart Data Access - SAP HANA and IQ .................................................... 61

2.3.1 The SDA ODBC Extra Adapter Properties .................................................... 66

2.4 Configure SAP IQ SSL support ................................................................................... 66

2.4.1 Pre requisites .................................................................................................. 66

2.4.2 SSL Configuration .......................................................................................... 68

2.4.3 Follow up activities ......................................................................................... 69

3. Configuration of the SAP Components .............................................................................. 71

3.1 SAP IQ related .............................................................................................................. 71

3.1.1 Create/configure SAP<SID>IQDB user ........................................................ 71

3.2 SAP BW related ............................................................................................................ 73

3.2.1 Apply the latest corrections for the SAP-NLS Solution. ............................... 73

3.2.2 Transaction DBCO - database connection to SAP IQ ................................... 74

3.2.3 Transaction RSDANLCON - connection to NLS storage .............................. 75

3.2.3.1 Increasing the Performance for the SAP-NLS load .. 75

3.2.4 SAP-NLS Backup Solution .............................................................................. 76

3.2.5 Monitor the SAP-NLS Connection ................................................................. 77

3.2.5.1 RSDA_SYB_PARTITION_MONITOR .......................... 77

3.2.5.2 Setup SAP IQ for transaction DBACOCKPIT ............ 78

3.2.5.3 Adding SAP IQ to the DBACOCKPIT transaction ..... 79

4. Using the SAP-NLS Solution .............................................................................................. 82

5. Appendix ............................................................................................................................. 83

5.1 Tipp’s for the IQ Administration ................................................................................. 83

5.2 Common Maintenance Tasks for SAP IQ .................................................................. 83

5.2.1 Aliases for the .profile of SAP IQ user ........................................................... 83

5.2.2 Increasing the Size of dbspace ...................................................................... 84

5.2.3 Modifying Cache Sizes or Startup Parameters ............................................ 84

5.2.4 Backup/Restore of an SAP IQ database ...................................................... 85

5.2.4.1 SAP IQ DB copy based on existing backup .............. 85


February 2016 3

1. Implementation SAP-NLS Solution with SAP IQ

1.1 Solution Overview

Documentation:

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/60/cf63e1bbbb49429ee6c35e6ad03a45/conten

t.htm?frameset=/en/4c/75184b167821d1e10000000a42189c/frameset.htm

1.2 Checking the Pre Requisites

1.2.1 Relevant Notes/Information Note 1750249 - SAPBWNews NW BW 7.30 ABAP SP9

Note 1782744 - SAPBWNews NW BW 7.31 ABAP SP07

Note 1858550 - DownPort von NLS IQ nach BW 7.0x

Note 1796393 - SAP BW near-line solution with Sybase IQ

Note 1737415 - SAP IQ: Enable remote/secondary connect to SAP IQ

The BW System you want to use should have either SP09 for BW 7.30 or SP07 for 7.31 applied. The

existence of BW on HANA is not required, as the SAP-NLS Solution works with every Database (unicode

enabled) supported by SAP NetWeaver 7.30 and higher. See Note 1796393 for the minimum Release

Level, if you cannot make the suggested SP Number.

The SAP IQ must be implemented on a separate physical server. It is not recommended to install the

software on an existing server which held already other Database Instances, as SAP IQ leverages the

complete CPU/Memory for its own usage. One IQ server can be used for multiple SAP-NLS

implementations.

Please note that the Solution is not available for SAP NetWeaver 7.0x Releases, SAP ERP Releases based

on NetWeaver 7.0x and Non Unicode Systems. Therefore use the CBW NLS Add-On from the

Development Partner PBS – https://www.pbs-software.com/en/products/nearline-storage/sap-

bw/index.html

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/60/cf63e1bbbb49429ee6c35e6ad03a45/content.htm?frameset=/en/4c/75184b167821d1e10000000a42189c/frameset.htm

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/60/cf63e1bbbb49429ee6c35e6ad03a45/content.htm?frameset=/en/4c/75184b167821d1e10000000a42189c/frameset.htm

https://service.sap.com/sap/support/notes/1750249










http://service.sap.com/sap/support/notes/1796393

https://www.pbs-software.com/fileadmin/medien/praesentationen/PBS_CBW_NLS.pdf

https://www.pbs-software.com/en/products/nearline-storage/sap-bw/index.html

https://www.pbs-software.com/en/products/nearline-storage/sap-bw/index.html


February 2016 4

1.2.2 Default file system layout on the SAP IQ server

Please provide for now the following file system layout on the designated IQ database server:

Server name: SAPIQSERVER

Database name: SAPIQDB

User name for SAP NLS schema: SAP<SID>IQ

Binary Installation Directory: /usr/sap/<SID>/SIQ<nr>/software/ # $SYBASE

Path for SYSTEM DB: /usr/sap/<SID>/SIQ<nr>/database

Path for DB: /usr/sap/<SID>/SIQ<nr>/siqdata/db # config

Path for SYSTEM LOG: /usr/sap/<SID>/SIQ<nr>/siqdata/log

Path for SYSTEM DBSPACE: /usr/sap/<SID>/SIQ<nr>/siqdata/system

Path for server MESSAGES: /usr/sap/<SID>/SIQ<nr>/siqdata/messages

Path for TEMPORARY Space: /usr/sap/<SID>/SIQ<nr>/siqdata/temp # IQ load

Path for TMP Space: /usr/sap/<SID>/SIQ<nr>/siqtemp # IQ sort

Path for HTML Query Plans: /usr/sap/<SID>/SIQ<nr>/siqdata/html

Path for trace files: /usr/sap/<SID>/SIQ<nr>/siqdata/trace

Path for further DBSPACE: /usr/sap/<SID>/SIQ<nr>/siqdata/SAP<SID>DBSPACExxx

Where <nr> is the Instance Number for the IQ DB

MAIN up to 16GB

TEMP twice MAIN up to 32GB

USER up to the size of your IQ DB

Distinguish between the “usage types”: NLS (Near-Line Storage) and DT (SAP HANA dynamic tiering)

So the Parameter <SID> points to a Near-Line Storage Database

The Implementing of SAP DT is done via the SAP HANA Implementation and is not referenced here at all.

All following creation scripts should refer to this file structure. Furthermore it is useful to create separate

partitions for the additional directories to prevent any file system overflow.

While the files for DBSPACE/TMP are defined static (and could also be raw devices), the following files or

directories are growing and need special attention: SYSTEM DB/LOG, MESSAGES and HTML.

You might use different locations/file system for the data and backup location as /usr/sap might be too

small. For productive environments a separation of data and backup is recommended.


February 2016 5

Simplex Server Architecture

Simplex is a single instance of an SAP IQ server running on a single node (machine). In a simplex

configuration, the files may be located on a host machine or on a network storage device (or distributed

between the host and the storage device)

http://help.sap.com/Download/Multimedia/zip-iq1610/iqintro.pdf

The Multiplex Architecture is not available for the SAP-NLS solution.

http://help.sap.com/Download/Multimedia/zip-iq1608/iqintro.pdf


February 2016 6

1.2.3 Software Components for the SAP-NLS Implementation Software Packages can be downloaded from the Software Marketplace (S-User required)

SAP IQ 16.0 Base Installation http://service.sap.com/installations

SAP IQ 15.4 ESD#3, IQ 16.0 SP’s https://support.sap.com/software/patches.html

SAP IQ Version 15.4 ESD#3 at https://support.sap.com/software/patches.html (Linux and

win64)

Or SAP IQ Version 16.0 GA at http://service.sap.com/installations (Linux and win64)

http://service.sap.com/installations

http://service.sap.com/patches


http://service.sap.com/installations


February 2016 7

SAP IQ ODBC Driver/Client for 15.4 and IQ 16.0 (lightweight client)

at https://support.sap.com/software/patches.html

Note 1951041 - SybaseIQNetClient 16.0 SP03 Release Notes Information

LibDBSL for SAP IQ for 7.20/7.21 EXT-UC Kernel (included in the Sybase ASE DB Version)

at https://support.sap.com/software/patches.html

Please Note that the LibDBSL for SAP Sybase ASE/IQ and the SAP IQ ODBC driver has to be applied

on every Application Server as well, if they are available. After the files are applied no restart of the

SAP Application Server’s necessary.





February 2016 8

SAP IQ Client (Win 32-Bit) - DVD51045880 for accessing the IQ database for the sql admin.

Get the smart data access drivers for HANA (≥SP06).


February 2016 9

1.2.4 SAP IQ Database Server under Linux

Installing For the First Time

Follow these steps to install SAP IQ for the first time.

Read the release bulletin for the latest information. See the special installation instructions section

for any installation instructions not included in this document.

Complete all pre-installation tasks. Apply any required operating system patches, check to see that

there is sufficient disk space and memory, and update any necessary configuration changes.

Determine the license model you want to use. SySAM supports served and unserved license

models. See the Sybase Software Asset Management (SySAM) 2 Users Guide to determine which

model is best suited for your environment.

Use the product and licensing information you received from SAP Sybase to log in to the SAP at

https://support.sap.com/licensekey and generate a license key for your software. The

mentioned licenses can be merged into one file by the time you create them.

Install SAP IQ server components, activate your license, then start and test your server.

Install and configure SAP IQ client components

Needed Licenses for the SAP-NLS option:

http://help.sap.com/Download/Multimedia/zipiq1610/SAP_IQ_Guide_to_Licensed_Options.pdf

o 7010846 SAP IQ Enterprise Edition

o 7010848 SAP IQ Unstructured Data Analytics

o 7010850 SAP IQ Very Large Database Management Option

To figure out the correct values for CPU cores, MAC address and the TB option (4TB) which are

needed for the license generation, you can run the following checks:

o Available CPU cores (relevant for the license)

grep -i "processor" /proc/cpuinfo | sort -u | wc –l

o Available CPU processors/sockets

grep -i "physical id" /proc/cpuinfo | sort -u | wc –l

o MAC address

ifconfig

If the SAP IQ binaries are already installed, you can also use the program cpuinfo as follows:

sybase@lt5006:/usr/sap/NLS/SAPIQ/server/SYSAM-2_0/bin> ./cpuinfo

License hostid: 5cf3fcdcb2f0

Detected 160 logical processor(s), 80 core(s), in 8 chip(s)

Installation SAP IQ 16.0 SP10

http://help.sap.com/iq1610/#section2

The Best Practice Guide for SAP IQ 16 can be found here - SAP IQ 16: Best Practices Guide

https://support.sap.com/licensekey

http://help.sap.com/Download/Multimedia/zipiq1610/SAP_IQ_Guide_to_Licensed_Options.pdf

http://scn.sap.com/docs/DOC-39896


February 2016 10

Installation Details: http://help.sap.com/saphelp_iq1610_iqicg_lin/helpdata/en/a8/921a5584f21015a16ac3f053c57a98/frameset.htm

Create the OS user sybase on the SAP IQ database server. The user requires remote access

authorization for remote accesses (TELNET or SSH) to the SAP IQ database server.

Set up the directory /usr/sap/<SID>/server on the SAP IQ database server. The owner is

user sybase. The directory should have at least 10 GB disk storage available for the Sybase

software.

For testing purposes: Set up the directory /usr/sap/<SID>/sapdata on the SAP IQ database

server. Owner is user sybase. The directory should guarantee disk space of at least 180 GB.

Productive use: Set up the directory /usr/sap/<SID>/sapdata on the SAP IQ database

server. Owner is user sybase. The directory should guarantee disk space of at least 300 GB. In

addition, there are the partitions of the database instance that are made available via SAN. If a

RAW device-based SAP IQ database instance should be used, the files

/dev/raw/raw<counter> and the RAW control file /dev/rawctl must be owned by user

sybase. The ownership has to be ensured even after the new start of the server.

Set up the directory /usr/sap/<SID>/sapdata/tmp according to the sizes above for data. The

Amount of disk space and data files for data and temp are equal. The owner is user sybase.

Additionally, set up the following directories as stated in Chapter 1.2.2

1.2.5 SAP IQ Database Server under Windows Installation Details: http://help.sap.com/saphelp_iq1610_iqicg_win/helpdata/en/a8/8e108184f21015afb7d500d7f48dbb/frameset.htm

The installation is performed on the SAP IQ database server under a user with administration

rights.

Set up the directory <drive>:\usr\sap\sybase\server on the SAP IQ database server. The

directory should have at least 10 GB disk storage available for the Sybase software.

For testing purposes: Set up the directory <drive>:\usr\sap\<SID>\sapdata on the SAP

IQ database server. The directory should guarantee disk space of at least 180 GB.

Productive use: Set up the directory <drive>:\usr\sap\<SID>\sapdata on the SAP IQ

database server. The directory should guarantee disk space of at least 300 GB. In addition,

there are the partitions of the database instance that are made available via SAN.

Set up the directory <drive>:\usr\sap\<SID>\sapdata\tmp

according to the sizes above for data.

The Amount of disk space and data files for data and temp are equal.

Additionally, set up the following directories as stated in Chapter 1.2.2

SAP IQ Development Center

http://scn.sap.com/community/sybase-iq

http://help.sap.com/saphelp_iq1608_iqicg_lin/helpdata/en/a8/921a5584f21015a16ac3f053c57a98/frameset.htm

http://help.sap.com/saphelp_iq1608_iqicg_lin/helpdata/en/a8/921a5584f21015a16ac3f053c57a98/frameset.htm

http://help.sap.com/saphelp_iq1608_iqicg_win/helpdata/en/a8/8e108184f21015afb7d500d7f48dbb/frameset.htm

http://help.sap.com/saphelp_iq1608_iqicg_win/helpdata/en/a8/8e108184f21015afb7d500d7f48dbb/frameset.htm

http://scn.sap.com/community/sybase-iq


February 2016 11

2. Installation of the Components

2.1 Installation/Configuration of the SAP IQ database

2.1.1 Sizing/Architecture/Scalability Overview

For a general sizing guideline see the following document: http://scn.sap.com/docs/DOC-41455

http://help.sap.com/Download/Multimedia/zip-iq1610/SAP_IQ_Performance_and_Tuning_Guide.pdf

Simplex Server Architecture

Simplex is a single instance of an SAP IQ server running on a single node (machine). In a simplex

configuration, the files may be located on a host machine or on a network storage device (or distributed

between the host and the storage device).

http://help.sap.com/saphelp_iq1610_iqintro/helpdata/en/a4/43ff3884f21015a8a2d49481839a6c/cont

ent.htm?frameset=/en/a8/8f131584f21015a82dd9c1d6f28058/frameset.htm&current_toc=/en/a8/8f1

31584f21015a82dd9c1d6f28058/plain.htm&node_id=19

Multiplex Server Architecture

Multiplex are multiple instances of SAP IQ servers running on multiple machines. SAP IQ supports read-

write transactions from multiple servers in the multiplex.

Each server has its own temporary store and catalog store. The shared IQ Store is common to all servers.

The primary server, or coordinator, manages all global read-write transactions and maintains the global

catalog. The table version log (TLV log) stores information about DLL operations and communicates

information about new table versions to the secondary servers.

http://help.sap.com/saphelp_iq1610_iqintro/helpdata/en/a4/43d07284f21015b92380028fcec7fa/content.htm?frameset=/en/a4/43ff3884f21015a8a2d49481839a6c/frameset.htm&current_toc=/en/a8/8f131584f21015a82dd9c1d6f28058/plain.htm&node_id=20

The Multiplex Architecture is not available for the SAP-NLS solution.

Scalability

SAP IQ’s patented design permits databases to scale to contain many terabytes of data.

Its index-based structure allows the database to store your data in a much smaller space than the size of

the raw input data, and access it far faster than a traditional relational database. These features make

SAP IQ ideal for storing and accessing very large databases (VLDBs).

Database administrators need to understand the options and features that affect performance, and follow

documented guidelines. While many default settings automatically provide the greatest efficiency, you

may need to experiment with certain option settings for the fastest results, based on your configuration,

your loading requirements, and your queries. Setting these options appropriately is necessary for top

performance in any SAP IQ database, but is especially important as your database grows to the multi-

terabyte scale.

http://help.sap.com/saphelp_iq1610_iqintro/helpdata/en/a6/9b9c3484f21015a68780567e0afdd6/content.htm?frameset=/en/a4/43d07284f21015b92380028fcec7fa/frameset.htm&current_toc=/en/a8/8f131584f21015a82dd9c1d6f28058/plain.htm&node_id=38&show_children=false


http://help.sap.com/Download/Multimedia/zip-iq1610/SAP_IQ_Performance_and_Tuning_Guide.pdf

http://help.sap.com/saphelp_iq1608_iqintro/helpdata/en/a4/43ff3884f21015a8a2d49481839a6c/content.htm?frameset=/en/a8/8f131584f21015a82dd9c1d6f28058/frameset.htm&current_toc=/en/a8/8f131584f21015a82dd9c1d6f28058/plain.htm&node_id=19










February 2016 12

2.1.2 Installation SAP IQ 15.4 Software

After downloading the software (IQ 15.4 ESD#03) and unpacking the executables into a temporary

directory start the Installation on Linux with the user sybase

You can use Putty (0.61) with the Xming Extension. For details how to use it, visit the URL

http://www.straightrunning.com/XmingNotes/

sybase@lt5006:/data/software/sybase/IQ15.4/server> ./setup.bin

On Windows run the setup.exe by double clicking the setup.exe

The detailed Steps are described with the software installation of SAP IQ 16.0 in Chapter 2.1.3, as the

steps are identical.

2.1.2.1 Add the SAP IQ ODBC driver 15.4 to the kernel

Unpack the SAR file to a temporary directory and copy the files to the SAP Kernel directory located at

/usr/sap/<SID>/DVEBMGS<nr>/exe

A restart of the SAP System is not necessary and the libraries must have 775 as file permission.

sybase@lt5006: /data/software/sybase/IQ15.4/Note1737415>

SAPCAR -xvf _sar\ IQCLIENT154SP01_0-10012189.SAR

SAPCAR: processing archive _sar/IQCLIENT154SP01_0-10012189.SAR (version 2.01)

SAPCAR: 25 file(s) extracted

http://www.straightrunning.com/XmingNotes/


February 2016 13

2.1.3 Installation SAP IQ 16.0 Software Documentation:

http://help.sap.com/iq1610/#section2 and http://help.sap.com/iq1610/#section5 Details for the sybase control center (SCC) installation http://help.sap.com/iq1610/#section5

After downloading the software (IQ 16.0 SP00) and unpacking the executables into a temporary directory

start the Installation on Linux with the user sybase

You can use Putty (0.65) with the MobaXterm. For details how to use it, visit the URL

http://mobaxterm.mobatek.net/features.html

sybase@lt5006:/data/software/sybase/IQ16_0/server> ./setup.bin

On Windows run the setup.exe by double clicking the setup.exe






February 2016 14

The directory /usr/sap/NLS/SAPIQ/server might already available and the environment variable

$SYBASE will point to /usr/sap/<SID>/SIQ<nr>/server


February 2016 15

In case of an Upgrade from IQ 15.4 to Version 16.0 you will find different directories here for the releases.

For the ease of the setup the option “Typical” contains the selected options from the Install Set

“Custom”. So you can directly proceed with the Option “Typical”.


February 2016 16

The Installation of the SySAM License Server is not necessary. The temporary license works for 30 days

and will be replaced by an official purchased license. If you plan to use a License Server for the complete

Sybase Landscape check this with the SAP Sybase Representatives.


February 2016 17

Don’t install the Evaluation Version of SAP IQ 16.0

Select the End-user license agreement and agree to the terms of the Sybase license install location.


February 2016 18

Apply the license in a later step.

Choose Enterprise Edition (EE - for all Options) and CPU License (CP).


February 2016 19

This is an optional step for alerting, mainly license expiring messages.


February 2016 20

HTML ports for the Sybase Central Application (web/java based). Check the Ports with your existing

available Ports, e.g. see - http://scn.sap.com/docs/DOC-11602



February 2016 21

To connect to Sybase Control Center, direct your browser to: https://<scc_server_hostname>:8283/scc

The default user accounts are sccadmin (Sybase Control Center) and uafadmin (SCC agent).


February 2016 22

Starting/Stopping with console prompt: $SYBASE/SCC-3_3/bin/scc.sh and scc.sh --stop

Starting in background: nohup $SYBASE/SCC-3_3/bin/scc.sh 2>&1 > scc-console.out &

If you are not ask about the password of user uafadmin/Sybase4me


February 2016 23

After the software installation is finished you can access the database instance from the Sybase control

center and create the main database.

Post- Installation Steps

Add the following lines to ~sybnls/.profile

source=/usr/sap/NLS/SAPIQ/IQ.sh

export

LD_LIBRARY_PATH=/usr/sap/HBT/SYS/exe/uc/linuxx86_64/hdbclient:$LD_LIBRARY_PATH

export PATH=$PATH: /usr/sap/NLS/SAPIQ/server/shared/JRE-7_0_7_64BIT/bin

export IQTMP16=/usr/sap/NLS/SAPIQ/sapdata/temp

alias start_siq='start_iq @/usr/sap/NLS/SAPIQ/SAPIQDB.cfg /usr/sap/NLS/SAPIQ

/SAPIQDB.db'

alias stop_siq='stop_iq -stop one'

alias start_SCC='nohup $SYBASE/SCC-3_3/bin/scc.sh >& scc-console.out &'

alias start_COCKPTIT='nohup $SYBASE/COCKPIT-4/bin/cockpit.sh >& cockpit-

console.out &'

alias stop_SCC='$SYBASE/SCC-3_3/bin/scc.sh --stop'

alias stop_COCKPIT='$SYBASE/COCKPIT-4/bin/cockpit.sh --stop'

Only the first line is strictly required, the other are optional / for convenience. If the directory /bin/env does not exist, enter the following command as root user

If the directory /bin/env does not exist, enter the following command as root user:

ln -s /usr/bin/env /bin/env


February 2016 24

2.1.4 Apply a Service Pack (SP) to the IQ 16.0 software

You should always consider implementing the latest available SP/Patch combination for SAP IQ 16.0

2.1.4.1 Apply Patches for SAP IQ 16.0 SP04

By the Availability of a service pack (SP) for the IQ 16.0 download them from the location

https://support.sap.com/software/patches.html

Online Help for SAP IQ16 SP04/SP08 -

http://help.sap.com/saphelp_iq1610_iqnfs/helpdata/en/a8/8d9d8684f21015b17fe04b3b8d27f6/frame

set.htm

The upgrade process is identical as the installation process if a complete binary upgrade is available.

See the Chapter 2.1.3.

Furthermore the Installation Routine will not detect an existing IQ installation; it will run as a fresh

Installation. Make sure you enter the correct path for $SYBASE

The following list is a chronology of the existing corrections for SAP IQ 16.0. You don´t have to apply all of

them. As patches for SAP IQ are cumulative, it is sufficient to apply the latest one, if this is a new

implementation.


http://help.sap.com/saphelp_iq1608_iqnfs/helpdata/en/a8/8d9d8684f21015b17fe04b3b8d27f6/frameset.htm

http://help.sap.com/saphelp_iq1608_iqnfs/helpdata/en/a8/8d9d8684f21015b17fe04b3b8d27f6/frameset.htm


February 2016 25

2.1.4.2 Apply SP04 for SAP IQ 16.0 (full)

Note 2015011 - SAPIQ 16.0 SP4 Release Notes Information

As SP03 was not a supported Patch for SAP-NLS, this minimum SP Level to start is 04

Online Help for SAP IQ16 SP03/SP04

http://help.sap.com/saphelp_iq1610_iqnfs/helpdata/en/90/541f2a088e45ea819466732d3db3b5/cont

ent.htm?frameset=/en/a3/573abe84f210159968c832723d04d8/frameset.htm&current_toc=/en/a8/8

d9d8684f21015b17fe04b3b8d27f6/plain.htm&node_id=22

Unpack the tar file to a temporary directory and run the setup.bin command

lt5006:/data/software/sybase/IQ16_0> tar -xvf IQSERV160004_0-20011180.TGZ

lt5006:/data/software/sybase/IQ16_0/ebf22161> ./setup.bin

To enable the X-Windows support for the IQ installer, follow the Instructions.



Make sure that the IQ server and the SCC is stopped before you start the update.



http://help.sap.com/saphelp_iq1608_iqnfs/helpdata/en/90/541f2a088e45ea819466732d3db3b5/content.htm?frameset=/en/a3/573abe84f210159968c832723d04d8/frameset.htm&current_toc=/en/a8/8d9d8684f21015b17fe04b3b8d27f6/plain.htm&node_id=22





February 2016 26

Starting SCC in Background nohup ./scc.sh >& scc-console.out &

Stopping SCC./scc.sh –stop

The SP installation doesn’t recognize the existing IQ installation, simply continue.


February 2016 27

Like the full initial SAP IQ installation, the option “typical” contains all needed options from “custom”


February 2016 28

Make sure you choose the existing license, otherwise you will not be able the start the IQ server.


February 2016 29

This is an optional task; it can be also revoked later.


February 2016 30


February 2016 31

Check that the right ports are used later in the SCC start. Check the file /usr/sap/NLS/SAPIQ/server/SCC-3_3/bin/scc-console.out

Check that the right port is used later in the IQ Agent Registration (8284).


February 2016 32

Check the file /usr/sap/NLS/SAPIQ/server/SCC-3_3/bin/scc-console.out


February 2016 33

The IQ lightweight client located in the SAP executables Directory has to be updated as well to SP04

according Chapter 2.1.7.1 as well.


February 2016 34

2.1.4.3 Apply one off Patch SP04.05 on top of SP04

Note 2037707 - SAP_IQ 16.0 SP04 PL05 Release Notes Information

SAP IQ one-off patches are fixing temporary problems as intermediate solution, until the next mayor

Support Package will be available. If already a Patch is available, you can skip the manual procedure.

To apply the one off patch 04.05 on top of SP04 for SAP IQ 16.0

Simply follow the description in Chapter 2.1.4.6

2.1.4.4 Apply one off Patch SP04.06 on top of SP04


As the binary patches are cumulative, you can directly apply the latest one off patch for SAP IQ.


2.1.5 Apply Patches for SAP IQ 16.0 SP08

2.1.5.1 Apply SP08.01 for SAP IQ 16.0

Note 2021344 - SAPIQ 16.0 SP08 Release Notes Information


Note 2016130 - SAP IQ: Remote connection to IQ 16.0 SP8

To apply SP08.01 for SAP IQ 16.0 follow Chapter 2.1.4.2 in this First Guidance Document.

As SP08.01 is a full update, you don´t have to apply SP08.00 first.

2.1.5.2 Apply one off Patch SP08.02 for SAP IQ 16.0


sybase@lt5006:/usr/sap/NLS/SAPIQ/database> ./stop_SAPIQDB

lt5006:/sybase> tar -xvf IQSERV160008P_2-20011180.TGZ

lt5006:/sybase/ebf23227/iq1600_sp08.02> dir

drwxr-xr-x 2 sybase users 0 Jul 15 00:05 bin64

drwxr-xr-x 2 sybase users 0 Jul 15 00:05 java

drwxr-xr-x 2 sybase users 0 Jul 15 00:19 lib64

drwxr-xr-x 2 sybase users 0 Jul 15 00:20 res

lt5006:/mnt/_i008817/sybase/ebf23227/iq1600_sp08.02> cp -rf *

/usr/sap/NLS/SAPIQ/server/IQ-16_0

sybase@lt5006:/usr/sap/NLS/SAPIQ/database> ./start_SAPIQDB
















February 2016 35

2.1.5.3 Apply one off Patch SP08.03 for SAP IQ 16.0


Note 1737415 - Sybase IQ: Enable remote/secondary connect to SAP Sybase IQ

Note 1999431 - SIQ: Setting up SSL for connections to IQ



In case the script patch_iq doesn’t work run in advance zypper install ksh

2.1.5.4 Apply SP08.20 for SAP IQ 16.0 (full)

Note 2098063 - SAP Sybase IQ 16.0 SP08 PL20 Release Notes Information

SAP IQ SP08.20 is delivered as a full update. So you can either update your existing implementation or

directly use this setup for a fresh installation.

It contains all updates between SP08.04 to 09 and the update to SP08.20. Details about the fixes can be

found in the EBF23761_README.txt attached to the mentioned SAP Note above.



To Update the SAP IQ server to Version SP08.20, run the upgrade procedure as stated in Chapter 2.1.6 You can always apply the latest one of patch, as they are cumulative.



https://css.wdf.sap.corp/sap/support/notes/1737415





https://websmp130.sap-ag.de/sap/support/sapnotes/public/services/attachment.htm?iv_key=012003146900001989332014&iv_version=0001&alt=2BCE4CB10DF674B172F4F3F7B32A284F4933B530348CF70F378C3730B4324FF2342D08498E8FCAD1F54A8A0C4B732A2FCE3208094BF54CCCCE7429A84C328F37F0C82EF476D4750C09514BCECFCFCE4C8DCF4BCC4DB5F575F4F4F3F57771F571F6F70B01B25D83D4120B0A722092A599504EB16D715E3E00&iv_guid=FA5696BFF54E0A4EA310D73C22AE0490


February 2016 36


Note 2120356 – SAP Sybase IQ 16.0 SP08 PL23 Release Notes Information

Note 2118895 - Improved Encrypted Password connection parameter support

SAP IQ SP08.23 is delivered as a one of patch. It contains all updates between SP08.21 to 23. Details

about the fixes can be found in the EBF24077_README.txt attached to the mentioned SAP Note above.






SAP IQ SP08.24 is delivered as a one of patch. It contains all updates between SP08.21 to 24. Details








directly use this setup for a fresh installation. It contains all updates up to SP08.27.Details about the fixes

can be found in the EBF24296_README.txt attached to the mentioned SAP Note above.





https://websmp130.sap-ag.de/sap/support/sapnotes/public/services/attachment.htm?iv_key=012006153200000187432015&iv_version=0001&alt=2BCE4CB10DF674B172F4F3F7B32A284F4933B530B08CF70F378C3730B40AAD2A0DB0CC702FF330CD8FCA0B704B76320D328C74F42AAE8834F6CFF3720A0D4F0932760EB670D7750C09514BCECFCFCE4C8DCF4BCC4DB5F575F4F4F3F57771F571F6F70B01B25D83D4120B0A722092A599504EB16D715E3E00&iv_guid=4E7E3DB8067C5344A9452BED8B0B0F56


https://websmp230.sap-ag.de/sap/support/sapnotes/public/services/attachment.htm?iv_key=012006153200000377302015&iv_version=0001&alt=2BCE4CB10DF674B172F4F3F7B32A284F4933B530328EF70F378A3730B48A3235F70BCA7337482932AF0A70F5292D0C2E34C934F20BB434CCD735343074C937D775D735CEF6D0750C09514BCECFCFCE4C8DCF4BCC4DB5F575F4F4F3F57771F571F6F70B01B25D83D4120B0A722092A599504EB16D715E3E00&iv_guid=119050DFBE1F0D40AAF693CB256307A1


https://websmp230.sap-ag.de/sap/support/sapnotes/public/services/attachment.htm?iv_key=012006153200000614542015&iv_version=0001&alt=2BCE4CB10DF674B172F4F3F7B32A284F4933B530B48CF70F378A3730B4722F8D0FD32D732976CE35B7F4314972CB73CE482A76C937882F7109F0F3740AC82EF770ADC8CD73D7750C09514BCECFCFCE4C8DCF4BCC4DB5F575F4F4F3F57771F571F6F70B01B25D83D4120B0A722092A599504EB16D715E3E00&iv_guid=F73FDFEFEC726A4C9300F7968DD3B6E4


February 2016 37

This Update works together with the improved LOAD performance updates for SAP-NLS.

Note 2130587 - SYB IQ: performance enhancement for LOAD statement

Note 2109015 - Continuation of Archiving Requests for Copy, Verification, and Deletion Phase in parallel

Note 2128579 - Data Load into SAP IQ during Copy Phase utilizes only one server-side Thread


Note 2151182 - SAP Sybase IQ 16.0 SP08 PL30 Release Notes Information







Note 2171604 - SAPSybaseIQ 16.0 SP08 PL32

SAP IQ SP08.32 is delivered as a one of patch. It contains all updates between up to SP08.35. Details




As SP08.32 is a full update, you don´t have to apply SP08.00 or any updates in between first.





https://websmp230.sap-ag.de/sap/support/sapnotes/public/services/attachment.htm?iv_key=012003146900000320982015&iv_version=0001&alt=2BCE4CB10DF674B172F4F3F7B32A284F4933B5303288F70F378A3730B44A4C2DD17574F4354FAB0C310BAC48F6B30C33318C7777CDF20CCF76CBF337F1CBAB3234350A0C4AD1750C09514BCECFCFCE4C8DCF4BCC4DB5F575F4F4F3F57771F571F6F70B01B25D83D4120B0A722092A599504EB16D715E3E00&iv_guid=F2A0EAE99255D6478015C8C71DEC4CCE


https://websmp230.sap-ag.de/sap/support/sapnotes/public/services/attachment.htm?iv_key=012003146900000986242015&iv_version=0001&alt=2BCE4CB10DF674B172F4F3F7B32A284F4933B530348FF70F378A3730B40A494F0D3231F02D09712B7409372808F1CF75C9F4097473753349330C0F2C3188F0724BF52E08CBD1750C09514BCECFCFCE4C8DCF4BCC4DB5F575F4F4F3F57771F571F6F70B01B25D83D4120B0A722092A599504EB16D715E3E00&iv_guid=B102237BB249394DA828633D742D5A29


February 2016 38


Note 2199398 - SAPSybaseIQ 16.0 SP08 PL35 Release Notes Information

SAP IQ SP08.35 is delivered as a full update. It contains all updates between SP08.31 to 35. Details about

the fixes can be found in the EBF25060_README.txt attached to the mentioned SAP Note above.





SAP IQ SP08.38 is delivered as a full update. It contains all updates between SP08.31 to 38. Details about

the fixes can be found in the EBF25400_README.txt attached to the mentioned SAP Note above.



2.1.6 Apply Patches for SAP IQ 16.0 SP10


Note 2165297 - SAP IQ 16.0 SP 10 Release Note

Note 2186634 - SYBASE IQ SERVER 16.0 SP10 PL01 Release Notes Information

Note 2194507 - SYBASE IQ SERVER 16.0 SP10 PL02 Release Notes Information






What‘s new in SAP IQ 16.0 SP10

http://help.sap.com/Download/Multimedia/zip-iq1610/SAP_IQ_Whats_New.pdf

Point-in-Time Recovery

Point-in-time recovery logs and log backups are version specific. SP 10 point-intime recovery logs and log

backups require an SP 10 engine. To perform an SP 8 point-in-time recovery with SP 8 logs, use an SP 8

engine. Use an SP 8.1 engine to perform point-in-time recovery with SP 8 or SP 8.1 logs.

LOAD TABLE IGNORE CONSTRAINT Behavior Change

In SAP IQ 16.0, a redesign in memory usage reduced memory footprint and provided better parallel

processing for loads. As a result, the row log file for LOAD TABLE IGNORE CONSTRAINT now returns

NULL strings instead of the original file contents for certain values when data conversion errors occur.


https://websmp230.sap-ag.de/sap/support/sapnotes/public/services/attachment.htm?iv_key=012006153200001411882015&iv_version=0002&alt=2BCE4CB10DF674B172F4F3F7B32A284F4933B5303288F70F378A3730B42A0CF1CE4ED40D74AB32288A32F2F03573710B364F0D4E2E730AB228758DF04BCF2E7029F4307331D7750C09514BCECFCFCE4C8DCF4BCC4DB5F575F4F4F3F57771F571F6F70B01B25D83D4120B0A722092A599504EB16D715E3E00&iv_guid=2938915EC20FE54D827ACEA0E4B14849


https://websmp130.sap-ag.de/sap/support/sapnotes/public/services/attachment.htm?iv_key=012003146900001806582015&iv_version=0001&alt=2BCE4CB10DF674B172F4F3F7B32A284F4933B530348EF70F378C3730B44AAA74F272338F0C76F3F34FB4C8090AB08C8F4CCB294D73AB4A764E4FCC082DF072AC7034304F2CD6750C09514BCECFCFCE4C8DCF4BCC4DB5F575F4F4F3F57771F571F6F70B01B25D83D4120B0A722092A599504EB16D715E3E00&iv_guid=2DFC92B50F36CC4C8C1302FAABE6D026




https://websmp130.sap-ag.de/sap/support/sapnotes/public/services/attachment.htm?iv_key=012006153200001273552015&iv_version=0001&alt=2BCE4CB10DF674B172F4F3F7B32A284F4933B530348EF70F378C3730B4322AF6F7724B4B8F8A7431CE2F4975C98E4A2A2F322B738F702B32362D2A29350DF5A82A0D4B2E2BD1750C09514BCECFCFCE4C8DCF4BCC4DB5F575F4F4F3F57771F571F6F70B01B25D83D4120B0A722092A599504EB16D715E3E00&iv_guid=1F2F80AAC0C7A647A726BA1EC1EA107D

http://help.sap.com/Download/Multimedia/zip-iq1610/SAP_IQ_Whats_New.pdf


February 2016 39

Direct I/O Support

SAP IQ now opens all UFS (Unix File System) database files using direct I/O.

start_iq Utility: -iqhrt Database Server Option (New)

Use the -iqhrt switch of the start_iq utility to enable high-resolution timing (to the millisecond) in the IQ

message log.


Note 2212909 - SAP IQ 16.0 SP10 PL03 Release Notes Information


directly use this setup for a fresh installation. It contains all updates up to SP10.03. Details about the fixes







directly use this setup for a fresh installation. It contains all updates up to SP10.06. Details about the fixes





https://websmp230.sap-ag.de/sap/support/sapnotes/public/services/attachment.htm?iv_key=012003146900001206222015&iv_version=0001&alt=2BCE4CB10DF674B172F4F3F7B32A284F4933B530B488F70F378A3730B4720C36F3772F0BF173F52DC8CF32094B0D0FF4D0CD4DF6742948A988F4097732C828D175754A0EF5D1750C09514BCECFCFCE4C8DCF4BCC4DB5F575F4F4F3F57771F571F6F70B01B25D83D4120B0A722092A599504EB16D715E3E00&iv_guid=99F9B5676A2672418C00CCF8D4CFA1F4


https://websmp130.sap-ag.de/sap/support/sapnotes/public/services/attachment.htm?iv_key=012003146900002046902015&iv_version=0002&alt=2BCE4CB10DF674B172F4F3F7B32A284F4933B5303488F70F378C3730B42AF437C84DB10849F14ACDAEF2C8F44C7131C94FF7F633CE0BF388AA0C712B3177CE2935D12DF24FD6750C09514BCECFCFCE4C8DCF4BCC4DB5F575F4F4F3F57771F571F6F70B01B25D83D4120B0A722092A599504EB16D715E3E00&iv_guid=399F0BDF48C29044B5BEA67DFE938F14


February 2016 40

2.1.7 Upgrade from SAP IQ from Version 15.4 to 16.0

If you started your Implementation with the Version 15.4 ESD#3 or earlier e.g. with the PBS NLS Add-On

and you want to upgrade to the latest Version with CESU-8 support, which is 16.0 SP01.03 you have to

upgrade the existing database software and the content of the database.

Detailed Upgrade procedure is described here:

http://help.sap.com/saphelp_iq1610_iqmig_lin/helpdata/en/a8/8cb5ae84f210158632dabe4df1f2d4/fr

ameset.htm

Update the database software as described in Chapter 2.1.3. Therefore you have to stop the IQ database

Stop the IQ database with

sybase@lt5006:/usr/sap/sybase/server/database>stop_iq

After the software update you will find a new directory in your $SYBASE root directory called IQ-16_0

Source the new IQ 16.0 database software

sybase@lt5006:/usr/sap/sybase/server>. IQ.sh

Check the .profile file in the user sybase home directory and the SYBASE.sh file for the correct

settings. The IQ.sh Profile contains the current setting for the correct IQ software Version.

Start the IQ database (for the Upgrade Process) with

sybase@lt5006:/usr/sap/NLS/SAPIQ/database>

start_iq @SAPIQDB.cfg SAPIQDB.db -iqro 1 -gm 1

Run the I-SQL Interface with

alter database upgrade;

http://help.sap.com/saphelp_iq1608_iqmig_lin/helpdata/en/a8/8cb5ae84f210158632dabe4df1f2d4/frameset.htm

http://help.sap.com/saphelp_iq1608_iqmig_lin/helpdata/en/a8/8cb5ae84f210158632dabe4df1f2d4/frameset.htm


February 2016 41


sybase@lt5006:/usr/sap/NLS/SAPIQ/database>stop_iq

Start the IQ database again (in normal mode) with


start_iq @SAPIQDB.cfg SAPIQDB.db

Your database IQ is now upgraded to Version 16.0.

As a final step apply the DB options again as described in Chapter 2.1.5.2

2.1.8 Upgrade SAP IQ from Version 16.0 SP04.0x to SP08.0x


http://help.sap.com/saphelp_iq1610_iqmig_lin/helpdata/en/ca/5240b988984d79bef3d2f0e13e095c/

content.htm?frameset=/en/a8/8cb5ae84f210158632dabe4df1f2d4/frameset.htm&current_toc=/en/a

8/8cb5ae84f210158632dabe4df1f2d4/plain.htm&node_id=3&show_children=false

Start the IQ database (for the Upgrade Process) with


start_iq @SAPIQDB.cfg SAPIQDB.db -iqro 1 -gm 1 -iqrvrec_bypass 1

Run the I-SQL Interface with

alter database upgrade;


sybase@lt5006:/usr/sap/NLS/SAPIQ/database>stop_iq



http://help.sap.com/saphelp_iq1608_iqmig_lin/helpdata/en/ca/5240b988984d79bef3d2f0e13e095c/content.htm?frameset=/en/a8/8cb5ae84f210158632dabe4df1f2d4/frameset.htm&current_toc=/en/a8/8cb5ae84f210158632dabe4df1f2d4/plain.htm&node_id=3&show_children=false




February 2016 42

Start the IQ database again (in normal mode) with



There are new features available with this Service Pack, and it is mandatory to replace the existing

$SYBASE Directory completely.

Check the existing IQ Release first with the following command:

% $IQDIR16/bin64/start_iq -v2

Restore your existing SCC configuration from your existing Backup of the existing server directory, e.g.

cp csi_config.xml /usr/sap/sybase/server/SCC-3_3/conf

If you installed SP08.0 or higher directly please Note that the way of activating the correct license key has

changed. After the license is installed, you have to activate the IQ_VLDBMGMT option as follows:

sp_iqlmconfig 'allow', 'ALL';

sp_iqlmconfig 'allow', 'IQ_VLDBMGMT', 1;

The IQ_UDA option can be activated with the creation of a partitioned table via the I-SQL client:

create table udatest (c1 integer PRIMARY KEY) partition by range (c1) (PMAX

values <= (MAX));

sp_iqlmconfig

Your database IQ is now upgraded to Version 16.0 SP08.01

As a final step apply the DB options again as described in Chapter 2.1.5.2


February 2016 43

2.1.9 Upgrade SAP IQ to SP10.0x

Note 2186634 - SYBASE IQ SERVER 16.0 SP10 Release Notes Information

Note 2186692 – SAP Sybase IQNC 16.0 SP10 PL01 Release Notes Information

Note 2044940 - Initial password to be used for authentication of SAP IQ Cockpit agent

SAP Help Information - http://help.sap.com/iq1610



SAP IQ Migration Guide to SP10

http://help.sap.com/Download/Multimedia/zip-iq1610/SAP_IQ_Migration_Linux.pdf

In Interactive SQL, run sp_iqcheckoptions on each database, and capture the output.

sp_iqcheckoptions generates a list of current database values and options. Use these values to

restore your database settings after you upgrade.

Validate your license against each database to ensure that your license maintenance support is in (or

near) compliance.

Migrating a database to SP 10 automatically disables point-in-time recovery (PITR). To re-enable point-in-

time recovery, complete all steps in this procedure, including a FULL, INCREMENTAL, or INCREMENTAL

SINCE FULL backup.

SET OPTION PUBLIC.IQ_POINT_IN_TIME_RECOVERY_LOGGING = 'ON'

ALTER DBSPACE IQ_SYSTEM_LOG RENAME /file-prefix

Configuration and Deployment Information

http://help.sap.com/iq1610#section3

If you are installing an initial Version of IQ 16.0 SP10.0x you don´t have to run any additional upgrade

scripts. If you are upgrading from a lower Version please follow the instruction from Chapter 2.1.6




http://help.sap.com/iq1610


http://help.sap.com/Download/Multimedia/zip-iq1610/SAP_IQ_Migration_Linux.pdf

http://help.sap.com/iq1610#section3


February 2016 44

2.1.11 Build and configure a new SAP IQ 15.4/16.0 database At this point in time this building step is a manual process which contains steps directly on the server and

some steps via the I-SQL interface from your client PC.

In our example we installed SAP IQ 16.0 on a Linux server with 16x4 Core CPU cores (necessary later for

the data stripping) and 256GB RAM. The SAP IQ ODBC client is installed on the Windows client as 64-Bit

application. The Software contains the Sybase Central 6.1 which can be used for the Administration of the

IQ database.

The Sybase Central Client picks the local language from your PC, so you see some screenshot’s in

German. Our used server is lt5006 and the SAP system SID is <SID>. The notation of the NLS

database follows the naming convention of a SAP database instance: SAP<SID>IQ

Check the .profile file in the user sybase home directory and the SYBASE.sh file for the correct

settings. The IQ.sh Profile contains the current setting for the correct IQ software Version.

. /usr/sap/NLS/SAPIQ/server/IQ-16_0/IQ-16_0.sh

cd /usr/sap/NLS/SAPIQ/database

2.1.11.1 Create the SAP IQ database for NLS

To create the database instance for the NLS solution the process has to initialize with the start of a

“default DB” which allows creating the main database.

The build process for 15.4 and 16.0 is identical and the I-SQL client tool is usable with both database

Versions. More Details about the Database Creation with SQL is described here:

http://help.sap.com/saphelp_iq1610_iqdb/helpdata/en/a6/fba0b184f2101591489266d5fd9f86/conten

t.htm?frameset=/en/a6/fb214f84f210159b9c8a125566c668/frameset.htm&current_toc=/en/a8/8bc8

c384f2101587988d375ed95c49/plain.htm&node_id=82&show_children=false

Note 1992512 - How to use Utility Database of SAP IQ

Log on with the user sybase and change to the sybase database directory


Start the utility_db as follows:

start_iq -n iq16_utility -gp 4096 -x "tcpip{PORT=2638}" -iqro 1 -gm 1 -iqlm

17066 -iqtc 17066 -iqmc 17066

Please note that the directory were you started the utility_db is the root, where all other files which are

created in the DB creation are related to. So please make sure, you start the temporary DB in the correct

directory /usr/sap/NLS/SAPIQ/database

Now that we started the default IQ database, we can use now the I-SQL Interface provided by the Sybase

Client to create the main database. This step can also be done via Sybase Control Center (SCC).

The default Port of the utility_db is 2638. If this port is occupied by other processes you can also

specify any other Port during the startup with the option -x tcpip{port=<yourport>}

This is now the first time to connect to the database via DBA/sql and the default Port 2638 to the

utility_db. The default logon to IQ is DBA/sql

http://help.sap.com/saphelp_iq1608_iqdb/helpdata/en/a6/fba0b184f2101591489266d5fd9f86/content.htm?frameset=/en/a6/fb214f84f210159b9c8a125566c668/frameset.htm&current_toc=/en/a8/8bc8c384f2101587988d375ed95c49/plain.htm&node_id=82&show_children=false






February 2016 45

dbisql -c "uid=dba;pwd=sql;eng=myserver;dbn=utility_db

In the I-SQL Interface paste the following SQL script for the creation of the main database.

The collation option CESU8BIN and encoding option CESU8 are only available in the latest 15.4 Patch

ESD#3 and 16.0 SAP IQ Version’s provided by SAP. The path can be created in an absolute or relative

relation. The file size specification might be necessary as well in the main database.

Assuming the utility_db is started in directory /usr/sap/NLS/SAPIQ/database

Default and Minimum Sizes of SAP IQ and Temporary Stores

http://help.sap.com/saphelp_iq1610_iqdb/helpdata/en/a7/00cb1184f21015a704f7a7c92c939e/conte

nt.htm

/* ------------------------------------------------------------*/

/* create_database.sql */

/* SAP IQ database instance "SAPIQDB" - CREATE DB */

/* V.20130320-01 */

/* ------------------------------------------------------------*/

CREATE DATABASE 'SAPIQDB.db'

LOG ON '../sapdata/log/SAPIQDB_log.log'

CASE RESPECT

PAGE SIZE 4096

COLLATION 'CESU8BIN' ENCODING 'CESU8'

BLANK PADDING ON;

JCONNECT ON

JAVA ON

IQ PATH '../sapdata/main/SAPIQDB_main_001.iq'

IQ SIZE 8192

IQ PAGE SIZE 524288

MESSAGE PATH '../sapdata/messages/SAPIQDB_msg.iqmsg'

TEMPORARY PATH '../sapdata/temp/SAPIQDB_tmp_001.iqtmp'

TEMPORARY SIZE 8192

http://help.sap.com/saphelp_iq1610_iqdb/helpdata/en/a7/00cb1184f21015a704f7a7c92c939e/content.htm

http://help.sap.com/saphelp_iq1610_iqdb/helpdata/en/a7/00cb1184f21015a704f7a7c92c939e/content.htm


February 2016 46

After the creation process is finished you can stop the utility_db and start the new created database

sybase@lt5006:/usr/sap/NLS/SAPIQ/database> stop_iq

2.1.11.2 The SAPIQDB configuration file

To start the IQ database you will need a configuration file. You can copy the following example and put the

file SAPIQDB.cfg to the database directory

http://help.sap.com/saphelp_iq1610_iqdb/helpdata/en/a2/91eeea84f21015ac39cef6d0ed26f0/conten

t.htm

#/* -----------------------------------------------------------*/

#/* @(#)SAPIQDB.cfg */

#/* SAP IQ database instance "SAPIQDB" - CONFIGURATION */

#/* -----------------------------------------------------------*/

### Name of the server

-n SAPIQSERVER

#### cache memory for catalog store. Set to 2 – 8 times size of the catalog file

-cl 1024m

-ch 4096m

-gc 20

-gd all

#### adjust according the existing memory we have 256GB HW.

#### Use 80% of existing RAM and reserve 1/3 for every parameter

-iqlm 68267

-iqtc 68267

-iqmc 68267

#### we have 16x4 core CPU hardware this forces on Intel to do more parallel

-iqnumbercpus 64

-iqpartition 16

#### network

-x tcpip{port=2640}

#### improving SQL anywhere interface for NLS queries

-gss 8m

-iqtss 2048

#### Number of connections in the IQ/SQL anywhere server/stack size/page size

-gn 150

-gm 100

-gp 4096

-ti 4400

#### timeout for debugging

-tl 600

#### we force clients to use large size as default

-p 64000

#### Displays diagnostic communication messages

-z

#### enable SAP IQ SSL support

# -ec TLS(IDENTITY=lt5006.id)

#### location of the temp dir for SQL anywhere

-dt /usr/sap/NLS/SAPIQ/sapdata/tmp

#### LOG DIAGNOSTIC

-o /usr/sap/NLS/SAPIQ/sapdata/log/SAPIQDB_DIAG.log

#### Name of log file

-zo /usr/sap/NLS/SAPIQ/sapdata/log/SAPIQDB_PROTOCOL.log

#### size of the log file

-zs 10m

#### Number of log files and size of iqmessagefile in mb

-zn 5

-iqmsgsz 100

-iqmsgnum 5

http://help.sap.com/saphelp_iq1610_iqdb/helpdata/en/a2/91eeea84f21015ac39cef6d0ed26f0/content.htm

http://help.sap.com/saphelp_iq1610_iqdb/helpdata/en/a2/91eeea84f21015ac39cef6d0ed26f0/content.htm


February 2016 47

It is suitable, to remove all comments/blanks/etc. from the file SAPIQDB.cfg to avoid unwanted and

irritating error messages.

To be compatible with the usage of the SAP Control Center (SCC) with the IQ database you will need to

link file SAPIQDB.cfg to the params.cfg in the same directory.

Now your database SAPIQDB is ready for the next steps like options and extending.

Additional Details on the sizing guidelines for SAP IQ 16.0 and Maintenance can be found here:


http://help.sap.com/saphelp_iq1610_iqdb/helpdata/en/a7/014adb84f21015b5a9e43ff9dad992/conte

nt.htm

2.1.11.3 start/stop the SAP IQ database

Please Note with IQ16 SP03 you have additionally to specify the IQTMP16 parameter.

Note 1927796 - IQ - Query failing with Error message : Temporary space limit exceeded

With a short script where you paste this line in a command you can ease the startup.

#/* -----------------------------------------------------------*/

# @(#)start_SAPIQDB

# start SAP IQ database instance "SAPIQDB"

#/* -----------------------------------------------------------*/

export IQTMP16=/usr/sap/NLS/SAPIQ/sapdata/tmp # set SA cat temp cache


sybase@lt5006:/usr/sap/NLS/SAPIQ/database> start_SAPIQDB

To stop the IQ database you can use the following script:

#/* -----------------------------------------------------------*/

# @(#)start_SAPIQDB

# start SAP IQ database instance "SAPNLS_DB"

#/* -----------------------------------------------------------*/

stop_iq -stop one

With a short script where you paste this line in a command you can stop now the IQ database exclusively,

e.g. you have more than one IQ database installed one physical server.

sybase@lt5006:/usr/sap/NLS/SAPIQ/database> stop_SAPIQDB

Additional Information about start_iq /stop_iq can be found here:

http://help.sap.com/saphelp_iq1610_iqicg_lin/helpdata/en/a6/8257b984f210159d74ad7d057bbc49/fr

ameset.htm


http://help.sap.com/saphelp_iq1610_iqdb/helpdata/en/a7/014adb84f21015b5a9e43ff9dad992/content.htm

http://help.sap.com/saphelp_iq1610_iqdb/helpdata/en/a7/014adb84f21015b5a9e43ff9dad992/content.htm



http://help.sap.com/saphelp_iq1608_iqicg_lin/helpdata/en/a6/8257b984f210159d74ad7d057bbc49/frameset.htm

http://help.sap.com/saphelp_iq1608_iqicg_lin/helpdata/en/a6/8257b984f210159d74ad7d057bbc49/frameset.htm


February 2016 48

2.1.11.4 The SAP Control Center (SCC)

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc01777.1601/doc/html/wil1352994883361.html

Starting with console prompt: $SYBASE/SCC-3_3/bin/scc.sh

SCC> shutdown

Starting in background: nohup $SYBASE/SCC-3_3/bin/scc.sh >& scc-console.out &

Stopping: $SYBASE/SCC-3_3/bin/scc.sh --stop

The default user accounts are sccadmin (SAP Control Center) and uafadmin/Sybase4me (IQ Agent).

Please make sure that you have created the following Link and restarted the SCC service for the correct usage of the SCC Agent.

ln -s /usr/bin/env /bin/env

Logon to the SAP Control Center (SCC) with sccadmin and <password>

http://server.domain.ext:8282/scc switches automatically to

https://server.domain.ext:8283/scc

https:// server.domain.ext:8283/help/index.jsp SCC online help



http://server.domain.ext:8282/scc

https://server.domain.ext:8283/scc

https://lt5006.wdf.sap.corp:8283/help/index.jsp


February 2016 49

Authenticate the IQ database first. Use DBA/sql as credentials (default)

Switch now to the Administration Console to Register and Authenticate the SCC IQ Agent.

Make sure you choose the correct port which is stated in the file SCC-3_3/bin/scc-console.out

Agent RMI Connection URL:

service:jmx:rmi:///jndi/rmi://lt5006:8284/agent

SAP Control Center successfully started

SCC Web Console:

http://lt5006:8282/scc

https://lt5006:8283/scc


February 2016 50

Authenticate the SCC Agent for your IQ server now

uafadmin/Sybase4me Now you can start monitoring and administer your IQ database.


February 2016 51


February 2016 52

2.1.11.5 The SAP IQ COCKPIT (successor of SCC)

http://help.sap.com/saphelp_iq1610_iqcpt/helpdata/en/14/170087751e10148a42872a40c620c2/frameset.htm

Note 2044940 - Initial password to be used for authentication of SAP IQ Cockpit agent (Sybase4me)

Note 2011352 - How to set Sybase IQ SCC passwords

Starting with console prompt: $SYBASE /COCKPIT-4/bin/cockpit.sh

COCKPIT> shutdown

Starting in background: nohup $SYBASE/COCKPIT-4/bin/cockpit.sh >& cockpit-console.out &

Stopping: $SYBASE/COCKPIT-4/bin/cockpit.sh --stop

The default user account is DBA/sql (different to the SAP Control Center).

https://lt5006.wdf.sap.corp:4283/cockpit/#

https://lt5006.wdf.sap.corp:4283/help/index.jsp

Please consult the SAP IQ COCKPIT Administration Guide for details:

http://help.sap.com/Download/Multimedia/zip-iq1610/iqcockpit.pdf

Executing the SAP IQ Cockpit Roles Script for a Role-Based System:

sybase@lt5006:/usr/sap/NLS/SAPIQ/server/COCKPIT-4/plugins/IQ-CMAP>

dbisql -c dsn=SAPIQDB -nogui cockpit_monitor_role_based_privileges_setup.sql





https://support.wdf.sap.corp/sap/support/notes/2011352

https://support.wdf.sap.corp/sap/support/notes/2011352

http://help.sap.com/Download/Multimedia/zip-iq1608/iqcockpit.pdf


February 2016 53

To create a DSN for your SAP IQ database, which can be used in several places run once the command

with the user sybase or sap<sid> and check the correct syntax.

sybase@lt5006:/usr/sap/NLS/SAPIQ/database> iqdsn -y -w "SAPIQDB" -c

"UID=DBA;PWD=sql;ServerName=SAPIQSERVER; LINKS=tcpip(host=lt5006;port=2638)"

sybase@lt5006:/usr/sap/NLS/SAPIQ/database> dbping -d -c dsn=SAPIQDB

This automatically creates the file .odbc.ini in the home directory of the sybase user which will be

used as well in the smart data access configuration.

To check the occupation of the chosen ports for the SAP IQ COCKPIT you can run the following command

sybase@lt5006:/usr/sap/NLS/SAPIQ/server/COCKPIT-4/bin> ./cockpit.sh -info

################################################################################

# Cockpit server Cockpit server 4.0 GA

# Copyright 2014 SAP AG. All rights reserved.

################################################################################

---------- SERVICE PORT CONFIGURATION ----------

Service Name Property Name Current Value In Use Address

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

RMI port 30594 true lt5006.wdf.

EmbeddedWebContainer http.port 30592 true ANY

EmbeddedWebContainer https.port 30593 true ANY

Tds tdsPort 30595 true ANY

SccSADataserver com.sybase.asa.server.port 4638 true ANY

Messaging messaging.db.port 4638 true ANY

Messaging messaging.port 4993 false ANY

Alert alert.database.port 4638 true ANY

sybase@lt5006:/usr/sap/NLS/SAPIQ/server/COCKPIT-4/bin>

To avoid errors in the following log files (not related to the core SAP IQ COCKPIT functionality)

/usr/sap/NLS/SAPIQ/server/COCKPIT-4/log/cockpit-console.out

/usr/sap/NLS/SAPIQ/server/COCKPIT-4/log/agent.log

In case of Problems, i.e. the Ports of the SccSADataserver and the Messaging Service are not

synchronized; you can run the following command to synchronize them:

./cockpit.sh –port db=xxxx

Furthermore all other related Ports for the SAP IQ COCKPIT can be changed/fixed at any time

stop_COCKPIT

./cockpit.sh -port db=34280,msg=34281,http=34282,https=34283,rmi=34284,tds=34285

start_COCKPIT


February 2016 54


February 2016 55

2.1.11.6 Create a technical user for the IQ COCKPIT

2.1.11.7 Pluggable Authentication Module (PAM) for UNIX

Configure SCC to use UNIX <username> and <password> login accounts.

If you are using SUSE version 11 and later, create a sybase-csi file in your /etc/pam.d directory that

contains:

# sybase-csi PAM Configuration (SUSE style)

auth include common-auth

account include common-account

password include common-password

session include common-session

For information about configuring additional platforms or versions, see




February 2016 56

2.1.11.8 Apply the DB Options for the SAP IQ database

Paste the following SQL script into the I-SQL Interface (without the “/*” lines) for the creation of the main

database. These Values are based on the current experiences with the SAP IQ database.

To activate these settings you have to restart the IQ database.

/* -------------------------------------------------------*/

/* @(#)options.sql */

/* SAP IQ database instance "SAPIQDB" - SET OPTIONS */

/* V.2013032.pro0-01 */

/* -------------------------------------------------------*/

-- only for IQ 15.x

-- set option public.minimize_storage='ON';

-- set option public.default_disk_striping='ON';

-- main settings for the SAP-NLS solution

set option public.allow_read_client_file='ON';

set option public.blocking='ON';

set option public.append_load='ON';

set option public.default_kb_per_stripe=128;

set option public.force_no_scroll_cursors='ON';

set option public.index_advisor='ON';

set option public.index_advisor_max_rows=10000;

set option public.main_reserved_dbspace_mb=12000;

set option public.max_cartesian_result=0;

set option public.os_file_cache_buffering='OFF';

set option public.os_file_cache_buffering_tempdb='OFF';

set option public.query_detail='ON';

set option public.query_plan='ON';

set option public.query_plan_after_run='ON';

set option public.query_plan_as_html_directory='../html';

set option public.query_temp_space_limit=0;

set option public.query_timing='ON';

set option public.string_rtruncation='OFF';

set option public.snapshot_versioning='row-level';

set option public.temp_reserved_dbspace_mb=12000;


February 2016 57

2.1.11.9 Extend the SAP IQ database (datafiles/temp)

Now the database has to be extended to use the optimum from the existing hardware resources like CPU

and RAM.

As a starting point we would normally split the data/tmp devices on a 50:50 basis. Over time we can add

more devices for data and may at some point arrive at a 60:40 ratio based on usage, content and query

profiles of our user base.

The general rule is then to subtract 100-Gb from the available (raw) device size and to then create

([#cores] * 2) additional devices all of an equal size to consume the remaining free disk space in the disk

array.

This results in the following (raw) disk definition. However, this also works with a standard file system.

Please Note that this step will take some time depending on the hardware resources.

/* -------------------------------------------------------*/

/* @(#)extend.sql */

/* SAP IQ database instance "SAPIQDB" - Extend DB */

/* V.20130320-01 */

/* -------------------------------------------------------*/

CREATE DBSPACE SAPIQDBSPACE001 USING

FILE SAPIQDBSPACE001_001 '../sapdata/SAPIQDBSPACE001_001.iq' size 12288,















FILE SAPIQDBSPACE001_016 '../sapdata/SAPIQDBSPACE001_016.iq' size 12288

STRIPING ON

STRIPESIZEKB 512;

ALTER DBSPACE IQ_SYSTEM_TEMP ADD

FILE SAPIQDB_tmp_002 '../temp/SAPIQDB_tmp_002.iqtmp' size 12288,















FILE SAPIQDB_tmp_017 '../temp/SAPIQDB_tmp_017.iqtmp' size 12288

;

set option public.default_dbspace='SAPIQDBSPACE001';


February 2016 58

2.1.11.10 Check the status of the SAP IQ database

After you logged on with the I-SQL interface you can run the following procedure to check the status of

the SAP IQ database and the usage of the correct license. Please Note, that some of the optional License

Options might not active, as long as there are not used so far (e.g. IQ_LOB)

The sp_iqstatus Stored Procedure

http://help.sap.com/saphelp_iq1610_iqdb/helpdata/en/a7/6dbe0784f21015898abccb108adfed/conte

nt.htm

sp_iqstatus;

sp_iqlmconfig;

sp_iqcheckoptions;

sp_iqcheckdb 'allocation database';

sp_iqcheckdb 'dropleaks database';

sp_iqdbspace;

sp_iqdbspaceobjectinfo

SAPIQDBSPACE001;

sp_iqfile SAPIQDBSPACE001;

The tmp files will be added to the existing main temp space, while data files are created additionally.

See also the different file extensions for the different file types.

http://help.sap.com/saphelp_iq1610_iqintro/helpdata/en/a4/43ff3884f21015a8a2d49481839a6c/cont

ent.htm?frameset=/en/a8/8f131584f21015a82dd9c1d6f28058/frameset.htm&current_toc=/en/a8/8f1

31584f21015a82dd9c1d6f28058/plain.htm&node_id=19

Additional useful System Stored Procedures for IQ16 can be found here:


Note 1843189 - SAP IQ Troubleshooting and diagnostics collection checklist

check this Note for more Information.

http://help.sap.com/saphelp_iq1610_iqdb/helpdata/en/a7/6dbe0784f21015898abccb108adfed/content.htm

http://help.sap.com/saphelp_iq1610_iqdb/helpdata/en/a7/6dbe0784f21015898abccb108adfed/content.htm







February 2016 59

2.2 Install the SAP components for SAP IQ

2.2.1 Add the ODBC IQ driver to the SAP Instance Note 2205476 - SAP IQ ODBC NLS drivers missing from SAP Support Portal

Go to - https://support.sap.com/software/patches.html

Create the Directory siqclient according to the existing hdbclient Directory and run the command

with the <sid>adm of your SAP BW system.

lt5006:/usr/sap/HBW/siqclient> SAPCAR -xvf

/data/software/sybase/IQCLIENT16010P_1-10013028.SAR

SAPCAR: processing archive /data/software/sybase/IQCLIENT16010P_1-10013028.SAR

(version 2.01)

x ebf24908

x ebf24908/dblgen16.res

x ebf24908/dblgen_iq16.res

x ebf24908/dblgja16_eucjis.res

x ebf24908/dblgja16_sjis.res

x ebf24908/dblgja16_utf8.res

x ebf24908/dblgja_iq16_eucjis.res

x ebf24908/dblgja_iq16_sjis.res

x ebf24908/dblgja_iq16_utf8.res

x ebf24908/dblgzh16_cp936.res

x ebf24908/dblgzh16_eucgb.res

x ebf24908/dblgzh16_utf8.res

x ebf24908/dblgzh_iq16_cp936.res

x ebf24908/dblgzh_iq16_eucgb.res

x ebf24908/dblgzh_iq16_utf8.res

x ebf24908/ident.txt

x ebf24908/libdbicu16.so

x ebf24908/libdbicu16_r.so

x ebf24908/libdbicudt16.so

x ebf24908/libdbodbc16.so

x ebf24908/libdbodbc16_n.so

x ebf24908/libdbodbc16_r.so

x ebf24908/libdbodbcansi16_r.so

x ebf24908/libdbodbcinst16_r.so

x ebf24908/libdbodm16.so

x ebf24908/libdbrsa16.so

x ebf24908/libdbrsa16_r.so

x ebf24908/libdbrsakp16_r.so

x ebf24908/libdbtasks16.so

x ebf24908/libdbtasks16_r.so


lt5006:/usr/sap/HBW/siqclient>


https://support.sap.com/software/patches.html


February 2016 60

2.2.2 Add the IQ LibDBSL to the SAP Kernel lt5006:/usr/sap/HBW/siqclient/ebf24908> SAPCAR -xvf

/data/software/sybase/lib_dbsl_310-20012226.sar

SAPCAR: processing archive /data/software/sybase/lib_dbsl_310-20012226.sar

(version 2.01)

x dbsybslib.so

x patchesdb.mf

x SIGNATURE.SMF


lt5006:/usr/sap/HBW/siqclient/ebf24908>

As the SAP IQ ODBC files create an additional ebfxxxxx Directory, make sure you specify the correct

Directory later on.

Add the following entries to the SAP BW instance Profile and restart the SAP BW system

SETENV_01 = :$(DIR_EXECUTABLE)$(DIR_SEP)siqclient/ebf24908




Before you do so, create the following logical links in the ODBC Directory to stay compatible with the old

SAP IQ ODBC drivers and the LibDBSL for SAP ASE/IQ.

lt5006:/usr/sap/HBW/siqclient/ebf24908>

ln -s libdbodbc16.so libdbodbc12.so

ln -s libdbodbc.so libdbodbc12.so

2.2.3 Configure unixODBC To understand the basic functionality visit the unixODBC Page at - http://www.unixodbc.org

Optionally, install the UNIX based ODBC tools as follows with the user root:

sybase@lt5006: /data/software/sybase> zypper install unixODBC

Or call the X-Windows tool yast2

You can check the Installation as follows:

lt5006:~ # odbcinst –j

unixODBC 2.2.12

DRIVERS............: /etc/unixODBC/odbcinst.ini

SYSTEM DATA SOURCES: /etc/unixODBC/odbc.ini

USER DATA SOURCES..: /root/.odbc.ini

lt5006:~ # ln -s /etc/unixODBC/odbc.ini /usr/sap/<SID>/home/.odbc.ini

Create an empty .odbc.ini file in the home directory of the <sid>adm of the HANA user and on the

sybase home directory of the user sybase with the following structure:

http://www.unixodbc.org/


February 2016 61

Please Note the necessary specific Parameters for SAP IQ (CommLinks) and SAP HANA (ServerNode)

cannot be added automatically to the file .odbc.ini

[SAPIQDB]

Driver=/usr/sap/<SID>/SAPIQ/server/IQ-16_0/lib64/libdbodbc16_r.so

ServerName=SAPIQSERVER

CommLinks=tcpip(host=lt5006.wdf.sap.corp;port=2640)

[<SID>HANA]

Driver=/usr/sap/<SID>/SYS/exe/uc/linuxx86_64/hdbclient/libodbcHDB.so

ServerNode=lt5006.wdf.sap.corp:3<nr>15

User=SYSTEM

Password=<secure>

On the SAP IQ host/location you can create the entry for the .odbc.ini automatically with the following

command and test the connection:

siqadm@lt5006:/usr/sap/SIQ/siqdata/db>

iqdsn -y -w "SAPIQDB" -c "UID=DBA;PWD=sql;ServerName=SAPIQSERVER;DBN=SAPIQDB;

Host='lt5006.wdf.sap.corp:2640'"

siqadm@lt5006:/usr/sap/SIQ/siqdata/db> dbping -d -c dsn=SAPIQDB

After these manual settings, you have to restart the HANA and the IQ server to make the changes active.

2.3 Configure Smart Data Access - SAP HANA and IQ


February 2016 62

Note 1868209 - SAP HANA Smart Data Access: Central Note

Note 1868702 - SAP HANA Smart Data Access: Remote DataSource Drivers

(smart data access driver install PDF attached)

Note 2165650 - BW Near-Line Storage with HANA Smart Data Access: FAQ

Note 1879294 - SAP HANA smart data access SP 1



Note 2157818 - SDA SAR file (use from HANA 1.0 Rev. 95 and onwards)

You can find the Detailed Description for the Smart Data Access

http://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdf

(SPS6 Document Version: 1.1 - 17-07-2013) - Chapter 16.3 - About SAP HANA Smart Data Access

Unpack the file IMDB_SDA100_03_5-20011324.SAR or higher into a temporary directory and run the

setup to install the ODBC drivers for HANA.

Please note that the Directory /usr/sap/<SID>/federation will be created now automatically.

Also a logical link federation from the Directory /usr/sap/HBW/SYS/global/hdb will be created.

sybase@lt5006:/data/software/temp>

SAPCAR -xvf _sar\IMDB_SDA100_03_5-20011324.SAR

SAPCAR: processing archive IMDB_SDA100_03_5-20011324.SAR (version 2.01)

sybase@lt5006:/data/software/temp>./install.sh -s <SID>

Copy the SAP IQ Network Client to a Directory which you can add as LD_LIBRARY_PATH to the

environment of the HANA user. See Chapter 2.4.3 for the Details.

For Example: use the already existing Directory /usr/sap/<SID>/federation

Update the environment for the HANA <sid>adm in the .customer.sh profile, so that the two

environment variables are set as shown. If the file .customer.sh does not exist, create this with

attributes 775.













http://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdf


February 2016 63

Order of calling the user environment:

.profile => .bashrc => .sapenv.sh and .customer.sh

export ODBC_IQ=libdbodbc16_r.so

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/sap/HDB/federation

Create a “New Remote Source” under the Section Provisioning and fill in the necessary settings


February 2016 64

This Source Name becomes now the Value of the Parameter REMOTE_SOURCE in the transaction

RSDANLCON

Create a virtual Table based on an existing Table located in the IQ Server.


February 2016 65

The Table is now visible in the SAP<SID> Schema of the BW on HANA System

Grant Remote Source privileges to SAP<SID> user

In SQL: GRANT CREATE VIRTUAL TABLE, DROP ON REMOTE SOURCE "I42_RK" TO "SAP<SID";


February 2016 66

Additional SAP Notes to consider:

Note 1989436 - Open ODS View with Smart Data Access - Invalid Table Name during Query Execution

Note 2100225 - BW Near-Line Storage with HANA SDA: Improved Handling of NLS Part Providers

Note 2100962 - BW Near-Line Storage with HANA Smart Data Access: Query Performance

Additional Notes with regards to BW query execution:

2063449 - Push down of BW OLAP functionalities to SAP HANA

https://blogs.saphana.com/2013/06/10/bw-on-hana-and-the-query-execution-mode/

See also the SCN article - http://scn.sap.com/docs/DOC-58084

The smart data access can also be enabled via the HANA LM option through the HANA studio.

SAP First Guidance - Business Warehouse on SAP HANA Installation

2.3.1 The SDA ODBC Extra Adapter Properties The string will be created automatically via the SAP HANA Studio interface. However it is suitable to refer

to the settings within this Document.

EngineName=lt5006_I42_42;DatabaseName=SAPIQDB;

CommLinks=tcpip(host=lt5006.wdf.sap.corp;port=34238);

2.4 Configure SAP IQ SSL support

2.4.1 Pre requisites

For the overall process you can follow the following help section how exemplarily describes SSL

configuration for the SAP Host Agent on UNIX. Even that at this time the SAP IQ description uses the

“Sybase native tools”, the Implementation is done with the SAP standard SSL package via SAPCryptoLib.

The procedure using the Sybase tools is described here:

Note 2117279 - SAP IQ: How to generate CSR for third party trusted CA (VeriSign)

SSL Scenario 1: Establishing Trust for Server-Side Authentication

http://help.sap.com/saphelp_nw74/helpdata/en/e2/03bd09d183488fa17da55ddb648f11/content.htm

?frameset=/en/7d/68d35fa2bb47168ae2603919232955/frameset.htm&current_toc=/en/cd/a393784

9b043509786c5b42171e5d3/plain.htm&node_id=5

Configuring SSL for SAP Host Agent on UNIX

http://help.sap.com/saphelp_nw74/helpdata/en/8d/12f7b9244b44219bd14d619d3a2123/content.htm

?frameset=/en/f9/50aeeb64604e818b24626d287b63b0/frameset.htm&current_toc=/en/21/98c4431

22744efae67c0352033691d/plain.htm&node_id=19





https://blogs.saphana.com/2013/06/10/bw-on-hana-and-the-query-execution-mode/


https://scn.sap.com/docs/DOC-41588


http://help.sap.com/saphelp_nw74/helpdata/en/e2/03bd09d183488fa17da55ddb648f11/content.htm?frameset=/en/7d/68d35fa2bb47168ae2603919232955/frameset.htm&current_toc=/en/cd/a3937849b043509786c5b42171e5d3/plain.htm&node_id=5



http://help.sap.com/saphelp_nw74/helpdata/en/8d/12f7b9244b44219bd14d619d3a2123/content.htm?frameset=/en/f9/50aeeb64604e818b24626d287b63b0/frameset.htm&current_toc=/en/21/98c443122744efae67c0352033691d/plain.htm&node_id=19




February 2016 67

Setting the Profile Parameters for Using SSL

http://help.sap.com/saphelp_nw74/helpdata/en/49/23691cbf5a1902e10000000a42189c/content.htm

Exporting a PKCS#12 File

http://help.sap.com/saphelp_nw74/helpdata/en/3d/5d3ffd5ae248ffa15f7bf9ee659f41/content.htm

Recommended Locations of Files

http://help.sap.com/saphelp_nw74/helpdata/en/18/68373b612a6448e10000000a11402f/content.ht

m?frameset=/en/3d/5d3ffd5ae248ffa15f7bf9ee659f41/frameset.htm&current_toc=/en/cd/a3937849

b043509786c5b42171e5d3/plain.htm&node_id=104

The SAP Cryptographic Library Installation Package Installation

http://help.sap.com/saphelp_nw74/helpdata/en/d3/62453cc7f35d0ee10000000a11405a/content.ht

m?frameset=/en/1b/002ed33dfd4391bd9f1ca1dab17810/frameset.htm&current_toc=/en/cd/a393784

9b043509786c5b42171e5d3/plain.htm&node_id=189

Note 1848999 - Central Note for CommonCryptoLib 8 (replacing SAPCRYPTOLIB)

Note 510007 - Setting up SSL on Application Server ABAP

Installing SAP Host Agent Manually

http://help.sap.com/saphelp_nw74/helpdata/en/8b/92b1cf6d5f4a7eac40700295ea687f/content.htm

?frameset=/en/8d/12f7b9244b44219bd14d619d3a2123/frameset.htm&current_toc=/en/21/98c44312

2744efae67c0352033691d/plain.htm&node_id=7

http://help.sap.com/saphelp_nw74/helpdata/en/49/23691cbf5a1902e10000000a42189c/content.htm

http://help.sap.com/saphelp_nw74/helpdata/en/3d/5d3ffd5ae248ffa15f7bf9ee659f41/content.htm

http://help.sap.com/saphelp_nw74/helpdata/en/18/68373b612a6448e10000000a11402f/content.htm?frameset=/en/3d/5d3ffd5ae248ffa15f7bf9ee659f41/frameset.htm&current_toc=/en/cd/a3937849b043509786c5b42171e5d3/plain.htm&node_id=104



http://help.sap.com/saphelp_nw74/helpdata/en/d3/62453cc7f35d0ee10000000a11405a/content.htm?frameset=/en/1b/002ed33dfd4391bd9f1ca1dab17810/frameset.htm&current_toc=/en/cd/a3937849b043509786c5b42171e5d3/plain.htm&node_id=189




http://help.sap.com/saphelp_nw74/helpdata/en/8b/92b1cf6d5f4a7eac40700295ea687f/content.htm?frameset=/en/8d/12f7b9244b44219bd14d619d3a2123/frameset.htm&current_toc=/en/21/98c443122744efae67c0352033691d/plain.htm&node_id=7




February 2016 68

2.4.2 SSL Configuration

In the following example the following assumption where made:

Use your own Password Phase which contains upper/lowercase, numeric and non-alpha characters. The

password option with sapgenpse is specified with the parameter -x

As the SAPHostAgent Installation is part of every SAP Installation we are using the user sapadm which is

called via root: sudo -u sapadm

If the Path Variables LD_LIBRARY_PATH and SECUDIR are already defined, you don´t have to call these

option additionally.

The SAP Notation for the Server PSE is SAPSSLS.pse

All files are created in the directory /usr/sap/hostctrl/exe/sec/ which is created beforehand.

Create the Server PSE

sudo -u sapadm LD_LIBRARY_PATH=/usr/sap/hostctrl/exe SECUDIR=/usr/sap/hostctrl/exe/sec

/usr/sap/hostctrl/exe/sapgenpse gen_pse -p SAPSSLS.pse -x Sybase#123 -r

/usr/sap/hostctrl/exe/sec/lt5006-csr.p10 "CN=lt5006.wdf.sap.corp, O=SAP AG, C=DE"

Grant SAP Host Agent access to the server PSE


/usr/sap/hostctrl/exe/sapgenpse seclogin -p SAPSSLS.pse -x Sybase#123 -O sapadm

Get the certificate as follows:

Send the certificate signing request to an appropriate CA.

Assuming that the CA replies to the request file with a CA-response-file which contains the signed

certificate in the PKCS#7 format, you can use this file as an input for importing the signed

certificate into the server PSE. If the used format is PKCS#7, the text file could be named

myhost.p7b

Import the signed certificate into the server PSE


/usr/sap/hostctrl/exe/sapgenpse import_own_cert -p SAPSSLS.pse -x Sybase#123 -c

/usr/sap/hostctrl/exe/sec/lt5006.p7b

Verify the server certificate chain


/usr/sap/hostctrl/exe/sapgenpse get_my_name -p SAPSSLS.pse -x Sybase#123 -v

Exporting the PKCS#12 file


/usr/sap/hostctrl/exe/sapgenpse export_p12 -p SAPSSLS.pse -x Sybase#123 -z Sybase#123 -v

lt5006.p12

Create the id file out of the PKCS#12 file with OpenSSL

sudo -u sapadm openssl pkcs12 -in lt5006.p12 -out lt5006.id -nodes

http://help.sap.com/saphelp_nw74/helpdata/en/49/3d9c9619341067e10000000a42189c/content.htm?frameset=/en/49/2371abbf5a1902e10000000a42189c/frameset.htm&current_toc=/en/cd/a3937849b043509786c5b42171e5d3/plain.htm&node_id=15


February 2016 69

Create the pem file out of the PKS#7 file with OpenSSL

sudo -u sapadm openssl pkcs7 -in lt5006.p7b -print_certs -out lt5006.pem

Create the crt file from the pem file

sudo -u sapadm cp lt5006.pem CIANLS.crt

List of created files during the procedure

lt5006:/usr/sap/hostctrl/exe/sec # dir

total 64

-rw-r--r-- 1 sapadm sapsys 6868 May 12 19:15 CIANLS.crt

-rw------- 1 sapadm sapsys 5191 May 12 18:06 SAPSSLS.pse

-rw-r--r-- 1 sapadm sapsys 106 May 12 17:56 cred_v2

-rw-r--r-- 1 sapadm sapsys 944 May 12 17:56 lt5006-csr.p10

-rw-r--r-- 1 sapadm sapsys 8776 May 12 18:49 lt5006.id

-rw-r--r-- 1 sapadm sapsys 1777 May 12 18:54 lt5006.key

-rw------- 1 sapadm sapsys 6408 May 12 18:47 lt5006.p12

-rw-r--r-- 1 sapadm sapsys 6495 May 12 18:06 lt5006.p7b

-rw-r--r-- 1 sapadm sapsys 6868 May 12 19:06 lt5006.pem

2.4.3 Follow up activities

Enhance the DBCON connection string with the following parameter SYBASE_SSL=1

See Chapter 3.2.2 for details.

Note 1999431 - SIQ: Setting up SSL for connections to IQ

Add the following Parameter to the SAP IQ startup configuration file and restart the SAP IQ database.

-ec TLS(TLS_TYPE=RSA;FIPS=Y;IDENTITY=lt5006.id) See Chapter 2.1.7.2 for details.

Update the SAP IQ ODBC driver and the LibDBSL to the latest Version

Note 2127203 - SAPSybaseIQ-NC 16.0 SP08 PL24 Release Notes Information

Note 2130587 - SYB IQ: Performance enhancement for LOAD statement

See Chapter 2.2.1 and Chapter 2.2.2 for details.

If you still have fragments from the old SAP IQ ODBC drivers in your Instance Executable directory, please

remove them before calling the SSL enabled connection once it is correctly configured.






February 2016 70

The location of the SAP IQ ODBC driver has changed. The necessary files are delivered with the SAP IQ

Network Client 16.0 at this time.

Check now the SSL enabled connection first for the enhanced DBCON with the following ABAP Program

ADBC_TEST_CONNECTION. See Chapter 3.2.2 for details.

Finally call the Transaction RSDANLCON you create the connection to the NLS storage on top of the DB

connection. See Chapter 3.2.3 for details.

Copy the file CIANLS.crt to the global Instance directory D:\usr\sap\HBW\SYS\global\

To enable the SSL support between SAP IQ and HANA based on SDA via ODBC drivers, enhance the

connection string in the SAP HANA Studio with the following parameter string:

Encryption=TLS(trusted_certificates=/usr/sap/hostctrl/exe/sec/CIANLS.crt)

See Chapter 2.3.1 for details.

Correct SDA SSL connection to SAP IQ


February 2016 71

3. Configuration of the SAP Components

Overall Documentation:

http://help.sap.com/saphelp_nw74/helpdata/en/e8/395401e46f4edca50aefeead7f3a44/frameset.htm

3.1 SAP IQ related

3.1.1 Create/configure SAP<SID>IQDB user You can use the SAP IQ COCKPIT to create the SAP-NLS user for nearline connection from SAP BW to

SAP IQ.

http://help.sap.com/saphelp_nw74/helpdata/en/e8/395401e46f4edca50aefeead7f3a44/frameset.htm


February 2016 72

Alternative you can create the user as well with the following script (grants must defined separately per

single line):

/* -----------------------------------------------------------*/

/* @(#)user.sql

/* SAP IQ database instance "SAP<SID>IQDB" - create USER

/* V.20130320-01

/* the Role RESOURCE is not available anymore in SP08

/* -----------------------------------------------------------*/

create user SAP<SID>IQDB identified by '**********';

grant READCLIENTFILE, MONITOR, MANAGE any EVENT to SAP<SID>IQDB;

grant ROLE SYS_AUTH_RESOURCE_ROLE to SAP<SID>IQDB with no ADMIN OPTION;

grant CREATE TABLE to SAP<SID>IQDB with no ADMIN OPTION;


February 2016 73

3.2 SAP BW related

3.2.1 Apply the latest corrections for the SAP-NLS Solution.

Therefore go to the Note search http://service.sap.com/notes and use the Keywords like

SAPKW74014 or SAPK-75003INSAPBW together with the component BW-WHM-DST-ARC

Use the Transaction SNOTE to upload several Notes at once and apply the corrections

Always use SP04 or higher for IQ 16.0, otherwise you have to import the following SAP Notes:

Note 1966432 - Event-based Backup Automation does not work anymore with IQ 16.0 SP 3

Note 1796393 - SAP BW near-line solution with SAP IQ

Note 1971524 - BW auf HANA: SQL Fehler 464 bei Archivierung eines IMOCubes (II)

Note 2023695 - SAP IQ NLS: Data corruption after upgrading from SAP IQ 16 sp01 to sp03

http://service.sap.com/notes












February 2016 74

3.2.2 Transaction DBCO - database connection to SAP IQ

Note 1737415 - SAP IQ: Enable remote/secondary connect to SAP IQ


Now that the LibDBSL for IQ is available in the SAP executables directory, it is now possible to create a DB

connection with the Transaction DBCO. Use the following parameter for the connection:

Connection info: SYBASE_SERVER=<server>.<domain>.<ext>

SYBASE_PORT=<port> e.g. 2640

SYBASE_IQ_ENGINE=SAPIQSERVER

SYBASE_DBNAME=SAPIQDB

SYBASE_CONTYPE=IQ

SYBASE_IQ_LOAD=1

SYBASE_IQ_CESU-8=1

SYBASE_IQ_LOCKWAIT=600

SYBASE_IQ_BUFFER_SIZE=500000

The general format of the connection info is: key_1=<value_1> key_2=<value_2> ....

key_n=<value_n> the key value pairs are separated by a space character.

SYBASE_SERVER, SYBASE_PORT, SYBASE_IQ_ENGINE, SYBASE_DBNAME, SYBASE_CONTYPE are

mandatory keys.

SYBASE_IQ_LOAD, SYBASE_IQ_LOCKWAIT, SYBASE_IQ_BUFFER_SIZE are optional.

Furthermore you can test the connection with the following ABAP Program ADBC_TEST_CONNECTION

A detailed test is done as well with the creation of the connection of the NLS storage.




February 2016 75

3.2.3 Transaction RSDANLCON - connection to NLS storage

With the Transaction RSDANLCON you create the connection to the NLS storage on top of the DB

connection.

Connection info: Name of the class: CL_RSDA_SYB_CONNECTION

Destination: N/A

Conn. Parameter: DBCON=SAPIQDB

Note 1876142 - BW NLS IQ: SQL error 0 in DB connection...

3.2.3.1 Increasing the Performance for the SAP-NLS load

Note 2109015 - Continuation of Archiving Requests for Copy, Verification, and Deletion Phase in parallel

Note 2128579 - Data Load into SAP IQ during Copy Phase utilizes only one server-side Thread


With these two SAP Notes two additional parameters are introduced to significantly increase the LOAD

statement for writing data into SAP-NLS.

Parameter LOAD_STRIPE_SIZE setting this parameter to a value n > 1 parallelizes the load.

Parameter LOAD_STRIPE_WITH is the parallel degree multiplied with SYBASE_IQ_BUFFER_SIZE






February 2016 76

Parameter SYBASE_IQ_LOAD_DIR could be changed at the database connection level (DBCO) and is by

default the data directory of the SAP Instance. If you plan to load a large amount of data, please make

sure that you have enough space left, or specify another directory/device.

LOAD_STRIPE_SIZE=4; LOAD_STRIPE_WIDTH=4

3.2.4 SAP-NLS Backup Solution

If you have the IQ Backup Solution in place you must enhance the Connection Parameter String with

BACKUP_REQUEST_EVENT=BACKUP_REQUEST

Note 1900379 - Improved Backup Automation with IQ NLS

Data Relocation to NLS takes place in (essentially) 3 phases: Copy Phase:

All data of a request is copied in individually committed packages to IQ

After commit of last package value of column commit_txn_id in view sysiqinfo is retrieved

An event to trigger backup is raised

Verification Phase:

Technical key of archived records is retrieved and verified for completeness

Deletion Phase:

Before data is deleted from primary database, most recent (i.e. maximum) backup id bu_id from

view sysiqbackuphistory is retrieved.

Deletion proceeds only if this bu_id is greater than commit_txn_id from copy phase.

Data is deleted from primary database

NLS Connection Parameter for IQ Back Up Handling

Connection Parameter ‘Backup_Request_Event =‘ allows to switch to BackUp mode




February 2016 77

3.2.5 Monitor the SAP-NLS Connection

3.2.5.1 RSDA_SYB_PARTITION_MONITOR

With the Report RSDA_SYB_PARTITION_MONITOR you can monitor the NLS connection at this time.

Double-click on the row you want to analyze


February 2016 78

For Monitoring Details you can also check the Log from the used Background Process via SM50

3.2.5.2 Setup SAP IQ for transaction DBACOCKPIT

Please consult the SAP IQ Operations Guide:

https://service.sap.com/~sapidb/011000358700000243172014E/GUIDE_DBA_SAP_IQ_7_40_SP8.PDF

In addition to the SAP Note 1737415 - SAP IQ: Enable remote/secondary connect to SAP IQ

You have to add the following parameter to the Instance Profile:

dbs/dba/ccms_maintenance = 1

dbs/dba/ccms_security_level = 0

And make sure that the ABAP administration user has at least the following SAP Role added:

SAP_BC_S_DBCON_ADMIN

For the necessary SAP IQ DB options please refer to the Chapter 2.1.7.6 of this Guide.

Before you run the following scripts check the following used sql scripts for their correctness:

/usr/sap/NLS/SAPIQ/server/IQ-16_0/DBACOCKPIT/scripts

create_queryplan_table.sql (might necessary to run this via I-SQL client)

set_queryplan_options.sql (insert the correct html location)

install_java_classes.sql (correct the location of the used java classes)





February 2016 79

Run the Procedure as stated in the SAP IQ Operations Guide Chapter 3.9.2:

script.sh DBN port user password

/usr/sap/NLS/SAPIQ/server/IQ-16_0/DBACOCKPIT/queryPlanUDF/bin/unix>

./install_queryplan_udf.sh SAPIQSERVER 2640 DBA sql

./load_queryplans_content.sh SAPIQSERVER 2640 DBA sql

Set query plan database options ...

Load query plan html content into the DBO.queryPlansTable ...

Load query plan html content successfully...

Add the following string to the table DBA_CONFIG with Transaction SE16

* * BI_SAP_NLS_ACTIVE X

3.2.5.3 Adding SAP IQ to the DBACOCKPIT transaction

Apply the following Note to enable the Data Volume Distribution within the DBACOCKPIT

Note 2021851 - Resolve run time error for Data Volume Distribution

Note 2047469 - SYB: Managed System Configuration running into ASE Error SQL4939

Note 1956005 - SYB: DBA Cockpit Release Notes 7.02 SP16, 7.30 SP12, 7.31 SP13, 7.40 SP8

Note 1882376 - SYB: DBA Cockpit Correction Collection SAP Basis 7.40

Note 2043277 - DBA: Allow transfer ownership also for non-SAP Solution Manager Systems

After you created the database connection to the NLS storage with transaction RSDANLCON, you can

also use this configuration to add the remote IQ database to the local DBACOCKPIT in your BW system.

Please Note that you have to create the connection to the SAP-NLS IQ within the DBACOCKPIT.









February 2016 80

The TabStrip “Performance” opens the standard database Cockpit.


February 2016 81

Under the TabStrip “Diagnostics” you can find the following additional Dashboards:

Unexpectedly Long Loads or Queries

http://help.sap.com/saphelp_iq1610_iqdb/helpdata/en/a7/6a03c384f21015aa07b1831ba75536/content.htm




February 2016 82

4. Using the SAP-NLS Solution

Now that the solution is installed and configured, you can go to the Administrator Workbench and start to

distribute your data to the IQ based storage.

For Details on How to Create Data Archiving Requests consult the SAP help portal

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4c/75184b167821d1e10000000a42189c/conten

t.htm?frameset=/en/4c/75184b167821d1e10000000a42189c/frameset.htm

Blog: Increasing the SAP-NLS Performance

http://scn.sap.com/community/bw-hana/blog/2015/11/17/increasing-the-sap-nls-performance

The Overview of the SAP-NLS Solution on the SCN - http://scn.sap.com/docs/DOC-54468

See the new released How-To Paper:

How to Archive Data from SAP NetWeaver BW to SAP IQ as Near line Storage

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4c/75184b167821d1e10000000a42189c/content.htm?frameset=/en/4c/75184b167821d1e10000000a42189c/frameset.htm

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4c/75184b167821d1e10000000a42189c/content.htm?frameset=/en/4c/75184b167821d1e10000000a42189c/frameset.htm

http://scn.sap.com/community/bw-hana/blog/2015/11/17/increasing-the-sap-nls-performance




February 2016 83

5. Appendix

5.1 Tipp’s for the IQ Administration

Best Practice SAP IQ Software Installation

SAP IQ comes with an installer for the platform chosen. It can be run in GUI or console mode and has both

a "typical installation" shortcut and options for a customized installation. For embedded installations, it

can be run in batch mode.

On Windows, install the SAP IQ server software as administrator user.

On UNIX, install the SAP IQ server software as user sybnls.

5.2 Common Maintenance Tasks for SAP IQ

5.2.1 Aliases for the .profile of SAP IQ user

These are useful settings for the file .profile in the home directory of the SAP IQ user.

Adapt the setting to your own environment.

export IQLANG=EN

source /usr/sap/SIQ/siqserver/IQ.sh

export

LD_LIBRARY_PATH=/usr/sap/HBT/SYS/exe/uc/linuxx86_64/hdbclient:$LD_LIBRARY_PATH

export PATH=/usr/sap/SIQ/siqserver/shared/SAPJRE-7_1_015_64BIT/bin:$PATH

export IQTMP16=/usr/sap/SIQ/siqdata/temp

alias start_SIQ='start_iq @/usr/sap/SIQ/siqdata/db/SAPIQDB.cfg

/usr/sap/SIQ/siqdata/db/SAPIQDB.db'

alias stop_SIQ='stop_iq -stop one'

alias start_SCC='nohup $SYBASE/SCC-3_3/bin/scc.sh >& scc-console.out &'

alias start_COCKPIT='nohup $SYBASE/COCKPIT-4/bin/cockpit.sh >& cockpit-

console.out &'

alias stop_SCC='$SYBASE/SCC-3_3/bin/scc.sh --stop'

alias stop_COCKPIT='$SYBASE/COCKPIT-4/bin/cockpit.sh --stop'

alias cddb='cd /usr/sap/SIQ/siqdata/db'

alias cdsw='cd /usr/sap/SIQ/siqserver'

alias dsn='dbping -d -c dsn=SAPIQDB'

cd /usr/sap/SIQ/siqdata/db


February 2016 84

5.2.2 Increasing the Size of dbspace

At the command line:

To increase the size of IQ_SYSTEM_MAIN dbspace:

alter dbspace IQ_SYSTEM_MAIN add file <logical-file-name-1> ‘<file-path-1>’ size

1GB, file <logical-file-name-2> '<file-path-2>' size 1 GB

To increase the size of IQ_SYSTEM_TEMP dbspace:

alter dbspace IQ_SYSTEM_temp add file <logical-file-name-1> '<file-path-1>' size

1 GB

To increase the size of RLV dbspace:

alter dbspace <rlv-dbspace-name> add file <logical-file-name-1> '<file-path-1>'

size 1GB, file <logical-file-name-2> '<file-path-2>' size 1 GB

To increase the size of user dbspace:

alter dbspace <user-dbspace-name> add file <logical-file-name-1> '<file-path-1>

size 1GB, file <logical-file-name-2> '<file-path-2>' size 1 GB

With SCC – use the online instructions provided here: SAP IQ 16.0 > Sybase Control Center 3.2.7 for SAP IQ> Administer and Monitor SAP IQ > DB Files http://help.sap.com/saphelp_iq1610_iqdb/helpdata/en/a6/f4ac2084f21015b4ff9f435c786314/content.htm?frameset=/en/a8/8bc8c384f2101587988d375ed95c49/frameset.htm&current_toc=/en/a8/8bc8c384f2101587988d375ed95c49/plain.htm&node_id=105&show_children=false

5.2.3 Modifying Cache Sizes or Startup Parameters To modify the cache sizes or startup parameters: Stop IQ server. Modify the SAPIQDB.cfg configuration file (located in /usr/sap/NLS/SAPIQ/database/). Restart IQ server.

http://help.sap.com/saphelp_iq1608_iqdb/helpdata/en/a6/f4ac2084f21015b4ff9f435c786314/content.htm?frameset=/en/a8/8bc8c384f2101587988d375ed95c49/frameset.htm&current_toc=/en/a8/8bc8c384f2101587988d375ed95c49/plain.htm&node_id=105&show_children=false




February 2016 85

5.2.4 Backup/Restore of an SAP IQ database

Online Documentation

http://help.sap.com/saphelp_iq1610_iqbackup/helpdata/en/a8/8c434084f21015b2aadf2ab640b09b/f

rameset.htm

BACKUP DATABASE Statement

http://help.sap.com/saphelp_iq1610_iqbackup/helpdata/en/a6/13fdea84f21015aaa499e4bc801d20/c

ontent.htm?frameset=/en/a6/236d0484f2101591fabb9064294f1d/frameset.htm&current_toc=/en/a8

/8c434084f21015b2aadf2ab640b09b/plain.htm&node_id=63

RESTORE DATABASE Statement

http://help.sap.com/saphelp_iq1610_iqbackup/helpdata/en/a6/236d0484f2101591fabb9064294f1d/c

ontent.htm?frameset=/en/a6/13fdea84f21015aaa499e4bc801d20/frameset.htm&current_toc=/en/a8

/8c434084f21015b2aadf2ab640b09b/plain.htm&node_id=64

5.2.4.1 SAP IQ DB copy based on existing backup

Existing SAP IQ system copies along the SAP BW system can also be done via an existing database

backup of SAP IQ. To create such a reusable backup you can follow the recommendation as follows:

Before and/or after a regular or bigger Archiving Process you should create a new full backup (or

on a regularly base, e.g. once a week)

Within a shorter timeframe, e.g. on daily basis create one “incremental since full” (INSF) backup

For every single Archive run you can use the backup automation, to create an incremental backup

If you have to restore the SAP IQ database, also for an IQ system copy proceed as follows:

Import the last full backup (it is suitable to verify the full backup before the usage with “RESTORE

VERIFY”)

Import the last INSF backup based on the full backup

Import all remaining incremental backup after the last INSF backup

With this procedure, it should be possible to restore a consistent level of the SAP IQ database.

However under rare circumstances it might happen that there are some unwanted inconsistencies, e.g.

during the status change within a NLS request. Such cases can be fixed on demand by the SAP support.

So it is suitable to test the procedure on a regular base, like doing a SAP IQ system copy along with the

BW system.

An Example of a backup/restore script is shown on the next pages.

http://help.sap.com/saphelp_iq1608_iqbackup/helpdata/en/a8/8c434084f21015b2aadf2ab640b09b/frameset.htm

http://help.sap.com/saphelp_iq1608_iqbackup/helpdata/en/a8/8c434084f21015b2aadf2ab640b09b/frameset.htm

http://help.sap.com/saphelp_iq1608_iqbackup/helpdata/en/a6/13fdea84f21015aaa499e4bc801d20/content.htm?frameset=/en/a6/236d0484f2101591fabb9064294f1d/frameset.htm&current_toc=/en/a8/8c434084f21015b2aadf2ab640b09b/plain.htm&node_id=63



http://help.sap.com/saphelp_iq1608_iqbackup/helpdata/en/a6/236d0484f2101591fabb9064294f1d/content.htm?frameset=/en/a6/13fdea84f21015aaa499e4bc801d20/frameset.htm&current_toc=/en/a8/8c434084f21015b2aadf2ab640b09b/plain.htm&node_id=64




February 2016 86

#/* -----------------------------------------------------------*/

### systemcopy from CIANLS to SAPIQDB

#/* -----------------------------------------------------------*/

## stop the target IQ

## Start utility_db on the target machine (use much memory; analog to the system

that is replaced by the load)

start_iq -n utility_db -iqmc 40000 -iqtc 60000

## Connect to utility_db:

dbisql -c "uid=DBA;pwd=sql;eng=utility_db;dbn=utility_db”

## At the target system

delete db-file and log-file of the instance to be replaced (SAPIQDB) delete all

data files of SAPIQDB as well

## Restore database

restore database '/usr/sap/sybase/sapdata/db/SAPIQDB.db'

from '/usr/sap/sybase/sapdata/backup/CIANLS_full_20140707_010000.014470'

rename IQ_SYSTEM_MAIN to '/xxxx/SAPIQDB_main_001.iq'

rename IQ_SYSTEM_TEMP to '/xxxxx/tmp/SAPIQDB_tmp_001.iqtmp'

rename NLSDBSPACE001_001 to '/xxxxx/NLSDBSPACE001/NLSDBSPACE001_001.iq'

....

rename NLSDBSPACE001_045 to '/xxxxx/NLSDBSPACE001/NLSDBSPACE001_045.iq'

rename CIANLS_tmp_002 to '/xxxx/tmp/SAPIQDB_tmp_002.iqtmp'

....

rename CIANLS_tmp_030 to '/xxxx/tmp/SAPIQDB_tmp_030.iqtmp'

rename IQ_SYSTEM_MSG to '/xxxxx/logfiles/SAPIQDB.iqmsg'

## Create transactionlog for the restored SAPIQDB:

dblog -t /usr/sap/sybase/sapdata/db/SAPIQDB.log

/usr/sap/sybase/sapdata/db/SAPIQDB.db

## start the target IQ

## log on to the target IQ (logins and passwords are loaded from original

instance CIANLS)

## create new schema user for NLS; BW is using the login to connect to IQ assign

appropriate permissions;

## same permissions as the original user maybe like this:

## only necessary if the user name contains the <sid> CIANLS

create user SAP<SID>IQDB identified by '**********';

grant READCLIENTFILE, MONITOR, MANAGE any EVENT to SAP<SID>IQDB;

grant ROLE SYS_AUTH_RESOURCE_ROLE to SAP<SID>IQDB with no ADMIN OPTION;

grant CREATE TABLE to SAP<SID>IQDB with no ADMIN OPTION;


February 2016 87

## change table owners; so that new user will be the owner


ALTER TABLE table_name ALTER OWNER TO new_owner

these are the tables:

select table_name, suser_name(creator) from systab

where suser_name(creator) = 'CIANLS'

and table_type_str = 'BASE'

## the statements for changing the owner are created with this command:

select 'alter table "' || suser_name(creator) || '"."' || table_name || '" alter

owner to "yyyy"' from systab where suser_name(creator) = 'CIANLS' and

table_type_str = 'BASE'

## creating the target views


## It is not possible to change the owner of a view; therefore the views must be

exported, the owner must be changed and then the statement must be applied

## This command can be used to display the views and replace the owner:

select replace (view_def, 'SAPQ6MNLS', 'DBA') from sysview where view_def like

'create view "SAPQ6MNLS"%'

## create the target messagefile (already done during the load)

select * from sysdbfile where upper(dbfile_name) like '%MSG%'

alter dbspace iq_system_msg rename 'new-pathname'

## rename the target dbfiles and dbspaces

## only necessary if the dbspace or dbfile names contain the <sid> CIANLS

alter dbspace yyy rename to xxx

alter dbspace yyy alter file xxx rename to zzz

## these are the dbspaces and dbfiles:

select dbfile_name from sysdbfile

select dbspace_name from sysdbspace

## or as a join:

select dbspace_name , dbfile_name from sysdbspace dbs, sysdbfile dbf where

dbs.dbspace_id = dbf.dbspace_id

## just an overview for checking additional objects, procedures, events, etc,

containing the instance name

select proc_name from sysprocedure where lower(proc_defn) like '%CIANLS%'

select event_name, source from sysevent where lower(source) like '%CIANLS%'

www.sap.com/contactsap


http://www.sap.com/contactsap

Date post:	05-Dec-2021
Category:	Documents
Upload:	others
View:	7 times
Download:	0 times

SAP First Guidance - BW on HANA 1

Documents