sap iq installation and update guide [ibm aix]

INSTALLATION GUIDE | PUBLICSAP IQ 16.1 SP 02Document Version: 1.0.0 – 2018-12-10

SAP IQ Installation and Update Guide [IBM AIX]

© 2

019

SAP

SE o

r an

SAP affi

liate

com

pany

. All

right

s re

serv

ed.

THE BEST RUN

Content

1 SAP IQ Installation and Update Guide [IBM AIX]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.1 You are Here in the Implementation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.2 Who Should Read this Document?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.3 What is SAP IQ?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.4 By the End of this Document, I Should be Able to.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 Learn What's New and Changed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113.1 What's New in this Release?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.2 Where this Guide Resides in the Information Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.3 Where do I Find Help?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4 Supported Server and Client Operating Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

5 Plan the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145.1 Installation Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Do I Need the SAP IQ Client? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Virtualized Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

5.2 Product Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Typical or Custom Installation?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17SAP IQ Server Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17SAP IQ Client Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Administration Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

5.3 License Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Evaluation Edition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Enterprise Edition and Licensed Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21License Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Before You Generate Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

5.4 Storage Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Raw Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Creating Dbspaces on Multiple Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Avoiding Environmental Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5.5 Network Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Network Clients and ODBC Kits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

5.6 Product Compatibilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385.7 Planning Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

6 Preinstallation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

2 P U B L I CSAP IQ Installation and Update Guide [IBM AIX]

Content

6.1 Check for Operating System Patches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406.2 Increase the Swap Space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416.3 Check Port Availability for SAP IQ Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416.4 Verify Network Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .416.5 Platform-Specific Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Adjust the Shared Memory Allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Enable the I/O Completion Ports (IOCP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Increase the Maximum User Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

6.6 Create the SAP IQ Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436.7 Download Installation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

7 Installing SySAM License Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457.1 Installing SySAM in GUI Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467.2 Installing SySAM in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477.3 Starting and Stopping a SYSAM License Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487.4 Apply or Update Licenses on the SySAM License Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .497.5 Understanding the SySAM Directory Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507.6 SySAM Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Using SySAM Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

8 Installing SAP IQ Server Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528.1 Installing a Server in GUI Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .538.2 Installing a Server in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558.3 Installing a Server in Unattended (Silent) Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Creating a Server Response File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Installing a Server Using a Response File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

8.4 Server Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .618.5 Finding Server Utilities and Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .628.6 Reviewing Server Installation Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

9 Installing SAP IQ Client Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659.1 Running the Client and Server On the Same System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .669.2 Installing a Client in GUI Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669.3 Installing a Client in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679.4 Installing a Client in Unattended (Silent) Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Creating a Client Response File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Installing a Client Using a Response File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

9.5 Client Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739.6 Finding Client Utilities and Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739.7 Reviewing Client Installation Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759.8 Configuring Client Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Connecting Using ODBC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

SAP IQ Installation and Update Guide [IBM AIX]Content P U B L I C 3

Connecting Using JDBC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Connecting Using OLE DB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Connecting Using Open Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Network Issues for SAP IQ Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81Connecting Across a Firewall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

10 Postinstallation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8410.1 (Optional) The Demo Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Creating the Demo Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Starting and Stopping the Demo Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86Removing the Demo Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

10.2 (Optional) The SAP IQ Utility Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Starting the SAP IQ Utility Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

10.3 Setting Up your Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Installation Directory Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88How SAP IQ Locates Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

10.4 Licensing After Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Verify and Authorize Optional Licensed Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Applying an Unserved License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Applying a Served License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

10.5 Starting and Running an SAP IQ Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10510.6 Stopping an SAP IQ Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10710.7 Start and Stop the SAP IQ Cockpit Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10810.8 Stopping the SAP IQ Cockpit Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10910.9 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

Using Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11010.10 Remove Sample Application Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11110.11 Starting Interactive SQL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11110.12 Verify SAP IQ Server Is Licensed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

11 What's Next?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Next Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

12 Troubleshooting your Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11512.1 What to do when the Installation Fails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Installer Fails with JVM Crash When Specifying Chinese Language. . . . . . . . . . . . . . . . . . . . . . 116Installer Returns Error "No Filesystem Could Mount Root" on Red Hat. . . . . . . . . . . . . . . . . . . . 116

12.2 Installer Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Installer Reports gzip File Not Found. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Installer Stops Responding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

12.3 Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118


Content

12.4 Do Not Install SAP IQ into the Same Directory as Other Products. . . . . . . . . . . . . . . . . . . . . . . . . . 119

12.5 Client Suite Installation Finishes, but with Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

12.6 Database Upgrade Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

12.7 Incorrect CPU Count on AIX Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

12.8 Installing New System Tables Requires ALTER DATABASE UPGRADE PROCEDURE ON. . . . . . . . . . 122

13 Uninstalling SAP IQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12313.1 Uninstalling SAP IQ Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Using GUI Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Using Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Using Unattended (Silent) Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

14 Upgrade to SAP IQ 16.1 SP 02. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12514.1 Supported Upgrade Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

14.2 SAP IQ 16.x Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Update SySAM License Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Initial Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Database Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Point-in-Time Recovery Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

14.3 SAP IQ 15.4.x Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Update SySAM License Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131

Initial Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132

Database Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Database Status Post Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

System Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137

Logical Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142

Role-Based Security Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

14.4 SAP IQ Database Administration Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

14.5 SAP IQ 12.7 Upgrade and Database Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Preparing to Migrate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190

Migration Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Migration Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198

Unloading Legacy Schemas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Migrating Legacy Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Postmigration Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223

14.6 Hardware Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Moving 32-Bit Databases to 64-bit Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Converting to a New Hardware Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228

SAP IQ Installation and Update Guide [IBM AIX]Content P U B L I C 5

1 SAP IQ Installation and Update Guide [IBM AIX]

Installation and configuration procedures for IBM AIX platforms.


SAP IQ Installation and Update Guide [IBM AIX]

2 Installation Overview

In this section:

You are Here in the Implementation Process [page 7]This guide assumes the evaluator/purchaser has already planned and sized the hardware for your SAP IQ implementation.

Who Should Read this Document? [page 9]This installation guide is intended for three SAP IQ audiences with different skill sets and knowledge: the evaluator/purchaser, the installer, and the network administrator.

What is SAP IQ? [page 9]SAP IQ is a highly optimized analytics server designed specifically to deliver superior performance for mission-critical business intelligence, analytics and data warehousing solutions.

By the End of this Document, I Should be Able to... [page 9]When you complete this document, you will have an initial installation ready to provision with your production data and settings.

2.1 You are Here in the Implementation Process

This guide assumes the evaluator/purchaser has already planned and sized the hardware for your SAP IQ implementation.

There are four stages to the implementation process:

SAP IQ Installation and Update Guide [IBM AIX]Installation Overview P U B L I C 7

Size Your Hardware

Set up your hardware. The SAP IQ Hardware Sizing Guide provides important hardware sizing information for all supported platforms. Sizing guidelines include:

● CPUs, cores, and processors● Memory● Storage● Network● Page sizes● Threads

See the SAP IQ Hardware Sizing Guide on the SAP Community Network .

Create Production System

Create and manage your production database. Create and manage users.

See SAP IQ Administration: Database.

Tune Production System

Tune your production database for optimal performance.

See the SAP IQ Performance and Tuning Guide.

Related Information

Where this Guide Resides in the Information Landscape [page 11]


Installation Overview

http://help.sap.com/disclaimer?site=http%3A%2F%2Fscn.sap.com%2Fdocs%2FDOC-41455

http://help.sap.com/disclaimer?site=http%3A%2F%2Fscn.sap.com%2Fcommunity%2Fiq

2.2 Who Should Read this Document?

This installation guide is intended for three SAP IQ audiences with different skill sets and knowledge: the evaluator/purchaser, the installer, and the network administrator.

Audience Description

Evaluator/purchaser The individual who makes the purchasing decision and determines the scale of the implementation, including simplex versus multiplex, the licensing model, and which licensable options to include.

The installation workflow in this guide assumes the purchaser/evaluator has already made these decisions.

Installer The individual who installs and configures SAP IQ server and client.

The installer might be the network administrator, or it might be someone without network administration privileges and training.

Network Administrator The individual responsible for hardware and OS setup.

If a task in this guide is not intended for all audiences, the task will state which audience the task applies to.

2.3 What is SAP IQ?

SAP IQ is a highly optimized analytics server designed specifically to deliver superior performance for mission-critical business intelligence, analytics and data warehousing solutions.

To learn more about SAP IQ, see Introduction to SAP IQ.

2.4 By the End of this Document, I Should be Able to...

When you complete this document, you will have an initial installation ready to provision with your production data and settings.

When you've finished this document, you'll have:

● A licensed and installed SAP IQ server● A licensed and installed SAP IQ client● A running initial database for testing your installation● A running Interactive SQL session

SAP IQ Installation and Update Guide [IBM AIX]Installation Overview P U B L I C 9

● A running SAP IQ Cockpit instance● Basic configuration settings

You are then ready to create your production environment.

See What's Next? [page 114] and You are Here in the Implementation Process [page 7].

Related Information

You are Here in the Implementation Process [page 7]What's Next? [page 114]


Installation Overview

3 Learn What's New and Changed

Locate information on what's new and changed in this release, locate sizing information, and find answers to commonly asked questions.

In this section:

What's New in this Release? [page 11]See What's New in SAP IQ 16.1 on the SAP Help Portal for information on what's new, changed, and removed in the latest SAP IQ 16.1 Support Package, and previous Support Packages.

Where this Guide Resides in the Information Landscape [page 11]Supporting documentation resources can help you with installation and configuration. Learn how this guide relates to other commonly-used SAP IQ documentation resources.

Where do I Find Help? [page 12]Find SAP IQ help on the SAP Help Portal, and on the Support Portal.

3.1 What's New in this Release?

See What's New in SAP IQ 16.1 on the SAP Help Portal for information on what's new, changed, and removed in the latest SAP IQ 16.1 Support Package, and previous Support Packages.

3.2 Where this Guide Resides in the Information Landscape

Supporting documentation resources can help you with installation and configuration. Learn how this guide relates to other commonly-used SAP IQ documentation resources.

When installing or upgrading SAP IQ, you'll need to refer to other documents to understand important changes in the software, learn how to create a productive database, and learn how to add users to your system. These documentation resources help you become productive as quickly as possible:

SAP Notes

Latest known issues for this release. Access the central SAP Note for this release of SAP IQ from the What's New section on the SAP Help Portal.

SAP IQ Installation and Update Guide [IBM AIX]Learn What's New and Changed P U B L I C 11

https://help.sap.com/viewer/p/SAP_IQ

What's New in SAP IQ 16.1 (SP 01 to SP 02)

Information on what's new, changed, and removed in the latest SAP IQ 16.1 Support Package, and all previous Support Packages. See What's New in SAP IQ 16.1 (SP 01 to SP 02).

SySAM Users Guide

Additional information about the SySAM product licensing and asset management system used by SAP IQ. The guide contains instructions for establishing and administering SySAM licenses. See the SySAM Users Guide.

Getting Started With SAP IQ

The Getting Started With SAP IQ guide assumes you've completed the tasks in this installation guide and have a licensed and working SAP IQ installation. Use Getting Started With SAP IQ to create your production database.

SAP IQ Administration: User Management and Security

Add users to your system and implement role-based security.

SAP IQ Cockpit

Without access to the SAP IQ Cockpit, you cannot use the Create Database wizard to create your initial server. See SAP IQ Cockpit.

3.3 Where do I Find Help?

Find SAP IQ help on the SAP Help Portal, and on the Support Portal.

See product documentation on the SAP Help Portal – online documentation you access using a standard Web browser. You can browse documents online or download them as PDFs. There are links to SAP IQ videos, and links to the SAP Community Network.

For technical support, visit the Support Portal . From the Support Portal, you can report an incident for technical assistance, or contact the Support team for non-technical assistance.


Learn What's New and Changed

https://help.sap.com/viewer/a1062dd5326f43528bbee3a94cf36d28/2.4.0.0/en-US

https://help.sap.com/viewer/p/SAP_IQ

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fcontactus

4 Supported Server and Client Operating Systems

SAP IQ is compatible with several platforms and operating systems.

Supported Server Operating Systems

For supported operating systems for SAP IQ 16.1 SP 02 server, see SAP Note 2479579 .

Supported Client Operating Systems

The SAP IQ client is required to access your SAP IQ server from a remote computer such as your desktop.

For supported operating systems for SAP IQ 16.1 SP 02 network client versions, see SAP Note 2479579 .

SAP IQ Installation and Update Guide [IBM AIX]Supported Server and Client Operating Systems P U B L I C 13

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/SAP Note 2479579

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/SAP Note 2479579

5 Plan the Installation

Before you install, you need to choose the type of installation and the components to install. You should also consider options for database storage, component licensing, and network configuration.

In this section:

Installation Types [page 14]Decide which installation type you need. You can install SAP IQ as a server or install only the software components that allow client connections to an SAP IQ server.

Product Components [page 16]Choose the components to install based on how you plan to use SAP IQ.

License Requirements [page 20]SAP IQ requires a product license for each product edition except the Evaluation Edition. You also need separate licenses for any optional features available for your edition.

Storage Options [page 36]Consider the storage options for your database system before installation.

Network Options [page 38]Do you plan to take advantage of SAP IQ distributed query processing? Distributed query processing can benefit from an optional high-speed interconnect. Use scalable interconnect technology to connect multiplex nodes.

Product Compatibilities [page 38]Information about the compatibility of SAP IQ with other products.

Planning Checklist [page 39]As you plan your installation, record your decisions on the planning checklist. Refer to the checklist when you respond to installation prompts.

5.1 Installation Types

Decide which installation type you need. You can install SAP IQ as a server or install only the software components that allow client connections to an SAP IQ server.

To install SAP IQ server components and administration tools, install SAP IQ Server Suite. To install the components required for client connections to an SAP IQ, install the SAP IQ Client Suite. Record your choice in the planning checklist for future reference.

You can also choose to install certain components from either installation type. See Typical or Custom Installation? [page 17]

In this section:

Do I Need the SAP IQ Client? [page 15]


Plan the Installation

If you develop applications to access data on an SAP IQ server, and your client application resides on a different platform from the SAP IQ server, you must install the appropriate SAP IQ client.

Virtualized Environments [page 16]SAP IQ is supported on virtualization engines, such as VMWare vSphere, with some restrictions.

Related Information

Served License Deployment Model [page 23]Administration Tools [page 19]Typical or Custom Installation? [page 17]SAP IQ Server Components [page 17]SAP IQ Client Components [page 19]

5.1.1 Do I Need the SAP IQ Client?

If you develop applications to access data on an SAP IQ server, and your client application resides on a different platform from the SAP IQ server, you must install the appropriate SAP IQ client.

Basically, you need an SAP IQ client installed on each machine where client applications reside. When installed on the SAP IQ server, the SAP IQ server can access SAP IQ on a remote server. For the contents of the SAP IQ Client Suite, see SAP IQ Client Components [page 19].

These examples will help you choose the right client products for your hardware and O/S platform.

If you are ... You need ... For example ...

Developing applications on one platform to access SAP IQ server on another platform.

An SAP IQ client on each platform where the client applications reside.

If you develop client applications on the Windows platform to access data in an SAP IQ server on Linux, install:

● SAP IQ client on Windows

Running queries against remote data sources. Queries may combine data from two SAP IQ databases on different platforms.

An SAP IQ client on the platform where you will run queries. In this case, you might install an SAP IQ server and an SAP IQ client on the same machine. Remote data accessed through the client will be queried as a proxy table.

If you plan to run queries on your Linux server but access data stored on both the Linux server and an HP server, install:

● SAP IQ client on Linux

Developing a web client application. An SAP IQ client on the application server's machine, not the machine where the browser runs.

If you have a web client application on HP, that queries the server on Linux, but you run the app through a browser on a Windows system, install:

● SAP IQ client on HP

SAP IQ Installation and Update Guide [IBM AIX]Plan the Installation P U B L I C 15

5.1.2 Virtualized Environments

SAP IQ is supported on virtualization engines, such as VMWare vSphere, with some restrictions.

● The virtual machine environments must be officially certified and approved by the corresponding operating system platform vendor.

● The operating system running in the virtual machine is already officially certified by SAP for SAP IQ. If an issue cannot be reproduced, then the customer may be asked to reproduce the problem running natively on the certified operating system, without the use of such virtualization systems.

● The extent of support does not cover performance. SAP does not guarantee the performance of SAP IQ products running on virtual machines.

SAP IQ licenses are valid for both physical and virtual environments.

SAP IQ uses SySAM for licensing and supports its sub-capacity licensing feature. See the SySAM Users Guide for more information if you run SAP IQ in a virtualized environment.

5.2 Product Components

Choose the components to install based on how you plan to use SAP IQ.

To create a custom server or client installation, just deselect any default components that you don't want, and add those optional components that you need. See Typical or Custom Installation? [page 17].

In this section:

Typical or Custom Installation? [page 17]A typical SAP IQ installation includes all of the software components that you need, but you may add optional components or remove components to create a custom installation.

SAP IQ Server Components [page 17]The SAP IQ Server Suite groups components by feature. A typical installation installs those components marked as default. Components not marked as default are options that you may add to a custom installation.

SAP IQ Client Components [page 19]Client components are grouped by feature. Items marked as default are installed in a typical installation. Optional items can be installed in a custom installation.

Administration Tools [page 19]SAP IQ database administration tools include SAP IQ Cockpit 4.0, a Web-based interface.




5.2.1 Typical or Custom Installation?

A typical SAP IQ installation includes all of the software components that you need, but you may add optional components or remove components to create a custom installation.

For example, if you have numerous servers licensed for SAP products that require SySAM licensing, you might want to install the SySAM License Server to manage all of the licenses across your system. You must use an SAP IQ custom installation to install the SySAM License Server, which is an optional component.

SAP IQ Server Components [page 17] and SAP IQ Client Components [page 19] describe all of the default and optional components. See Served License Deployment Model [page 23] for more information about this component.

5.2.2 SAP IQ Server Components

The SAP IQ Server Suite groups components by feature. A typical installation installs those components marked as default. Components not marked as default are options that you may add to a custom installation.

SAP IQ

Installs a high performance relational database management system and data analytics tools.

Components Default Description

SAP IQ Server X Installs server software and additional Connectivity Language Modules to support character sets for Eastern Europe, Turkey, and Greece.

SAP IQ Client X Installs graphical and command-line utilities used to connect to an SAP IQ Server.

SAP IQ Web Drivers X Drivers for Perl, Python and Ruby used to connect to SAP IQ databases from web-based or standalone applications.

SAP IQ ODBC Driver X Installs drivers for the Open Database Connectivity standard, used to connect to SAP IQ databases from ODBC-aware applications, client tools, ODBC drivers, and Web application development tools.

SAP Control Center

Installs the framework in which SAP products can install components for managing and monitoring SAP resources. (Replaced by SAP IQ Cockpit)



Management User Interface for SAP IQ SAP Control Center (SCC) is a Web-based administrative console for Sybase products. At least one SCC server is required to deploy SAP Control Center.

Remote Command and Control Agent for SAP IQ

Provides Web-based management and monitoring tools. SAP Control Center Agent is required to manage SAP IQ servers within SAP Control Center.

Cockpit Framework

Installs the framework in which SAP products can install components for managing and monitoring SAP resources. (Replaces SAP Control Center)


SAP IQ Cockpit X SAP IQ Cockpit is a personalized work center for SAP IQ, which provides SAP IQ SP 02 management capabilities in a graphical environment.

SAP jConnect


SAP jConnect for JDBC X SAP jConnect is a Type 4 JDBC driver, which is entirely Java-based. SAP jConnect is JDBC 4.0 compliant.

SySAM


SySAM License Server Installs FLEXnet Licensing utilities to support your licensing model. The SySAM License Server provides the ability to create a central license server from which multiple installed SAP products can retrieve licenses.

SySAM License Utilities X The SySAM License Utilities are a set of programs that provide license administration, reporting and diagnostic information. It is recommended that these utilities be installed on every machine that an SAP product is installed on.



5.2.3 SAP IQ Client Components

Client components are grouped by feature. Items marked as default are installed in a typical installation. Optional items can be installed in a custom installation.

SAP IQ

Installs graphical and command-line utilities used to connect to an SAP IQ Server, Web application development tools, and ODBC drivers.

Components Default Notes

SAP IQ Client X Installs graphical and command-line utilities used to connect to an SAP IQ Server.

SAP IQ Web Drivers X Drivers for Perl, Python and Ruby used to connect to SAP IQ databases from web-based or standalone applications.

SAP IQ ODBC Driver X Installs drivers for the Open Database Connectivity standard, used to connect to SAP IQ databases from ODBC-aware applications, client tools, ODBC drivers, and Web application development tools.

SAP jConnect

Components Default Notes

SAP jConnect for JDBC X SAP jConnect is a Type 4 JDBC driver, which is entirely Java-based. SAP jConnect is JDBC 4.0 compliant.

NoteDrivers for PHP are not included in SAP IQ installation package. See http://php.net for more information.

5.2.4 Administration Tools

SAP IQ database administration tools include SAP IQ Cockpit 4.0, a Web-based interface.

SAP IQ Cockpit provides a view specific to SAP IQ and full access to all its features.

See SAP IQ Cockpit for more details.


http://help.sap.com/disclaimer?site=http://php.net

5.3 License Requirements

SAP IQ requires a product license for each product edition except the Evaluation Edition. You also need separate licenses for any optional features available for your edition.

Read this section to decide:

● What licenses you need.● Whether you want to manage and distribute licenses from a network license server.

You can manage licenses using the network license server (served licenses), or manage licenses individually yourself (unserved licenses). See License Deployment [page 22].

Whether you install a licensed or evaluation edition, you have 90-day access to all features and options. To use an option beyond the 90-day evaluation period, you must purchase and install an appropriate license. The SySAM licensing mechanism lets your system administrator enable and monitor the site's use of SAP products.

Because using an unlicensed option on a licensed server can cause the server to shut down when the initial grace period expires, the DBA must explicitly authorize access to an optionally licensed feature. SAP IQ will not try to check out an optional license by default. Unless the DBA grants access to an option, the option is unavailable.

NoteSAP IQ periodically checks the number of processors it can use and attempts to check out additional licenses for any increase. SAP IQ shuts down after 90 days if additional licenses are not made available within this period.

When you purchase an SAP product, you receive an e-mail message that tells you how to generate SAP IQ license keys on the Web. The e-mail message also provides specific product and licensing information. Use this information when you generate your licenses.

After installation, you can view and change the license management configuration and enable or disable optional licenses. See Verify and Authorize Optional Licensed Components [page 102] for information about authorizing optional features and other issues related to license management configuration.

NoteIf SAP IQ was licensed using a per-processor license type in previous releases, the license quantity was determined at startup. In this release, SAP IQ periodically checks for the number of processors it can use and attempts to check out additional licenses for any increase. SAP IQ shuts down after 90 days, if additional licenses are not made available within this period. See the SySAM 2 Users Guide for details regarding license grace.

In this section:

Evaluation Edition [page 21]The Evaluation Edition does not require a license. The Evaluation Edition is an unlicensed server, which provides full access to all features and options available in the Enterprise Edition. To run an unlicensed database beyond a 30-day evaluation period, however, you must purchase and install an appropriate license.



Enterprise Edition and Licensed Options [page 21]SAP IQ Enterprise Edition requires a CPU license and supports several licensing options.

License Deployment [page 22]Before you generate a license for SAP IQ, determine the license deployment model.

Before You Generate Licenses [page 31]Have the necessary information available before generating licenses.

5.3.1 Evaluation Edition

The Evaluation Edition does not require a license. The Evaluation Edition is an unlicensed server, which provides full access to all features and options available in the Enterprise Edition. To run an unlicensed database beyond a 30-day evaluation period, however, you must purchase and install an appropriate license.

5.3.2 Enterprise Edition and Licensed Options

SAP IQ Enterprise Edition requires a CPU license and supports several licensing options.

Orderable License Actual License Description

CPU IQ_CORE Restricts the number of cores (not CPUs) that a server can use.

VLDB MO IQ_VLDBMGMT Allows you to create multiple tablespaces and additional dbspaces beyond the defaults:

● You are allowed one IQ_SYSTEM_TEMP dbspace, one IQ_SYSTEM_MAIN dbspace, one IQ_SHARED_TEMP, and one additional user defined main store dbspace.

● Additional dbspaces require the IQ_VLDBMGMT license, which restricts the ability to create table partitions. An IQ_VLDBMGMT is required whenever an SAP IQ server creates or starts with two or more IQ user dbspaces.

Each VLDB license allows for 1 TB of storage. You will need to purchase one license for each additional TB of storage in the main store.

If you are not licensed for the IQ_VLDBMGMT option, SAP IQ returns a No such feature exists error when you try to create more than one table partition or user dbspace.

ASO IQ_SECURITY Allows you to use column encryption, ECC Kerberos and FIPS. The number of ASO licenses must match the number of cores.

MPXO IQ_MPXNODE Allows you to start secondary multiplex nodes (readers/writers). The number of nodes must always be less than the number of cores, as each multiplex server must have at least one core.


Orderable License Actual License Description

IDBA-PSO IQ_UDF Allows you to define and run high-performance scalar and aggregate user-defined functions.

This license is only available with approved third-party libraries.

IQ_IDA Allows you to build, deploy and run your own C/C++ V4 User-Defined Functions (UDF).

The IQ_IDA license will function as both the InDatabase Analytics Option and Partner Solutions license.

UDA IQ_UDA Allows you to use the IQ Text Search functionality, which lets SAP IQ search unstructured and semi-structured data. An IQ_UDA also includes an IQ_LOB license. This license applies to TEXT indexes.

5.3.3 License Deployment

Before you generate a license for SAP IQ, determine the license deployment model.

● The served license model – licenses are deployed to one or more SySAM license servers. Using a license server simplifies and centralizes license administration if you run SAP IQ on several machines, as doing so provides more control over software assets.

● The unserved license model – you generate and download a separate license for each machine where the SAP IQ server runs.

In this section:

Served License Deployment Model [page 23]The license server is a lightweight application that serves licenses to products running on any operating system.

Unserved License Deployment Model [page 23]Under an unserved model, licenses are installed locally and always available.

Comparing the License Deployment Models [page 23]Compare the characteristics between the served and unserved license models to determine which setup works best for your environment.

Using SAP IQ when the License Server is Offline [page 24]Even when a SySAM-enabled product is disconnected from its license server, SySAM allows you to borrow licenses for your product to work offline.

How SySAM Checks Out Licenses [page 24]SAP SySAM related products check out licenses on start-up, and perform periodic heartbeat checks to verify that licenses remain available. If a license is unavailable, the product determines whether it can be awarded a grace period.

Common License Deployment Scenarios [page 25]



Learn about some typical license server deployment scenarios and suggestions for a SySAM setup that best serves each scenario. You can mix and match the suggested configurations with other variations, to best suit your needs.

5.3.3.1 Served License Deployment Model

The license server is a lightweight application that serves licenses to products running on any operating system.

When you choose the served license deployment model, licenses are deployed to one or more SySAM license servers.

A license server can run on a low-end machine or a machine with spare cycles. For example, a license server running on a Solaris UltraSparc-60 serving 100 different licenses to 200 product instances, may use 50 MB of memory, 5 minutes of CPU time per week, and 100 MB of disk space per year.

After you install the required license servers and generate served licenses, install your products. You can configure the products to obtain licenses from one or more license servers.

NoteYou cannot start the license server until there is at least one served license saved to the licenses directory on the license server host machine.

5.3.3.2 Unserved License Deployment Model

Under an unserved model, licenses are installed locally and always available.

Obtain licenses and save them individually on the machines where SAP IQ will run. You will be responsible for updating licenses when required.

5.3.3.3 Comparing the License Deployment Models

Compare the characteristics between the served and unserved license models to determine which setup works best for your environment.

Unserved Served

Licenses are used only on the machine for which the license was generated.

Licenses can be distributed from a network license server to SAP IQ servers running on any machine within the network.

Obtain licenses and save them individually on the machines where SAP IQ will run.

Obtain licenses and save all of them on the license server host machine.


Unserved Served

When new licenses are required for SAP IQ updates, you update and deploy each license for each machine where the SAP IQ update will run.

When new licenses are required for SAP IQ updates, you update all licenses for a specific license server in a single step.

Licenses are installed locally and always available. Requires a functioning license server and network. If either of these fails, you install an alternate license server or fix the problem before the SAP IQ grace period expires.

If a machine where SAP IQ is running fails, you regenerate all of its licenses and deploy those licenses to the replacement machine.

If a machine where SAP IQ is running fails, you move the product to a new machine, where it acquires licenses from the running license server.

If the license server host machine fails, the Manage License Hosts functionality at SMP or SPDC allows you to move its licenses to a new network license server host.

License files are distributed across each machine running SAP IQ, and therefore are difficult to manage and control.

License files are centrally located and managed.

Unserved Standalone Seat (SS) licenses do not allow you to use SAP IQ via Remote Desktop Connection or other terminal services clients.

You can use SAP IQ via Remote Desktop Connection or other Terminal Services clients, irrespective of the type of license in use.

5.3.3.4 Using SAP IQ when the License Server is Offline

Even when a SySAM-enabled product is disconnected from its license server, SySAM allows you to borrow licenses for your product to work offline.

You can use the licensed product offline until the borrowed licenses expire.

When borrowed licenses expire, you reconnect to the network license server and borrow them again for the product to work offline. If you do not reborrow licenses before your currently borrowed licenses expire, the product runs only for a runtime grace period, then ceases to function.

NoteTypically, the maximum duration for which you can borrow a license is 90 days.

5.3.3.5 How SySAM Checks Out Licenses

SAP SySAM related products check out licenses on start-up, and perform periodic heartbeat checks to verify that licenses remain available. If a license is unavailable, the product determines whether it can be awarded a grace period.

The grace period starts from the time a license was last in use and persists for 90 days. At the end of the grace period, the product performs an orderly shutdown, if running, or fails to start up. If the license (or a



replacement license) becomes available, the cycle continues with the heartbeat, noting the last use of the license.

In this section:

Three-License-Server Redundancy [page 25]Tolerance for temporary licensing failure is usually sufficient. However, in certain circumstances, you may choose to use “three-license-server redundancy.”

5.3.3.5.1 Three-License-Server Redundancy

Tolerance for temporary licensing failure is usually sufficient. However, in certain circumstances, you may choose to use “three-license-server redundancy.”

For example:

● A grace period is not provided for the license type Floating License (FL).● Standby copy systems rarely qualify for a grace period because they are unlikely to have been used within

the last 90 days.● Company policy dictates the use of redundancy.

For three-license-server redundancy, use three machines that each:

● Run the same version of the SySAM license server.● Have good intermachine communication.● Use a separate copy of the same license files.

A product using per-processor licensing checks out a license quantity equal to the number of processors it can use. If there are not enough licenses, it applies a runtime grace period. A runtime grace period is also applied if the number of processors increases and the product is unable to check out additional licenses. The product shuts down if additional licenses are not made available within the runtime grace period. Decreasing the available number of processors while it is running does not reduce the required license quantity. You must restart the product on the correct number of processors.

5.3.3.6 Common License Deployment Scenarios

Learn about some typical license server deployment scenarios and suggestions for a SySAM setup that best serves each scenario. You can mix and match the suggested configurations with other variations, to best suit your needs.

In this section:

Small Environment, Unserved Licenses [page 26]The easiest setup for this environment is to use unserved licenses, which have a simple initial setup and require little, if any, ongoing monitoring.

Single Site with Multiple Products, Served Licenses [page 27]This deployment scenario assumes you have one site, running multiple products, that requires asset management capabilities.


Multiple Sites with Security Considerations and Remote Users [page 29]This deployment scenario has multiple sites, each with multiple SAP products, with a license server at each site. This removes the dependency on network availability and latency, and can provide load balancing.

5.3.3.6.1 Small Environment, Unserved Licenses

The easiest setup for this environment is to use unserved licenses, which have a simple initial setup and require little, if any, ongoing monitoring.

This deployment scenario uses an unserved license deployment model that works best in:

● Very small environments using only a few license files that require little management. If you have more than 10 hosts, it is probably better to move to a served license deployment model, since a served license allows you to update all licenses in one step.

● Hosts that are isolated (or need to be isolated) from one network to another; for example, secure networks, and so on.

● Secure environments, where communication between hosts is limited or restricted; for example, all ports are blocked, or specific ports are not allowed to be opened on a host.

● Occasionally connected systems, such as laptops or handheld devices.

Figure 1: Small Unserved License Configuration

The "Small Unserved License Configuration" figure illustrates a simple unserved license architecture with two hosts: ASTRO and ELROY. Each license file is installed locally on the same machine that runs the SySAM 2-



enabled products that use that specific license file. The license is used only on the machine on which it is installed. In each license file representation, the license file HOSTID matches the unique license host identification for the machine on which the associated licensed product is installed.

To get this information, run lmutil hostid from the $SYBASE/SYSAM-2_0/bin directory, on each machine for which you want to determine the host ID.

When you log in to the SPDC or SAP Support Portal to generate licenses, enter the correct host ID for the machine where the product will run.

When using an unserved license, remember that:

● The unserved license is valid only on the machine for which it was generated. The license is node-locked to the host where your SySAM 2-enabled product is installed, and the license activates products only on that host. You cannot copy the license file to another machine and use it to run another instance of a product.

● The unserved license deployment model does not use a license server. When you start a product, it looks for a local license file.

● You must manage unserved licenses, regardless of the architecture in which they are implemented. Most licenses have a version that usually coincides with the end of your annual support agreement with SAP.To download and apply product updates and patches, when you renew your product support, update your SySAM licenses to reflect that fact. Renewing support and updating the corresponding license files on a few hosts is not difficult, but trying to update 100 or 1,000 hosts would be a formidable task.

5.3.3.6.2 Single Site with Multiple Products, Served Licenses

This deployment scenario assumes you have one site, running multiple products, that requires asset management capabilities.

Typically, a served license with one license server that serves all SAP licenses works most efficiently in such an environment. The overhead of maintaining the license server is compensated by the asset management functionality and a reduction in ongoing license maintenance because of the license server.


Figure 2: Single-Site Served License Configuration

The "Single-Site Served License Configuration" figure shows one license server that is set up to grant SySAM licenses to all SAP products in use. Each instance of a product contacts the license server to acquire a license.

You can set up the license server on a separate host machine, but because the license server uses few resources, it can typically be hosted on an existing machine.



5.3.3.6.3 Multiple Sites with Security Considerations and Remote Users

This deployment scenario has multiple sites, each with multiple SAP products, with a license server at each site. This removes the dependency on network availability and latency, and can provide load balancing.

Figure 3: Multiple Sites and License Servers

The "Multiple Sites and License Servers" figure illustrates an organization with major sites in New York, London, and Tokyo. Each site uses multiple instances of multiple SAP products. A license server is installed at each site and individual product instances acquire licenses from the license server at that site.

You can configure the products to find remote license servers if the required license cannot be found on the site license server, or if the site license server is not running. To share a limited number of floating licenses across all sites while using the site license server for other licenses, set up those floating licenses on the license server where floating licenses are likely to be used frequently. At the other sites, you can set up license search paths. The redundancy provided by this configuration is limited to the number of unused licenses, including any overdraft licenses that remain on each license server.

You can also consider alternate configurations. For example, if the network communication between two sites is extremely reliable with minimal latency, you can share a license server between two sites. Smaller remote sites can share a license server with a larger site that provides the most reliable network connection, even though the larger site may not be the closest site geographically.

This setup is an extension to the multiple site case explained above. It also addresses additional considerations including security within your network, remote users, and DMZs. This setup uses a mix of license models and


servers to meet your needs. Individual components of this deployment can be applied to any of the other deployment scenarios.

Figure 4: Complex, Multiple-Site Installations

The "Complex, Multiple-Site Installations" figure depicts a multiple-site deployment with multiple product setup with additional security requirements. In this example:

● The Headquarters network includes both development and production installations.● The production installations are set up within a secure subnet within the network.● The database and application servers that serve the Web are set up in the DMZ.● Home office and mobile users access the software remotely through VPN.● There is a disaster recovery center at a remote location.● There are other secondary sites for the organization.

This example uses a single license server for Headquarters, which serves the development, production, and remote users’ needs. While the license server is shared for development and production needs, available licenses can be demarcated based on intended deployment.

● The production subnet security policies are relaxed to allow connections to the license server host and port.

● The VPN policies allow a connection to license server host and ports.



If your security policies do not permit the production subnet to access a license server outside the subnet, set up a separate license server inside the subnet.

NoteUse a fixed port for the lmgrd license manager and SAP vendor daemon in such situations. Firewall and VPN policies must accommodate both lmgrd and SAP port numbers. This means that SERVER lines and VENDOR lines in all license files must specify the port numbers chosen for the license manager and SAP daemon processes. For example, a license server running on machine server_1 with the lmgrd license manager daemon, listening on port 27001 and the SAP vendor daemon listening on port 27100 should use a license file headed with the following two lines:

SERVER server_1 ANY 27001 VENDOR SAP PORT=27100

Unserved licenses are set up on the DMZ to serve licenses to product instances using the Web. This reduces the need to set up another license server or open up additional traffic through the firewall.

SAP recommends that you use a separate license server for your disaster recovery site. This ensures availability of the license server in case of a major catastrophe at the primary site.

If your disaster recovery setup includes cold-standby servers, set up the license servers in a three-server redundant cluster. This reduces the possibility of a license server being unavailable when a cold-standby server is attempting to come online. Such redundancy for license servers is typically not needed unless you are using cold-standby systems.

Each secondary or remote site can have its own license server.

5.3.4 Before You Generate Licenses

Have the necessary information available before generating licenses.

Required Information or Action

Served License Model

Unserved License Model Description

License deployment model X X Decide whether to use a served or unserved license deployment model. Typically, this is a company-wide decision that is made only once. Therefore, this is one of the most important things to determine before license generation.

Product machine host ID X Determine the host ID of the machine, or machine partition where the product will run.

License server – download and install

X Download the standalone license server software and install the SySAM license server before you generate the product’s licenses, and before you install the product.

License server host ID X Determine the host ID of the machine where the license server will run.

License server host name X Determine the host name of the machine where the license server will run.


Required Information or Action

Served License Model

Unserved License Model Description

License server TCP/IP port numbers

X Determine the port numbers on which the license server will listen for license requests.

In this section:

Determining Host IDs [page 32]Identify the host ID of the machine where the licenses will be deployed.

Access Through a Firewall or VPN [page 34]SySAM license server listens on two TCP/IP ports for incoming license requests. Therefore, firewall or VPN policies require a set-up to allow access to both ports.

License Types [page 35]SAP IQ is sold under different license types that control where you can use it. License types include in production, standby, or development and test environments.

Generating a SySAM License [page 36]Log in to SAP Service Marketplace to generate a license key for SAP IQ. Refer to the email you received for information about your account.

5.3.4.1 Determining Host IDs

Identify the host ID of the machine where the licenses will be deployed.

● For served licenses, specify the host ID of the machine where the license server will run.● For unserved licenses, specify the physical host ID of the machine where the product will run.

If you are running a product with per-CPU or per-CHIP licensing that supports SySAM sub-capacity, and you want to run the product in a virtualized environment, use the sysamcap utility to enter the host ID for the virtual machine, partition, or resource-set.

SPDC or SMP remembers the host information so that you can select the same license server when generating additional licenses.

In this section:

Finding the Host ID for a Physical Machine [page 32]Use the lmutil utility or the appropriate operating system command to find your host ID.

Finding Host IDs for Machines with Multiple Network Adapters [page 34]On some platforms, the host ID is derived from the network adapter address.

5.3.4.1.1 Finding the Host ID for a Physical Machine

Use the lmutil utility or the appropriate operating system command to find your host ID.

The lmutil utility is included in the SySAM license server download.



To determine the host ID of the machine using lmutil, enter:

lmutil lmhostid

Platform Host ID Type Native OS Command

Windows Ethernet Address ipconfig/all(use "Physical Address" value)

Solaris Host ID hostid

Linux Ethernet Address /sbin/ifconfig eth0 (use "HWaddr" value)

MAC OS X Ethernet Address /sbin/ifconfig eth0 (use "ether" value)

Tru-UNIX (Digital) Ethernet Address netstat -i

IBM AIX Host ID uname -m (returns 000276513100), then remove both the first and the last two digits, and use the remaining eight digits

HP-UX PA-RISC Host ID uname -i (convert to hex, or prepend with #)

HP-UX Itanium Machine ID getconf CS_PARTITION_IDENT (prefix with "ID_STRING=")

SGI Host ID /etc/sysinfo -s (convert to hex, or prefix #)

Each host ID type has valid formats that will be checked when generating a license. Make sure the value entered matches these valid formats.

Ethernet addresses are 12 character hex values consisting of digits 0 through 9 and characters A through F. They may be entered in any of the following formats:

● 12AB34CD56EF● 12-AB-34-CD-56-EF● 3.12:AB:34:CD:56:EF

For some platforms, the host ID can also be entered in decimal formats, in this case prefix the host ID with the "#" sign. Example: #1039716963

The Disk Serial Number is always entered with a "DISK_SERIAL_NUM=" prefix. For example: DISK_SERIAL_NUM=3e2e17fd

The machine ID string is always entered with an "ID_STRING=" prefix. For example: ID_STRING=9c766319-db72-d411-af62-0060b05e4c05


5.3.4.1.2 Finding Host IDs for Machines with Multiple Network Adapters

On some platforms, the host ID is derived from the network adapter address.

Context

If the machine where your product is installed or where the license server is hosted has multiple network adapters, running lmutil lmhostid returns one host ID for each network adapter, and returns output similar to this:

The FLEXlm host ID of this machine is ""0013023c8251 0015c507ea90"" Only use ONE from the list of hostids.

It is important that you:

● Choose only one host ID to enter during license generation.● Use the value associated with the primary wired Ethernet adapter.● Do not use values associated with internal loopback or virtual adapters.

If you cannot determine the host ID using the lmutil lmhostid output, use the native operating system commands to get additional details.

5.3.4.2 Access Through a Firewall or VPN

SySAM license server listens on two TCP/IP ports for incoming license requests. Therefore, firewall or VPN policies require a set-up to allow access to both ports.

The SySAM license server consists of two processes: the license manager daemon (lmgrd) and the vendor daemon (SYBASE).

Set the ports by specifying their port numbers in the license files on the SySAM license server. For example, to force lmgrd to listen on port 27010 and the SYBASE vendor daemon to listen on port 27011, the license file header should have:

SERVER keyserver 1D1D1D1D 27010 VENDOR SYBASE PORT=27011

A SySAM enabled product only needs to know the port where lmgrd is listening. The product connects to lmgrd on that port and will then be told which port to use to connect to the SYBASE vendor daemon. This means that the product's local license file just needs to contain the following:

SERVER keyserver ANY 27010 USE_SERVER

When generating licenses at SPDC, specify the license server port to fix the port for lmgrd. Edit the license file to specify the SYBASE vendor daemon port.



When generating licenses at SMP, specify both ports. The port for lmgrd is specified as License Server Port 1, and the SYBASE vendor daemon port as License Server Port 2. For three-server-redundant configurations, you can only specify the SYBASE vendor daemon port for the primary license server; same value is used for the secondary and tertiary license servers.

NoteYou can specify any unused port number between 0 and 64000. On UNIX, choose a port number greater than 1024, as most port numbers less than 1024 are privileged port numbers. Do not specify a number in the range 27000 to 27009 for License Server Port 2, as ports in this range are used by the lmgrd process when no port is specified for License Server Port 1.

5.3.4.3 License Types

SAP IQ is sold under different license types that control where you can use it. License types include in production, standby, or development and test environments.

The license type determines the quantity of licenses required, such as whether a license is required for each machine; or for each CPU, or CPU chip; or per terabyte of storage.

For example, SAP IQ purchased under the CPU License (CP) type requires one license per CPU on the machine, partition, or resource set where it will run. SAP IQ purchased under the Server License (SR) type requires a single license for the machine, partition, or resource set.

Make sure you select the correct license type when you generate your SySAM license file, since your account may have the same product licensed under multiple license types.

When you generate licenses, each license type is presented on the License Information screen, such as:

License Type: CPU License (CP)

In this section:

Optional Feature Licenses [page 35]Some applications are offered as base products with optional features that require an additional separate license.

5.3.4.3.1 Optional Feature Licenses

Some applications are offered as base products with optional features that require an additional separate license.

You can mix license types. For example, you can order SAP IQ under the Server License (SR) license type and order an optional feature (such as IQ_VLDBMGMT) under the CPU License (CP) type.

Optional features are licensed only with the base product of the same product edition. For example, if you order SAP IQ, you cannot use an Evaluation Edition optional feature license with the Enterprise Edition base product. In addition, the entitled use of the license types must be compatible; for example, both types should allow use in a production environment.


5.3.4.4 Generating a SySAM License

Log in to SAP Service Marketplace to generate a license key for SAP IQ. Refer to the email you received for information about your account.

Context

When you purchase SySAM–enabled SAP products, such as SAP IQ, you must generate, download, and deploy product licenses. You will need a license whether you use the served or unserved deployment model.

● To generate your unserved license, you need the host ID and host name of the SAP IQ server.● To generate your served license, you need the host ID and host name of the SySAM license server.● Served licenses require a license server. If you do not plan to use an existing license server, you must install

one before you install SAP IQ.

Procedure

1. Start your browser, and login to the SAP Service Marketplace at: https://support.sap.com/licensekey .2. Follow the online instructions.3. Save your license to a temporary location on the local file system. You must save the license file with

a .lic extension.

5.4 Storage Options

Consider the storage options for your database system before installation.

For SAP IQ dbspaces in production, use a fault-tolerant file system implemented by a high-performance, redundant disk array (for example, RAID 5). For single-server systems, you can use a local file system, but multiplex systems require raw devices, ideally on a Storage Area Network device. Multiple raw disks enable SAP IQ to stripe data across devices, which improves performance.

In this section:

Raw Devices [page 37]On UNIX-like operating systems, you can create a database or dbspace on a raw device or a file system file.

Creating Dbspaces on Multiple Files [page 37]Due to the IBM implementation of reads for JFS database files, SAP IQ performance improves if you create dbspaces on each disk, instead of creating one large file. Smaller files allow SAP IQ to handle disk I/O operations much more efficiently, especially when combined with disk striping and possibly multiple controllers.



http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Flicensekey

Avoiding Environmental Issues [page 37]Installing SAP SQL Anywhere and SAP IQ on different machines avoids potential start-up problems.

5.4.1 Raw Devices

On UNIX-like operating systems, you can create a database or dbspace on a raw device or a file system file.

Disk partitions are typically accessed in two modes: file system mode (for example through the UFS file system) or raw mode. Raw mode does unbuffered I/O, generally making a data transfer to or from the device with every read or write system call. UFS is the default UNIX file system, and is a buffered I/O system, which collects data in a buffer until it can transfer an entire buffer at a time.

You create a database or dbspace on a raw device or a file system file. SAP IQ uses the path name you specify to determine whether the partition is a raw partition or a file system file. Raw partitions can be any size.

When you allocate file system files for dbspaces (System, IQ main, or IQ temporary), do not place the files on a file system that is shared over a local area network. Doing so can lead to poor I/O performance and other problems, including overloading the local area network. Any storage type can be used for SAP IQ so long as it is configured in a way that SAP IQ supports (raw devices on any platform, local file systems for databases on any platform, NFS on Linux, and GPFS on Linux) and follows proper sizing guidelines.

To avoid conflicts, restrict the management of dbspaces to a single database administrator on a single connection.

5.4.2 Creating Dbspaces on Multiple Files

Due to the IBM implementation of reads for JFS database files, SAP IQ performance improves if you create dbspaces on each disk, instead of creating one large file. Smaller files allow SAP IQ to handle disk I/O operations much more efficiently, especially when combined with disk striping and possibly multiple controllers.

The current recommendation is that you create three files per underlying disk drive.

When setting up raw partitions, the system administrator specifies the sector size, which defines the minimum usable chunk of disk (and sets the minimum block size). When you use raw partitions, the integer you specify as a block size must be a multiple of the sector size.

5.4.3 Avoiding Environmental Issues

Installing SAP SQL Anywhere and SAP IQ on different machines avoids potential start-up problems.

Install SAP SQL Anywhere and SAP IQ on different host machines. When you install both products on the same machine, the environment variables for the product installed last overwrite those of the product installed first, causing start-up problems for the first product.


5.5 Network Options

Do you plan to take advantage of SAP IQ distributed query processing? Distributed query processing can benefit from an optional high-speed interconnect. Use scalable interconnect technology to connect multiplex nodes.

For best performance, use:

● A high-speed network interconnect providing a local network that connects all multiplex nodes. Use an interconnect bandwidth of 1 GB or higher or the highest bandwidth, lowest latency interconnect available.

● Two physically separate network interfaces for each multiplex node:○ A public network for multiplex interconnection traffic and client traffic.○ A private network for multiplex interconnect traffic only, excluding external client traffic. Currently,

multiplex interconnects support only the TCP/IP standard.These two networks improve security, fault-tolerance, and performance.

● A switch that enables high-speed communication between nodes.● Network cards that reside on different fabrics so that the multiplex survives network failure. Separate the

public and private networks physically.● Private interconnect fabrics that contain only links to machines participating in the multiplex. Private

interconnect for all multiplex nodes should connect to the same switch, which connects to no other public switches or routers.

● Redundant network interface cards added to private or public networks if desired. The private and public connection information allows for multiple IP addresses on each.

In this section:

Network Clients and ODBC Kits [page 38]Network Clients and ODBC development kits are available on the SAP IQ product support page.

5.5.1 Network Clients and ODBC Kits

Network Clients and ODBC development kits are available on the SAP IQ product support page.

There are no 32-bit ODBC drivers for SAP IQ SAP IQ. Use the SAP IQ 16.0 32-bit ODBC drivers instead.

See the Technical Release Information on the SAP IQ 16.1 Product Support Page .

5.6 Product Compatibilities

Information about the compatibility of SAP IQ with other products.

These SAP products are certified with this version of SAP IQ:

● jConnect for JDBC 8.0

These SAP products are certified to work as back ends in CIS functionality with this version of SAP IQ:



http://help.sap.com/disclaimer?site=https%3A%2F%2Fwebsmp230.sap-ag.de%2Fsap%28bD1lbiZjPTAwMQ%3D%3D%29%2Fsupport%2Fpam%2Fpam.html%3Fsmpsrv%3Dhttps%253A%252F%252Fwebsmp201.sap-ag.de%23pvnr%3D67838200100900005877%26ts%3D0%26pt%3Dg%257Cd

● SAP SQL Anywhere 17.0● SAP Adaptive Server Enterprise (SAP ASE) 16.0

5.7 Planning Checklist

As you plan your installation, record your decisions on the planning checklist. Refer to the checklist when you respond to installation prompts.

Question See Notes

Do you have the SAP administrator user name and password? You need this information to log on to the machine to run the installation.

Create the SAP IQ Account [page 43]

Will you initially install a licensed or evaluation edition?

License Requirements [page 20]

Do you plan to use SySAM license server?

License Deployment [page 22] and SAP IQ Server Components [page 17]

Do you need the SAP IQ Client? Do I Need the SAP IQ Client? [page 15]

Do you plan to use the SAP IQ Cockpit? Administration Tools [page 19]

If installing SAP IQ Cockpit, are the default ports available? If the default ports are in use, identify substitute ports to be specified during the installation.

Check Port Availability for SAP IQ Cockpit [page 41]

Based on your answers above, which installation type should you use?

Typical or Custom Installation? [page 17]

Where do you plan to install the SAP IQ? What is the absolute path to the location?

Storage Options [page 36] and Network Options [page 38]


6 Preinstallation Tasks

Complete these tasks before starting the installation process. These are operating system-level tasks to be completed by the network administrator.

In this section:

Check for Operating System Patches [page 40]Check with your vendor and apply the latest operating system patches. Do not use a patch that is earlier than the version suggested for your operating system.

Increase the Swap Space [page 41]The recommended minimum swap space is 1 GB. Certain operations may cause the memory usage to grow dynamically. Changing the way SAP IQ uses buffers can dramatically change the way it uses memory.

Check Port Availability for SAP IQ Cockpit [page 41]SAP IQ Cockpit uses reserved port numbers.

Verify Network Functionality [page 41]Make sure your network devices can communicate before you install SAP IQ.

Platform-Specific Tasks [page 41]Complete these platform-specific tasks before starting the installation process.

Create the SAP IQ Account [page 43]Create an SAP IQ account to provide consistent ownership and privileges for all installation, upgrade, and administration tasks.

Download Installation Files [page 43]SAP IQ installation and update packages are available on the SAP Software Download Center.

6.1 Check for Operating System Patches

Check with your vendor and apply the latest operating system patches. Do not use a patch that is earlier than the version suggested for your operating system.

See Supported Server and Client Operating Systems [page 13].


Preinstallation Tasks

6.2 Increase the Swap Space

The recommended minimum swap space is 1 GB. Certain operations may cause the memory usage to grow dynamically. Changing the way SAP IQ uses buffers can dramatically change the way it uses memory.

Depending on the load, swap requirements may exceed space allotted. Insufficient swap space may result in the system supporting fewer users, and large processes that cannot acquire sufficient swap space may be prematurely killed by the operating system.

See your operating system documentation for information about extending swap space.

6.3 Check Port Availability for SAP IQ Cockpit

SAP IQ Cockpit uses reserved port numbers.

Before proceeding, if you are planning to install SAP IQ, verify the availability of the following ports . If already in use, identify alternate port numbers to be specified during installation.

● HTTP Port: 4282● HTTPS Port: 4283● RMI Port: 4992● TDS Port: 4998

6.4 Verify Network Functionality

Make sure your network devices can communicate before you install SAP IQ.

SAP IQ uses networking software whenever the client and server components are installed on different systems. Use the ping command to and from another computer to verify that the server where you plan to install SAP IQ can use TCP/IP to communicate with other devices on your network.

6.5 Platform-Specific Tasks

Complete these platform-specific tasks before starting the installation process.

In this section:

Adjust the Shared Memory Allocation [page 42]The -iqsmem switch for shared memory allocation now supports values greater than 512 MB on 64-bit IBM AIX platforms. The maximum supported limit for a single shared memory segment on AIX-64 increased from 256 MB to 32 TB. Adjusting this switch results in a significant performance increase.

SAP IQ Installation and Update Guide [IBM AIX]Preinstallation Tasks P U B L I C 41

Enable the I/O Completion Ports (IOCP) [page 42]AIX I/O Completion Port (IOCP) status may be defined, but not enabled. This problem applies to all AIX platforms and may occur after an install or upgrade.

Increase the Maximum User Processes [page 43]For new installations, the default setting is 40. For a production system, set this value to a minimum of 250. See your operating system documentation for information on setting this parameter.

6.5.1 Adjust the Shared Memory Allocation

The -iqsmem switch for shared memory allocation now supports values greater than 512 MB on 64-bit IBM AIX platforms. The maximum supported limit for a single shared memory segment on AIX-64 increased from 256 MB to 32 TB. Adjusting this switch results in a significant performance increase.

Set the -iqsmem switch to a value, which is exactly equal to the sum of IQ_SYSTEM_MAIN (dbname.iq) and IQ_SYSTEM_TEMP (dbname.iqtmp) buffer cache sizes. Do not set this switch to another value.

6.5.2 Enable the I/O Completion Ports (IOCP)

AIX I/O Completion Port (IOCP) status may be defined, but not enabled. This problem applies to all AIX platforms and may occur after an install or upgrade.

Context

Symptoms may include ENOEXEC and Cannot load module messages.

Procedure

1. Log in to the server as root.2. Validate the current IOCP status: "lsdev-Cc iocp"

lsdev returns one of these messages:○ If the message reads iocp0 Defined I/O Completion Ports, continue to the next step.○ If the message readsiocp0 Available I/O Completion Ports, there is no need to continue.

3. Issue the following command: smitty <iocp>.

4. Select Configure Defined I/O Completion Ports.When processing is complete, output should read iocp0 Available.

5. Press F10 to exit.6. Run lsdev -Cc iocp.



Output should read iocp0 Available I/O Completion Ports.

6.5.3 Increase the Maximum User Processes

For new installations, the default setting is 40. For a production system, set this value to a minimum of 250. See your operating system documentation for information on setting this parameter.

6.6 Create the SAP IQ Account

Create an SAP IQ account to provide consistent ownership and privileges for all installation, upgrade, and administration tasks.

Create the SAP IQ user on every machine you plan to install SAP IQ server, SAP IQ client, or the SySAM license server on. The SAP IQ user can be a normal nonadministration user and does not require root access. Log in to machines as this user to install or administer SAP IQ.

If you have already installed other SAP software, the SAP IQ user may already exist. If so, verify that you can log in to the machine using this account. If there is no SAP IQ account on your system, see your operating system documentation for instructions for creating new user accounts.

6.7 Download Installation Files

SAP IQ installation and update packages are available on the SAP Software Download Center.

Context

To access the SAP IQ installation files, on the SAP Software Download Center , select Software Downloads.

Procedure

1. Select SUPPORT PACKAGES & PATCHES By Alphabetical Index (A-Z) I SYBASE IQ SYBASE IQ 16.1

2. Choose the component to download.3. Choose the operating system from the dropdown list, if applicable.4. Choose the patch level to download.

SAP IQ Installation and Update Guide [IBM AIX]Preinstallation Tasks P U B L I C 43

http://help.sap.com/disclaimer?site=https%3A%2F%2Flaunchpad.support.sap.com%2F%23%2Fsoftwarecenter

5. Click the Shopping Cart icon to add the selected components to the download basket.6. Click Download Basket and complete the download.

Next Steps

Uncompress the download image on the same machine where you plan to install SAP IQ. Do not copy an uncompressed installation archive to a secondary machine to perform the installation.

Each archive contains a single folder with the installation files. Rename these folders to make them easier to identify. For example, rename the folder with SAP IQ server installation files to server.

Once unpacked and renamed, verify that the SAP IQ account has full privileges (read, write, execute) to all archive folders. Modify privileges as needed. Missing privileges on any of the folders may result in an incomplete installation.



7 Installing SySAM License Server

The SAP IQ Server Suite installation media includes the SySAM license server.

The SySAM license server is required for a served license deployment model.

In this section:

Installing SySAM in GUI Mode [page 46]Use this option to install the SySAM license server using a graphical user interface (GUI). The GUI installer is wizard-driven and supports all product editions and installation types.

Installing SySAM in Console Mode [page 47]Choose a console installation if you prefer a non-GUI interface. Installing SySAM License Manger in console mode is similar to installing in GUI mode, except that you run the installer from the command line, and enter text to select the installation options.

Starting and Stopping a SYSAM License Server [page 48]You start and stop the license server from a console or command line.

Apply or Update Licenses on the SySAM License Server [page 49]Copy your served licenses to the license directory on the SySAM license server, and update the license server.

Understanding the SySAM Directory Structure [page 50]SySAM files are installed in the SYSAM-2_0 directory.

SySAM Utilities [page 50]The licensing utility program, lmutil, includes options for managing licensing activities.

Related Information

Download Installation Files [page 43]Unserved License Deployment Model [page 23]SySAM Users Guide

SAP IQ Installation and Update Guide [IBM AIX]Installing SySAM License Server P U B L I C 45


7.1 Installing SySAM in GUI Mode

Use this option to install the SySAM license server using a graphical user interface (GUI). The GUI installer is wizard-driven and supports all product editions and installation types.

Prerequisites

● The SAP IQ package has been downloaded and unpacked.● You are logged on as the SAP IQ user account.

Procedure

1. Change to the setup directory where you downloaded and unpacked your SAP IQ software.2. Start the installer:

Type ./setup.bin and follow the instructions on the screen.

3. When prompted, specify a parent install directory. Do not install SySAM license server into a destination directory or path that contains spaces. The GUI installer warns you if you try to install to an invalid path or if the parent install directory or path has changed since the last installation on the machine and you are about to replace the existing environment variables. If installing the SySAM license server and SAP IQ server on the same machine, do not install to a common parent directory.

4. Select Custom as the installation type. Deselect all selected options. Select SySAM License Server only.5. Select Evaluate for the license type.6. Complete and accept the terms of the licensing agreement.7. Review the installation summary and make adjustments as needed.8. Begin the installation.

Next Steps

You next task is to Apply or Update Licenses on the SySAM License Server [page 49].

Related Information

Create the SAP IQ Account [page 43]Download Installation Files [page 43]


Installing SySAM License Server

7.2 Installing SySAM in Console Mode

Choose a console installation if you prefer a non-GUI interface. Installing SySAM License Manger in console mode is similar to installing in GUI mode, except that you run the installer from the command line, and enter text to select the installation options.

Prerequisites


Context

NoteAt any time, from within the console installer, to return to the previous prompt, type back.

Procedure

1. From a console, change to the setup directory where you unpacked your software.2. Start the installer:

./setup.bin -i console

and follow the instructions on the screen.3. When prompted, specify a parent install directory. Do not install SySAM license server into a destination

directory or path that contains spaces. The console installer does not warns you if you try to install to an invalid path or if the parent install directory or path has changed since the last installation on the machine and you are about to replace the existing environment variables. If installing the SySAM license server and SAP IQ server on the same machine, do not install to a common parent directory.

4. Select Custom as the installation type. 5. Type 1,7,10,12 to deselect all selected options, and then type 11 to select SySAM License Server only.

6. Select Evaluate for the license type.7. Complete and accept the terms of the licensing agreement.8. Review the installation summary and make adjustments as needed.9. Begin the installation.


Next Steps

You next task is to Apply or Update Licenses on the SySAM License Server [page 49].

Related Information

Create the SAP IQ Account [page 43]Download Installation Files [page 43]SySAM Users Guide

7.3 Starting and Stopping a SYSAM License Server

You start and stop the license server from a console or command line.

Prerequisites

● At least one license file (.lic) exists in the licenses directory.

Procedure

1. Change to the <sysam_installation_dir>/SYSAM-2_0/bin directory.

2. Start or stop the license server:

Action Syntax

Start the license server ./sysam start

Stop the license server ./sysam stop

3. To verify that the license server is running, enter sysam status.

NoteThe SySAM License Server Installer installs both IPv4-only and IPv4/IPv6 dual-stack license server binaries during installation and configures use of IPv4-only binaries.

Use the sysam configure [IPv6 | IPv4] to configure the appropriate version of the license server. For example, sysam configure IPv6 will configure use of the IPv4/IPv6 dual stack binaries. For more information, see the SySAM Users Guide published with SAP IQ documentation.




Related Information

SySAM Users Guide

7.4 Apply or Update Licenses on the SySAM License Server

Copy your served licenses to the license directory on the SySAM license server, and update the license server.

Procedure

1. Navigate to the <sysam_installation_direcory>/SYSAM-2_0/licenses folder.

CautionThe SySAM license server and the SAP IQ server both have a SYSAM-2_0/licenses subfolder structure. If you installed both servers on the same machine, be sure to navigate to the SYSAM-2_0/licenses folder of the SySAM license server, not of the SAP IQ server.

2. Delete the temporary license file SySAMLicenseServer.lic.

3. Copy the served licenses to the folder.4. Change to the <sysam_installation_direcory>/SYSAM-2_0/bin directory.

5. Type: ./sysam reread

NoteStopping and starting the SySAM license server also forces the server to update the licenses.

Related Information

SySAM Users Guide




7.5 Understanding the SySAM Directory Structure

SySAM files are installed in the SYSAM-2_0 directory.

The SYSAM-2_0 directory contains these default subdirectories and files:

bin● sysam – wrapper script to manage the license server● lmgrd – license server manager daemon● SYBASE – vendor daemon● lmutil – licensing Utility program (from Flexera)● lmtools.exe – (Windows only) GUI License Utility program (from Flexera)● installs.exe – (Windows only) program used internally to install the SySAM Windows service that

automatically starts the license server● cpuinfo – utility program that reports the processor counts for the machine, or for the specified

containment level if the SYBASE_SAM_CAPACITY environment variable is set● sysamcap – utility program used to configure sub-capacity licensing

licenses● *.lic – license files● SYBASE.opt – license server options file

locales● unicode – localized message files for the sysamcap and cpuinfo utilities

log● SYBASE.log – license server debug log

7.6 SySAM Utilities

The licensing utility program, lmutil, includes options for managing licensing activities.

The options available in lmutil are:

● lmborrow – supports license borrowing.● lmdiag – diagnoses license checkout problems.● lmdown – shuts down selected license daemons.● lmhostid – reports the system host identifier for the machine on which the command is run.● lminstall – (not supported by SAP) converts license files to different formats.● lmnewlog – moves the existing report log information to a new file name and starts a new report log file

with the existing file name.● lmpath – allows direct control over license file path settings. You should place all license files in the license

directory rather than scattering them and modifying the license server's search path.



● lmremove – releases the failed license to the pool of free licenses. If an SAP product is still using the license, the product obtains the license again during its next heartbeat.

● lmreread – directs the license daemon to reread the license file and to start any new vendor daemons.● lmstat – displays the license server system status.● lmswitch – tells the license server to start writing to a new debug log file. When you restart the license

server, it uses the debug log file specified in the options file, so you must ensure the old log is renamed to avoid appending to it.

● lmswitchr – switches the report log to a new file name. You should use lmnewlog to archive the report log instead.

● lmver – reports the FLEXnet licensing version of a library or binary file.

In this section:

Using SySAM Utilities [page 51]Learn how to see a list of optional parameters of SySAM utilities.

7.6.1 Using SySAM Utilities

Learn how to see a list of optional parameters of SySAM utilities.

Context

SAP does not support the functionality of all optional parameters.

Procedure

1. To see a full list, enter:

lmutil -help

2. To see a list of parameters for lmborrow, enter:

lmutil lmborrow -help

NoteIn addition, the sysam script, also located in the bin directory, provides a wrapper for the most frequently used FLEXnet utilities. To display the help text, which provides complete instructions, enter:

sysam help


8 Installing SAP IQ Server Software

SAP IQ server installation media supports GUI, console, and unattended (silent) installs. You can use the installation media to install a new SAP IQ server and selected components or to add additional components to an existing installation.

In this section:

Installing a Server in GUI Mode [page 53]Use this option to install your server software using a graphical user interface (GUI). The GUI installer is wizard-driven and supports all product editions and installation types.

Installing a Server in Console Mode [page 55]Choose a console installation if you prefer a non-GUI interface. Installing server components in console mode is similar to installing in GUI mode, except that you run the installer from the command line, and enter text to select the installation options.

Installing a Server in Unattended (Silent) Mode [page 57]Unattended or silent installations are typically used to update multiple systems. Except for the absence of the GUI screens, all actions of InstallAnywhere are the same, and the result of a server installation in silent mode is exactly the same as one done in either GUI or console mode.

Server Environment Variables [page 61]

Finding Server Utilities and Files [page 62]SAP IQ uses environment variables to point to different installation directories.

Reviewing Server Installation Logs [page 64]The installer writes a general log to the $SYBASE directory that records all installation activity and individual logs for each installed component. If an installation problem occurs, start with the IQ_Suite.log, then refer to the component log for specific details.

Related Information

Download Installation Files [page 43]


Installing SAP IQ Server Software

8.1 Installing a Server in GUI Mode

Use this option to install your server software using a graphical user interface (GUI). The GUI installer is wizard-driven and supports all product editions and installation types.

Prerequisites

● The SAP IQ package has been downloaded and unpacked.● You are logged on as the SAP IQ user account.● If you plan to apply an unserved license during installation, the license file is in a location accessible to the

installer.● If you plan to apply a served license during installation, the SYSAM license server must be configured and

running. See Installing SySAM License Server [page 45].

Procedure



3. When prompted, specify a parent install directory. Do not install SAP IQ into a destination directory or path that contains spaces.

For a new server installation, specify a new parent install directory. Do not install to an SAP IQ directory from a previous installation.

If installing the SySAM license server and SAP IQ server on the same machine, do not install to a common parent directory.

If adding components to an existing SAP IQ server, specify the existing parent install directory. Specifying a different parent directory overwrites existing environment variables and may cause unexpected behavior.

The GUI installer warns you if you try to install to an invalid path or if the parent install directory or path has changed since the last installation on the machine and you are about to replace the existing environment variables.

4. Do one of:

For Action

New installations Select Typical to install all default components. Select Custom to select and deselect individual components to install.

SAP IQ Installation and Update Guide [IBM AIX]Installing SAP IQ Server Software P U B L I C 53

For Action

Adding components to an existing installation

Select Custom and select only the additional components to install. Deselecting components already installed does not uninstall them, but can significantly speed up the installation process by not reinstalling existing features along with new features. To remove installed feature, see Uninstalling SAP IQ [page 123].

See Product Components [page 16] for information on available components.

5. Indicate whether you want to license SAP IQ now or evaluate the software. You can add your license later if preferred. See Licensing After Installation [page 101].

6. Complete and accept the terms of the licensing agreement.7. If licensing now:

a. Specify one of:

To Action

Use specify license keys Change to the location of the unserved license file and select it.

Use previously deployed license server Specify the host name of the license server. Use the machine name or the IP address.

Continue installation without a license key If you are unable to enter a valid license key or connect to a license server, select this option to continue the installation.

b. Specify the product edition and license type being installed.c. (Optional) Configure SYSAM e-mail alerts.

SYSAM e-mail alerts do not contain HELO tokens, which some SMTP mail servers require to process messages correctly. If your SMTP server requires a HELO token, append the email.helo.fqdn property to the SYSAM property file. The property value should be the fully qualified domain name, such as email.helo.fqdn=sybase.com.

The SYSAM properties file is located in the /$SYBASE/IQ-16_1/Sysam%IQDIR16% directory and is named <servername>.properties, where <servername> is the name of your server.

8. Review the installation summary and make adjustments as needed.9. Begin the installation.10. If installing SAP Cockpit:

a. Accept the default ports or change as needed.

TipRefer to your planning checklist.

b. Indicate if you want to start the IQ cockpit server now. You can start it later if preferred.

Related Information

Create the SAP IQ Account [page 43]



Download Installation Files [page 43]Installing SySAM License Server [page 45]Planning Checklist [page 39]Uninstalling SAP IQ [page 123]

8.2 Installing a Server in Console Mode

Choose a console installation if you prefer a non-GUI interface. Installing server components in console mode is similar to installing in GUI mode, except that you run the installer from the command line, and enter text to select the installation options.

Prerequisites

● The SAP IQ package has been downloaded and unpacked.● You are logged on as the SAP IQ user account.● If you plan to apply an unserved license during installation, the license file is in a location accessible to the

installer.● If you plan to apply a served license during installation, the SYSAM license server must be configured and

running. See Installing SySAM License Server [page 45].

Context

As the installer runs, refer to your planning checklist for answers to the various prompts. The prompts displayed may vary, depending on the components selected for installation.

NoteAt any time, from within the console installer, to return to the previous prompt, type back.

Procedure



and follow the instructions on the screen.3. When prompted, specify a parent install directory. Do not install SAP IQ into a destination directory or path

that contains spaces.


For new server installations, you must specify a new parent install directory. Do not install to an SAP IQ directory leftover from a previous installation.

If installing the SySAM license server and SAP IQ server on the same machine, do not install to a common parent directory.


The console installer does not warns you if you try to install to an invalid path or if the parent install directory or path has changed since the last installation on the machine and you are about to replace the existing environment variables.

4. Do one of:

For Action

New Installations Select Typical to install all default components. Select Custom to select and deselect individual components to install.

For "Custom" installations, type the number of the feature to be selected or deselected. The number acts as a switch to the current setting of a feature, though the display does not update.

For example, to install the SAP IQ server only, type 7,10,12.

NoteSpecifying a parent product automatically applies the switch to any child components associated with that feature. For example, typing 1 is equivalent to typing 2,4,5,6. However, if you typed 1,2,4,5,6, the 1 would deselect SAP IQ and all its children, then 2,4,5,6 would reselect each specified child feature. The net result would be that all children within SAP IQ would be installed.




5. Indicate whether you want to license SAP IQ now or evaluate the software. You can add your license later if preferred. See Licensing After Installation [page 101].

6. Complete and accept the terms of the licensing agreement.7. If licensing now:

a. Specify one of:

To Action

Use specify license keys Change to the location of the unserved license file and select it.



To Action

Use previously deployed license server Specify the host name of the license server. Use the machine name or the IP address.

Continue installation without a license key If you are unable to enter a valid license key or connect to a license server, select this option to continue the installation.

b. Specify the product edition and license type being installed.c. (Optional) Configure SYSAM e-mail alerts.

SYSAM e-mail alerts do not contain HELO tokens, which some SMTP mail servers require to process messages correctly. If your SMTP server requires a HELO token, append the email.helo.fqdn property to the SYSAM property file. The property value should be the fully qualified domain name, such as email.helo.fqdn=sybase.com.

The SYSAM properties file is located in the /$SYBASE/IQ-16_1/Sysam%IQDIR16% directory and is named <servername>.properties, where <servername> is the name of your server.

8. Review the installation summary and make adjustments as needed. Ensure that expected features are being installed.

9. Begin the installation.10. If installing SAP Cockpit:

a. Accept the default ports or change as needed.

TipRefer to your planning checklist.

b. Indicate if you want to start the IQ cockpit server now. You can start it later if preferred.

Related Information

Create the SAP IQ Account [page 43]Download Installation Files [page 43]Installing SySAM License Server [page 45]Planning Checklist [page 39]Uninstalling SAP IQ [page 123]

8.3 Installing a Server in Unattended (Silent) Mode

Unattended or silent installations are typically used to update multiple systems. Except for the absence of the GUI screens, all actions of InstallAnywhere are the same, and the result of a server installation in silent mode is exactly the same as one done in either GUI or console mode.


In this section:

Creating a Server Response File [page 58]You create a response file by recording your responses while running a server installation. You can create the file using either GUI or console mode.

Installing a Server Using a Response File [page 60]The system uses the responses in the file to perform the server installation.

8.3.1 Creating a Server Response File

You create a response file by recording your responses while running a server installation. You can create the file using either GUI or console mode.

Prerequisites


Context

The response file is not created until the current installation completes. Your responses to screen prompts, not your actual keystrokes, are recorded in the file. Give careful thought to your responses as they will be used in every installation using the response file.

If you are using an unserved license model, it is recommended that you select an evaluation license when creating a response file. You can apply the unserved license after running the silent install. However, if you choose to license when creating the response file, the unserved license file specified in the response file must be available to the installer. If the file is not found during installation, the silent installation fails with a licensing error message.

If you are using a served license model, ensure the SYSAM License Manger is configured and running before you select license server when creating a response file.

Procedure




Mode Syntax

GUI ./setup.bin -r <responseFileName>

Console ./setup.bin -i console -r <responseFileName>

where <responseFileName> includes the absolute path and file name of the response file. If no path is specified, the file is created in the current folder.

NoteThough optional, it is recommended that you add the file extension .properties to any custom response file you create to help identify it.

3. Respond to the screen prompts as you would for an attended installation.

Tip○ Keep in mind that your responses to each prompt are being saved to the file and will be used for

each unattended installation. While it is possible to edit the response file before using it, this should be kept to a minimum to prevent unexpected errors in the file from spelling errors or invalid responses, which could cause the installation to fail or not install as intended.

○ It is not recommended that you license SAP IQ with a license file when creating a response file. The license file name and location would be recorded in the response file. For an unattended installation to successfully license the SAP IQ server using this response file, the license file would need to have the same name and exist in the specified location on the machine before the installation begins.

4. Review the installation summary and make adjustments as needed.5. Begin the installation.

Results

The response file is created when the installation completes.

Related Information

Create the SAP IQ Account [page 43]Download Installation Files [page 43]Installing SySAM License Server [page 45]Planning Checklist [page 39]


8.3.2 Installing a Server Using a Response File

The system uses the responses in the file to perform the server installation.

Prerequisites

● The SAP IQ package has been downloaded and unpacked.● You are logged on as the SAP IQ user account.● If your response file specifies an unserved license, the license file is available to the installer in the location

specified in the response file.● If you plan to apply a served license during installation, the SySAM license server is configured and

running.

Context

You can use the default response file, installer.properties or a custom response file. You can edit any response file, but be careful. If you edit the information in the file and it becomes invalid, the silent installation might fail. To override the default installation options, use the -f argument to point to a custom response file.

The cursor disappears when the silent installation begins and reappears once complete. Press Ctrl + c at any time to cancel a silent installation.

Procedure


setup.bin –f <responseFileName> -i silent -DAGREE_TO_SAP_LICENSE=true -DSYBASE_PRODUCT_LICENSE_TYPE=license

where:

Argument Description

-f <responseFileName> Optional argument that includes the absolute path and file name of the response file. If you omit this argument, the installer defaults to installer.properties or other .properties file in the same installation directory.

-i silent Required switch that starts the silent installer.

-DAGREE_TO_SAP_LICENSE=true Required argument that indicates you accept Sybase end-user license agreement.




-DSYBASE_PRODUCT_LICENSE_TYPE=license

Required argument to install a licensed version of the software. Not required for evaluation version.

- DUNINSTALL_DELETE_DATA_FILES=true Optional argument that deletes unnecessary files after installation.

Results

If the response file references an unserved license that cannot be found, the silent installation fails with an error message.

If the response file references a SySAM license server that is not running, the installation completes, but the SAP IQ server is configured to use an evaluation license. Start the license server, then stop and restart the SAP IQ server to apply the served license.

Related Information

Create the SAP IQ Account [page 43]Download Installation Files [page 43]Installing SySAM License Server [page 45]Planning Checklist [page 39]

8.4 Server Environment Variables

To set the environment variables, change to the SAP IQ parent installation directory and execute one of the following:

● For the tcsh or C (csh) shell, enter:

source ./IQ.csh

● For the Korn (ksh), Bash, or Bourne (sh) shells, enter:

source ./IQ.sh

TipTo automatically set the environment variables upon logon, consider adding the file to the /etc/profile.d.

NoteFor additional information about environment variables, see Environment Variables [page 91].


8.5 Finding Server Utilities and Files

SAP IQ uses environment variables to point to different installation directories.

Directory Variables


Variable Points To Description

$SYBASE User-defined parent installation directory

Directory that contains the core SAP IQ server product directory as well as the directories for selected components.

$IQDIR16 Product installation directory IQ-16_1, a subdirectory of the parent installation directory.

Directory that contains the core SAP IQ server product directories.

Parent Installation Directories

The user-defined installation directory ($SYBASE) contains the files, scripts, and other objects required to support the server.

Directory Contents

charsets Character sets available for compatibility with Adaptive Server Enterprise.

COCKPIT-4 SAP IQ Cockpit startup and configuration files.

collate Collation sequences available for compatibility with Adaptive Server Enterprise.

config Various configuration files.

IQ-16_1 Subdirectories, scripts, and property files required to run the server.

jConnect-16_0 JDBC 4.0 compliant driver for SAP IQ.

jre Java runtime environment.

jutils-3_0 Version 3.0 Java-based utilities, including Ribo, a Tabular Data Streams utility.

locales Language modules for system messages and date/time formats.

log Installation log files.

OCS-16_0 Open Client tools and utilities.

shared Objects and libraries shared by other components, including the Java Runtime Environment (JRE).

Sybase_Install_Registry Server registry file that holds information related to the installed products. Do not modify.

sybuninstall Subdirectories for scripts that uninstall SAP IQ and SySAM.



Directory Contents

SYSAM-2_0 SySAM licenses and utilities. This directory contains three subdirectories: bin, licenses, and log.

ThirdPartyLegal Third party license terms and agreements.

Product Installation Directories

IQ-16_1 ($IQDIR16) is a subdirectory of the user-defined installation directory ($SYBASE) that contains the files, scripts, and other objects required to run the server.

Directory Contents

bin64 Utilities you use to start and manage your server.

DBACOCKPIT Stores query plans generated by DBA Cockpit.

demo Sample data and scripts for the demo database.

install Installation history file.

java Different JAR files.

lib64 Various library files.

logfiles SAP IQ writes log files to this directory.

lsunload Local Store Unload utility.

res Character encoding resource files.

samples Sample SAP SQL Anywhere tools and scripts.

scripts Sample scripts and stored procedures.

sdk Subdirectories for various language utilities.

shared Objects and libraries shared by other components, including the Java Runtime Environment (JRE).

Sysam Local SySAM configuration information.

tix Tcl/Tk extension library.

unload Various unload scripts, files, and utilities.

Related Information

Server Environment Variables [page 61]


8.6 Reviewing Server Installation Logs

The installer writes a general log to the $SYBASE directory that records all installation activity and individual logs for each installed component. If an installation problem occurs, start with the IQ_Suite.log, then refer to the component log for specific details.

The installer also creates a set of corresponding .out files for each component .log file. These files capture different component installation activities. If the installer runs normally, these files may remain empty.

All installation log files are found in the log directory within the SAP IQ parent installation directory.

NoteDo not confuse this log directory with the logfiles directory in the $IQDIR16 directory, which contains SAP IQ log files not related to installation.

File Name Contents

conn_add_lang.log Additional Connectivity Language Modules

conn_lang.log Connectivity Language Modules

iq_agent.log SAP IQ Agent Plug-in

iq_client_common.log Client components

iq_client_ms.log Windows client components

iq_client_web.log Web Drivers

iq_odbc.log ODBC Driver

iq_server.log Server components

iq_shared.log Shared SAP IQ Configuration files

IQ_Suite.log SAP IQ Server Suite installation summary

IQ_Suite_Variable_Reference.log InstallAnywhere installation variables

iqcmap.log SAP IQ Cockpit installation summary

jconnect16.log SAP jConnect installation summary

jre8.log Java Runtime Environment v8 installation (SAP IQ and SAP IQ Cockpit)

lang.log Language Modules

scc_cfw.log Cockpit framework installation summary

open_client.log Open Client installation summary

scc_server.log SAP IQ Cockpit user interface installation summary

sysam_util.log SySAM License Utilities installation summary



9 Installing SAP IQ Client Software

SAP IQ client installation media supports GUI, console, and unattended (silent) installs. You can use the installation media to install a new SAP IQ client and selected components or to add additional components to an existing installation.

In this section:

Running the Client and Server On the Same System [page 66]Your SAP IQ server can connect to a remote SAP IQ server. In this scenario, the SAP IQ server becomes a client of the remote SAP IQ server, and requires an SAP IQ client.

Installing a Client in GUI Mode [page 66]Use this option to set up your client software in a graphical user interface (GUI) environment. The GUI installer is wizard-driven and supports all product editions and installation types.

Installing a Client in Console Mode [page 67]Choose a command-line installation if you prefer a non-windowing interface or for developing custom installation scripts. Installing the client in console mode is similar to installing in GUI mode, except that you run the installer from the command line, and enter text to select the installation options.

Installing a Client in Unattended (Silent) Mode [page 70]Unattended or silent installations are typically used to update multiple systems. Except for the absence of the GUI screens, all actions of InstallAnywhere are the same, and the result of a client installation in silent mode is exactly the same as one done in GUI mode with the same responses.

Client Environment Variables [page 73]

Finding Client Utilities and Files [page 73]SAP IQ uses environment variables to point to different installation directories.

Reviewing Client Installation Logs [page 75]The installer writes a general log to the $SYBASE directory that records all installation activity and individual logs for each installed component. If an installation problem occurs, start with the IQ_Suite.log, then refer to the component log for specific details.

Configuring Client Connectivity [page 75]SAP IQ supports ODBC and JDBC connectivity.

Related Information

Download Installation Files [page 43]

SAP IQ Installation and Update Guide [IBM AIX]Installing SAP IQ Client Software P U B L I C 65

9.1 Running the Client and Server On the Same System

Your SAP IQ server can connect to a remote SAP IQ server. In this scenario, the SAP IQ server becomes a client of the remote SAP IQ server, and requires an SAP IQ client.

SAP IQ uses a shared memory segment and several semaphores for communication between the client and server on the same machine. Shared memory is the default communications mechanism when the client and server are on the same system. Shared memory is configured automatically, and starts automatically.

9.2 Installing a Client in GUI Mode

Use this option to set up your client software in a graphical user interface (GUI) environment. The GUI installer is wizard-driven and supports all product editions and installation types.

Prerequisites


Procedure



3. When prompted, specify a parent install directory. Do not install SAP IQ into a destination directory or path that contains spaces.

For new installations, you must specify a new parent install directory. Do not install to an SAP IQ directory leftover from a previous installation.


The GUI installer warns you if you try to install to an invalid path or if the parent install directory or path has changed since the last installation on the machine and you are about to replace the existing environment variables.

4. Do one of:


Installing SAP IQ Client Software

For Action





5. Complete and accept the terms of the licensing agreement.6. Review the installation summary and make adjustments as needed.7. Begin the installation.

Related Information

Create the SAP IQ Account [page 43]Download Installation Files [page 43]Installing SAP IQ Server Software [page 52]Planning Checklist [page 39]Uninstalling SAP IQ [page 123]

9.3 Installing a Client in Console Mode

Choose a command-line installation if you prefer a non-windowing interface or for developing custom installation scripts. Installing the client in console mode is similar to installing in GUI mode, except that you run the installer from the command line, and enter text to select the installation options.

Prerequisites



Context

Note● If you are installing the SAP IQ client on a machine with SAP IQ server already installed, you must

perform the installation using the SAP IQ server installer, not the SAP IQ client installer. See Installing SAP IQ Server Software [page 52].

● At any time, from within the console installer, to return to the previous prompt, type back.

Procedure



and follow the instructions on the screen.3. When prompted, specify a parent install directory. Do not install SAP IQ into a destination directory or path

that contains spaces.

For new installations, you must specify a new parent install directory. Do not install to an SAP IQ directory leftover from a previous installation.


The console installer does not warns you if you try to install to an invalid path or if the parent install directory or path has changed since the last installation on the machine and you are about to replace the existing environment variables.

4. Do one of:



For Action


For "Custom" installations, type the number of the feature to be selected or deselected. The number acts as a switch to the current setting of a feature, though the display does not update.

For example, to install the client only without drivers, type 1,2. 1 deselects SAP IQ and all its children. 2 then reselects the IQ client only.

NoteSpecifying a parent product automatically applies the switch to any child components associated with that feature. For example, typing 1 is equivalent to typing 2,3,4. However, if you typed 1,2,4, the 1 would deselect SAP IQ and all its children, then 2,3,4 would reselect each specified child feature. The net result would be that all children within SAP IQ would be installed.

Adding components to an existing installation Select Custom and select only the additional components to install. Deselecting components already installed does not uninstall them, but can significantly speed up the installation process by not reinstalling existing features along with new features. To remove installed feature, see Uninstalling SAP IQ [page 123].


5. Complete and accept the terms of the licensing agreement.6. Review the installation summary and make adjustments as needed. Ensure that expected features are

being installed.7. Begin the installation.

Related Information

Create the SAP IQ Account [page 43]Download Installation Files [page 43]Installing SAP IQ Server Software [page 52]Planning Checklist [page 39]Uninstalling SAP IQ [page 123]


9.4 Installing a Client in Unattended (Silent) Mode

Unattended or silent installations are typically used to update multiple systems. Except for the absence of the GUI screens, all actions of InstallAnywhere are the same, and the result of a client installation in silent mode is exactly the same as one done in GUI mode with the same responses.

In this section:

Creating a Client Response File [page 70]You create a response file by recording your responses while running a client installation. You can create the file using either GUI or console mode.

Installing a Client Using a Response File [page 71]The system uses the responses in the file to perform the client installation.

9.4.1 Creating a Client Response File

You create a response file by recording your responses while running a client installation. You can create the file using either GUI or console mode.

Prerequisites


Context

The response file is not created until the current installation completes. Your responses to screen prompts, not your actual keystrokes, are recorded in the file. Give careful thought to your responses as they will be used in every installation using the response file.

Procedure




Mode Syntax

GUI ./setup.bin -r <responseFileName>

Console ./setup.bin -i console -r <responseFileName>

where <responseFileName> includes the absolute path and file name of the response file. If no path is specified, the file is created in the current folder.

NoteThough optional, it is recommended that you add the file extension .properties to any custom response file you create to help identify it.

3. Respond to the screen prompts as you would for an attended installation.4. Review the installation summary and make adjustments as needed.5. Begin the installation.

Results

The response file is created when the installation completes.

Related Information

Create the SAP IQ Account [page 43]Download Installation Files [page 43]Installing SAP IQ Server Software [page 52]Planning Checklist [page 39]

9.4.2 Installing a Client Using a Response File

The system uses the responses in the file to perform the client installation.

Prerequisites



Context

You can use the default response file, installer.properties or a custom response file. You can edit any response file, but be careful. If you edit the information in the file and it becomes invalid, the silent installation might fail. To override the default installation options, use the -f argument to point to a custom response file.

The cursor disappears when the silent installation begins and reappears once complete. Press Ctrl + c at any time to cancel a silent installation.

Procedure


setup.bin –f <responseFileName> -i silent -DAGREE_TO_SAP_LICENSE=true -DSYBASE_PRODUCT_LICENSE_TYPE=license

where:


-f <responseFileName> Optional argument that includes the absolute path and file name of the response file. If you omit this argument, the installer defaults to installer.properties or other .properties file in the same installation directory.

-i silent Required switch that starts the silent installer.

-DAGREE_TO_SAP_LICENSE=true Required argument that indicates you accept Sybase end-user license agreement.

-DSYBASE_PRODUCT_LICENSE_TYPE=license

Required argument to install a licensed version of the software. Not required for evaluation version.

- DUNINSTALL_DELETE_DATA_FILES=true Optional argument that deletes unnecessary files after installation.

Related Information

Create the SAP IQ Account [page 43]Download Installation Files [page 43]Installing SAP IQ Server Software [page 52]Planning Checklist [page 39]



9.5 Client Environment Variables

NoteYou don't need to set client environment variables if the server and client are installed on the same host.

To set the environment variables, change to the SAP IQ parent installation directory and execute one of the following:

● For the tcsh or C (csh) shell, enter:

source ./IQ.csh

● For the Korn (ksh), Bash, or Bourne (sh) shells, enter:

source ./IQ.sh

TipTo automatically set the environment variables upon logon, consider adding the file to the /etc/profile.d.

NoteFor additional information about environment variables, see Environment Variables [page 91].

9.6 Finding Client Utilities and Files


Directory Variables


Variable Points To Description

$SYBASE User-defined parent installation directory

Directory that contains the core SAP IQ client product directory as well as the directories for selected components.

$IQDIR16 Product installation directory IQ-16_1, a subdirectory of the parent installation directory.

Directory that contains the core SAP IQ client product directories.


Parent Installation Directory

The user-defined directory ($SYBASE) contains the files, scripts, and other objects required to support the client.

Directory Contents

IQ-16_1 SAP IQ client components.

jConnect-16_0 JDBC 4.0 compliant driver for SAP IQ.

shared Shared software components.

Sybase_Install_Registry Client component registry file.

jre Java Runtime Environment directory.

jutils-3_0 Version 3.0 Java-based utilities, including Ribo, a Tabular Data Streams utility.

log Client log file directory.

ThirdPartyLegal Third-party license agreements.

sybuninstall Subdirectories for scripts that uninstall SAP IQ and SySAM.

Product Installation Directory

IQ-16_1 ($IQDIR16) is a subdirectory of the user-defined installation directory ($SYBASE) that contains the files, scripts, and other objects required to run the client.

Directory Contents

bin<platform> Utilities you use to start and manage your server. <platform> value is 64 or 32, depending on your installation.

install Installation history file.

java Different JAR files.

lib<platform> Various library files. <platform> value is 64 or 32, depending on your installation.

res Character encoding resource files.

samples Sample SAP SQL Anywhere tools and scripts.

sdk Subdirectories for various language utilities.

shared Subdirectories for various shared components.

tix Tcl/Tk extension library.

Related Information

Client Environment Variables [page 73]



9.7 Reviewing Client Installation Logs

The installer writes a general log to the $SYBASE directory that records all installation activity and individual logs for each installed component. If an installation problem occurs, start with the IQ_Suite.log, then refer to the component log for specific details.

The installer also creates a set of corresponding .out files for each component .log file. These files capture different component installation activities. If the installer runs normally, these files may remain empty.

All installation log files are found in the log directory within the SAP IQ parent installation directory.

NoteDo not confuse this log directory with the logfiles directory in the $IQDIR16 directory, which contains SAP IQ log files not related to installation.

File Name Contents

iq_client_common.log Client components

iq_client_ms.log Windows client components

IQ_ClientSuite.log SAP IQ Client Suite installation summary

IQ_ClientSuite_Variable_Reference.log InstallAnywhere installation variables

iq_client_web.log Web Drivers

iq_odbc.log ODBC Driver

iq_shared.log Shared SAP IQ Configuration files

jconnect16.log SAP jConnect installation summary

jre8.log Java Runtime Environment v8 installation (SAP IQ and SAP IQ Cockpit)

9.8 Configuring Client Connectivity

SAP IQ supports ODBC and JDBC connectivity.

In this section:

Connecting Using ODBC [page 76]Open Database Connectivity (ODBC) is a standard API that allows a single application to access a variety of data sources through ODBC–compliant drivers.

Connecting Using JDBC [page 80]JDBC and jConnect provide access to SAP IQ for Java-based applications.

Connecting Using OLE DB [page 80]SAP IQ includes an OLE DB provider as an alternative to ODBC. OLE DB is a data access model from Microsoft that uses the Component Object Model (COM) interfaces. Unlike ODBC, OLE DB does not


assume that the data source uses a SQL query processor. Although OLE DB requires a Windows client, you can use OLE DB to access Windows and UNIX servers.

Connecting Using Open Client [page 81]Clients require a server object in the interfaces file to access server properties and methods. Use the SAP IQ Directory Services Editor (dsedit) to create the interfaces file entries. These instructions apply to sever installations only.

Network Issues for SAP IQ Servers [page 81]Properly configured UNIX servers run under the TCP/IP protocol, which enables non–UNIX clients to communicate with the server.

Connecting Across a Firewall [page 82]Set the CommLinks connection parameters in your application's connection string to connect across a firewall.

9.8.1 Connecting Using ODBC

Open Database Connectivity (ODBC) is a standard API that allows a single application to access a variety of data sources through ODBC–compliant drivers.

In this section:

ODBC Conformance [page 76]ODBC drivers manufactured by different vendors may vary widely in the functions they provide. SAP IQ supports ODBC 3.5.2.

Installing ODBC Drivers [page 77]Server and client installations include ODBC drivers. Platform-specific drivers are available from the SAP Product Download Center and SAP Service Marketplace.

Using UNIX or Linux–Based Query Tools Through ODBC [page 78]There are several ways to use ODBC to connect to UNIX or Linux-based query tools.

Managing ODBC Data Sources [page 78]On UNIX-like operating systems, ODBC data sources are stored in a system information file. Although this file is named .odbc.ini by default, it can have any name.

Command Line Connections to 32-bit Applications [page 80]Use dbisql to connect to 32-bit applications from the command line.

9.8.1.1 ODBC Conformance

ODBC drivers manufactured by different vendors may vary widely in the functions they provide. SAP IQ supports ODBC 3.5.2.

Conformance level Sybase IQ support

Core conformance All core features.



Conformance level Sybase IQ support

Level 1 conformance All level 1 features, except for asynchronous execution of ODBC functions.

SAP IQ does support multiple threads sharing a single connection. The requests from the different threads are serialized by SAP IQ.

Level 2 conformance All level 2 features, except:

● Three-part names of tables and views. This is not applicable for SAP IQ.● Asynchronous execution of ODBC functions for specified individual state

ments.● Ability to time out login requests and queries.

Note● Although you can use new ODBC 3.5.x features such as descriptors in your ODBC applications, ODBC

2.x applications will continue to work with SAP IQ.● For more information about ODBC, see the ODBC Programmer's Reference, available from Microsoft

Corporation as part of the ODBC software development kit, or from the Microsoft Web site at: http://msdn.microsoft.com/en-us/library/windows/desktop/ms714177(v=vs.85).aspx .

9.8.1.2 Installing ODBC Drivers

Server and client installations include ODBC drivers. Platform-specific drivers are available from the SAP Product Download Center and SAP Service Marketplace.

Application Linking

If you use an ODBC application that uses libodbc.so (libodbc.so.1) or libodbcinst.so (libodbcinst.so.1), you can create symbolic links that point to $IQDIR16/lib64/libdbodbc16.so.1 for single-threaded or $IQDIR16/lib64/libdbodbc16_r.so.1 for multi-threaded applications.

If you are creating an ODBC application, you can link directly to libdbodbc16.so for non–threaded applications and libdbodbc16_r.so for threaded applications. References to ODBC functions are resolved at run-time.

32-bit and 64-bit Drivers

UNIX 64-bit applications, including many third-party tools, can use 64-bit ODBC drivers to connect to 64-bit SAP IQ servers. 32-bit applications can use 32-bit ODBC drivers to connect to 64-bit IQ servers. (32-bit applications cannot use 64-bit ODBC drivers to connect to 64-bit IQ servers.)


http://help.sap.com/disclaimer?site=http%3A%2F%2Fmsdn.microsoft.com%2Fen-us%2Flibrary%2Fwindows%2Fdesktop%2Fms714177%28v%3Dvs.85%29.aspx

http://help.sap.com/disclaimer?site=http%3A%2F%2Fmsdn.microsoft.com%2Fen-us%2Flibrary%2Fwindows%2Fdesktop%2Fms714177%28v%3Dvs.85%29.aspx

The SAP IQ Client software supplied with all platforms contains an ODBC driver for connecting from Windows-based ODBC applications. To connect via ODBC from 32-bit UNIX client applications, download and install the 32-bit ODBC driver kit. Check the EBF/Update information for the appropriate driver.

9.8.1.3 Using UNIX or Linux–Based Query Tools Through ODBC

There are several ways to use ODBC to connect to UNIX or Linux-based query tools.

Tools that do not require extensive driver manager services can use symbolic links to connect directly to the driver. Tools that require a driver manager may ship with a driver manager.

For information and recommendations about compatible driver managers available for specific applications, see the documentation for the application.

On UNIX-like operating systems, ODBC data sources are stored in .odbc.ini. Use a text editor to update this file manually, or use the cross–platform iqdsn utility to create an ODBC data source.

You can use files as data sources instead of databases. File data sources are stored as files with the extension .dsn.

9.8.1.4 Managing ODBC Data Sources

On UNIX-like operating systems, ODBC data sources are stored in a system information file. Although this file is named .odbc.ini by default, it can have any name.

A system information file can include any connection parameter. This sample DSN connects to the demo database:

[My Data Source] Userid=DBA Password=<password> EngineName=test_serverCommLinks=tcpip(port=1870)AutoStop=noDatabaseName=iqdemo DatabaseFile=iqdemo.db

System Information File Location

SAP IQ searches the following locations, in order, for the system information file:

1. The <$ODBCINI> environment variable2. The <$HOME> environment variable3. The user's Home directory4. The <$PATH> environment variable



NoteSAP IQ clients ignore these environment variables when searching for the system information file:

● <$ODBC_HOME>● <$ODBC_INI>

Use specific host/port/server connection arguments. AIX broadcast mechanism in a subnetted environment cannot detect with the BROADCAST message that another server of the same name and port number is running even in the same subnet.

Connecting with a Data Source Entry

To use a data source entry to connect to your database, open a terminal, and use dbisql with the data source entry name in a connection string. For example:

% dbisql –c "dsn=sample_dsn"

NoteAny database started from a connection string is, by default, stopped when there are no more connections to it, and any database that is loaded from a connection string is unloaded as soon as there are no more connections to it when the Autostop connection parameter is set to yes.

Connecting without a Data Source Entry

To connect without using .odbc.ini, open a terminal, and use dbisql all connection parameters. For example:

% dbisql –c "UID=DBA;PWD=<password>;AutoStop=no; ENG=<engine name>;DBF=$IQDIR16/demo/iqdemo.db"

This example is shown on multiple lines, however, you must enter the entire command at the command prompt on one line.

Additional Information

See iqdsn Database Administration Utility in the SAP IQ Utility Guide.


9.8.1.5 Command Line Connections to 32-bit Applications

Use dbisql to connect to 32-bit applications from the command line.

To connect to a 32-bit application without using a data source, use dbisql to connect from the command line. To connect to the iqdemo.db you would use a command similar to this:

dbisql -c "UID=DBA;PWD=<password>;AUTOSTOP=no; ENG=<engine_name>;DBF=$SYBASE/IQ-16_1/demo/iqdemo.db"

9.8.2 Connecting Using JDBC

JDBC and jConnect provide access to SAP IQ for Java-based applications.

Java Database Connectivity (JDBC) is a Java application programming interface (API) that provides programmatic access to SAP IQ. jConnect is an SAP utility that provides high-performance native access to all SAP products as a standard installation option.

Interactive SQL (dbisql) can use either JDBC or ODBC connectivity.

The SQL Anywhere JDBC driver is the default driver for Interactive SQL.

NoteThe iAnywhere JDBC driver is deprecated.

9.8.3 Connecting Using OLE DB

SAP IQ includes an OLE DB provider as an alternative to ODBC. OLE DB is a data access model from Microsoft that uses the Component Object Model (COM) interfaces. Unlike ODBC, OLE DB does not assume that the data source uses a SQL query processor. Although OLE DB requires a Windows client, you can use OLE DB to access Windows and UNIX servers.

SAP IQ supports Dynamic (dynamic scroll), Static (insensitive) and Forward only (no–scroll) cursors, but does not support Keyset (scroll) cursors. In SAP IQ the isolation level is always 3, no matter what you specify.

SAP IQ does not support Windows CE or remote updates through a cursor.


See OLE DB Connection Parameters in SAP IQ Programming.



9.8.4 Connecting Using Open Client

Clients require a server object in the interfaces file to access server properties and methods. Use the SAP IQ Directory Services Editor (dsedit) to create the interfaces file entries. These instructions apply to sever installations only.

Prerequisites

● You must be the owner of the SAP IQ home directory ($SYBASE) to run dsedit● Make a copy of the interfaces file before you make any changes

Procedure

1. From a terminal, change to $SYBASE/OCS-16_0/bin2. Start dsedit.

3. On the Select a Directory Service dialog, select the interfaces file or driver (default) or select a directory service to open, and then click OK.

4. From the Directory Service Session dialog, choose Add new server entry.5. On the Server Entry Editor dialog, enter the SAP IQ server name, then click the Add new network

transport.6. On the Network Transport Editor dialog, enter the host name and port number of the SAP IQ server and

then click OK.7. On the Server Entry Editor dialog, click OK.8. On the Directory Service Session dialog, click Close session.9. On the Select a Directory Service dialog, click Exit10. On the dsedit question dialog, click Yes to confirm exit.

9.8.5 Network Issues for SAP IQ Servers

Properly configured UNIX servers run under the TCP/IP protocol, which enables non–UNIX clients to communicate with the server.

Verified TCP/IP Protocol Stacks

For SAP IQ to run properly, the protocol stack on the client and server computers must be compatible at each layer. Many vendors supply TCP/IP protocol stacks and associated software. SAP IQ communications have been explicitly verified with these TCP/IP implementations:


● TCP/IP For NetWare● Microsoft Winsock version 2.0

User Datagram Protocol

There are several entries into the TCP/IP protocol stack. SAP IQ employs the User Datagram Protocol (UDP). While it is called a transport protocol here and elsewhere, UDP provides little more than a user interface to the network layer IP. In particular, UDP is not a guaranteed transmission protocol.

Tuning Performance Under TCP/IP

Although the default packet size for TCP/IP is 1460 bytes, a larger packet size may improve query response time, especially for queries that transfer a large amount of data between a client and a server process. You can set the maximum packet size using the database server command lines or CommBufferSize (CBSIZE) in the client connection string. This option may be used with the start_iq command.

9.8.6 Connecting Across a Firewall

Set the CommLinks connection parameters in your application's connection string to connect across a firewall.

There are restrictions on connections when the client application is on one side of a firewall and the server is on the other. Firewall software filters network packets according to network port. Also, it is common to disallow UDP packets from crossing the firewall.

● Set the ClientPort parameter to a range of allowed values for the client application to use. You can then configure your firewall to allow these packets across. You can use the short form CPort.

● Set the HOST parameter to the host name on which the database server is running. You can use the short form IP.

● Specify the port your database server is using in the ServerPort parameter if it is not using the default port of 2638. You can use the short form Port.

● Set the DoBroadcast=NONE parameter to prevent UDP from being used when connecting to the server.

In this example, the connection string fragment:

● Restricts the client application to ports 5050 through 5060● Connects to a server named myeng running on the machine at address myhost using the server port 2020

No UDP broadcast is carried out because of the DoBroadcast option.

CEng=myeng;Links=tcpip(ClientPort=5050– 5060;Host=myhost;Port=2020;DoBroadcast=NONE)




See Connection and Communication Parameters in SAP IQ Administration: Database.


10 Postinstallation Tasks

Once your server and client software is installed, the postinstallation tasks help you verify if it is correctly configured, licensed, and running.

In this section:

(Optional) The Demo Database [page 85]The SAP IQ demo database (iqdemo.db) is a database that contains sample data about a fictional company that sells athletic clothing.

(Optional) The SAP IQ Utility Server [page 87]The utility server is a phantom database with no physical representation. It has no database file, and therefore it cannot contain data.

Setting Up your Environment [page 88]These topics describe the installation and operating system settings used by SAP IQ.

Licensing After Installation [page 101]All product editions except the Evaluation Edition require a license. Optional features are sold and licensed separately.

Starting and Running an SAP IQ Server [page 105]Use the start_iq startup utility to start your server. start_iq is a command line utility that runs on all platforms and ensures that all required parameters are set correctly.

Stopping an SAP IQ Server [page 107]SERVER OPERATOR system privilege is the default permission level required to stop a server, but you can use the -gk startup option to change the default to ALL or NONE. Setting the permission level to ALL lets all users stop the server; setting the permission level to NONE means that no one can stop the server. In a production environment, only the Server Operator should be allowed to stop the database server.

Start and Stop the SAP IQ Cockpit Agent [page 108]SAP IQ Cockpit is a Web-based tool for managing and monitoring SAP IQ servers. The SAP IQ Cockpit agent must be running to log on to the SAP IQ Cockpit. Run the cockpit command to start SAP IQ Cockpit agent.

Stopping the SAP IQ Cockpit Agent [page 109]Stop the SAP IQ Cockpit agent. Once stopped, you can no longer use the SAP IQ Cockpit.

Configuration [page 109]This section outlines basic configuration concepts and procedures of an SAP IQ server.

Remove Sample Application Files [page 111]Before you deploy your server in a production environment, remove the sample client applications.

Starting Interactive SQL [page 111]Interactive SQL is a utility that ships with SAP IQ and lets you execute SQL statements, build scripts, and display database data. It is a component of the SAP IQ client software.

Verify SAP IQ Server Is Licensed [page 112]After you license an SAP IQ sever, verify that the license was accepted.


Postinstallation Tasks

10.1 (Optional) The Demo Database

The SAP IQ demo database (iqdemo.db) is a database that contains sample data about a fictional company that sells athletic clothing.

Many of the examples throughout the documentation use the demo database as a data source. It is installed as part of the SAP IQ Server installation and resides on the server. You can also use the demo database to test your installation.

For a new SAP IQ installation, to successfully log on to the SAP IQ Cockpit requires that at least one server be running. Without access to the SAP IQ Cockpit, you cannot use the Create Database wizard to create your initial server. The SAP IQ demo database can be used as the initial server.

Use of the demo database is optional and has no performance impact.

NoteThe demo database is not designed to be used as a production database.

In this section:

Creating the Demo Database [page 85]Use the SAP IQ script to create the demo database.

Starting and Stopping the Demo Database [page 86]You can start and stop the demo database as needed.

Removing the Demo Database [page 87]Once you have created a production database on the SAP IQ server, you may choose to remove the demo database. Removal is optional and has no performance impact on your production system if not removed.

10.1.1 Creating the Demo Database

Use the SAP IQ script to create the demo database.

Prerequisites

● You are logged on as the SAP IQ user account.● All environment variables are properly set.

SAP IQ Installation and Update Guide [IBM AIX]Postinstallation Tasks P U B L I C 85

Procedure

1. From a console, change to

$IQDIR16/demo

2. Type:

./mkiqdemo.sh -dba <username> -pwd <password>

3. Follow the screen prompts to create the database. Minimum password length is 6 characters.

NoteYou can adjust the minimum password length using the -mpl optional command line argument. Example:

./mkiqdemo.sh -dba <username> -pwd <password> -mpl <8>

Results

The demo database is created, but not started. See Starting and Stopping the Demo Database [page 86]. It is called iqdemo.db and resides in the $IQDIR16/demo directory.

10.1.2 Starting and Stopping the Demo Database

You can start and stop the demo database as needed.

Prerequisites

● You are logged on as the SAP IQ user account.● All environment variables are properly set.

Procedure

1. From a console, change to the directory where you created the demo database.

cd $IQDIR16/demo

2. To start the demo database, enter:

start_iq @iqdemo.cfg iqdemo.db



3. To stop the demo database, execute:

stop_iq -stop

10.1.3 Removing the Demo Database

Once you have created a production database on the SAP IQ server, you may choose to remove the demo database. Removal is optional and has no performance impact on your production system if not removed.

In the $IQDIR16/demo directory, delete all file beginning with iqdemo. Also delete the demodata folder.

10.2 (Optional) The SAP IQ Utility Server

The utility server is a phantom database with no physical representation. It has no database file, and therefore it cannot contain data.

For a new SAP IQ installation, to successfully log on to the SAP IQ Cockpit requires that at least one server be running. Without access to the SAP IQ Cockpit, you cannot use the Create Database wizard to create your initial server. The SAP IQ utility server can be used as the initial server.

The utility server has no default password. It uses a temporary password, which you define during startup. The password is valid only for the duration the utility server is running. A new password must be defined each time the utility server is started.

When logged in to the utility server in the SAP IQ Cockpit console, you can use the Create Database wizard to your first database.

In this section:

Starting the SAP IQ Utility Server [page 87]The SAP IQ utility server must be running before you can use it to log in to the SAP IQ Cockpit console and should be stopped immediately after creating the initial SAP IQ server.

10.2.1 Starting the SAP IQ Utility Server

The SAP IQ utility server must be running before you can use it to log in to the SAP IQ Cockpit console and should be stopped immediately after creating the initial SAP IQ server.

Prerequisites

● You are logged on as the SAP IQ user account.


● All environment variables are properly set.

Procedure

1. From a console, change to the $SYBASE/IQ-16_1/bin64 directory.:

$SYBASE/IQ-16_1/bin64/cockpitutildb.sh

2. Specify a temporary password for the utility server.

10.3 Setting Up your Environment

These topics describe the installation and operating system settings used by SAP IQ.

Depending on the operating system, these settings may be stored as environment variables, initialization file entries, or registry entries.

In this section:

Installation Directory Structure [page 88]When you install SAP IQ, several directories may be created. This section describes the directory structure.

How SAP IQ Locates Files [page 89]To start and run, SAP IQ must find and access several types of files. Several directories or files with identical names may reside on a system.

Environment Variables [page 91]SAP IQ uses environment variables to store various types of information. Environment variables can be modified, if needed, and not all variables need to be set in all circumstances.

10.3.1 Installation Directory Structure

When you install SAP IQ, several directories may be created. This section describes the directory structure.

The directories created depend on which options you choose during installation and which directories already exist in your SAP IQ directory (the parent directory defined by $SYBASE).

By default, SAP IQ software is installed in a unique subdirectory under the SAP IQ parent directory. This subdirectory is called the installation directory. Other tools provided with SAP IQ have unique subdirectories under the SAP IQ parent directory. This section describes only the subdirectory structure for SAP IQ.

By default, the SAP IQ installation directory is IQ-16_1. The location of IQ-16_1 varies, depending on where you install SAP IQ. The IQ-16_1 directory is also referred to by the environment variable $IQDIR16.



The SAP IQ installation directory holds a number of directories and files:

Demo directory ($SYBASE/IQ-16_1/demo) Holds the tools required to build the iqdemo database. The iqdemo database files are iqdemo.db, iqdemo.iq, iqdemo.iqmsg, and iqdemo.iqtmp. Use ./mkiqdemo.sh to create the iqdemo database. The iqdemo database can be used to demonstrate problems to Technical Support.

Demo data subdirectory ($SYBASE/IQ-16_1/demo/adata) Holds data to allow the creation of the iqdemo database. .

Scripts directory ($SYBASE/IQ-16_1/scripts) Holds some scripts used in examples and when creating catalog objects like stored procedures. Do not edit these scripts. If you edit, delete, or move these scripts, the server will not operate properly.

Samples directories ($SYBASE/IQ-16_1/samples) The samples directory contains SQL samples and user-defined function (UDF) samples. The $SYBASE/IQ-16_1/samples/sqlanywhere directory contains directories of SQL samples. The sqlanywhere/c directory holds C++ examples that illustrate using ESQL (embedded SQL) and C with SAP SQL Anywhere. Because SAP SQL Anywhere and SAP IQ share common code, you can modify these examples for use with SAP IQ. The /samples/udf directory holds sample C++ scalar and aggregate UDFs.

Additional directories Additional directories hold executables, libraries, help files, and so on. Subdirectories within IQ-16_1 containing these files include /bin64, /lib64, /logfiles, /res, and /tix.

10.3.2 How SAP IQ Locates Files

To start and run, SAP IQ must find and access several types of files. Several directories or files with identical names may reside on a system.

Understanding how SAP IQ finds these files is important to ensure that you use the correct files. The types of files include but are not limited to:

Libraries Might include product libraries or system libraries. File name extensions include.so.nnn or .so. These files are required to run SAP IQ. If an incorrect DLL is found, a version mismatch error may occur. For example, library files might be found in $IQDIR16/lib64 or $SYBASE/OCS-16_0/lib3p64. An empty directory, $IQDIR16/usrlib, lets you supersede default libraries with custom libraries and patches, because start_iq includes usrlib before regular library directories. SAP IQ uses both SAP Adaptive Server Enterprise (SAP ASE) and SAP SQL Anywhere libraries. If either of these products have already been installed on your system, note the directory where they are installed to avoid confusion.Interface files Required to run SAP IQ.Configuration files Used to specify connection parameters. Examples include iqdemo.cfg.Database files Store the data and metadata. For example: iqdemo.db, iqdemo.iq, iqdemo.iqmsg, iqdemo.iqtmp.Log files Store information about the current session on the server and connected database. For example, a server log might be named $SYBASE/IQ-16_1/logfiles/yourservername.0006.srvlog. The database log (for example, $SYBASE/IQ-16_1\demo\iqdemo.log) is created when you connect to the database. For more information about these files, see SAP IQ Administration: Database and SAP IQ Utility Guide.Product scripts Are sample files that show how to create, populate, and upgrade databases.


User files Include flat files used with the LOAD command and SQL scripts used with tools such as Interactive SQL.Temporary files Created by to store temporary information for operations like performing sorts for queries.

Some file names are specified in SQL statements and must be located at runtime. Examples of SQL statements that use file names include the following:

INSTALL statement the name of the file that holds Java classes.LOAD TABLE statement The name of the file from which data should be loaded.CREATE DATABASE statement A file name is needed for this statement and similar statements that can create files.

In some cases, SAP IQ uses a simple algorithm to locate files. In other cases, a more extensive search is carried out.

In this section:

Simple File Searching [page 90]In many SQL statements such as LOAD TABLE or CREATE DATABASE, the file name is interpreted as relative to the current working directory of the database server; that is, where the server was started.

Extensive File Searching [page 90]SAP IQ programs, including the database server and administration utilities, carry out extensive searches for required files, such as DLLs or shared libraries.

10.3.2.1 Simple File Searching

In many SQL statements such as LOAD TABLE or CREATE DATABASE, the file name is interpreted as relative to the current working directory of the database server; that is, where the server was started.

Also, when a database server is started and a database file name (DBF parameter) is supplied, the path is interpreted as relative to the directory in which the server was started.

10.3.2.2 Extensive File Searching

SAP IQ programs, including the database server and administration utilities, carry out extensive searches for required files, such as DLLs or shared libraries.

In these cases, SAP IQ programs look for files in the following order:

The executable directory the directory in which the program executable is held. Also, directories with the following paths relative to the program executable directory:

● Parent of the executable directory.● A child of the parent directory named scripts.

Current working directory when a program is started, it has a current working directory (the directory from which it is started). This directory is searched for required files.



Location registry entry on a Windows installation, SAP IQ adds a LOCATION registry entry. The indicated directory is searched, followed by the following:

● A child named scripts● A child with the operating system name (bin32, bin, and so on)System-specific directories this includes directories where common operating system files are held, such as the Windows directory and the Windows\system directory on Windows.CLASSPATH directories for Java files, directories listed in the CLASSPATH environment variable are searched to locate files.PATH directories directories in the system path and the user’s path are searched to locate files.LIBRARY PATH directories directories listed in the LIBPATH environment variable are searched for shared libraries.

10.3.3 Environment VariablesSAP IQ uses environment variables to store various types of information. Environment variables can be modified, if needed, and not all variables need to be set in all circumstances.

Environment variables are set by running a shell script after installation.

In this section:

Modifying Environment Variables on UNIX [page 92]On UNIX platforms, running environment source files sets the required environment variables. However, if you must set optional variables or change defaults, use this procedure.

Running UNIX Environment Source Files [page 93]Environment source files set the required environment variables on UNIX.

COCKPIT_JAVA_HOME Environment Variable [page 93]This variable specifies the location of the Java Runtime Environment used by SAP IQ Cockpit.

IQCHARSET Environment Variable [page 94]IQCHARSET sets the default character set.

IQDIR16 Environment Variable [page 94]IQDIR16 identifies the location of the SAP IQ directory and is the location for other directories and files under that directory.

IQLANG Environment Variable [page 95]IQLANG sets the default language.

IQLOGDIR16 Environment Variable [page 96]The IQLOGDIR16 environment variable defines the location of various log files. IQLOGDIR16 is not set by the installation program.

IQTMP16 Environment Variable [page 97]The IQTMP16 environment variable is not set by the installation program. IQTMP16 is used by SAP IQ to indicate a directory where temporary files are kept.

JAVA_HOME Environment Variable [page 98]Defines JRE home, which points to directory containing bin/java.

LIBPATH or LD_LIBRARY_PATH Environment Variable [page 98]


LIBPATH or LD_LIBRARY_PATH specifies the directories where SAP IQ shared libraries are located.

PATH Environment Variable [page 99]PATH is an operating system required variable that includes the directories where SAP IQ executables are located.

SQLCONNECT Environment Variable [page 99]SQLCONNECT specifies connection parameters that are used by several of the database administration utilities, such as Interactive SQL, dbinfo, and dbstop, when connecting to a database server.

SYBASE Environment Variable [page 100]SYBASE identifies the location of SAP database applications, such as SAP Open Server.

SAP_JRE8_64, SAP_JRE8_32 Environment Variables [page 100]This variable specifies the location of the Java Runtime Environment used by SAP IQ Cockpit.

10.3.3.1 Modifying Environment Variables on UNIX

On UNIX platforms, running environment source files sets the required environment variables. However, if you must set optional variables or change defaults, use this procedure.

Procedure

1. To check the setting for an environment variable, use:

echo $<variable-name>

For example, to see the setting for the $SYBASE variable, type:

echo $SYBASE

Which returns:

/<parent install directory>/IQ-16_1

2. In one of your startup files (.cshrc, .shrc, or .login), add a line that sets the variable.

In some shells (such as sh, bash, ksh) the line is:

<VARIABLE>=<value>;export <VARIABLE>

In other shells (such as csh, tsch) the line is:

setenv <VARIABLE> "<value>"



10.3.3.2 Running UNIX Environment Source Files

Environment source files set the required environment variables on UNIX.

Context

Issue the following command to set all required environment variables.

Procedure

Change to the SAP IQ parent installation directory and execute one of the following:○ For the tcsh or C (csh) shell, enter:

source ./IQ.csh

○ For the Korn (ksh), Bash, or Bourne (sh) shells, enter:

source ./IQ.sh

10.3.3.3 COCKPIT_JAVA_HOME Environment Variable

This variable specifies the location of the Java Runtime Environment used by SAP IQ Cockpit.

If not set, SAP IQ Cockpit startup checks for the location of the Java VM in the SAP_JRE8 environment variables.

Settings

COCKPIT_JAVA_HOME = $SYBASE/IQ-16_1/shared/SAPJRE<version>

Operating System

Required.


10.3.3.4 IQCHARSET Environment Variable

IQCHARSET sets the default character set.

<Charset> is a character set name. For example, setting IQCHARSET=cp1252 sets the default character set to cp1252.

The first of the following values set determines the default character set.

● IQCHARSET environment variable● Query the operating system

If no character set information is specified, use iso_1 for UNIX.

Setting

IQCHARSET=<charset>

10.3.3.5 IQDIR16 Environment Variable

IQDIR16 identifies the location of the SAP IQ directory and is the location for other directories and files under that directory.

● $IQDIR16/bin[64]/logfiles is the default location for the server log and backup and restore log (the backup history file). You can override this default by setting the IQLOGDIR16 environment variable.

● $IQDIR16/demo is the location for the iqdemo database files.

Setting

IQDIR16 = $SYBASE/IQ-16_1

Operating System

(Required) Set by the environment source file or the installation program. This default setting can be changed on Windows.



10.3.3.6 IQLANG Environment Variable

IQLANG sets the default language.

<Language_code> is the two-letter combination representing a language. For example, setting IQLANG=DE sets the default language to German.

The first of the following values set determines the default language.

● IQLANG environment variable● Query the operating system

If no language information is set, English is the default.

Setting

IQLANG=<language_code>

Operating System

Optional but recommended in non-English environments.

In this section:

List of Language Label Values [page 95]Valid language label values and their equivalent ISO 639 language codes. Set the two-letter ISO_639 language code in the IQ_LANG environment variable.

10.3.3.6.1 List of Language Label Values

Valid language label values and their equivalent ISO 639 language codes. Set the two-letter ISO_639 language code in the IQ_LANG environment variable.

Language ISO_639 Language Code Language Label Alternative Label

Arabic AR arabic N/A

Czech CS czech N/A

Danish DA danish N/A

Dutch NL dutch N/A

English EN us_english english

Finnish FI finnish N/A


Language ISO_639 Language Code Language Label Alternative Label

French FR french N/A

German DE german N/A

Greek EL greek N/A

Hebrew HE hebrew N/A

Hungarian HU hungarian N/A

Italian IT italian N/A

Japanese JA japanese N/A

Korean KO korean N/A

Lithuanian LT lithuanian N/A

Norwegian NO norwegian norweg

Polish PL polish N/A

Portuguese PT portuguese portugue

Russian RU russian N/A

Simplified Chinese ZH chinese simpchin

Spanish ES spanish N/A

Swedish SV swedish N/A

Thai TH thai N/A

Traditional Chinese TW tchinese tradchin

Turkish TR turkish N/A

Ukrainian UK ukrainian N/A

10.3.3.7 IQLOGDIR16 Environment Variable

The IQLOGDIR16 environment variable defines the location of various log files. IQLOGDIR16 is not set by the installation program.

● The server log is in the file servername.nnnn.srvlog (where nnnn is the number of times the server has been started) in the directory specified by IQLOGDIR16.

If IQLOGDIR16 is not set to a valid, write-enabled directory, then most utilities, including start_iq, use the default location $IQDIR16/logfiles for all server logs.

Setting

IQLOGDIR16 = <path>



Operating System

Optional.

10.3.3.8 IQTMP16 Environment Variable

The IQTMP16 environment variable is not set by the installation program. IQTMP16 is used by SAP IQ to indicate a directory where temporary files are kept.

The IQTMP16 environment variable should point to a local directory for those using NFS (network file system), which permits the IQTMP16 directory to purge directories and files that are no longer needed as client connections are closed. Each client connection creates several directories and files in a temporary directory. These are needed only for the duration of the connection. The directory must have write permissions for all users who connect to the server.

NoteThe temporary files whose location is defined by IQTMP16 are files used by the client and server. This variable does not control the default location of your IQ temporary store. The CREATE DATABASE statement controls the default location of your IQ temporary store.

CautionDo not set IQTMP16 to $SYBASE or $IQDIR16.

If you do not explicitly set IQTMP16, IQTMP16 is set to a subdirectory in the tmp directory.

If more than one database server is running on a machine, each server and associated local client needs a separate temporary directory to avoid conflicts. When you do not specify a port or engine number for connection, SAP IQ uses shared memory connectivity instead of network connectivity.

To avoid conflicts when using shared memory:

● Create a temporary directory dedicated to each server. Make sure that each local client uses the same temporary directory as its server by setting the IQTMP16 environment variable explicitly in both environments.

● Create a data source name in the .odbc.ini file (on UNIX) for each server and provide detailed connection information.

● Use connection strings that specify explicit parameters instead of relying on defaults.● Confirm connections by issuing:

SELECT "database name is" = db_name(), "servername_is" = @@servername

Setting

IQTMP16 = <temp_directory>


Operating System

Optional on UNIX. Not used on Windows platforms.

10.3.3.9 JAVA_HOME Environment Variable

Defines JRE home, which points to directory containing bin/java.

Used if the location of the Java VM is not set in the SAP_JRE8 environment variables.

JAVA_HOME is commonly created when installing a VM.

On UNIX, run the SYBASE.csh (C shell) or SYBASE.sh (Bourne or Korn shell) environment source file to find and start the correct JRE for the SAP IQ engine. The Java VM location specified in JAVA_HOME takes precedence over the location returned by SYBASE.csh or SYBASE.sh. If neither JAVA_HOME nor the SYBASE.csh or SYBASE.sh scripts locate the Java VM, SAP IQ will not load a Java VM.

Settings

JAVA_HOME = $SYBASE/shared/JRE<version>

Operating System

Required.

10.3.3.10 LIBPATH or LD_LIBRARY_PATH Environment Variable

LIBPATH or LD_LIBRARY_PATH specifies the directories where SAP IQ shared libraries are located.

Set the library path variable by running the environment source file.

Settings

LIBPATH = <installation_path/lib>



Operating System

Required. Variable name is platform dependent. UNIX only.

10.3.3.11 PATH Environment Variable

PATH is an operating system required variable that includes the directories where SAP IQ executables are located.

On UNIX, run the environment source file to include the necessary directories.

Setting

PATH = <installation_path>

Operating System

Required.

10.3.3.12 SQLCONNECT Environment Variable

SQLCONNECT specifies connection parameters that are used by several of the database administration utilities, such as Interactive SQL, dbinfo, and dbstop, when connecting to a database server.

The SQLCONNECT environment variable is optional, and is not set by the installation program.

This string is a list of parameter settings, of the form parameter=<value>, delimited by semicolons.

The number sign “#” is an alternative to the equals sign; use it if you are setting the connection parameters string in the SQLCONNECT environment variable. Using “=” inside an environment variable setting is a syntax error. The = sign is allowed only in Windows.

NoteSpecifying connection parameters in SQLCONNECT rather than on the command line offers greater security on UNIX systems. It prevents users from being able to display your password with ps -ef. This is especially useful if you run Interactive SQL or other utilities in quiet mode. Note that specifying connection parameters in SQLCONNECT rather than on the command line is more secure, but is not entirely secure. Because the password is in plain text, it is possible for hostile action to extract it from the environment context. For more information, see Connection and Communication Parameters Reference in SAP IQ Administration: Database.


Settings

SQLCONNECT = <parameter>#<value> ; ...

Operating System

Optional.

10.3.3.13 SYBASE Environment Variable

SYBASE identifies the location of SAP database applications, such as SAP Open Server.

You must set the SYBASE variable before you can perform many tasks on the SAP IQ server or client.

Setting

SYBASE = <path>

Operating System

Required.

10.3.3.14 SAP_JRE8_64, SAP_JRE8_32 Environment Variables

This variable specifies the location of the Java Runtime Environment used by SAP IQ Cockpit.

On startup, SAP IQ Cockpit checks COCKPIT_JAVA_HOME for Java version definition. If COCKPIT_JAVA_HOME is undefined, SAP IQ Cockpit checks for installed JREs in this order:

● SAP_JRE8_64● SAP_JRE8● SAP_JRE8_32

SAP IQ Cockpit then sets COCKPIT_JAVA_HOME to the first value it finds in this list.



Setting

On UNIX, the JRE environment variable is automatically set by sourcing the IQ.sh (Bourne/Korn shell) or IQ.csh (C shell) file.

To manually set the JRE environment variable:

COCKPIT_JAVA_HOME=$SYBASE/shared/SAPJRE-8_(minor_version)_64BIT

or:

COCKPIT_JAVA_HOME=$SYBASE/shared/SAPJRE-8_(minor_version)_32BIT

10.4 Licensing After Installation

All product editions except the Evaluation Edition require a license. Optional features are sold and licensed separately.

Whether you install a licensed or evaluation edition, you have 90-day access to all features and options. To use an option beyond the 90-day evaluation period, you must purchase and apply an appropriate served or unserved license.

Using an unlicensed option on a licensed server can throw the server into grace mode, which can cause the server to shutdown when the grace period expires. The DBA or other equivalent user must explicitly authorize access to an optionally licensed feature. A server will not attempt to check-out an optional license by default. Unless the DBA grants access to an option, the option will not be available.

In this section:

Verify and Authorize Optional Licensed Components [page 102]Your license controls the optional components licensed on an SAP IQ server. After applying the license, use the sp_iqlmconfig to allow or disallow the feature.

Applying an Unserved License [page 103]You can update an SAP IQ server from an evaluation license to an unserved license.

Applying a Served License [page 104]You can update an SAP IQ server from an evaluation license to a served license.


10.4.1 Verify and Authorize Optional Licensed Components

Your license controls the optional components licensed on an SAP IQ server. After applying the license, use the sp_iqlmconfig to allow or disallow the feature.

To verify your licensed components, connect to the server, start Interactive SQL (dbisql), and run sp_iqlmconfig without parameters to return a set of properties and values that indicate the state of your licenses:

Property Value ----------------------------------------------------- Edition EELicense Type DTApplication Type IQIQ_CORE License Count in use 2 (CPU core based)Optional license in use : IQ_UDA No Optional license in use : IQ_LOB NoOptional license in use: IQ_SECURITY NoOptional license in use: IQ_MPXNODE NoOptional license in use: IQ_VLDBMGMT NoIQ_VLDBMGMT License Count in use 0 Optional license in use: IQ_UDF NoOptional license in use: IQ_IDA NoOptional license in use: IQ_URIDA NoOptional license in use: IQ_TS_FSF NoEmail Severity NONESMTP Host smtpSMTP Port 25 Email Sender Email Recipients

Authorizing Optional Features

Run sp_iqlmconfig with the allow or disallow parameter to enable or disable an optional license. The ALL keyword enables or disables all optional licenses, except IQ_VLDBMGT:

sp_iqlmconfig 'allow', 'ALL' // enable all, except IQ_VLDBMGT sp_iqlmconfig 'disallow', 'IQ_SECURITY' // disable IQ_SECURITY

Use the IQ_VLDBMGT and <quantity> parameters to change the number of available IQ_VLDBMGT licenses:

sp_iqlmconfig 'allow', 'IQ_VLDBMGT', '8' // increase by 8 sp_iqlmconfig 'disallow', 'IQ_VLDBMGT', '2' // decrease by 2

See the sp_iqlmconfig stored procedure in SAP IQ SQL Reference for information about authorizing optional features and other issues related to license management configuration.

License Server Issues

All license server status and error messages are written to the SYBASE.log in the log directory. To diagnose issues with a license server, check the $SYBASE/SYSAM-2_0/log/SYBASE.log file. You can use iqdemo.db to perform this task.

A line that begins with “Checked out license...” indicates a successful license configuration. If you see a “Sysam: FLEXnet Licensing error:” message, check with your SAP representative to resolve the issue.




● See Managing the License Server Debug Log and Troubleshooting SySAM Errors in the SySAM Users Guide.

10.4.2 Applying an Unserved License

You can update an SAP IQ server from an evaluation license to an unserved license.

Context

If an unserved license is not applied before the evaluation period ends, the server shuts down and cannot be started until a valid license is applied. If an unserved license is incorrectly applied during the evaluation period, the server continues to function in evaluation mode. After application, always verify the unserved license is being used.

Procedure

1. Stop any running databases.2. Navigate to $SYBASE/SYSAM-2_0/3. If it doesn't already exist, create a folder named licenses. The folder name must be exact, both spelling

and case.4. Copy the unserved license to $SYBASE/SYSAM-2_0/licenses5. Restart the database.6. Review the .iqmsg file to verify the server is using an unserved license.

Related Information

Verify SAP IQ Server Is Licensed [page 112]



10.4.3 Applying a Served License

You can update an SAP IQ server from an evaluation license to a served license.

Prerequisites

The SySAM License Server is running and licensed.

Context

If a served license is not applied before the evaluation period ends, the server shuts down and cannot be started until a valid license is applied. If a served license is incorrectly applied during the evaluation period, the server continues to function in evaluation mode. After application, always verify the served license is being used.

Procedure

1. Stop any running databases.2. Navigate to $SYBASE/SYSAM-2_0/3. If it doesn't already exist, create a folder named licenses. The folder name must be exact, both spelling

and case.4. In the licenses folder, create a text file with the extension .lic. Add the following two lines to the file:

SERVER <license_server_machine_name> ANY USE_SERVER

5. Restart the database.6. Review the .iqmsg file to verify the server is using a served license.

If the server is not using the served licenses, make sure the served license is applied to the SySAM license server. See Apply or Update Licenses on the SySAM License Server [page 49]

Related Information

Verify SAP IQ Server Is Licensed [page 112]



10.5 Starting and Running an SAP IQ Server

Use the start_iq startup utility to start your server. start_iq is a command line utility that runs on all platforms and ensures that all required parameters are set correctly.

Starting a Server or Database

To use start_iq to start a server or database, change to a directory where you have write privileges, and use this command format:

start_iq [<server-options> ] [ <database-file> [<database-options>]<, ...>]

A startup command may include several startup parameters:

● <server-options> – include the database server name and other options that control the behavior of the server, for all databases that are running on that server

● <database-file > – is the file name of the catalog store. You can omit this option, or enter one or more database file names on the command line.Each database is loaded and available for applications. If the starting directory contains the database file, you do not need to specify the path; otherwise, you must specify the path. You do not need to specify the .db file extension.

● <database-options> – control certain aspects of each database file you start.

Default Startup Parameters

start_iq uses a default configuration file ($IQDIR16/scripts/default.cfg) to set the default start-up parameters.

Parameter Value Description

–c 48 MB Catalog store cache size.

–gc 20 Checkpoint interval.

–gd all Allows all users to start the database by connecting.

–gl all Allows all users to load or unload tables.

–gm 10 Default number of connections.

–gp 4096 Catalog store page size.

–ti 4400 Client timeout set to 72 hours. Prevents users with long queries from being logged off over a long weekend.


Configuration Files

To override the default start-up parameters, store your options in a configuration file. To start a server with a configuration file:

start_iq @<configuration_filename>.cfg <dbname>.db

This command starts the database and sets parameters named in the (optional) configuration (.cfg) file.

On the start_iq command line, the last option you specify takes precedence, so to override your configuration file, list any options you want to change after the configuration file name. For example:

start_iq @iqdemo.cfg –x 'tcpip{port=1870}' iqdemo.db

The –x parameter here overrides connection information in the iqdemo.cfg file.

A configuration file for the demo database (iqdemo.cfg) is installed in the $IQDIR16/demo directory as an example.

Default Server Directories

The directory where the server is started becomes the default directory for all server files created by SAP IQ. If you run the start_iq utility from $IQDIR16/bin64, the script changes the directory to “./..” to avoid creating database files in the /bin directory.

Startup and Server Logs

SAP IQ writes start-up and server logs in the $IQDIR16/logfiles directory:

● Startup information is saved in the servername.nnnn.stderr file.● Server status is logged in the servername.nnnn.srvlog file.

The <nnnn> variable in the file name indicates the number of times the server has been started. For example, localhost.0004.srvlog localhost_iqdemo.0006.srvlog.

NoteIf SAP SQL Anywhere is installed on the same subnet as SAP IQ, the server must have a unique name. Both SAP SQL Anywhere and SAP IQ servers default to the port 2638.

Use a new port number for each server. Set each new port number in the $IQDIR16/scripts/default.cfg file. Change the following line in each IQ database configuration file (for example, $IQDIR16/demo/iqdemo.cfg) to update the port number:

–x tcpip{port=2638}




See start_iq Server Options in SAP IQ Utility Guide

10.6 Stopping an SAP IQ Server

SERVER OPERATOR system privilege is the default permission level required to stop a server, but you can use the -gk startup option to change the default to ALL or NONE. Setting the permission level to ALL lets all users stop the server; setting the permission level to NONE means that no one can stop the server. In a production environment, only the Server Operator should be allowed to stop the database server.

Do not shut down a server while it is still connected to one or more clients. If you try this, you get a warning that any uncommitted transactions will be lost. Disconnect or close all the clients and try again.

Server Shutdown Commands

Several commands shut down the database server.

Command Description

stop_iq Shuts down a server completely without regard for users, connections or load process status:

Syntax:

stop_iq [ options ]

dbstop Stops a server or database. The syntax is:

dbstop [ <options> ] <server-name>

Where:

● <options> – additional options let you stop a server, even if there are active connections.

● <server-name> – specify <server-name>, as well as any connection parameters you specified when you started the server.

STOP ENGINE STOP ENGINE is a SQL statement that stops a database server. The syntax is as follows, where UNCONDITIONALLY stops a database server, even if there are client connections to the server:

STOP ENGINE <engine-name> [ UNCONDITIONALLY ]


Server Shutdown Methods

There are several methods to shut down or stop a server.

Method Action

Command line Run the stop_iq or dbstop commands.

Interactive SQL Run the stop engine command to stop a named database server.

Stopping Servers in Cron or At Jobs

To use stop_iq in a cron or at job, specify the full path name to the stop_iq executable and the appropriate –stop option:

$SYBASE/IQ-16_1/bin64/stop_iq –stop one

Setting –stop one shuts down a single server, when exactly one running server was started by the user ID that starts the cron or at job. This prevents accidentally shutting down the wrong server if several are running.

$SYBASE/IQ-16_1/bin64/stop_iq –stop all

Setting –stop all shuts down all servers that were started by the user ID that starts the cron or at job.


● See STOP ENGINE Statement in SAP IQ SQL Reference● See dbstop Database Shutdown Utility and stop_iq Database Shutdown Utility in the SAP IQ Utility Guide● See Stopping Servers in SAP IQ Administration: Database

10.7 Start and Stop the SAP IQ Cockpit Agent

SAP IQ Cockpit is a Web-based tool for managing and monitoring SAP IQ servers. The SAP IQ Cockpit agent must be running to log on to the SAP IQ Cockpit. Run the cockpit command to start SAP IQ Cockpit agent.

Context

These instructions assume all environment variables are set properly.



From a console, type:

cockpit.sh

Results

Messages on the progress of the launch appear in a command window. When SAP IQ Cockpit runs, the command window becomes the SAP IQ Cockpit console; you can issue commands to get status information for SAP IQ Cockpit and its ports, plug-ins, and services.

See the SAP IQ Cockpit guide for details on using this administration tool.

10.8 Stopping the SAP IQ Cockpit Agent

Stop the SAP IQ Cockpit agent. Once stopped, you can no longer use the SAP IQ Cockpit.

Context

These instructions assume all environment variables are set properly.

From a console containing the cockpit prompt, type:

cockpit.sh -stop

If the console containing the cockpit prompt has been closed, from a new console, type:

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

Results

See the SAP IQ Cockpit guide for details on using this administration tool.

10.9 Configuration

This section outlines basic configuration concepts and procedures of an SAP IQ server.

In this section:


Using Configuration Files [page 110]Use a configuration file to store server startup options.

10.9.1 Using Configuration Files

Use a configuration file to store server startup options.

To start a server or database with a configuration file, change to a directory where you have write privileges, and use the following command format:

start_iq @<configuration_filename>.cfg <dbname>.db

If a startup parameter is passed from the command line and the same parameter exists in the .cfg file, the value in the command line overrides the value in .cfg file.

Configuration files can contain line breaks, and can include any set of options, including the @data option. Use a number sign (#) to designate lines as comments. An ampersand (&) character that appears by itself at the end of a line indicates that the previous token is continued on the next line. See the SAP IQ Utility Guide for a complete list of startup parameters.

Default Configuration File

When you start a server and do not include any command line parameters or specify a configuration file, SAP IQ retrieves the start-up parameters from a default configuration file, default.cfg, in the $IQDIR16/scripts directory. The default.cfg file is also the source of parameters for the Service Manager and multiplex configurations. You can maintain consistency by editing parameters in default.cfg.

To increase the amount of virtual memory, change the parameters in default.cfg. To reduce the virtual memory that other programs use, add swap space to machines or reduce SAP IQ memory demands (cache sizes, thread count, stack size, etc.).

Security and Configuration Files

You can use the dbfhide (File Hiding) utility to encrypt your configuration files. If you specify log file parameters (-o <logfile>) in encrypted files, the log is not available to the start_iq utility. You may want to add parameters that do not require encryption on the command line or in a separate configuration file. For example:

start_iq @encrypt_params @other_params

or

% start_iq @encrypt_params -n myserv -c 400 -o $IQDIR16/logfile/myserv.log



10.10 Remove Sample Application Files

Before you deploy your server in a production environment, remove the sample client applications.

The SAP IQ Server Suite installation may include directories that contain sample client applications, which are included for training purposes only. Remove these sample directories before you deploy your server in a production environment:

● $IQDIR16/samples● $IQDIR16/sdk

10.11 Starting Interactive SQL

Interactive SQL is a utility that ships with SAP IQ and lets you execute SQL statements, build scripts, and display database data. It is a component of the SAP IQ client software.

Prerequisites

The Interactive SQL component is installed. See Installing SAP IQ Client Software [page 65].

Context

To use Interactive SQL to connect to a database, it must be running. Enter the connection parameters to the database. Interactive SQL does not accept @filename parameters. Exit codes are 0 (success) or nonzero (failure).

Interactive SQL uses the deprecated iAnywhere JDBC driver.

If the options specified do not include user ID and password, the Connect window opens, allowing you to enter the required information.

Procedure

1. In a command shell, type:

dbisql [ <options> ] [ <dbisql-command> | <command-file> ]

2. On the Connect dialog, enter the parameters for the database and click Connect.


Results

See the SAP IQ Interactive SQL Guide for more information on using Interactive SQL.

Related Information

Installing SAP IQ Client Software [page 65]

10.12 Verify SAP IQ Server Is Licensed

After you license an SAP IQ sever, verify that the license was accepted.

Prerequisites

The license file is checked when you start the SAP IQ server. Ensure the server has been restarted at least once since the license was applied.

Procedure

1. Navigate to the data directory for the server. For example, for the initial database, navigate to

$SYBASE/IQ-16_1/demo

2. Open the iqdemo.iqmsg file in a text editor.

3. Search the file for Using licenses from.

Results

If the server is successfully licensed, using either a served or unserved license, the message Using licenses from:... appears.

If the server is using an evaluation license, the message Checked out graced license... appears.

If a valid license cannot be found, the message Cannot find license file. appears. Verify:

● The license file is in the licenses folder.



● The path to the license file is ...\SYSAM-2_0\licenses.● licenses is correctly spelled and is plural, not singular.


11 What's Next?

Create your production database.

Next Steps

Prerequisites

● The initial database is running. See Starting and Stopping the Demo Database [page 86].

NoteAlternately, you can start the utility database (utility.db) instead of the initial database. For information on the utility database, see SAP IQ Administration: Database.

Procedure

1. Create your simplex or multiplex production database using either Interactive SQL or SAP IQ Cockpit. See the SAP IQ Interactive SQL Guide or SAP IQ Cockpit guides.

2. Create users or implement LDAP. See the SAP IQ Administration: User Management and Security guide.3. Create groups and assign privileges and users. See the SAP IQ Administration: User Management and

Security guide.4. Review the Database Administration Workflow documented in SAP IQ Administration: Database to:

○ Create the production database○ Create tables in your database○ Create indexes for your tables○ Load data into your tables

5. Review the <database>.cfg configuration file and make adjustments as necessary.

6. Tune your database for optimal performance. See the SAP IQ Performance and Tuning Guide.


What's Next?

12 Troubleshooting your Installation

Find solutions to common installation problems.

If you don't find your issue in the troubleshooting topics, see SAP Note 2489003 – SAP IQ 16.1 SP 02 Release Note for a list of know issues.

In this section:

What to do when the Installation Fails [page 115]Installation fails with an error. You are unsure what to do next.

Installer Issues [page 116]This section describes issues related to the installer.

Licensing [page 118]This section describes licensing-related issues.

Do Not Install SAP IQ into the Same Directory as Other Products [page 119]Do not install SAP IQ 16.1 into the same directory as other SAP IQ products.

Client Suite Installation Finishes, but with Errors [page 119]You receive an error message when installing the client suite.

Database Upgrade Issues [page 120]Important information about database upgrades.

Incorrect CPU Count on AIX Servers [page 122]You may encounter incorrect CPU counts on AIX servers.

Installing New System Tables Requires ALTER DATABASE UPGRADE PROCEDURE ON [page 122]To install new system tables, you must run ALTER DATABASE UPGRADE PROCEDURE ON on existing databases after installing SAP IQ 16.1.

12.1 What to do when the Installation Fails

Installation fails with an error. You are unsure what to do next.

Solution

Check the install log: $SYBASE/log/IQ_Suite.log

The install log can help you trace the install progress and troubleshoot failed installations.

The installer also writes individual logs for components included as part of the install to the $SYBASE/log directory.

SAP IQ Installation and Update Guide [IBM AIX]Troubleshooting your Installation P U B L I C 115

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/2489003

Check the other troubleshooting topics in this section for topics matching the issues reported in the install log.

In this section:

Installer Fails with JVM Crash When Specifying Chinese Language [page 116][CR #783752] SAP IQ may fail to install when specifying LANG=ZH_CN.UTF-8 and LC_ALL=ZH_CN.UTF-8.

Installer Returns Error "No Filesystem Could Mount Root" on Red Hat [page 116]The installer returns a "No filesystem could mount root" error when you attempt to install on IBM P6 and P7 machines.

12.1.1 Installer Fails with JVM Crash When Specifying Chinese Language

[CR #783752] SAP IQ may fail to install when specifying LANG=ZH_CN.UTF-8 and LC_ALL=ZH_CN.UTF-8.

Solution

Use the settings LANG=C, LC_ALL= (blank), then run the installer as setup.bin –l ZH_CN.UTF-8.

12.1.2 Installer Returns Error "No Filesystem Could Mount Root" on Red Hat

The installer returns a "No filesystem could mount root" error when you attempt to install on IBM P6 and P7 machines.

The error message is:rhel6 install error: No filesystem could mount root, tried: iso9660

SolutionFollow the steps on http://www.ibm.com/developerworks/forums/thread.jspa?threadID=357314 and re-install.

12.2 Installer Issues

This section describes issues related to the installer.


Troubleshooting your Installation

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.ibm.com%2Fdeveloperworks%2Fforums%2Fthread.jspa%3FthreadID%3D357314

In this section:

Installer Reports gzip File Not Found [page 117][CR #771401] The installer returns the error: gzip: "Not Found".

Installer Stops Responding [page 117]Issue: A network resource causes the installer to stop responding and returns a syntax error. The df command also stops responding.

12.2.1 Installer Reports gzip File Not Found

[CR #771401] The installer returns the error: gzip: "Not Found".

The message displays because the installer cannot find the path to the gzip file.

Solution:

You must install gzip and reference it in the path for the installer. The installer expects to find gzip in the /usr/bin directory.

On some machines, gzip is located in the /usr/contrib/bin/ directory. If this is the case, update the path and run the installer.

12.2.2 Installer Stops Responding

Issue: A network resource causes the installer to stop responding and returns a syntax error. The df command also stops responding.

The error message is:syntax error near unexpected token 'fi'.Solution:

1. Identify the network file system (NFS) mounts that may have problems:

strace -e statfs, statfs64 df

2. Use the umount command to unmount an identified NFS mount:

umount -l <path>

3. Repeat the above steps until there are no more NFS mounts that have stopped responding.

NoteThe umount command requires root permission. If umount unmounts the NFS, you may have to restart your machine.


12.3 Licensing

This section describes licensing-related issues.

Installer does not Prompt for License File Information

You run the installer, but the installer does not prompt for any license file information.

SolutionThis occurs when you launch the installer using a relative path.

To resolve this issue, launch the installer from the directory where it is located, or launch the installer using an absolute path.

License Server Reports Wrong Number of Available Licenses

[CR #669653] When a product requires multiple licenses and the license server does not have enough licenses available to satisfy its needs, the failure message reported by the product does not show the correct amount that were available (that the product could obtain).

In this example, there are five license in a SySAM server; three are in use by another host, so only two licenses can be obtained. But SYSAM will report a message similar to:Insufficient IQ_CORE licenses. SAP IQ requires4 IQ_CORE licenses but only 5 could be obtained.

SolutionNone. SAP is aware of the problem and will address the issue in a future release.

Licensing Behavior in a Virtual Environment

[CR #628596, #628403] SAP IQ cannot be installed or fails to start in a virtual environment and reports an error.

SAP IQ cannot be installed or fails to start in a virtual environment and reports an error similar to the following:

Cannot determine the total number of processor cores on the machine from within this virtual system. The IQ_CORE("DH") license type is restricted for use on a machinewith a maximum of 4 processor cores regardless ofwhether the virtual system is limited to use fewerprocessor cores. You need to run 'sysamcap' on thephysical machine (or virtual-machine/partition controldomain) and set the reported environment variable prior to running Installer.



This error occurs in the following circumstances:

● SAP IQ is running on a virtual system that lacks access to the processor counts of the physical machine (this applies to all virtual environments except AIX LPAR and HP-UX vPar).

● SAP IQ is using a license type that is restricted for use to a machine with no more than a specific number of processors (for example, ASE Small Business Edition cannot be used on a machine with more than two processor chips).

Solution

Run the sysamcap DEFAULT command on the physical machine or control domain for the virtualization technology (for example, VMware ESX console, or XEN dom0), then set the environment variable reported prior to running the product or product installer. The process is described in the SYSAM Sub-capacity Licensing section of the SYSAM Users Guide SySAM 2 Users Guide.

12.4 Do Not Install SAP IQ into the Same Directory as Other Products

Do not install SAP IQ 16.1 into the same directory as other SAP IQ products.

Installing SAP IQ 16.1 into the same directory with older SAP products may render some or all of these products unusable.

12.5 Client Suite Installation Finishes, but with Errors

You receive an error message when installing the client suite.

The error message is:

The installation of SAP IQ Client Suite 16.1 SPxx (64-bit) us finished, but some errors occurred during the install. Please check the installer log file.

The log file contains an error similar to:

Install Uninstaller: SAP IQ Client Suite 16.1 SP01 (64-bit) (Install All Uninstaller Components)Status: ERROR

Solution

When installing, you selected an existing directory instead of a new directory.

Set the $SYBASE environment variable.


12.6 Database Upgrade Issues

Important information about database upgrades.

For detailed information about upgrading SAP IQ, see Upgrade to SAP IQ 16.1 SP 02 [page 125].

Shut Down All Products That Use $SYBASE Before Upgrade

[CR #750748] The SYBASE variable identifies the location of the common parent directory shared by SAP applications like SAP ASE and SAP Open Client.

Failure to shut down all products that use $SYBASE may generate signal 11 (SIGSEGV) errors when you upgrade SAP IQ.

SolutionShut down all SAP applications, restart the SAP IQ server, and retry the upgrade.

Drop All JOIN and All LD Indexes

[CR #702052] On multiplex, drop all logical servers named AUTO, COORDINATOR, ALL or DEFAULT.

If you do not drop these objects and try to run an ALTER DATABASE UPGRADE in SAP IQ 16.1, the upgrade fails and the server returns a message that indicates that a database upgrade is not possible when these objects are in use.

Recovery InformationTo recover from a failed upgrade, shut down the 16.1 server, open the database with SAP IQ 15.x, and drop all LD and all JOIN indexes as well as any named logical servers before proceeding with the migration.

ALTER DATABASE UPGRADE Fails with the Error "Not allowed while 'DBA' is using the database"

[CR #675890] Database upgrade procedures in the Installation and Configuration Guide instruct you to use several startup flags to start or restart a server. If SAP IQ Cockpit is running, or another process that automatically connects to SAP IQ, you must increase the number of connections using the -gm flag or the upgrade fails.

In an environment where many processes automatically connect to SAP IQ, consider temporarily starting SAP IQ on a different port using the -x flag. This option prevents all existing processes from connecting to IQ since the port will be unknown to them. You can also use this method for any maintenance task that requires SAP IQ connectivity to be limited.

For example, the SAP IQ upgrade procedure follows this sequence for a simplex server:



1. Shut down the server, then restart with these startup flags:-gm 1 -iqro 12. Run ALTER DATABASE UPGRADE. SAP IQ returns an error:

Not allowed while 'DBA' is using the databaseSimilarly, the IQ multiplex upgrade procedure follows this sequence:

1. Shut down the multiplex, then restart the coordinator with these startup flags:

-iqmpx_sn 1 -gm 1 -iqro 1

2. Run ALTER DATABASE UPGRADE. IQ returns an error:

Not allowed while 'DBA' is using the database

Solution 1The -gm switch controls the number of connections when you start the server.

1. Start the server with -gm 2 (which allows two connections), or drop the existing connection, which is used by SAP IQ Cockpit when the server starts.

2. Verify the number of connections using the sp_iqconnection command.3. If necessary, drop any connections used by SAP IQ Cockpit (or other processes) using the DROP

CONNECTION <id_number> command.

Solution 2Temporarily start IQ on a different port using the –x switch: The –x switch controls the port that IQ uses when you start the server.

● On a simplex server, use the –x switch to specify a new port number:

start_iq @yourserver.cfg yourdb.db -x 'tcpip{port=<new_port>}'

● On a multiplex server, use both the –x switch and the iqmpx override switch to specify a new port number:

start_iq @yourserver.cfg yourdb.db -iqmpx_ov 1 -x 'tcpip{port=<new_port>}'

Block Number Issues May Cause Corruption

Issues with certain block numbers may cause corruption in upgraded databases. For more information, see 2034975 .


http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/2034975

12.7 Incorrect CPU Count on AIX Servers

You may encounter incorrect CPU counts on AIX servers.

Client Connections May Fail When Server Performs License Checks

[CR #670991] Client connections to an AIX server may occasionally fail when the server performs periodic CPU license checks. This can sometimes result in an incorrect CPU count.

Solution

If you find that CPU counts are no longer correct, use this command to reset the SYBASE_SAM_CPUINFO environment variable that controls the license counting mechanism:

Set SYBASE_SAM_CPUINFO=ORIGINAL

Incorrect Core Count when SMT is Greater Than 2 Per Core

[CR #656959] SAP IQ may incorrectly count more cores than are actually present on AIX POWER7 systems when Simultaneous MultiThreading (SMT) is greater than 2 per core. This may result in the SAP IQ server not starting due to licensing problems, or the server may start in grace mode.

Solution

Turn off hyperthreading, configure SMT equal to 2 per core, or contact SAP Technical Support.

12.8 Installing New System Tables Requires ALTER DATABASE UPGRADE PROCEDURE ON

To install new system tables, you must run ALTER DATABASE UPGRADE PROCEDURE ON on existing databases after installing SAP IQ 16.1.

For syntax, see SAP IQ SQL Reference guide.



13 Uninstalling SAP IQ

Uninstall SAP IQ server and/or client.

In this section:

Uninstalling SAP IQ Software [page 123]To uninstall SAP IQ, run the uninstaller from a console or terminal. Instructions apply to IQ server and client software installed on the same host.

13.1 Uninstalling SAP IQ Software

To uninstall SAP IQ, run the uninstaller from a console or terminal. Instructions apply to IQ server and client software installed on the same host.

Prerequisites

● You are logged on as the SAP IQ user account.

Context

The uninstall process removes features installed by InstallAnywhere, using any mode. It does not remove files and folders created after the installation. These files and folders must be manually removed.

Using GUI Mode

Procedure

1. From a console, change to:

$SYBASE/sybuninstall/IQSuite

2. Start the installer:

Type ./uninstall and follow the instructions on the screen.

3. To remove all installed SAP IQ components, choose Completely Uninstall. To uninstall select components, choose Uninstall Specific Features.

SAP IQ Installation and Update Guide [IBM AIX]Uninstalling SAP IQ P U B L I C 123

Using Console Mode

Procedure




Type ./uninstall -i console and follow the instructions on the screen.

3. To remove all installed SAP IQ components, choose Completely remove all features and components. To uninstall select components, choose Choose specific features that were installed by InstallAnywhere.

Using Unattended (Silent) Mode

Context

An unattended uninstall can only be run from the command line. The silent uninstaller displays no status messages. User files are not deleted by default. To delete user files, include the -DUNINSTALL_DELETE_DATA_FILES=true flag to the uninstall command.

Procedure




Type ./uninstall -i silent - DUNINSTALL_DELETE_DATA_FILES=true and follow the instructions on the screen.


Uninstalling SAP IQ

14 Upgrade to SAP IQ 16.1 SP 02

This support package includes updates to features currently installed on your system.

SAP IQ 16.1 SP 02 is a complete installation package. A previous release of the software is not a prerequisite for this support package. See the cover letter included as part of this release for a list of enhancements. The cover letter is found in the server folder on the installation media.

NoteSAP IQ 16.1 SP 01 increased the minimum password length from three to six characters. After performing a database upgrade, existing passwords from a pre- SAP IQ 16.1 SP 01 database continue to work, even if they do not meet the new minimum password length. The new minimum password length is enforced when modifying existing or creating new passwords. Users are strongly encouraged to change nonconforming passwords to benefit from this security change.

In this section:

Supported Upgrade Scenarios [page 125]Your upgrade path to SAP IQ 16.1 SP 02 depends on your current version of SAP IQ.

SAP IQ 16.x Upgrades [page 126]Download and installation instructions for sites running SAP IQ 16.x.

SAP IQ 15.4.x Upgrades [page 130]Download and installation instructions for sites running SAP IQ 15.4.x.

SAP IQ Database Administration Tools [page 189]The SAP IQ database administration tool provides a personalized work center for SAP IQ.

SAP IQ 12.7 Upgrade and Database Migration [page 190]Updating a 12.7 catalog requires a database file migration, not a simple database upgrade. Migration tools bundled with SAP IQ can recreate the legacy database schema and database options.

Hardware Changes [page 227]Perform these steps to move your software to a new hardware platform.

14.1 Supported Upgrade Scenarios

Your upgrade path to SAP IQ 16.1 SP 02 depends on your current version of SAP IQ.

Starting Version Upgrade Scenario

SAP IQ 16.x 1. Perform a full backup of the existing system.2. Upgrade directly to SAP IQ 16.1.x. See SAP IQ 16.x Upgrades [page

126].

SAP IQ Installation and Update Guide [IBM AIX]Upgrade to SAP IQ 16.1 SP 02 P U B L I C 125

Starting Version Upgrade Scenario

SAP IQ 15.4.x 1. Perform a full backup of the existing system.2. Upgrade to SAP IQ 16.1.x. See SAP IQ 15.4.x Upgrades [page 130].3. Verify that the system updated successfully.

SAP IQ 12.7.x 1. Perform a full backup of the existing system.2. Upgrade to SAP IQ 16.1.x. See SAP IQ 16.x Upgrades [page 126]..3. Migrate your 12.7 database. See SAP IQ 12.7 Upgrade and Database Mi

gration [page 190].4. Verify that the system migrated successfully.

14.2 SAP IQ 16.x Upgrades

Download and installation instructions for sites running SAP IQ 16.x.

In this section:

Update SySAM License Server [page 126]If you are using SySAM license server, and are updating from SAP IQ 16.0 SP10 or earlier, you must upgrade SySAM license server before updating SAP IQ.

Initial Steps [page 127]Some steps differ for simplex and multiplex servers. See the cover letter for release-specific instructions.

Installation [page 128]Simplex and multiplex installation procedures.

Database Upgrade [page 128]Upgrade your database before you perform database read-write operations.

Point-in-Time Recovery Changes [page 129]Migrating a database to SP 02 automatically disables point-in-time recovery. To re-enable point-in-time recovery, complete all steps in this procedure, including a FULL, INCREMENTAL, or INCREMENTAL SINCE FULL backup.

14.2.1 Update SySAM License Server

If you are using SySAM license server, and are updating from SAP IQ 16.0 SP10 or earlier, you must upgrade SySAM license server before updating SAP IQ.

SAP IQ 16.1 SP 02 requires SySAM license server 2.4. Use of an obsolete license server with SAP IQ may result in license server startup failure, with the error: FlexNet Licensing error:-5,414.

To verify the current version of SySAM license server, at a command line, enter:

lmgrd -v


Upgrade to SAP IQ 16.1 SP 02

The SySAM server is included in the SAP IQ update package.

See SySAM Users Guide for details on updating.

Related Information

SySAM Users Guide

14.2.2 Initial Steps

Some steps differ for simplex and multiplex servers. See the cover letter for release-specific instructions.

Procedure

1. Download the support package from the SAP Software Download Center .2. Back up your current installation, and save copies of any changes you made to default login and post-login

scripts. Make sure the backups are readable.3. Check with your operating system vendor for information about the latest operating system patches.

Use the recommended operating system patch. Do not use a patch that is earlier than the version suggested for your operating system.

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

5. Validate your license against each database to ensure that your license maintenance support is in (or near) compliance.A server without a maintenance contract for more than a year will not run. Validating your licenses ensures that your database functions correctly after you install the SP. See the SySAM Users Guide for validation procedures.

6. Do one of the following:

Option Description

SAP IQ server Shut down the server.

Multiplex Shut down all multiplex nodes.

7. Uninstall SAP IQ.





14.2.3 Installation

Simplex and multiplex installation procedures.

Procedure

1. Use the appropriate utility to extract the support package to a directory on the file system.2. Install the support package. Do not install to the same directory as other SAP Products. On multiplex

servers, install the support package on each node separately.3. Change to the SAP IQ parent installation directory and execute one of the following:

○ For the tcsh or C (csh) shell, enter:

source ./IQ.csh


source ./IQ.sh

4. In a terminal, change to $IQDIR16/bin64.

5. Check the version string on the server to verify that the support package installed correctly:

start_iq -v2

The results should match the version string in the cover letter.6. Restart the server or multiplex.

14.2.4 Database Upgrade

Upgrade your database before you perform database read-write operations.

Context




Procedure


Option Description

SAP IQ server In the configuration file, set the -gm 1 and -iqro 1 startup flags, then start the SAP IQ 16.1 SP 02 server.

Multiplex In the configuration file, set the -iqmpx_sn 1, -gm 1, and -iqro 1 startup flags, then start the coordinator on the SAP IQ 16.1 SP 02 multiplex.

2. Start Interactive SQL and connect to the database.3. Use ALTER DATABASE UPGRADE to upgrade the database.

ALTER DATABASE UPGRADE instantiates all binaries and schema changes. To roll back to a previous version, you must restore from backup.

4. Run sp_iqcheckdb ('allocation database') to verify that there are no errors.


Option Description

SAP IQ server Shut down and restart the server normally (without the -gm 1 and -iqro 1 startup flags).

Multiplex Shut down and restart the coordinator normally (without the -iqmpx_sn 1, -gm 1, and -iqro 1 startup flags). Synchronize and restart all multiplex secondary servers.

6. Back up the database.

14.2.5 Point-in-Time Recovery Changes

Migrating a database to SP 02 automatically disables point-in-time recovery. To re-enable point-in-time recovery, complete all steps in this procedure, including a FULL, INCREMENTAL, or INCREMENTAL SINCE FULL backup.

Procedure

1. Set the IQ_POINT_IN_TIME_RECOVERY_LOGGING option to ON:

SET OPTION PUBLIC.IQ_POINT_IN_TIME_RECOVERY_LOGGING = 'ON'

2. Identify the directory where you want to open the new point-in-time recovery logs:

ALTER DBSPACE IQ_SYSTEM_LOG RENAME <new-directory-specification>/file-prefix

The <new-directory-specification> must point to an existing directory, and a different location than the existing logs. For multiplex servers, this directory must reside on a shared file system and be writable by all multiplex nodes. ALTER DBSPACE assumes that any string terminated by a slash (Windows) or


backslash (UNIX) in the <new-directory-specification> is a directory name. A terminating string without a slash or backslash is prefixed to the log name.

3. Perform a full data backup:

BACKUP DATABASE ... TO archive_device ...

14.3 SAP IQ 15.4.x Upgrades

Download and installation instructions for sites running SAP IQ 15.4.x.

In this section:

Update SySAM License Server [page 131]If you are using SySAM license server, and are updating from SAP IQ 16.0 SP10 or earlier, you must upgrade SySAM license server before updating SAP IQ.

Before You Begin [page 131]This support package includes changes to the system tables and database schema. Objects no longer supported by SAP IQ 16.1 must be removed or modified before a database upgrade.

Initial Steps [page 132]Some steps differ for simplex and multiplex servers. See the cover letter for release-specific instructions.

Installation [page 132]Simplex and multiplex installation procedures.

Database Upgrade [page 133]Upgrade your database before you perform database read-write operations.

Database Status Post Upgrade [page 134]SAP IQ 16.1 databases upgraded from 15.x are initially set to run in 15.x compatibility mode. You must explicitly change several compatibility settings to complete the upgrade to 16.1.

System Procedures [page 137]Enhanced role-based security changes the way privileged system procedures run.

Logical Servers [page 142]An SAP IQ 16.1 multiplex database upgrade changes the way users access multiplex servers. Starting with SAP IQ 15.4, logical servers provide the only means to access the multiplex server nodes.

Role-Based Security Model [page 142]New SAP IQ 16.1 role-based security replaces the authority-based security model.



14.3.1 Update SySAM License Server

If you are using SySAM license server, and are updating from SAP IQ 16.0 SP10 or earlier, you must upgrade SySAM license server before updating SAP IQ.

SAP IQ 16.1 SP 02 requires SySAM license server 2.4. Use of an obsolete license server with SAP IQ may result in license server startup failure, with the error: FlexNet Licensing error:-5,414.

To verify the current version of SySAM license server, at a command line, enter:

lmgrd -v

The SySAM server is included in the SAP IQ update package.

See SySAM Users Guide for details on updating.

Related Information

SySAM Users Guide

14.3.2 Before You Begin

This support package includes changes to the system tables and database schema. Objects no longer supported by SAP IQ 16.1 must be removed or modified before a database upgrade.

Prerequisites

In SAP IQ 16.1, continuous NBit dictionary compression replaces FP(1), FP(2), and FP(3) byte dictionary compression. Flat FP indexes require more storage space than in earlier releases due to different architecture. Plan for increased storage space requirements.

Procedure

1. Use the DISCONNECT statement to disconnect all users from the 15.x server.2. Drop all JOIN and all LD indexes from the 15.x database.3. Update DATE columns that contain a time portion.

There is a known issue that affects any partition defined on a DATE column that contains a time portion:○ Use ALTER TABLE MERGE to combine the partition with the next partition.○ Use ALTER TABLE SPLIT to divide the resulting partition into a definition with the same criteria, but

no time portion.



4. Drop and re-create all SAP IQ 15.2 TEXT indexes that have not already been dropped and re-created as part of a version 15.2 ESD upgrade.

TEXT indexes created in SAP IQ 15.2 are incompatible with later versions of SAP IQ.5. Shut down the SAP IQ 15.x server or multiplex.

If the server stops responding during shutdown, do not proceed to the next step. Restart the database and shut it down again. Proceed to the next task only on a clean shutdown.

14.3.3 Initial Steps

Some steps differ for simplex and multiplex servers. See the cover letter for release-specific instructions.

Procedure

1. Download the support package from the SAP Software Download Center .2. Back up your current installation, and save copies of any changes you made to default login and post-login

scripts. Make sure the backups are readable.3. Check with your operating system vendor for information about the latest operating system patches.

Use the recommended operating system patch. Do not use a patch that is earlier than the version suggested for your operating system.

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

5. Validate your license against each database to ensure that your license maintenance support is in (or near) compliance.A server without a maintenance contract for more than a year will not run. Validating your licenses ensures that your database functions correctly after you install the SP. See the SySAM Users Guide for validation procedures.

6. Uninstall SAP IQ.

14.3.4 Installation

Simplex and multiplex installation procedures.

Procedure

1. Use the appropriate utility to extract the support package to a directory on the file system.





2. Install the support package. Do not install to the same directory as other SAP Products. On multiplex servers, install the support package on each node separately.

3. Change to the SAP IQ parent installation directory and execute one of the following:○ For the tcsh or C (csh) shell, enter:

source ./IQ.csh


source ./IQ.sh

4. In a terminal, change to $IQDIR16/bin64.

5. Check the version string on the server to verify that the support package installed correctly:

start_iq -v2

The results should match the version string in the cover letter.6. Restart the server or multiplex.

14.3.5 Database Upgrade

Upgrade your database before you perform database read-write operations.

Context


Procedure


Option Description

SAP IQ server In the configuration file, set the -gm 1 and -iqro 1 startup flags, then start the SAP IQ 16.1 SP 02 server.

Multiplex In the configuration file, set the -iqmpx_sn 1, -gm 1, and -iqro 1 startup flags, then start the coordinator on the SAP IQ 16.1 SP 02 multiplex.


2. Start Interactive SQL and connect to the database.3. Use DROP INDEX to drop all LD and JOIN indexes.

4. Upgrade the database.

ALTER DATABASE UPGRADE instantiates all binaries and schema changes. To roll back to a previous version, you must restore from backup.

5. Run sp_iqcheckdb ('allocation database') to verify that there are no errors.


Option Description

SAP IQ server Shut down and restart the server normally (without the -gm 1 and -iqro 1 startup flags).

Multiplex Shut down and restart the coordinator normally (without the -iqmpx_sn 1, -gm 1, and -iqro 1 startup flags). Synchronize and restart all multiplex secondary servers.

7. Back up the database.

14.3.6 Database Status Post Upgrade

SAP IQ 16.1 databases upgraded from 15.x are initially set to run in 15.x compatibility mode. You must explicitly change several compatibility settings to complete the upgrade to 16.1.

Indexes

● Continuous NBit dictionary compression replaces FP(1), FP(2), and FP(3) byte dictionary compression. FP(1), FP(2), and FP(3) indexes roll over to NBit(8), NBit(16), and NBit(24) respectively. All data types except LOB (both character and binary) and BIT data types may be NBit columns.If FP_NBIT_IQ15_COMPATIBILITY is OFF, IQ UNIQUE determines whether the column loads as Flat FP or NBit. .

● New tiered HG index structure decouples load performance from HG index size. In 15.x, load throughput could degrade as the amount of data in an HG index increased. As the index grew, loading the same amount of data could take more time. The new tiered structure decouples load performance from the HG index size to increase throughput.The CREATE_HG_WITH_EXACT_DISTINCTS option determines whether newly created HG indexes are tiered or non-tiered. If this option is ON, all new HG indexes are non-tiered. To take advantage of the new structure, set this option to OFF. Use sp_iqrebuildindex to convert non-tiered HG indexes to tiered HG, and vice versa.

Column Constraints

IQ UNIQUE determines whether the column loads as Flat FP or NBit.

In SAP IQ 16.1, IQ UNIQUE explicitly defines the expected cardinality of a column and determines whether the column loads as Flat FP or NBit. Columns retain their IQ UNIQUE value during a 15.x to 16.1 database upgrade.



Setting IQ UNIQUE to 0 loads the column as Flat FP. Columns without an IQ UNIQUE constraint or columns with an IQ UNIQUE <n> value that is less than the limit defined by the FP_NBIT_AUTOSIZE_LIMIT option is not necessary. Auto-size functionality automatically sizes all low or medium cardinality columns as NBit. Use IQ UNIQUE in cases where you want to where you want to load the column as Flat FP or when you want to load as NBit and the number of distinct values exceeds the auto-size limits.

Database Options

The following database options control NBit behavior and HG indexes.

Option Description

FP_NBIT_IQ15_COMPATIBILITY

Provides tokenized FP support similar to that available in 15.x. This option is ON by default in all 16.1 databases upgraded from 15.x and OFF in all newly created 16.1 databases.

● If this option is ON, the database engine uses the MINIMIZE_STORAGE, FP_LOOKUP_SIZE, and FP_LOOKUP_SIZE_PPM options to optimize column storage. These options are ignored in 16.1.

● If this option is OFF, the database engine ignores 15.x options and columns conform to SAP IQ 16.1 NBit storage options.

Set this option to OFF to take advantage of NBit column compression.

CREATE_HG_WITH_EXACT_DISTINCTS

Determines whether new HG indexes explicitly created with a CREATE INDEX command, or implicitly creating or altering a table with a PRIMARY KEY or a FOREIGN KEY declaration, are tiered or non-tiered. This option is ON in 16.1 databases upgraded from 15.x and all newly created 16.1 databases. If this option is ON, all new HG indexes are non-tiered. To take advantage of the new tiered HG index structure, set this option to OFF.

Use sp_iqrebuildindex to convert non-tiered HG indexes to tiered HG, and vice versa.

CREATE_HG_AND_FORCE_PHYSICAL_DELETE

Governs 16.1 delete behavior for tiered HG indexes. This option determines whether SAP IQ performs a physical delete immediately or defers the delete to a point later in the load.

CREATE_HG_AND_FORCE_PHYSICAL_DELETE is ON by default, which instructs SAP IQ to perform physical deletes.

REVERT_TO_V15_OPTIMIZER

Forces the query optimizer to mimic SAP IQ 15.x behavior. REVERT_TO_V15_OPTIMIZER is ON by default in all 16.1 databases upgraded from 15.x. REVERT_TO_V15_OPTIMIZER is OFF by default in all newly created SAP IQ 16.1 databases.

If you plan to use SAP IQ 16.1 hash partitioning features, set the REVERT_TO_V15_OPTIMIZER to OFF.

Startup Options

Some load operations may require more large memory than the 2 GB default provides. If memory requirements exceed the default, use the -iqlm startup option to increase the memory that SAP IQ can dynamically request from the OS. Set -iqlm as a switch as part of the command or configuration file that starts the server.


As a general rule, large memory requirements represent one third of the total available physical memory allocated to SAP IQ. To ensure adequate memory for the main and temporary IQ stores, set the -iqlm, -iqtc, and -iqmc startup parameters so that each parameter receives one third of all available physical memory allocated to SAP IQ.

In most cases, you should allocate 80% of total physical memory to SAP IQ to prevent SAP IQ processes from being swapped out. Adjust actual memory allocation to accommodate other processes running on the same system. For example, on a machine with 32 cores and 128 GB of total available physical memory, you would allocate 100 GB (approximately 80% of the 12 8GB total) to SAP IQ processes. Following the general rule, you would set the -iqlm, -iqtc, and -iqmc parameters to 33 GB each.

Object Names

Reserved words cannot be used as object names.

An SAP IQ 15.x database could contain tables, columns, and other objects named row. In SAP IQ 16.1, row is a reserved word and cannot be used as an object name.

To use a reserved word as an object name, enclosed the object name in brackets (regardless of the QUOTED_IDENTIFIER setting) or double quotes (if QUOTED_IDENTIFIER='ON' [default]):

// QUOTED_IDENTIFIER ON | OFF select * from [row];alter table row2 rename [row] to col_row;// QUOTED_IDENTIFIER='ON'select "row" from row2; alter table "row" rename rownew;

Stored Procedures

Use these stored procedures to review and change column constraints and indexes.

Procedure Name Description

sp_iqcolumnmetadata Returns index metadata for all columns in one or more tables.

sp_iqindexmetadata Returns details about column indexes, including the index types (Flat FP, NBit, HG, and tiered HG), distinct counts, IQ UNIQUE value, and NBit dictionary size.



Procedure Name Description

sp_iqrebuildindex Rebuilds FP indexes (Flat FP as NBit, or NBit as Flat FP) and HG indexes (single HG as tiered HG, or tiered HG as single HG). Before you can insert or update new data, you must rebuild all columns greater than 255 bytes wide.

The index_clause can reset IQ UNIQUE <n> to an explicit value from 0 (to recast an NBit column to Flat FP) up to the limits defined in the FP_NBIT_AUTOSIZE_LIMIT and FP_NBIT_LOOKUP_MB options.

sp_iqrebuildindex also enables read-write access to columns that contain large object (LOB) data. LOB columns migrated from 15.x databases are read-only until you run sp_iqrebuildindex.

The estimated cardinality for NBit columns with an IQ UNIQUE value below or equal to the FP_NBIT_AUTOSIZE_LIMIT is stored as 0 regardless of the FP_NBIT_IQ15_COMPATIBILITY setting. This affects the value returned from sp_iqindexmetadata.

sp_iqindexrebuildwidedata

Identifies wide columns that you must rebuild before they are available for read/write activities. sp_iqindexrebuildwidedata also generates a list of statements that you can use to rebuild the columns.

This applies to CHAR, VARCHAR, BINARY, and VARBINARY columns wider than 255 characters, as well as all Long Varchar and Long Binary columns.

Related Information

sp_iqcheckdb Proceduresp_iqcolumnmetadata Proceduresp_iqindexmetadata Proceduresp_iqrebuildindex Proceduresp_iqrebuildindexwide Procedure

14.3.7 System Procedures

Enhanced role-based security changes the way privileged system procedures run.

In this section:

System Procedure Changes [page 138]Prior to SAP IQ 16.1, privileged system procedures ran with the privileges of its owner, typically the dbo system role; this is called the SYSTEM PROCEDURE DEFINER model. In 16.x, privileged system procedures run with the privileges of the person executing it; this is called the SYSTEM PROCEDURE INVOKER model.

Pre- 16.x Privileged System Procedures [page 139]A list of pre- 16.x privileged system procedures.

Regrant EXECUTE Privilege [page 141]


https://help.sap.com/viewer/a898e08b84f21015969fa437e89860c8/16.1.2.14/en-US/a59d2e0484f21015922aa8b764f89495.html

https://help.sap.com/viewer/a898e08b84f21015969fa437e89860c8/16.1.2.14/en-US/a87e284f84f21015b893da0ff4572d65.html

https://help.sap.com/viewer/a898e08b84f21015969fa437e89860c8/16.1.2.14/en-US/a5ad0e4b84f21015866c8fef1c8fee50.html

https://help.sap.com/viewer/a898e08b84f21015969fa437e89860c8/16.1.2.14/en-US/a5b342e484f21015b652c2f5c7685bca.html

https://help.sap.com/viewer/a898e08b84f21015969fa437e89860c8/16.1.2.14/en-US/a8838e9184f21015b8ded62c34f2a3ee.html

When you upgrade a database, there is a set of privileged system procedures for which you must regrant the EXECUTE privilege if the upgraded database continues to use the SYSTEM PROCEDURE DEFINER security model.

14.3.7.1 System Procedure Changes

Prior to SAP IQ 16.1, privileged system procedures ran with the privileges of its owner, typically the dbo system role; this is called the SYSTEM PROCEDURE DEFINER model. In 16.x, privileged system procedures run with the privileges of the person executing it; this is called the SYSTEM PROCEDURE INVOKER model.

NoteThis behavior change applies to SAP IQ privileged system procedures only, and not to user-defined stored procedures.

In the SYSTEM PROCEDURE DEFINER model, when you grant a user explicit EXECUTE object-level privilege on a system procedure, any privileges required to run any authorized tasks associated with the system procedure are automatically inherited from the owner (definer of the system procedure).

In the SYSTEM PROCEDURE INVOKER model, the EXECUTE object-level privilege for each system procedure is granted to the PUBLIC role. Since, by default, every user is a member of the PUBLIC role, every user automatically inherits the required EXECUTE object-level privilege. Any additional system privileges needed to run the system procedure are not inherited; you must now directly or indirectly grant them to the user.

This behavior change might create a loss of functionality on custom stored procedures and applications that explicitly grant EXECUTE object-level privilege on system procedures. For this reason, the default upgrade process for pre- 16.x database uses a combination of the two models. Privileged system procedures that existed in IQ versions earlier than 16.x continue to run using the SYSTEM PROCEDURE DEFINER model, while any privileged system procedures introduced in 16.x or later use the SYSTEM PROCEDURE INVOKER model.

You can override the default upgrade behavior so that all privileged system procedures for all versions use only the SYSTEM PROCEDURE INVOKER model if the potential loss of functionality is not a concern. If you are unsure of potential loss of functionality, upgrade your database to use the default behavior, then investigate. If you determine that it is not an issue, and you want all system procedures to run using the SYSTEM PROCEDURE INVOKER model, use the ALTER DATABASE statement to change the default security model. When you override the default upgrade behavior, the EXECUTE object-level privilege to run privileged system procedures is revoked from all users and roles and granted to the PUBLIC role.

To specify a security model, use the CREATE DATABASE statement, ALTER DATABASE UPGRADE statement, or the Initialization utility (iqinit).

Once a database is upgraded to SAP IQ 16.1, the default upgrade behavior for any subsequent upgrades (for example to 16.1 SP 02, SP 03, and so on) is to continue to use the current security model.

There is a small subset of pre- 16.x privileged system procedures that has always run with the privileges of the user running the procedure, rather than the owner of the procedure. In addition to EXECUTE object-level privilege on the system procedure, you must be granted additional system privileges that are specific to the system procedure.

When running privileged system procedures using the SYSTEM PROCEDURE DEFINER model, the DBO system role is typically the owner of the procedures. By default, the dbo system role is granted the SYS_AUTH_DBA_ROLE compatibility role. This ensures that the role is indirectly granted all privileges



necessary to execute system procedures. Migrating the SYS_AUTH_DBA_ROLE compatibility role can result in the dbo system role losing the ability to execute privileged system procedures. See Implications of Migrating Compatibility Roles [page 187] for details.

14.3.7.2 Pre- 16.x Privileged System Procedures

A list of pre- 16.x privileged system procedures.

Privileged System Procedures Using the Combined Security Model

For these privileged system procedures, if the database is configured to use SYSTEM PROCEDURE DEFINER, you only need EXECUTE object-level privilege on the procedure to run it. If the database is configured to use SYSTEM PROCEDURE INVOKER, you also need the individual system privileges required by each procedure. Refer to the SAP IQ SQL Reference Guide for the system privileges required to run each system procedure.


● sa_audit_string● sa_checkpoint_execute● sa_disable_auditing_type● sa_disk_free_space● sa_enable_auditing_type● sa_external_library_unload● sa_flush_cache● sa_list_external_library● sa_server_option● sa_procedure_profile● sa_procedure_profile_summary● sa_table_page_usage● sa_validate

● sp_iq_reset_identity● sp_iqaddlogin● sp_iqbackupdetails● sp_iqbackupsummary● sp_iqcardinality_analysis● sp_iqcheckdb● sp_iqcheckoptions● sp_iqclient_lookup● sp_iqcolumn● sp_iqcolumnuse● sp_iqconnection● sp_iqconstraint● sp_iqcontext● sp_iqconstraint● sp_iqcontext● sp_iqcursorinfo● sp_iqdatatype● sp_iqdbsize

● sp_iqdbspace● sp_iqdbspaceinfo● sp_iqdbspaceobjectinfo● sp_iqdbstatistics● sp_iqdroplogin● sp_iqemptyfile● sp_iqestdbspaces● sp_iqestspace● sp_iqevent● sp_iqfile● sp_iqhelp● sp_iqindex● sp_iqindex_alt● sp_iqindexadvice● sp_iqindexfragmentation● sp_iqindexinfo● sp_iqindexmetadata● sp_iqindexsize● sp_iqindexuse● sp_iqlmconfig● sp_iqlocks● sp_iqmodifyadmin● sp_iqmodifylogin● sp_iqmpxcheckdqpconfig● sp_iqmpxdumptlvlog● sp_iqmpxfilestatus● sp_iqmpxincconnpoolinfo● sp_iqmpxincheartbeatinfo● sp_iqcopyloginpolicy● sp_iqmpxincconnpoolinfo● sp_iqmpxincheartbeatinfo

● sp_iqmpxinfo● sp_iqmpxversioninfo● sp_iqobjectinfo● sp_iqpkeys● sp_iqprocedure● sp_iqprocparm● sp_iqrebuildindex● sp_iqrename● sp_iqrestoreaction● sp_iqrowdensity● sp_iqsetcompression● sp_iqsharedtempdistrib● sp_iqshowcompression● sp_iqshowpsexe● sp_iqspaceinfo● sp_iqspaceused● sp_iqstatistics● sp_iqstatus● sp_iqsysmon● sp_iqtable● sp_iqtablesize● sp_iqtableuse● sp_iqtransaction● sp_iqunusedcolumn● sp_iqunusedindex● sp_iqunusedtable● sp_iqversionuse● sp_iqview● sp_iqwho● sp_iqworkmon

Privileged System Procedures Using Invoker Privileges

These pre- 16.x privileged system procedures run with the privileges of the user who is running the procedure, not the owner of the procedure, regardless of the security model setting. Therefore, in addition to the EXECUTE object-level privilege on the system procedure, which is, by default, granted through membership in PUBLIC role, you must also be granted the additional system privileges required by the system procedure. Refer to the SAP IQ SQL Reference Guide for the system privileges required to run each system procedure.

● sa_describe_shapefile● sa_get_user_status● sa_locks● sa_performance_diagnostics● sa_report_deadlocks● sa_text_index_stats



14.3.7.3 Regrant EXECUTE Privilege

When you upgrade a database, there is a set of privileged system procedures for which you must regrant the EXECUTE privilege if the upgraded database continues to use the SYSTEM PROCEDURE DEFINER security model.

The system procedures for which you must regrant the privilege are:

● sa_audit_string● sa_checkpoint_execute● sa_disable_auditing_type● sa_disk_free_space● sa_enable_auditing_type● sa_external_library_unload● sa_flush_cache● sa_list_external_library● sa_server_option● sa_procedure_profile● sa_procedure_profile_summary● sa_table_page_usage● sa_validate

To determine the security model of your upgraded database, execute:

select IF ((HEXTOINT(substring(db_property('Capabilities'),1,length(db_property('Capabilities'))-20)) & 8) = 8) THEN 1ELSE 0END IF

A value of 1 indicates the database is using the SYSTEM PROCEDURE INVOKER model. A value of 0 indicates that the database is using the SYSTEM PROCEDURE DEFINER.

The MANAGE ANY OBJECT PRIVILEGE system privilege is required to grant the EXECUTE object-level privilege.

To grant the privilege, execute:

GRANT EXECUTE ON [ owner.] {<procedure-name> | <user-defined-function-name> } TO <userID [,...]>

Related Information

Pre- 16.x Privileged System Procedures [page 139]


14.3.8 Logical Servers

An SAP IQ 16.1 multiplex database upgrade changes the way users access multiplex servers. Starting with SAP IQ 15.4, logical servers provide the only means to access the multiplex server nodes.

Upgrading a multiplex database creates an appropriate logical server for each server-specific login policy. Login policies are updated to use a logical server configuration that provides access to the same set of multiplex servers as prior to upgrade.

If a login policy does not allow access to any node (such as when the base setting of LOCKED is ON and there are no multiplex server-level overrides), the login policy is set to a system-defined logical server, NONE, instead of creating a new logical server. NONE indicates that the login policy does not allow access to any multiplex server.

If a login policy has no explicit setting for the LOCKED option, either at the base level or via a multiplex server-level override, no logical server is created for that policy. Such a login policy inherits the logical server assignment of the root login policy.

● Membership configuration of a logical server provides access to the same multiplex nodes as the corresponding 15.x login policy. If the login policy allowed access to the current coordinator server, a logical membership of the coordinator is also added to the logical server.

● Logical server names are derived from login policy names. If the login policy name is fewer than 126 characters, the logical server follows this naming convention: LS_<login policy name>. For example, for a login policy named mpx_grp1, a logical server LS_mpx_grp1 is created and assigned to that login policy.If the login policy name exceeds 125 characters, a logical server is created with the same name as of the login policy, that is, without adding an LS_ prefix.

● During the upgrade, some login policy option settings or multiplex server-level overrides are reset or removed. In the root login policy, LOCKED and MAX_CONNECTIONS overrides are reset to default values ( 'OFF' and 10 respectively).Settings for LOCKED and MAX_CONNECTIONS are removed from user-defined login policies. Multiplex server-level overrides are removed from all login policies.

● To retain pre-upgrade behavior for existing applications, the login policy option LOGIN_REDIRECTION is added to the root logical server policy with its value set to off.

See Manage Resources Through Logical Servers in SAP IQ Administration: Multiplex.

14.3.9 Role-Based Security Model

New SAP IQ 16.1 role-based security replaces the authority-based security model.

In this section:

What Happened to Authorities, Permissions, and Groups? [page 144]SAP IQ 16.x introduces a role-based security model. Earlier versions used authorities, permissions, object-level permissions, and groups. The role-based security model uses roles, system privileges, object-level privileges, and user-extended roles.

Authorities Become Compatibility Roles [page 145]



When you upgrade to 16.1, users who are granted authorities in the earlier version are automatically granted an equivalent compatibility role. If the user previously had the ability to administer the authority, he or she has the ability to administer the compatibility role in 16.0.

Permissions Become Privileges [page 146]SAP IQ versions earlier than 16.x used object-level permissions such as ALTER and SELECT for tables and views. These permissions are now called object-level privileges.

Groups Become Roles [page 146]When you upgrade an IQ database earlier than 16.0, each group is converted to an equivalent user-extended role of the same name. Members of the original group are automatically granted the new role and all of its underlying system privileges. Authorities and object-level permissions granted to the original group are converted to equivalent compatibility roles and system privileges and are granted to the user-extended role.

Change to Concept of a Super-User (DBA Authority) [page 147]In SAP IQ versions earlier than 16.x, the DBA user was often considered a super-user by virtue of being granted the DBA authority. The DBA user continues to exist in 16.x, however, the concept has changed.

Changes to the GRANT Statement Syntax [page 148]The GRANT syntax for authorities, permissions, and groups is supported, but deprecated. If you have applications that use the pre- 16.x GRANT statement syntax, modify them to use the new syntax for roles and privileges.

Changes to the REVOKE Statement Syntax [page 150]The REVOKE syntax for authorities, permissions, and groups is supported but deprecated. If you have applications that use the pre- 16.x REVOKE statement syntax, modify them to use the new syntax for roles and privileges.

Changes to REMOTE DBA [page 152]The REMOTE DBA authority is replaced by the SYS_RUN_REPLICATION_ROLE system role. This role allows user to administer replication.

Changes in Inheritance Behavior [page 152]In SAP IQ versions earlier than 16.0, when you granted the DBA, REMOTE DBA, BACKUP, RESOURCE, and VALIDATE authorities to a group, the underlying permissions were not inherited by members of the group.

Changes in Administering the Database Publisher [page 153]In 16.x, the PUBLISH authority is replaced by the PUBLIC.db_publisher database option. You change the publisher by changing the database option.

Compatibility Roles [page 153]Compatibility roles exist for backward compatibility with versions of SAP IQ earlier than 16.0. that support authority-based security.

Backward Compatibility in SAP IQ 16.1 [page 188]Grant and revoke syntax for role-based security differs significantly from authority-based security. However, SAP IQ 16.1 is fully backward compatible with authority-based syntax.

Stored Procedure to Map Authorities to System Roles [page 189]The sp_auth_sys_role_info stored procedure generates a report, which maps each authority to a corresponding system role name.

Connecting to SAP IQ 15.x Databases with SAP IQ 16.x [page 189]Role-based syntax is not supported in SAP IQ 15.x databases.


14.3.9.1 What Happened to Authorities, Permissions, and Groups?

SAP IQ 16.x introduces a role-based security model. Earlier versions used authorities, permissions, object-level permissions, and groups. The role-based security model uses roles, system privileges, object-level privileges, and user-extended roles.

NoteYou can use an SAP IQ 16.x server with an IQ database from an earlier version (pre- 16.x). When you do, full backward compatibility is provided for that database, and its security model is not changed.

In pre- 16.x, authorities are database-level permissions. For example, a user with BACKUP authority can back up the database. Some authorities bundle object-level permissions. For example, a user with PROFILE authority can perform application profiling and database tracing tasks, which involve using system procedures that are not otherwise available for use. You cannot create new authorities, alter the permissions they comprised, or drop them. You can grant administrative rights (WITH GRANT), but cannot limit the grant to administrator rights only.

In 16.x, roles replace authorities, with the added benefit that you can create new roles, alter the system privileges granted, and drop them. Roles and privileges provide a more granular control when granting system privileges to users. You can also grant roles to users with administrative rights only. A user can then grant and revoke the role, but cannot exercise the underlying privileges.

In pre- 16.x, permissions allowed you to create, modify, query, use, or delete database objects such as tables, views, and users.

In 16.x, system privileges replace permissions in functionality. Every privileged operation that you can perform on a database object now has a grantable system privilege. You can grant system privileges individually to users or to a role.

In 16.x, the meaning of permissions has changed. In pre- 16.x versions, a permission meant a grantable capability. Now, permission means the result of an evaluation of whether an operation can be performed. For example, you have permission to alter the table if you are the owner or you have the ALTER ANY TABLE system privilege.

In pre- 16.x, groups were a collection of one or more users whose authorities and permissions were determined at the group level. A user was granted group status, and then other users were granted membership in that group.

In 16.x, the group paradigm is achieved using user-extended roles. If you have a user with a set of privileges that you want to grant to other users, you extend the user to become a user-extended role, and then grant that role to other users.

Upgrading a pre- 16.x database automatically converts your existing authority, permission, and group hierarchy into an equivalent role, privilege, and user-extended role hierarchy. Every pre- 16.x authority has a compatibility role. These roles are easily identifiable because their names start with SYS_AUTH. Compatibility roles contain the system privileges required to perform the same operations as the corresponding previous authority.

To take full advantage of the control and granularity of privileges available with role-based security, SAP recommends that, after migration, you review the compatibility role grants of each user and adjust membership and system privilege grants as necessary.



14.3.9.2 Authorities Become Compatibility Roles

When you upgrade to 16.1, users who are granted authorities in the earlier version are automatically granted an equivalent compatibility role. If the user previously had the ability to administer the authority, he or she has the ability to administer the compatibility role in 16.0.

The naming convention for each compatibility role retains the original authority name, but is prefaced with "SYS_AUTH_" and suffixed with "_ROLE". For example, the authority BACKUP becomes the role SYS_AUTH_BACKUP_ROLE, authority RESOURCE becomes role SYS_AUTH_RESOURCES_ROLE, and so on.

You cannot modify compatibility roles. However, you can migrate them to a user-defined role, and then modify them. When you migrate a compatibility role to a user-defined role, all users who are granted the compatibility role are granted the new user-defined role. Once each underlying system privilege is granted to at least one other role, you can drop the compatibility role. To restore compatibility roles, use the CREATE ROLE statement.

SQL statements are backward compatibility to support applications that grant or revoke authorities. However, the old syntax is deprecated and SAP recommends that you changed your applications to use the new SQL syntax for roles.

This table shows each authority and its equivalent compatibility role.

Authority Compatibility Role Description

BACKUP SYS_AUTH_BACKUP_ROLE

Allows a user to back up databases and transaction logs with archive or image backups by using the BACKUP DATABASE statement or dbbackup utility.

DBA SYS_AUTH_DBA_ROLE

SYS_AUTH_SA_ROLE

SYS_AUTH_SSO_ROLE

Allows users to perform all possible privileged operations. Users with the SYS_AUTH_DBA_ROLE role can create database objects and assign ownership of these objects to other user IDs, change table structures, create new user IDs, revoke permissions from users, back up the database, and so on.

Of the possible privileged operations that the SYS_AUTH_DBA_ROLE compatibility role can perform, the SYS_AUTH_SA_ROLE compatibility role allows the user to perform all database administration-related activities, such as creating tables, and backing up data.

Of the possible privileged operations that the SYS_AUTH_DBA_ROLE compatibility role can perform, the SYS_AUTH_SSO_ROLE compatibility role allows the user to perform the security and access-related administration activities, such as creating users, and granting privileges on objects.

PROFILE SYS_AUTH_PROFILE_ROLE

Allows a user to perform profiling, tracing, and diagnostic operations.

READCLIENTFILE SYS_AUTH_READCLIENTFILE_ROLE

Allows a user to read files on the client computer, for example when loading data from a file on a client computer.

READFILE SYS_AUTH_READFILE_ROLE

Allows a user to use the OPENSTRING clause in a SELECT statement to read a file.


Authority Compatibility Role Description

REMOTE DBA SYS_RUN_REPLICATION_ROLE system role

SYS_REPLICATION_ADMIN_ROLE system role

Allows a SQL Remote user to perform replication activities by using the dbremote and dbmisync utilities. It does not, however, allow administration of replication.

The SYS_REPLICATION_ADMIN_ROLE system role is provided for replication administration.

RESOURCE SYS_AUTH_RESOURCE_ROLE

Allows a user to create database objects, such as tables, views, stored procedures, and triggers.

VALIDATE SYS_AUTH_VALIDATE_ROLE

Allows a user to perform database, table, index, and checksum validation by using the VALIDATE statement or dbvalid utility.

WRITECLIENTFILE SYS_AUTH_WRITECLIENTFILE_ROLE

Allows a user to write to files on a client computer, for example, when using the UNLOAD TABLE statement to write data to a client computer.

WRITEFILE SYS_AUTH_WRITEFILE_ROLE

Allows a user to execute the xp_write_file system procedure.

In an authority-based security model, there was no way to limit the grant if a user did not need all of the permissions vested in an authority. This resulted in users often being granted more permissions than necessary, a potential security concern. The role-based security model addresses this concern by allowing system privileges to be granted at a granular level.

Since the migration process ensures that all existing privileges are preserved at the user and group level, SAP recommends that, after migration, you review the compatibility role grants for each user and adjust membership as necessary.

14.3.9.3 Permissions Become Privileges

SAP IQ versions earlier than 16.x used object-level permissions such as ALTER and SELECT for tables and views. These permissions are now called object-level privileges.

When you upgrade your database, users granted permissions are automatically granted the equivalent object-level privileges.

SQL statements that grant or revoke object-level permissions/privileges still work.

In addition to object-level privileges, there are now grantable system privileges for every authorized operation.

14.3.9.4 Groups Become Roles

When you upgrade an IQ database earlier than 16.0, each group is converted to an equivalent user-extended role of the same name. Members of the original group are automatically granted the new role and all of its underlying system privileges. Authorities and object-level permissions granted to the original group are converted to equivalent compatibility roles and system privileges and are granted to the user-extended role.



If an authority was inheritable, grantees of the new user-extended role inherit the underlying system privileges of the equivalent compatibility role. If the authority was not inheritable, the grantees of the user-extended role do not inherit the underlying system privileges of the equivalent compatibility role. If the legacy group had a password, only the extended user of the user-extended role inherits the underlying system privileges of the compatibility role that is not inheritable.

System groups become system roles with the same name.

Group/System Role Description

dbo This role owns many system stored procedures, views, and tables.

diagnostics This role owns the diagnostic tables and views, and can perform operations on them.

PUBLIC This role has SELECT permission on the system tables. Any new user ID is automatically granted the PUBLIC role.

ra_systabgroup This role allows users to perform replication server functionality.

SYS This role owns the system tables and views (IQ catalog) for the database, and can perform operations on them.

SYS_SPATIAL_ADMIN_ROLE This role allows users to create, alter, or drop spatial objects.

14.3.9.5 Change to Concept of a Super-User (DBA Authority)

In SAP IQ versions earlier than 16.x, the DBA user was often considered a super-user by virtue of being granted the DBA authority. The DBA user continues to exist in 16.x, however, the concept has changed.

In SAP IQ versions earlier than 16.x, you created a super-user by granting a user DBA authority. Users with DBA authority can perform any privileged task in the system. When you upgrade your database to 16.x, any users granted DBA authority are granted the equivalent SYS_AUTH_DBA_ROLE compatibility role and become a super-user. After migration, the super-user itself must be managed to preserve its super-user abilities.

When you create a new role without specify an administrator, users with the MANAGE ROLES system privilege (global administrators) can administer the role. Since MANAGE ROLES is one of the system privileges granted to the SYS_AUTH_DBA_ROLE compatibility role, super-users can administer new roles.

However, if you create a new role and assign administrators, administration is then limited to only those administrators; global administrators, and thus super-users, cannot administer the role. You must explicitly assign the super-user as an administrator of the role.

You can migrate the SYS_AUTH_DBA_ROLE compatibility role to a user-defined role, and eventually drop it. Since the ability of the super-user to perform any privileged task is dependent on the SYS_AUTH_DBA_ROLE compatibility role, before you drop the SYS_AUTH_DBA_ROLE compatibility role, you must grant the super-user membership in the new user-defined role or grant each of the underlying system privileges directly or indirectly to the super-user.


14.3.9.6 Changes to the GRANT Statement Syntax

The GRANT syntax for authorities, permissions, and groups is supported, but deprecated. If you have applications that use the pre- 16.x GRANT statement syntax, modify them to use the new syntax for roles and privileges.

In SAP IQ versions earlier than 16.x, DBA, REMOTE DBA, RESOURCE, and VALIDATE authorities were not inheritable. When you upgrade your database to 16.x, the WITH NO SYSTEM PRIVILEGE INHERITANCE clause ensures that inheritance behavior remains consistent with earlier releases.

Users granted DBA and REMOTE DBA authorities could grant them to others. In 16.x, the WITH ADMIN clause is introduced to ensure that administration rights behavior remains consistent with previous releases.

Table 1: Non-Inheritable Authorities

Pre- 16.x Syntax New Syntax

GRANT DBA TO <grantee>[,...] > GRANT ROLE SYS_AUTH_DBA_ROLE TO <grantee> [,...]>

WITH ADMIN OPTION

WITH NO SYSTEM PRIVILEGE INHERITANCE

GRANT REMOTE DBA TO <grantee>[,...]> GRANT ROLE SYS_RUN_REPLICATION_ROLE TO <grantee> [,...]>

WITH NO ADMIN OPTION


GRANT BACKUP TO <grantee>[,...]> GRANT ROLE SYS_AUTH_BACKUP_ROLE TO <grantee> [,...] >


GRANT RESOURCE TO <grantee>[,...] > GRANT ROLE SYS_AUTH_RESOURCE_ROLE TO <grantee> [,...]>


GRANT VALIDATE TO <grantee>[,...]> GRANT ROLE SYS_AUTH_VALIDATE_ROLE TO <grantee> [,...]>


Table 2: Inheritable Authorities


GRANT Multiplex Admin TO <grantee> [,...]> GRANT ROLE SYS_AUTH_MULTIPLEX_ADMIN_ROLE TO <grantee> [,...] >

GRANT Operator TO <grantee> [,...]> GRANT ROLE SYS_AUTH_OPERATOR_ROLE TO <grantee> [,...]>




GRANT Perms Admin TO <grantee> [,...]> GRANT ROLE SYS_AUTH_PERMS_ADMIN_ROLE TO <grantee> [,...]>

GRANT PROFILE TO <grantee> [,...]> GRANT ROLE SYS_AUTH_PROFILE_ROLE TO <grantee> [,...]>

GRANT READCLIENTFILE TO <grantee> [,...]> GRANT ROLE SYS_AUTH_READCLIENTFILE_ROLE TO <grantee> [,...]>

GRANT READFILE TO <grantee> [,...]> GRANT ROLE SYS_AUTH_READFILE_ROLE TO <grantee> [,...]>

GRANT Space Admin TO <grantee> [,...]> GRANT ROLE SYS_AUTH_SPACE_ADMIN_ROLE TO <grantee> [,...]>

GRANT Spatial Admin TO <grantee> [,...]> GRANT ROLE SYS_AUTH_SPATIAL_ADMIN_ROLE TO <grantee> [,...]>

GRANT WRITECLIENTFILE TO <grantee> [,...]> GRANT ROLE SYS_AUTH_WRITECLIENTFILE_ROLE TO <grantee> [,...]>

GRANT WRITEFILE TO <grantee> [,...]> GRANT ROLE SYS_AUTH_WRITEFILE_ROLE TO <grantee> [,...]>

GRANT CONNECT TO <username>

[ IDENTIFIED BY <pwd> ]

No change

GRANT GROUP TO <user> CREATE OR REPLACE <rolename>

FOR USER <user>

GRANT MEMBERSHIP IN GROUP <groupname>[,...]>

TO <grantee>[,...]>

GRANT ROLE <groupname>[,...] >

TO <grantee>[,...]>

GRANT PUBLISH TO <grantee> No change; however, you can also set the new PUBLIC option, db_publisher:

SET OPTION PUBLIC.db_publisher=<grantee_id>



GRANT <permission>[,...]>

ON <[ owner.]object-name>

TO <grantee>[,...]>

[ WITH GRANT OPTION ]

<permission>:

ALL [ PRIVILEGES ]

| ALTER

| DELETE

| INSERT

| REFERENCES [ ( column-name, ...) ]

| SELECT [ ( column-name, ... ) ]

| UPDATE [ ( column-name, ... ) ]

No change

GRANT EXECUTE ON <[owner.]{ procedure-name | user-defined-function >}

TO <grantee>[,...] >

No change

GRANT INTEGRATED LOGIN TO <user-profile-name>[,...]>

AS USER <user>

No change

GRANT KERBEROS LOGIN

TO <client-Kerberos-principal [, …] >

AS USER <user>

No change

GRANT CREATE ON <dbspacename> [,...]>

TO <grantee> [,...]>

No change

14.3.9.7 Changes to the REVOKE Statement Syntax

The REVOKE syntax for authorities, permissions, and groups is supported but deprecated. If you have applications that use the pre- 16.x REVOKE statement syntax, modify them to use the new syntax for roles and privileges.


REVOKE CONNECT FROM <user> No change




REVOKE <permission>[,...]>

ON

<[ owner.]object-name>

FROM <grantee>[,...]>

<permission>:

ALL [ PRIVILEGES ]

| ALTER

| DELETE

| INSERT

| REFERENCES [ ( column-name, ...) ]

| SELECT [ ( column-name, ... ) ]

| UPDATE [ ( column-name, ... ) ]

No change, except to naming convention. Object-level permissions are now object-level privileges.

REVOKE EXECUTE ON [ <owner.]{ procedure-name | user-defined-function> }

FROM <grantee> <[,...] >

No change

REVOKE INTEGRATED LOGIN FROM <user> No change

REVOKE KERBEROS LOGIN FROM <user> <[,...] >

AS USER <user>

No change

REVOKE CREATE ON <dbspacename> [,...]> FROM <grantee> [,...] >

No change

14.3.9.8 Changes to REMOTE DBA The REMOTE DBA authority is replaced by the SYS_RUN_REPLICATION_ROLE system role. This role allows user to administer replication.

The GRANT REMOTE DBA statement syntax is still supported but deprecated. Change your applications to grant this new role.

14.3.9.9 Changes in Inheritance BehaviorIn SAP IQ versions earlier than 16.0, when you granted the DBA, REMOTE DBA, BACKUP, RESOURCE, and VALIDATE authorities to a group, the underlying permissions were not inherited by members of the group.

In 16.0, the default behavior when granting SYS_AUTH_DBA_ROLE, SYS_RUN_REPLICATION_ROLE, SYS_AUTH_BACKUP_ROLE, SYS_AUTH_RESOURCE_ROLE, and SYS_AUTH_VALIDATE_ROLE (formerly DBA,



REMOTE DBA, BACKUP, RESOURCE, and VALIDATE) to a user-defined role allows members of the user-defined role to inherit the underlying system privileges of the role. The WITH NO SYSTEM INHERITANCE clause retains the non-inheritance behavior.

To retain the non-inheritance behavior of these roles after upgrading, include the WITH NO SYSTEM PRIVILEGE INHERITANCE clause in the GRANT ROLE statement, if you have applications that you are changing to use the new GRANT syntax, and want to preserve the non-inheritance behavior.

NoteThe WITH NO SYSTEM PRIVILEGE INHERITANCE clause is supported only with these specific roles; any other use results in an error.

For example, you grant User1 the ALTER ANY OBJECT system privilege. You extend User1 to become a role and grant User1 to User2. You want to grant the SYS_AUTH_DBA_ROLE role to User1, but you do not want User2 to inherit the system privileges vested to SYS_AUTH_DBA_ROLE. Execute:

GRANT ROLE SYS_AUTH_DBA_ROLE TO User1 WITH NO SYSTEM PRIVILEGE INHERITANCE;

14.3.9.10 Changes in Administering the Database Publisher

In 16.x, the PUBLISH authority is replaced by the PUBLIC.db_publisher database option. You change the publisher by changing the database option.

In IQ versions earlier than 16.x, the database publisher was controlled by using the GRANT PUBLISH and REVOKE PUBLISH statements. You determine the current publisher by querying the CURRENT PUBLISHER special value. The GRANT PUBLISH and REVOKE PUBLISH syntax is still supported, but deprecated.

You can also still query the CURRENT PUBLISHER to determine the current publisher.

The SET ANY SYSTEM OPTION system privilege is required to set PUBLIC.db_publisher.

14.3.9.11 Compatibility Roles

Compatibility roles exist for backward compatibility with versions of SAP IQ earlier than 16.0. that support authority-based security.

You can grant, revoke, and under specific conditions, delete compatibility roles. You cannot modify any of the underlying system privileges. However, you can migrate compatibility roles to user-defined roles, and then modify the underlying system privileges. When you migrate a compatibility role, all grantees of the compatibility role are automatically granted the user-defined role.

Use the compatibility roles SYS_AUTH_SA_ROLE and SYS_AUTH_SSO_ROLE to administer and grant all individual system privileges in a new database. The union of the system privileges of these two roles is granted to the compatibility role SYS_AUTH_DBA_ROLE. By default, SYS_AUTH_DBA_ROLE is granted to the DBA user with administrative privileges. Thus, all system privileges are initially granted to the DBA user.

You can grant users to, and revoke users from, compatibility roles.


In this section:

Grant Compatibility Roles [page 154]Granting a compatibility role is semantically equivalent to granting each of its underlying system privileges and roles.

Revoking a Compatibility Role [page 184]Revoke a compatibility role from a user or role.

Migrating a Compatibility Role [page 184]Migrate all underlying system privileges of a compatibility role to a user-defined role.

Dropping a Compatibility Role [page 186]All compatibility roles, with the exception of SYS_AUTH_SA_ROLE and SYS_AUTH_SSO_ROLE can be dropped. SYS_AUTH_SA_ROLE and SYS_AUTH_SSO_ROLE are automatically dropped when SYS_AUTH_DBA_ROLE is dropped.

Re-creating a Compatibility Role [page 187]Re-creates a dropped compatibility role.

Implications of Migrating Compatibility Roles [page 187]Some system roles are indirectly granted the system privileges necessary to execute privileged tasks through membership in compatibility roles.

14.3.9.11.1 Grant Compatibility Roles

Granting a compatibility role is semantically equivalent to granting each of its underlying system privileges and roles.

In this section:

Granting SYS_AUTH_SA_ROLE [page 155]Allows users to perform authorized tasks pertaining to data and system administration responsibilities.

Granting SYS_AUTH_SSO_ROLE [page 158]Allows users to perform authorized tasks pertaining to security and access control responsibilities.

Granting SYS_AUTH_DBA_ROLE [page 160]Allows users to perform all authorized tasks.

Granting SYS_AUTH_BACKUP_ROLE [page 164]Allows users to perform all backups.

Granting SYS_AUTH_MULTIPLEX_ADMIN_ROLE [page 166]Allows users to perform authorized tasks to manage multiplex.

Granting SYS_AUTH_OPERATOR_ROLE [page 167]Allows users to checkpoint databases, drop connections (including those for users with SYS_AUTH_DBA_ROLE), back up databases, and monitor the system.

Granting SYS_AUTH_PERMS_ADMIN_ROLE [page 169]Allows users to manage data privileges, groups, authorities, and passwords.

Granting SYS_AUTH_PROFILE_ROLE [page 171]Allows users to enable or disable server tracing for application profiling.

Granting SYS_AUTH_READFILE_ROLE [page 172]



Allows users to read to a file that is resident on the server machine.

Granting SYS_AUTH_READCLIENTFILE_ROLE [page 173]Allows users to read to a file that is resident on the client machine.

Granting SYS_AUTH_RESOURCE_ROLE [page 175]Allows users to create new database objects, such as tables, views, indexes, or procedures.

Granting SYS_AUTH_SPACE_ADMIN_ROLE [page 177]Allows users to manage dbspaces.

Granting SYS_AUTH_USER ADMIN_ROLE [page 178]Allows users to manage external logins, login policies, and other users.

Granting SYS_AUTH_VALIDATE_ROLE [page 179]Allows users to validate or check tables, materialized views, indexes, or databases in the system store. The objects can be owned by any user.

Granting SYS_AUTH_WRITEFILE_ROLE [page 181]Allows users to write to a file that is resident on the server machine.

Granting SYS_AUTH_WRITECLIENTFILE_ROLE [page 182]Allows users to write to a file that is resident on the client machine.

14.3.9.11.1.1 Granting SYS_AUTH_SA_ROLE

Allows users to perform authorized tasks pertaining to data and system administration responsibilities.

Prerequisites

Administrative privilege over SYS_AUTH_SA_ROLE role.

Context

You can grant this role with or without administrative rights. When granted with administrative rights, you can manage (grant and revoke) the role, as well as use any of the underlying system privileges. When granted with administrative rights only, you can manage the role, but not use its underlying system privileges. Finally, when granted with no administrative rights, you can only use its underlying system privileges.

Procedure

To grant the SYS_AUTH_SA_ROLE role, execute one of these statements:


Administrative Option Statement

With full administrative rights GRANT ROLE SYS_AUTH_SA_ROLE TO <grantee [,...]>

WITH ADMIN OPTION

With administrative rights only GRANT ROLE SYS_AUTH_SA_ROLE TO <grantee [,...]>

WITH ADMIN ONLY OPTION

With no administrative rights GRANT ROLE SYS_AUTH_SA_ROLE TO <grantee [,...]>


In this section:

System Privileges Granted to SYS_AUTH_SA_ROLE [page 156]Each system privilege is granted with full administrative rights.

14.3.9.11.1.1.1 System Privileges Granted to SYS_AUTH_SA_ROLE

Each system privilege is granted with full administrative rights.

● ACCESS SERVER LS● ALTER ANY INDEX● ALTER ANY MATERIALIZED VIEW● ALTER ANY OBJECT● ALTER ANY PROCEDURE● ALTER ANY SEQUENCE● ALTER ANY TEXT CONFIGURATION● ALTER ANY TABLE● ALTER ANY TRIGGER● ALTER ANY VIEW● ALTER DATABASE● ALTER DATATYPE● BACKUP DATABASE● CHECKPOINT● COMMENT ANY OBJECT● CREATE ANY INDEX● CREATE ANY MATERIALIZED VIEW● CREATE ANY MUTEX SEMAPHORE● CREATE ANY OBJECT● CREATE ANY PROCEDURE● CREATE ANY SEQUENCE● CREATE ANY TABLE



● CREATE ANY TEXT CONFIGURATION● CREATE ANY TRIGGER● CREATE ANY VIEW● CREATE DATABASE VARIABLE● CREATE DATATYPE● CREATE EXTERNAL REFERENCE● CREATE MATERIALIZED VIEW● CREATE MESSAGE● CREATE PROCEDURE● CREATE PROXY TABLE● CREATE TABLE● CREATE TEXT CONFIGURATION● CREATE VIEW● DEBUG ANY PROCEDURE● DELETE ANY TABLE● DROP ANY INDEX● DROP ANY MATERIALIZED VIEW● DROP ANY MUTEX SEMAPHORE● DROP ANY OBJECT● DROP ANY PROCEDURE● DROP ANY SEQUENCE● DROP ANY TABLE● DROP ANY TEXT CONFIGURATION● DROP ANY VIEW● DROP DATATYPE● DROP MESSAGE● EXECUTE ANY PROCEDURE● INSERT ANY TABLE● LOAD ANY TABLE● MANAGE ANY DATABASE VARIABLE● MANAGE ANY DBSPACE● MANAGE ANY EVENT● MANAGE ANY EXTERNAL ENVIRONMENT● MANAGE ANY EXTERNAL OBJECT● MANAGE ANY MIRROR SERVER● MANAGE ANY SPATIAL OBJECT● MANAGE ANY STATISTICS● MANAGE ANY WEB SERVICE● MANAGE LISTENERS● MANAGE MULTIPLEX● MANAGE PROFILING● MANAGE ANY PROPERTY HISTORY● MANAGE REPLICATION● MONITOR● READ CLIENT FILE


● READ FILE● REORGANIZE ANY OBJECT● SELECT ANY TABLE● SELECT PUBLIC DATABASE VARIABLE● SERVER OPERATOR● SET ANY PUBLIC OPTION● SET ANY SYSTEM OPTION● SET ANY USER DEFINED OPTION● TRUNCATE ANY TABLE● UPDATE ANY MUTEX SEMAPHORE● UPDATE ANY TABLE● UPDATE PUBLIC DATABASE VARIABLE● UPGRADE ROLE● USE ANY SEQUENCE● VALIDATE ANY OBJECT● WRITE CLIENT FILE● WRITE FILE

14.3.9.11.1.2 Granting SYS_AUTH_SSO_ROLE

Allows users to perform authorized tasks pertaining to security and access control responsibilities.

Prerequisites

Administrative privilege over SYS_AUTH_SSO_ROLE role.

Context


Procedure

To grant the role, execute one of these statements:




With full administrative rights GRANT ROLE SYS_AUTH_SSO_ROLE TO <grantee [,...]>

WITH ADMIN OPTION

With administrative rights only GRANT ROLE SYS_AUTH_SSO_ROLE TO <grantee [,...]>


With no administrative rights GRANT ROLE SYS_AUTH_SSO_ROLE TO <grantee [,...]>


In this section:

System Privileges Granted to SYS_AUTH_SSO_ROLE [page 159]Each system privilege is granted with full administrative rights only unless noted.

14.3.9.11.1.2.1 System Privileges Granted to SYS_AUTH_SSO_ROLE

Each system privilege is granted with full administrative rights only unless noted.

● ACCESS USER PASSWORD● ALTER ANY OBJECT OWNER● ANY USER● CHANGE PASSWORD● DROP CONNECTION● MANAGE ANY OBJECT PRIVILEGES● MANAGE ANY LDAP SERVER● MANAGE ANY LOGIN POLICY● MANAGE ANY USER● MANAGE AUDITING● MANAGE ROLES● SET ANY SECURITY OPTION● SET USER (granted with the administrative rights only)


14.3.9.11.1.3 Granting SYS_AUTH_DBA_ROLE

Allows users to perform all authorized tasks.

Prerequisites

Administrative privilege over SYS_AUTH_DBA_ROLE role.

Context

This role indirectly grants all compatibility roles, and some system roles, to a user. It is the union of the underlying system privileges of each of these roles that makes the SYS_AUTH_DBA_ROLE role the "super" role.


NoteWhen migrating from SAP IQ 15.4 and earlier, the concept of inheritance of the underlying system privileges of this system role represents a change in behavior in SAP IQ 16.0 or later. For SAP IQ 15.4 and earlier behavior, use the WITH NO SYSTEM PRIVILEGE INHERITANCE clause.

The WITH ADMIN ONLY OPTION clause is invalid when using the WITH NO SYSTEM PRIVILEGE INHERITANCE clause. The WITH NO ADMIN OPTION clause is valid, but not required, as it is semantically equivalent to the WITH NO SYSTEM PRIVILEGE INHERITANCE clause.

Procedure

To grant the SYS_AUTH_DBA_ROLE role, execute one of these statements:


With full administrative rights GRANT ROLE SYS_AUTH_DBA_ROLE TO <grantee [,...]>

WITH ADMIN OPTION

With administrative rights only GRANT ROLE SYS_AUTH_DBA_ROLE TO <grantee [,...]>


With no administrative rights GRANT ROLE SYS_AUTH_DBA_ROLE TO <grantee [,...]>





With full administrative rights,

but no system privilege inheritance

GRANT ROLE SYS_AUTH_REMOTE_DBA_ROLE TO <user_ID>

WITH ADMIN OPTION


In this section:

Roles Granted to SYS_AUTH_DBA_ROLE [page 161]System and compatibility roles granted to the SYS_AUTH_DBA_ROLE role.

System Privileges Granted to SYS_AUTH_DBA_ROLE [page 162]Through the granting of all compatibility roles and select system roles, system privileges are indirectly granted to the SYS_AUTH_DBA_ROLE role. The underlying system privileges of the SYS_AUTH_SA_ROLE and SYS_AUTH_SSO_ROLE roles are indirectly granted with full administrative rights. All other compatibility roles and system roles are indirectly granted with administrative rights only.

14.3.9.11.1.3.1 Roles Granted to SYS_AUTH_DBA_ROLE

System and compatibility roles granted to the SYS_AUTH_DBA_ROLE role.

These compatibility roles are granted with full administrative rights:

● SYS_AUTH_SA_ROLE● SYS_AUTH_SSO_ROLE

These compatibility roles are granted with administrative rights only:

● SYS_AUTH_RESOURCE_ROLE● SYS_AUTH_BACKUP_ROLE● SYS_AUTH_VALIDATE_ROLE● SYS_AUTH_READFILE_ROLE● SYS_AUTH_PROFILE_ROLE● SYS_AUTH_READCLIENTFILE_ROLE● SYS_AUTH_WRITECLIENTFILE_ROLE● SYS_AUTH_WRITEFILE_ROLE● SYS_AUTH_USER_ADMIN_ROLE● SYS_AUTH_SPACE_ADMIN_ROLE● SYS_AUTH_MULTIPLEX_ADMIN_ROLE● SYS_AUTH_OPERATOR_ROLE● SYS_AUTH_PERMS_ADMIN_ROLE

These system roles are granted with administrative rights only:

● SYS_SPATIAL_ADMIN_ROLE


● diagnostics● rs_systabgroup● SYS● DBO● PUBLIC

14.3.9.11.1.3.2 System Privileges Granted to SYS_AUTH_DBA_ROLE

Through the granting of all compatibility roles and select system roles, system privileges are indirectly granted to the SYS_AUTH_DBA_ROLE role. The underlying system privileges of the SYS_AUTH_SA_ROLE and SYS_AUTH_SSO_ROLE roles are indirectly granted with full administrative rights. All other compatibility roles and system roles are indirectly granted with administrative rights only.

● ACCESS USER PASSWORD● ACCESS SERVER LS● ALTER ANY INDEX● ALTER ANY MATERIALIZED VIEW● ALTER ANY OBJECT● ALTER ANY OBJECT OWNER● ALTER ANY PROCEDURE● ALTER ANY SEQUENCE● ALTER ANY TABLE● ALTER ANY TEXT CONFIGURATION● ALTER ANY TRIGGER● ALTER ANY VIEW● ALTER DATABASE● ALTER DATATYPE● BACKUP DATABASE● CHANGE PASSWORD● CHECKPOINT● COMMENT ANY OBJECT● CREATE ANY INDEX● CREATE ANY MATERIALIZED VIEW● CREATE ANY MUTEX SEMAPHORE● CREATE ANY OBJECT● CREATE ANY PROCEDURE● CREATE ANY SEQUENCE● CREATE ANY TABLE● CREATE ANY TEXT CONFIGURATION● CREATE ANY TRIGGER● CREATE ANY VIEW● CREATE DATABASE VARIABLE● CREATE DATATYPE



● CREATE EXTERNAL REFERENCE● CREATE MATERIALIZED VIEW● CREATE MESSAGE● CREATE PROCEDURE● CREATE PROXY TABLE● CREATE TABLE● CREATE TEXT CONFIGURATION● CREATE VIEW● DEBUG ANY PROCEDURE● DELETE ANY TABLE● DROP ANY INDEX● DROP ANY MATERIALIZED VIEW● DROP ANY MUTEX SEMAPHORE● DROP ANY OBJECT● DROP ANY PROCEDURE● DROP ANY SEQUENCE● DROP ANY TABLE● DROP ANY TEXT CONFIGURATION● DROP ANY VIEW● DROP CONNECTION● DROP DATATYPE● DROP MESSAGE● EXECUTE ANY PROCEDURE● LOAD ANY TABLE● INSERT ANY TABLE● MANAGE ANY DATABASE VARIABLE● MANAGE ANY DBSPACE● MANAGE ANY EVENT● MANAGE ANY EXTERNAL ENVIRONMENT● MANAGE ANY EXTERNAL OBJECT● MANAGE ANY LDAP SERVER● MANAGE ANY LOGIN POLICY● MANAGE ANY MIRROR SERVER● MANAGE ANY OBJECT PRIVILEGES● MANAGE ANY PROPERTY HISTORY● MANAGE ANY SPATIAL OBJECT● MANAGE ANY STATISTICS● MANAGE ANY USER● MANAGE ANY WEB SERVICE● MANAGE AUDITING● MANAGE LISTENERS● MANAGE MULTIPLEX● MANAGE PROFILING● MANAGE REPLICATION● MANAGE ROLES


● MONITOR● READ CLIENT FILE● READ FILE● REORGANIZE ANY OBJECT● SELECT ANY TABLE● SELECT PUBLIC DATABASE VARIABLE● SERVER OPERATOR● SET ANY PUBLIC OPTION● SET ANY SECURITY OPTION● SET ANY SYSTEM OPTION● SET ANY USER DEFINED OPTION● SET USER (granted with administrative rights only)● TRUNCATE ANY TABLE● UPDATE ANY MUTEX SEMAPHORE● UPDATE ANY TABLE● UPDATE PUBLIC DATABASE VARIABLE● UPGRADE ROLE● USE ANY SEQUENCE● VALIDATE ANY OBJECT● WRITE CLIENT FILE● WRITE FILE

14.3.9.11.1.4 Granting SYS_AUTH_BACKUP_ROLE

Allows users to perform all backups.

Prerequisites

Administrative privilege over SYS_AUTH_BACKUP_ROLE.

Context





The WITH ADMIN ONLY OPTION and WITH ADMIN OPTION clauses are invalid when using the WITH NO SYSTEM PRIVILEGE INHERITANCE clause. The WITH NO ADMIN OPTION clause is valid, but not required, as it is semantically equivalent to the WITH NO SYSTEM PRIVILEGE INHERITANCE clause.

Procedure

To grant the SYS_AUTH_BACKUP_ROLE role, execute one of the following statements:


With full administrative rights

GRANT ROLE SYS_AUTH_BACKUP_ROLE TO <user_ID>

WITH ADMIN OPTION

With administrative rights only



With no administrative rights



With no system privilege inheritance



ExampleExample:

This example grants the SYS_AUTH_BACKUP_ROLE to Mary with administrative rights and inheritance of the underlying system privileges of the role.

GRANT ROLE SYS_AUTH_BACKUP_ROLE TO Mary WITH ADMIN OPTION

This example grants the SYS_AUTH_BACKUP_ROLE to Joe with neither administrative rights nor inheritance of the roles underlying system privileges.

GRANT ROLE SYS_AUTH_BACKUP_ROLE TO Joe WITH NO SYSTEM PRIVILEGE INHERITANCE

In this section:

System Privileges Granted to SYS_AUTH_BACKUP_ROLE [page 166]The BACKUP DATABASE system privilege is granted with no administrative rights.


14.3.9.11.1.4.1 System Privileges Granted to SYS_AUTH_BACKUP_ROLE

The BACKUP DATABASE system privilege is granted with no administrative rights.

14.3.9.11.1.5 Granting SYS_AUTH_MULTIPLEX_ADMIN_ROLE

Allows users to perform authorized tasks to manage multiplex.

Prerequisites

Administrative privilege over SYS_AUTH_MULTIPLEX_ADMIN_ROLE.

Context


Procedure

To grant the SYS_AUTH_MULTIPLEX_ADMIN_ROLE role, execute one of the following statements:


With full administrative rights GRANT ROLE SYS_AUTH_MULTIPLEX_ADMIN_ROLE TO <user_ID>

WITH ADMIN OPTION

With administrative rights only GRANT ROLE SYS_AUTH_MULTIPLEX_ADMIN_ROLE TO <user_ID>


With no administrative rights GRANT ROLE SYS_AUTH_MULTIPLEX_ADMIN_ROLE TO <user_ID>


ExampleExample:



This example grants the SYS_AUTH_MULTIPLEX_ADMIN_ROLE to Mary, with no administrative rights.

GRANT ROLE SYS_AUTH_MULTIPLEX_ADMIN_ROLE TO Mary WITH NO ADMIN OPTION

In this section:

System Privileges Granted to SYS_AUTH_MULTIPLEX_ADMIN_ROLE [page 167]The ACCESS SERVER LS and MANAGE MULTIPLEX system privileges are granted with the no administrative rights.

14.3.9.11.1.5.1 System Privileges Granted to SYS_AUTH_MULTIPLEX_ADMIN_ROLE

The ACCESS SERVER LS and MANAGE MULTIPLEX system privileges are granted with the no administrative rights.

14.3.9.11.1.6 Granting SYS_AUTH_OPERATOR_ROLE

Allows users to checkpoint databases, drop connections (including those for users with SYS_AUTH_DBA_ROLE), back up databases, and monitor the system.

Prerequisites

Administrative privilege over SYS_AUTH_OPERATOR_ROLE.

Context





Procedure

To grant the SYS_AUTH_OPERATOR_ROLE role, execute one of the following statements:


With full administrative rights GRANT ROLE SYS_AUTH_OPERATOR_ROLE TO <user_ID>

WITH ADMIN OPTION

With administrative rights only GRANT ROLE SYS_AUTH_OPERATOR_ROLE TO <user_ID>


With no administrative rights GRANT ROLE SYS_AUTH_OPERATOR_ROLE TO <user_ID>


With no system privilege inheritance

GRANT ROLE SYS_AUTH_OPERATOR_ROLE TO <user_ID>


ExampleExample:

This example grants the SYS_AUTH_OPERATOR_ROLE to Mary with administrative rights and inheritance of the underlying system privileges of the role.

GRANT ROLE SYS_AUTH_OPERATOR_ROLE TO Mary WITH ADMIN OPTION

This example grants the SYS_AUTH_OPERATOR_ROLE to Joe with neither administrative rights or inheritance of the underlying system privileges of the role.

GRANT ROLE SYS_AUTH_OPERATOR_ROLE TO Joe WITH NO SYSTEM PRIVILEGE INHERITANCE

In this section:

System Privileges Granted to SYS_AUTH_OPERATOR_ROLE [page 169]Each system privilege is granted with no administrative rights.



14.3.9.11.1.6.1 System Privileges Granted to SYS_AUTH_OPERATOR_ROLE

Each system privilege is granted with no administrative rights.

● ACCESS SERVER LS● BACKUP DATABASE● CHECKPOINT● DROP CONNECTION● MONITOR

14.3.9.11.1.7 Granting SYS_AUTH_PERMS_ADMIN_ROLE

Allows users to manage data privileges, groups, authorities, and passwords.

Prerequisites

Administrative privilege over SYS_AUTH_PERMS_ADMIN_ROLE.

Context


Procedure

To grant the SYS_AUTH_PERMS_ADMIN_ROLE role, execute one of the following statements:


With full administrative rights GRANT ROLE SYS_AUTH_PERMS_ADMIN_ROLE TO <user_ID>

WITH ADMIN OPTION

With administrative rights only GRANT ROLE SYS_AUTH_PERMS_ADMIN_ROLE TO <user_ID>




With no administrative rights GRANT ROLE SYS_AUTH_PERMS_ADMIN_ROLE TO <user_ID>


ExampleExample:

This example grants the SYS_AUTH_PERMS_ADMIN_ROLE to Mary, with only administrative rights.

GRANT ROLE SYS_AUTH_PERMS_ADMIN_ROLE TO Mary WITH ADMIN ONLY OPTION

In this section:

Roles Granted to SYS_AUTH_PERMS_ADMIN_ROLE [page 170]Compatibility roles granted with full administrative rights.

System Privileges Granted to SYS_AUTH_PERMS_ADMIN_ROLE [page 171]Each system privilege is granted with no administrative rights.

14.3.9.11.1.7.1 Roles Granted to SYS_AUTH_PERMS_ADMIN_ROLE

Compatibility roles granted with full administrative rights.

● SYS_AUTH_BACKUP_ROLE● SYS_AUTH_OPERATOR_ROLE● SYS_AUTH_USER_ADMIN_ROLE● SYS_AUTH_SPACE_ADMIN_ROLE● SYS_AUTH_MULTIPLEX_ADMIN_ROLE● SYS_AUTH_RESOURCE_ROLE● SYS_AUTH_VALIDATE_ROLE● SYS_AUTH_PROFILE_ROLE● SYS_AUTH_READFILE_ROLE● SYS_AUTH_READCLIENTFILE_ROLE● SYS_AUTH_WRITEFILE_ROLE● SYS_AUTH_WRITECLIENTFILE_ROLE



14.3.9.11.1.7.2 System Privileges Granted to SYS_AUTH_PERMS_ADMIN_ROLE


● CHANGE PASSWORD● MANAGE ANY OBJECT PRIVILEGES● MANAGE ROLES

14.3.9.11.1.8 Granting SYS_AUTH_PROFILE_ROLE

Allows users to enable or disable server tracing for application profiling.

Prerequisites

Administrative privilege over SYS_AUTH_PROFILE_ROLE.

Context

You can grant this role with or without administrative rights. When granted with administrative rights, you can manage (grant and revoke) the role, as well as use any of the underlying system privileges. When granted with administrative rights only, you can manage the role, but not use its underlying system privileges. Finally, when granted with no administrative rights, you can only use its underlying system privileges. By default, the SYS_AUTH_PROFILE_ROLE is granted the diagnostics system role with no administrative rights.

Procedure

To grant the SYS_AUTH_PROFILE_ROLE role, execute one of the following statements:


With full administrative rights GRANT ROLE SYS_AUTH_PROFILE_ROLE TO <user_ID>

WITH ADMIN OPTION

With administrative rights only GRANT ROLE SYS_AUTH_PROFILE_ROLE TO <user_ID>


With no administrative rights GRANT ROLE SYS_AUTH_PROFILE_ROLE TO <user_ID>




ExampleExample:

This example grants the SYS_AUTH_PROFILE_ROLE to Mary, with administrative rights.

GRANT ROLE SYS_AUTH_PROFILE_ROLE TO Mary WITH ADMIN OPTION

In this section:

System Privileges Granted to SYS_AUTH_PROFILE_ROLE [page 172]The MANAGE PROFILING system privilege is granted with no administrative rights.

14.3.9.11.1.8.1 System Privileges Granted to SYS_AUTH_PROFILE_ROLE

The MANAGE PROFILING system privilege is granted with no administrative rights.

14.3.9.11.1.9 Granting SYS_AUTH_READFILE_ROLE

Allows users to read to a file that is resident on the server machine.

Prerequisites

Administrative privilege over SYS_AUTH_READFILE_ROLE.

Context




Procedure

To grant the SYS_AUTH_READFILE_ROLE role, execute one of the following statements:


With full administrative rights GRANT SYS_AUTH_READFILE_ROLE TO <user_ID>

WITH ADMIN OPTION

With administrative rights only GRANT SYS_AUTH_READFILE_ROLE TO <user_ID>


With no administrative rights GRANT SYS_AUTH_READFILE_ROLE TO <user_ID>


ExampleExample:

This example grants the SYS_AUTH_READFILE_ROLE to Mary, with no administrative rights.

GRANT ROLE SYS_AUTH_READFILE_ROLE TO Mary WITH NO ADMIN OPTION

In this section:

System Privileges Granted to SYS_AUTH_READFILE_ROLE [page 173]The READ FILE system privilege is granted with no administrative rights.

14.3.9.11.1.9.1 System Privileges Granted to SYS_AUTH_READFILE_ROLE

The READ FILE system privilege is granted with no administrative rights.

14.3.9.11.1.10 Granting SYS_AUTH_READCLIENTFILE_ROLE

Allows users to read to a file that is resident on the client machine.

Prerequisites

Administrative privilege over SYS_AUTH_READCLIENTFILE_ROLE.


Context


Procedure

To grant the SYS_AUTH_READCLIENTFILE_ROLE role, execute one of the following statements:


With full administrative rights GRANT ROLE SYS_AUTH_READCLIENTFILE_ROLE TO <user_ID>

WITH ADMIN OPTION

With administrative rights only GRANT ROLE SYS_AUTH_READCLIENTFILE_ROLE TO <user_ID>


With no administrative rights GRANT ROLE SYS_AUTH_READCLIENTFILE_ROLE TO <user_ID>


ExampleExample:

This example grants the SYS_AUTH_READCLIENTFILE_ROLE to Mary, with only administrative rights.

GRANT ROLE SYS_AUTH_READCLIENTFILE_ROLE TO Mary WITH ADMIN ONLY OPTION

In this section:

System Privileges Granted to SYS_AUTH_READCLIENTFILE_ROLE [page 175]The READ CLIENT FILE system privilege is granted with no administrative rights.



14.3.9.11.1.10.1 System Privileges Granted to SYS_AUTH_READCLIENTFILE_ROLE

The READ CLIENT FILE system privilege is granted with no administrative rights.

14.3.9.11.1.11 Granting SYS_AUTH_RESOURCE_ROLE

Allows users to create new database objects, such as tables, views, indexes, or procedures.

Prerequisites

Administrative privilege over SYS_AUTH_RESOURCE_ROLE.

Context




Procedure

To grant the SYS_AUTH_RESOURCE_ROLE role, execute one of the following statements:


With full administrative rights GRANT ROLE SYS_AUTH_RESOURCE_ROLE TO <user_ID>

WITH ADMIN OPTION



With administrative rights only GRANT ROLE SYS_AUTH_RESOURCE_ROLE TO <user_ID>


With no administrative rights GRANT ROLE SYS_AUTH_RESOURCE_ROLE TO <user_ID>


With no system privilege inheritance GRANT ROLE SYS_AUTH_RESOURCE_ROLE TO <user_ID>


ExampleExample:

This example grants the SYS_AUTH_RESOURCE_ROLE to Mary with administrative rights and inheritance of the underlying system privileges of the role.

GRANT ROLE SYS_AUTH_RESOURCE_ROLE TO Mary WITH ADMIN OPTION

This example grants the SYS_AUTH_RESOURCE_ROLE to Joe with neither administrative rights nor inheritance of the roles underlying system privileges.

GRANT ROLE SYS_AUTH_RESOURCE_ROLE TO Joe WITH NO SYSTEM PRIVILEGE INHERITANCE

In this section:

System Privileges Granted to SYS_AUTH_RESOURCE_ROLE [page 176]Each system privilege is granted with no administrative rights.

14.3.9.11.1.11.1 System Privileges Granted to SYS_AUTH_RESOURCE_ROLE


● CREATE TABLE● CREATE PROXY TABLE● CREATE VIEW● CREATE MATERIALIZED VIEW● CREATE PROCEDURE● CREATE DATATYPE● CREATE MESSAGE● CREATE TEXT CONFIGURATION● CREATE ANY SEQUENCE



● CREATE ANY TRIGGER● ALTER ANY TRIGGER● CREATE ANY OBJECT

14.3.9.11.1.12 Granting SYS_AUTH_SPACE_ADMIN_ROLE

Allows users to manage dbspaces.

Prerequisites

Administrative privilege over SYS_AUTH_SPACE_ADMIN_ROLE.

Context


Procedure

To grant the SYS_AUTH_SPACE_ADMIN_ROLE role, execute one of the following statements:


With full administrative rights GRANT ROLE SYS_AUTH_SPACE_ADMIN_ROLE TO <user_ID>

WITH ADMIN OPTION

With administrative rights only GRANT ROLE SYS_AUTH_SPACE_ADMIN_ROLE TO <user_ID>


With no administrative rights GRANT ROLE SYS_AUTH_SPACE_ADMIN_ROLE TO <user_ID>


ExampleExample:


This example grants the SYS_AUTH_SPACE_ADMIN_ROLE to Mary, with no administrative rights.

GRANT ROLE SYS_AUTH_SPACE_ADMIN_ROLE TO Mary WITH NO ADMIN OPTION

In this section:

System Privileges Granted to SYS_AUTH_SPACE_ADMIN_ROLE [page 178]The ACCESS SERVER LS and MANAGE ANY DBSPACE system privileges are granted with no administrative rights.

14.3.9.11.1.12.1 System Privileges Granted to SYS_AUTH_SPACE_ADMIN_ROLE

The ACCESS SERVER LS and MANAGE ANY DBSPACE system privileges are granted with no administrative rights.

14.3.9.11.1.13 Granting SYS_AUTH_USER ADMIN_ROLE

Allows users to manage external logins, login policies, and other users.

Prerequisites

Administrative privilege over SYS_AUTH_USER ADMIN_ROLE.

Context


Procedure

To grant the SYS_AUTH_USER ADMIN_ROLE role, execute one of the following statements:




With full administrative rights GRANT ROLE SYS_AUTH_USER_ADMIN_ROLE TO <user_ID>

WITH ADMIN OPTION

With administrative rights only GRANT ROLE SYS_AUTH_USER_ADMIN_ROLE TO <user_ID>


With no administrative rights GRANT ROLE SYS_AUTH_USER_ADMIN_ROLE TO <user_ID>


ExampleExample:

This example grants the SYS_AUTH_USER_ADMIN_ROLE to Mary, with administrative rights.

GRANT ROLE SYS_AUTH_USER_ADMIN_ROLE TO Mary WITH ADMIN OPTION

In this section:

System Privileges Granted to SYS_AUTH_USER_ADMIN_ROLE [page 179]The MANAGE ANY LOGIN POLICY and MANAGE ANY USER system privileges are granted with no administrative rights.

14.3.9.11.1.13.1 System Privileges Granted to SYS_AUTH_USER_ADMIN_ROLE

The MANAGE ANY LOGIN POLICY and MANAGE ANY USER system privileges are granted with no administrative rights.

14.3.9.11.1.14 Granting SYS_AUTH_VALIDATE_ROLE

Allows users to validate or check tables, materialized views, indexes, or databases in the system store. The objects can be owned by any user.

Prerequisites

Administrative privilege over SYS_AUTH_VALIDATE_ROLE.


Context




Procedure

To grant the SYS_AUTH_VALIDATE_ROLE role, execute one of the following statements:


With full administrative rights GRANT ROLE SYS_AUTH_VALIDATE_ROLE TO <user_ID>

WITH ADMIN OPTION

With administrative rights only GRANT ROLE SYS_AUTH_VALIDATE_ROLE TO <user_ID>


With no administrative rights GRANT ROLE SYS_AUTH_VALIDATE_ROLE TO <user_ID>


With no system privilege inheritance GRANT ROLE SYS_AUTH_VALIDATE_ROLE TO <user_ID>


ExampleExample:

This example grants the SYS_AUTH_VALIDATE_ROLE to Mary with administrative rights and inheritance of the underlying system privileges of the role.

GRANT ROLE SYS_AUTH_VALIDATE_ROLE TO Mary WITH ADMIN OPTION

This example grants the SYS_AUTH_VALIDATE_ROLE to Joe with neither administrative rights nor inheritance of the roles underlying system privileges.

GRANT ROLE SYS_AUTH_VALIDATE_ROLE TO Joe




In this section:

System Privileges Granted to SYS_AUTH_VALIDATE_ROLE [page 181]The VALIDATE ANY OBJECT system privilege is granted with no administrative rights.

14.3.9.11.1.14.1 System Privileges Granted to SYS_AUTH_VALIDATE_ROLE

The VALIDATE ANY OBJECT system privilege is granted with no administrative rights.

14.3.9.11.1.15 Granting SYS_AUTH_WRITEFILE_ROLE

Allows users to write to a file that is resident on the server machine.

Prerequisites

Administrative privilege over SYS_AUTH_WRITEFILE_ROLE.

Context


Procedure

To grant the role, execute one of the following statements:


With full administrative rights GRANT ROLE SYS_AUTH_WRITEFILE_ROLE TO <user_ID>

WITH ADMIN OPTION



With administrative rights only GRANT ROLE SYS_AUTH_WRITEFILE_ROLE TO <user_ID>


With no administrative rights GRANT ROLE SYS_AUTH_WRITEFILE_ROLE TO <user_ID>


ExampleExample:

This example grants the SYS_AUTH_WRITEFILE_ROLE to Mary, with no administrative rights.

GRANT ROLE SYS_AUTH_WRITEFILE_ROLE TO Mary WITH NO ADMIN OPTION

In this section:

System Privileges Granted to SYS_AUTH_WRITEFILE_ROLE [page 182]The WRITE FILE system privilege is granted with no administrative rights.

14.3.9.11.1.15.1 System Privileges Granted to SYS_AUTH_WRITEFILE_ROLE

The WRITE FILE system privilege is granted with no administrative rights.

14.3.9.11.1.16 Granting SYS_AUTH_WRITECLIENTFILE_ROLE

Allows users to write to a file that is resident on the client machine.

Prerequisites

Administrative privilege over SYS_AUTH_WRITECLIENTFILE_ROLE.

Context

You can grant this role with or without administrative rights. When granted with administrative rights, you can manage (grant and revoke) the role, as well as use any of the underlying system privileges. When granted with



administrative rights only, you can manage the role, but not use its underlying system privileges. Finally, when granted with no administrative rights, you can only use its underlying system privileges.

Procedure

To grant the SYS_AUTH_WRITECLIENTFILE_ROLE role, execute one of the following statements:


With full administrative rights GRANT ROLE SYS_AUTH_WRITECLIENTFILE_ROLE TO <user_ID>

WITH ADMIN OPTION

With administrative rights only GRANT ROLE SYS_AUTH_WRITECLIENTFILE_ROLE TO <user_ID>


With no administrative rights GRANT ROLE SYS_AUTH_WRITECLIENTFILE_ROLE TO <user_ID>


ExampleExample:

This example grants the SYS_AUTH_WRITECLIENTFILE_ROLE to Mary, with only administrative rights.

GRANT ROLE SYS_AUTH_WRITECLIENTFILE_ROLE TO Mary WITH ADMIN ONLY OPTION

In this section:

System Privileges Granted to SYS_AUTH_WRITECLIENTFILE_ROLE [page 184]The SWRITE CLIENT FILE system privilege is granted with no administrative rights.


14.3.9.11.1.16.1 System Privileges Granted to SYS_AUTH_WRITECLIENTFILE_ROLE

The SWRITE CLIENT FILE system privilege is granted with no administrative rights.

14.3.9.11.2 Revoking a Compatibility Role

Revoke a compatibility role from a user or role.

Prerequisites

Administrative privilege over the compatibility role being revoked.

Procedure

To revoke a compatibility role, execute one of these statements:


Administrative rights only REVOKE ADMIN OPTION FOR ROLE <compatibility_role>

FROM <grantee [,...]>

Membership in the role and

any administrative rights

REVOKE ROLE <compatibility_role>

FROM <grantee [,...]>

14.3.9.11.3 Migrating a Compatibility Role

Migrate all underlying system privileges of a compatibility role to a user-defined role.

Prerequisites

Administrative privilege over the role being migrated, and the MANAGE ROLES system privilege.



Context

Compatibility roles are immutable, but you can migrate them in their entirety to a new user-defined role. Once migrated, the compatibility role is automatically dropped. This process is systematically equivalent to individually granting each underlying system privilege to a user-defined role, then manually dropping the compatibility role.

During migration:

● A new user-defined role is created.● All system privileges currently granted to the migrating role are granted to the new user-defined role.● All users and roles currently granted to the migrating role are granted to the new user-defined role.● Administrators of the compatibility role continue to be the administrators of the new migrated role.● The compatibility role is dropped.

You cannot use ALTER ROLE to individually migrate the SYS_AUTH_SA_ROLE and SYS_AUTH_SSO_ROLE compatibility roles. These two compatibility roles are automatically migrated when SYS_AUTH_DBA_ROLE is migrated.

The name of the new role cannot already exist, or begin with the prefix SYS_ and end with the suffix _ROLE when migrating a compatibility role.

Procedure

To migrate a compatibility role, execute one of these statements:

Compatibility Role Statement

SYS_AUTH_DBA_ROLE ALTER ROLE <SYS_AUTH_DBA_ROLE>

MIGRATE TO <new_dba_role_name, new_sa_role_name, new_sso_role_name>

Any other compatibility role ALTER ROLE <compatibility_sys_role_name>

MIGRATE TO <new_role_name>

ExampleExample

The following statement migrates SYS_AUTH_DBA_ROLE to the new roles Custom_DBA_Role, Custom_SA_Role, and Custom_SSO_Role, respectively.

ALTER ROLE SYS_AUTH_DBA_ROLE MIGRATE TO Custom_DBA_Role, Custom_SA_Role, Custom_SSO_Role

This statement migrates the SYS_AUTH_OPERATOR_ROLE role to the new role Custom_Operator_role.

ALTER ROLE SYS_AUTH_OPERATOR_ROLE MIGRATE TO Custom_Operator_Role


In both examples, all users, underlying system privileges, and roles granted to the original roles are automatically migrated to the new roles, then SYS_AUTH_DBA_ROLE, SYS_AUTH_SA_ROLE, SYS_AUTH_SSO_ROLE and SYS_AUTH_OPERATOR_ROLE are dropped.

14.3.9.11.4 Dropping a Compatibility Role

All compatibility roles, with the exception of SYS_AUTH_SA_ROLE and SYS_AUTH_SSO_ROLE can be dropped. SYS_AUTH_SA_ROLE and SYS_AUTH_SSO_ROLE are automatically dropped when SYS_AUTH_DBA_ROLE is dropped.

Prerequisites

● Administrative privilege over the role being dropped.● Each of the system privileges granted to a compatibility role is granted to at least one user-defined role.

Context

The WITH REVOKE clause is only required when dropping a compatibility role that is currently granted to users or roles. You can re-create any dropped compatibility role. See Re-creating a Compatibility Role [page 187].

Procedure

To delete a compatibility role, execute one of these statements:

Drop Condition Statement

Compatibility role not currently granted to any user or role. DROP ROLE <role_name>*

Compatibility role currently granted to users or roles. DROP ROLE <role_name>* WITH REVOKE

*<role_name> cannot be SYS_AUTH_SA_ROLE or SYS_AUTH_SSO_ROLE.

Related Information

Re-creating a Compatibility Role [page 187]



14.3.9.11.5 Re-creating a Compatibility Role

Re-creates a dropped compatibility role.

Prerequisites

● MANAGE ROLES system privilege.● Administrative privileges on all of the system privileges granted to the compatibility role being re-created.

Context

Re-creating SYS_AUTH_DBA_ROLE is semantically equivalent to re-creating both the SYS_AUTH_SA_ROLE and SYS_AUTH_SSO_ROLE roles; you cannot re-create these two roles separately.

When you re-create any compatibility role other than SYS_AUTH_DBA_ROLE, administrative privileges on the re-created compatibility role are automatically granted to SYS_AUTH_DBA_ROLE, as long as it still exists.

When you re-create any compatibility role other than SYS_AUTH_DBA_ROLE, or SYS_AUTH_PERMS_ADMIN_ROLE, administrative privileges on the re-created compatibility role are automatically granted to SYS_AUTH_PERMS_ADMIN_ROLE, as long as it still exists.

Procedure

To re-create a compatibility role, execute:CREATE ROLE <compatibility_role_name> [ WITH ADMIN [ONLY] <userid [, ...]> ]

14.3.9.11.6 Implications of Migrating Compatibility Roles

Some system roles are indirectly granted the system privileges necessary to execute privileged tasks through membership in compatibility roles.

You cannot revoke the underlying system privileges of a compatibility role; you must first migrate it to a user-defined role. Only then can you revoke individual underlying system privileges from the new role and grant them to other user-defined roles per the organization's security requirements. This enforces separation of duties.

You can migrate compatibility roles automatically or manually. The method of migration can impact the ability of a system role or the DBO system role to continue performing authorized tasks.

Regardless of the migration method used, once a compatibility role or the SYS_AUTH_DBA_ROLE role is dropped, if you revoke a system privilege from the new user-defined role and grant it to another user-defined role, you must do one of the following to ensure that system roles especially the dbo system role, retains all the


system privileges required to execute the applicable privileged tasks or multiplex management stored procedures:

● Grant each system privilege revoked from the migrated user-defined role directly to the applicable system roles or dbo role; or

● Grant membership in the user-defined role to which the system privileges are granted to the applicable system roles or dbo system role.

The system roles that are members of compatibility roles, and might potentially be impacted by migration include:

System Role Compatibility Role

dbo SYS_AUTH_DBA_ROLE

SYS_AUTH_RESOURCE_ROLE

SYS_RUN_REPLICATION_ROLE SYS_AUTH_DBA_ROLE

Automatic Migration

The ALTER ROLE statement creates a new user-defined role, automatically grants all underlying system privileges of the compatibility role to the new user-defined role, makes each member of the compatibility role a member of the new user-defined role, then drops the compatibility role.

Automatic migration assumes that the destination user-defined role does not already exist and that all system privileges are migrated to the same new user-defined role.

Manual Migration

Use the CREATE ROLE statement to create a new user-defined role. Use the GRANT statement to grant each underlying system privilege to one or more users or roles. Use the DROP statement to drop the compatibility role once all underlying system privileges are granted to at least one other user or role.

Members of the migrated compatibility role are not automatically granted membership in the new user-defined role. As a result, members of some system roles may no longer be able to perform the expected privileged tasks once the compatibility role is dropped. You must grant membership in the new user-defined role to the affected system roles or directly grant the required system privileges to affected members.

14.3.9.12 Backward Compatibility in SAP IQ 16.1

Grant and revoke syntax for role-based security differs significantly from authority-based security. However, SAP IQ 16.1 is fully backward compatible with authority-based syntax.

SAP IQ 16.1 provides well-documented mappings and stored procedures to assist in transition. All stored procedures, functions, and queries created in pre- 16.0 databases will continue to run after upgrading.



14.3.9.13 Stored Procedure to Map Authorities to System Roles

The sp_auth_sys_role_info stored procedure generates a report, which maps each authority to a corresponding system role name.

A separate row is generated for each authority. No privilege is required to execute the procedure.

14.3.9.14 Connecting to SAP IQ 15.x Databases with SAP IQ 16.x

Role-based syntax is not supported in SAP IQ 15.x databases.

When using SAP IQ 16.x to connect to a 15.x database, only authority-based syntax is valid. Using role-based syntax returns errors. For example, GRANT ROLE returns an error message; GRANT MEMBERSHIP IN GROUP does not.

Beyond this limitation, there should be no change in functionality and no noticeable change in performance using SAP IQ 16.x with a 15.x database.

14.4 SAP IQ Database Administration Tools

The SAP IQ database administration tool provides a personalized work center for SAP IQ.

The SAP IQ Cockpit Framework is installed as part of an SAP IQ server installation. It provides a view specific to SAP IQ and full access to SP 02 features.

The SAP IQ Cockpit Framework manages communication between an SAP IQ Cockpit command and control agent, SAP IQ server, and Web client. The SAP IQ Cockpit agent continually broadcasts information about the server to subscribing clients via the SAP IQ Cockpit framework. Messages from the Web client pass through the SAP IQ Cockpit framework to the agent, which in turn, processes the request on the SAP IQ server.

SAP IQ Cockpit activities range from simple resource monitoring to complete SAP IQ SP 02 database administration.


● SAP Database Administration Tools in SAP IQ Installation and Update Guide● SAP IQ Cockpit online help


14.5 SAP IQ 12.7 Upgrade and Database Migration

Updating a 12.7 catalog requires a database file migration, not a simple database upgrade. Migration tools bundled with SAP IQ can recreate the legacy database schema and database options.

In this section:

Preparing to Migrate [page 190]Perform these tasks before you migrate your database.

Migration Utilities [page 191]Utilities and support tools bundled with SAP IQ.

Migration Issues [page 198]SAP IQ no longer supports some legacy features. Run iqunload in schema unload mode to generate a script (reload.sql) that contains the entire database schema. Compare the contents of this file to find unsupported syntax and metadata.

Unloading Legacy Schemas [page 206]To unload legacy schema, run iqunload in schema unload mode (iqunload -n ) on the same machine as the legacy schema.

Migrating Legacy Databases [page 207]Run iqunload in database migration mode (iqunload -au) to migrate a legacy database.

Postmigration Tasks [page 223]SAP IQ 16 databases upgraded from 12.7 are initially set to run in 15.x compatibility mode. To complete the change from 15.x to 16.1, you must explicitly change several 15.x compatibility settings to complete the 16.1 upgrade.

14.5.1 Preparing to Migrate

Perform these tasks before you migrate your database.

Procedure

1. Upgrade to SAP IQ 12.7 ESD #5. All migration paths assume that you are migrating from SAP IQ 12.7 ESD #5 as a minimum.

2. Regenerate any sort-key values. SAP IQ 12.7 SORTKEY function uses a different sort-key value than SAP IQ 15 and later.

3. Review the collation. SAP IQ no longer supports custom collations. Custom collations are preserved in database rebuilds only if you rebuild the database in a single step. Use a collation included with SAP IQ 15.0 or later.

4. Back up your current installation and save copies of any changes you made to default login and post login scripts. Create your backups on removable media, like tape, DVD, or CD. Make sure the backups are readable.



5. Review and understand the database migration utilities. Use iqunload to re-create the schema for your database or migrate your 12.7 database. iqlsunload utility is available to move 12.7 local stores for 12.7 multiplex servers.

6. Use DROP TABLE statements to drop all global temporary tables before you run the iqunload utility. You can recreate the global temporary tables after migration.

7. Drop all servers of type asejdbc before you run the iqunload utility.

The asejdbc server class is deprecated. Servers of type asejdbc must be dropped prior to running iqunload. 12.7 databases with remote server definitions based on the asejdbc driver will not have these definitions migrated to by the iqunload tool and will not give an error at the beginning of an unload saying that you need to drop any asejdbc servers (if there are any present).

8. Resolve potential migration errors. SAP IQ no longer supports some 12.7 features and objects. Update these objects before you migrate the database.

9. Use sp_iqcheckdb to verify that your 12.7 database is clean and error free.

For information on sp_iqcheckdb output, see Administration: Backup, Restore, and Data Recovery > System Recovery and Database Repair.

14.5.2 Migration Utilities

Utilities and support tools bundled with SAP IQ.

In this section:

iqunload for SAP IQ 12.7 Database Migration [page 191]A command line utility for SAP IQ 12.7 database migration to re-create the legacy catalog on the new database catalog in the current installation.

iqlsunload for Local Store Unload [page 195]In current multiplex configurations, multiple nodes can write to the main store, which eliminates the need for local stores. iqlsunload is a command line utility that you can use to unload a 12.7 local store. iqlsunload is used only in 12.7 ESD #5 multiplex migrations.

Support Processes [page 197]Running iqunload in migration mode (-au) starts iqunlspt and iqsrv16.

14.5.2.1 iqunload for SAP IQ 12.7 Database Migration

A command line utility for SAP IQ 12.7 database migration to re-create the legacy catalog on the new database catalog in the current installation.

iqunload does not change SAP IQ data and temp dbspaces. The utility preserves all legacy database options and applies them to the new database. SAP IQ ignores any legacy options that no longer apply to the current version of the software.


NoteIf you are reloading a 12.7 database, remove any square brackets or back quotes in identifiers; otherwise, the reload fails.

Syntax

iqunload [ <options> ]

Parameters

The iqunload utility takes one or more options.

-ap size

(Optional) sets the page size for the new catalog store.-au

Required for migration mode. Migrates the database.

Specify an -au argument to start iqunload in migration mode or -n argument, but not both.-c "keyword = value, ..."

(Required) supplies database connection parameters. You must specify a DBF parameter to specify the name of the database file for migration. The file path is either absolute or relative to the server startup directory.-dc

(Optional) recalculates computed columns in the database.-ms_filename

Optional for simplex migration; required for multiplex migration. Use -ms_filename to specify a file name for the new empty IQ_SYSTEM_MAIN store created during the migration.

If not specified, the default new main store is a file system file called new_main_store.iq.-ms_reserve

(Optional) Specifies the size of the new IQ_SYSTEM_MAIN reserve, in MB. If unspecified, defaults to zero.-ms_size

(Optional) specifies the size of the new IQ_SYSTEM_MAIN store, in MB, based on the database size. The minimum, assuming a default page size, is 200 MB. If you specifiy an –ms_size value smaller than the computed value, SAP IQ uses the computed value; otherwise the specified value is used.-n

Required for schema unload only. Unloads the schema definition only. The -n parameter requires 12.7 ESD #5 or later. Specify -au or -n argument, but not both.-new_startline

(Optional) specify startup switches for the new server that is the migration target. For a complete list of server startup switches, see the Utility Guide.



-o file_name

(Optional) logs output messages to <file_name>.-q

(Optional) suppresses messages and windows.-r file_name

(Optional) specifies the file name.-t list

(Optional) outputs listed tables only. Can specify OwnerName.TableName or TableName alone.-ul

(Optional) unloads password hashes.-v

(Optional) returns verbose messages.-y

(Optional) replaces existing reload schema SQL script with new output without confirmation.

Examples

● Migrates a simplex database to a current server:

iqunload –au –c "UID=DBA;PWD=<password>;DBF=/mydevice/test_dir/test2.db"

● Unloads a legacy database schema and renames the generated SQL script to test2_reload.sql:

iqunload –n -c "UID=DBA;PWD=<password>;DBF=/test_dir/test2/test2.db; ENG=myserver_test2" –r "/test_dir/unload_dir/test2_reload.sql"

● Migrates database test3.db. The START connection parameter specifies switches for starting the database being reloaded. The -new_startline parameter specifies switches for starting the utility_db to create the new catalog store:

iqunload –au –c "UID=DBA;PWD=<password>;DBF=test3.db; START=–ch 128M –iqmc 50" –new_startline "–ch 256M –iqtc 400"

Do not include -iqnotemp <XYZ> in the new start line; this causes migration to fail. As part of the migration process, temp files are added to IQ_SYSTEM_TEMP. If you start the server with the -iqnotemp option, iqunload cannot add these temp files

● Migrates the legacy database, asiqdemo.db, using a raw device for the IQ_SYSTEM_MAIN store:

iqunload –au –c "UID=DBA;PWD=<password>;DBF=asiqdemo.db" –ms_filename "/dev/rdsk/c4t0d0s3"


Usage

iqunload has two working modes: schema unload and migration.

Schema Unload Mode

iqunload requires an -n argument to start in schema unload mode. Schema unload mode unloads a 12.7 ESD #5 database schema, and generates a script (reload.sql) that can re-create the schema for a database in a current version of the software. A -c argument is required for connection parameters:

iqunload -n -c "UID=DBA;PWD=SQL;ENG=my_engine;DBN=my_dbname"

Schema unload mode re-creates the schema, but does not migrate data. To migrate data, extract the legacy data and load the new database.

Migration Mode

iqunload requires an -au argument to start in migration mode. iqunload migration mode interfaces with the 12.7 support engine (iqunlspt) and the current database server (iqsrv16):

● Start the legacy database and generate the schema● Start the current SAP IQ server● Create a new database and apply the legacy schema

General Usage

● Insufficient cache memory causes migration errors. iqunload uses default values for various cache sizes (catalog cache, main buffer cache, temp cache). If the legacy database requires higher cache values, use the –ch and -cl options as part of the START connection parameter to increase the cache size.

● During database migration, the server creates a message file (*.iqmsg.R) as it reloads the generated schema. This file is normally deleted as part of a cleanup operation for successful migrations. If the migration fails during the reload stage, cleanup does not occur, and *.iqmsg.R remains in the unload directory. *.iqmsg.R may contain information that can help solve your migration problems.

● iqunload writes some temporary files to the $IQTMP16 directory. If you set the $IQTMP16 environment variable, set it to a valid directory name.

● Users with wide tables (large numbers of column/null values) should not decrease the catalog store page size for database migration.

● If the legacy database contains invalid views, SAP IQ completes the migration but issues warnings. A warning may occur, for example, if the tables involved in a view are dropped.

● If the legacy database is encrypted, use the DBKEY connection parameter to provide the encryption key. The migrated database uses the same encryption key.

Permissions

DBA authority

Parent topic: Migration Utilities [page 191]



Related Information

iqlsunload for Local Store Unload [page 195]Support Processes [page 197]

14.5.2.2 iqlsunload for Local Store Unload

In current multiplex configurations, multiple nodes can write to the main store, which eliminates the need for local stores. iqlsunload is a command line utility that you can use to unload a 12.7 local store. iqlsunload is used only in 12.7 ESD #5 multiplex migrations.

iqlsunload is bundled with all versions of SAP IQ starting with 12.7 ESD #5.

Syntax

iqlsunload [ <options> ] <directory> [ @<data> ] <data>:[ <environment variable> | <file> ]

Parameters

The iqlsunload utility takes one or more options.

-al (Optional) unloads IQ local store schema and data.-c "keyword=value;..." (Optional) supplies database connection parameters.-h (Optional) prints out the syntax (help) for the utility.-o filename (Optional) logs output messages, including errors, to <filename>.-q (Optional) suppresses messages and windows.-r directory (Optional) specifies the directory where SQL scripts are generated. The default reload command file is reload.sql in the current directory. The directory is relative to the current directory of the client application, not the server.-t list (Optional) outputs listed tables only. Can specify OwnerName.TableName or TableName alone. Cannot be specified with al argument.-v (Optional) outputs verbose messages.-y (Optional) replaces existing reload schema SQL script without confirmation.directory Identifies the directory where iqlsunload unloads the data files. Create this directory before you run iqlsunload, or point to an existing directory. This directory must be relative to the database on the database server.


Example

This example unloads local stores from a database called mpxtest2, extracting any table data to the directory /mydevice/test_dir/unload_dir:

iqlsunload -o iqunload_624.out -al -c "UID=DBA;PWD=<password>;ENG=myserver_mpxtest02" /mydevice/test_dir/unload_dir

Usage

● Run iqlsunload from the $IQDIR16/lsunload directory to pick up updated libraries before resolving any IQ 12.7 libraries.

Unloaded ObjectsRunning iqlsunload with an -al argument unloads these persistent objects:

● Base tables● Global temporary tables● Indexes● Domains (user-defined data types)● Constraints (column check constraint, table constraint, primary key, foreign key, unique, default, IQ unique,

not null)● Views● Stored procedures and functions● Messages● Remote servers and external logins● Events

Empty User NamesSAP IQ no longer allow users with empty user names. You cannot drop or migrate users with empty user names the 12.6 or 12.7 server. The schema reload operation warns that an empty user name has been encountered and that the user will not be re-created. The reload operation ignores such users and any associated objects.

Unloading Tablesiqlsunload ignores any system tables or nonexistent tables:

● If you extract table schema and data only, the legacy database collation must match the collation of the current database collation.

● If you do not qualify table names with owner names, iqlsunload extracts table data from all tables with that table name.

Output Filesiqlsunload generates these output files:

● reload_schema.sql – re-creates schema for unloaded objects (either objects from local store or tables selected by the user.) This script is executed against a node that writes to the multiplex. This node can be



either the existing writer node, or a writer or coordinator for the multiplex after migration, depending on where you plan to re-create the schema.

● extract_data.sql – extracts table data for the unloaded tables from the local store. Execute this script in Interactive SQL while connected to the query node from which it was generated. When this script executes, it generates the data files into the directory data.

● reload_data.sql – loads extracted table data. This script is executed on the node where you ran reload_schema.sql, and reloads the data extracted from the extract_data.sql file.

Permissions

DBA


Related Information

iqunload for SAP IQ 12.7 Database Migration [page 191]Support Processes [page 197]

14.5.2.3 Support Processes

Running iqunload in migration mode (-au) starts iqunlspt and iqsrv16.

iqunlspt

iqunlspt is a self-contained subset of the SAP IQ 12.7 (ESD #5) database engine. It runs as a background process and provides support for legacy database unloads. iqunlspt starts on your legacy database with these options as defaults:

iqunlspt -iqnotemp 100 -iqro 1 -c 48MB -gc 20 -gd all -gk all -gl all -gm 1 -gu all -ti 4400 -x shmem .

If your database requires special switches or memory setting, iqunlspt accepts additional startup arguments. See the Utility Guide.

Default cache settings are sufficient for most migrations. At migration, data queries execute against the system catalogs, not IQ data, so the iqunlspt engine needs lower cache levels than complex queries or multiple concurrent users. The amount of time required to start the legacy database is the same as to start iqunlspt. This time is included in the iqunload startup time.


iqsrv16

iqunload starts iqsrv16 with these options:

iqsrv16 -gp 4096 -c 40p -gc 20 -gd all -gk all -gl all -gm 1 -gu all -qi -qs -ti 4400

iqsrv16 also includes the -n parameter followed by a special randomly generated server name. The -c 40p setting provides a larger cache for the catalog store, allowing the server engine to execute many schema DDL statements. Both server start commands use the default values for -iqmc and -iqtc. If the legacy server requires larger startup values, use the -c switch to increase the server cache memory.


Related Information

iqunload for SAP IQ 12.7 Database Migration [page 191]iqlsunload for Local Store Unload [page 195]

14.5.3 Migration Issues

SAP IQ no longer supports some legacy features. Run iqunload in schema unload mode to generate a script (reload.sql) that contains the entire database schema. Compare the contents of this file to find unsupported syntax and metadata.

In this section:

Unsupported Objects [page 199]Check the schema for objects SAP IQ no longer supports.

Troubleshooting Syntax Changes [page 200]Review the reload script (reload.sql) for legacy syntax that can cause iqunload to fail.

Schema Size [page 201]Increase the cache memory to migrate large and extremely large schemas.

Output Logs [page 202]Check the output logs to isolate migration problems.

Data Storage Changes [page 204]SAP IQ 16.1 migration creates a new catalog store and changes some legacy options.

Post-Migration Files [page 205]iqunload generates a set of files derived from the legacy database. .



14.5.3.1 Unsupported Objects

Check the schema for objects SAP IQ no longer supports.

Table 3: Unsupported metadata

Object Details Action

Invalid database, table, or user names

Table names cannot contain double quote characters. User names and database names cannot contain double quote characters, single quote, or semicolon characters. User names and database names cannot start or end with a space.

Change the object name.

Reserved logical server names

A logical server cannot be named ALL, AUTO, COORDINATOR, DEFAULT, OPEN, or SERVER.

Drop the logical server before upgrading.

Join indexes Join indexes are no longer supported.iqunload does not run if the database to be migrated contains join indexes.

Drop all join indexes before migrating data.

LD indexes LD indexes are no longer supported. Drop all LD indexes before migrating data.

Database with BLANK PADDING OFF

iqunload searches BLANK PADDING OFF databases for any indexes that would become invalid after migration. iqunload fails and lists indexes and constraints that must be dropped and in which order.

Drop these indexes and constraints before the schema reloads, and re-create the indexes and constraints after schema reload has been completed.

Unenforced constraints iqunload fails and lists unenforced constraints that must be dropped.

Drop unenforced constraints before proceeding with migration.

Old 1-byte FP or old 2-byte FP indexes

Databases created with SAP IQ 12.4.2 or earlier may have these indexes. Because these indexes were automatically created by SAP IQ, you cannot drop and re-create them; you must rebuild them.

Allow iqunload to check for these and list them. Rebuild these indexes using sp_iqrebuildindex before migration. The rebuilt indexes are upgraded.

Parent topic: Migration Issues [page 198]

Related Information

Troubleshooting Syntax Changes [page 200]Schema Size [page 201]Output Logs [page 202]Data Storage Changes [page 204]Post-Migration Files [page 205]


14.5.3.2 Troubleshooting Syntax Changes

Review the reload script (reload.sql) for legacy syntax that can cause iqunload to fail.

Problem Solution

A DECLARE LOCAL TEMPORARY TABLE statement in a procedure or trigger causes a syntax error if the table name is prefixed with an owner name.

Remove the owner name.

If a CREATE TRIGGER statement does not include an owner name for the table on which the trigger is defined, and the table must be qualified with an owner when referenced by the user executing the reload.sql file, the statement fails with a '<table–name>' not found error.

Prefix the table name with the owner name.

If an object name (such as a table, column, variable, or parameter name) corresponds to a reserved word introduced in a later version of SAP IQ, the reload fails. (For reserved words, see Reference: Building Blocks, Tables, and Procedures. For example:

CREATE PROCEDURE p( ) BEGINDECLARE NCHAR INT;SET NCHAR = 1; END

Change all references to the reserved word to use a differ-ent name. For variable names, prefixing the name with @ is a common convention that prevents naming conflicts.

Views that use Transact-SQL outer joins (by specifying *= or =*) may not be created properly when they are reloaded.

Add the following line to the reload script:

SET TEMPORARY OPTION tsql_outer_joins='on'

Also set this option for your database. Rewrite any views or stored procedures that use Transact–SQL outer joins.

Stored procedures that use Transact–SQL outer joins may not work correctly.

Rewrite views and stored procedures.

Functions that have OUT or INOUT parameters cannot be reloaded.

OUT and INOUT parameters are no longer supported. Drop these functions before reloading.


Related Information

Unsupported Objects [page 199]Schema Size [page 201]



Output Logs [page 202]Data Storage Changes [page 204]Post-Migration Files [page 205]

14.5.3.3 Schema Size

Increase the cache memory to migrate large and extremely large schemas.

Large Schemas

Default cache settings for large schemas may be too small and can exhaust dynamic memory in the iqsrv16 server. Use the -c switch to increase the server cache memory and -new_startline to pass the switch to the server.

A diagnostic example includes these switches:

-ca 1 -c 1000m -o /iq15outputdir/iq16console.out

● -ca 1 – enables dynamic catalog cache sizing, and logs memory cache statistics to the console.● -c 1000m – sets the initial catalog cache at 1 GB.● -o /outputdir/iq16console.out – specifies the log file for console output.

Use a text editor to examine the .out file log entries. Watch how the catalog store adjusts the cache and determines if the setting is appropriate.

NoteThe value shown for -c is in bytes. Set switches appropriately for your system. To specify megabytes, use the m suffix, as shown.

Extremely Large Schemas

Running iqunload in schema unload mode (iqunload -n) generates a single script (reload.sql ) that includes the entire legacy schema. In some cases, you may need to break a very large reload.sql file into pieces that can be executed sequentially. This also helps the server manage the cache.

If iqunload fails in migration mode (iqunload -au) because dynamic memory is exhausted, set the cache settings as high as your hardware and operating system limitations allow. If the failure continues, contact SAP for assistance.



Related Information

Unsupported Objects [page 199]Troubleshooting Syntax Changes [page 200]Output Logs [page 202]Data Storage Changes [page 204]Post-Migration Files [page 205]

14.5.3.4 Output Logs

Check the output logs to isolate migration problems.

SAP IQ 16.1 Engine Logs

Use the -new_startline "-z -zr all" argument to start iqsrv16 with extra logging:

iqunload -au -c "UID=DBA;PWD=<password>;DBF=/iq-15/unload/127/db/iq127db.db" -new_startline "-z -zr all" -o iq15db.out

SAP IQ 12.7 Engine Logs

Use the START = -z -zr all argument to start the 12.7 engine with extra logging:

iqunload -v -au -c "UID=DBA;PWD=<password>;DBF=/iq-15/unload/127/db/iq127db.db;START=-z -zr all -o iq127db.out"

See the Utility Guide for details about the -z and -zr all parameters.

Server Not Found

A message similar to this indicates that iqunload started the database but could not connect to the server:

SQL error:Database server not found

Check to see if iqunlspt is running and stop the process before retrying iqunload.



For example, here is top output:

load averages: 1.45, 1.19, 0.80; up 3+16:22:31 10:2172 processes: 168 sleeping, 2 zombie, 2 on cpuCPU states: 79.1% idle, 18.9% user, 1.9% kernel, 0.0%iowait, 0.0% swapMemory: 16G phys mem, 13G free mem, 16G swap, 16G freeswapPID USERNAME LWP PRI NICE SIZE RES STATE TIME CPU COMMAND21223 ybrown 1 59 0 2908K 1844K cpu 0:00 0.12% top21172 ybrown 476 59 0 319M 264M sleep 0:01 0.05% iqunlspt24890 ybrown 14 29 10 79M 43M sleep 0:49 0.03% java 20103 ybrown 1 59 0 7916K 2080K sleep 0:00 0.00% sshd

To stop the process, enter the command kill -9 and supply the process ID:

kill –9 21172

Trying to run iqunload without killing an orphaned iqunlspt process, may generate this error:

SQL error: Unable to start specified database: autostarting database failed.

Obsolete Stored Procedures

Migration replaces 12.7 login procedures with new login management functions.

sp_login_environment replaces the 12.7 default login procedure DBA.sp_iq_process_login and dbo.sa_post_login_procedure replaces the 12.7 default post-login procedure DBA.sp_iq_process_post_login. iqunload generally replaces obsolete options with new defaults, but if the 12.7 option is set on a specific user instead of PUBLIC (the default), the log file may report errors:

E. 10/31 16:53:40. Login procedure 'DBA.sp_iq_process_login' caused SQLSTATE '52W09' E. 10/31 16:53:40. Procedure 'sp_iq_process_login' not found


Related Information

Unsupported Objects [page 199]Troubleshooting Syntax Changes [page 200]Schema Size [page 201]Data Storage Changes [page 204]Post-Migration Files [page 205]sp_login_environment system procedure-z database server option


https://help.sap.com/viewer/a898e08b84f21015969fa437e89860c8/16.1.2.14/en-US/3be648506c5f1014a4bf98ee992b6027.html

https://help.sap.com/viewer/a893062984f21015b9e8b03f96ed0cbb/16.1.2.14/en-US/3bcf1cd06c5f1014bcadbab61e41e0a2.html

-zr database server option

14.5.3.5 Data Storage Changes

SAP IQ 16.1 migration creates a new catalog store and changes some legacy options.

Dbspaces

In current versions of SAP IQ, all user data should reside in a user dbspace comprised of one or more files. Migration converts main dbspaces into files under one user dbspace: IQ_MAIN, for the SAP IQ main store, and temporary dbspaces into files under a single temporary dbspace, IQ_SYSTEM_TEMP, for a single SAP IQ temporary store. Existing catalog store dbspaces remain as dbspaces with a single file. All of the old main dbspaces become files in the new iq_main user main dbspace. Migration sets the PUBLIC.default_dbspace option to the value iq_main.

Logical names for files created from converted dbspaces are the dbspace name followed by an underscore and the file ID. For example, a main dbspace with file ID 16384 becomes IQ_SYSTEM_MAIN_16384.

Main Store

Migration creates a new system file for the IQ_SYSTEM_MAIN dbspace that contains no tables. By default, the name of this file is new_main_store.iq, but you can use the ms_filename argument to specify a different file name. The iqunload utility computes the size of the new IQ_SYSTEM_MAIN based on the size of your existing database.

If you accept the default settings for iqunload -au -c, the new store marked as MAIN has DBSpaceName = IQ_SYSTEM_MAIN, DBFileName = IQ_SYSTEM_MAIN and path = new_main_store.iq. For multiplex migration, the location of the new main store must be visible to all nodes on the multiplex, and you must use the -ms_filename argument to specify the path instead of the default value of new_main_store.iq.

When you migrate a database, specify the file to use for the new IQ_SYSTEM_MAIN dbspace, its name, whether or not to use a raw device, and the size of the main store and its reserve.

Migrating IQ_SYSTEM_MAIN

Specify the IQ_SYSTEM_MAIN size in the database migration command. The -ms_size parameter requires a value in MB, not GB. Omit -ms_size and -ms_reserve to specify a raw device. For a raw device, you must specify an unused raw partition.

This statement creates an IQ_SYSTEM_MAIN on a raw device:

iqunload -au -ms_filename /dev/rdsk/c1t0d1 -c "UID=DBA;PWD=SQL;DBF=latest.db"



https://help.sap.com/viewer/a893062984f21015b9e8b03f96ed0cbb/16.1.2.14/en-US/3bcf350c6c5f10148193ba9cdfb86912.html


Related Information

Unsupported Objects [page 199]Troubleshooting Syntax Changes [page 200]Schema Size [page 201]Output Logs [page 202]Post-Migration Files [page 205]

14.5.3.6 Post-Migration Files

iqunload generates a set of files derived from the legacy database. .

This table lists pre- and post-migration files:

Pre-Migration Post-Migration Files Description

asiqdemo.db asiqdemo.db.before_schema_reload

The 12.7 catalog database. This file is copied at the OS level upon successful migration; it is not a result of the SQL backup command.

asiqdemo.log asiqdemo.log The database log file is regenerated when the migrated database is used with the 16.1 server.

asiqdemo.iq asiqdemo.iq The old SAP IQ 12.7 IQ_SYSTEM_MAIN dbspace. This file and all other user dbspaces are unaffected by the migration process. This dbspace is added as a file to a user main dbspace.

asiqdemo.iqtmp

asiqdemo.iqtmp The IQ_SYSTEM_TEMP dbspace. No operations are performed on this dbspace during migration. This file becomes the IQ 16.1 database temporary store.

asiqdemo.iqmsg

asiqdemo.iqmsg.before_schema_reload

The IQ 12.7 message file. This file is copied at the OS level upon successful migration.

asiqdemo.db The new 16.1 migrated catalog database.

new_main_store.iq The new IQ_SYSTEM_MAIN dbspace for the migrated database.



Related Information

Unsupported Objects [page 199]Troubleshooting Syntax Changes [page 200]Schema Size [page 201]Output Logs [page 202]Data Storage Changes [page 204]

14.5.4 Unloading Legacy Schemas

To unload legacy schema, run iqunload in schema unload mode (iqunload -n ) on the same machine as the legacy schema.

Procedure

1. Copy these files from <$IQDIR16>/unload to <$ASDIR>/scripts:

○ unloadold.sql○ unload.sql ○ optdeflt.sql○ opttemp.sql

2. Start the legacy server.3. Run iqunload in schema unload mode (iqunload -n ).

Include the appropriate connection parameters and other startup options. Schema unload mode creates a SQL script (reload.sql) in the current directory that contains the legacy database schema. reload.sql does not contain any checkpoints. For very large schemas, edit reload.sql, to add a few checkpoints. If you do not include extra checkpoints, IQ generates additional metadata objects that requires extra (-iqmc) main cache memory.

reload.sql also contains a CREATE DATABASE template command that is commented out.

4. Create a new 16.1 database.

Set the IQ SIZE and TEMPORARY SIZE clauses to create an IQ_SYSTEM_MAIN of 10 GB and IQ_SYSTEM_TEMP of 5 GB. For example:

CREATE DATABASE 'test.db' IQ PATH 'test.iq'IQ SIZE 10240TEMPORARY PATH 'test.iqtmp' TEMPORARY SIZE 5120

5. Start and connect to the new database.6. Run the reload.sql against the new database.

Execution time roughly approximates the actual time to allow for database migration, excluding validation checks. Correct any errors. Perform this process iteratively until you can cleanly load the legacy schema.



14.5.5 Migrating Legacy Databases

Run iqunload in database migration mode (iqunload -au) to migrate a legacy database.

In this section:

Simplex Migration [page 207]Migrate a 12.7 database simplex database to 16.1.

Multiplex Migration [page 209]Migrate multiplex databases, performing all steps in sequence.

14.5.5.1 Simplex Migration

Migrate a 12.7 database simplex database to 16.1.

1. Migrating the Legacy Database [page 207]Make sure that the database file is not in use, and run the iqunload utility with the -au (migrate database) and -c (connection parameters).

2. Verifying the Migrated Database [page 208]To verify simplex migration, start the migrated database in read-only mode and perform post-migration tasks.

14.5.5.1.1 Migrating the Legacy Database

Make sure that the database file is not in use, and run the iqunload utility with the -au (migrate database) and -c (connection parameters).

This command migrates the simplex database mytest and saves output in unload.out in the current directory:

iqunload –au –c "uid=DBA;pwd=SQL;dbf=mytest" –o unload.out

The database and the iqunload utility must be on the same machine to migrate the database, or iqunload returns an error. -o is an optional switch that sends a copy of the console output to the specified log file, here named unload.out.

Because the example specified DBF=mytest.db, the iqunload utility attempts to connect to this database in the current directory. You can also specify the full path to the database, as shown here:

iqunload -au -c "dbf=/ybrown/iq-16/unload/iq127db.db;uid=DBA;pwd=SQL"Output: Sybase IQ Unload Utility Version 16.0.0.788 Connecting and initializing Unloading user and group definitions Unloading table definitions Unloading index definitions


Unloading functions Unloading view definitions Unloading procedures Unloading triggers Unloading SQL Remote definitions Creating new database Creating indexes for (1/14) "DBA"."sales_order"

Creating indexes for (2/14) "DBA"."sales_order_items" Creating indexes for (3/14) "DBA"."contact" Creating indexes for (4/14) "DBA"."customer" Creating indexes for (5/14) "DBA"."fin_code" Creating indexes for (6/14) "DBA"."fin_data" Creating indexes for (7/14) "DBA"."product" Creating indexes for (8/14) "DBA"."department" Creating indexes for (9/14) "DBA"."employee" Creating indexes for (10/14)"DBA"."alt_sales_order" Creating indexes for (11/14) "DBA"."alt_sales_order_items" Creating indexes for (12/14) "DBA"."iq_dummy" Creating indexes for (13/14) "DBA"."emp1" Creating indexes for (14/14) "DBA"."sale"

Successfully backed up file "/ybrown/iq-16/ unload/127/db/iq127db.db" by renaming it to "/ybrown/iq-16/unload/127/db/iq127db.db.before_schema_reload".Successfully backed up file "/ybrown/iq-16/unload/127/db/iq127db.iqmsg" by renaming it to "/ybrown/iq-16/unload/127/db/iq127db.iqmsg.before_schema_reload" Successfully reloaded schema of database "/ybrown/iq-16/unload/127/db/iq127db.db".

Perform post migration tasks. Make sure that the migration completed correctly. Back up your new databases.

Parent topic: Simplex Migration [page 207]

Next task: Verifying the Migrated Database [page 208]

14.5.5.1.2 Verifying the Migrated Database

To verify simplex migration, start the migrated database in read-only mode and perform post-migration tasks.

Procedure

1. Start the 16.1 database in read-only mode:

start_iq -iqro 1

When starting the coordinator in 16.1, use the same port as the 12.7 writer server.2. Issue a CHECKPOINT command.



3. Run the 16.1 version of sp_iqcheckdb in verify mode:

sp_iqcheckdb ('verify database')

If you run the procedure from Interactive SQL, redirect output to a file by entering:

dbisql -c "..." "sp_iqcheckdb ('verify database')" >& filename

where “...” represents startup parameters for your database.4. Issue a COMMIT statement.

5. Check sp_iqcheckdb results for errors.

If there is an error, you can revert to the previous database as long as you do not restart the database in write mode. To revert to the 12.7 catalog , copy all the .before_schema_reload files to the same file without the .before_schema_load file extension.

6. After you perform the read-only checks, stop the database server and restart in write mode.

Results

NoteFor information on interpreting sp_iqcheckdb results and corrective action, see Administration: Backup, Restore, and Data Recovery > System Recovery and Database Repair.

Task overview: Simplex Migration [page 207]

Previous: Migrating the Legacy Database [page 207]

14.5.5.2 Multiplex Migration

Migrate multiplex databases, performing all steps in sequence.

1. Synchronizing the Multiplex Nodes [page 210]Check the SQL Remote and multiplex server log files for synchronization problems.

2. Migrate Local Stores [page 211]To move the 12.7 local stores before migration, use iqlsunload.

3. Start the Multiplex Write Server [page 216]To clean the internal state information, start the write server in single-node mode.

4. Multiplex Migration Parameters [page 217]To migrate the multiplex, run iqunload with the appropriate parameters.

5. Verifying the Migrated Multiplex Database [page 219]Verify the migrated database in read-only mode and correct any errors.


6. Starting the Coordinator [page 220]Starting the multiplex coordinator in single-node mode (-iqmpx_sn) and read-only (-iqro) performs some initial database checks. For coordinators, the server must reset an identity cookie before you can use the multiplex.

7. Manually Synchronize the Secondary Nodes [page 220]To start the secondary nodes, install SAP IQ 16.1, then synchronize from the coordinator node. When you migrate a query node, it becomes a reader node.

8. Start the Secondary Nodes [page 221]To start the secondary nodes, all nodes of the multiplex must be running.

9. Set the Failover Node [page 222]After you migrate the multiplex data, connect to the coordinator, and set the failover node.

10. Troubleshooting Multiplex Migration [page 222]If you cannot migrate your multiplex database, try this alternate method.

14.5.5.2.1 Synchronizing the Multiplex Nodes

Check the SQL Remote and multiplex server log files for synchronization problems.

Procedure

1. Start the multiplex server.2. Start SQL Remote on all multiplex nodes.

Give the multiplex time to propagate any changes throughout the multiplex. To do this, look at the write server console log file and check that the events starting with ev_iqmpx have successfully executed. By default, the server console log file is created in $ASDIR/logfiles.

For example:

Now accepting requestsOS Available: 933096K, Working Set: 83988K, Cache Target: 11483K OS Available: 860680K, Working Set: 83996K, Cache Target: 11483KNext time for 'ev_iqmpxq2w' is 2008/11/23 22:03:00.000Next time for 'ev_iqmpxstatus' is 2008/11/23 22:03:00.000OS Available: 859232K, Working Set: 84112K, Cache Target: 11489KOS Available: 861052K, Working Set: 84424K, Cache Target: 11489KOS Available: 860972K, Working Set: 84428K, Cache Target: 11489KOS Available: 850248K, Working Set: 85540K, Cache Target: 11579KOS Available: 850104K, Working Set: 85568K, Cache Target: 11579KNext time for 'ev_iqmpxq2w' is 2008/11/23 22:04:00.000Next time for 'ev_iqmpxstatus' is 2008/11/23 22:04:00.000OS Available: 850120K, Working Set: 85600K, Cache Target: 11579KNext time for 'ev_iqmpxq2w' is 2008/11/23 22:05:00.000Next time for 'ev_iqmpxstatus' is 2008/11/23 22:05:00.000 OS Available: 852668K, Working Set: 85604K, Cache Target: 11579K

3. Wait for SQL Remote to scan the log files, then view the logs.

Wait for SQL Remote to process any messages:

I. 11/23 22:06:10. Scanning logs starting at offset 0001787252



I. 11/23 22:06:10. Hovering at end of active log

4. Shut down SQL Remote and multiplex servers.If you simply shut down the multiplex servers, the SQL Remote servers detect that the multiplex servers are no longer running and shut themselves down. By default, the SQL Remote servers should shut themselves down within 60 seconds.

5. Shut down query servers in the multiplex. They are no longer required.6. If the logs report no errors, verify the database.

Task overview: Multiplex Migration [page 209]

Next: Migrate Local Stores [page 211]

14.5.5.2.2 Migrate Local Stores

To move the 12.7 local stores before migration, use iqlsunload.

To migrate your local store, consolidate node-specific information into either the existing 12.7 writer or the new SAP IQ 16.1 main store. Customize the process to meet your data requirements.

For query nodes with node- or department-specific information, use tablespaces and partitioning to achieve the same results.

If information is duplicated across your query nodes, you may need to migrate only a single query server's local store. The duplicated information on the other query servers becomes redundant and can be ignored for multiplex migration.

In this section:

Partitioning Query Server Data [page 212]If the same table exists on multiple query nodes, and each node has its own subset of the data, manually edit the local store migration scripts.

Addressing Overlapping Query Server Data [page 212]If the same table exists on each query node with overlapping data sets, you must resolve the issue. Extract the data files to ensure that data sets are unique, or rename the tables and then reload all the unique tables.

Moving Local Stores [page 215]Unload and move the 12.7 local stores.

Parent topic: Multiplex Migration [page 209]

Previous task: Synchronizing the Multiplex Nodes [page 210]

Next: Start the Multiplex Write Server [page 216]


14.5.5.2.2.1 Partitioning Query Server Data

If the same table exists on multiple query nodes, and each node has its own subset of the data, manually edit the local store migration scripts.

Context

For a department-specific employee table on each query server, follow these basic steps:

Procedure

1. Unload the schema and data from the query nodes.

The reload_schema.sql script produced for each query node contains the same schema definition for employee.

2. Execute the reload_schema.sql from one of the query nodes against either the existing 12.7 writer or the new SAP IQ 16.1 main store.

3. Execute the reload_data.sql script from each of the query nodes against the same server.

This procedure creates the employee table once but loads each query node data set.

Task overview: Migrate Local Stores [page 211]

Related Information

Addressing Overlapping Query Server Data [page 212]Moving Local Stores [page 215]

14.5.5.2.2.2 Addressing Overlapping Query Server Data

If the same table exists on each query node with overlapping data sets, you must resolve the issue. Extract the data files to ensure that data sets are unique, or rename the tables and then reload all the unique tables.

Procedure

1. Run iqlsunload against all query servers with local stores that have the data to consolidate.



2. Modify the reload_schema.sql and reload_data.sql files to use the new table names. Do not modify extract_data.sql; it references the table found in the query server's local store.

3. Run extract_data.sql from each node.

Results

The following example shows modifications to the iqlsunload output to carry out step 2. Suppose that the reload_schema.sql script contains:

CREATE TABLE "DBA"."sales_order" "id" unsigned int NOT NULL IQ UNIQUE (648), "cust_id" unsigned int NOT NULL IQ UNIQUE (111), "order_date" "datetime" NOT NULL IQ UNIQUE (376), "fin_code_id" char(2) NULL IQ UNIQUE (1), "region" char(7) NULL IQ UNIQUE (5), "sales_rep" unsigned int NOT NULL IQ UNIQUE (75), PRIMARY KEY ("id"),

Modify reload_schema.sql to:

CREATE TABLE "DBA"."q1_sales_order" "id" unsigned int NOT NULL IQ UNIQUE (648), "cust_id" unsigned int NOT NULL IQ UNIQUE (111), "order_date" "datetime" NOT NULL IQ UNIQUE (376), "fin_code_id" char(2) NULL IQ UNIQUE (1), "region" char(7) NULL IQ UNIQUE (5), "sales_rep" unsigned int NOT NULL IQ UNIQUE (75), PRIMARY KEY ("id"),

extract_data.sql contains:

---- Extract Table Data for table sales_order -- NOTE: Approximately 57672 bytes of storage space.-- will be required to extract the data for this table.---- The following will unload the data for table sales_order, row group 1, column group 1

SET TEMPORARY OPTION temp_extract_name1 = 'DBA_sales_order_1_1_DATA_1.inp';SET TEMPORARY OPTION temp_extract_name2 ='DBA_sales_order_1_1_DATA_2.inp';SET TEMPORARY OPTION temp_extract_name3 ='DBA_sales_order_1_1_DATA_3.inp';SET TEMPORARY OPTION temp_extract_name4 ='DBA_sales_order_1_1_DATA_4.inp';SET TEMPORARY OPTION temp_extract_name5 ='DBA_sales_order_1_1_DATA_5.inp';SET TEMPORARY OPTION temp_extract_name6 ='DBA_sales_order_1_1_DATA_6.inp';SET TEMPORARY OPTION temp_extract_name7 ='DBA_sales_order_1_1_DATA_7.inp';SET TEMPORARY OPTION temp_extract_name8 ='DBA_sales_order_1_1_DATA_8.inp';SELECT id, cust_id, order_date, IFNULL(fin_code_id, @null_string, fin_code_id),IFNULL(region, @null_string, region), sales_rep FROM "DBA"."sales_order"


WHERE rowid( "sales_order" ) >= 1 AND rowid( "sales_order" ) <= 648;

SET TEMPORARY OPTION temp_extract_name1 = '';SET TEMPORARY OPTION temp_extract_name2 = '';SET TEMPORARY OPTION temp_extract_name3 = '';SET TEMPORARY OPTION temp_extract_name4 = '';SET TEMPORARY OPTION temp_extract_name5 = '';

Leave extract_data.sql code unchanged to extract the sales_order table from the query server.

Suppose that reload_data.sql contains:

-- Reload Table Data for table "sales_order" -------------------------------------------------ALTER TABLE "DBA"."sales_order" MODIFY cust_id NULL;ALTER TABLE "DBA"."sales_order" MODIFY order_date NULL;ALTER TABLE "DBA"."sales_order" MODIFY sales_rep NULL;SET @max_row_id = ( SELECT MAX( rowid( "sales_order" ) )+1 FROM "DBA"."sales_order" );

SET @load_statement = 'LOAD TABLE "DBA"."sales_order"(id, cust_id, order_date, fin_code_id NULL('''||@null_string||''' ) , region NULL('''||@null_string||''' ) , sales_rep) FROM'''||@extract_directory||'DBA_sales_order_1_1_DATA_1.inp'','''||@extract_directory||'DBA_sales_order_1_1_DATA_2.inp'', '''||@extract_directory||'DBA_sales_order_1_1_DATA_3.inp'','''||@extract_directory||'DBA_sales_order_1_1_DATA_4.inp'','''||@extract_directory||'DBA_sales_order_1_1_DATA_5.inp'', '''||@extract_directory||'DBA_sales_order_1_1_DATA_6.inp'', '''||@extract_directory||'DBA_sales_order_1_1_DATA_7.inp'', '''||@extract_directory||'DBA_sales_order_1_1_DATA_8.inp'' ROW DELIMITED BY ''\n'' QUOTES ON ESCAPES OFF DEFAULTS OFF FORMAT ASCII IGNORE CONSTRAINT ALL 0 START ROW ID '||@max_row_id;

CALL IqExecuteCommand( @load_statement ); ALTER TABLE "DBA"."sales_order" MODIFY cust_id NOTNULL;ALTER TABLE "DBA"."sales_order" MODIFY order_date NOTNULL;ALTER TABLE "DBA"."sales_order" MODIFY sales_rep NOT NULL;

Change reload_data.sql to:

-- Reload Table Data for table "q1_sales_order"-------------------------------------------------ALTER TABLE "DBA"."q1_sales_order" MODIFY cust_id NULL;ALTER TABLE "DBA"."q1_sales_order" MODIFY order_dateNULL;ALTER TABLE "DBA"."q1_sales_order" MODIFY sales_repNULL;SET @max_row_id = ( SELECT MAX( rowid( "q1_sales_order"



) )+1 FROM "DBA"."q1_sales_order" );

SET @load_statement = 'LOAD TABLE "DBA"."q1_sales_order"(id, cust_id, order_date, fin_code_id NULL('''||@null_string||''' ) , region NULL('''||@null_string||''' ) , sales_rep) FROM'''||@extract_directory||'DBA_q1_sales_order_1_1_DATA_1.inp'','''||@extract_directory||'DBA_q1_sales_order_1_1_DATA_2.inp'','''||@extract_directory||'DBA_q1_sales_order_1_1_DATA_3.inp'','''||@extract_directory||'DBA_q1_sales_order_1_1_DATA_4.inp'', '''||@extract_directory||'DBA_q1_sales_order_1_1_DATA_5.inp'', '''||@extract_directory||'DBA_q1_sales_order_1_1_DATA_6.inp'', '''||@extract_directory||'DBA_q1_sales_order_1_1_DATA_7.inp'', '''||@extract_directory||'DBA_q1_sales_order_1_1_DATA_8.inp'' ROW DELIMITED BY ''\n'' QUOTES ON ESCAPES OFFDEFAULTS OFF FORMAT ASCII IGNORE CONSTRAINT ALL 0 START ROW ID '||@max_row_id;

CALL IqExecuteCommand( @load_statement );ALTER TABLE "DBA"."q1_sales_order" MODIFY cust_id NOT NULL;ALTER TABLE "DBA"."q1_sales_order" MODIFY order_date NOT NULL;ALTER TABLE "DBA"."q1_sales_order" MODIFY sales_rep NOT NULL;

This example shows query server schema and data that require intervention during migration. Your situation may vary, but you have complete control of the content of the final reload_schema.sql and reload_data.sql files.


Related Information

Partitioning Query Server Data [page 212]Moving Local Stores [page 215]

14.5.5.2.2.3 Moving Local Stores

Unload and move the 12.7 local stores.

Prerequisites

Upgrade to SAP IQ 12.7 ESD #5 or later.


Procedure

1. Source the ASIQ-12_7.sh or .csh file.

2. Run the 12.7 iqlsunload utility against each query server with a local store.

3. Edit reload_schema.sql:

○ Delete unwanted objects.○ Change any commented objects in the reload_schema.sql that you want to reload.○ Add commands to define any objects that you defined in sp_mpxcfg_<servername> procedures.

4. Edit extract_data.sql to remove objects you do not want to migrate. These objects are generally the same ones you removed from reload_schema.sql.

5. Use Interactive SQL to run extract_data.sql from your 12.7 local store.

You now have unloaded the schema and data for local objects in the 12.7 local store.6. Run the reload_schema.sql and reload_data.sql scripts against the 12.7 write server.

NoteIf you prefer, wait until the write server has been migrated to version 16.1 and run reload_schema.sql and reload_data.sql against the new coordinator.


Related Information

Partitioning Query Server Data [page 212]Addressing Overlapping Query Server Data [page 212]

14.5.5.2.3 Start the Multiplex Write Server

To clean the internal state information, start the write server in single-node mode.

NoteYou must specify your login and password as arguments to the start_server script.

Start the writer node with the server arguments -gm 1 and -iqmpx_sn 1:

-gm 1 -iqmpx_sn 1

If you use administrative startup scripts, create a copy of the start_server.sh script to start the write server you want to migrate. For example, copy the existing file start_server.sh to a new file called start_server_single_node.sh.



Suppose that start_server.sh contains this startup command:

start_asiq -STARTDIR /work/iq-127/mpx/main @/work/iq- 127/mpx/main/params.cfg -n mpx_main $readonly $nomain -x tcpip{port=62631} /work/iq-127/mpx/main/main.db $dbkey

Add the two single node startup arguments to change the preceding command as follows in start_server_single_node.sh:

start_asiq -STARTDIR /work/iq-127/mpx/main @/work/iq- 127/mpx/main/params.cfg -n mpx_main -gm 1 -iqmpx_sn 1 $readonly $nomain -x tcpip{port=62631} /work/iq-127/ mpx/main/main.db $dbkey

There are now two script files, start_server.sh and start_server_single_node.sh to make the server ready for migration:

1. Start the writer node with start_server_single_node.sh.2. Shut down the writer node.3. Start the writer node with start_server.sh.4. Shut down the writer node.5. Shut down the SAP Sybase IQ 12.7 server.


Previous: Migrate Local Stores [page 211]

Next: Multiplex Migration Parameters [page 217]

14.5.5.2.4 Multiplex Migration Parameters

To migrate the multiplex, run iqunload with the appropriate parameters.

Minimum required parameters for a multiplex writer are -au (migrate database), -c (connection parameters), ENG= connection parameter and -ms_filename. The ENG= value must match the existing server name in SAP IQ 12.7, and the -ms_filename specifies the new main store for the migrated writer. This path must be the same for all nodes in the multiplex.

There are two differences in the way you will execute the iqunload utility for multiplex:

● Specify the engine name in the -c connection parameters. This is the same name that your <mpx_dir>/<writer_node>/start_server script file uses to start the writer node. The iqunload utility initially attempts to start the database server as simplex. This start requires the name of the server to match the naming conventions for the multiplex nodes. Once iqunload detects that the server is a multiplex node, it shuts the node down and restarts it using the -iqmpx_sn 1 option.

● The name of the new main store must be visible and accessible by all nodes of the multiplex. This is important because the main store file name defaults to new_system_main.iq, and its location is relative to the catalog database file (.db). Later, when you synchronize the SAP IQ 16.1 multiplex, the catalog is replicated to the secondary nodes, formerly known as the query nodes. If you leave the default value for the


main store name unchanged, the path remains new_system_main.iq and secondary nodes cannot find the shared main store.

For multiplex writers, required arguments are:

● ENG – argument specifies the multiplex main engine name. iqunload attempts to start the database and determine whether the database is a simplex or multiplex. If multiplex, the server name is enforced. If you are unsure of the server name, check the administrative script start_server in the database directory.

● DBF – argument must specify the actual path used to create the multiplex. If you are unsure of this, look at the SYSIQFILE table in your 12.7 server to verify the database path.

● -ms_filename – argument specifies the location of the new main store. This path must be visible and accessible by all servers in the multiplex.

For example:

iqunload -au -v -c "uid=DBA;pwd=SQL;dbf=/sunx5prod/users/marshall/mpx127/w1/w1.db;eng=w1_1234" -ms_filename ../shared/new_main_store.iq

Sybase IQ Unload Utility Version 15.2.0.5533 Connecting and initializing 2008-11-23 22:32:07 Unloading user and group definitions 2008-11-23 22:32:08 Unloading table definitions 2008-11-23 22:32:09 Unloading index definitions 2008-11-23 22:32:09 Unloading functions 2008-11-23 22:32:09 Unloading view definitions 2008-11-23 22:32:09 Unloading procedures 2008-11-23 22:32:09 Unloading triggers 2008-11-23 22:32:09 Unloading SQL Remote definitions 2008-11-23 22:32:09 Unloading MobiLink definitions 2008-11-23 22:32:10 Creating new database 2008-11-23 22:32:48 Reloading user and group definitions 2008-11-23 22:32:48 Reloading table definitions 2008-11-23 22:32:53 Reloading index definitions 2008-11-23 22:32:53 Reloading functions 2008-11-23 22:32:53 Reloading view definitions 2008-11-23 22:32:53 Reloading procedures 2008-11-23 22:32:53 Reloading triggers 2008-11-23 22:32:53 Reloading SQL Remote definitions 2008-11-23 22:32:53 Reloading MobiLink definitions

Successfully backed up file "/sunx5prod/users/marshall/mpx127/w1/w1.db" by renaming it to"/sunx5prod/users/marshall/mpx127/w1/w1.db.before_schema_reload".Successfully backed up file"/sunx5prod/users/marshall/mpx127/main.db" by renaming it to"/sunx5prod/users/marshall/mpx127/main.db.before_schema_reload".Successfully backed up file/sunx5prod/users/marshall/mpx127/main.iqmsg" by renaming it to"/sunx5prod/users/marshall/mpx127/main.iqmsg.before_schema_reload".Successfully reloaded schema of database "/sunx5prod/users/marshall/mpx127/main.db".


Previous: Start the Multiplex Write Server [page 216]



Next task: Verifying the Migrated Multiplex Database [page 219]

14.5.5.2.5 Verifying the Migrated Multiplex Database

Verify the migrated database in read-only mode and correct any errors.

Procedure

1. Start the database using the read-only switch, -iqro 1. Start the coordinator (the 12.7 write server) using both -iqro 1 and single node mode, -iqmpx_sn 1.

When starting the coordinator in 16.1, use the same port used by the 12.7 writer server.2. Issue a CHECKPOINT command.

3. Run sp_iqcheckdb in verify mode:

sp_iqcheckdb 'verify database'

4. Issue a COMMIT statement.

Results

The server is currently in read-only mode, and cannot complete some post migration tasks. Additionally, the verification reports some problems with Block Count Mismatch, Blocks Leaked, and Unallocated Blocks in Use. No other segments of the verify database should report any errors.

For example:

'** Block Count Mismatch','79','*****' '** Blocks Leaked','25','*****' '** Unallocated Blocks in Use','104','*****'

Examine the sp_iqcheckdb report for errors. If you need to contact SAP Technical Support, you must provide the output from sp_iqcheckdb.


Previous: Multiplex Migration Parameters [page 217]

Next: Starting the Coordinator [page 220]


14.5.5.2.6 Starting the Coordinator

Starting the multiplex coordinator in single-node mode (-iqmpx_sn) and read-only (-iqro) performs some initial database checks. For coordinators, the server must reset an identity cookie before you can use the multiplex.

Once you successfully restart the coordinator with iqro 1 and iqmpx_sn 1, shut it down and restart it without any special switches.

For example:

start_iq @params.cfg -n mpx_main -iqmpx_ov 1 -x 'tcpip{port=62631}' /workserver/work/iq-127/mpx/main.db


Previous task: Verifying the Migrated Multiplex Database [page 219]

Next task: Manually Synchronize the Secondary Nodes [page 220]

14.5.5.2.7 Manually Synchronize the Secondary Nodes

To start the secondary nodes, install SAP IQ 16.1, then synchronize from the coordinator node. When you migrate a query node, it becomes a reader node.

Procedure

1. Back up the query node files. Back up existing catalog .db, catalog .log and iqmsg files.

For example:

rename /sunx5prod/users/work/iq-127/mpx/q1/q1.db /sunx5prod/users/work/iq-127/mpx/q1/q1.db.before_schema_reloadrename /sunx5prod/users/work/iq-127/mpx/q1/q1.log /sunx5prod/users/work/iq-127/mpx/q1/q1.log.before_schema_reloadrename /sunx5prod/users/work/iq-127/mpx/q1/q1.iqmsg /sunx5prod/users/work/iq-127/mpx/q1/q1.iqmsg.before_schema_reload

2. Issue a dbbackup command to synchronize servers. You might have a different name for the query node's catalog file, depending on your configuration. In the following example, q1.db is the catalog file name on the query node:

dbbackup -y -x -c "uid=dba;pwd=sql;eng=mpx_main;dbf=/sunx5prod/users/work/iq-127/mpx/main/main.db" /sunx5prod/users/work/iq-127/mpx/q1



SQL Anywhere Backup Utility Version 11.0.1.5533 Debug (702 of 699 pages, 100% complete)Transaction log truncated Database backup completed

3. If your query nodes do not use a different catalog database name, skip to step 4.

Step 2 synchronizes the catalog database file from the coordinator. If you prefer to use the same catalog database file name as the coordinator, adjust any server start and stop administration scripts on the secondary nodes to use the new name.

To retain the same catalog database file names:○ Rename the synchronized coordinator catalog database file name. For example, assuming the

coordinator file was called main.db and the secondary server was called q1.db, enter:

mv main.db q1.db

rename main.db q1.db

○ Rename the log file for the query node. This is necessary as the file renamed above still contains an internal pointer to main.log:

dblog -t q1.log q1.db

4. Start the secondary server in normal mode:

start_iq @params.cfg -n mpx_q1 -x 'tcpip{port=62632}' -o /worksrver/work/iq-127/mpx/q1/o.out -Z -zr all -zo /worksrver/iq-127/mpx/q1/zo.out /workserver/work/ iq-127/mpx/q1/main.db

The above command line is derived from your existing query server start_server administration script.

5. Repeat these steps on the remaining secondary nodes that you want to migrate.


Previous: Starting the Coordinator [page 220]

Next task: Start the Secondary Nodes [page 221]

14.5.5.2.8 Start the Secondary Nodes

To start the secondary nodes, all nodes of the multiplex must be running.

Procedure

Start the secondary servers with the command line startup utility.


For example:

start_iq @params.cfg -n <server_name> database_file.db

Where <<server_name> specifies the secondary server. You can obtain the name from the existing start server administration script. The specified database_file.db is the name resulting after you performed the secondary node synchronization.


Previous task: Manually Synchronize the Secondary Nodes [page 220]

Next task: Set the Failover Node [page 222]

14.5.5.2.9 Set the Failover Node

After you migrate the multiplex data, connect to the coordinator, and set the failover node.

Procedure

Use a command like this to set the failover node:.

ALTER MULTIPLEX SERVER servername ASSIGN AS FAILOVER SERVER

Where <servername> is one of the secondary nodes.


Previous task: Start the Secondary Nodes [page 221]

Next: Troubleshooting Multiplex Migration [page 222]

14.5.5.2.10 Troubleshooting Multiplex Migration

If you cannot migrate your multiplex database, try this alternate method.

● Drop all query nodes, to change the SAP IQ 12.7 multiplex to a simplex database.● Follow the steps for simplex databases to migrate the database to SAP IQ 16.1.● Convert the simplex SAP IQ 16.1 database to multiplex, following the steps in Administration: Multiplex >

Create Multiplex Servers > Converting Databases to Multiplex.




Previous task: Set the Failover Node [page 222]

14.5.6 Postmigration Tasks

SAP IQ 16 databases upgraded from 12.7 are initially set to run in 15.x compatibility mode. To complete the change from 15.x to 16.1, you must explicitly change several 15.x compatibility settings to complete the 16.1 upgrade.

Indexes

● In Fast Projection (FP) indexes, continuous NBit dictionary compression replaces FP(1), FP(2), and FP(3) byte dictionary compression. FP(1), FP(2), and FP(3) indexes roll over to NBit(8), NBit(16), and NBit(24) respectively. All data types except LOB (both character and binary) and BIT data types may be NBit columns.If FP_NBIT_IQ15_COMPATIBILITY is OFF, IQ UNIQUE determines whether the column loads as Flat FP or NBit. Setting IQ UNIQUE to 0 loads the column as Flat FP. Columns without an IQ UNIQUE constraint load as NBit up to the NBit auto-sizing limits.

● New tiered HG index structure decouples load performance from HG index size. In 15.x, load throughput could degrade as the amount of data in an HG index increased. As the index grew, loading the same amount of data could take more time. The new tiered structure decouples load performance from the HG index size to increase throughput.

Constraints

Constraint Description

IQ UNIQUE In SAP IQ 16.1, IQ UNIQUE explicitly defines the expected cardinality of a column and determines whether the column loads as Flat FP or NBit. Columns retain their IQ UNIQUE(<n>) value during a 15.x to 16.1 database upgrade.

Setting IQ UNIQUE to 0 loads the column as Flat FP. Columns without an IQ UNIQUE constraint or columns with an IQ UNIQUE <n> value that is less than the limit defined by the FP_NBIT_AUTOSIZE_LIMIT option is not necessary. Auto-size functionality automatically sizes all low or medium cardinality columns as NBit. Use IQ UNIQUE in cases where you want to where you want to load the column as Flat FP or when you want to load as NBit and the number of distinct values exceeds the auto-size limits.


Options

Option Description

FP_NBIT_IQ15_COMPATIBILITY Provides tokenized FP support similar to that available in 15.x. This option is ON by default in all 16.1 databases upgraded from 15.x and OFF in all newly created 16.1 databases.

● If this option is ON, the database engine uses the MINIMIZE_STORAGE, FP_LOOKUP_SIZE, and FP_LOOKUP_SIZE_PPM options to optimize column storage. These options are ignored in 16.1.

● If this option is OFF, the database engine ignores 15.x options and columns conform to SAP IQ NBit storage options.

Set this option to OFF to take advantage of NBit column compression.

CREATE_HG_WITH_EXACT_DISTINCTS

Determines whether new HG indexes explicitly created with a CREATE INDEX command, or implicitly creating or altering a table with a PRIMARY KEY or a FOREIGN KEY declaration, are tiered or non-tiered. This option is ON in 16.1 databases upgraded from 15.x and all newly created 16.1 databases. If this option is ON, all new HG indexes are non-tiered. To take advantage of the new tiered HG index structure, set this option to OFF.

Use sp_iqrebuildindex to convert non-tiered HG indexes to tiered HG and vice versa.

CREATE_HG_AND_FORCE_PHYSICAL_DELETE

Governs 16.1 delete behavior for tiered HG indexes. This option determines whether SAP IQ performs a physical delete immediately or defers the delete to a point later in the load.

CREATE_HG_AND_FORCE_PHYSICAL_DELETE is ON by default, which instructs SAP IQ to perform physical deletes.

REVERT_TO_V15_OPTIMIZER REVERT_TO_V15_OPTIMIZER forces the query optimizer to mimic SAP IQ 15.x behavior. REVERT_TO_V15_OPTIMIZER='ON' by default in all 16.1 databases upgraded from 15.x. REVERT_TO_V15_OPTIMIZER='OFF' by default in all newly created SAP IQ 16.1 databases.

If you plan to use SAP IQ hash partitioning features, set the REVERT_TO_V15_OPTIMIZER ='OFF' in databases upgraded from 15.x to 16.1.

Object Names

Reserved words cannot be used as object names.

An SAP IQ 15.x database could contain tables, columns, and other objects named row. In SAP IQ 16.1, row is a reserved word and cannot be used as an object name.



To use a reserved word as an object name, enclosed the object name in brackets (regardless of the QUOTED_IDENTIFIER setting) or double quotes (if QUOTED_IDENTIFIER='ON' [default]):

Stored Procedures

Use these stored procedures to review and change column indexes and constraints:

Procedure Description

sp_iqcolumnmetadata Returns index metadata for all columns in one or more tables.

sp_iqindexmetadata Returns details about column indexes, including the index types (Flat FP, NBit, HG, and tiered HG), distinct counts, IQ UNIQUE <n> value, and NBit dictionary size.

sp_iqrebuildindex Rebuilds FP indexes (Flat FP as NBit, or NBit as Flat FP) and HG indexes (single HG as tiered HG, or tiered HG as single HG). Before you can insert or update new data, you must rebuild all columns greater than 255 bytes wide.

The index_clause can reset IQ UNIQUE <n> to an explicit value from 0 (to recast an NBit column to Flat FP) up to the limits defined in the FP_NBIT_AUTOSIZE_LIMIT and FP_NBIT_LOOKUP_MB options.

sp_iqrebuildindex also enables read-write access to columns that contain large object (LOB) data. LOB columns migrated from 15.x databases are read-only until you run sp_iqrebuildindex.

The estimated cardinality for NBit columns with an IQ UNIQUE value below or equal to the FP_NBIT_AUTOSIZE_LIMIT is stored as 0 regardless of the FP_NBIT_IQ15_COMPATIBILITY setting. This affects the value returned from sp_iqindexmetadata.

sp_iqindexrebuildwidedata Identifies wide columns that you must rebuild before they are available for read/write activities. sp_iqindexrebuildwidedata also generates a list of statements that you can use to rebuild the columns.

This applies to CHAR, VARCHAR, BINARY, and VARBINARY columns wider than > 255 characters, as well as all Long Varchar and Long Binary columns.


Re-create Indexes for EUC_TAIWAN Data

In SAP IQ 15 and later, the character encoding specification for the EUC–TAIWAN collation now uses the EUC_TW character set. You must re-create indexes on data in version 12.7 or earlier databases that use the EUC_TAIWAN collation to make them work with SAP IQ 16.

Update Configuration Files

Compare your existing params.cfg files with the new default.cfg file created by the installation. The installation does not update or overwrite existing params.cfg files. In each params.cfg file, update any parameter defaults that differ from those in the default.cfg file, while maintaining any customized parameter settings that are appropriate for your system. Add any new startup parameters in default.cfg to your params.cfg file. The -gl parameter, for example, is required for server startup in version 12.5 and later.

Preserve Database Options

SAP IQ preserves the settings of all 12.7 database options that are still valid in migrated databases. Check for deprecated features.

Back Up Your Databases

● Back up your databases again with the BACKUP statement. If you use the BACKUP statement instead of a system–level backup, you can run backups and queries concurrently.

● For a multiplex migration, back up only the coordinator only in this manner. For secondary servers, run the dbbackup utility from the secondary server directory.


● SAP IQ Administration: Database > Index SAP IQ Columns > Index Types Comparison > Fast Projection (FP) Index

● SAP IQ Administration: Database > Index SAP IQ Columns > Index Types Comparison > High_Group (HG) Index

● SAP IQ SQL Reference > SQL Statements > ALTER TABLE● SAP IQ SQL Reference > Database Options > Alphabetical List of Options > FP_NBIT_IQ15_

COMPATIBILITY_MODE● SAP IQ SQL Reference > Database Options > Alphabetical List of Options >

CREATE_HG_WITH_EXACT_DISTINCTS● SAP IQ SQL Reference > System Procedures > Alphabetical List of System Stored Procedures >

sp_iqindexmetadata



● SAP IQ SQL Reference > System Procedures > Alphabetical List of System Stored Procedures > sp_iqrebuildindex

14.6 Hardware Changes

Perform these steps to move your software to a new hardware platform.

In this section:

Moving 32-Bit Databases to 64-bit Platforms [page 227]Perform these steps to move a 32-bit database to a 64-bit platform.

Converting to a New Hardware Platform [page 228]Perform these steps to move a database to another platform with the same endian structure.

14.6.1 Moving 32-Bit Databases to 64-bit Platforms

Perform these steps to move a 32-bit database to a 64-bit platform.

Prerequisites

● Review backup and restore procedures in SAP IQ Administration: Backup, Restore, and Data Recovery. ● Make note of the 32-bit server raw device and IQ store path names. Raw device and IQ store path names on

the 64-bit target must match those on the 32-bit machine.

Procedure

1. Log in to your 32-bit server and backup the database.2. Copy the backup to the 64-bit machine, and restore the database.

You may need to rename raw device and path names to ensure that they match.3. On the 64-bit machine, do one of the following:

Server Action

Simplex Start the database with the appropriate startup flags.

Multiplex Start the coordinator with the -iqmpx_sn 1, -gm 1 , -iqro 1, and -iqmpx_ov 1 startup flags.

4. Start Interactive SQL and connect to the database.


5. Use DROP MULTIPLEX SERVER to drop all existing secondary nodes.

6. Use ALTER DATABASE UPGRADE to upgrade the database.

See ALTER DATABASE Statement in SAP IQ SQL Reference.7. Run sp_iqcheckdb ('allocation database') and verify that the database is error free.

sp_iqcheckdb checks the validity of the current database. See sp_iqcheckdb Procedure in SAP IQ SQL Reference.

8. Perform these steps for multiplex servers only:a. Shut down and restart the coordinator normally (without the -gm 1 , -iqro 1, and -iqmpx_ov

startup flags).b. Use CREATE MULTIPLEX SERVER STATEMENT to recreate the secondary nodes.

14.6.2 Converting to a New Hardware Platform

Perform these steps to move a database to another platform with the same endian structure.

Context

Platforms must share the same endian structure. Move your database, then migrate your data.

Procedure

1. Back up the database.2. Shut down the SAP IQ server.3. Install the server on the new platform. Your migration can take place on the same or a different machine.4. Start the server on the new hardware platform.5. Connect to the utility database, utility_db.

6. Restore the database from the backup you created in step 1.7. Shut down the server and restart it against the restored database.8. Start Interactive SQL and run ALTER DATABASE UPGRADE.

Results

NoteIf the SAP IQ version is more recent than the version on legacy platform, you must upgrade the database.



Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

SAP IQ Installation and Update Guide [IBM AIX]Important Disclaimers and Legal Information P U B L I C 229

www.sap.com/contactsap

© 2019 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

https://www.sap.com/about/legal/trademark.html

sap iq installation and update guide [ibm aix]

Documents