First Guidance SAP BW: Implementation SAP …docshare01.docshare.tips/files/25041/250413825.pdf · SAP NetWeaver BW 7.0x ... (successor of SAP Control Center).. 46 2.1.7.5 Pluggable

SAP First Guidance

SAP BW 7.3x/7.4

SAP Realtime Database Platform

Applicable Releases:

SAP NetWeaver BW 7.0x

SAP NetWeaver BW 7.3x

Sybase 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. 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 with Sybase IQ.

For more Information please contact [email protected]

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

mailto:[email protected]

SAP First Guidance

SAP BW 7.3x/7.4

SAP Realtime Database Platform

Version 1.81

July 2014

© Copyright 2014 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 Sybase IQ 15.4#ESD3, further SAP adaption, Sybase 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 Sybase IQ 16.0, SAP-NLS Backup, corrections/additions

1.32 Update IQ 16.0 SP03, IQ Agent and SCC additions

1.40 Adding extended table support access IQ-HANA, DBACOCKPIT

1.42 Update IQ 16.0 SP04.02-05

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

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 Sybase IQ

July 2014 1

Table of Contents

1. Implementation SAP-NLS Solution with Sybase 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 IQ server ....................................................... 4

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

1.2.4 Sybase IQ Database Server under Linux .......................................................... 8

1.2.5 Sybase IQ Database Server under Windows .................................................... 9

2. Installation of the Components....................................................................................... 10

2.1 Installation/Configuration of the Sybase IQ database ............................................... 10

2.1.1 Sizing/Architecture/Scalability Overview ...................................................... 10

2.1.2 Installation IQ 15.4 Software ............................................................................. 11

2.1.2.1 Add the IQ ODBC driver 15.4 to the kernel ................. 11

2.1.3 Installation IQ 16.0 Software ............................................................................ 12

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

2.1.4.1 Apply one-off patch on top of SP01 .......................... 24

2.1.4.2 Apply SP04 for Sybase IQ 16.0...................................25

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

2.1.4.4 Apply SP08.01 for Sybase IQ 16.0 ............................ 34

2.1.4.5 Apply one off Patch SP08.02 for Sybase IQ 16.0 .... 34

2.1.5 Upgrade from IQ from Version 15.4 to 16.0 ................................................... 34

2.1.6 Upgrade from IQ from Version 16.0 SP04.0x to SP08.0x ........................... 36

2.1.7 Build and configure a new IQ 15.4/16.0 database ......................................... 37

2.1.7.1 Create the IQ database for NLS................................. 38

2.1.7.2 start/stop the IQ database ......................................... 41

2.1.7.3 start/stop the SAP Control Center (SCC) ............... 42

2.1.7.4 The COCKPIT (successor of SAP Control Center) .. 46

2.1.7.5 Pluggable Authentication Module (PAM) for UNIX .. 47

2.1.7.6 Apply the DB Options for the IQ database ................ 47

2.1.7.7 Extend the IQ database (datafiles/temp) ................ 48

2.1.7.8 Check the status of the SAP Sybase IQ database ... 49

2.2 Install the SAP components for Sybase IQ ................................................................. 50

2.2.1 Add the ODBC IQ driver to the SAP Kernel .................................................... 50

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

2.3 Configure Smart Data Access - HANA and IQ ............................................................. 51

2.4 Configure extended table access – HANA and IQ .......................................................53

2.4.1 Creating the RLV dbspace in IQ .......................................................................54

2.4.2 Checking the RLV Store Memory Usage .........................................................54

2.4.3 Creating the Extended Storage in SAP HANA ................................................54

2.4.4 Validating the Extended Storage Configuration............................................ 56


July 2014 2

2.4.5 Enable BW Objects for using the Extended Storage ...................................... 57

2.4.5.1 Pre-Requisites .............................................................. 57

2.4.5.2 Procedure for write-optimized DataStore objects ... 57

2.4.5.3 Procedure for PSA Tables .......................................... 58

3. Configuration of the SAP Components .......................................................................... 59

3.1 Sybase IQ related ........................................................................................................... 59

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

3.2 SAP NetWeaver BW related........................................................................................... 61

3.2.1 Apply the latest corrections for the NLS Solution. ........................................ 61

3.2.2 Transaction DBCO - database connection to IQ ........................................... 62

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

3.2.4 SAP-NLS Backup Solution............................................................................... 64

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

3.2.5.1 RSDA_SYB_PARTITION_MONITOR.......................... 65

3.2.5.2 Adding Sybase IQ to DBACOCKPIT transaction...... 66

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

5. Appendix ....................................................................................................................... 69

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

5.2 Common Maintenance Tasks for IQ ............................................................................ 69

5.2.1 Increasing the Size of dbspace ....................................................................... 69

5.2.2 Modifying Cache Sizes or Startup Parameters ............................................. 70

5.2.3 Backup/Restore of an IQ database ................................................................ 70


July 2014 3

1. Implementation SAP-NLS Solution with Sybase 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 1796393 - SAP BW near-line solution with Sybase IQ

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

The BW System you want to use must 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.

The Sybase 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 IQ leverages the complete

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

For the current timeframe the supported OS versions for the SAP-NLS solutions are Windows X64 and

Linux X86-64. Additional OS Versions are under Evaluation.

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 NLS Add-On from the Development

Partner PBS – http://www.pbs-software.com

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://www.pbs-software.com/


July 2014 4

1.2.2 Default file system layout on the IQ server

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

Server name: SAPIQ_SERVER

Database name: SAPIQ_DB

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

Binary Installation Directory: /usr/sap/<SID>/SAPIQ/server/ # $SYBASE

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

Path for SYSTEM LOG: /usr/sap/<SID>/SAPIQ/sapdata/log

Path for SYSTEM DBSPACE: /usr/sap/<SID>/SAPIQ/sapdata/system

Path for server MESSAGES: /usr/sap/<SID>/SAPIQ/sapdata/messages

Path for TEMPORARY Space: /usr/sap/<SID>/SAPIQ/sapdata/temp # IQ load

Path for TMP Space: /usr/sap/<SID>/SAPIQ/sapdata/tmp # IQ sort

Path for HTML Query Plans: /usr/sap/<SID>/SAPIQ/sapdata/html

Path for further DBSPACE: /usr/sap/<SID>/SAPIQ/sapdata/SAP<SID>DBSPACExxx

Distinguish between the “usage types”: NLS (Near-Line Storage) and ETS (Extended Table Storage)

So the Parameter <SID> could bei either point to a Near-Line Storage Database, or to an Extended Table

Storage Database due to the different Backup Strategies.

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.


July 2014 5

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

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

IQ 15.4 ESD#3, IQ 16.0 SP’s http://service.sap.com/patches

Sybase IQ Version 15.4 ESD#3 at http://service.sap.com/patches (Linux and win64)

Or Sybase 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


July 2014 6

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

at http://service.sap.com/patches

Note 1951041 - SybaseIQNetClient 16.0 SP03 Release Notes Information

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

at http://service.sap.com/patches

Please Note that the LibDBSL for SAP Sybase ASE/IQ and the SAP Sybase 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.


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



July 2014 7

SAP Sybase IQ Client (Win 32-Bit) - DVD51045880

Create a temporary directory structure to store the needed files. Either one of the LibDBSL files

matches your 7.20/7.21 or higher EXT-UC Kernel.

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


July 2014 8

1.2.4 Sybase IQ Database Server under Linux

Installing For the First Time

Follow these steps to install SAP Sybase 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

Sybase Product Download Center at: https://sybase.subscribenet.com or SAP® Service

Marketplace at http://service.sap.com/licensekeys 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 Sybase IQ server components, activate your license, then start and test your server.

Install and configure SAP Sybase IQ client components

Needed Licenses for the SAP-NLS option:

o 7010846 Sybase IQ Enterprise Edition

o 7010848 Sybase IQ Unstructured Data Analytics

o 7010850 Sybase IQ Very Large Database Management Option

To figure out the correct values for CPU cores and MAC address 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

http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc10083.1600/doc/html/san1282692425799.h

tml

Check out the additional needed license options with the Product Version Enterprise Edition (IQ_EE) here

Unstructured Data Analytics option (IQ_UDA) supports binary large object (BLOB)

Very Large Database Management Option (IQ_VLDBMGMT)

These are bundled in the SAP-NLS License provided by SAP.

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc38159.1600/doc/html/r

hi1334847427020.html

https://sybase.subscribenet.com/

http://service.sap.com/licensekeys

http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc10083.1600/doc/html/san1282692425799.html



July 2014 9

Installation Details: http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc10083.1540/doc/html/title.html

Create the OS user sybase on the Sybase IQ database server. The user requires remote access authorization for remote accesses (TELNET or SSH) to the Sybase IQ database server.

Set up the directory /usr/sap/sybase/server on the Sybase 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/sybase/sapdata on the Sybase 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/sybase/sapdata on the Sybase 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 Sybase 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/sybase/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:

/usr/sap/NLS/SAPIQ/database

/usr/sap/NLS/SAPIQ/sapdata/db

/usr/sap/NLS/SAPIQ/sapdata/log

/usr/sap/NLS/SAPIQ/sapdata/system

/usr/sap/NLS/SAPIQ/sapdata/messages

/usr/sap/NLS/SAPIQ/sapdata/temp

/usr/sap/NLS/SAPIQ/sapdata/html

1.2.5 Sybase IQ Database Server under Windows Installation Details: http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc30056.1540/doc/html/title.html

The installation is performed on the Sybase IQ database server under a user with administration rights.

Set up the directory <drive>:\usr\sap\sybase\server on the Sybase 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\sybase\sapdata on the Sybase IQ database server. The directory should guarantee disk space of at least 180 GB.

Productive use: Set up the directory <drive>:\usr\sap\sybase\sapdata on the Sybase 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\sybase\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 like in the description above. The (current) Best Practice Guide for Sybase IQ 15.4 can be found here: http://www.sybase.com.br/files/White_Papers/SybaseIQ15_BestPractices_03012012.pdf

http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc10083.1540/doc/html/title.html

http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc30056.1540/doc/html/title.html

http://www.sybase.com.br/files/White_Papers/SybaseIQ15_BestPractices_03012012.pdf


July 2014 10

2. Installation of the Components

2.1 Installation/Configuration of the Sybase IQ database

2.1.1 Sizing/Architecture/Scalability Overview

For a general sizing guideline see the following document:

http://www.sybase.com/files/Technical_Documents/Sybase_IQ_Sizing_Guide.pdf

Simplex Server Architecture

Simplex is a single instance of an SAP Sybase 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://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc38159.1600/doc/html/rhi1334847

427020.html

Multiplex Server Architecture

Multiplex are multiple instances of SAP Sybase IQ servers running on multiple machines. SAP Sybase 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://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc38159.1600/doc/html/rhi1334847426786.html

Scalability

SAP Sybase 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 Sybase 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 Sybase IQ database, but is especially important as your database grows to the multi-terabyte scale.


SAP Sybase IQ Development Center

http://scn.sap.com/community/developer-center/analytic-server

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

http://www.sybase.com/files/Technical_Documents/Sybase_IQ_Sizing_Guide.pdf







http://scn.sap.com/community/developer-center/analytic-server

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


July 2014 11

2.1.2 Installation 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 Sybase IQ 16.0 in Chapter 2.1.3, as the

steps are identical.

2.1.2.1 Add the 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>/DVEBMGS02/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



July 2014 12

2.1.3 Installation IQ 16.0 Software Documentation:

http://help.sap.com/iq1608/#section2 and http://help.sap.com/iq1608/#section5 Details for the sybase control center (SCC) installation http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01002.0327/doc/pdf/scc_installation.pdf

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.61) with the Xming Extension. For details how to use it, visit the URL


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

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

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

http://help.sap.com/iq1608/#section5

http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01002.0327/doc/pdf/scc_installation.pdf

http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01002.0327/doc/pdf/scc_installation.pdf



July 2014 13

The directory /usr/sap/sybase/server might already available and the environment variable $SYBASE will point to /usr/sap/sybase/server


July 2014 14

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”.


July 2014 15

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.


July 2014 16

Don’t install the Evaluation Version of Sybase IQ 16.0

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


July 2014 17

Apply the license in a later step.

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


July 2014 18

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


July 2014 19

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

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


July 2014 20

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).


July 2014 21

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

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


July 2014 22

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 /sybase/SAPNLS/IQ.sh

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

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

alias start_nls='start_iq @SAPIQDB.cfg SAPIQDB.db'

alias stop_nls='stop_iq'

Only the first line is strictly required, the other are optional / for convenience.

If th e direc tory /bin/env do es no t exis t, e nt er the follo wing c omman d 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


July 2014 23

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

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


Online Help for Sybase IQ16 SP01

http://infocenter.sybase.com/help/index.jsp?docset=/com.sybase.infocenter.help.iq.16.0.1/doc/html/

title.html&docSetID=1962

The upgrade process is identical as the installation process, see Chapter before. Make sure the user sa is unlocked before you apply the SPx Package.

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

Installation.


http://infocenter.sybase.com/help/index.jsp?docset=/com.sybase.infocenter.help.iq.16.0.1/doc/html/title.html&docSetID=1962



July 2014 24

2.1.4.1 Apply one-off patch on top of SP01

Sybase 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 as

described and follow the procedure in Chapter 2.1.4

The one-off patch for SP01 (01.01) is fixing the following problems:

SwrID CR Description

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

SP01.01 735487 An update statement to update IQ table failed when the statement included the

IsNumeric function.

1> update t set a = '1' where isnumeric(a)=0 2> go Msg 7338, Level 15,

State 0: SQL Anywhere Error -728: Update operation attempted on non-updatable remote query

SP01.01 741466 Alter Table Add Default fails after INSERT into Quoted

Identifier Tablename Example:

CREATE TABLE "/TAB1"(COL1 int not null)

INSERT INTO "/TAB1" values (1);

ALTER TABLE "/TAB1" add COL2 int default 0

SP01.01 739459 If CESU8BIN was selected as collation to create the database, the resource could not

be registered properly. This is now resolved.

To Apply the Correction, please follow the following instructions:

Stop the IQ server and the sybase control center (SCC) first

Unpack the TGZ file (AIX, Linux64) with tar –xvf LinuxAMD64-iq160_ctrl01.01.tgz

Or Unzip the ZIP file (Win64) Win64-iq160_ctrl01.01.zip into a temporary directory on

your IQ server. Make sure the file properties (user:group) are correct.

Move to the temporary directory and copy the new binaries into the right directories in the $SYBASE

location.

$SYBASE/SCC-3_2/bin/scc.sh --stop

cd /data/software/sybase/IQ16_0/SP01.01

cd iq1600_sp01.01

cp -Rp * /data/sap/sybase/server/IQ-16_0

cd scciq-3_2

cp -Rp * /data/sap/sybase/server/SCC-3_3/plugins

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

Restart the IQ server and the SCC Instance

Now your Sybase IQ one-off patch on top of SP01 is applied and ready to use.

Please Note: This Procedure is obsolete, as already newer SP’s released, as stated in Chapter 2.1.4.2

Furthermore the one off patch EBF 21738: 16.0 SP01 PL03 is not necessary either, as there is SP03

for IQ 16.0 available since 20th of December 2013


July 2014 25

2.1.4.2 Apply SP04 for Sybase IQ 16.0

Note 2015011 - SAPIQ 16.0 SP4 Release Notes Information

There is no upgrade procedure from SP03 to SP04, as this is only a binary switch.

Online Help for Sybase IQ16 SP03

http://infocenter.sybase.com/help/index.jsp?docset=/com.sybase.infocenter.help.iq.16.0.4/doc/html/

title.html&docSetID=1962

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

lt5006:/data/software/sybase/IQ16_0> tar -xvf IQSERV160003_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.

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








July 2014 26

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

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


July 2014 27

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

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


July 2014 28

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


July 2014 29

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


July 2014 30


July 2014 31

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

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


July 2014 32

Check the file /usr/sap/sybase/server/SCC-3_2/bin/scc-console.out


July 2014 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.


July 2014 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

To apply the one off patch 04.05 on top of SP04 for Sybase IQ 16.0 follow Chapter 2.1.4.1 in this First

Guidance Document.

2.1.4.4 Apply SP08.01 for Sybase IQ 16.0

Note 2021344 - SAPIQ 16.0 SP08 Release Notes Information


To apply SP08.01 for Sybase 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.4.5 Apply one off Patch SP08.02 for Sybase IQ 16.0


To apply the one off patch 08.02 on top of SP08 for Sybase IQ 16.0 follow Chapter 2.1.4.1 in this First

Guidance Document.

2.1.5 Upgrade from 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://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01825.1600/doc/pdf/iqmigwin.pdf

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










http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01825.1600/doc/pdf/iqmigwin.pdf


July 2014 35

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;

Stop the IQ database with

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


July 2014 36

2.1.6 Upgrade from IQ from Version 16.0 SP04.0x to SP08.0x


Start the IQ database (for the Upgrade Process) with


start_iq @CIANLS.cfg CIANLS.db -iqro 1 -gm 1 -gd DBA -iqrvrec_bypass 1

Run the I-SQL Interface with

alter database upgrade;

Stop the IQ database with

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

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));




July 2014 37

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

2.1.7 Build and configure a new 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 Sybase IQ 16.0 on a Linux server with 16x4 Core CPU cores (necessary later

for the data stripping) and 256GB RAM. The Sybase 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


July 2014 38

2.1.7.1 Create the 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://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01771.1600/doc/html/san1283555

474735.html

Note 1992512 - How to use Utility Database of SAP Sybase 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}"

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

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






July 2014 39

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 Sybase 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

/* ============================================================*/

/* create_database.sql */

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

/* V.20130320-01 */

/* ============================================================*/

CREATE DATABASE 'SAPIQDB.db'

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

COLLATION 'CESU8BIN'

ENCODING 'CESU8'

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

CASE RESPECT

IQ PATH 'SAPIQDB_main_001.iq'

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

PAGE SIZE 262144

IQ SIZE 8192

TEMPORARY SIZE 8192

JCONNECT ON

JAVA ON

BLANK PADDING ON

;


July 2014 40

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

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

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

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

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

#/* V.20130320-01 */

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

### Name of the server

-n SAPIQSERVER

#### -c 512 increased on 20130207 to support 2 GB files as client blob loading

-c 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

#### location of the temp dir for IQ

-dt /usr/sap/sybase/sapdata/temp

#### network

-x tcpip{port=2640}

#### everybody is allowed to load table statement

-gl all

#### Number of connections in the server

-gm 100

-gp 4096

-ti 4400

#### timeout for debugging

-tl 600

#### Prevent UDP connection support

-sb 0

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

-p 16000

#### Displays diagnostic communication messages

-z

#### log activities on the server

#-zr all

#### LOG DIAGNOSTIC

-o /usr/sap/sybase/sapdata/log/SAPIQDB_DIAG.log

#### Name of log file

-zo /usr/sap/sybase/sapdata/log/SAPIQDB_PROTOCOL.log

#### size of the log file

-zs 10m

#### Number of log files

-zn 5

#### size of iqmessagefile in mb

-iqmsgsz 100

#### versions of iqmessagefile

-iqmsgnum 5


July 2014 41

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 Sybase IQ 16.0 and Maintenance can be found here:


http://help.sap.com/iq1608/

2.1.7.2 start/stop the 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 Sybase IQ database instance "SAPIQDB"

# V.20132002-01

# -----------------------------------------------------------------------------

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 Sybase IQ database instance "SAPNLS_DB"

# V.20132002-01

# -----------------------------------------------------------------------------

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_iq1608_iqicg_lin/helpdata/en/a6/8257b984f210159d74ad7d057bbc49/f

rameset.htm


http://help.sap.com/iq1608/



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


July 2014 42

2.1.7.3 start/stop the SAP Control Center (SCC)

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

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

SCC> shutdown

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

The default user accounts are sccadmin (SAP Control Center) and uafadmin (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


July 2014 43

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


July 2014 44

Authenticate the SCC Agent for your IQ server now

Now you can start monitoring and administer your IQ database.


July 2014 45


July 2014 46

2.1.7.4 The COCKPIT (successor of SAP Control Center)

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

COCKPIT> shutdown

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

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

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

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

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

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

# 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 4284 false lt5006

EmbeddedWebContainer http.port 4282 false ANY

EmbeddedWebContainer https.port 4283 false ANY

Tds tdsPort 4285 false ANY

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

Messaging messaging.db.port 4638 false ANY

Messaging messaging.port 4993 false ANY

Alert alert.database.port 4638 false ANY

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

sybase@lt5086:/usr/sap/NLS/SAPIQ/server/COCKPIT-4/bin> ./instance -enable

Enabling shared install mode for /usr/sap/NLS/SAPIQ/server/COCKPIT-4 ...

sybase@lt5086:/usr/sap/NLS/SAPIQ/server/COCKPIT-4/bin> ./passencrypt -csi

Password:

{SHA-256:uGCK23UdXjI=}cBtv6ogXg73gmHdmtsayivf5ToiACmwspY7Y7lnqsIE=

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


July 2014 47

2.1.7.5 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

http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01267.0327/doc/html/bth1253572

423588.html

2.1.7.6 Apply the DB Options for the 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 Sybase IQ database.

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

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

/* @(#)options.sql */

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

/* V.20130320-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=1000;

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;

http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01267.0327/doc/html/bth1253572423588.html

http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01267.0327/doc/html/bth1253572423588.html


July 2014 48

2.1.7.7 Extend the 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 */

/* Sybase 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 128;

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';


July 2014 49

2.1.7.8 Check the status of the SAP Sybase IQ database

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

the SAP Sybase 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)

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://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc38159.1600/doc/html/rhi1334847

427020.html

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

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc38151.1540/doc/html/s

an1278453250070.html

Note 1843189 - SAP Sybase IQ Troubleshooting and diagnostics collection checklist

check this Note for more Information.



http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc38151.1540/doc/html/san1278453250070.html

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc38151.1540/doc/html/san1278453250070.html



July 2014 50

2.2 Install the SAP components for Sybase IQ

2.2.1 Add the ODBC IQ driver to the SAP 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.


SAPCAR -xvf _sar\IQCLIENT160SP0X_0-1001xxxx.SAR

SAPCAR: processing archive _sar/IQCLIENT160SP03_0-1001xxxx.SAR (version 2.01)

x dblgen16.res

x dblgen_iq16.res

x dblgja16_eucjis.res

x dblgja16_sjis.res

x dblgja16_utf8.res

x dblgja_iq16_eucjis.res

x dblgja_iq16_sjis.res

x dblgja_iq16_utf8.res

x dblgzh16_cp936.res

x dblgzh16_eucgb.res

x dblgzh16_utf8.res

x dblgzh_iq16_cp936.res

x dblgzh_iq16_eucgb.res

x dblgzh_iq16_utf8.res

x libdbicu16.so

x libdbicu16_r.so

x libdbicudt16.so

x libdbodbc12.so

x libdbodbc16_n.so

x libdbodbc16_r.so

x libdbodbcansi16_r.so

x libdbodbcinst16_r.so

x libdbodm16.so

x libdbtasks16.so

x libdbtasks16_r.so


2.2.2 Add the IQ LibDBSL to the SAP Kernel sybase@lt5006:/data/software/sybase/IQ16.0/Note1737415>

SAPCAR -xvf _sar\lib_dbsl_xxx-10010165.sar

SAPCAR: processing archive lib_dbsl_427-10010165.sar (version 2.01)

x dbsybslib.so

x dbsybslib.pdb

x patches.mf

x SIGNATURE.SMF



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


July 2014 51

2.3 Configure Smart Data Access - HANA and IQ

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 1879294 - SAP HANA smart data access SP 1

Note 1981141 - SAP HANA smart data access SP 3

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 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>

Update the <sid>adm (.sapenv.sh) profile so that the two environment variables are set as shown:

export ODBC_IQ=libdbodbc16_r.so

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/sap/NLS/SAPIQ/server/IQ-16_0/lib64

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

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

following structure:

lt5006: /usr/sap/<SID>/home> vi .odbc.ini

[IQSOURCE]

Driver= libdbodbc16.so

ServerName=SAPIQSERVER

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

After these manual settings, you have to restart the HANA server to make the changes active. lt5006:/usr/sap/<SID>/HDB<nr>> HDB stop

lt5006:/usr/sap/<SID>/HDB<nr>> HDB start










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


July 2014 52

Use a SAP HANA Studio Version from SP06 onwards to configure a new remote source to an existing IQ

server.

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

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

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

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


July 2014 53

2.4 Configure extended table access – HANA and IQ

Extended Table Feature is on Pilot Release only! Please consult the following SAP Note:

Note 1983178 - HANA Extended Storage for BW - early shipment

(Setting up extended tables for BW and concept PDF attached)

Overall Guide for extended table storage - http://scn.sap.com/docs/DOC-53592

SAP Sybase IQ 16 Hardware Sizing Guide - http://scn.sap.com/docs/DOC-41455

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

Note 1637145 - SAP BW on HANA: Sizing SAP In-Memory Database

The extended table feature is available on pilot usage with the following product versions onwards:

SAP NetWeaver BW 7.4 SPS05 and higher SAP HANA SPS07 and higher

SAP IQ 16.0 SP04.02 and higher

The SAP IQ ODBC driver is installed For now you have to activate a parameter in the Configuration of the HANA (a restart is necessary) in the indexserver.ini enable_extended_storage_feature = true

SAP IQ for BW on HANA extended storage is supported only on the Linux x86-64 operating system.

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










July 2014 54

2.4.1 Creating the RLV dbspace in IQ The RLV (row level verification) store must be only large enough to keep the data in memory that is being

loaded and changed prior to being merged with the IQ main store data.

The correct amount depends on the number of tables, and how frequently the data is loaded and merged.

Use the sizing guidelines provided in the SAP Note 1637145 to determine the optimal size for RLV

dbspace.

Enter this statement into the DBISQL SQL Statements window; changing the settings to match those

required for your site (this example creates an RLV dbspace of 4 GB):

Start interactive SQL: dbisql –c “uid=DBA;pwd=sql;eng=SAPIQSERVER;dbn=SAPIQDB”

CREATE DBSPACE SYB_RLV

using file SYB_RLV_001

'/usr/sap/NLS/SAPIQ/database/sapdata/SAPIQDB_RLV_001.iq'

size 12 GB

IQ RLV STORE;

sp_iqcheckdb 'check dbspace SYB_RLV'

sp_iqcheckdb 'allocation dbspace SYB_RLV'

HANA extended storage does not support raw devices. You must use filesystem devices. Refer to the

sizing guidelines to size the user dbspace. If your Sybase IQ database is already created like that, there is

no further adaption of the database needed.

2.4.2 Checking the RLV Store Memory Usage The stored procedure sp_iqrlvmemory checks the RLV store memory usage per table.

Start interactive SQL: dbisql –c “uid=DBA;pwd=sql;eng=SAPNLS_SERVER;dbn=SAPIQDB”

sp_iqrlvmemory 'EXT_/BIC/B0000641000_SAPHBW' (for PSA table /BIC/B0000641000)

2.4.3 Creating the Extended Storage in SAP HANA Before tables can be created or generated as extended tables, you need to connect SAP IQ to the SAP

HANA database. This is done by creating an extended storage in the SAP HANA Administration Console of

the SAP HANA Studio.

Open the SQL console for the SAP HANA system and create the extended storage configuration with the

following SQL statement running in the SAP<SID> Schema:

CREATE EXTENDED STORAGE CONFIGURATION

'Driver=/usr/sap/<SID/federation/libdbodbc16_r.so;

ServerName=<Name of IQ server>;

CommLinks=tcpip(host=<host name>:<port>)'

WITH CREDENTIAL TYPE 'PASSWORD' USING 'user=<Name of IQ database user>;

password=<Password of IQ database user>;

hanauser=<Name of SAP HANA database user>;

hanapassword=<Password of SAP HANA database user>';


July 2014 55

Tables can now be created as extended tables in the HANA database.

See also the SCN Document - https://scn.sap.com/docs/DOC-53048

Example:

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


July 2014 56

2.4.4 Validating the Extended Storage Configuration

In the SQL console for the SAP HANA system you can check the extended storage configuration.

In the console you can execute the following command example. This checks drivers and dependency files

of the SAP IQ database:

hdbsdautil -t iqodbc -S "Driver=libdbodbc16_r.so;

DatabaseName=<Name of IQ database>;

ServerName=<Name of IQ server>;

CommLinks=tcpip(host=<host name>;port=<port>)"

-U <user name>

-P <password>

–info

Example:

lt5006:/usr/sap/HBW/HDB10> hdbsdautil -t iqodbc -S

"Driver=/usr/sap/HDB/federation/libdbodbc16_r.so;enginename=SAPIQSERVER;CommLink

s=tcpip(host=lt5006.wdf.sap.corp:2640)" -U DBA -P sql -Q "select count(*) from

sysobjects" -info

Verifying command arguments...

Checking ODBC configuration in string:

"Driver=/usr/sap/HBW/federation/libdbodbc16_r.so;enginename=CIANLS;CommLinks=tcp

ip(host=lt5006.wdf.sap.corp:2640)"...... OK!

Check ODBC drivers...... OK!

Connecting remote database...... OK!

Dumping ODBC information:

==========================================================================

Driver ODBC version: 03.51

Driver version: 16.00.0627

Driver name: SQL Anywhere

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

Server name: CIANLS

DBMS name: Sybase IQ

DBMS version: 16.00.0000

ODBC conformance: Level 2

ODBC SQL conformance: Extended grammar

SQL identifier case: Case insensitive

Maximum qualifier name length: 0

Maximum table name length: 128

==========================================================================

Executing SQL: select count(*) from sysobjects

Result of SQL execution:

==============================================================================

Col 1: type 3, precision 10, scale 0, colname count(), nullable 0

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

Fetched row 1: [1250]

==============================================================================


July 2014 57

2.4.5 Enable BW Objects for using the Extended Storage

2.4.5.1 Pre-Requisites

If you already used the Extended Table Feature as a Pilot Solution and you update your existing IQ

16.0 Installation from SP04.0x to SP08.0x or higher, you have to pay special attention to the RLV

space. See Chapter 2.1.6 for more Details.

A filled WO-DSO or PSA cannot be moved to an Extended Table. You can only create an empty

Object with the option “Extended Table”.

2.4.5.2 Procedure for write-optimized DataStore objects


July 2014 58

2.4.5.3 Procedure for PSA Tables

Check for the table as well from the HANA studio


July 2014 59

3. Configuration of the SAP Components

Documentation:

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/e8/395401e46f4edca50aefeead7f3a44/framese

t.htm

3.1 Sybase IQ related

3.1.1 Create/configure SAP<SID>IQDB user You can use the Sybase Control to create the necessary user

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/e8/395401e46f4edca50aefeead7f3a44/frameset.htm

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/e8/395401e46f4edca50aefeead7f3a44/frameset.htm


July 2014 60

Alternative you can create the user as well with the following script. In case the authorizations

“read/write client file” is not supported anymore by the server, use the role DBA.

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

/* @(#)user.sql */

/* Sybase IQ database instance "SAPIQDB" - create USER */

/* V.20130320-01 */

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

create user SAP<SID>IQDB identified by '**********';

grant BACKUP, READCLIENTFILE, RESOURCE to SAP<SID>IQDB

grant DBA to SAP<SID>IQDB

If we have more than one System connect to the IQ database, the logon is handled differently to separate

the access of the user data.


July 2014 61

3.2 SAP NetWeaver BW related

3.2.1 Apply the latest corrections for the NLS Solution.

Therefore go to the Note search http://service.sap.com/notes and use the Keywords SAPKW73011 NLS:

BW-BEX-OT-DBIF 1937201 Error without exception with sel. deletion with NLS

BW-BEX-OT-OLAP 1891983 System throws an error SFK_MESSAGE-02- when you have NLS

BW-BEX-OT-VC 1893890 Slow query to NLS with selection of navigation attributes

BW-WHM-DST-ARC 1858550 Downport NLS IQ to BW 7.0X

BW-WHM-DST-ARC 1920209 SPO archiving: Message RSDA 101 in the copy phase

BW-WHM-DST-ARC 1931251 NLS lookup results in the error CX_RSDA_ACCESS_ERROR

BW-WHM-DST-ARC 1937705 NLS: Lookup on write-optimized DSO returns error RSDA 252

BW-WHM-DST-ARC 1884712 Error COMPUTE_BCD_OVERFLOW during DAP archiving

BW-WHM-DST-ARC 1890790 BW on SAP HANA: SQL error 464 during archiving of IMOCube

BW-WHM-DST-ARC 1900379 Improved Backup Automation with IQ NLS

BW-WHM-DST-ARC 1900909 Lookup on NLS loses where condition

BW-WHM-DST-ARC 1901325 NLS/ADK write variant shows initial values in process chain

The mentioned Notes reflecting also the corrections after applying NetWeaver 7.30 SP10.

With the Note 1858550 it is also possible to use the SAP-NLS released with 7.30 SP09 in lower 7.30

releases as well.

Use the Transaction SNOTE to upload several Notes at once and apply the corrections

In Addition after you have SP03 applied for IQ 16.0 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 Sybase 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

http://service.sap.com/~sapidb/012003146900001557242013























July 2014 62

3.2.2 Transaction DBCO - database connection to IQ

Note 1737415 - Sybase IQ: Enable remote/secondary connect to SAP Sybase 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=SAPIQDB

SYBASE_DBNAME=SAPIQDB

SYBASE_CONTYPE=IQ

SYBASE_IQ_LOAD=1

SYBASE_IQ_CESU-8=1

SYBASE_IQ_BUFFER_SIZE=500000

SYBASE_IQ_LOCKWAIT=600

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.



July 2014 63

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...



July 2014 64

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




July 2014 65

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


July 2014 66

For Monitoring Details you can also check the Log from the used Background Process via SM50

3.2.5.2 Adding Sybase IQ to DBACOCKPIT transaction

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.


July 2014 67


July 2014 68

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

See also the Blog of Rainer Schlachter (Senior Developer, SAP AG) with additional Details.

SAP BW 730: What's New in the SAP BW Near-Line Storage Solution

The Overview of the SAP-NLS Solution on the SCN - http://scn.sap.com/docs/DOC-39944

See the new released How-To Paper:

How to Archive Data from SAP NetWeaver BW to SAP Sybase 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/people/rainer.schlachter/blog/2011/02/17/sap-bw-730-whats-new-in-the-sap-bw-near-line-storage-solution




July 2014 69

5. Appendix

5.1 Tipp’s for the IQ Administration

BP IQ IS IQ Software Installation

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 IQ server software as administrator user.

On UNIX, install the IQ server software as user sybnls.

5.2 Common Maintenance Tasks for IQ

You can perform a number of maintenance tasks at the command line or with SAP Control Center (SCC).

5.2.1 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 Sybase IQ 16.0 > Sybase Control Center 3.2.7 for SAP Sybase IQ> Administer and Monitor SAP Sybase IQ > DB Files

http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01267.0327/doc/html/jwi1278974853813.html




July 2014 70

5.2.2 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.

5.2.3 Backup/Restore of an IQ database

www.sap.com/contactsap


http://www.sap.com/contactsap