what's new in sap iq 16 · new features were introduced in sap® iq 16.0 sp 10. if you are...

PUBLIC

SAP IQ 16.0 SP 10Document Version: 1.2 – 2016-04-13

What's New in SAP IQ 16.0

Content

1 Releases Referenced in this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 Support Package 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.1 Shared-Nothing Multiplex (New). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.2 Point-in-Time Recovery (Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3 Performance Optimization (New and Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4 SQL Statements (Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.5 Database Options (New and Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.6 Tables and Views (Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.7 Stored Procedures (New and Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.8 Utilities (Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

iqunload Utility: Logical Backup Tool (Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22start_iq Utility: -iqhrt Database Server Option (New). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

2.9 Database Properties (New). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.10 SAP IQ Cockpit (New and Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.11 Indexes (Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3 Support Package 8 PL20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.1 Linux: Multiplex on NFS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263.2 SQL Statements (Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

4 Support Package 8 PL1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284.1 Point-in-Time Recovery (Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.2 SQL Statements (Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .354.3 Database Options (Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

5 Support Package 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375.1 PAM User Authentication (New). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385.2 Point-in-Time Recovery (New). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395.3 In-Memory Row-Level Versioning on Multiplex (New). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .455.4 SAP IQ Cockpit (New). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455.5 Authorizing Optional Features (New). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465.6 OData Support (New). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.7 Database Options (New and Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485.8 Database Properties (New and Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505.9 SQL Statements (Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505.10 Utilities (Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525.11 Stored Procedures (New and Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

2P U B L I C© 2016 SAP SE or an SAP affiliate company. All rights reserved.

What's New in SAP IQ 16.0Content

5.12 Tables and Views (Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535.13 Product Editions (Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535.14 default.cfg (Changed). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545.15 Documentation Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

6 Support Package 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

7 Support Package 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567.1 New Features in SP03. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

New JRE Environment Variables and Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567.2 Behavior Changes in SP03. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

FIPS Encryption Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Advanced Security Option Requirement for FIPS and RSA. . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

8 Support Package 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598.1 New Features in SP2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

Multiplex High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Cache Dbspace for Direct-Attached Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60LOAD TABLE Supports Loading from Compressed .gzip or .gz Files. . . . . . . . . . . . . . . . . . . . . . 61

8.2 Performance Improvements in SP2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61LIKE Condition Acceleration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

8.3 Behavior Changes in SP2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Database Option Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Encryption Support Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64SAP IQ Implicitly Rebuilds Wide Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66IS [NOT] DISTINCT FROM Search Condition Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Query Plan Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66SQL Statement Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Stored Procedure Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Table and View Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Deprecated Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

8.4 SAP Control Center Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

9 Support Package 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

10 Initial Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7410.1 Read This First: Helpful Hints Before You Start Using SAP IQ 16.0. . . . . . . . . . . . . . . . . . . . . . . . . . 7510.2 New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

SAP Control Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Concealment of Sensitive Information in Output Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . .81Connection Blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Global Transaction Resiliency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Login Redirection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85


P U B L I C© 2016 SAP SE or an SAP affiliate company. All rights reserved. 3

RLV Data Store for Write-Optimized Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Scale-Up and Scale-Out Performance Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Security Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Shared System Temporary Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Table Partitioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98System Secure Feature Keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

10.3 Performance Improvements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Cache Ejection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100DQP Performance Improvements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Micro Query Performance Improvement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

10.4 Discontinued Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101JDBC™ 3 Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102JDBC-Based Server Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102LOAD TABLE Statement: Discontinued Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Time Series Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Discontinued Database Server Startup Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Discontinued Indexes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Discontinued Login Policy Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Discontinued Time Series SQL Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Discontinued TLS and HTTPS Certificate and Certificate_Password Protocol Options. . . . . . . . 107Discontinued Tables and Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Discontinued Tools and Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107

10.5 Deprecated Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109Deprecated Database Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Deprecated Database Server Startup Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Deprecated Stored Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Deprecated System Tables and Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111Deprecated User Management Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Deprecated Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

10.6 Behavior Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Backward Compatibility: Changes to Default Behavior. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Backward Compatibility: Migration Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Connection Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118Database Option Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120JRE and Java Runtime Environment Variable Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126Logical Server Policy Option Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Login Policy Option Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128ODBC Driver Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Query Plan Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130SQL Function Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132SQL Statement Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133



Stored Procedure Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Table and View Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Utility Option Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

10.7 Administration Tool Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150SAP Control Center Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

10.8 Documentation Collection Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Documentation (deprecated). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155



1 Releases Referenced in this Document

Not every SAP IQ 16.0 Support Package (SP) and patch (PL) release is listed in this What's New document.

This document lists only those Support Packages and patches containing:

● New features● Changed features● Deleted features

If a Support Package or patch does not contain new/changed/deleted features, it does not have a section in this document.


What's New in SAP IQ 16.0Releases Referenced in this Document

2 Support Package 10

New features were introduced in SAP® IQ 16.0 SP 10. If you are updating from an earlier release or support package, you must run the ALTER DATABASE UPGRADE command.

In this section:

Shared-Nothing Multiplex (New) [page 8]Shared-nothing multiplex is a storage architecture for massively parallel processing (MPP) of big data, wherein primary data is stored on a set of direct-attached storage (DAS) devices spread across a set of servers, rather than on a shared storage area network (SAN).

Point-in-Time Recovery (Changed) [page 11]Backup and Recovery changes for SAP IQ 16.0 SP 10.

Performance Optimization (New and Changed) [page 12]Changes that improve database performance.

SQL Statements (Changed) [page 15]SQL statement syntax changes for SAP IQ 16.0 SP 10.

Database Options (New and Changed) [page 17]Database option syntax changes for SAP IQ 16.0 SP 10.

Tables and Views (Changed) [page 19]System view column changes for SAP IQ 16.0 SP 10.

Stored Procedures (New and Changed) [page 20]System stored procedure changes for SAP IQ 16.0 SP 10.

Utilities (Changed) [page 22]Changes to utility parameters for SAP IQ 16.0 SP 10.

Database Properties (New) [page 23]Database property changes for SAP IQ 16.0 SP 10.

SAP IQ Cockpit (New and Changed) [page 25]SAP IQ Cockpit changes for SAP IQ 16.0 SP 10.

Indexes (Changed) [page 25]The High_Non_Group (HNG) and Low_Fast (LF) indexes are now obsolescent, although support for these indexes will continue.

What's New in SAP IQ 16.0Support Package 10


2.1 Shared-Nothing Multiplex (New)

Shared-nothing multiplex is a storage architecture for massively parallel processing (MPP) of big data, wherein primary data is stored on a set of direct-attached storage (DAS) devices spread across a set of servers, rather than on a shared storage area network (SAN).

Note● Shared-nothing multiplex is not supported on Windows platforms in this release of SAP IQ.● Shared-nothing multiplex does not support point-in-time recovery in this release of SAP IQ.● Shared-nothing multiplex does not support row-level versioning (RLV) in this release of SAP IQ.

Shared-nothing multiplex is the latest in a series of scale-out features that began with SAP IQ 15.3. Shared-nothing multiplex provides I/O scale-out, where local direct-attached storage can achieve higher I/O performance than SAN.

SAP IQ maintains its flexible architecture; your implementation can combine shared-nothing dbspaces with traditional shared dbspaces. Moreover, your shared-nothing dbspace can contain shared file system (SFS) files. See Shared File System DAS Dbfiles [page 10].

Do not confuse DAS dbspaces with cache dbspaces. The DAS dbspace is a primary data store, whereas the cache dbspace caches persistent data from main dbspaces. The cache dbspace is a high-speed buffer pool extension dbspace composed of one or more DAS devices attached to a simplex or multiplex node. The cache dbspace caches copies of locally-used IQ main store read-only pages, reducing access requests to the IQ main store devices. The cache dbspace, however, is compatible with shared-nothing storage, and can improve data access performance for any data violating affinity. DAS dbfile data with affinity is never written to the cache dbspace file.

Like other multiplexes, you need to set up Transport Layer Security (TLS). In a shared-nothing multiplex you configure TLS for DAS internode communications, as well as for INC and MIPC connections.



How to Create a Shared-Nothing Multiplex

Before you can load and query data in your shared-nothing multiplex, follow these steps to create shared-nothing storage.

1. Review sizing and technical prerequisites.2. Create a multiplex with DQP.3. Create a shared-nothing logical server.4. Enable distributed query processing (DQP) in the logical server policy.5. Add all shared-nothing logical servers to the login policy.6. Create a DAS dbspace and DAS dbfiles.

You are now ready to load data to your shared-nothing multiplex, and run queries against it.

For details, see Shared-Nothing Multiplex in Administration: Multiplex.

DAS Dbspaces

A DAS dbspace is an IQ main store dbspace for shared-nothing storage of primary data, where the data is stored on a set of DAS devices. A DAS dbspace is associated with one logical server, and contains a set of DAS dbfiles, and their mirror files, within the logical server.

You can create multiple DAS dbspaces for the logical server. Each DAS dbspace, however, must be associated with one logical server. The members of the logical server must be excluded from other DAS dbspace logical servers. The size and speed of DAS devices in the DAS dbspace should be nearly identical across all physical servers to ensure even data distribution, and consistent performance.



DAS Dbfiles

A DAS dbfile is an IQ main store dbfile physically located on a DAS device attached to one server. It can be a raw partition, or operating system file. A DAS dbfile is always contained within a DAS dbspace and is always associated with one logical server. DAS dbfile mirroring (optional but recommended) ensures high availability in a shared-nothing environment by creating one or more redundant copies of a DAS dbfile on other physical servers in the logical server. When mirroring exists, the original file is known as the primary DAS dbfile; the redundant copy is known as the mirror DAS dbfile.

Each writer node in the logical server requires a primary DAS dbfile. A writer node without a primary DAS dbfile causes an OUT OF SPACE error.

Shared File System DAS Dbfiles

You can combine shared file system (SFS) DAS dbfiles, and non-SFS DAS dbfiles, in the same DAS dbspace. Non-SFS DAS dbfiles reside only on their respective local nodes, and cannot be moved to other nodes in the DAS dbspace. SFS DAS dbfiles, on the other hand, can be reassigned to other nodes in the DAS dbspace. Both SFS DAS dbfiles and non-SFS DAS dbfiles use the same type of "hard" affinity mapping, where you use the SERVER keyword to specify the physical server associated with a DAS dbfile. You can combine SFS and non-SFS DAS dbfiles in your shared-nothing multiplex, which gives you design flexibility.

NoteIn SAP IQ 16.0 SP 10, SFS is supported for primary DAS dbfiles only. A primary DAS dbfile is a dbfile that is not a mirror copy.

You specify that a primary DAS dbfile is an SFS file using the new SHARED PATH keywords of the CREATE DBSPACE and ALTER DBSPACE commands.

You can reassign all SFS DAS dbfiles from one server to another using the new sp_iqreassignsharedfiles stored procedure.

Documentation

See these topics in the SAP IQ 16.0 SP 10 documentation:

Area Manual Topic

Information on setting up and using shared-nothing logical servers, DAS dbspaces, and DAS dbfiles.

Administration: Multiplex Shared-Nothing Multiplex

DAS dbspace backup and restore. Administration: Backup, Restore, and Data Recovery

Shared-Nothing Multiplex Backup and Recovery



Area Manual Topic

Setting TLS for DAS internode communication.

Administration: Multiplex DAS Internode Communication

SQL statements enhanced with shared-nothing multiplex support.

Reference: Statements and Options ALTER DBSPACE Statement

CREATE DBSPACE Statement

Stored procedures enhanced with shared-nothing multiplex support.

Reference: Building Blocks, Tables, and Procedures

sp_iqcheckdb Procedure

sp_iqdbspace Procedure

sp_iqemptyfile Procedure

sp_iqfile Procedure

sp_iqrebalance Procedure

sp_iqstatus Procedure

System views enhanced with shared-nothing multiplex support.

Reference: Building Blocks, Tables, and Procedures

SYSIQDBSPACE System View

SYSIQDBFILE System View

SYSIQTAB System View

2.2 Point-in-Time Recovery (Changed)

Backup and Recovery changes for SAP IQ 16.0 SP 10.

NotePoint-in-Time Recovery is not supported on multiplex in this release of SAP IQ.

Point-in-Time Recovery Point-in-time recovery logs and log backups are version specific. SP 10 point-in-time recovery logs and log backups require an SP 10 engine. To perform an SP 8 point-in-time recovery with SP 8 logs, use an SP 8 engine. Use an SP 8.1 engine to perform point-in-time recovery with SP 8 or SP 8.1 logs.

Re-enabling point-in-time recovery after a database restore is no longer required. Point-in-time recovery resumes logging operations after recovery operations are complete.

Re-enabling point-in-time recovery is required after an upgrade from SP 8 to SP 10.



Alternate Database Timelines A point-in-time recovery to a time earlier than the end-point of the point-in-time recovery logs creates an alternate database timeline. Subsequent point-in-time recovery operations may be done on any existing timeline.

To support alternate timelines, point-in-time recovery log backups include globally unique identifiers (GUID) that establish the current timeline, the previous timeline, log sequence. The previous timeline GUID includes an OFFSET reference to the position in the previous timeline from which the current timeline branched.

All point-in-time recovery operations that restore to an alternate timeline require an ON TIMELINE clause and timeline GUID that identifies the alternate timeline. Point-in-time recovery operations without this clause restore to the current timeline.

Incremental RLV Dbspace Backups Point-in-time recovery on RLV-enabled databases no longer requires you to backup and manually restore all RLV dbspace files before RESTORE DATABASE RECOVER UNTIL operations. Automatic point-in-time recovery backups incrementally backup the RLV dbspace in a way that each subsequent log backup only copies those blocks which have not been previously backed up.

2.3 Performance Optimization (New and Changed)

Changes that improve database performance.

Improving Equality Condition Performance

SAP IQ leverages information available in a hash-partitioned or a hash-range-partitioned table to improve the performance of some equality conditions on the hash-partitioning basis column.

The optimization is applied when all of the following are true:

1. The SQL statement contains a condition of the form:

<column> = constant-expression

The expression cannot apply to <>, <, <=, >, >=, IN, NOT IN, or BETWEEN conditions.2. That <column> is a base column in a real table, not from a view or a derived table.3. The base column is the sole basis for the hash partitioning of the table containing that <column>.4. That constant-expression is either a literal constant, a host variable, or a simple scalar expression

containing only constants and host variables, not a scalar subquery or an aggregate expression.5. The equality condition is in the SQL statement at a location which allows it to be applied at the leaf node in

the query plan, not in some other query block, and not in a ON clause of FULL OUTER JOIN in the same query block.

6. The datatype of the constant-expression is highly compatible with the datatype of the base column.



7. There is no HG or LF index on that base column. When all these conditions are true, then the optimizer will infer an additional condition of the form:

HashPartitionNumber( <column> ) = integer-constant

where that integer-constant is the hash partition number for the constant-expression in the original condition. This condition will appear in the query plan like any other inferred condition.

By executing this inferred condition before the original equality condition, that original equality condition only needs to scan the FP cell values for rows contained within that one hash partition.

Additional Information

Performance and Tuning > Schema Design > Hash Partitioning

LOAD TABLE IGNORE CONSTRAINT Behavior Change

In SAP IQ 16.0, a redesign in memory usage reduced memory footprint and provided better parallel processing for loads. As a result, the row log file for LOAD TABLE IGNORE CONSTRAINT now returns NULL strings instead of the original file contents for certain values when data conversion errors occur.

For example, assume the following SQL statement:

LOAD TABLE dbo.IQ_TEST ( amount ASCII(10) null(ZEROS), FILLER ('\n')) FROM 'c:\data\test.data'quotes offescapes offformat 'ascii'strip offwith checkpoint offignore constraint DATA VALUE 50message Log 'c:\log\test.log' row log 'c:\log\test.row' only log ALL

The test.data file contains these values:

100.4 ABCED 265.3456 23.4 . 234 345

SAP IQ 15.4 returns these rows:

2 ,ABCED , 5 , . ,



SAP IQ 16.0 returns these rows:

1 ,NULL, 2 ,NULL,

Cases such as column check constraints continue to generate the correct rows.

UNION ALL Parallelism

SAP IQ now fully parallelizes and distributes UNION ALL operators on a cost basis, along with other data flow operators, regardless of the number of unions, union arms, or operator types. You will see significant performance increases over previous releases, on the same hardware, without tuning or schema changes. This improvement particularly benefits DAS configurations. Unions are even partially parallelized if some arms do not allow parallelism or are not worth parallelizing on a cost basis.

Examples of common UNION ALL operations:

● Queries combine similar data from multiple locations, often a small work table and a larger historical table. Queries typically select data from all tables.

● Identical tables store a similar size period of data. Queries typically select data from specific periods.

Direct I/O Support

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



2.4 SQL Statements (Changed)

SQL statement syntax changes for SAP IQ 16.0 SP 10.

Statement Description

ALTER DBSPACE New ALTER DBSPACE keywords to support DAS dbspaces and DAS dbfiles for shared-nothing multiplex:

● MIRROR [PATH]: New keyword for creating mirror copy when creating a primary DAS dbfile.

● SERVER: New keyword for specifying the physical server associated with a DAS dbfile.

● ADD EXISTING PATH: New keyword for adding a mirror copy of an existing DAS dbfile.Example:

ALTER DBSPACE das1 ADD EXISTING PATH '/dev/das/3' SERVER mpx_2 MIRROR dasM2 PATH '/dev/das/4' SERVER mpx_1;

● ENFORCE WRITE SAFE ON | OFF: New keyword to enable or disable enforced DAS dbfile mirroring for high availability.

ALTER DBSPACE das1 ENFORCE WRITE SAFE ON;

● PRIMARY: New keyword specifying that the current mirror DAS dbfile will become the primary DAS dbfile.Example:

ALTER DBSPACE das1 ALTER FILE dasM2 PRIMARY;

● SHARED PATH: New keyword to create a primary DAS dbfile in a shared file system.Example:

ALTER DBSPACE sfs_dbs ADD FILE f3 SHARED PATH '/shared_disk/f3.iq' SERVER writer1

● REASSIGN TO SERVER: New ALTER FILE clause keyword to change the owning server of a shared file system primary DAS dbfile.Example:

ALTER DBSPACE sfs_dbs ALTER FILE f3 REASSIGN TO SERVER writer2

● ONLINE|OFFLINE: New ALTER FILE clause keywords to take a DAS dbfile offline, or back online.Example:

ALTER DBSPACE sfs_dbs ALTER FILE f3 OFFLINE

See ALTER DBSPACE Statement in Reference: Statements and Options for detailed syntax and usage information. See Shared Nothing Multiplex in Administration: Multiplex for information on DAS dbspaces and DAS dbfiles.




CREATE DBSPACE

New keywords to support DAS dbspace and DAS dbfile for shared-nothing multiplex:

● PATH: New keyword following the FILE clause. Specifies the path to the direct-attached storage device; either for the primary DAS dbfile, or a mirror DAS dbfile.

● SHARED PATH: New keyword following the FILE clause. Specifies the path to a shared file system primary DAS dbfile.

● SERVER: New keyword. Specifies the physical server name.

● MIRROR: New keyword. Creates a mirror copy of a primary DAS dbfile, stored on another server node within the logical server for redundancy.

● ON LOGICAL SERVER [ENFORCE WRITE SAFE]: New keyword. Specifies that the dbspace you are creating is a DAS dbspace. The optional ENFORCE WRITE SAFE clause specifies enforced DAS dbfile mirroring.

Example:

CREATE DBSPACE USING FILE src_1 PATH '/dev/cr01t1s1/' SERVER mpx1 MIRROR mirror_1 PATH '/dev/cr02t1s2' SERVER mpx2 ON LOGICAL SERVER ENFORCE WRITE SAFE;

See CREATE DBSPACE Statement in Reference: Statements and Options for detailed syntax and usage information. See Shared Nothing Multiplex in Administration: Multiplex for information on DAS dbspaces and DAS dbfiles.

NoteSAP IQ now supports IQ_SYSTEM_MAIN plus one user dbspace and one DAS dbspace in the base product license. You must be licensed for the IQ_VLDBMGMT option in order to create additional dbspaces.

.

LOAD TABLE New optional clauses to enhance functionality of the statement:

● QUOTES: allows user-defined enclosure character around string values.

● QUOTE: controls whether input strings are enclosed in quotation characters.

● QUOTE ESCAPE: allows user-defined escape character.

RESTORE DATABASE

New optional MULTIPLEX keyword for shared-nothing multiplex. Instructs all secondary nodes with primary DAS dbfiles to search for <archive_device.<server-id> .

New ON TIMELINE clause is required to restore the database to an alternate timeline in point-in-time recovery operations:

ON TIMELINE ' <GUID> '

The ON TIMELINE clause requires a timeline GUID that identifies the alternate timeline. Point-in-time recovery operations without this clause restore to the current timeline.




New CLEAR LOGS clause ignores the current database log area and cancels the automatic log backups that normally occur during a point-in-time recovery operation:

CLEAR LOGS

If RESTORE DATABASE cannot locate the transaction log, RLV log, and point-in-time recovery logs during a point-in-time recovery, the recovery operation fails. This can happen in cases when the database is restored to a new location and there are no logs available in the new environment. In cases like this, use the CLEAR LOGS clause to ignore the current log area of the database you want to restore and cancel the automatic log backups that normally occur during a recovery operation.

Point-in-time recovery operations generally restore the dbfiles to a different location than the current dbspace. The new OVERWRITE EXISTING clause restores a database from backup to a location that already has a database and overwrites any existing dbfiles with the same name:

OVERWRITE EXISTING

The OVERWRITE EXISTING clause can appear as a restore option at any position in a RESTORE DATABASE statement.

2.5 Database Options (New and Changed)

Database option syntax changes for SAP IQ 16.0 SP 10.

Option Description

AES_ENCRYPT_HEADER_FORMAT (New) Decrypts encrypted data upgraded or imported from databases prior to SAP IQ 15.4:

SET OPTION public.AES_ENCRYPT_HEADER_FORMAT = <VAL>

<VAL> is an integer that identifies the source release. <VAL> defaults to -1, which decrypts data encrypted in the same format as the current release.

Do not use this option without specific instructions from an SAP IQ product support engineer. Incorrect usage can result in decryption errors when SAP IQ attempts to read the data.

See AES_ENCRYPT_HEADER_FORMAT in Reference: Statements and Options.

DAS_TCP_TIMEOUT (New) Considered by the system when determining the remote procedure call (RPC) timeout value for individual TCP RPCs used in shared-nothing multiplex internal communications.

See DAS_TCP_TIMEOUT in Reference: Statements and Options.



Option Description

MIN_NUMERIC_DIVISION_SCALE

(New) Controls the number of decimal places displayed for division operations on constant numeric values.

See MIN_NUMERIC_DIVISION_SCALE in Reference: Statements and Options.

RV_MAX_LOOKUP_MB (New) Limits the total in-memory dictionary size for implicit NBit FP columns.

See RV_MAX_LOOKUP_MB Option in Reference: Statements and Options.

RV_MAX_TOKEN (New) Provides an upper bound for the number of NBit tokens used in the in-memory dictionary.

See RV_MAX_TOKEN Option in Reference: Statements and Options.

MAX_RV_REMOTE_TRANSFER_MB (Changed) Limits the volume of RLV-enabled table data allowed to be transferred from the RLV store when a statement is executed on another node. The default value has changed from 200 to 1000. New databases created with SAP IQ 16.0 SP08 PL01 or later use the new default. Databases created prior to 16.0 SP08 PL01 use the original default, even after upgrading.

MPX_GTR_ENABLED (New) Enables global transaction resiliency functionality on the coordinator. Global transaction resiliency allows DML read-write transactions on writers to survive temporary communication failures between coordinator and writer and temporary failure of coordinator due to server failure, shutdown, or failover.

See MPX_GTR_ENABLED Option in Reference: Statements and Options.

MPX_MIPC_TIMEOUT (Changed) The default has changed to 180 seconds.

See MPX_MIPC_TIMEOUT in Reference: Statements and Options.

MPX_WORK_UNIT_TIMEOUT (Changed) The default has changed to 600 seconds.

See MPX_WORK_UNIT_TIMEOUT in Reference: Statements and Options.

RV_MERGE_TABLE_COMMIT_AGE (New behavior) RV_MERGE_TABLE_COMMIT_AGE lets you configuration an RLV merge to occur based on a time interval since the last commit.

See CONVERSION_MODE Option in Administration: In-Memory Row-Level Versioning or Reference: Statements and Options.

RV_MERGE_TABLE_DELPERCENT (New) Defines the threshold of deleted and committed table rows to trigger a merge expressed as a percentage.

See RV_MERGE_TABLE_DELPERCENT Option in Reference: Statements and Options.

RV_BLOCK_SIZE_ALLOCATION_STRATEGY

(New) Defines the strategy to use for subsequent array allocation for fixed length datatype columns in the RLV in-memory store.

See Adaptive Fixed Block Allocators in Administration: In-Memory Row-Level Versioning.



Option Description

RV_DELTA_INCREASE_IN_FIX_DATA_BLOCKSIZE

(New) Defines the delta size increase size (in Bytes) for subsequent array allocation for fixed length datatype columns in the RLV in-memory store.


RV_FIX_DATA_BLOCKSIZE (New) Defines the size (in Bytes) of every subsequent array allocation for fixed length datatype columns in the RLV in-memory store.


RV_INITIAL_FIX_DATA_BLOCKSIZE

(New) Defines the size (in Bytes) of the first array allocation for fixed length datatype columns in the RLV in-memory store.


RV_VAR_DATA_BLOCKSIZE (New) Defines the size (in Bytes) of every array allocation for variable length datatype columns in the RLV in-memory store.

See RV_VAR_DATA_BLOCKSIZE Option in Reference: Statements and Options.

TRUSTED_CERTIFICATES_FILE (Changed) Now also specifies the trust relationship for outbound Transport Layer Security (TLS) connections made by DAS internode connections in a shared-nothing multiplex.

See TRUSTED_CERTIFICATES_FILE Option in Reference: Statements and Options.

2.6 Tables and Views (Changed)

System view column changes for SAP IQ 16.0 SP 10.

System Table Description of Change

ISYSIQDBSPACE New columns to support shared-nothing multiplex:

enforce_write_safe 'T' – DAS dbfile mirroring is enforced for the DAS dbspace; 'F' – DAS dbfile mirroring is not enforced for the DAS dbspace.ls_id The logical server associated with the DAS dbspace.

See SYSIQDBSPACE System View in Reference: Building Blocks, Tables, and Procedures.




ISYSIQDBFILE New columns to support shared-nothing multiplex:

server_id Multiplex server name.mirror_of_dbfile_id The ID of the primary DAS dbfile mirrored by this DAS dbfile.

See SYSIQDBFILE System View in Reference: Building Blocks, Tables, and Procedures.

ISYSIQTAB New columns to support shared-nothing multiplex:

affinity_map Table affinity map ID.

affinity_map_size Size of the table affinity map.

See SYSIQTAB System View in Reference: Building Blocks, Tables, and Procedures.

2.7 Stored Procedures (New and Changed)

System stored procedure changes for SAP IQ 16.0 SP 10.

Procedure Description

sp_iqcalcbaserlvstore (New) Gives approximate in-memory usage of a specified RLV-enabled table.

See sp_iqcalcbaserlvstore Procedure in Reference: Building Blocks, Tables, and Procedures and Understand RLV Memory Initial Requirements and Usage in Administration: In-Memory Row-Level Versioning.

sp_iqbackupsummary Added "PITR" to backup_type column.

See sp_iqbackupsummary Procedure in Reference: Building Blocks, Tables, and Procedures.

sp_iqdbspace Introduced two BlkTypes identifiers related to RLV store memory:

RC Number of blocks actually in use by RLV store memory.

RU Number of blocks used by the commit log.

These identifiers assist in calculating available RLV store memory in an RLV dbspaces.




sp_iqemptyfile When emptying a primary DAS dbfile, copy the primary DAS dbfile to a new storage device, and then use sp_iqemptyfile to mark the original storage as empty.

See sp_iqemptyfile Procedure in Reference: Building Blocks, Tables, and Procedures.

sp_iqfile New columns to support shared-nothing multiplex:

servername The server that created the DAS dbfile.MirrorLogicalFileName Logical filename of the primary DAS dbfile.IsDASSharedFile "T" indicates that the primary DAS dbfile is from a shared file system (SFS); otherwise "F".

See sp_iqfile Procedure in Reference: Building Blocks, Tables, and Procedures.

sp_iqmergerlvstable (New) Triggers a merge on a group of row-level version (RLV) enabled tables in the IQ main store.

See sp_iqmergerlvstable in Reference: Building Blocks, Tables, and Procedures.

sp_iqreassignsharedfiles New procedure. Applies to DAS dbspaces only.

Reassigns shared file system primary DAS dbfiles from a source server to a target server.

Adds the target server to the shared-nothing logical server, if the target server is not already a member.

See sp_iqreassignsharedfiles in Reference: Building Blocks, Tables, and Procedures.

sp_iqrebalance New procedure. Applies to DAS dbspaces only.

Redistributes and rebalances data across all active servers in a DAS dbspace's logical server.

See sp_iqrebalance Procedure in Reference: Building Blocks, Tables, and Procedures.

sp_iqrlvmemory Added two columns to output to report RLV store memory usage per table fragment and per transaction.

sp_iqstatus If a DAS dbspace exists, the first column of the main dbspace information reflects DAS dbspace.

See sp_iqstatus Procedure in Reference: Building Blocks, Tables, and Procedures.



2.8 Utilities (Changed)

Changes to utility parameters for SAP IQ 16.0 SP 10.

Utility Description

db_backupheader (Changed) Extended backup data record includes globally unique identifiers that identify the current timeline, previous timeline, current log sequence, and previous log sequence.

The previous timeline GUID includes an OFFSET reference to the position within the previous timeline from which the current timeline branched. All GUIDs carry a timestamp created at the time the point-in-time recovery operation begins.

In this section:

iqunload Utility: Logical Backup Tool (Changed) [page 22]The iqunload utility has new functionality if run against an SAP IQ 15.4 or higher database.

start_iq Utility: -iqhrt Database Server Option (New) [page 22]Use the -iqhrt switch of the start_iq utility to enable high-resolution timing (to the millisecond) in the IQ message log.

2.8.1 iqunload Utility: Logical Backup Tool (Changed)

The iqunload utility has new functionality if run against an SAP IQ 15.4 or higher database.

When run against a SAP IQ 12.7 database, iqunload migrates the database, re-creating the legacy catalog on the new database catalog in the current installation. When run against a SAP IQ 15.4 or later database, iqunload unloads the database schema and optionally its data into a SQL script file. You can then load the schema file into another SAP IQ database of the same version.

When run against 15.4 or higher database, you can export part or all of the database schema, and optionally data, into an SQL script.

See the Utility Guide.

2.8.2 start_iq Utility: -iqhrt Database Server Option (New)

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

See start_iq Database Server Startup Utility > start_iq Server Options > -iqhrt database server option in the Utility Guide.



2.9 Database Properties (New)

Database property changes for SAP IQ 16.0 SP 10.

Alternate Timelines

New database properties that support point-in-time recovery to alternate timelines.

Property Name Description

CurrentRedoPos Current log redo position:

select db_property('CurrentRedoPos')

Returns a numeric OFFSET value. Results are similar to: '1573909'.

CurrentTimelineID Globally unique identifier for the current database timeline:

select db_property('CurrentTimelineID')

Returns a 36 character string. Results are similar to: '670e7768-34ae-11e4-8000-a6da5f46c1e9'.

CurrentTimelineUTCCreationTime UTC timestamp which identifies when the current database timeline was created:

select db_property('CurrentTimelineUTCCreationTime')

Returns a UTC timestamp. Results are similar to: '2014-09-05 11:40:38.591+00:00 '.

CurrentTransactionLogID Globally unique identifier for the current transaction log:

select db_property('CurrentTransactionLogID')

Returns a 36 character string. Results are similar to: '6a0c9c38-34ae-11e4-8000-a6da5f46c1e9 '.

IQPointInTimeRecoveryLogFilename Current point-in-time recovery log name and location:

select db_property('IQPointInTimeRecoveryLogFilename')

Returns the path to the point-in-time recovery log. Results are similar to: '/IQ-16_0/demo/pitrLog/PITR__000_000001_0001.iqlog'.

IQPointInTimeRecoveryLogStatus Current status of point-in-time recovery log:

select db_property('IQPointInTimeRecoveryLogStatus')

Returns a boolean ON or OFF value.



Property Name Description

LastCheckpointTime Last checkpoint time:

select db_property('LastCheckpointTime')

Returns a UTC timestamp. Results are similar to: '2014-09-09 11:28:04.219 '.

LastCommitRedoPos Redo position at end of last commit:

select db_property('LastCommitRedoPos')


LastSyncedRedoPos Last log redo position written and synchronized to disk:

select db_property('LastSyncedRedoPos')


LastWrittenRedoPos Last redo position written to disk:

select db_property('LastWrittenRedoPos')


PreviousTimelineID Globally unique identifier for the previous database timeline:

select db_property('PreviousTimelineID')

Returns a 36 character string. Results are similar to: '98b69a5c-2c0c-11e4-8000-853d9a9151da '.

PreviousTimelineUTCCreationTime UTC timestamp that identifies when the previous database timeline was created:

select db_property('PreviousTimelineUTCCreationTime')

Returns a 36 character string. Results are similar to: '2014-08-25 12:02:14.128566+00:00'.

PreviousTransactionLogID Globally unique identifier for the previous transaction log:

select db_property('PreviousTransactionLogID')

Returns a 36 character string. Results are similar to: '9bf0b6bc-2c0c-11e4-8000-853d9a9151da'.

TimelineBranchOffset Transaction log offset in the previous database timeline from which the current timeline was branched:

select db_property('TimelineBranchOffset')




2.10 SAP IQ Cockpit (New and Changed)

SAP IQ Cockpit changes for SAP IQ 16.0 SP 10.

Database Creation

SAP IQ Cockpit now allows allows you to create a new database, but only after first logging on to the SAP IQ Cockpit.

For new SAP IQ Cockpit installations, where no database exists, use the SAP IQ utility server to log on to SAP IQ Cockpit and create the first database.

Platform Support

SAP IQ Cockpit is now supported on all platforms supported by SAP IQ.

2.11 Indexes (Changed)

The High_Non_Group (HNG) and Low_Fast (LF) indexes are now obsolescent, although support for these indexes will continue.

We encourage you to move your HNG and LF indexes to High_Group (HG) indexes. HG indexes offer better performance than HNG and LF indexes. See SAP Note 2162805 .



http://help.sap.com/disclaimer?site=https://service.sap.com/sap/support/notes/2162805

3 Support Package 8 PL20

New features were introduced in SAP IQ 16.0 SP 8 patch-level release 20 (PL20). If you are updating from an earlier release or support package, you must run the ALTER DATABASE UPGRADE command.

In this section:

Linux: Multiplex on NFS [page 26]In previous releases, data files on Linux systems were not supported on Network File System (NFS) shared-disk storage

SQL Statements (Changed) [page 27]Syntax changes for SAP IQ 16.0 SP 8 PL20.

3.1 Linux: Multiplex on NFS

In previous releases, data files on Linux systems were not supported on Network File System (NFS) shared-disk storage

On Linux x86-64 and x64 (Red Hat Enterprise Linux and SuSE Linux Enterprise Server), SAP IQ now uses O_DIRECT to open files. O_DIRECT enables SAP IQ 16.0 SP 8 PL20 for Linux to support multiplex on filesystem files, including NFS.

NFS v3 and higher is supported.


What's New in SAP IQ 16.0Support Package 8 PL20


Syntax changes for SAP IQ 16.0 SP 8 PL20.


CREATE EXISTING TABLE Proxy tables can now be declared with LOCAL TEMPORARY semantics. Performance of proxy tables is significantly improved in some cases.

New Syntax:

CREATE EXISTING LOCAL TEMPORARY TABLE <IQtab(col, specs> at '<HANAInstance>.<schema>..<hanatab>'

If LOCAL TEMPORARY is specified, the new remote table will be private to the connection and will be destroyed automatically, just like a local temporary table.

See CREATE EXISTING TABLE Statement in Reference: Statements and Options for syntax and usage details.



4 Support Package 8 PL1

New features were introduced in SAP IQ 16.0 SP 8 patch-level release 01 (PL1). If you are updating from an earlier release or support package, you must run the ALTER DATABASE UPGRADE command.

In this section:

Point-in-Time Recovery (Changed) [page 28]Point-in-time recovery restores all committed database operations prior to a specified point in time. A point in time can be expressed as a timestamp and timezone, or as a transaction log offset.

SQL Statements (Changed) [page 35]Syntax changes for SAP IQ 16.0 SP 8 PL1.

Database Options (Changed) [page 36]Database option changes for SAP IQ 16.0 SP 8 PL1.

4.1 Point-in-Time Recovery (Changed)

Point-in-time recovery restores all committed database operations prior to a specified point in time. A point in time can be expressed as a timestamp and timezone, or as a transaction log offset.


Point-in-time recovery extends, but does not replace standard backup and recovery operations. Point-in-time recovery always begins by restoring a database from a data backup, then replays all committed activity from the recovery logs that cover the entire time period between the backup and the specified point in time. Transactions that were in progress, but not committed are rolled back.

Redirecting Log Output

By default, SAP IQ saves the point-in-time recovery log in the same directory as the .db file. To save the log in another directory, use:

ALTER DBSPACE IQ_SYSTEM_LOG RENAME ' new-directory-specification/file-prefix '

The new-directory-specification must point to an existing directory. If point-in-time recovery logging is active, using this command with a new-directory-specification, opens a new log at the new location.



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.

Point-in-time recovery (PITR) log backups can be can be performed manually, or automatically at set intervals.

Log Size

The IQ_LOG_MAX_SIZE option limits the size of the log:

SET OPTION PUBLIC.IQ_LOG_MAX_SIZE = ' <megabytes> '

The default setting of 0 allows the log size to increase without limit. If you limit the log size, and the file exceeds the limit, the server closes the current log, and creates a new log in the same directory. Subsequent backups are written to the new log.

Log Names

All recovery logs include a .iqlog extension. Token position within the file name provide statistics about the log:

<prefix> A <prefix> is optional. If the ALTER DBSPACE new-directory-specification includes a terminating string without a slash or backslash, the terminating string is prefixed to the log name.

_000 The first 3 digits in the log name is the server ID. SAP IQ always assigns _000 as the server ID to simplex servers.

_000000 The 6 digits that follow the server identifier, is the log sequence number.

If IQ_POINT_IN_TIME_RECOVERY_LOGGING is ON, each log backup or ALTER DBSPACE IQ_SYSTEM_LOG RENAME closes the current log and opens a new one. Each new log increments the log sequence number.



_0000 The 4 digits that follow the log sequence number is the log sub-sequence number.

A new log that opens after a backup or ALTER DBSPACE IQ_SYSTEM_LOG RENAME starts with a sub-sequence equal to 1. If the archive size exceeds the value set by IQ_LOG_MAX_SIZE, the server closes the current log and opens a new one. The sub-sequence number is incremented to reflect the change.

Automatic Backups

To backup the logs required by point-in-time recovery at set time intervals, use:

SET OPTION PUBLIC.IQ_POINT_IN_TIME_RECOVERY_LOG_BACKUP_INTERVAL= ' <minutes> ' Time intervals are expressed in minutes. The IQ_SYSTEM_LOG_BACKUP_INTERVAL option backs up the transaction log and RLV log. The point-in-time recovery logs (.iqlog) are not included in the backup because of size considerations. The IQ_SYSTEM_LOG_BACKUP_INTERVAL option must be explicitly set. The minimum supported backup interval is 5 minutes. Default behavior requires manual backups of the activity logs.

Manual Backups

A manual backup archives the point-in-time recovery logs:

BACKUP DATABASE ... POINT IN TIME RECOVERY LOGS ONLY TO ' target-directory / archive-file-name '

SAP IQ closes the current log and starts a new one. Copies of the previous logs are left behind as backups. The archive is written to the to the target-directory.

POINT IN TIME RECOVERY LOGS ONLY supports only one TO clause, which points to a location on the file system. Name of the archive is user-determine. No other options are allowed. The POINT IN TIME RECOVERY LOGS ONLY clause can only be used to backup activity logs for point-in-time recovery. Do not use this clause as part of a data backup.

RESTORE and Recovery

Always begin a point-in-time recovery by restoring a database from a full data backup, then apply all incremental backups prior to the point in time you want to recover. Use the RESTORE DATABASE point-in-time recovery syntax extensions as a final step to replay all committed activity from the recovery logs that cover the entire time period between the backup and the period just prior point in time you specify:

RESTORE DATABASE '< db_file >



saves the point-in-time recovery log in the same directory as thePerform a data' [ FROM '< file-name >' <...> [ USING LOG PATH ' directory, [...]] RECOVER UNTIL [ TIMESTAMP <timestamptz> | OFFEST <log-offset> ] KEY <key_spec> [ VERIFY COMPATIBILE ]

Always specify a timestamp that is greater than the backup time of the data backup specified in the FROM clause of the restore command. This ensures that the database includes all committed transactions in the recovery logs. If the specified point in time is earlier than the last checkpoint in the backup database, the server returns an error.

Restriction● A dbspace that you create after enabling point-in-time recovery may only be recorded in the point-in-

time recovery log. If this is the case, you cannot rename the dbspace during a RESTORE DATABASE RECOVER UNTIL operation.

● For RLV-enabled databases, attempting point-in-time recovery to a point beyond the last log backup causes the RESTORE DATABASE RECOVER UNTIL operation to fail. Always restore the RLV dbspace files of the old database in the right location manually before you run the point-in-time recovery, so that the correct version of the RLV log is used and the data recovered is correct.Manually restore all RLV dbspace files before you perform a RESTORE DATABASE RECOVER UNTIL operation from an INCREMENTAL backup.

● Point-in-time recovery log backups that fail before the backup is complete return incomplete results and generate a Files are missing for point-in-time recovery exception. Accurate point-in-time recovery is only possible with complete log backups. If the backup fails, SAP IQ creates a transaction log backup called <timestamp>.log in the IQ_SYSTEM_LOG directory. Remove this file and manually backup the point-in-time recovery log.

Performing Point-in-Time Recovery

1. Shutdown the database server.2. Start a server that you can use to connect to the utility database:

start_iq -su mypwd -gd DBA -gm 1 -n my_server

3. Start dbisql and connect to the utility database:

dbisql -c "UID=DBA;PWD=mypwd;DBN=utility_db"

4. Perform a full database restore prior to the point in time you want to recover.Run all RESTORE DATABASE commands from dbisql. Repeat this step, for every incremental backup you want to restore. All incremental backups must be prior to the point in time you want to recover.

5. Run RESTORE DATABASE with the appropriate point-in-time syntax extensions to recover from the recovery logs and PITR archives. See the Recovery Scenarios for syntax examples.

6. Shutdown the server and utility database.7. Start the database server normally.



Recovery Scenarios

Examples use UNIX path conventions; Windows path names are similar.

Point in time recovery using point in time recovery logs only:

// enable Point in time recovery SET OPTION PUBLIC.IQ_POINT_IN_TIME_RECOVERY_LOGGING = 'ON'ALTER DBSPACE IQ_SYSTEM_LOG RENAME '/demo/pitrLog/PITRLOG'BACKUP DATABASE FULL to '/demo/dataBackup/FULL1'// perform some DDL/DML operations CREATE TABLE T1 ( ID INT )INSERT INTO T1 VALUES (1)// record timestamp TS1 / OFFSET OFS1TS1 : select getdate()OFS1 : select db_property('LastCommitRedoPos')// perform DDL/ DML operationsCREATE TABLE T2 ( ID INT )INSERT INTO T2 VALUES (1)// record timestamp TS2 / OFFSET OFS2TS2 : select getdate()OFS2 : select db_property('LastCommitRedoPos')// restore the database to point in time TS1 / OFS1// shutdown the database// save the transaction log to ‘/demo/savelog’// start a utility server// drop the databaseRESTORE DATABASE 'iqdemo' FROM '/demo/dataBackup/FULL1' RECOVER UNTIL TIMESTAMP '<TS1>' USING LOG PATH '/demo/pitrLog/' , ‘/demo/savelog’// ORRESTORE DATABASE 'iqdemo' FROM '/demo/dataBackup/FULL1' RECOVER UNTIL OFFSET <OFS1> USING LOG PATH '/demo/pitrLog/', ‘/demo/savelog’

Point-in-time recovery using point-in-time recovery logs and point-in-time recovery log backup archives:

// enable point-in-time recovery SET OPTION PUBLIC.IQ_POINT_IN_TIME_RECOVERY_LOGGING = 'ONALTER DBSPACE IQ_SYSTEM_LOG RENAME '/demo/pitrLog/PITRLOG'BACKUP DATABASE FULL to '/demo/dataBackup/FULL1'// perform DDL / DML operationsCREATE TABLE T1 ( ID INT )INSERT INTO T1 VALUES (1)RECORD TIME STAMP TS1 / OFFSET OFS1TS1 : select getdate()OFS1 : select db_property('LastCommitRedoPos')// perform DDL / DML operationsCREATE TABLE T2 ( ID INT )INSERT INTO T2 VALUES (1)RECORD TIME STAMP TS2 / OFFSET OFS2TS2 : select getdate()OFS2 : select db_property('LastCommitRedoPos')// perform a PITR log backupBACKUP DATABASE POINT IN TIME RECOVERY LOGS ONLY TO '/demo/pitrLogBackup/PITR1'// perform DDL/ DML operationsCREATE TABLE T3 ( ID INT )INSERT INTO T3 VALUES (1)// restore the database to point-in-time TS2 OR OFS2// shutdown the database// start a utility server// drop the databaseRESTORE DATABASE 'iqdemo' FROM '/demo/dataBackup/FULL1'



RECOVER UNTIL TIMESTAMP '<TS2>' USING LOG PATH '/demo/pitrLogBackup/', '/demo/pitrLog/' // ORRESTORE DATABASE 'iqdemo' FROM '/demo/dataBackup/FULL1' RECOVER UNTIL OFFSET <OFS2> USING LOG PATH '/demo/pitrLogBackup/', '/demo/pitrLog/'

Point-in-time recovery on an RLV-enabled database with an incremental backup:

// Full database backupBACKUP DATABASE FULL TO '/demo/dataBackup/FULL1'// perform DDL / DML operationsCREATE TABLE T0 ( ID INT )INSERT INTO T0 VALUES (1)RECORD TIME STAMP TS0 / OFFSET OFS0// enable point-in-time recovery using an incremental backupSET OPTION PUBLIC.IQ_POINT_IN_TIME_RECOVERY_LOGGING = 'ONALTER DBSPACE IQ_SYSTEM_LOG RENAME '/demo/pitrLog/PITRLOG'BACKUP DATABASE INCREMENTAL to '/demo/dataBackup/INCR1'// perform DDL / DML operationsCREATE TABLE T1 ( ID INT )INSERT INTO T1 VALUES (1)RECORD TIME STAMP TS1 / OFFSET OFS1TS1 : select getdate()OFS1 : select db_property('LastCommitRedoPos')// perform DDL / DML operationsCREATE TABLE T2 ( ID INT )INSERT INTO T2 VALUES (1)RECORD TIME STAMP TS2 / OFFSET OFS2// Note the RLV DBspace files and their location select * from sp_iqfile() where segmentType = 'RLV'"// restore the database to point-in-time TS1 OR OFS1// shutdown the database// save the transaction log to ‘/demo/savelog’// Do a physical file backup of all files in the RLV Dbspace.// start a utility server// drop the database// Perform a restore of database from backup FULL1RESTORE DATABASE 'iqdemo' FROM '/demo/dataBackup/FULL1' // restore the RLV Dbspace files from the backup taken above to its original location// perform a point-in-time recovery to time TS1 using incremental backup INCR1 RESTORE DATABASE 'iqdemo' FROM '/demo/dataBackup/INCR1' RECOVER UNTIL TIMESTAMP '<TS1>' USING LOG PATH '/demo/pitrLog/' , ‘/demo/savelog’



Backup History

Use the sp_iqpurgebackuphistory stored procedure to manage backup history. sp_iqpurgebackuphistory deletes all rows from the SysIQBackupHistory and SysIQBackupHistoryDetail system tables, that match criteria defined by four parameters:

Parameter Type Description

bu_id unsigned bigint

Deletes entries that match the bu_id:

sp_purgeiqbackuphistory(bu_id ='9277')

bu_time_low

timestamp Deletes entries with timestamps (hh:mm:ss.ms) greater than or equal to bu_time_low:

sp_purgeiqbackuphistory( bu_time_low='2013/01/01')

bu_time_high

timestamp Deletes entries with backup times less than or equal to bu_time_high:

sp_purgeiqbackuphistory( bu_time_high='2013/01/01' )

bu_type tinyint Deletes entries that match the bu_type:

● 0 = FULL● 1 = INCREMENTAL● 2= INCREMENTAL SINCE FULL

Since SysIQBackupHistory and SysIQBackupHistoryDetail are system tables, purging entries is non-transactional and cannot be rolled back.


● See the IQ_POINT_IN_TIME_RECOVERY_LOGGING, IQ_POINT_IN_TIME_RECOVERY_LOG_INTERVAL, IQ_LOG_INTERVAL database options in Reference: Statements and Options

● See ALTER DBSPACE, BACKUP DATABASE, and RESTORE DATABASE statements in Reference: Statements and Options

● See sp_purgeiqbackuphistory procedure in Reference: Building Blocks, Tables, and Procedures




Syntax changes for SAP IQ 16.0 SP 8 PL1.


RESTORE DATABASE Restrictions that affect RLV-enabled databases for the RESTORE DATABASE RECOVER UNTIL clause in point-in-time recovery operations:

RECOVER UNTIL [ TIMESTAMP <timestamptz> | OFFEST <log-offset> ]

Attempting point-in-time recovery to a point beyond the last log backup causes the RESTORE DATABASE RECOVER UNTIL operation to fail. Always restore the RLV dbspace files of the old database in the right location manually before you run the point-in-time recovery, so that the correct version of the RLV log is used and the data recovered is correct.

Manually restore all RLV dbspace files before you perform a RESTORE DATABASE RECOVER UNTIL operation from an INCREMENTAL backup.

Restriction that affects the USING LOG PATH clause in point-in-time recovery operations on multiplex servers:

[ USING LOG PATH ' directory, [...]]

Use the current transaction log from the coordinator node. Do not include transaction logs from secondary nodes. Including transaction logs from secondary nodes causes point-in-time recovery to fail, and return a Files are missing for Point-in-time-Recovery error.

Additional Information:

● Reference: Statements and Options > RESTORE DATABASE Statement● Administration: Backup, Restore, and Data Recovery > Point-in-Time Recovery



4.3 Database Options (Changed)

Database option changes for SAP IQ 16.0 SP 8 PL1.

Option Name Description

IQ_POINT_IN_TIME_RECOVERY_LOGGING

Point-in-time recovery logging requires a data backup to become fully enabled. In previous releases, this meant performing a full data backup. Starting with SAP IQ 16.0 SP 8 PL1, point-in-time recovery logging becomes fully enabled after a FULL, INCREMENTAL, or INCREMENTAL SINCE FULL backup.

On multiplex servers, all servers must be shut down during first data backup to enable point-in-time recovery logging on the coordinator. Start the coordinator only to perform the backup. After the backup is complete, the administrator must synchronize all writers before starting them up.

Setting the POINT_IN_TIME_RECOVERY_LOGGING option to OFF, disables point-in-time recovery immediately. To re-enable point-in-time recovery, you must set POINT_IN_TIME_RECOVERY_LOGGING option to ON, then perform a FULL, INCREMENTAL, or INCREMENTAL SINCE FULL backup.

Point-in-time recovery logging will be disabled during the following multiplex configuration changes:

● Multiplex failover● Simplex to multiplex conversion● Multiplex to simplex conversion

To re-enable point-in-time recovery after multiplex configuration changes, shut down all servers. Start the coordinator or new failover coordinator, then use the ALTER DBSPACE IQ_SYSTEM_LOG RENAME command to rename the point-in-time recovery log. Perform a full data backup. Synchronize and restart all secondary nodes.

Additional Information:

● Reference: Statements and Options > IQ_POINT_IN_TIME_RECOVERY_LOGGING Option

● Administration: Backup, Restore, and Data Recovery > Point-in-Time Recovery



5 Support Package 8

New features, performance improvements, behavior changes, and user interface changes were introduced in SAP IQ 16.0 SP 8. If you are updating from an earlier release or support package, you must run the ALTER DATABASE UPGRADE command.

In this section:

PAM User Authentication (New) [page 38]Pluggable Authentication Module (PAM) support lets you write programs that rely on authentication independently of the underlying authentication scheme. PAM user authentication requires the Advanced Security Option license.

Point-in-Time Recovery (New) [page 39]Point-in-time recovery restores all committed database operations to a specified point in time. A point in time can be expressed as a timestamp and timezone, or as a log offset. This feature is available for new SAP IQ 16.0 Support Package 8 databases, and databases upgraded to Support Package 8.

In-Memory Row-Level Versioning on Multiplex (New) [page 45]In-memory row-level versioning (RLV) is now supported in multiplex.

SAP IQ Cockpit (New) [page 45]SAP IQ Cockpit is a new graphical administration tool for on-board management and monitoring of SAP IQ. SAP IQ Cockpit will replace SAP Control Center in a future support package.

Authorizing Optional Features (New) [page 46]New license checkout behavior requires the DBA to authorize access to any optionally licensed feature. SAP IQ will not attempt to check-out an optional license by default.

OData Support (New) [page 47]SAP IQ now includes an OData Server that allows web clients to communicate with an SAP IQ database server. Web clients can send OData requests to a configurable OData Producer hosted in an HTTP server, which converts OData concepts into relational database operations.

Database Options (New and Changed) [page 48]Database option changes for SAP IQ 16.0 SP 8.

Database Properties (New and Changed) [page 50]New database properties for SAP IQ 16.0 SP 8.

SQL Statements (Changed) [page 50]Syntax changes for SAP IQ 16.0 SP 8.

Utilities (Changed) [page 52]Changes to startup parameters for SAP IQ 16.0 SP 8.

Stored Procedures (New and Changed) [page 52]System stored procedure changes for SAP IQ 16.0 SP08.

Tables and Views (Changed) [page 53]System view column changes for SAP IQ 16.0 SP 8.

Product Editions (Changed) [page 53]



The Small Business Edition (SE) and Single Application Edition Server (SA) are no longer available.

default.cfg (Changed) [page 54]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 the default.cfg configuration file. The -tl parameter was added to default.cfg, with a value of 0.

Documentation Changes [page 54]The SAP IQ 16.0 SP 8 documentation collection contains new and retitled manuals.

5.1 PAM User Authentication (New)

Pluggable Authentication Module (PAM) support lets you write programs that rely on authentication independently of the underlying authentication scheme. PAM user authentication requires the Advanced Security Option license.

PAM authentication centralizes user authentication in a separate external system-wide module. If you already use PAM for other databases, such as SAP ASE you can use the same credentials on all of your systems.

You can "plug in" any authentication mechanism to a PAM system by writing an authentication module. To configure PAM to use that module, add the module to the service name, the set of rules used in PAM authentication.

PAM is a service supported on many UNIX-based systems, but not Windows. The implementation for PAM User Authentication in SAP IQ uses standard APIs to interface with PAM service in the operating system. In the SAP IQ 16.0 release, these APIs have been validated on the LinuxAMD64 operating system. The other UNIX operating systems have not been formally validated by SAP. See your operating system documentation for details on how to enable and set up PAM for SAP IQ.

You must upgrade your database to Support Package 8, or create a new database to use PAMUA.

Enabling PAM User Authentication

1. Configure PAM on your Linux or UNIX system. For this example, assume a PAM service name PamRule.2. Add the PAM value to the LOGIN_MODE database option:

SET OPTION PUBLIC.login_mode = PAMUA

3. Create a login policy that assigns values to pam_servicename and (optionally) pam_failover_to_std:

CREATE LOGIN POLICY pam_policy

pam_servicename = PamRule

pam_failover_to_std = ON

4. Assign the login policy to the users of PAMUA:

ALTER USER pam_userID LOGIN POLICY pam_policy



5. Verify that users can log on using PAM user authentication:

dbping –c “uid=pam_userID;pwd=<pam_user_password>;links=tcpip(host=iq_server;port=6263);eng=IQdb” –d

See also these topics:

● ALTER LOGIN POLICY Statement in Reference: Statements and Options● CREATE LOGIN POLICY Statement in Reference: Statements and Options● LOGIN_MODE Option in Reference: Statements and Options● Login Policy Options in Reference: Statements and Options● SYSLOGINPOLICYOPTION system view in Reference: Building Blocks, Tables, and Procedures

5.2 Point-in-Time Recovery (New)

Point-in-time recovery restores all committed database operations to a specified point in time. A point in time can be expressed as a timestamp and timezone, or as a log offset. This feature is available for new SAP IQ 16.0 Support Package 8 databases, and databases upgraded to Support Package 8.


Point-in-time recovery extends, but does not replace standard backup and recovery operations. Point-in-time recovery always begins by restoring a database from a data backup, then replays all committed activity from the recovery logs that cover the entire time period between the backup and the specified point in time. Transactions that were in progress, but not committed are rolled back.

Point-in-time recovery differs from standard backup and restore operations. Point-in-time recovery cannot recover a database from a clean shutdown or crash via normal crash recovery.

Enabling Point-in-Time Recovery

1. Set IQ_POINT_IN_TIME_RECOVERY_LOGGING to 'ON':

SET OPTION PUBLIC.IQ_POINT_IN_TIME_RECOVERY_LOGGING = 'ON'

2. Use ALTER DBSPACE to identify the directory where you want to archive the recovery logs:

ALTER DBSPACE IQ_SYSTEM_LOG RENAME <new-directory-specification>/<file-prefix>

SAP IQ.db file by default. This command saves the log in another directory. The saves the point-in-time recovery log in the same directory as the new-directory-specification must point to an existing directory. For multiplex servers, the IQ_SYSTEM_LOG directory must reside on a shared file system and be writable by all multiplex nodes. For other constraints, see Redirecting Log Output.



3. BACKUP DATABASE ... TO <archive_device>

Point in time recovery logging only becomes fully enabled when the data backup begins. On multiplex servers, all servers must be shut down during first data backup to enable point-in-time recovery logging. Shutdown all secondary nodes first. Allow some time to let the coordinator release all global free list allocations, then shutdown the coordinator. Start the coordinator only to perform the backup. After the backup is complete, synchronize all and restart all secondary nodes.

Redirecting Log Output

By default, SAP IQ saves the point-in-time recovery log in the same directory as the .db file. To save the log in another directory, use:

ALTER DBSPACE IQ_SYSTEM_LOG RENAME ' new-directory-specification/file-prefix '

The new-directory-specification must point to an existing directory. If point in time recovery logging is active, using this command with a new-directory-specification, opens a new log at the new location. 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.

Log Size

The IQ_LOG_MAX_SIZE option limits the size of the log:

SET OPTION PUBLIC.IQ_LOG_MAX_SIZE = ' <megabytes> '

The default setting of 0 allows the log size to increase without limit. If you limit the log size, and the file exceeds the limit, the server closes the current log, and creates a new log in the same directory. Subsequent backups are written to the new log.



Log Names

All recovery logs include a .iqlog extension. Token position within the file name provide statistics about the log:

Position Description

<prefix> A <prefix> is optional. If the ALTER DBSPACE new-directory-specification includes a terminating string without a slash or backslash, the terminating string is prefixed to the log name.

_000 The first 3 digits in the log name is the server ID. SAP IQ always assigns _000 as the server ID to simplex servers.

_000000 The 6 digits that follow the server identifier, is the log sequence number.

If IQ_POINT_IN_TIME_RECOVERY_LOGGING is ON, each log backup or ALTER DBSPACE IQ_SYSTEM_LOG RENAME closes the current log and opens a new one. Each new log increments the log sequence number.

_0000 The 4 digits that follow the log sequence number is the log sub-sequence number.

A new log that opens after a backup or ALTER DBSPACE IQ_SYSTEM_LOG RENAME starts with a sub-sequence equal to 1. If the archive size exceeds the value set by IQ_LOG_MAX_SIZE, the server closes the current log and opens a new one. The sub-sequence number is incremented to reflect the change.

Automatic Backups

To backup the logs required by point-in-time recovery at set time intervals, use:

SET OPTION PUBLIC.IQ_POINT_IN_TIME_RECOVERY_LOG_BACKUP_INTERVAL= ' <minutes> ' Time intervals are expressed in minutes. The IQ_SYSTEM_LOG_BACKUP_INTERVAL option backs up the transaction log and RLV log. The point-in-time recovery logs (.iqlog) are not included in the backup because of size considerations. The IQ_SYSTEM_LOG_BACKUP_INTERVAL option must be explicitly set. The minimum supported backup interval is 5 minutes. Default behavior requires manual backups of the activity logs.

Manual Backups

A manual backup archives the point-in-time recovery logs:

BACKUP DATABASE ... POINT IN TIME RECOVERY LOGS ONLY TO ' target-directory / archive-file-name '

SAP IQ closes the current log and starts a new one. Copies of the previous logs are left behind as backups. The archive is written to the to the target-directory.



POINT IN TIME RECOVERY LOGS ONLY supports only one TO clause, which points to a location on the file system. Name of the archive is user-determine. No other options are allowed. The POINT IN TIME RECOVERY LOGS ONLY clause can only be used to backup activity logs for point-in-time recovery. Do not use this clause as part of a data backup.

RESTORE and Recovery

Always begin a point-in-time recovery by restoring a database from a full data backup, then apply all incremental backups prior to the point in time you want to recover. Use the RESTORE DATABASE point-in-time recovery syntax extensions as a final step to replay all committed activity from the recovery logs that cover the entire time period between the backup and the period just prior point in time you specify:

RESTORE DATABASE '< db_file > saves the point-in-time recovery log in the same directory as thePerform a data' [ FROM '< file-name >' <...> [ USING LOG PATH ' directory, [...]] RECOVER UNTIL [ TIMESTAMP <timestamptz> | OFFEST <log-offset> ] KEY <key_spec> [ VERIFY COMPATIBILE ]

Always specify a timestamp that is greater than the backup time of the data backup specified in the FROM clause of the restore command. This ensures that the database includes all committed transactions in the recovery logs. If the specified point in time is earlier than the last checkpoint in the backup database, the server returns an error.

Restriction● A dbspace that you create after enabling point-in-time recovery may only be recorded in the point-in-

time recovery log. If this is the case, you cannot rename the dbspace during a RESTORE DATABASE RECOVER UNTIL operation.

● For RLV-enabled databases, attempting point-in-time recovery to a point beyond the last log backup causes the RESTORE DATABASE RECOVER UNTIL operation to fail. Always restore the RLV dbspace files of the old database in the right location manually before you run the point-in-time recovery, so that the correct version of the RLV log is used and the data recovered is correct.Manually restore all RLV dbspace files before you perform a RESTORE DATABASE RECOVER UNTIL operation from an INCREMENTAL backup.

● Point-in-time recovery log backups that fail before the backup is complete return incomplete results and generate a Files are missing for point-in-time recovery exception. Accurate point-in-time recovery is only possible with complete log backups. If the backup fails, SAP IQ creates a transaction log backup called <timestamp>.log in the IQ_SYSTEM_LOG directory. Remove this file and manually backup the point-in-time recovery log.

Performing Point-in-Time Recovery

1. Shutdown the database server.



2. Start a server that you can use to connect to the utility database:

start_iq -su mypwd -gd DBA -gm 1 -n my_server

3. Start dbisql and connect to the utility database:

dbisql -c "UID=DBA;PWD=mypwd;DBN=utility_db"

4. Perform a full database restore prior to the point in time you want to recover.Run all RESTORE DATABASE commands from dbisql. Repeat this step, for every incremental backup you want to restore. All incremental backups must be prior to the point in time you want to recover.

5. Run RESTORE DATABASE with the appropriate point-in-time syntax extensions to recover from the recovery logs and PITR archives. See the Recovery Scenarios for syntax examples.

6. Shutdown the server and utility database.7. Start the database server normally.

Recovery Scenarios

Point in time recovery using point in time recovery logs only:

// enable Point in time recovery SET OPTION PUBLIC.IQ_POINT_IN_TIME_RECOVERY_LOGGING = 'ON'ALTER DBSPACE IQ_SYSTEM_LOG RENAME '/demo/pitrLog/PITRLOG'BACKUP DATABASE FULL to '/demo/dataBackup/FULL1'// perform some DDL/DML operations CREATE TABLE T1 ( ID INT )INSERT INTO T1 VALUES (1)// record timestamp TS1 / OFFSET OFS1TS1 : select getdate()OFS1 : select db_property('LastCommitRedoPos')// perform DDL/ DML operationsCREATE TABLE T2 ( ID INT )INSERT INTO T2 VALUES (1)// record timestamp TS2 / OFFSET OFS2TS2 : select getdate()OFS2 : select db_property('LastCommitRedoPos')// restore the database to point in time TS1 / OFS1// shutdown the database// save the transaction log to ‘/demo/savelog’// start a utility server// drop the databaseRESTORE DATABASE 'iqdemo' FROM '/demo/dataBackup/FULL1' RECOVER UNTIL TIMESTAMP '<TS1>' USING LOG PATH '/demo/pitrLog/' , ‘/demo/savelog’// ORRESTORE DATABASE 'iqdemo' FROM '/demo/dataBackup/FULL1' RECOVER UNTIL OFFSET <OFS1> USING LOG PATH '/demo/pitrLog/', ‘/demo/savelog’

Point-in-time recovery using point-in-time recovery logs and point-in-time recovery log backup archives:

// enable point-in-time recovery SET OPTION PUBLIC.IQ_POINT_IN_TIME_RECOVERY_LOGGING = 'ONALTER DBSPACE IQ_SYSTEM_LOG RENAME '/demo/pitrLog/PITRLOG'BACKUP DATABASE FULL to '/demo/dataBackup/FULL1'// perform DDL / DML operationsCREATE TABLE T1 ( ID INT )INSERT INTO T1 VALUES (1)RECORD TIME STAMP TS1 / OFFSET OFS1



TS1 : select getdate()OFS1 : select db_property('LastCommitRedoPos')// perform DDL / DML operationsCREATE TABLE T2 ( ID INT )INSERT INTO T2 VALUES (1)RECORD TIME STAMP TS2 / OFFSET OFS2TS2 : select getdate()OFS2 : select db_property('LastCommitRedoPos')// perform a PITR log backupBACKUP DATABASE POINT IN TIME RECOVERY LOGS ONLY TO '/demo/pitrLogBackup/PITR1'// perform DDL/ DML operationsCREATE TABLE T3 ( ID INT )INSERT INTO T3 VALUES (1)// restore the database to point-in-time TS2 OR OFS2// shutdown the database// start a utility server// drop the databaseRESTORE DATABASE 'iqdemo' FROM '/demo/dataBackup/FULL1' RECOVER UNTIL TIMESTAMP '<TS2>' USING LOG PATH '/demo/pitrLogBackup/', '/demo/pitrLog/' // ORRESTORE DATABASE 'iqdemo' FROM '/demo/dataBackup/FULL1' RECOVER UNTIL OFFSET <OFS2> USING LOG PATH '/demo/pitrLogBackup/', '/demo/pitrLog/'

Backup History

Use the sp_iqpurgebackuphistory stored procedure to manage backup history. sp_iqpurgebackuphistory deletes rows from the SysIQBackupHistory and SysIQBackupHistoryDetail system tables that match criteria defined by four parameters:

Parameter Type Description

bu_id unsigned bigint

Deletes entries that match the bu_id:

sp_purgeiqbackuphistory(bu_id ='9277')

bu_time_low

timestamp Deletes entries with timestamps (hh:mm:ss.ms) greater than or equal to bu_time_low:

sp_purgeiqbackuphistory( bu_time_low='2013/01/01')

bu_time_high

timestamp Deletes entries with backup times less than or equal to bu_time_high:

sp_purgeiqbackuphistory( bu_time_high='2013/01/01' )

bu_type tinyint Deletes entries that match the bu_type:

● 0 = FULL● 1 = INCREMENTAL● 2 = INCREMENTAL SINCE FULL● 5 = POINT IN TIME RECOVERY



Since SysIQBackupHistory and SysIQBackupHistoryDetail are system tables, purging entries is non-transactional and cannot be rolled back.


● See the IQ_POINT_IN_TIME_RECOVERY_LOGGING, IQ_POINT_IN_TIME_RECOVERY_LOG_INTERVAL, IQ_LOG_INTERVAL database options in Reference: Statements and Options

● See ALTER DBSPACE, BACKUP DATABASE, and RESTORE DATABASE statements in Reference: Statements and Options

● See sp_purgeiqbackuphistory procedure in Reference: Building Blocks, Tables, and Procedures

5.3 In-Memory Row-Level Versioning on Multiplex (New)

In-memory row-level versioning (RLV) is now supported in multiplex.

The RLV store, resides on the coordinator, making it the RLV writer. All other nodes in the multiplex are RLV readers.

On the RLV writer, you can execute DDL, DML and query data. On RLV readers, data in RLV-enabled tables is available to queries, but modification of data and schema is not allowed.

For queries involving RLV-enabled tables executing on RLV readers:

● The RLV reader makes an ODBC connection to the RLV writer.● Only the part of the query referencing RLV-enabled tables is forwarded to and executed on the RLV writer.● Results are then sent back to the RLV reader.● All non-RLV-enabled table portions of the query execute on the RLV reader.

5.4 SAP IQ Cockpit (New)

SAP IQ Cockpit is a new graphical administration tool for on-board management and monitoring of SAP IQ. SAP IQ Cockpit will replace SAP Control Center in a future support package.

Unlike SAP Control Center, SAP IQ Cockpit is designed as an onboard management solution, where you install the cockpit on each SAP IQ simplex host, and manage and monitor that system. In a multiplex, you install the cockpit on each node.

SAP IQ Cockpit provides availability monitoring, historical monitoring, and real-time monitoring in a scalable Web application. It offers real-time alerts of availability, performance, and capacity issues, and intelligent tools for spotting performance and usage trends. Availability, performance, and capacity alerts are configured and enabled by default.

The SAP IQ installer gives you the option of installing either SAP IQ Cockpit, SAP Control Center, or both:



● For an enterprise-level landscape view of all database systems in your data center – such as a heat chart perspective reporting the health status of multiple systems – install SAP Control Center.

● If you are managing/monitoring an SAP IQ simplex or multiplex host, and intend to use new SP 8 features (for example, point-in-time recovery, or in-memory row-level versioning on multiplexes), install SAP IQ Cockpit.

● If you are managing/monitoring an SAP IQ simplex or multiplex host, but do not intend to use new SP 8 features, you can install either SAP IQ Cockpit, or SAP Control Center. SAP Control Center supports SP03 (and earlier) support packages.

● SAP IQ Cockpit uses server-based authentication, which means that an SAP IQ system will not appear in the Login screen until an IQ database is created and started. In order to log into SAP IQ Cockpit for the first time, you can install either SAP IQ Cockpit or SAP Control Center to create an initial database:○ Start SAP IQ Cockpit, and create the demo database. Then, login using SAP IQ Cockpit and create the

IQ database.○ Or, use SAP Control Center to create an IQ database. Then, login using SAP IQ Cockpit.

5.5 Authorizing Optional Features (New)

New license checkout behavior requires the DBA to authorize access to any optionally licensed feature. SAP IQ will not attempt to check-out an optional license by default.

All servers provide a initial 30-day grace period, which provides access to all SAP IQ features and options. To use an option beyond the 30-day evaluation period, you must purchase and install an appropriate SAP Software Asset Management (SySAM) 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.

Authorizing access to a separately licensed option, grants access to that option by all users system-wide. Separately licensed features continue to be available as licensed options after the grace period expires.

Verifying Your License

To verify your license, 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 No



Optional 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 Reference: Building Blocks, Tables, and Procedures for information about authorizing optional features and other issues related to license management configuration.

NoteThe disallow parameter can only disable an unlicensed option if the option is not in use. If the server checks out an unlicensed option, the option cannot be unauthorized and the server may fall into grace mode.

5.6 OData Support (New)

SAP IQ now includes an OData Server that allows web clients to communicate with an SAP IQ database server. Web clients can send OData requests to a configurable OData Producer hosted in an HTTP server, which converts OData concepts into relational database operations.

These features have been added as part of OData support:

● OData protocol version 2 compliance● OData Producer● Embedded Jetty WebServer (with alternative HTTP server support)● OData Server utility● OData Server Stop utility● Service utility (dbsvc) can create OData Windows services

These enhancements have been added as part of OData support:

Multiple OData Producer support The OData Server supports multiple customizable OData Producers that allow you to establish multiple database connections. Use the new embedded HTTP server option, Producers, in your OData Server configuration to create OData Producers.Optimistic Concurrency Control (ETags) OData Producers now support Optimistic Concurrency Control as defined by version 2.0 of the OData Specification. The concurrencytoken clause of the ENTITY OSDL



statement is used to generate ETags that identify the state of an entity instance at the time the instance is requested.Search strings are restricted to 254 bytes When using OData filters—such as startswith, substringof, and indexofwith—on long search strings, searches are performed on the first 254 bytes only.Support for proxy table insertions All key properties must be explicitly specified when creating entities in entity sets that are proxy tables in an SAP IQ database.Substringof return value The substringof(s1, s2) filter returns whether the s1 string is a substring of s2.

5.7 Database Options (New and Changed)

Database option changes for SAP IQ 16.0 SP 8.


CONVERSION_MODE (Behavior change.) CONVERSION_MODE option 2 allows all explicit conversions to be permitted as implicit conversions on various operations. If this option is not set, the user must use CAST or CONVERT in queries that require explicit conversions.

See CONVERSION_MODE in Reference: Statements and Options.

CONVERSION_ERROR (Behavior change.) SAP IQ no longer truncates converted tinyint, smallint, int, unsigned int, double, bigint, unsigned bigint, date, datetime values that are greater than the column width. If the CONVERSION_ERROR option is OFF, SAP IQ inserts a NULL value when possible. If CONVERSION_ERROR is ON, SAP IQ logs a conversion error.

See CONVERSION_ERROR in Reference: Statements and Options.

IQ_LOG_MAX_SIZE (New option.) Sets the maximum size, in megabytes, of the point-in-time recovery archive.

SET OPTION PUBLIC.IQ_LOG_MAX_SIZE = 'megabytes'

If the archive exceeds the size limit, the server creates a new archive in the archive directory. The default value (0) sets an unlimited size for the archive.

See IQ_LOG_MAX_SIZE in Reference: Statements and Options.




IQ_POINT_IN_TIME_RECOVERY_LOGGING Enables point-in-time recovery logging:

SET OPTION PUBLIC.IQ_POINT_IN_TIME_RECOVERY_LOGGING = 'ON'

Setting this option is the first of two steps required to fully enable point-in-time recovery.

See IQ_POINT_IN_TIME_RECOVERY_LOGGING in Reference: Statements and Options.

IQ_SYSTEM_LOG_BACKUP_INTERVAL Sets a time interval, in minutes, between automatic backups of the point-in-time recovery logs.

SET OPTION PUBLIC.IQ_POINT_IN_TIME_RECOVERY_LOG_BACKUP_INTERVAL='minutes'

Enables automatic backups of the PITR recovery logs. The minimum supported backup interval is 5 minutes. Default behavior requires manual backup of the logs as part of the BACKUP DATABASE statement.

See IQ_SYSTEM_LOG_BACKUP_INTERVAL in Reference: Statements and Options.

LOGIN_MODE (New allowed value.) PAMUA specifies that all logins to the database must be made using PAM logins.

See LOGIN_MODE in Reference: Statements and Options.

MAX_RV_REMOTE_TRANSFER_MB (New) On a multiplex, limit the volume of RLV-enabled table data allowed to be transferred from the RLV store when a statement is executed on another node.

See MAX_RV_REMOTE_TRANSFER_MB in Reference: Statements and Options

PROGRESS_MESSAGES (New) Controls whether progress messages are sent from the database server to the client.

See PROGRESS_MESSAGES in Reference: Statements and Options

.



5.8 Database Properties (New and Changed)

New database properties for SAP IQ 16.0 SP 8.

Name Status Description

PointInTimeRecovery New Is point-in-time recovery enabled:

● Requested - The IQ_POINT_IN_TIME_RECOVERY_LOGGING option is ON, but logging is not enabled by doing a data backup

● On - The IQ_POINT_IN_TIME_RECOVERY_LOGGING option is ON and logging is enabled

● Off - The IQ_POINT_IN_TIME_RECOVERY_LOGGING option is OFF or disabled

IQPointInTimeRecoveryLogFilename New Returns the full path of the current IQ_SYSTEM_LOG file.

IQPointInTimeRecoveryLogStatus New Returns the current status of point-in-time recovery log.

LastCommitRedoPos Changed Returns the log offset of the last committed transaction.


Syntax changes for SAP IQ 16.0 SP 8.


ALTER DBSPACE

New syntax. By default, SAP IQ saves the point-in-time recovery log in the same directory as the .db file. To save the log in another directory, use:

ALTER DBSPACE IQ_SYSTEM_LOG RENAME <new-directory-specification> / file-prefix

The new-directory-specification must point to an existing directory. For multiplex servers, this directory must reside on a shared file system and be writable by all multiplex nodes.

See ALTER DBSPACE Statement in Reference: Statements and Options for detailed syntax and usage information.

ALTER LOGIN POLICY

New login policy options.

● PAM_FAILOVER_TO_STD – use standard authentication if PAM authentication is enabled but the PAM library is unavailable due to a system failure.

● PAM_SERVICENAME – the PAM service name to use when authenticating.

See ALTER LOGIN POLICY Statement in Reference: Statements and Options for detailed syntax and usage information.




ALTER MULTIPLEX SERVER

New clause:

● ENABLE | DISABLE RLV STORE supports of RLV in an existing multiplex

See ALTER MULTIPLEX SERVER Statement in Reference: Statements and Options for detailed syntax and usage information.

BACKUP DATABASE

New Syntax. A manual backup archives the point-in-time recovery logs:

POINT IN TIME RECOVERY LOGS ONLY TO ' <target-directory> / <archive-file-name> '

SAP IQ closes the current log and starts a new one. Copies of the previous logs are left behind as backups. The archive is written to the to the <target-directory>.

See BACKUP DATABASE Statement in Reference: Statements and Options for detailed syntax and usage information.

CREATE LOGIN POLICY

New login policy options.

● PAM_FAILOVER_TO_STD – Use standard authentication if PAM authentication is enabled but the PAM library is unavailable due to a system failure.

● PAM_SERVICENAME – The PAM service name to use when authenticating.

See CREATE LOGIN POLICY Statement in Reference: Statements and Options for detailed syntax and usage information.

CREATE MULTIPLEX SERVER

New clause:

● ENABLE | DISABLE RLV STORE supports of RLV in a new multiplex

See CREATE MULTIPLEX SERVER Statement in Reference: Statements and Options for detailed syntax and usage information.

RESTORE DATABASE

New syntax instructs the server to search along multiple paths to locate multiple point-in-time recovery archives:

USING LOG PATH ' directory 1, directory 2, ... '

New syntax recovers data from the recovery logs up to the date and time specified by the timestamp, or transaction log offset:

RECOVER UNTIL [ TIMESTAMP <timestamptz> | OFFSET <log-offset> ]

<timestamptz> is a TIMESTAMP WITH TIMEZONE datatype. <logoffset> is an UNSIGNED BIGINT that represents a transaction log offset.

See RESTORE DATABASE Statement in Reference: Statements and Options for detailed syntax and usage information.



5.10 Utilities (Changed)

Changes to startup parameters for SAP IQ 16.0 SP 8.

Table 1: Startup Parameters

Parameter Description

–iqlrt New start_iq startup parameter controls the number of threads that SAP IQ uses during point-in-time recovery operations.

Usage:

-iqlrt <number>

Default is 50 threads per CPU. Total number of all server threads cannot exceed 4096.

See -iqlrt iqsrv16 Server Option in the Utility Guide.

5.11 Stored Procedures (New and Changed)

System stored procedure changes for SAP IQ 16.0 SP08.


sp_iqlmconfig New license configuration parameters let the DBA explicitly authorize access to licensed options. Unless an optional feature is explicitly authorized, access to that feature will not be available.

See sp_iqlmconfig Procedure in Reference: Building Blocks, Tables, and Procedures.

sp_iqbackupdetails Behavior change. Now includes PITR (point-in-time recovery) as a value in the backup_type column.

See sp_iqbackupdetails in Reference: Building Blocks, Tables, and Procedures.

sp_iqbackupsummary Behavior change. Now includes details about point-in-time recovery backups.

See sp_iqbackupsummary in Reference: Building Blocks, Tables, and Procedures.

sp_iqmpxinfo Behavior change. Now includes details about the RLV store in mutliplex.

See sp_iqmpxinfo in Reference: Building Blocks, Tables, and Procedures.




sp_iqpurgebackuphistoryy New. Manages backup history and deletes rows from the SysIQBackupHistory and SysIQBackupHistoryDetail system tables.

See sp_iqpurgebackuphistory in Reference: Building Blocks, Tables, and Procedures.

sp_iqrestoreaction Behavior change. Now identifies actions required to bring a database to a consistent state with a given point in time. Not supported for multiple timelines or alternate timelines.

See sp_iqrestoreaction in Reference: Building Blocks, Tables, and Procedures.

5.12 Tables and Views (Changed)

System view column changes for SAP IQ 16.0 SP 8.

System View Description of Change

SYSLOGINPOLICYOPTION Names and values now supported for new login policy options PAM_FAILOVER_TO_STD and PAM_SERVICENAME.

See Login Policy Options in Reference: Statements and Options.

SYSIQMPXSERVER RLV now supported in multiplex.

See Administration: In-Memory Row-Level Versioning.

5.13 Product Editions (Changed)

The Small Business Edition (SE) and Single Application Edition Server (SA) are no longer available.

SAP® IQ 16.0 SP 8 is available in these product editions:

● Enterprise Edition● Evaluation Edition● Express Edition● Edge Edition



5.14 default.cfg (Changed)

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 the default.cfg configuration file. The -tl parameter was added to default.cfg, with a value of 0.

Table 2: New parameter set by start_iq

Parameter Value Description

-tl 0 Disables the sending of liveness packets across a client/server. This setting prevents the client/server connection from being severed, which is useful when troubleshooting.

5.15 Documentation Changes

The SAP IQ 16.0 SP 8 documentation collection contains new and retitled manuals.

Title Description

Interactive SQL Guide New guide for using the Interactive SQL (dbisql) utility. Formerly located in Utility Guide.

What's New in SAP IQ 16.0 Retitled. Formerly titled New Features Summary.

SAP IQ Cockpit New online help guide for using SAP IQ Cockpit.



6 Support Package 4

The version of OpenSSL has been upgraded to 1.0.1i to increase security.



7 Support Package 3

JRE and licensing changes were introduced in SAP® IQ 16.0 SP 3. If you are updating from an earlier release or support package, you must run the ALTER DATABASE UPGRADE command.

NoteThe previous support package—SP 2—was released only on Linux. Support package SP 3 includes functionality introduced in previous support packages. If you installed SP03 on IBM AIX, HP-UX, Solaris, or Windows, see the 16.0 SP2 New Features Summary section of this document for additional new features, performance enhancements, and behavior changes new to your platform.

In this section:

New Features in SP03 [page 56]SAP IQ 16.0 SP03 includes the new SAP Java Runtime Environment.

Behavior Changes in SP03 [page 57]SAP IQ 16.0 SP03 introduces encryption-related behavior changes.

7.1 New Features in SP03

SAP IQ 16.0 SP03 includes the new SAP Java Runtime Environment.

In this section:

New JRE Environment Variables and Directories [page 56]New JRE environment variables and directories were added in SAP IQ 16.0 SP03.

7.1.1 New JRE Environment Variables and Directories

New JRE environment variables and directories were added in SAP IQ 16.0 SP03.

The SYBASE_JRE7 environment variables were replaced with:

● SAP_JRE7_64● SAP_JRE7● SAP_JRE7_32

The $Sybase/shared/JRE<version> directory was replaced with these directories on UNIX:

● $SYBASE/shared/JRE-7_(minor_version)_32BIT● $SYBASE/shared/JRE-7_(minor_version)_64BIT



The %Sybase/shared/JRE<version> directory was replaced with these directories on Windows:

● %SYBASE%\shared\JRE-7_(minor_version)_32BIT● %SYBASE%\shared\JRE-7_(minor_version)_64BIT

7.2 Behavior Changes in SP03

SAP IQ 16.0 SP03 introduces encryption-related behavior changes.

NoteThe previous support package—SP2—was released only on Linux. If you installed SP03 on IBM AIX, HP-UX, Solaris, or Windows, see the Behavior Changes in SP2 section of this document for additional behavior changes new to your platform.

In this section:

FIPS Encryption Support [page 57]As of 16.0 SP03, SAP IQ no longer supports FIPS encryption on the IBM AIX, HP-UX, or Linux POWER platforms.

Advanced Security Option Requirement for FIPS and RSA [page 58]SAP IQ no longer requires the Advanced Security Option for FIPS and RSA encryption support.

7.2.1 FIPS Encryption Support

As of 16.0 SP03, SAP IQ no longer supports FIPS encryption on the IBM AIX, HP-UX, or Linux POWER platforms.

SAP IQ SP03 supports FIPS on:

● LinuxAMD64 Server● Solaris Sparc Server● Solaris AMD64 Server● Windows AMD64 Server● LinuxAMD32 Client● Windows32 Client

For behavior changes, see Encryption Support Changes in the 16.0 SP2 New Features Summary section of this document.



7.2.2 Advanced Security Option Requirement for FIPS and RSA

SAP IQ no longer requires the Advanced Security Option for FIPS and RSA encryption support.

For details about the Advanced Security Option, see Guide to Licensed Options.



8 Support Package 2

New features, performance improvements, behavior changes, and SAP Control Center (SCC) changes were introduced in SAP IQ 16.0 SP 2. If you are updating from an earlier release or support package, you must run the ALTER DATABASE UPGRADE command.

In this section:

New Features in SP2 [page 59]SAP IQ 16.0 SP2 includes several new features.

Performance Improvements in SP2 [page 61]SAP IQ 16.0 SP2 introduces performance improvements.

Behavior Changes in SP2 [page 62]SAP IQ 16.0 SP2 introduces several behavior changes.

SAP Control Center Changes [page 71]There have been changes to the SAP IQ plug-in for SAP Control Center (SCC) 3.3.

8.1 New Features in SP2

SAP IQ 16.0 SP2 includes several new features.

In this section:

Multiplex High Availability [page 60]In the event of a coordinator failure, local SCC IQ agents can now automatically restart any server in the multiplex, start a new coordinator, or perform automatic failover.

Cache Dbspace for Direct-Attached Storage [page 60]Use the cache dbspace to add direct-attached storage devices, such as high-performance solid-state disks (SSDs), to your multiplex nodes or simplex server. Local direct-attached storage provides an SSD buffer pool extension to your database, which can improve I/O performance in general, and shared SAN device performance in particular.

LOAD TABLE Supports Loading from Compressed .gzip or .gz Files [page 61]The FROM clause of the LOAD TABLE statement now supports loading external files compressed with .gzip file compression.



8.1.1 Multiplex High Availability

In the event of a coordinator failure, local SCC IQ agents can now automatically restart any server in the multiplex, start a new coordinator, or perform automatic failover.

The ability to restart nodes safely and automatically improves the high availability of SAP IQ.

Automatic restart and coordinator failover require a running SCC IQ Agent on the host where the multiplex server runs. If SCC is unavailable, manual coordinator restart or failover is needed.

Start an agent for each node. To associate a specific agent login with a target server, use the CREATE AGENT statement. Use ALTER AGENT to change the agent login information, or DROP AGENT to delete the login information. To enable automatic coordinator failover, set the root logical server policy option ENABLE_AUTOMATIC_FAILOVER.

The system view SYSIQMPXSERVERAGENT stores agent login information.

See these topics in the SAP IQ 16.0 SP2 documentation:

● Enabling Automatic Restart and Coordinator Failover in Administration: Multiplex● ALTER AGENT Statement, ALTER LS POLICY Statement, CREATE AGENT Statement, CREATE LS POLICY

Statement, and DROP AGENT Statement in Reference: Statements and Options● SYSIQMPXSERVERAGENT System View in Reference: Building Blocks, Tables, and Procedures.

8.1.2 Cache Dbspace for Direct-Attached Storage

Use the cache dbspace to add direct-attached storage devices, such as high-performance solid-state disks (SSDs), to your multiplex nodes or simplex server. Local direct-attached storage provides an SSD buffer pool extension to your database, which can improve I/O performance in general, and shared SAN device performance in particular.

Configure a cache dbspace local to each node. The server then caches copies of locally used read-only pages—for the IQ main store dbspaces to which this node has affinity—in the cache dbspace. In subsequent reads from the IQ main store dbspace files, the server first checks the cache dbspace to see if the page exists. If it does exist, the server reads the page from the high-speed SSD cache dbspace, rather than the shared SAN IQ main store dbspace, thereby increasing performance.

Use SAP Control Center and these stored procedures to report key performance indicators for your direct-attached storage:

● sp_iqcheckdb● sp_iqdbspace● sp_iqfile● sp_iqstatus

The CREATE DBSPACE statement now supports cache dbspaces. You can also create the cache dbspace, and manage the dbspace and its storage, using SAP Control Center.


● Cache Dbspace for Direct-Attached Storage in Administration: Database● Creating the Cache Dbspace in Administration: Database



● Dropping the Cache Dbspace in Administration: Database● Adding Storage to the Cache Dbspace in Administration: Database● Removing Storage from the Cache Dbspace in Administration: Database● Disabling and Re-enabling the Cache Dbspace in Administration: Database● Changing the Readonly/Readwrite Status of a Cache Dbspace DBfile in Administration: Database● Monitoring the Cache Dbspace in Administration: Database● CREATE DBSPACE Statement in Reference: Statements and Options● sp_iqcheckdb Procedure in Reference: Building Blocks, Tables, and Procedures● sp_iqdbspace Procedure in Reference: Building Blocks, Tables, and Procedures● sp_iqfile Procedure in Reference: Building Blocks, Tables, and Procedures● sp_iqstatus Procedure in Reference: Building Blocks, Tables, and Procedures

Related Information

Stored Procedure Changes [page 69]SQL Statement Changes [page 68]

8.1.3 LOAD TABLE Supports Loading from Compressed .gzip or .gz Files

The FROM clause of the LOAD TABLE statement now supports loading external files compressed with .gzip file compression.

The LOAD TABLE statement can load compressed client and server files only in gzip format. Any file with an extension ".gz" or ".gzip" is assumed to be a compressed file. Named pipes or secondary files are not supported during a compressed file load. Compressed files and uncompressed files can be specified in the same LOAD TABLE statement. Each compressed file in a load is processed by one thread.

ON FILE ERROR CONTINUE is not supported for compressed file loading.

See this topic in the SAP IQ 16.0 SP2 documentation:

LOAD TABLE Statement in Reference: Statements and Options

8.2 Performance Improvements in SP2

SAP IQ 16.0 SP2 introduces performance improvements.

In this section:

LIKE Condition Acceleration [page 62]



LIKE conditions now run faster, provided the LIKE pattern contains at least <N> contiguous nonwildcard characters.

8.2.1 LIKE Condition Acceleration

LIKE conditions now run faster, provided the LIKE pattern contains at least <N> contiguous nonwildcard characters.

You must be specifically licensed to use the Unstructured Data Analytics functionality.


● Comparison of WD and TEXT Indexes in Unstructured Data Analytics● LIKE Conditions in Reference: Building Blocks, Tables, and Procedures

8.3 Behavior Changes in SP2

SAP IQ 16.0 SP2 introduces several behavior changes.

In this section:

Database Option Changes [page 63]If you are updating from an earlier release of SAP IQ, the truncation behavior and maximum values of some database options has changed in release 16.0 SP2.

Encryption Support Changes [page 64]SAP IQ includes OpenSSL encryption libraries that provide strong encryption for LinuxAMD64 Server, LinuxAMD32 Client, and Windows32 Client. Certicom encryption libraries are no longer supplied on these platforms. Encryption providers have not changed for jConnect, Open Client, and SAP Control Center components.

SAP IQ Implicitly Rebuilds Wide Columns [page 66]SAP IQ implicitly rebuilds CHAR,VARCHAR, BINARY, and VARBINARY columns wider than 255 characters, as well as all LONG VARCHAR and LONG BINARY columns in databases migrated to SAP IQ 16.0 SP 10 the first time a pre-16.0 non-RLV base table is opened for read-write access.

IS [NOT] DISTINCT FROM Search Condition Support [page 66]The ANSI SQL search conditions IS DISTINCT FROM and IS NOT DISTINCT FROM are now supported in SAP IQ 16.0 SP2.

Query Plan Changes [page 66]SAP IQ 16.0 SP2 introduces new query plan nodes.

SQL Statement Changes [page 68]Syntax changes for SAP IQ 16.0 SP2.

Stored Procedure Changes [page 69]Catalog stored procedure and system stored procedure changes for SAP IQ 16.0 SP2.

Table and View Changes [page 71]



SAP IQ 16.0 SP2 includes a new system table named ISYSIQMPXSERVERAGENT.

Deprecated Features [page 71]SAP IQ no longer supports these features. All deprecated features will be removed in a future release.

8.3.1 Database Option Changes

If you are updating from an earlier release of SAP IQ, the truncation behavior and maximum values of some database options has changed in release 16.0 SP2.

In this section:

CONVERSION_ERROR Option [page 63]Depending on the CONVERSION_ERROR option setting, SAP IQ reports data type conversion errors as either errors, or warnings.

JOIN_SIMPLIFICATION_THRESHOLD Option [page 63]The maximum allowed value of the JOIN_SIMPLIFICATION_THRESHOLD database option has changed to 24 in SAP IQ release 16.0 SP2.

MAX_JOIN_ENUMERATION Option [page 64]The maximum allowed value of the MAX_JOIN_ENUMERATION database option has changed to 32 in SAP IQ release 16.0 SP2.

8.3.1.1 CONVERSION_ERROR Option

Depending on the CONVERSION_ERROR option setting, SAP IQ reports data type conversion errors as either errors, or warnings.

In releases earlier than 16.0 SP2, SAP IQ silently truncated the results when converting from TINYINT, SMALLINT, INT, DOUBLE, DATE, DATETIME, TIME, BIGINT, UNSIGNED BIGINT, and UNSIGNED INT to CHAR or VARCHAR.

If a problem occurs when converting these data types in 16.0 SP2, SAP IQ logs the failure as an error or warning in the .iqmsg file. If the CONVERSION_ERROR option is ON, SAP IQ reports the problem as an error. If the CONVERSION_ERROR option is OFF, the problem is reported as a warning.


CONVERSION_ERROR Option [TSQL] in Reference: Statements and Options

8.3.1.2 JOIN_SIMPLIFICATION_THRESHOLD Option

The maximum allowed value of the JOIN_SIMPLIFICATION_THRESHOLD database option has changed to 24 in SAP IQ release 16.0 SP2.

In previous releases, the maximum allowed value was 64.




JOIN_SIMPLIFICATION_THRESHOLD Option in Reference: Statements and Options

8.3.1.3 MAX_JOIN_ENUMERATION Option

The maximum allowed value of the MAX_JOIN_ENUMERATION database option has changed to 32 in SAP IQ release 16.0 SP2.

In previous releases, the maximum allowed value was 64.


MAX_JOIN_ENUMERATION Option in Reference: Statements and Options

8.3.2 Encryption Support Changes

SAP IQ includes OpenSSL encryption libraries that provide strong encryption for LinuxAMD64 Server, LinuxAMD32 Client, and Windows32 Client. Certicom encryption libraries are no longer supplied on these platforms. Encryption providers have not changed for jConnect, Open Client, and SAP Control Center components.

Identity Files

OpenSSL FIPS supports AES encryption for the private key of an identity file (.id). New servers using the OpenSSL FIPS encryption module will not start when using an identity file that has its private key encrypted with 3DES.

You must reencrypt the identity file using AES. For example, to use an upgraded viewcert utility, enter:

viewcert -p -o new-file-name.id -op new-password -ip old-password old-file-name.id

The new and old passwords can be the same.

In sample server identity file rsaserver.id, and client identity file rsaclient.id, private keys are encrypted using AES rather than 3DES.

Versions of the database server that use the Certicom encryption module will not start when using an identity file that has its private key encrypted using AES. Trusted root certificate files specified using trusted_certificates do not need to be modified.

Self-Signed Certificates

Self-signed certificates must now have the Certificate Signing attribute set when using the identity encryption HTTPS option (-xs start_iq option). To determine if a certificate has the Certificate Signing attribute set,



use the viewcert utility and look for Certificate Signing in the Key Usage portion of the output. If the Certificate Signing attribute is not set, regenerate the certificates.

The Create Certificate utility (createcert) and View Certificate utility (viewcert) now use AES rather than 3DES encryption. In createcert, use the -3des option to create a 3DES-encrypted server identity file that can be used by both new and old database servers. New database servers running in FIPS mode cannot start using 3DES-encrypted certificates; however, if you are not running in FIPS mode, you can use 3DES-encrypted certificates. In the View Certificate utility, to use AES rather than 3DES encryption, specify the -p option to PEM-encode the output, and specify the -ip and -op options to set the password. In viewcert, use the -3des option to encrypt output and passwords using 3DES instead of AES.

FIPS Driver File

Previously, the 32-bit Windows database server loaded the FIPS driver file, dbfips16.dll, only when needed. Now, the 32-bit Windows database server loads dbfips16.dll at startup, and keeps it loaded for the life of the server. If loading dbfips16.dll fails, an error is returned only when an attempt is made to use FIPS encryption.

Libraries

Shared libraries sbgse2.dll and libsbgse2.so are no longer installed. SAP IQ software includes new shared libraries to deploy for FIPS encryption:

Platform Libraries

Windows 64-bit libeay32.dll, ssleay32.dll, msvcr100.dllWindows 32-bit libeay32.dll, ssleay32.dll, msvcr90.dllLinux libcrypto.so, libssl.so

On Windows, you must use the 64-bit libraries on a 64-bit system.

See Deprecated Features in this document.

See these topics in the SAP IQ 16.0 documentation:

● FIPS-certified encryption technology and FIPS Support in SAP IQ in Administration: User Management and Security

● @data iqsrv16 Server Option in Utility Guide

Related Information

Deprecated Features [page 71]



8.3.3 SAP IQ Implicitly Rebuilds Wide Columns

SAP IQ implicitly rebuilds CHAR,VARCHAR, BINARY, and VARBINARY columns wider than 255 characters, as well as all LONG VARCHAR and LONG BINARY columns in databases migrated to SAP IQ 16.0 SP 10 the first time a pre-16.0 non-RLV base table is opened for read-write access.

You can also explicitly rebuild wide columns using the sp_iqrebuildindexwide procedure. sp_iqrebuildindexwide can rebuild wide tables by table_name, table_owner, and level. Depending on the argument, this procedure can rebuild all pre-16.0 columns wider than 255 bytes, some or all tokenized FPs, VARCHAR/VARBINARY columns, and all fixed Flat FPs for specified tables in the database.

See sp_iqrebuildindexwide Procedure in Reference: Building Blocks, Tables, and Procedures.

8.3.4 IS [NOT] DISTINCT FROM Search Condition Support

The ANSI SQL search conditions IS DISTINCT FROM and IS NOT DISTINCT FROM are now supported in SAP IQ 16.0 SP2.


Search Conditions in Reference: Building Blocks, Tables, and Procedures

8.3.5 Query Plan Changes

SAP IQ 16.0 SP2 introduces new query plan nodes.

New Query Plan Nodes

Node Change Description

Projection Cache Dbspace Stats New node indicating:

HitRate Percentage of hit count in the total cache dbspace read count.Finds Total cache dbspace read count.Hits Hit count.Pageouts Count of pages written to the cache dbspace by the buffer manager.IOms Time, in milliseconds, the buffer manager took to read to and write from the cache dbspace.




Condition <n> Cache Dbspace Stats New node indicating:

HitRate Percentage of hit count in the total cache dbspace read count.Finds Total cache dbspace read count.Hits Hit count.Pageouts Count of pages written to the cache dbspace by the buffer manager.IOms Time, in milliseconds, the buffer manager took to read to and write from the cache dbspace.

New Query Details

The Query Details area of the plan contains these changes:

● Two new rows for TEXT index-based prefiltering: Adjunct Index, Adjunct constraint. These rows existed in previous releases for WD index-based pre-filtering only.

● New row showing the number of rows remaining after pre-filtering.● New row specifying the type of subquery: Distribute Sort Based Uncorrelated IN subquery.

CPU Utilization Bar Graph Changes

Increased resolution A new tooltip over the user (green) / system (red) CPU usage bar shows CPU utilization percentage. In a multiplex, the leader node query plan shows CPU utilization against the total number of available cores in the cluster.

Thread Utilization Bar Graph Changes

Increased resolution If the maximum number of threads is >100, then thread utilization shows as a percentage. A new tooltip over the thread utilization bar shows the utilization percentage.



8.3.6 SQL Statement Changes

Syntax changes for SAP IQ 16.0 SP2.


ALTER AGENT New statement to change the agent port, or agent user name and password for the SCC agent on the target server. You can now use the SCC agent to enable high availability for a multiplex.

See ALTER AGENT Statement in Reference: Statements and Options.

ALTER LS POLICY New root logical server policy option ENABLE_AUTOMATIC_FAILOVER, which defaults to OFF.

See ALTER LS POLICY Statement in Reference: Statements and Options.

CREATE AGENT New statement to specify agent port, agent user name, and password for the SCC agent on the target server. You can now use the SCC agent to enable high availability for a multiplex.

See CREATE AGENT Statement in Reference: Statements and Options.

CREATE DBSPACE New IQ CACHE STORE keyword for creating a cache dbspace.

See CREATE DBSPACE Statement in Reference: Statements and Options.

CREATE LS POLICY New root logical server policy option ENABLE_AUTOMATIC_FAILOVER, which defaults to OFF.

See CREATE LS POLICY Statement in Reference: Statements and Options.

DROP AGENT New statement to drop the SCC agent from the target server. You can now use the SCC agent to enable high availability for a multiplex.

See DROP AGENT Statement in Reference: Statements and Options.

LOAD TABLE The FROM clause now supports compressed client and server files only in gzip format. Any file with an extension ".gz" or ".gzip" is assumed to be a compressed file.

In releases earlier than 16.0 SP2, SAP IQ silently truncated the results when converting from TINYINT, SMALLINT, INT, DOUBLE, DATE, DATETIME, TIME, BIGINT, UNSIGNED BIGINT, or UNSIGNED INT to CHAR or VARCHAR.

If a problem occurs when converting these data types in 16.0 SP2, SAP IQ logs the failure as an error or warning in the .iqmsg file. If the CONVERSION_ERROR option is ON, SAP IQ reports the problem as an error. If the CONVERSION_ERROR option is OFF, the problem is reported as a warning.

SELECT SELECT now supports the FIRST, TOP, and LIMIT row limitation clauses in the top query block in a statement:

FIRST | TOP { ALL | <limit-expression> } [ START AT <startat-expression> ]

LIMIT { [ offset-expression, ] limit-expression | limit-expression OFFSET offset-expression }

See SELECT Statement in Reference: Statements and Options.



8.3.7 Stored Procedure Changes

Catalog stored procedure and system stored procedure changes for SAP IQ 16.0 SP2.


sp_iqcheckdb Changed procedure. sp_iqcheckdb now verifies the cache dbspace. The cache dbspace is new in this release.

● Check mode supports sp_iqcheckdb 'check cache'.

● Verify mode supports sp_iqcheckdb 'verify cache'.

● Allocation mode supports sp_iqcheckdb 'allocation cache'.

● Dropleaks mode supports sp_iqcheckdb 'dropleaks cache'.

See sp_iqcheckdb Procedure in Reference: Building Blocks, Tables, and Procedures.

sp_iqdbspace Changed procedure. Displays information about dbspaces of type CACHE. The cache dbspace is new in this release.

See sp_iqdbspace Procedure in Reference: Building Blocks, Tables, and Procedures.

sp_iqfile Changed procedure. Displays detailed information for direct-attached storage device dbfiles in the cache dbspace. The cache dbspace is new in this release.

See sp_iqdbfile Procedure in Reference: Building Blocks, Tables, and Procedures.

sp_iqindexrebuildwidedata sp_iqindexrebuildwidedata is deprecated and will be removed in a future release.




sp_iqrebuildindexwide New procedure. Explicitly rebuilds wide columns.

SAP IQ implicitly rebuilds CHAR,VARCHAR, BINARY, and VARBINARY columns wider than 255 characters, as well as all LONG VARCHAR and LONG BINARY columns in databases migrated to SAP IQ 16.0 SP 10 the first time a pre-16.0 non-RLV base table is opened for read-write access.

You can also explicitly rebuild wide columns using the sp_iqrebuildindexwide procedure. sp_iqrebuildindexwide can rebuild wide tables by table_name, table_owner, and level. Depending on the argument, this procedure can rebuild all pre-16.0 columns wider than 255 bytes, some or all tokenized FPs, VARCHAR/VARBINARY columns, and all fixed Flat FPs for specified tables in the database.

See sp_iqrebuildindexwide Procedure in Reference: Building Blocks, Tables, and Procedures.

sp_iqstatus Changed procedure. Displays memory usage information for direct-attached storage in the new cache dbspace.

See sp_iqstatus Procedure in Reference: Building Blocks, Tables, and Procedures.

sp_iqsysmon Behavior change. New parameters added: rlv and lma

See sp_iqsysmon in Reference: Building Blocks, Tables, and Procedures.

Related Information

Cache Dbspace for Direct-Attached Storage [page 60]



8.3.8 Table and View Changes

SAP IQ 16.0 SP2 includes a new system table named ISYSIQMPXSERVERAGENT.

New System Tables


ISYSIQMPXSERVERAGENT New table stores connection information for the IQ SCC Agent for each multiplex node, enabling high availability.

See SYSIQMPXSERVERAGENT System View in Reference: Building Blocks, Tables, and Procedures.

8.3.9 Deprecated Features

SAP IQ no longer supports these features. All deprecated features will be removed in a future release.

Elliptic Curve Encryption (ECC)

Support for ECC encryption has been removed. This change affects these features:

● The IsEccAvailable server property has been removed.● The -ec database server option no longer accepts ECC for the TLS_TYPE protocol option. The TLS_TYPE

protocol option has been removed from the documentation but is still supported by the software for backward compatibility.

● The ENCRYPTION connection parameter no longer accepts ECC for the TLS_TYPE argument. The TLS_TYPE argument has been removed from the documentation but is still supported for backward compatibility.

● The Certificate Creation utility (createcert) no longer accepts the -ec option and the -t option no longer accepts ecc for the encryption type.

8.4 SAP Control Center Changes

There have been changes to the SAP IQ plug-in for SAP Control Center (SCC) 3.3.

NoteThe name has changed from Sybase Control Center to SAP Control Center.



Brief descriptions of new and enhanced features:

Table 3: SAP Control Center Changes

New/Enhanced Feature Description

Configuration File Editor Server configuration option updates – new options have been added to the Configuration File Editor for configuring multiplex and simplex servers:

Large Memory maximum amount of memory, in megabytes, that SAP IQ can dynamically request from the operating system for temporary use.RLV Memory amount of memory, in megabytes, available to the RLV Store.Temporary Files Directory directory where temporary files are stored.Request Log Copies number of request log file copies to retain.Message Log Size maximum size of the message log, in megabytes.Message Log Archives number of old message logs maintained by the server.

Failover Wizard The Failover Wizard now detects when the coordinator and designated failover node are both down, and lets you choose new nodes for each to enable failover.

Multiplex Server Properties You can now set multiplex server properties to enable high availability.

RLV Statistics You can now monitor RLV memory usage and merge history statistics in a simplex environment. RLV statistics are also available in SAP IQ data collections.

Database Upgrade Wizard You can now upgrade a simplex or multiplex database in SAP Control Center. This functionality is currently limited to upgrading a 15.3 or 15.4 database to the current 16.0 version.

Cache Dbspace Use the cache dbspace to add direct-attached storage devices, such as high-performance solid state disks (SSDs), to your multiplex nodes or simplex server.



9 Support Package 1

No new features were introduced in SAP IQ 16.0 SP 1. If you are updating from an earlier release or support package, you must run the ALTER DATABASE UPGRADE command.



10 Initial Release

New features, performance improvements, behavior changes, administration tool changes, and documentation collection changes were introduced in SAP IQ 16.0. Some features from earlier releases were deprecated or discontinued. If you are updating from a 15.x release, you must run the ALTER DATABASE UPGRADE command.

In this section:

Read This First: Helpful Hints Before You Start Using SAP IQ 16.0 [page 75]Although the SAP® IQ 16 What's New in SAP IQ 16.0 describes all new SAP IQ functionality, some features may require additional action on your part to take advantage of the new architecture introduced in the initial 16.0 version.

New Features [page 79]New features were introduced in SAP IQ 16.0.

Performance Improvements [page 99]Distributed query processing and micro query performance has improved in SAP IQ 16.0. The new Cache Ejection feature improves performance by eliminating unnecessary cache page reads.

Discontinued Features [page 101]If you are upgrading from an earlier release of SAP IQ 16.0, note the features and functionality discontinued in this release. Discontinued features and functionality are not supported by SAP.

Deprecated Features [page 109]If you are upgrading from an earlier release of SAP IQ, note the features and functionality deprecated in release 16.0. Deprecated features and functionality are supported for backward compatibility, but are not recommended. Support will be removed in an upcoming release.

Behavior Changes [page 112]Several behavior changes have been introduced in SAP IQ 16.0.

Administration Tool Changes [page 150]Sybase Central is replaced by SAP Control Center (SCC).

Documentation Collection Changes [page 154]The SAP IQ 16.0 documentation collection contains new documentation, redesigned manuals, and retitled manuals. This topic helps you locate content in the 16.0 collection.


What's New in SAP IQ 16.0Initial Release

10.1 Read This First: Helpful Hints Before You Start Using SAP IQ 16.0

Although the SAP® IQ 16 What's New in SAP IQ 16.0 describes all new SAP IQ functionality, some features may require additional action on your part to take advantage of the new architecture introduced in the initial 16.0 version.

Load Performance Configuration Issues

Customers upgrading from a previous release, for example, may need to change some initial compatibility options or rebuild wide columns to accommodate different datatypes. The new load engine provides better performance, but requires changes to the default memory allocation to use all available hardware resources efficiently.

This topic highlights migration issues and features which impact load performance. See the appropriate topics in the SAP IQ core documentation set for details. Migration (Linux and UNIX) and Migration (Windows) are new administration manuals in 16.0, describing the steps for upgrading your database, steps to install maintenance releases, and information on upgrading to the role-based security model. Administration: Load Management is also new in 16.0, describing data import and export procedures.

NBit

Continuous NBit dictionary compression replaces 1, 2, and 3 byte dictionary compression as the default column storage mechanism in 16.0. All datatypes except LOB (character and binary) and BIT datatypes can be NBit columns.

The IQ UNIQUE column constraint determines whether a column loads as Flat FP or NBit FP. An IQ UNIQUE n value set to 0 loads the column as Flat FP. An n value greater than 0 but less than the FP_NBIT_AUTOSIZE_LIMIT creates a NBit column initially sized to <n>. Columns without an IQ UNIQUE constraint implicitly load as NBit up to the auto-size limit.

Using IQ UNIQUE with an <n> value less than the auto-size limit is not necessary. The load engine automatically sizes all low or medium cardinality columns as NBit. Use IQ UNIQUE in cases where you want to load the column as Flat FP or when you want to load a column as NBit when the number of distinct values exceeds the value of the FP_NBIT_AUTOSIZE_LIMIT option.

Loads and Large Memory

Large memory represents the maximum amount of memory that SAP IQ can dynamically request from the OS for temporary use. Because some load operations may require more large memory than the 2GB default provides, adjust the startup options that control large and cache memory allocation based on the total amount of available physical memory.



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 128GB of total available physical memory, you would allocate 100GB (approximately 80% of the 128GB total) to SAP IQ processes. Following the general rule, you would set the -iqlm, -iqtc, and -iqmc parameters to 33GB each.

See -iqlm iqsrv16 Server Option and -iqmc iqsrv16 Server Option in the Utility Guide.

Index Changes

Changes to FP and HG indexes take advantage of the new column compression mechanism and improve load performance.

Index Description

New Fast Projection (FP) Indexes Take advantage of the new continuous NBit dictionary compression, which replaces 1, 2, and 3 byte dictionary compression. FP(1), FP(2), and FP(3) indexes roll over to NBit(8), NBit(16), and NBit(24) respectively.

If FP_NBIT_IQ15_COMPATIBILITY='OFF', IQ UNIQUE constraints applied to the column determine whether the column loads as Flat FP or NBit.

See Fast Projection ( FP ) Index in Administration: Database.

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. This option is ON in all new 16.0 databases and all 16.0 databases migrated from 15.x. To take advantage of the new structure, set this option to OFF. See CREATE_HG_WITH_EXACT_DISTINCTS Option in Reference: Statements and Options.

Use sp_iqrebuildindex to convert non-tired HG indexes to tiered HG and vice-versa.

Stored Procedures

New stored procedures return information about column indexes and constraints.




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.

See sp_iqindexmetadata Procedure in Reference: Building Blocks, Tables, and Procedures.

sp_iqcolumnmetadata Returns FP index metadata for one or more user tables or all tables in the database.

See sp_iqcolumnmetadata Procedure in Reference: Building Blocks, Tables, and Procedures.

sp_iqindexrebuildwidedata Identifies wide columns that you must rebuild before they are available for read/write activities. Output includes statements that you can use with sp_iqrebuildindex to rebuild the columns.

See sp_iqindexrebuildwidedata Procedure in Reference: Building Blocks, Tables, and Procedures.

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.

See sp_iqrebuildindex Procedure in Reference: Building Blocks, Tables, and Procedures.

Database Options

Some database options are not enabled to take advantage of 16.0 features. Maintaining limited compatibility after a database upgrade provides some flexibility to transition existing applications.



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.0 databases upgraded from 15.x and OFF in all newly created 16.0 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.0.

● 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.0 databases upgraded from 15.x and all newly created 16.0 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.0 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.0 databases upgraded from 15.x. REVERT_TO_V15_OPTIMIZER='OFF' by default in all newly created SAP IQ 16.0 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.0.

Related Information

NBit Dictionary Compression [page 88]Discontinued Indexes [page 104]Database Option Changes [page 120]Stored Procedure Changes [page 140]Utility Option Changes [page 149]Hash Partitioning [page 91]Backward Compatibility: Changes to Default Behavior [page 113]Backward Compatibility: Migration Considerations [page 116]



10.2 New Features

New features were introduced in SAP IQ 16.0.

In this section:

SAP Control Center [page 80]SAP Control Center (SCC) is a Web-based administrative console that replaces Sybase Central. SAP Control Center was initially released with the name "Sybase Control Center".

Concealment of Sensitive Information in Output Requests [page 81]Sensitive information - passwords and encryption keys - is now hidden when statements are printed to request level logs, are logged by diagnostic tracing, or when expressions containing sensitive information are used as column names.

Connection Blocking [page 82]Connection blocking blocks a statement until a server write-lock becomes available. The new connection blocking behavior enables competing write-transactions to establish their snapshot versions more efficiently and collaboratively, minimizing lock contention during table writes to the IQ main store and RLV store.

Global Transaction Resiliency [page 83]DML read-write transactions on multiplex writer nodes now survive temporary communication failures between coordinator and writer nodes and temporary failure of the coordinator due to server failure, shutdown or failover. Prior to SAP IQ 16.0 such failures guaranteed failure of the global transaction on the writer node and required the user to roll back the entire transaction.

Login Redirection [page 85]SAP IQ 16.0 provides load balancing when a user tries to log into an overloaded node by redirecting the attempted login to a node that is less loaded in the same logical server.

RLV Data Store for Write-Optimized Storage [page 85]Use the new row-level versioning (RLV) data store in your simplex database to perform row-level updates, inserts, and deletes, in real-time. When a table is registered for storage in the RLV data store, multiple users can write to different rows of the same table concurrently.

Scale-Up and Scale-Out Performance Features [page 86]Scale up features take advantage of multiple cores and high parallelism in a single servers to provide high load and query performance. Multiplex and logical servers scale-out to multiple servers to improve query performance.

Security Management [page 92]New features pertaining to security, user management, and LDAP user authentication.

Shared System Temporary Store [page 97]A multiplex configuration with shared temporary storage can use the IQ_SHARED_TEMP dbspace as a shared system temporary store instead of requiring a separate local store for each secondary server. The shared system temporary store simplifies multiplex configuration, improves performance, and supports distributed query processing.

Table Partitioning [page 98]Table partitioning can improve performance by dividing large tables into smaller, more manageable storage objects. SAP IQ 16.0 now supports range, hash, and hash-range partitioning schemes.

System Secure Feature Keys [page 99]



The system secure feature key now allows you to create customized secure feature keys that are assigned to a specific users, limiting users' access to only the features secured by the administrator for that key.

10.2.1 SAP Control Center

SAP Control Center (SCC) is a Web-based administrative console that replaces Sybase Central. SAP Control Center was initially released with the name "Sybase Control Center".

Sybase Central is not supported in SAP IQ 16.0 and is not available as an installation option. SAP Control Center replaces Sybase Central.

SAP Control Center provides a single comprehensive Web administration console for managing real-time performance, status, and availability monitoring of large-scale enterprise servers. SAP Control Center combines a rich client administrative console, agents, common services, and tools for managing database products. It provides historical monitoring, threshold-based alerts and notifications, and intelligent tools for identifying performance and usage trends. SAP Control Center architecture includes an SCC server and SCC agent. A single SCC server can monitor up to 100 SAP IQ servers.

Use SAP Control Center to administer SAP IQ:

● Simplex servers● Multiplex servers● Logical servers● Remote servers● External logins● Databases● Tables● Views● Materialized views● Domains● Text configuration objects● Text indexes● Sequence generators● Spatial support● Security and user management● Dbspaces● DB Files● Events● External Environments● Funtions● Procedures● Web Services

NoteSAP Control Centerfor SAP IQ (the IQMAP 3.2.7 plugin for SCC 3.2.8) is included with the SAP IQ installer for these platforms:



● Win64● Solaris Sparc● Solaris x64● LinuxAMD64

SAP Control Center for SAP IQ is not supported on:

● AIX64● HP64● IBM LinuxPPC64

To install SAP Control Center for SAP IQ on Win32 and LinuxAMD32, you must install SCC 3.2.8 and IQMAP 3.2.7 via the SCC 3.2.8 DVD.

Related Information

SAP Control Center Changes [page 151]Discontinued Tools and Utilities [page 107]

10.2.2 Concealment of Sensitive Information in Output Requests

Sensitive information - passwords and encryption keys - is now hidden when statements are printed to request level logs, are logged by diagnostic tracing, or when expressions containing sensitive information are used as column names.

Additionally, output of the REWRITE function, connection_property( 'LastStatement' ) and any statements recorded in event tracing is sanitized. Any expression that represents a password, key, or sensitive data is hidden.

For example, encrypt( 'a', 'abc', 'AES') now outputs as encrypt( '***', '***', AES).

The sensitive parameters in the built-in procedures ENCRYPT and DECRYPT are now hidden.

Sensitive parameters are now hidden in these system procedures:

● sa_verify_password● sp_password● xp_startmail● xp_startsmtp

Passwords and keys are now hidden in these statements:

● GRANT CONNECT● CREATE DATABASE● START DATABASE● DROP DATABASE● CREATE EXTERNLOGIN



● SET TEMPORARY OPTION secure_feature_key = <key>

10.2.3 Connection Blocking

Connection blocking blocks a statement until a server write-lock becomes available. The new connection blocking behavior enables competing write-transactions to establish their snapshot versions more efficiently and collaboratively, minimizing lock contention during table writes to the IQ main store and RLV store.

In earlier releases, when several clients attempted to perform write-operations against the same table, the server used a queuing mechanism to queue up waiting write requests while the table was locked by the write-transaction. Client applications used retry logic to send write-lock requests until the table was available for locking. However, the transaction snapshot version was created at transaction creation time, prior to obtaining the table write lock. It was possible, therefore, for a competing write-transaction to obtain the lock when the server put your transaction to sleep. In this scenario, when the server woke your transaction, the server noted that your version was older than the transaction committed by the other user, causing a future-version error and an inability to write.

Connection blocking is the mechanism where the server puts the connection to sleep and wakes it when the other connection releases the table write- lock. When you enable connection blocking, any transaction attempting to obtain a lock conflicting with an existing lock held by another transaction waits until either the conflicting lock is released, or until the blocking timeout value is reached. If the lock isn't released when the blocking timeout value is reached, then your waiting transaction receives an error.

When you disable connection blocking, your connection attempting to obtain the lock held by another connection receives an error immediately. The server rolls back the current operation.

Two database options support connection blocking:

BLOCKING database option Controls the behavior in response to locking conflicts. If the blocking option is set to ON, any transaction attempting to obtain a lock that conflicts with an existing lock held by another transaction waits until every conflicting lock is released or until the blocking timeout value is reached. If the lock is not released within the blocking timeout period (in milliseconds), then an error is returned for the waiting transaction.BLOCKING_TIMEOUT database option Controls how long (in milliseconds) a transaction waits to obtain a lock.

In release 16.0, transaction snapshot versioning is delayed until your transaction obtains the table write-lock. This guarantees your transaction is blocked if another writer exists. Delayed transaction snapshot versioning is enabled by default, and requires no configuration.


● Administration: Database > Manage Transactions and Versioning > Transaction Blocking● Administration: In-Memory Row-Level Versioning > Manage Blocking in the RLV Store● Reference: Statements and Options > Database Options > Alphabetical List of Options > BLOCKING Option● Reference: Statements and Options > Database Options > Alphabetical List of Options >

BLOCKING_TIMEOUT Option



Related Information

Database Option Changes [page 120]RLV Data Store for Write-Optimized Storage [page 85]

10.2.4 Global Transaction Resiliency

DML read-write transactions on multiplex writer nodes now survive temporary communication failures between coordinator and writer nodes and temporary failure of the coordinator due to server failure, shutdown or failover. Prior to SAP IQ 16.0 such failures guaranteed failure of the global transaction on the writer node and required the user to roll back the entire transaction.

When a user connects to a writer node and executes read-write DML commands against shared objects, the writer starts a global transaction on the coordinator. The transaction starts on an internal internode communication (INC) connection from writer to coordinator.

For example, INSERT or LOAD commands on shared database objects are global transactions. If a failure occurs, the global transaction and corresponding INC connection is suspended.

If the temporary failure resolves within a user-defined timeout period, the global transaction continues as if there was no failure. The user can commit, roll back, or continue the transaction. Use the MPX_LIVENESS_TIMEOUT option to set the timeout period, which defaults to an hour (default value 3600).

If the failure persists longer than the user-defined timeout period, the global transaction cannot resume and the user must roll back the whole transaction.

If there is a DML command actively executing while the failure happens, the command behavior depends on the user-defined timeout and the command type.

To check connection status (active or suspended), use the sp_iqconnection system procedure on a writer node or sp_iqmpxsuspendedconninfo system procedure on a coordinator. Run sp_iqmpxincstatistics for a snapshot of the aggregate statistics of the INC status since server startup.

See these new and updated topics in the SAP IQ 16.0 documentation:

● Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures

● Reference: Statements and Options > Database Options > Alphabetical List of Options > MPX_LIVENESS_TIMEOUT Option

● Administration: Multiplex > Manage Transactions > Troubleshoot Transactions

This feature does not affect transactions initiated on the coordinator.

In this section:

Communication Failure or Coordinator Failure and Restart During Global Transaction [page 84]If internode communication (INC) fails or the coordinator fails or is shut down during a writer-initiated global transaction, transactions suspend and resume automatically if the INC is restored before a user-specified timeout expires.



10.2.4.1 Communication Failure or Coordinator Failure and Restart During Global Transaction

If internode communication (INC) fails or the coordinator fails or is shut down during a writer-initiated global transaction, transactions suspend and resume automatically if the INC is restored before a user-specified timeout expires.

Delays in command execution may indicate INC suspend and resume operations. If INC is interrupted, the coordinator suspends a global transaction for an hour. The transaction resumes successfully as soon as INC is restored. If the timeout value elapses, the transaction fails. Set the MPX_LIVENESS_TIMEOUT database option to change the timeout period.

The following cases describe the behavior of writer nodes if the communication to the coordinator resumes before timeout.

Writer Command Status Command Behavior Result

Actively executing command Command suspends, except for ROLLBACK, which executes locally on writer.

Command succeeds.

New DML command Command suspends and resumes, except for ROLLBACK and ROLLBACK TO SAVEPOINT, which execute locally on the writer.

If communication is restored, resumed commands succeed.

The following cases describe the behavior of writer nodes if the communication failure exceeds the timeout period.

Writer Command Status Command Behavior Result

Suspended DML command on connection

The suspended command fails and returns an error about the non-recoverable state of the transaction.

You must roll back the transaction. Rollback happens automatically if the suspended command is COMMIT or ROLLBACK to SAVEPOINT.

No suspended DML command on connection

The next command returns an error about the non-recoverable state of the transaction.

You must roll back the transaction.

To check connection status, use the sp_iqconnection system procedure on a writer node or the sp_iqmpxsuspendedconninfo system procedure on a coordinator.

Run sp_iqmpxincstatistics for a snapshot of the aggregate statistics of the INC status since server startup.

NoteIf a global transaction initiated from a writer node modifies both global and local persistent objects (for example, an SA base table and an IQ base table), and the coordinator fails during commit, global object changes may be committed while local object changes are lost. This is consistent with a scenario that updates both local and proxy tables in the same transaction, where “best effort” is used to commit both local and global components of a transaction.



10.2.5 Login Redirection

SAP IQ 16.0 provides load balancing when a user tries to log into an overloaded node by redirecting the attempted login to a node that is less loaded in the same logical server.

Use the LOGIN_REDIRECTION logical server policy to enable redirection. You can now define your own logical server policies and assign them to one or more logical servers to specify server behavior. Connection parameters, logical server policies, login policies, and user privileges determine the nodes available to a particular user for processing.

For example, the following creates a logical server policy lsp1 where login redirection is enabled and associates the new policy with logical server ls1:

CREATE LS POLICY lsp1 LOGIN_REDIRECTION=ON ALTER LOGICAL SERVER ls1 POLICY lsp1

To specify the target logical server, connect using the LOGICALSERVER parameter. To specify the target server role instead, connect with the NODETYPE parameter. For example, to connect an application executing INSERT or UPDATE statements to a member node with the writer role, use NODETYPE=WRITER.

You can specify the current coordinator without knowing the host name by using the built-in logical server, COORDINATOR.

If login redirection is enabled and a connection is allowed, SAP IQ redirects connections when:

● The initial connection node is not a member of the target logical server.● The initial connection node is a member of the target logical server but has a role other than that

requested.● The initial node is a member of the target logical server and has the requested role, but the user has

reached the limit of maximum connections on the current logical server member node.

If the initial request fails, SAP IQ returns a list of available nodes to the user. If available member nodes of the requested role are unavailable, the connection fails.

Related Information

Connection Changes [page 118]Logical Server Policy Option Changes [page 127]SQL Statement Changes [page 133]

10.2.6 RLV Data Store for Write-Optimized Storage

Use the new row-level versioning (RLV) data store in your simplex database to perform row-level updates, inserts, and deletes, in real-time. When a table is registered for storage in the RLV data store, multiple users can write to different rows of the same table concurrently.

For information on architecture, configuration, blocking, locking, monitoring, merging, and troubleshooting row-level versioning, see the new manual Administration: In-Memory Row-Level Versioning.



SAP IQ 16.0 introduces a new data store:

RLV Store The in-memory data store optimized for high-performance row-level updates. The RLV store acts as a staging area for write events. If a table is enabled for row-level versioning, then all LOAD TABLE, INSERT, UPDATE, and DELETE events write directly to the RLV store. In-memory data in the RLV store is periodically merged into the IQ main store. You can set parameters for automatic merges, and you can merge on-demand.

The IQ main store is optimized for high performance queries, rather than table writes. The RLV store adds high-performance write capability to your database. You can use row-level versioning in conjunction with your existing insert mechanisms such as bulk loading. For example, your applications can make real-time updates during business hours, while overnight a bulk load operation bypasses the RLV store and loads updated data directly to the IQ main store.

You do not require a separate license to use the RLV store. However, row-level versioning requires:

● A simplex database● A single RLV dbspace● You have enabled row-level snapshot versioning● You have enabled RLV storage on the specified table, or on all base tables

If a table is RLV-enabled, SAP IQ table DDL behavior is unchanged. DDL events on a table (adding a column, for example) require an exclusive lock on that table.


● Administration: In-Memory Row-Level Versioning > About In-Memory Row-Level Versioning● Administration: In-Memory Row-Level Versioning > Appendix: SQL Reference

Related Information

Database Option Changes [page 120]Table and View Changes [page 146]SQL Statement Changes [page 133]Connection Blocking [page 82]

10.2.7 Scale-Up and Scale-Out Performance Features

Scale up features take advantage of multiple cores and high parallelism in a single servers to provide high load and query performance. Multiplex and logical servers scale-out to multiple servers to improve query performance.

In this section:

Fully Parallel Bulk Load [page 87]New load engine effectively scales data loads to make use of all additional hardware.

Tiered High Group Index Structure [page 87]New tiered High Group (HG) index structure decouples load performance from HG index size.



NBit Dictionary Compression [page 88]Continuous NBit dictionary compression replaces 1, 2, 3 byte dictionary compression in the initial 16.0 version. All datatypes except LOB (character and binary) and BIT datatypes may be NBit columns.

Hash Partitioning [page 91]Hash Partitioning reduces resource usage and internode communication.

Data Affinity [page 91]Data affinity accesses cached data to boost query performance in multiplex servers.

Non-Partitioned Query Scale-Out [page 91]For non-partitioned data, new JOIN and GROUP BY algorithms reduce the amount of intermediate results that are exchanged during distributed query execution.

Cache Ejection [page 91]Caches are handled more efficiently with multiple writers in SAP IQ Multiplex.

Login Redirection [page 92]Logical servers can redirect connections at login time.

LDAPUA [page 92]LDAP user authentication (LDAPUA) allows client applications to send user names and passwords to SAP IQ for authentication by an LDAP server.

10.2.7.1 Fully Parallel Bulk Load

New load engine effectively scales data loads to make use of all additional hardware.

SAP IQ 16.0 uses all available cores in the box for better throughput, regardless of the number of columns you load. The higher number of cores, the better load performance you get. Due to high parallelism, you may encounter larger demands on your I/O system and you may need to increase your storage bandwidth to realize improvements.

10.2.7.2 Tiered High Group Index Structure

New tiered High Group (HG) index structure decouples load performance from HG index size.

In SAP IQ 15, 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.




See these topics in the SAP IQ documentation:

Database Migration

Migration > Database UpgradesDatabase Administration

Administration: Database > Index Data > Index Types Comparison > High_Group (HG) IndexDatabase Options

Reference: Statements and Options > Database Options > Alphabetical List of Options >CREATE_HG_WITH_EXACT_DISTINCTSStored Procedures

● Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqrebuildindex Procedure

● Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqindexmetadata Procedure

10.2.7.3 NBit Dictionary Compression

Continuous NBit dictionary compression replaces 1, 2, 3 byte dictionary compression in the initial 16.0 version. All datatypes except LOB (character and binary) and BIT datatypes may be NBit columns.

NBit dictionary compression provides more efficient compression and greater performance than 1, 2, 3 byte dictionary compression. The IQ UNIQUE column constraint explicitly determines whether the column loads as Flat FP or NBit FP. An IQ UNIQUE <n> value set to 0 specifies a Flat FP. An <n> value greater than 0 but less than FP_NBIT_AUTOSIZE_LIMIT creates a NBit column initially sized to <n>.

Columns without an IQ UNIQUE constraint implicitly load as NBit up to the limits defined in the FP_NBIT_AUTOSIZE_LIMIT. Use IQ UNIQUE in cases where you want to load the column as Flat FP or when you want to load a column as NBit when the number of distinct values exceeds the auto-size limit.

NoteBIT, BLOB,and CLOB data types do not support NBit dictionary compression. If FP_NBIT_IQ15_COMPATIBILITY=’OFF’, a non-zero IQ UNIQUE column specification in a CREATE TABLE or ALTER TABLE statement that includes these data types returns an error.

NBIT Levels and corresponding IQ UNIQUE cutoffs

SAP IQ 15 supported three levels of tokenization: FP(1), FP(2) and FP(3). SAP IQ 16.0 supports 31 possible NBit levels.



NBit Value IQ UNIQUE

1 2

2 4

3 8

4 16

5 32

6 64

7 128

8 256 1

9 512

10 1024

11 2048

12 4096

13 8192

14 16384

15 32768

16 65536 2

17 131972

18 262144

19 524288

20 1048576

21 2097152

22 4194304

23 8388608

24 16777216 3

25 33554432

26 67108864



NBit Value IQ UNIQUE

27 134217728

28 268435456

29 536870912

30 1073741824

31 2147483647

1 Equivalent to FP(1)




See these topics in the SAP IQ documentation:

Database Migration

Migration > Database Upgrades

Database Administration

Administration: Database > Index Data > Index Types Comparison > Fast Projection (FP) Index

Statements

● Reference: Statements and Options > SQL Statements > CREATE TABLE Statement● Reference: Statements and Options > SQL Statements > ALTER TABLE Statement

Database Options

● Reference: Statements and Options > Database Options > Alphabetical List of Options > FP_NBIT_AUTOSIZE_LIMIT

● Reference: Statements and Options > Database Options > Alphabetical List of Options > FP_NBIT_ENFORCE_LIMITS

● Reference: Statements and Options > Database Options > Alphabetical List of Options > FP_NBIT_IQ15_COMPATIBILITY

● Reference: Statements and Options > Database Options > Alphabetical List of Options > FP_NBIT_LOOKUP_MB

● Reference: Statements and Options > Database Options > Alphabetical List of Options > FP_NBIT_ROLLOVER_MAX_MB

Stored Procedures

● Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqrebuildindex Procedure

● Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqcardinality_analysis Procedure



● Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqindexmetadata Procedure

10.2.7.4 Hash Partitioning

Hash Partitioning reduces resource usage and internode communication.

To take advantage of hash partitioning, you need to create a new hash partitioned table, choose an appropriate high cardinality column as a partitioning key, and reload the data from an existing table into the newly created hash partitioned table. With hash-partitioning, queries on a large number of rows (of the order of 1 billion rows) use less temp space and perform better with a large number of cores. In a multiplex environment, hash-partitioning significantly reduces shared temp bandwidth requirements, allowing for better scale-out across multiple servers.

10.2.7.5 Data Affinity

Data affinity accesses cached data to boost query performance in multiplex servers.

For optimum scale-out performance, SAP recommends that you have 4-8 multiplex nodes with total memory across the cluster that can hold most of the working set data for the queries. Affinity is automatically enabled for multiplex databases. No user intervention or maintenance is required.

10.2.7.6 Non-Partitioned Query Scale-Out

For non-partitioned data, new JOIN and GROUP BY algorithms reduce the amount of intermediate results that are exchanged during distributed query execution.

These new features improve query performance in cases limited by shared temp or interconnect bandwidth. The optimizer automatically selects these new operators on a cost basis. No user intervention is required but some limitations apply:

● The optimizer has a limited cost mode for the new algorithms. It may not use them in all cases where they may provide benefit or may use them sub-optimal situations

● New grouping algorithms are limited to non-null data

10.2.7.7 Cache Ejection

Caches are handled more efficiently with multiple writers in SAP IQ Multiplex.

Each server in the Multiplex now has to re-read only a fraction of pages to determine what data pages have changed since the last read. Only the data pages that have changed are re-read and others are just read from the cache. This reduces I/O and thereby gains in overall load and queries.



10.2.7.8 Login Redirection

Logical servers can redirect connections at login time.

Login Redirection lets you dynamically change the logical server group by adding or removing multiplex nodes to rebalance the workload as connections are redirected to servers in the logical server group at any given time. All redirection logic is contained in the client libraries and the server. There is no need to update existing applications. Applications will try to connect to any server in the multiplex, and if login redirection is turned on for the login policy in question, the connection will be redirected to the appropriate node in the logical server group.

10.2.7.9 LDAPUA

LDAP user authentication (LDAPUA) allows client applications to send user names and passwords to SAP IQ for authentication by an LDAP server.

Authentication using the LDAP server allows you to use server-wide passwords instead of SAP IQ or application-specific passwords. This feature requires an enterprise-wide, central LDAP server.

10.2.8 Security Management

New features pertaining to security, user management, and LDAP user authentication.

In this section:

Role-Based Security [page 93]Role-based security, also called role-based access control (RBAC), allows the breakdown of privileged operations into fine-grained sets that can be individually granted to users.

User Management [page 95]Enhancements to user management now support dual control password change and the elimination of an potential lockdown scenario due to failed login attempts.

SAP IQ LDAP Authentication [page 96]SAP IQ can be integrated into any existing enterprise-wide directory access framework based on Lightweight Directory Access Protocol (LDAP), a widely accepted international standard.

Transport Layer Security for Multiplex [page 97]SAP IQ supports encrypted communication connections on multiplex.

Running Privileged System Procedures [page 97]SAP IQ provides increased security when running privileged system procedures.



10.2.8.1 Role-Based Security

Role-based security, also called role-based access control (RBAC), allows the breakdown of privileged operations into fine-grained sets that can be individually granted to users.

It provides granular access control in a flexible and easy to use manner and enforces the separation of duties principle by making it possible to assign disjointed sets of privileged tasks to separate autonomous entities. Finally, it allows full control over which system privileges and roles can be granted to other entities.

Role-based security is based on the concepts of system and object-level privileges and roles. A privilege controls the ability to perform a specific task and can be granted directly to a user. A role is an entity to which system privileges and object-level privileges can be associated. Granting system and object-level privileges to a role and then granting the role to users allows users to inherit the privileges of the role. You can also grant roles to other roles to create a hierarchical security structure.

Each system privilege or role has designated administrators whose responsibility it is to control which users are granted the system privilege or role, which users can themselves act as administrators of the system privilege or role, or which users can do both.

See these topics:

● Administration: User Management and Security > Security Management● Administration: User Management and Security > Security Management > Plan and Implement Role-Based

Security● Administration: User Management and Security > Security Management > Roles● Administration: User Management and Security > Security Management > Privileges● Administration: User Management and Security > Security Management > Users

In this section:

Ability to Impersonate Another User [page 93]The SET USER system privilege allows a user to assume the exact roles and system privileges of (impersonate) another user. Once begun, impersonation of another user remains in effect until it is terminated or the current session ends.

Minimum Number of Role Administrators [page 94]The ability to manage roles is a privilege granted to select users and roles.

10.2.8.1.1 Ability to Impersonate Another User

The SET USER system privilege allows a user to assume the exact roles and system privileges of (impersonate) another user. Once begun, impersonation of another user remains in effect until it is terminated or the current session ends.

To grant the SET USER system privilege:

● Each grantee (user doing the impersonating) must be an existing user or role.● Each target user (user being impersonated) must be an existing user with a login password.● The grantor (user granting the system privilege) must have administrative rights to the SET USER system

privilege.



● Each grantee must have been granted at least all roles and system privileges with same or higher administrative options as the target user.

NoteFailure to meet the final condition does not prevent the system privilege from being granted to the user; it does, however, prevent the user from executing the SETUSER command to successfully impersonate another user.

NoteThis functionality is not currently implemented in SAP IQ Cockpit.

See these topics:

● Administration: User Management and Security > Security Management > Impersonation

Related Information

SQL Statement Changes [page 133]

10.2.8.1.2 Minimum Number of Role Administrators

The ability to manage roles is a privilege granted to select users and roles.

Through the process of dropping roles and users or revoking roles and system privileges, you might have a scenario where there are no users or roles left with sufficient system privilege to manage the remaining roles. This configurable option ensures that no role can be revoked or dropped if doing so reduces the remaining number of role administrators below a set value.

See these topics:

● Administration: User Management and Security > Security Management > Roles > User-Defined Roles > Role and Global Role Administrators

Related Information

Database Option Changes [page 120]



10.2.8.2 User Management

Enhancements to user management now support dual control password change and the elimination of an potential lockdown scenario due to failed login attempts.

In this section:

Dual Control of User Password Management [page 95]The dual control option provides an added level of security for users resetting passwords for other users. It ensures that no single user knows or controls the password of another user.

Automatic Unlocking of User Accounts [page 95]User accounts are locked if users exceed the maximum failed login attempts limit. Once locked, the account must be manually unlocked by a user granted the MANAGE ANY USER system privilege.

10.2.8.2.1 Dual Control of User Password Management

The dual control option provides an added level of security for users resetting passwords for other users. It ensures that no single user knows or controls the password of another user.

This option requires that two users participate when resetting the password of a user other than themselves. Each user defines a portion of the password. The reset password then becomes the union of the two passwords.

NoteThis functionality is not currently implemented in SAP Control Center.

See these topics:

● Administration: User Management and Security > Security Management > Manage Passwords

Related Information

SQL Statement Changes [page 133]Login Policy Option Changes [page 128]

10.2.8.2.2 Automatic Unlocking of User Accounts

User accounts are locked if users exceed the maximum failed login attempts limit. Once locked, the account must be manually unlocked by a user granted the MANAGE ANY USER system privilege.

However, since users with the MANAGE ANY USER system privilege are also subject to lockdown due to failed login attempts, you might have a scenario whereby all users with the necessary system privilege to unlock



accounts are themselves locked out. The automatic unlocking of user accounts feature prevents this lock-down scenario from occurring.

See these topics :

● Administration: User Management and Security > Security Management > Login Policies

Related Information

Login Policy Option Changes [page 128]

10.2.8.3 SAP IQ LDAP Authentication

SAP IQ can be integrated into any existing enterprise-wide directory access framework based on Lightweight Directory Access Protocol (LDAP), a widely accepted international standard.

Integration with LDAP user authentication supports:

● Authentication using searched distinguished name (DN)● Failover to a secondary LDAP server for high availability● Automatic failback to previously failed servers● Integration with OpenLDAP third-party libraries● Secure communication with LDAP servers● Efficient design for frequent, short-lived connections● Extensibility to multiple domains and multiple LDAP servers

See these topics in the SAP IQ 16.0 Administration: User Management and Security documentation:

● See Administration: User Management and Security > Advanced Security Options in SAP IQ > LDAP Authentication Support in SAP IQ

Related Information

Database Option Changes [page 120]Login Policy Option Changes [page 128]SQL Statement Changes [page 133]Table and View Changes [page 146]Stored Procedure Changes [page 140]Utility Option Changes [page 149]



10.2.8.4 Transport Layer Security for Multiplex

SAP IQ supports encrypted communication connections on multiplex.

Use the -ec server option to specify FIPS-certified RSA encryption on packets transmitted to and from clients.


● Administration: User Management and Security > Security Management > Transport Layer Security > Setting up transport-layer security

● Utility Guide > start_iq Database Server Startup Utility > start_iq Server Options > -ec iqsrv16 database server option

10.2.8.5 Running Privileged System Procedures

SAP IQ provides increased security when running privileged system procedures.

For new databases, system procedures that perform authorized tasks now execute with the privileges of the person running the procedure rather than the privileges of the creator of the procedure.

This increased security can be enabled on migrated databases, with some considerations. See Migration > Database Upgrades > Changes to System Procedures that Perform Privileged Operations

Related Information

Privileged System Procedure Execution [page 118]

10.2.9 Shared System Temporary Store

A multiplex configuration with shared temporary storage can use the IQ_SHARED_TEMP dbspace as a shared system temporary store instead of requiring a separate local store for each secondary server. The shared system temporary store simplifies multiplex configuration, improves performance, and supports distributed query processing.

On multiplex systems:

● When you set the logical server policy option TEMP_DATA_IN_SHARED_TEMP ON, SAP IQ creates all temporary objects on the IQ_SHARED_TEMP dbspace. You must restart secondary nodes after setting this option or after adding a read-write file to the shared temporary store. (If the shared temporary store contains no read-write file, or if you do not restart secondary nodes, data instead writes to IQ_SYSTEM_TEMP.)

● Temporary user objects (such as tables or table indexes) that you create using the IN IQ_SYSTEM_TEMP clause go in either IQ_SYSTEM_TEMP or IQ_SHARED_TEMP, depending on the value of the logical server option TEMP_DATA_IN_SHARED_TEMP:○ If TEMP_DATA_IN_SHARED_TEMP is 'OFF', objects go in IQ_SYSTEM_TEMP.



○ If TEMP_DATA_IN_SHARED_TEMP is set 'ON', objects go in IQ_SHARED_TEMP.SAP IQ does not support creating temporary user objects using the IN IQ_SHARED_TEMP clause.

● The WITH STOP SERVER clause automatically shuts down all servers in the logical server. These statements support WITH STOP SERVER:○ ALTER LOGICAL SERVER○ ALTER LS POLICY○ CREATE LOGICAL SERVER○ DROP LOGICAL SERVER

● If you use ALTER LS POLICY ... WITH STOP SERVER to change the TEMP_DATA_IN_SHARED_TEMP option 'ON|OFF', all servers in that logical server shut down automatically. You must restart the servers to force the logical server to place temporary data in the store specified by the TEMP_DATA_IN_SHARED_TEMP option.

● If you use ALTER LS POLICY to set TEMP_DATA_IN_SHARED_TEMP 'OFF', the logical server starts placing temporary data in the SYSTEM temporary area after the next normal server startup.

● You can also change the TEMP_DATA_IN_SHARED_TEMP value indirectly using CREATE LOGICAL SERVER, ALTER LOGICAL SERVER, or DROP LOGICAL SERVER statements and the WITH STOP SERVER clause.

Related Information

Discontinued Features [page 101]Logical Server Policy Option Changes [page 127]SQL Statement Changes [page 133]

10.2.10 Table Partitioning

Table partitioning can improve performance by dividing large tables into smaller, more manageable storage objects. SAP IQ 16.0 now supports range, hash, and hash-range partitioning schemes.

● Range partitioning divides large tables by a range of partition-key values established for each partition. As part of an information life cycle management strategy, range partitioning can shorten backup and restore times; provide a finer level of granularity for data validation; and support tiered storage.

● Hash partitioning maps data to partitions based on <partition-key> values processed by an internal hashing function. Hash partitioning can enhance join performance on large tables and distributed queries (DQP).

● Hash-range partitioning provides the benefits of hash partitioning and range partitioning. Hash partitioning provides the best distributed query performance; range sub-partitioning enhances administrative tasks as part of an information life cycle management strategy.

NoteRange-partitions and composite partitioning schemes, like hash-range partitions, require the separately licensed VLDB Management option.




● Administration: Database > Manage SAP IQ Database Objects > Table Partitions● Administration: Load Management > Bulk Loads with the LOAD TABLE Statement > Considerations for

Partitioned Table Loads● Reference: Statements and Options > SQL Statements > ALTER TABLE Statement● Reference: Statements and Options > SQL Statements > CREATE TABLE Statement

10.2.11 System Secure Feature Keys

The system secure feature key now allows you to create customized secure feature keys that are assigned to a specific users, limiting users' access to only the features secured by the administrator for that key.

Customized secure feature keys are managed by system procedures.


● Administration: User Management and Security > Security Management > Data Security.

10.3 Performance Improvements

Distributed query processing and micro query performance has improved in SAP IQ 16.0. The new Cache Ejection feature improves performance by eliminating unnecessary cache page reads.

In this section:

Cache Ejection [page 100]This enhancement prevents the buffer manager from performing unnecessary rereads of cached pages from disk, improving performance through a reduction of disk I/O and internode communication.

DQP Performance Improvements [page 100]Distributed Query Processing (DQP) performance is improved in SAP IQ 16.0.

Micro Query Performance Improvement [page 101]In previous releases, the QUERY_PLAN option was ON by default, meaning that every query generated a query plan regardless of the size of the query. In SAP IQ 16.0, use the new QUERY_PLAN_MIN_TIME option when QUERY_PLAN is ON to prevent the server from generating query plans for micro queries, resulting in a database server performance improvement.



10.3.1 Cache Ejection

This enhancement prevents the buffer manager from performing unnecessary rereads of cached pages from disk, improving performance through a reduction of disk I/O and internode communication.

A cache ejection policy determines how a system identifies and replaces stale cache data. Each server in a multiplex system has its own cache.

10.3.2 DQP Performance Improvements

Distributed Query Processing (DQP) performance is improved in SAP IQ 16.0.

Performance Improvement Description

Affinity-based work allocation

For DQP eligible queries, SAP IQ identifies preferred nodes for scans of specific row ranges and partition IDs. Once a query establishes an affinity for a piece of data, subsequent queries that need the same data use the same node for their work.

Use the database options AFFINITY_AUTOEXCLUDE_TIMEOUT and CACHE_AFFINITY_PERCENT to control allocation.

Asymmetric sort merge join algorithm

The new asymmetric sort merge join algorithm improves performance in distributed queries that join and sort high-cardinality data.

Advanced DBAs can control algorithm choice using the JOIN_PREFERENCE option.

Early aggregation An optimization where distincting, grouping, and aggregates are pushed into a sort, rather than sorting all rows first, then performing any aggregation outside the sort as a second step.

Advanced DBAs can control algorithm choice using the AGGREGATION_PREFERENCE option.

Option to use DQP over the network

DQP over the network keeps data in memory in the temporary cache instead of in the IQ_SHARED_TEMP dbspace. The option that provides the best performance may vary by query, and depends on the performance of the network relative to the I/O system.

Use the DQP_ENABLED logical server policy option to control DQP processing. The DQP_ENABLED and DQP_ENABLED_OVER_NETWORK database options control DQP at the connection level.

Related Information

Query Plan Changes [page 130]



10.3.3 Micro Query Performance Improvement

In previous releases, the QUERY_PLAN option was ON by default, meaning that every query generated a query plan regardless of the size of the query. In SAP IQ 16.0, use the new QUERY_PLAN_MIN_TIME option when QUERY_PLAN is ON to prevent the server from generating query plans for micro queries, resulting in a database server performance improvement.


● Performance and Tuning Guide > Optimizing Queries and Deletions > Planning Queries > Using Query Plans > Preventing Query Plan Generation for Micro Queries

● Reference: Statements and Options > Database Options > Alphabetical List of Options > QUERY_PLAN Option

● Reference: Statements and Options > Database Options > Alphabetical List of Options > QUERY_PLAN_MIN_TIME Option

Related Information

Database Option Changes [page 120]

10.4 Discontinued Features

If you are upgrading from an earlier release of SAP IQ 16.0, note the features and functionality discontinued in this release. Discontinued features and functionality are not supported by SAP.

In this section:

JDBC™ 3 Connectivity [page 102]SAP IQ no longer supports JDBC 3 connectivity.

JDBC-Based Server Classes [page 102]JDBC-based server classes are no longer supported and generate errors.

LOAD TABLE Statement: Discontinued Syntax [page 102]Several clauses of the LOAD TABLE statement, deprecated in previous releases, are discontinued in SAP IQ 16.0.

Time Series Analysis [page 103]The time series analysis feature has been removed from SAP IQ 16.0. The Visual Numerics Inc. (VNI) third-party external libraries IMSL C Stat and C Math have been removed from the product.

Discontinued Database Server Startup Options [page 103]The start_iq options -cw, -cm, and -ec are no longer supported.

Discontinued Indexes [page 104]JOIN, LD, FP(1), FP(2), and FP(3) indexes are not supported in SAP IQ 16.0.

Discontinued Login Policy Option [page 104]



The dqp_enabled login policy option is not a valid login policy option in SAP IQ 16.0.

Discontinued Time Series SQL Functions [page 105]Time series functions are not supported in SAP IQ 16.0.

Discontinued TLS and HTTPS Certificate and Certificate_Password Protocol Options [page 107]TLS and HTTPS certificate and certificate_password protocol options were renamed to identity and identity_password, respectively, in an earlier release.

Discontinued Tables and Views [page 107]The system tables ISYSIQJOINIDX and ISYSIQJOINIXCOLUMN are no longer supported. Their corresponding system views SYSIQJOINIDX and SYSIQJOINIXCOLUMN are no longer supported.

Discontinued Tools and Utilities [page 107]Sybase CentralTM, the SQL Anywhere® debugger, iqdsedit, and iqisql are discontinued in SAP IQ 16.0.

10.4.1 JDBC™ 3 Connectivity

SAP IQ no longer supports JDBC 3 connectivity.

SAP IQ 16.0 supports JDBC 4 and supplies the jodbc4.jar file in $IQDIR16/java on UNIX or %IQDIR16%\Java on Windows. The jodbc.jar file is no longer supplied.

SAP IQ 16.0 also supports jConnect™ for JDBC 7.0.

10.4.2 JDBC-Based Server Classes

JDBC-based server classes are no longer supported and generate errors.

Discontinued Item Description

JDBC-Based Server Classes All support for JDBC-based server classes is discontinued. If your application uses any of the following, update your application to use the corresponding odbc server class:

● asejdbc● iqjdbc● sajdbc

10.4.3 LOAD TABLE Statement: Discontinued Syntax

Several clauses of the LOAD TABLE statement, deprecated in previous releases, are discontinued in SAP IQ 16.0.

The STRIP ON clause of the LOAD TABLE statement is discontinued. Using the STRIP ON clause will result in an error. Use STRIP RTRIM instead.



The BLOCK FACTOR clause of the LOAD TABLE statement, deprecated in release 15.2, is discontinued. Using the BLOCK FACTOR clause will result in an error.

The BLOCK SIZE clause of the LOAD TABLE statement, deprecated in release 15.2, is discontinued. Using the BLOCK SIZE clause will result in an error.

The UNLOAD FORMAT clause of the LOAD TABLE statement, deprecated in release 15.2, is discontinued. Using the UNLOAD FORMAT clause will result in an error.

10.4.4 Time Series Analysis

The time series analysis feature has been removed from SAP IQ 16.0. The Visual Numerics Inc. (VNI) third-party external libraries IMSL C Stat and C Math have been removed from the product.

These time series manuals have been removed from the SAP IQ documentation collection:

● Time Series Guide● IMSL C Numerical Library User Guide Volume 2 of 2: C Stat Library

Time series functions are no longer bundled with the server. Users can still continue to build their own UDFs.

Related Information

Discontinued Time Series SQL Functions [page 105]

10.4.5 Discontinued Database Server Startup Options

The start_iq options -cw, -cm, and -ec are no longer supported.


-cw iqsrv16 database server startup option (deprecated) Deprecated in previous releases, support for this start_iq option has been removed in release 16.0.

-cm iqsrv16 database server startup option Support for this start_iq option has been removed in release 16.0.

-ec iqsrv16 database server startup option parameter TLS_TYPE=ECC

Support for the ECC algorithm has been removed in release 16.0. TLS_TYPE=ECC is no longer supported.



10.4.6 Discontinued Indexes

JOIN, LD, FP(1), FP(2), and FP(3) indexes are not supported in SAP IQ 16.0.


JOIN Indexes SAP IQ no longer supports JOIN indexes. All references to this item have been removed from the documentation.

Customers who are migrating a database from a previous edition must drop all JOIN indexes before upgrading to SAP IQ 16.0.

LD Indexes LD (LOWDISK) indexes were replaced by HG indexes in release 12.0. If you have a very old database, note that SAP IQ no longer supports LD indexes. All references to this item have been removed from the documentation.

Customers who are migrating a database from a previous edition must drop all LD indexes before upgrading to SAP IQ 16.0.

FP(1), FP(2), FP(3) indexes SAP IQ no longer supports FP(1), FP(2), FP(3) indexes.

Continuous NBit dictionary compression replaces 1, 2, 3 byte dictionary compression. FP(1), FP(2), FP(3) indexes rollover to NBit 8, 16, 24 respectively.

NoteFailing to drop all LD or JOIN indexes before an ALTER DATABASE UPGRADE in SAP IQ 16.0 causes the upgrade to fail, and the server will return a message that indicates that a database upgrade is not possible when these objects are in use.

To recover, shutdown the 16.0 server, open the database with SAP IQ 15.x, and drop all LD and all JOIN indexes before proceeding with the migration.

10.4.7 Discontinued Login Policy Option

The dqp_enabled login policy option is not a valid login policy option in SAP IQ 16.0.

On upgrade, if you had configured this option for any login policy, these options will be lost.

After upgrading, configure the dqp_enabled logical server policy option for the logical servers where Distributed Query Processing (DQP) is required. You can to choose whether DQP should use the network for intermediate result sets, or use shared temporary storage.

For details, see DQP_ENABLED Option and DQP_ENABLED_OVER_NETWORK Option in Administration: Multiplex.



10.4.8 Discontinued Time Series SQL Functions

Time series functions are not supported in SAP IQ 16.0.


TS_ARMA_AR Function [Aggregate]

Discontinued SQL function. Not supported.

TS_ARMA_CONST Function [Aggregate]


TS_ARMA_MA Function [Aggregate]


TS_AUTOCORRELATION Function [Aggregate]


TS_AUTO_ARIMA Function [Aggregate]


TS_AUTO_ARIMA_OUTLIER Function [Aggregate]


TS_AUTO_ARIMA_RESULT_AIC Function [Scalar]


TS_AUTO_ARIMA_RESULT_AICC [Scalar]


TS_AUTO_ARIMA_RESULT_BIC Function [Scalar]


TS_AUTO_ARIMA_RESULT_FORECAST_ERROR Function [Scalar]


TS_AUTO_ARIMA_RESULT_FORECAST_VALUE Function [Scalar]


TS_AUTO_ARIMA_RESULT_MODEL_P Function [Scalar]


TS_AUTO_ARIMA_RESULT_MODEL_Q Function [Scalar]


TS_AUTO_ARIMA_RESULT_MODEL_S Function [Scalar]


TS_AUTO_ARIMA_RESULT_MODEL_D Function [Scalar]


TS_AUTO_ARIMA_RESULT_RESIDUAL_SIGMA Function [Scalar]


TS_AUTO_UNI_AR Function [Aggregate]


TS_BOX_COX_XFORM Function [Aggregate]





TS_DIFFERENCE Function [Aggregate]


TS_DOUBLE_ARRAY Function [Scalar]


TS_ESTIMATE_MISSING Function [Aggregate]


TS_GARCH Function [Aggregate] Discontinued SQL function. Not supported.

TS_GARCH_RESULT_A Function [Scalar]


TS_GARCH_RESULT_AIC Function [Scalar]


TS_GARCH_RESULT_USER [Scalar]


TS_INT_ARRAY Function [Scalar] Discontinued SQL function. Not supported.

TS_LACK_OF_FIT Function [Aggregate]


TS_LACK_OF_FIT_P Function [Aggregate]


TS_MAX_ARMA_AR Function [Aggregate]


TS_MAX_ARMA_CONST Function [Aggregate]


TS_MAX_ARMA_LIKELIHOOD Function [Aggregate]


TS_MAX_ARMA_MA Function [Aggregate]


TS_OUTLIER_IDENTIFICATION Function [Aggregate]


TS_PARTIAL_AUTOCORRELATION Function [Aggregate]


TS_VWAP Function [Aggregate] Discontinued SQL function. Not supported.

Related Information

SQL Function Changes [page 132]SQL Function Changes [page 132]



10.4.9 Discontinued TLS and HTTPS Certificate and Certificate_Password Protocol Options

TLS and HTTPS certificate and certificate_password protocol options were renamed to identity and identity_password, respectively, in an earlier release.

Attempting to use the discontinued names certificate and certificate_password in SAP IQ 16.0 results in an error.

10.4.10 Discontinued Tables and Views

The system tables ISYSIQJOINIDX and ISYSIQJOINIXCOLUMN are no longer supported. Their corresponding system views SYSIQJOINIDX and SYSIQJOINIXCOLUMN are no longer supported.

System Tables

System Table Description

ISYSIQJOINIDX SAP IQ no longer supports this table.

ISYSIQJOINIXCOLUMN SAP IQ no longer supports this table.

System Views

System View Description

SYSIQJOINIDX SAP IQ no longer supports this view.

SYSIQJOINIXCOLUMN SAP IQ no longer supports this view.

Related Information

Table and View Changes [page 146]

10.4.11 Discontinued Tools and Utilities

Sybase CentralTM, the SQL Anywhere® debugger, iqdsedit, and iqisql are discontinued in SAP IQ 16.0.

In this section:



Debugger [page 108]The SQL Anywhere debugger has been discontinued in SAP IQ 16.0. The debugger was used during the development of SQL stored procedures.

iqdsedit Utility [page 108]All support for the iqdsedit utility has been discontinued. Use the DSEdit utility (dsedit.exe) instead.

iqisql Utility [page 108]All support for the iqisql utility has been discontinued.

Sybase Central [page 109]The Sybase Central graphical administration tool has been discontinued. SAP Control Center replaces it.

10.4.11.1 Debugger

The SQL Anywhere debugger has been discontinued in SAP IQ 16.0. The debugger was used during the development of SQL stored procedures.

A debugging tool will be available in a future release.

10.4.11.2 iqdsedit Utility

All support for the iqdsedit utility has been discontinued. Use the DSEdit utility (dsedit.exe) instead.

10.4.11.3 iqisql Utility

All support for the iqisql utility has been discontinued.

Use the isql Interactive SQL utility instead.



10.4.11.4 Sybase Central

The Sybase Central graphical administration tool has been discontinued. SAP Control Center replaces it.

10.5 Deprecated Features

If you are upgrading from an earlier release of SAP IQ, note the features and functionality deprecated in release 16.0. Deprecated features and functionality are supported for backward compatibility, but are not recommended. Support will be removed in an upcoming release.

In this section:

Deprecated Database Options [page 109]Some database options, and the DQP_ENABLED login policy option, are deprecated or discontinued in SAP IQ 16.0.

Deprecated Database Server Startup Options [page 110]The host parameter of start_iq option -x is deprecated in SAP IQ 16.0.

Deprecated Stored Procedures [page 110]Several stored procedures are deprecated in SAP IQ 16.0.

Deprecated System Tables and Views [page 111]Several system tables and views are deprecated in SAP IQ 16.0.

Deprecated User Management Functionality [page 111]Authorities and groups are deprecated in SAP IQ 16.0 and are replaced by role-based security. However, role-based security is backwards compatible with authorities and groups.

Deprecated Environment Variables [page 111]Several environment variables are deprecated in SAP IQ 16.0.

10.5.1 Deprecated Database Options

Some database options, and the DQP_ENABLED login policy option, are deprecated or discontinued in SAP IQ 16.0.

Deprecated Item Description

APPEND_LOAD The APPEND_LOAD option is deprecated. This option still exists but the setting will be ignored.

DQP_ENABLED login policy option Discontinued. Replaced by DQP_ENABLED logical server policy option.

LARGE_DOUBLES_ACCUMULATOR Discontinued. Replaced by FLOATING_POINT_ACCUMULATOR option.




MAX_WARNINGS Since SAP IQ no longer supports JOIN INDEXES, the MAX_WARNINGS option is no longer required.

10.5.2 Deprecated Database Server Startup Options

The host parameter of start_iq option -x is deprecated in SAP IQ 16.0.


host parameter for -x iqsrv16 database server startup option The host network connection parameter of the -x option is deprecated in release 16.0.

10.5.3 Deprecated Stored Procedures

Several stored procedures are deprecated in SAP IQ 16.0.


sp_addgroup With the implementation of role-based security, SAP IQ no longer supports groups. However, the procedure remains, for backward compatibility.

sp_changegroup With the implementation of role-based security, SAP IQ no longer supports groups. However, the procedure remains, for backward compatibility.

sp_dropgroup With the implementation of role-based security, SAP IQ no longer supports groups. However, the procedure remains, for backward compatibility.

sp_iqcardinality_analysis sp_iqcardinality_analysis no longer returns an index type value or index recommendation. Users are advised to run Index Advisor for suggestions about additional column indexes. sp_iqcardinality_analysis is deprecated and will be removed in a future release.

Related Information

Stored Procedure Changes [page 140]



10.5.4 Deprecated System Tables and Views

Several system tables and views are deprecated in SAP IQ 16.0.

Table Description

ISYSGROUP Table no longer used in SAP IQ 16.0; however, SYSGROUP system view remains for backward compatibility.

ISYSUSERAUTHORITY Table no longer used in SAP IQ 16.0; however, SYSUSERAUTHORITY system view remains for backward compatibility.

10.5.5 Deprecated User Management Functionality

Authorities and groups are deprecated in SAP IQ 16.0 and are replaced by role-based security. However, role-based security is backwards compatible with authorities and groups.


Authorities Authorities have become user-defined roles. During the upgrade of an existing database to SAP IQ 16.0, each deprecated SAP IQ 15.x authority is replaced with an equivalent user-defined compatibility role, which contains an equivalent set of privileged tasks.

Groups Groups have become user-extended roles. During the upgrade of an existing database to SAP IQ 16.0, each existing group in the database is replaced with an equivalent user extended role, using the same name. All members of the original group are automatically granted membership in the equivalent new role. Any authorities granted to the original group are automatically replaced with the equivalent compatibility role and granted to the new user-extended role.

10.5.6 Deprecated Environment Variables

Several environment variables are deprecated in SAP IQ 16.0.

The following SYBASE_JRE6 Java environment variables are deprecated:

● SYBASE_JRE6_64● SYBASE_JRE6● SYBASE_JRE6_32● SYBASE_JRE5_64



Related Information

JRE and Java Runtime Environment Variable Changes [page 126]

10.6 Behavior Changes

Several behavior changes have been introduced in SAP IQ 16.0.

In this section:

Backward Compatibility: Changes to Default Behavior [page 113]The default behavior of the initial 16.0 version has changed in some areas.

Backward Compatibility: Migration Considerations [page 116]If you are upgrading from an earlier release of SAP IQ, several new features and functionality introduced in the initial 16.0 version are backward compatible.

Connection Changes [page 118]SAP IQ 16.0 enhances database connections.

Database Option Changes [page 120]The initial 16.0 version includes database option changes.

JRE and Java Runtime Environment Variable Changes [page 126]SAP IQ 16.0 requires JRE_7. The SYBASE_JRE Java environment variables have changed accordingly.

Logical Server Policy Option Changes [page 127]Changes affected logical server policy options in SAP IQ 16.0.

Login Policy Option Changes [page 128]There are changes to some login policy options in SAP IQ 16.0.

ODBC Driver Changes [page 129]The name of the ODBC driver (DBODBC16.DLL) changed in SAP IQ 16.0.

Query Plan Changes [page 130]New load execution plans and query plan nodes in SAP IQ 16.0.

SQL Function Changes [page 132]Function changes for SAP IQ 16.0.

SQL Statement Changes [page 133]Syntax changes for SAP IQ 16.0.

Stored Procedure Changes [page 140]The initial 16.0 version includes catalog stored procedure and system stored procedure changes.

Table and View Changes [page 146]SAP IQ 16.0 includes new and changed system tables and views.

Utility Option Changes [page 149]The initial 16.0 version includes option changes for the isql and start_iq utilities.



10.6.1 Backward Compatibility: Changes to Default Behavior

The default behavior of the initial 16.0 version has changed in some areas.

In this section:

Constraint Violation Checks [page 113]The order in which the database server evaluates check constraints and unique constraints has changed in SAP IQ 16.0. This behavior change occurs only for LOAD or INSERT statements containing the clause IGNORE CONSTRAINT CHECK <x>, UNIQUE <y>.

Database Options: Changed Defaults [page 114]If you are upgrading from an earlier release of SAP IQ, note that default values of some database options changed in release 16.0.

Reserved Words [page 116]Reserved words in SAP IQ 16.0.

Parent topic: Behavior Changes [page 112]

Related Information

Backward Compatibility: Migration Considerations [page 116]Connection Changes [page 118]Database Option Changes [page 120]JRE and Java Runtime Environment Variable Changes [page 126]Logical Server Policy Option Changes [page 127]Login Policy Option Changes [page 128]ODBC Driver Changes [page 129]Query Plan Changes [page 130]SQL Function Changes [page 132]SQL Statement Changes [page 133]Stored Procedure Changes [page 140]Table and View Changes [page 146]Utility Option Changes [page 149]

10.6.1.1 Constraint Violation Checks

The order in which the database server evaluates check constraints and unique constraints has changed in SAP IQ 16.0. This behavior change occurs only for LOAD or INSERT statements containing the clause IGNORE CONSTRAINT CHECK <x>, UNIQUE <y>.

Check constraints are now evaluated before unique constraints. This behavior change may lead to different load results compared to 15.4, depending on the constraints specified, and the data being loaded.



Consider this simple LOAD TABLE example comparing 15.4 constraint evaluation behavior with 16.0:

1. Create the table:

CREATE TABLE t1( c1 int, c2 int, primary key(c1), CHECK( c1 < c2 ) );

2. Load values:

LOAD TABLE t1 { 4,3 }, {4,5 } FROM ‘sample_data.dat’ IGNORE CONSTRAINT CHECK 0, UNIQUE 0

In 15.4, the database server detects unique constraint violations before check constraint violations:○ HG index detects a unique violation on { 4, 5 }, so row 2 is removed.○ This leaves row 1 which contains { 4, 3 }. This violates the check constraint, so row 1 is removed.○ The result is zero rows in the table.

In 16.0, check constraint violations are detected first, resulting in a different outcome:○ Row { 4,3 } is discarded due to the check constraint violation.○ HG index only sees one row so there is no unique constraint violation.○ The resulting row { 4, 5 } does not violate the check constraint.○ The result is one row in the table: { 4, 5 }.

A related behavior change affects column defaults in statements containing the clause IGNORE CONSTRAINT CHECK. In SAP IQ 16.0, column default violations are never ignored.

In this section:

Constraint Violation Checks: Message Log and Row Log [page 114]In previous versions, the row ID listed in msg.log and row.log indicated the actual row ID. In SAP IQ 16.0, the row ID represents the logical row ID of the specified constraint violation.

10.6.1.1.1 Constraint Violation Checks: Message Log and Row Log

In previous versions, the row ID listed in msg.log and row.log indicated the actual row ID. In SAP IQ 16.0, the row ID represents the logical row ID of the specified constraint violation.

10.6.1.2 Database Options: Changed Defaults

If you are upgrading from an earlier release of SAP IQ, note that default values of some database options changed in release 16.0.

In this section:

JOIN_SIMPLIFICATION_THRESHOLD Option [page 115]The default value for the JOIN_SIMPLIFICATION_THRESHOLD database option changed to12 in SAP IQ 16.0.

MIN_PASSWORD_LENGTH Option [page 115]



The default value for the MIN_PASSWORD_LENGTH database option changed to 3 in SAP IQ 16.0.

QUERY_PLAN Option [page 115]The default value for the QUERY_PLAN database option changed to OFF in SAP IQ 16.0.

QUERY_DETAIL Option [page 115]The default value for the QUERY_DETAIL database option changed to ON in SAP IQ 16.0.

QUERY_PLAN_AFTER_RUN Option [page 115]The default value for the QUERY_PLAN_AFTER_RUN database option changed to ON in SAP IQ 16.0.

QUERY_TIMING Option [page 116]The default value for the QUERY_TIMING database option changed to ON in SAP IQ 16.0.

10.6.1.2.1 JOIN_SIMPLIFICATION_THRESHOLD Option

The default value for the JOIN_SIMPLIFICATION_THRESHOLD database option changed to12 in SAP IQ 16.0.

10.6.1.2.2 MIN_PASSWORD_LENGTH Option

The default value for the MIN_PASSWORD_LENGTH database option changed to 3 in SAP IQ 16.0.

In previous releases, any length or an empty password were permitted.

10.6.1.2.3 QUERY_PLAN Option

The default value for the QUERY_PLAN database option changed to OFF in SAP IQ 16.0.

In previous releases, the default was ON.

10.6.1.2.4 QUERY_DETAIL Option

The default value for the QUERY_DETAIL database option changed to ON in SAP IQ 16.0.

In previous releases, the default was OFF.

10.6.1.2.5 QUERY_PLAN_AFTER_RUN Option

The default value for the QUERY_PLAN_AFTER_RUN database option changed to ON in SAP IQ 16.0.




10.6.1.2.6 QUERY_TIMING Option

The default value for the QUERY_TIMING database option changed to ON in SAP IQ 16.0.


10.6.1.3 Reserved Words

Reserved words in SAP IQ 16.0.

Item Description

Object Names Unlike previous releases, reserved words in SAP IQ 16.0 cannot be used as object names, unless enclosed in brackets or double quotes.

A SAP IQ 15 database could contain tables, columns, and other objects named row. In SAP IQ 16.0, row is a reserved word and cannot be used as an object name.

To use a reserved word as an object name, enclose 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;

array New reserved word in SAP IQ 16.0.

json New reserved word in SAP IQ 16.0.

row New reserved word in SAP IQ 16.0.

rowtype New reserved word in SAP IQ 16.0.

unnest New reserved word in SAP IQ 16.0.

varray New reserved word in SAP IQ 16.0.

10.6.2 Backward Compatibility: Migration Considerations

If you are upgrading from an earlier release of SAP IQ, several new features and functionality introduced in the initial 16.0 version are backward compatible.

In this section:



GRANT/REVOKE Syntax [page 117]The syntax to grant and revoke system privileges in the role-based security model has changed significantly.

Role-Based Security in Stored Procedures [page 118]The enhanced role-based security model of SAP IQ 16.0 retains backward compatibility with authority-based syntax.

Privileged System Procedure Execution [page 118]As part of role-based security, the way in which privileged system procedures run has changed.


Related Information

Backward Compatibility: Changes to Default Behavior [page 113]Connection Changes [page 118]Database Option Changes [page 120]JRE and Java Runtime Environment Variable Changes [page 126]Logical Server Policy Option Changes [page 127]Login Policy Option Changes [page 128]ODBC Driver Changes [page 129]Query Plan Changes [page 130]SQL Function Changes [page 132]SQL Statement Changes [page 133]Stored Procedure Changes [page 140]Table and View Changes [page 146]Utility Option Changes [page 149]

10.6.2.1 GRANT/REVOKE Syntax

The syntax to grant and revoke system privileges in the role-based security model has changed significantly.

However, support for the previous syntax continues. One-to-one mappings between the authority-based and role-based models and group-based and role-based syntax assist in the transition to the new role-based syntax.

See:

● Migration > Upgrading to Role-Based Security > Changes to the GRANT Statement Syntax.● Migration > Upgrading to Role-Based Security > Changes to the REVOKE Statement Syntax.



10.6.2.2 Role-Based Security in Stored Procedures

The enhanced role-based security model of SAP IQ 16.0 retains backward compatibility with authority-based syntax.

All user-defined stored procedures, functions, and queries created on SAP IQ 15.x databases will continue to run after they are upgraded.

10.6.2.3 Privileged System Procedure Execution

As part of role-based security, the way in which privileged system procedures run has changed.

In pre-16.0 databases, privileged system procedures ran with the privileges of its owner, referred to as the SYSTEM PROCEDURE DEFINER model. In new 16.0 databases, privileged system procedures run with the privileges of the person executing it, referred to as the SYSTEM PROCEDURE INVOKER model.

To minimize potential loss of functionality as a result of this behavior change, after upgrading using the default options, all pre-16.0 system procedures continue to run using the SYSTEM PROCEDURE DEFINER model. Any system procedures introduced in 16.0 or later run using the SYSTEM PROCEDURE INVOKER model.

See:

● Migration > Upgrading to Role-Based Security > Changes to System Procedures that Perform Privileged Operations

● Migration > Upgrading to Role-Based Security > Managing System Procedure Execution

10.6.3 Connection Changes

SAP IQ 16.0 enhances database connections.

Table 4: Connection Parameter Changes


LogicalServer [LS] Specifies the target logical server, enabling redirection of a connection from one multiplex node to another. When unspecified, The logical server defaults to the setting of the <default_logical_server> option in the user login policy.

See Administration: Database > Connect to Servers and Databases > Connection and Communication Parameters > Connection Parameters > LogicalServer Connection Parameter [LS]




NodeType Connects an application to a logical server member node that has a specific role.

See Administration: Database > Connect to Servers and Databases > Connection and Communication Parameters > Connection Parameters > NodeType Connection Parameter

Redirect Controls login redirection at the connection level.

See Administration: Database > Connect to Servers and Databases > Connection and Communication Parameters > Connection Parameters > Redirect Connection Parameter


Related Information

Backward Compatibility: Changes to Default Behavior [page 113]Backward Compatibility: Migration Considerations [page 116]Database Option Changes [page 120]JRE and Java Runtime Environment Variable Changes [page 126]Logical Server Policy Option Changes [page 127]Login Policy Option Changes [page 128]ODBC Driver Changes [page 129]Query Plan Changes [page 130]SQL Function Changes [page 132]SQL Statement Changes [page 133]Stored Procedure Changes [page 140]Table and View Changes [page 146]Utility Option Changes [page 149]



10.6.4 Database Option Changes

The initial 16.0 version includes database option changes.

Option Description

AFFINITY_AUTOEXCLUDE_TIMEOUT The amount of time before SAP IQ removes a shut down node from the affinity map and reassigns its partitions to other nodes.

Allowed values are 0 to 10080 minutes (1 week). The default is 10 minutes.

AGGREGATION_PREFERENCE The allowed value range is now -6 to 6.

These values are new in SAP IQ 16.0:

4 prefer aggregation with a distinct/grouping sort.5 prefer aggregation with a sort if grouping columns include all the partitioning keys of a hash partitioned table.6 prefer aggregation with a hash if grouping columns include all the partitioning keys of a hash partitioned table.-4 avoid aggregation with a distinct/grouping sort.-5 avoid aggregation with a sort if grouping columns include all the partitioning keys of a hash partitioned table.-6 avoid aggregation with a hash if grouping columns include all the partitioning keys of a hash partitioned table.

ALLOW_SNAPSHOT_VERSIONING New option. Applies to all base tables in the database (as opposed to RLV-enabled tables only). Restricts table versioning for all base tables to either table-level or row-level snapshot versioning. This option does not apply to the IQ catalog store.

The default is YES.

ANSI_SUBSTRING [TSQL] The default changed to ON.

NoteDefault values in recent releases:

16.0 ON15.4 OFF15.3 OFF15.0 - 15.2 ESD3 ON

APPEND_LOAD The APPEND_LOAD option is deprecated. This option still exists but the setting will be ignored.



Option Description

BASE_TABLES_IN_RLV New option. Registers new tables in the RLV store, enabling row-level versioning for IQ main store tables. RLV-enabled tables are eligible for multiple writer concurrent access. You can override this setting at the table level using the CREATE TABLE statement. Has no effect on IQ main store tables created before you set this option ON. Has no effect on tables from an upgraded database.

BLOCKING New allowed value: ON. This setting causes any transaction attempting to obtain a lock that conflicts with an existing lock held by another transaction to wait until every conflicting lock is released, or until the blocking_timeout threshold is reached.

BLOCKING is not supported on secondary nodes of a multiplex. It is supported on the multiplex coordinator node, and in simplex implementations.

BLOCKING_TIMEOUT New option. Controls how long (in milliseconds) a transaction waits to obtain a lock.

BLOCKING_TIMEOUT is not supported on secondary nodes of a multiplex. It is supported on the multiplex coordinator node, and in simplex implementations.

CACHE_AFFINITY_PERCENT Allowed values are 0 -100.

Maximum percentage of main cache to use for affinity. Non-affinity data can use this area if insufficient affinity data exists.

CREATE_HG_WITH_EXACT_DISTINCTS Determines whether newly created HG indexes are tiered or non-tiered.This option is ON in all new 16.0 databases and all 16.0 databases migrated from 15.x.To take advantage of the new structure, set this option to OFF.

CREATE_HG_AND_FORCE_PHYSICAL_DELETE

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

DQP_ENABLED Set the temporary database option DQP_ENABLED OFF to disable DQP for the current connection. Set the option ON (the default value) to enable DQP for the current connection, but only when DQP is enabled by the policy option for the logical server of the current connection.



Option Description

DQP_ENABLED_OVER_NETWORK Set the temporary database option DQP_ENABLED_OVER_NETWORK to ON to enable DQP over the network for the current connection. The DQP_ENABLED database option must also be set to ON and the DQP_ENABLED logical server policy option must not be set to 1. If the DQP_ENABLED logical server policy option is set to 2, then this database option has no affect and all queries will use DQP over the network.

ENABLE_ASYNC_IO New option.

Allows a DBA to enable or disable the asynchronous IO used by the RLV persistence log for row-level versioning.

FLOATING_POINT_ACCUMULATOR New option. Replaces LARGE_DOUBLES_ACCUMULATOR.

FP_LOOKUP_SIZE Sets the number of lookup pages and reserves cache memory for FP indexes in SAP IQ databases where the FP_NBIT_IQ15_COMPATIBILITY option is ON.

FP_LOOKUP_SIZE_PPM Controls the amount of main cache allocated to FP indexes in SAP IQ databases where the FP_NBIT_IQ15_COMPATIBILITY option is ON.

FP_NBIT_AUTOSIZE_LIMIT New option. Limits the number of distinct values that an NBit column can load implicitly. Columns implicitly load as NBit up to the auto-size limits. Columns with an IQ UNIQUE n value set to 0 loads as Flat FP. Columns with an n value greater than 0 but less than the auto-size limit sets the NBit limit to n.

FP_NBIT_ENFORCE_LIMITS New option. If this option is ON, and an NBit column exceeds explicit or implicit sizing limits, the operation throws an error and rolls back.

FP_NBIT_IQ15_ COMPATIBILITY New option. Provides tokenized FP support similar to that available in SAP IQ 15. Defaults to OFF in a newly created 16.0 database. Set to ON in SAP IQ databases upgraded from 15.x.

FP_NBIT_LOOKUP_MB New option. Limits the dictionary size for implicit NBit columns. Columns that exceed these limits rollover to Flat FP.

FP_NBIT_ROLLOVER_MAX_MB New option. Sets the dictionary size (values and counts) for implicit NBit rollovers. If this option is ON, columns that exceed this limit rollover to Flat FP.



Option Description

JOIN_PREFERENCE The allowed value range is now -12 to 12.

These values changed in SAP IQ 16.0:

6 previously the action was prefer prejoin. The new action is prefer asymmetric sort merge join.-6 previously the action was avoid prejoin. The new action is avoid asymmetric sort merge join.

These values are new in SAP IQ 16.0:

8 prefer asymmetric sort merge push down join.9 prefer partitioned hash join if the join keys include all the partition keys of a hash partitioned table.10 prefer partitioned hash-push down join if the join keys include all the partition keys of a hash partitioned table.11 prefer partitioned sort-merge join if the join keys include all the partition keys of a hash partitioned table.12 prefer partitioned sort-merge push-down join if the join keys include all the partition keys of a hash partitioned table.-8 avoid asymmetric sort merge push down join.-9 avoid partitioned hash join if the join keys include all the partition keys of a hash partitioned table.-10 avoid partitioned hash-push down join if the join keys include all the partition keys of a hash partitioned table.-11 avoid partitioned sort-merge join if the join keys include all the partition keys of a hash partitioned table.-12 avoid partitioned sort-merge push-down join if the join keys include all the partition keys of a hash partitioned table.

JOIN_SIMPLIFICATION_THRESHOLD New option - Controls the minimum number of tables being joined together before any join optimizer simplifications are applied.

LOG_DEADLOCKS New option - Controls whether deadlock reporting is turned on or off.

LOGIN_MODE New option. Add LDAPUA to the LOGIN_MODE option to use LDAP user authentication.

MAX_WARNINGS Since SAP IQ no longer supports JOIN INDEXES, the MAX_WARNINGS option is no longer required.

MIN_ROLE_ADMINS New option. Specifies the minimum number of role administrators for each role. Ensures that no role can be dropped if doing so reduces the remaining number of role administrators below a set value. Value range is 1 (default) – 10.

MINIMIZE_STORAGE Behavior change. Minimizes disk space for columns in 16.0 databases where the FP_NBIT_IQ15_COMPATIBILITY option is ON. Ignored where the FP_NBIT_IQ15_COMPATIBILITY option is OFF.



Option Description

NOTIFY_MODULUS Behavior change – Default value for new SAP IQ 16.0 database changed from 100000 to 0. Default value remains unchanged for an upgraded pre-16.0 database.

QUERY_DETAIL Default changed to ON.

QUERY_PLAN Default changed to OFF.

QUERY_PLAN_AFTER_RUN Default changed to ON.

QUERY_PLAN_MIN_TIME New option. Specifies a threshold for query execution in microseconds. The query plan is generated only if query execution time exceeds the threshold. QUERY_PLAN must be ON.

QUERY_TIMING Default changed to ON.

REVERT_TO_V15_OPTIMIZER New option. Forces the query optimizer behaves as it did in 15.4. Forces the query optimizer to mimic 15.x behavior. This option is OFF in all newly created 16.0 databases. Set to ON in SAP IQ databases upgraded from 15.x.

To take advatage of new DQP and algorithms and hash partitioning features, set this option to OFF in databases upgraded from 15.x.

ROUND_TO_EVEN New option. When ROUND_TO_EVEN option is set to ON, the ROUND function rounds half to the nearest even number. When the option is set to OFF (the default), the ROUND function rounds half away from zero.

RV_AUTO_MERGE_EVAL_INTERVAL New option. Configures the evaluation period used to determine when an automated background merge of the row-level versioned (RLV) and IQ main stores should occur.

The default is 15 minutes.

RV_MERGE_NODE_MEMSIZE New option. An automated merge of the row-level versioned (RLV) store and IQ main stores occurs based on the merge thresholds, including RV_MERGE_NODE_MEMSIZE. When this node threshold is exceeded, a merge will be triggered.

The default is 75%.

RV_MERGE_TABLE_MEMPERCENT New option. An automated merge of the row-level versioned (RLV) store and IQ main stores occurs based on the merge thresholds, including RV_MERGE_TABLE_MEMPERCENT. If this table threshold is exceeded, a merge will be triggered for the specific table.

The default is 0%.

RV_MERGE_TABLE_NUMROWS New option. An automated merge of the row-level versioned (RLV) store and IQ main stores occurs based on the merge thresholds, including RV_MERGE_TABLE_NUMROWS. If this table threshold is exceeded, a merge will be triggered for the specific table.

The default is 10000000.



Option Description

RV_RESERVED_DBSPACE_MB New option. A portion of the RLV store must be reserved for memory used by data structures during critical operations.

The default is The minimum of 50 Mb or half the size of the RLV dbspace.

SNAPSHOT_VERSIONING New option. Applies to RLV-enabled tables only (as opposed to all base tables in the database). Controls whether RLV-enabled tables are accessed using single-writer table-level versioning, or multiple writer row-level versioning. This option does not apply to the IQ catalog store.

The default is TLV.

TRUSTED_CERTIFICATE_FILE New option. For TLS connections from SAP IQ to other servers. Specifies the file name containing the certificate of the certificate authorities (CA) that are trusted. The trusted CAs are the signers of the certificates used by:

● The external LDAP directory server for use with LDAP User Authentication

● The server certificate in use by the SAP IQ multiplex server for INC and MIPC connections.


Related Information

Backward Compatibility: Changes to Default Behavior [page 113]Backward Compatibility: Migration Considerations [page 116]Connection Changes [page 118]JRE and Java Runtime Environment Variable Changes [page 126]Logical Server Policy Option Changes [page 127]Login Policy Option Changes [page 128]ODBC Driver Changes [page 129]Query Plan Changes [page 130]SQL Function Changes [page 132]SQL Statement Changes [page 133]Stored Procedure Changes [page 140]Table and View Changes [page 146]Utility Option Changes [page 149]Query Plan Changes [page 130]DQP Performance Improvements [page 100]Database Options: Changed Defaults [page 114]Deprecated Database Options [page 109]



10.6.5 JRE and Java Runtime Environment Variable Changes

SAP IQ 16.0 requires JRE_7. The SYBASE_JRE Java environment variables have changed accordingly.

The SYBASE_JRE7_64, SYBASE_JRE7_32 environment variable specifies the location of the Java Runtime Environment used by SAP Control Center. On startup, SAP Control Center checks SCC_JAVA_HOME for Java version definition. If SCC_JAVA_HOME is undefined, SAP Control Center checks for installed JREs in this order:

● SYBASE_JRE7_64● SYBASE_JRE7_32

The following SYBASE_JRE6 Java environment variables are deprecated:

● SYBASE_JRE6_64● SYBASE_JRE6● SYBASE_JRE6_32● SYBASE_JRE5_64


Related Information

Backward Compatibility: Changes to Default Behavior [page 113]Backward Compatibility: Migration Considerations [page 116]Connection Changes [page 118]Database Option Changes [page 120]Logical Server Policy Option Changes [page 127]Login Policy Option Changes [page 128]ODBC Driver Changes [page 129]Query Plan Changes [page 130]SQL Function Changes [page 132]SQL Statement Changes [page 133]Stored Procedure Changes [page 140]Table and View Changes [page 146]Utility Option Changes [page 149]



10.6.6 Logical Server Policy Option Changes

Changes affected logical server policy options in SAP IQ 16.0.

Option Description

DQP_ENABLED New option. When set to 0, query processing is not distributed. When set to 1 (the default), query processing is distributed as long as a writable shared temporary file exists. When set to 2, query processing is distributed over the network, and the shared temporary store is not used.

LOGIN_REDIRECTION New option. When ON, enables login redirection for logical servers governed by specified login policy. When OFF (the default), disables login redirection.

REDIRECTION_WAITERS_THRESHOLD

New option. Specifies the number of connections that can queue before SAP IQ redirects a connection to this logical server. Can be any integer value (defaults to 5).

TEMP_DATA_IN_SHARED_TEMP When ON, all temporary table data and eligible scratch data writes to the shared temporary store, provided that the shared temporary store has at least one read-write file added. You must restart all multiplex nodes after setting this option or after adding a read-write file to the shared temporary store. (If the shared temporary store contains no read-write file, or if you do not restart nodes, data instead writes to IQ_SYSTEM_TEMP.) When OFF (the default), all temporary table data and scratch data writes to the local temporary store.

See Reference: Statements and Options > SQL Statements > ALTER LS POLICY Statement.


Related Information

Backward Compatibility: Changes to Default Behavior [page 113]Backward Compatibility: Migration Considerations [page 116]Connection Changes [page 118]Database Option Changes [page 120]JRE and Java Runtime Environment Variable Changes [page 126]Login Policy Option Changes [page 128]ODBC Driver Changes [page 129]Query Plan Changes [page 130]SQL Function Changes [page 132]SQL Statement Changes [page 133]Stored Procedure Changes [page 140]Table and View Changes [page 146]Utility Option Changes [page 149]



10.6.7 Login Policy Option Changes

There are changes to some login policy options in SAP IQ 16.0.

Option Description

AUTO_UNLOCK_TIME New option. The time period after which locked accounts not granted the MANAGE ANY USER system privilege are automatically unlocked. This option can be defined in any login policy, including the root login policy.

ROOT_AUTO_UNLOCK_TIME New option. The time period after which locked accounts granted the MANAGE ANY USER system privilege are automatically unlocked. This option can be defined in the root login policy only.

CHANGE_PASSWORD_DUAL_CONTROL

New option. Requires input from two users, each granted the CHANGE PASSWORD system privilege, to change the password of another user.

LDAP_PRIMARY_SERVER New option. Specifies the name of the primary LDAP server.

LDAP_SECONDARY_SERVER New option. Specifies the name of the secondary LDAP server.

LDAP_AUTO_FAILBACK_PERIOD New option. Specifies the time period, in minutes, after which automatic failback to the primary server is attempted.

LDAP_FAILOVER_TO_STD New option. Permits authentication with standard authentication when authentication with the LDAP server fails due to system resources, network outage, connection timeouts, or similar system failures. However, it does not permit an actual authentication failure returned from an LDAP server to fail over to standard authentication.

LDAP_REFRESH_DN New option. Updates the ldap_refresh_dn value in the ISYSLOGINPOLICYOPTION system table with the current time, stored in Coordinated Universal Time (UTC).

Each time a user authenticates with LDAP, if the value of the option ldap_refresh_dn in ISYSLOGINPOLICYOPTION is more recent than the user_dn value in ISYSUSER, a search for a new user DN occurs. The user_dn value is then updated with the new user DN and the user_dn_changed_at value is again updated to the current time.

See Reference: Statements and Options > SQL Statements > ALTER LOGIN POLICY Statement.


Related Information

Backward Compatibility: Changes to Default Behavior [page 113]Backward Compatibility: Migration Considerations [page 116]Connection Changes [page 118]Database Option Changes [page 120]JRE and Java Runtime Environment Variable Changes [page 126]Logical Server Policy Option Changes [page 127]



ODBC Driver Changes [page 129]Query Plan Changes [page 130]SQL Function Changes [page 132]SQL Statement Changes [page 133]Stored Procedure Changes [page 140]Table and View Changes [page 146]Utility Option Changes [page 149]

10.6.8 ODBC Driver Changes

The name of the ODBC driver (DBODBC16.DLL) changed in SAP IQ 16.0.

In 15.4, the driver name was SQL Anywhere. In 16.0, the driver name is Sybase IQ.

If you have an ODBC application that references the driver name directly, you will need to update the driver name in the application. If your ODBC application references the data source name, no application changes are required.


Related Information

Backward Compatibility: Changes to Default Behavior [page 113]Backward Compatibility: Migration Considerations [page 116]Connection Changes [page 118]Database Option Changes [page 120]JRE and Java Runtime Environment Variable Changes [page 126]Logical Server Policy Option Changes [page 127]Login Policy Option Changes [page 128]Query Plan Changes [page 130]SQL Function Changes [page 132]SQL Statement Changes [page 133]Stored Procedure Changes [page 140]Table and View Changes [page 146]Utility Option Changes [page 149]



10.6.9 Query Plan Changes

New load execution plans and query plan nodes in SAP IQ 16.0.

Load Execution Plans

The Interactive SQL Query Plan Viewer now supports SAP IQ load execution plans. Load execution plans detail the steps that the database engine uses to insert data into a table.

Load plans use the same database options as query execution plans. Text versions of the plan are written to the .iqmsg file. HTML versions include a Data Flow Object (DFO) tree that identifies the number of rows processed at each stage of the load. Different SQL statements generate different DFO trees and the same statement may generate different trees for different kind of tables (un-partitioned, range partitioned, hash partitioned, hash-range partitioned, etc.).

Load execution plans support these SQL statements:

● LOAD..INTO● INSERT..LOCATION● INSERT..VALUES● INSERT..INTO● CREATE INDEX● ALTER TABLE ADD column (with default value)● DECLARE CURSOR FOR UPDATE● PARALLEL IQ statements

To generate a load plan, set the appropriate QUERY_PLAN options, then use the Interactive SQL Query Plan Viewer to create the plan.

NoteUse query plans only to evaluate the efficiency of a particular query or load. Running SAP IQ with the QUERY_PLAN option set to ON can significantly impact performance, particularly as the volume of INSERT...VALUE statements increase.

New query plan nodes


Distinct Sort (inserter) New node indicating early aggregation algorithm is used.

Distinct Sort (retriever) New node indicating early aggregation algorithm is used.

Grouping Sort (inserter) New node indicating early aggregation algorithm is used.

Grouping Sort (retriever) New node indicating early aggregation algorithm is used.




Join (Asymmetric Sort-Merge) New node indicating an asymmetric sort-merge join is used.

Join (Asymmetric Sort-Merge PushDown) New node indicating an asymmetric sort-merge join is used.

Order By (Full Rewind) New node indicating an asymmetric sort-merge join is used. Displays on the right branch of a Join (Asymmetric Sort-Merge) node.

Order By (Per-Work-Unit) New node indicating an operator that performs a sort on a work-unit worth of data. For example, it displays on the left branch under a Join (Asymmetric Sort-Merge) node.


● Reference: Statements and Options > Database Options > Alphabetical List of Options > QUERY_DETAIL Option

● Reference: Statements and Options > Database Options > Alphabetical List of Options > QUERY_NAME Option

● Reference: Statements and Options > Database Options > Alphabetical List of Options > QUERY_PLAN Option

● Reference: Statements and Options > Database Options > Alphabetical List of Options > QUERY_PLAN_AFTER_RUN Option

● Reference: Statements and Options > Database Options > Alphabetical List of Options > QUERY_PLAN_AS_HTML Option

● Reference: Statements and Options > Database Options > Alphabetical List of Options > QUERY_PLAN_AS_HTML_DIRECTORY Option

● Reference: Statements and Options > Database Options > Alphabetical List of Options > QUERY_PLAN_MIN_TIME

● Reference: Statements and Options > Database Options > Alphabetical List of Options > QUERY_PLAN_TEXT_ACCESS Option

● Reference: Statements and Options > Database Options > Alphabetical List of Options > QUERY_PLAN_TEXT_CACHING Option

● Reference: Statements and Options > Database Options > Alphabetical List of Options > QUERY_ROWS_RETURNED_LIMIT Option

● Reference: Statements and Options > Database Options > Alphabetical List of Options > QUERY_TEMP_SPACE_LIMIT Option

● Reference: Statements and Options > Database Options > Alphabetical List of Options > QUERY_TIMING Option


Related Information

Backward Compatibility: Changes to Default Behavior [page 113]



Backward Compatibility: Migration Considerations [page 116]Connection Changes [page 118]Database Option Changes [page 120]JRE and Java Runtime Environment Variable Changes [page 126]Logical Server Policy Option Changes [page 127]Login Policy Option Changes [page 128]ODBC Driver Changes [page 129]SQL Function Changes [page 132]SQL Statement Changes [page 133]Stored Procedure Changes [page 140]Table and View Changes [page 146]Utility Option Changes [page 149]Database Option Changes [page 120]DQP Performance Improvements [page 100]

10.6.10 SQL Function Changes

Function changes for SAP IQ 16.0.

Table 5: System Functions

Function Description

sp_has_role New function. Returns an integer value indicating whether the invoking user has been granted a specified system privilege or user-defined role. When used for checking within user-defined stored procedures, this function can display an error message when a user fails a check.

See Reference: Building Blocks, Tables, and Procedures > SQL Functions > Alphabetical List of Functions> sp_has_role Function [System].


Related Information

Backward Compatibility: Changes to Default Behavior [page 113]Backward Compatibility: Migration Considerations [page 116]Connection Changes [page 118]Database Option Changes [page 120]JRE and Java Runtime Environment Variable Changes [page 126]Logical Server Policy Option Changes [page 127]Login Policy Option Changes [page 128]ODBC Driver Changes [page 129]Query Plan Changes [page 130]



SQL Statement Changes [page 133]Stored Procedure Changes [page 140]Table and View Changes [page 146]Utility Option Changes [page 149]Discontinued Time Series SQL Functions [page 105]

10.6.11 SQL Statement Changes

Syntax changes for SAP IQ 16.0.


ALTER DATABASE New clauses:

● RESTART prevents the database from automatically restarting after an upgrade.● SYSTEM PROCEDURE AS DEFINER defines whether to execute system procedures that

perform privileged tasks with the privileges of the invoker (the person calling the procedure) or the definer (the owner of the procedure).○ OFF means all system procedures execute with the privileges of the invoker.○ ON (default), or not specified means pre-16.0 system procedures execute with the

privileges of the definer and 16.0 or later system procedures execute with the privileges of the invoker.

See Reference: Statements and Options > SQL Statements > ALTER DATABASE

ALTER LDAP SERVER

New statement to modify the defined properties for the LDAP server.

See Reference: Statements and Options > SQL Statements > ALTER LDAP SERVER Statement.

ALTER LOGICAL SERVER

New clauses:

● POLICY clause associates a logical server with a user-defined logical server policy.● WITH STOP SERVER clause automatically shuts down all servers in the logical server.

AUTO is now a reserved logical server name.

See Reference: Statements and Options > SQL Statements > ALTER LOGICAL SERVER Statement.

ALTER LOGIN POLICY

New clauses:

● DEFAULT_LOGICAL_SERVER sets the target logical server context if you omit LogicalServer from the connection string.

● LDAP_PRIMARY_SERVER, LDAP_SECONDARY_SERVER, LDAP_AUTO_FAILBACK_PERIOD, LDAP_FAILOVER_TO_STD, and LDAP_REFRESH_ON allow the defining of SAP IQ LDAP user authentication related properties in login policies.

● ROOT_AUTO_LOCK_TIME (root login policy only) and AUTO_UNLOCK_TIME let you define user account management related properties in login policies.

● CHANGE_PASSWORD_DUAL_CONTROL requires input from two users, each granted the CHANGE PASSWORD system privilege, to change the password of another user.

See Reference: Statements and Options > SQL Statements > ALTER LOGIN POLICY




ALTER LS POLICY You can alter user-created policies to control the behavior of associated logical servers in your multiplex. Enable login redirection, specify which nodes in a logical server are available for processing queries, the placement of temporary table data, and how many connections can queue before redirection. New options DQP_ENABLED, LOGIN_REDIRECTION, REDIRECTION_WAITERS_THRESHOLD, and TEMP_DATA_IN_SHARED_TEMP added.

New WITH STOP SERVER clause automatically shuts down all servers in the logical server.

This statement can also alter the root ls policy to change the value of different ls policy options.

See Reference: Statements and Options > SQL Statements > ALTER LS POLICY Statement.

ALTER ROLE New statement lets you migrates a compatibility role to a user-defined system role, then automatically drops the compatibility role.

See Reference: Statements and Options > SQL Statements > ALTER ROLE Statement.

ALTER TABLE New syntax extensions enable you to either register the table with the RLV store for real-time in-memory updates, or disable RLV storage.

New syntax supports changing a table owner.

See Reference: Statements and Options > SQL Statements > ALTER TABLE Statement.

ALTER USER New REFRESH_DN clause lets you clear the saved DN and timestamp for a user, which is used during SAP IQ LDAP user authentication.

See Reference: Statements and Options > SQL Statements > ALTER USER.

COMMENT ON New LDAP_SERVER clause lets you create a comment on a SAP IQ LDAP server object.

See Reference: Statements and Options > SQL Statements > COMMENT.

COMMENT ON LS POLICY

New clause allows comment to document the purpose or guidelines for using new user-defined logical server policies.

See Reference: Statements and Options > SQL Statements > COMMENT ON LS POLICY Statement.

CREATE DATABASE New SYSTEM PROCEDURE AS DEFINER clause defines whether to execute system procedures that perform privileged tasks with the privileges of the invoker (the person calling the procedure) or the definer (the owner of the procedure).

● OFF (default), or not specified means all system procedures execute with the privileges of the invoker.

● ON means pre-16.0 system procedures execute with the privileges of the definer and 16.0 or later system procedures execute with the privileges of the invoker.

CREATE DBSPACE New syntax extension for creating an RLV store dbspace.

See Reference: Statements and Options > SQL Statements > CREATE DBSPACE Statement.

CREATE LDAP SERVER

New statement to create a new LDAP server for LDAP user authentication.

See Reference: Statements and Options > SQL Statements > CREATE LDAP SERVER Statement.




CREATE LOGICAL SERVER

New POLICY clause associates a logical server with a user-defined logical server policy. AUTO is now a reserved logical server name.


See Reference: Statements and Options > SQL Statements > CREATE LOGICAL SERVER Statement.

CREATE LOGIN POLICY

New clauses:

● DEFAULT_LOGICAL_SERVER sets the target logical server context if you omit LogicalServer from the connection string.

● LDAP_PRIMARY_SERVER, LDAP_SECONDARY_SERVER, LDAP_AUTO_FAILBACK_PERIOD, LDAP_FAILOVER_TO_STD, and LDAP_REFRESH_ON allow the defining of SAP IQ LDAP user authentication related properties in login policies.

● ROOT_AUTO_LOCK_TIME (root login policy only) and AUTO_UNLOCK_TIME let you define user account management related properties in login policies.

● CHANGE_PASSWORD_DUAL_CONTROL requires input from two users, each granted the CHANGE PASSWORD system privilege, to change the password of another user.

See Reference: Statements and Options > SQL Statements > CREATE LOGIN POLICY.

CREATE LS POLICY New statement lets you create your own policies to control the behavior of associated logical servers in your multiplex. Enable login redirection. Specify which nodes in a logical server are available for processing queries, the placement of temporary table data, and how many connections can queue before redirection.

New options DQP_ENABLED, LOGIN_REDIRECTION, REDIRECTION_WAITERS_THRESHOLD, and TEMP_DATA_IN_SHARED_TEMP added.

See Reference: Statements and Options > SQL Statements > CREATE LS POLICY Statement.

CREATE ROLE New statement lets you create a new user-defined role, extends an existing user to act as a role, or manages role administrators on a role.

See Reference: Statements and Options > SQL Statements > CREATE ROLE Statement.




CREATE TABLE New syntax enables you to register the table with the RLV store.

CREATE [ GLOBAL TEMPORARY ] TABLE <<table-name>> { ENABLE | DISABLE } RLV STORE

New syntax extensions support range, hash, and hash-range partitioning schemes:

<partitioning-scheme:> { <range-partitioning-scheme> | <hash-partitioning-scheme> | <hash-range-partitioning-scheme> }

Hash partitioning maps data to partitions based on the composite value of a set of partition key columns and an internal hash function. Hash partitioning distributes data to partitions based on composite value of a set of partition key columns, which can enhance query join performance on a large table. Hash-range partitioning is a composite partitioning scheme that distributes data to partitions based on the composite value of a set of partition key columns, an internal hash function, and range sub-partition. Hash-range partitioning maps data to sub-partitions based on a range of sub-partition key values.

See Reference: Statements and Options > SQL Statements > CREATE TABLE Statement.

DECLARE LOCAL TEMPORARY TABLE

New syntax enables you to register the table with the RLV store.

See Reference: Statements and Options > SQL Statements > DECLARE LOCAL TEMPORARY TABLE Statement.

DROP LDAP SERVER New statement lets you remove an LDAP server from the database after verifying that it is not in a READY or ACTIVE state.

See Reference: Statements and Options > SQL Statements > DROP LDAP SERVER.

DROP LOGICAL SERVER


See Reference: Statements and Options > SQL Statements > DROP LOGICAL SERVER

DROP LS POLICY New statement lets you delete the policy if a user-defined policy is not currently used for any logical server. You cannot drop the root policy.

See Reference: Statements and Options > SQL Statements > DROP LS POLICY Statement.

DROP ROLE New statement lets you remove a user-defined role from the database at any time as long as all dependent roles will are left with the minimum required number of administrator users with active passwords.

See Reference: Statements and Options > SQL Statements > DROP ROLE.




INSERT New INSERT...VALUES support for (DEFAULT), DEFAULT VALUES or VALUES() clauses that insert rows with all default values. Assuming that there are 3 columns in table t2, these examples are semantically equivalent:

INSERT INTO t2 values (DEFAULT, DEFAULT, DEFAULT);

INSERT INTO t2 DEFAULT VALUES;

INSERT INTO t2() VALUES();

INSERT...VALUES also supports multiple rows. The following example inserts 3 rows into table t1:

CREATE TABLE t1(c1 varchar(30)); INSERT INTO t1 VALUES ('morning'),('afternoon'), ('evening');

SAP IQ treats all load/inserts as full-width inserts. Columns not explicitly specified on the load/insert statement, the value loaded will either be the column DEFAULT value for the column (if defined) or NULL (if no DEFAULT value is defined).

INSERT no longer supports the START ROW ID option. A LOAD or INSERT statement can still include this option, but SAP IQ will ignore the value.

INSERT/SELECT from an empty table that has a data type mismatch with the target table returns an error rather than not reporting the mismatch.

You can use the statement to insert data into an RLV-enabled table.

See Reference: Statements and Options > SQL Statements > INSERT Statement.

LOAD TABLE SAP IQ treats all load/inserts as full-width inserts. Columns not explicitly specified on the LOAD/INSERT statement, the value loaded will either be the DEFAULT value for the column (if defined) or NULL (if the column has no DEFAULT value).

LOAD TABLE no longer supports the START ROW ID option. LOAD or INSERT statements can still include START ROW ID, but SAP IQ will ignore the value.

The load engine no longer supports files in which input rows span file boundaries. A partial input row that occurs at the end of any file will now be treated according to the ON PARTIAL INPUT ROW setting.

LOAD TABLE no longer supports UNLOAD FORMAT syntax.

You can use the statement to load a file into an RLV-enabled table.

The default value of the LOAD TABLE NOTIFY clause was 100000 prior to release 16.0. In SAP IQ 16.0 the default has changed to 0, meaning no notifications are printed by default.

See Reference: Statements and Options > SQL Statements > LOAD TABLE Statement.




INSERT..SELECT Prior to SAP IQ 16.0, attempting to use INSERT..SELECT on only NULL values when the source and target data types mismatched inserted the NULL values even when explicit conversion was required. Now SAP IQ will properly enforce that explicit conversion is required and correctly return the error Unable to implicitly convert column <name> from data type <type>.

For example:

CREATE TABLE t_int(c1 INT null); CREATE TABLE t_char(c1 CHAR(5) null);INSERT INTO t_int values (NULL); INSERT INTO t_char select * from t_int;

Prior to 16.0, a NULL value would be inserted into t_char. Starting in 16.0, the required conversion error will occur. To use explicit conversion use CAST or CONVERT, for example:

INSERT INTO t_char select cast(c1 as char(5)) from t_int;

See Reference: Statements and Options > SQL Statements > INSERT Statement.

GRANT/REVOKE <database object permissions>

New clauses. You can grant and revoke the TRUNCATE and LOAD object permissions to users and roles.

See Reference: Statements and Options > SQL Statements > GRANT Database Object Permissions.

See Reference: Statements and Options > SQL Statements > REVOKE Database Object Permissions.

GRANT/REVOKE <system privilege>

New statements let you grant and revoke of specific system privileges to specific users, with or without administrative rights.

See Reference: Statements and Options > SQL Statements > GRANT System Privilege Statement.

See Reference: Statements and Options > SQL Statements > REVOKE System Privilege Statement.

GRANT/REVOKE CHANGE PASSWORD

New statement that lets you allow users to manage passwords for other users and administer the CHANGE PASSWORD system privilege.

See Reference: Statements and Options > SQL Statements > GRANT CHANGE PASSWORD Statement.

See Reference: Statements and Options > SQL Statements > REVOKE CHANGE PASSWORD Statement.

GRANT/REVOKE SET USER

New statements that allow you to grant and revoke the ability for one user to impersonate another user and administer the SET USER system privilege.

See Reference: Statements and Options > SQL Statements > GRANT SET USER Statement.

See Reference: Statements and Options > SQL Statements > REVOKE SET USER Statement.




GRANT/REVOKE ROLE

New statements that allow you to grant and revoke roles to users or other roles, with or without administrative rights.

See Reference: Statements and Options > SQL Statements > GRANT ROLE Statement.

See Reference: Statements and Options > SQL Statements > REVOKE ROLE Statement.

SELECT New FOR JSON clause lets you execute an SQL statement against your database and return the results as a JSON document.

TRUNCATE TABLE New syntax extension let you TRUNCATE partitions in hash partitioned and hash-range partitioned tables.

See Reference: Statements and Options > SQL Statements > TRUNCATE TABLE Statement.

VALIDATE LDAP SERVER

New statement allows the validation of proposed changes to the settings of existing LDAP servers before applying them.

See Reference: Statements and Options > SQL Statements > VALIDATE LDAP SERVER Statement.


Related Information

Backward Compatibility: Changes to Default Behavior [page 113]Backward Compatibility: Migration Considerations [page 116]Connection Changes [page 118]Database Option Changes [page 120]JRE and Java Runtime Environment Variable Changes [page 126]Logical Server Policy Option Changes [page 127]Login Policy Option Changes [page 128]ODBC Driver Changes [page 129]Query Plan Changes [page 130]SQL Function Changes [page 132]Stored Procedure Changes [page 140]Table and View Changes [page 146]Utility Option Changes [page 149]



10.6.12 Stored Procedure Changes

The initial 16.0 version includes catalog stored procedure and system stored procedure changes.

Table 6: Catalog Stored Procedures


sa_get_ldapserver_status New procedure. Allows you to determine the current status of the LDAP server configuration object.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of Catalog Stored Procedures > sa_get_ldapserver_status System Procedure.

sa_get_user_status New output information. For LDAP user authentication, output includes the distinguished name (DN) for the user and the date and time the distinguished name was found. For dual control password management, output includes current status of a dual control password change, and if active, the user IDs of the two administrators performing the change.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of Catalog Stored Procedures > sa_get_user_status System Procedure.

sa_make_object Behavior change. Previously, the sa_make_object system procedure required RESOURCE authority and could be used to create objects owned by other users, even though RESOURCE authority didn't actually give a user permissions to create objects owned by others. For example, if a user with RESOURCE authority attempted to execute the equivalent CREATE statement, the statement would fail.

Now, when using sa_make_object, you must have all appropriate privileges required to create objects owned by self or others. The actual privileges you need depend on the creation operation you are performing.

sa_report_deadlocks New procedure. Retrieves information about deadlocks from an internal buffer created by the database server.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of Catalog Stored Procedures > sa_report_deadlocks System Procedure.

sa_server_option Behavior change. New parameters added: rlv_auto_merge and rlv_memory_mb.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of Catalog Stored Procedures > sa_server_option System Procedure.

sp_auth_sys_role_info New procedure. Generates a report that maps legacy authorities to corresponding system roles and role IDs. This procedure returns a row for each authority.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of Catalog Stored Procedures > sp_auth_sys_role_info System Procedure.




sp_alter_secure_feature_key New procedure. Alters a previously-defined secure feature key by modifying the authorization key and/or the feature list.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of Catalog Stored Procedures > sp_alter_secure_feature_key system procedure.

sp_create_secure_feature_key New procedure. Creates a new secure feature key.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of Catalog Stored Procedures > sp_create_secure_feature_key system procedure.

sp_displayroles New procedure. Displays all roles granted to a user-defined role or a user, or displays the entire hierarchical tree of roles.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of Catalog Stored Procedures > sp_displayroles System Procedure.

sp_drop_secure_feature_key New procedure. Deletes a secure feature key.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of Catalog Stored Procedures > sp_drop_secure_feature_key system procedure.

sp_list_secure_feature_keys New procedure. Returns a list of defined secure feature keys.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of Catalog Stored Procedures > sp_list_secure_feature_keys system procedure.

sp_objectpermission New procedure. Generates a report on object permissions granted to the specified role or user name or object permissions granted on the specified object or dbspace.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of Catalog Stored Procedures> sp_objectpermission System Procedure.

sp_proc_priv New procedure. Generates a report of the minimum system privileges required to run a stored procedure and pass the permission check for the procedure.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of Catalog Stored Procedures > sp_proc_priv system procedure.

sp_sys_priv_role_info New procedure. Generates a report to map system privileges to corresponding system roles and role IDs. A singe row is returned for each system privilege.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of Catalog Stored Procedures > sp_sys_priv_role_info System Procedure.




sp_use_secure_feature_key New procedure. Enables an existing secure feature key.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of Catalog Stored Procedures > sp_use_secure_feature_keys system procedure.

Table 7: System Stored Procedures


sp_iqcardinality_analysis sp_iqcardinality_analysis no longer returns an index type value or index recommendation. Users are advised to Run Index Advisor for suggestions about additional column indexes. sp_iqcardinality_analysis is deprecated and will be removed in a future release.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqcardinality_analysis.

sp_iqcolumn Behavior change. sp_iqcolumn no longer includes est_cardinality as part of the output.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqcolumn.

sp_iqcolumnmetadata New procedure. Returns index metadata for all columns in one or more tables.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqcolumnmetadata.

sp_iqconnection New columns added to display the name of the underlying INC connection and connection suspension status.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqconnection.

sp_iqdbsize New columns RLVLogBlocks and RLVLogBytes added.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqdbsize.

sp_iqdbspace The DBSpace Type column now displays RLV.

Block Type R (RLV Free List Manager) is added to the BlkTypes block type identifiers.

The Stripingon column is now always F.

The StripeSize column is now always 1.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqdbspace.




sp_iqdbspaceinfo This stored procedure is not supported for RLV dbspaces. The procedure returns no results if you specify an RLV dbspace.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqdbspaceinfo.

sp_iqdbspaceobjectinfo This stored procedure is not supported for RLV dbspaces. The procedure returns no results if you specify an object located in an RLV dbspace.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqdbspaceobjectinfo.

sp_iqemptyfile This stored procedure is not supported for RLV dbspaces. The procedure returns an error message f you specify a file located in an RLV dbspace.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqemptyfile.

sp_iqfile The SegmentType column now displays RLV.

Block Type R (RLV Free List Manager) is added to the BlkTypes block type identifiers.

The RWMode column is now always RW.

The StripeSize column is now always 1.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqfile.

sp_iqindexmetadata Behavior change. Returns details about column indexes, column constraints, and NBit dictionary size. New HG index output columns include Cardinality Range Min - Max, Estimated Cardinality, Accuracy of Cardinality, and Force Physical Delete.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqindexmetadata.

sp_iqindexrebuildwidedata() New procedure. Identifies wide columns in migrated databases that you must rebuild before they are available for read/write activities.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqindexrebuildwidedata().

sp_iqlocks Behavior change. Support for write-intent locks and row-level locks for RLV.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqlocks.




sp_iqmergerlvstore New procedure. Triggers a merge of the row-level versioned (RLV) store with the IQ main store.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqmergerlvstore.

sp_iqmpxincstatistics New procedure. Displays a snapshot of the aggregate statistics of internode communication (INC) status since server startup as of the moment of execution.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures >sp_iqmpxincstatistics.

sp_iqmpxsuspendedconninfo New procedure. Shows details about currently suspended connections and transactions on the coordinator node.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqmpxsuspendedconninfo .

sp_iqrebuildindex Behavior changes. Rebuilds FP indexes (Flat FP as NBit, or NBit as Flat FP); HG indexes (single HG as tiered HG, or tiered HG as single HG); LOB data and columns greater than 255 bytes wide.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqrebuildindex.

sp_iqrlvmemory New procedure. Monitors RLV store memory usage per table.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqrlvmemory.

sp_iqrowdensity Behavior change. Returns 1.0 for density in all cases.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqrowdensity.

sp_iqspaceused New columns rlvLogKB and rlvLogKBUsed added.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqspaceused.

sp_iqstatistics Behavior change. OperationsActiveLoadTableStatements statistic now returns correct value.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqstatistics.

sp_iqstatus New output rows:

● RLV memory limit● RLV memory used

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqstatus.




sp_iqtable New PartitionType column indicates table partition type (Range, Hash, Hash-Range, None).

New isRLV column indicates if the table is RLV-enabled.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqtable.

sp_iqtablesize New columns RlvLogPages and RlvLogKBytes added.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqtablesize.

sp_iqtransaction New VersioningType, Blocking, and Blocking Timeout columns.

See Reference: Building Blocks, Tables, and Procedures > System Procedures > Alphabetical List of System Stored Procedures > sp_iqtransaction.


Related Information

Backward Compatibility: Changes to Default Behavior [page 113]Backward Compatibility: Migration Considerations [page 116]Connection Changes [page 118]Database Option Changes [page 120]JRE and Java Runtime Environment Variable Changes [page 126]Logical Server Policy Option Changes [page 127]Login Policy Option Changes [page 128]ODBC Driver Changes [page 129]Query Plan Changes [page 130]SQL Function Changes [page 132]SQL Statement Changes [page 133]Table and View Changes [page 146]Utility Option Changes [page 149]Deprecated Stored Procedures [page 110]



10.6.13 Table and View Changes

SAP IQ 16.0 includes new and changed system tables and views.

New System Tables

System Table Contains

ISYSIQMPXSERVERAGENT New table. Stores agent connection definitions for the given multiplex server.

ISYSIQPARTITIONCOLUMN One row for each column of a partition described in ISYSPARTITION view in a partitioned table described in the ISYSPARTITIONSCHEME view.

See Reference: Building Blocks, Tables, and Procedures > System Tables and Views > System Views > SYSPARTITION System View for details.

ISYSIQRLVMERGEHISTORY New table logging RLV merge events from the RLV store to the IQ main store. A log entry is added for each row-level versioning (RLV) enabled-table each time a merge between the RLV store and the IQ main store begins. Log entries are updated when the merge is complete.

See Reference: Building Blocks, Tables, and Procedures > System Tables and Views > System Views > SYSIQRLVMERGEHISTORY System View for details.

ISYSIQRVLOG New table tracking RLV log streams.

See Reference: Building Blocks, Tables, and Procedures > System Tables and Views > System Views > SYSIQRVLOG System View for details.

ISYSCERTIFICATE New table storing certificates in text PEM-format.

See Reference: Building Blocks, Tables, and Procedures > System Tables and Views > System Views > SYSCERTIFICATE System View for details.

ISYSLDAPSERVER Contains attributes for the LDAP server.

See Reference: Building Blocks, Tables, and Procedures > System Tables and Views > Alphabetical List of System Views > SYSLDAPSERVER.

ISYSPARTITION One row for each range subpartition of a hash-range partitioned table. Because Hash partitions are logical rather than physical objects, ISSYPARTITION will not contain any rows for hash partitions of hash partitioned table or hash-range partitioned table.

See Reference: Building Blocks, Tables, and Procedures > System Tables and Views > System Views > SYSPARTITION System View for details.

ISYSPARTITIONKEY* One row for each column of a partition key.

See Reference: Building Blocks, Tables, and Procedures > System Tables and Views > System Views > SYSPARTITIONKEY System View for details.



System Table Contains

ISYSPARTITIONSCHEME One row for each hash partitioned table and each hash-range partitioned table. The hash function and the number of hash partitions per table is fixed for the database and is not stored as part of this table.

See Reference: Building Blocks, Tables, and Procedures > System Tables and Views > System Views > SYSPARTITIONSCHEME System View for details.

ISYSROLEGRANTEXT New table containing syntax extensions pertaining to the SET USER and CHANGE PASSWORD system privileges.

See Reference: Building Blocks, Tables, and Procedures > System Tables and Views > Alphabetical List of System Views > SYSROLEGRANTEXT.

ISYSROLEGRANT New table containing one row for each grant of a system or user-defined role.

See Reference: Building Blocks, Tables, and Procedures > System Tables and Views > Alphabetical List of System Views > SYSROLEGRANT.

ISYSSUBPARTITIONKEY* One row for each column of a subpartition key.

See Reference: Building Blocks, Tables, and Procedures > System Tables and Views > System Views > SYSSUBPARTITIONKEY System View for details.

Note*ISYSPARTITIONKEY and ISYSSUBPARTITIONKEY share identical schemas.

Changed System Tables


ISYSIQDBSPACE New column is_rlv_store indicating if the dbspace is a RLV store dbspace.

See Reference: Building Blocks, Tables, and Procedures > System Tables and Views > System Views > SYSIQDBSPACE System View for details.

ISYSIQIDX Removed columns:

● link_table_id● link_column_id

ISYSIQTAB New column is_rlv indicating if RLV storage is enabled on this table.

Removed column join_id.

See Reference: Building Blocks, Tables, and Procedures > System Tables and Views > System Views > SYSIQTAB System View for details.




ISYSIQTABCOL Removed columns:

● link_table_id● link_column_id● has_original● original_not_null● original_unique

Added column is_nbit

ISYSTABLEPERM Column loadauth and truncateauth added to indicate current grant status of the object privileges.

See Reference: Building Blocks, Tables, and Procedures > System Tables and Views > Alphabetical List of System Views > SYSTABLEPERM.

ISYSUSER Columns for user_dn and user_dn_cached_at added for LDAP user authentication. Column user_type added to identify user type for RBAC. Column dual_password added for the first and second parts of the dual password for a user.

See Reference: Building Blocks, Tables, and Procedures > System Tables and Views > Alphabetical List of System Views > SYSUSER.


Related Information

Backward Compatibility: Changes to Default Behavior [page 113]Backward Compatibility: Migration Considerations [page 116]Connection Changes [page 118]Database Option Changes [page 120]JRE and Java Runtime Environment Variable Changes [page 126]Logical Server Policy Option Changes [page 127]Login Policy Option Changes [page 128]ODBC Driver Changes [page 129]Query Plan Changes [page 130]SQL Function Changes [page 132]SQL Statement Changes [page 133]Stored Procedure Changes [page 140]Utility Option Changes [page 149]Discontinued Tables and Views [page 107]Deprecated System Tables and Views [page 111]



10.6.14 Utility Option Changes

The initial 16.0 version includes option changes for the isql and start_iq utilities.

Table 8: isql Changes

Option Description

--URP New option for the Interactive SQL utility (isql). Allows you to specify a remote password and provides TDS login redirection for logical servers.

See Utility Guide > isql Interactive SQL Utility..

Table 9: start_iq Changes

Utility Description

-al New option for the start_iq utility, -al allows you to extend authentication to select users using standard authentication. This may be necessary when the <login_mode> database options are restricted to SAP IQ LDAP user authentication (LDAPUA) only, but no user or login policy exists that permits LDAPUA authentication.

See start_iq > -al iqsrv16 Server Option or start_iq > -al iqsrv16 Database Option under start_iq Database Server Startup Utility in the Utility Guide .

-iqlm New option. The –iqlm startup option specifies the maximum amount of memory that SAP IQ can dynamically request from OS for temporary use. Set –iqlm as a switch as part of the command or configuration file that starts the server.

Default large memory is 2048MB. Large memory requirements represent one third of the total available physical memory. 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 memory.

See Utility Guide > start_iq Database Server Startup Utility > start_iq Server Options > -iqlm iqsrv16 Server Option.

–iqmc Behavior change. Default memory for –iqmc is 64MB.

Large memory requirements are one third of all available physical memory. To ensure adequate memory for the main store, set the –iqmc startup parameter to one third of available physical memory.

See Utility Guide > start_iq Database Server Startup Utility > start_iq Server Options > -iqmc iqsrv16 Server Option.

-iqrlvmem New option. Server startup argument to govern the RLV store memory usage. Only used if RLV storage is enabled. The default is 2GB.



Utility Description

–iqtc Behavior change. Default memory for –iqtc is 64MB.

Large memory requirements are one third of all available physical memory. To ensure adequate memory for the IQ temporary store cache, set the –iqtc startup parameter to one third of available physical memory.

See Utility Guide > start_iq Database Server Startup Utility > start_iq Server Options > -iqtc iqsrv16 Server Option.

-sf New feature set. manage_keys added to the manage_security feature set for the start_iq -sf option. Allows you to specify which features you want to secure for databases running on the database server.


Related Information

Backward Compatibility: Changes to Default Behavior [page 113]Backward Compatibility: Migration Considerations [page 116]Connection Changes [page 118]Database Option Changes [page 120]JRE and Java Runtime Environment Variable Changes [page 126]Logical Server Policy Option Changes [page 127]Login Policy Option Changes [page 128]ODBC Driver Changes [page 129]Query Plan Changes [page 130]SQL Function Changes [page 132]SQL Statement Changes [page 133]Stored Procedure Changes [page 140]Table and View Changes [page 146]

10.7 Administration Tool Changes

Sybase Central is replaced by SAP Control Center (SCC).

In this section:

SAP Control Center Changes [page 151]The SAP IQ plug-in for SAP Control Center 3.2.7 provides complete administration and management functionality. SAP Control Center (initally released as Sybase Control Center) replaces the Sybase Central administration tool.



10.7.1 SAP Control Center Changes

The SAP IQ plug-in for SAP Control Center 3.2.7 provides complete administration and management functionality. SAP Control Center (initally released as Sybase Control Center) replaces the Sybase Central administration tool.

Brief descriptions of new and enhanced features in SCC 3.2.7:

Table 10: SAP Control Center Changes


External Environments External environment administration – In previous releases, only the Java external environment was supported. In SCC 3.2.7, you can administer these external environments: ODBC, ESQL, .NET, Java, Perl, PHP.

Tables Table administration – Perform table management tasks such as creating/deleting a base table and moving a table to another dbspace.

● Creating/deleting a base table● Creating/deleting a global temporary table● Creating/deleting a proxy table● Modifying table properties● Moving a table to another dbspace● Managing table columns● Managing table constraints● Managing table indexes● Managing table partitions● Managing IQ catalog store (system store) table triggers● Generating table DDL commands● Viewing table data in the Execute SQL window

SAP IQ server and SCC agent logs

View and filter logs, copy and paste from log snapshots.

The log displays as a static snapshot that does not refresh automatically.

Domains Domain administration – Create, view and update domains. The Administration Console tree lists domains under schema objects.




Views View administration – Perform view management tasks such as creating a view and recompiling a materialized view.

● Creating a view● Modifying a view● Disabling a view● Recompiling and enabling a view● Deleting a view● Generating view DDL commands● Managing triggers on an IQ catalog store (system store) view● Listing materialized views● Creating a materialized view● Modifying a materialized view● Validating materialized view data● Refreshing materialized view data● Truncating materialized view data● Setting a clustered index on a materialized view● Disabling a materialized view● Recompiling a materialized view● Generating materialized view DDL commands● Managing triggers on a materialized view

Web Services Web service administration – Perform web service management tasks such as creating, modifying, and deleting web services.

● Creating a Web service● Enabling a Web service● Disabling a Web service● Modifying a Web service● Deleting a Web service● Generating Web service DDL commands

Logical Servers Logical server support has been enhanced as follows:

● When you authenticate a multiplex server resource, SCC automatically generates one logical server resource per logical server, if one does not already exist. SCC sets the resource name to the multiplex name followed by a colon and the logical server name. For example, myMPX1:MyLS1.

● Create, edit, and delete logical server policies to control logical server access and context.

● Monitor logical servers from the Perspective Resources View, Heat Chart, or Administration Console.

● For better load balancing, SAP IQ can now redirect new multiplex logins to a node with a lighter load in the same logical server.

● Two generated administration scripts include new connection parameters in the connection string:○ stop_server.sh (.bat) includes LS=SERVER

○ sync_server.sh (.bat) includes LS=COORDINATOR




Login Mappings Login mappings – Map a Windows user profile or a Kerberos principal to an existing user in the database to maintain a single user ID for database connections, operating system, and network logins.

Transport layer security for multiplex

Transport layer security – Configure transport layer security with RSA encryption in a multiplex environment.

Global Transaction Resiliency Global transaction resiliency – Monitor the suspended, resumed, and rolled back status of INC (internode communication) connections for global transactions.

Row-level Versioning Row-level Versioning (RLV) – Use the new RLV data store in your simplex database to perform row-level updates, inserts, and deletes, in real-time. When a table is enabled for storage in the RLV data store, multiple users can write to different rows of the table concurrently.

Remote Access Remote Access – Access data from other data sources by creating Remote Server definitions, Proxy Tables, Remote Procedures and External Logins.

LDAP Server LDAP server administration - Create, modify, and delete LDAP servers.

Role-Based Security Role-based security administration – Perform user and role management for role-based users, user-extended roles, and standalone roles. Tasks include create, modify and delete, as well as grant and revoke system privileges and object permissions to users and roles.

Triggers on Views View trigger administration – Create, modify, and delete triggers on views.

Sequence Generator Sequence Generator administration - Create, modify, and delete sequence generators.

Related Information

Discontinued Tools and Utilities [page 107]SAP Control Center [page 80]



10.8 Documentation Collection Changes

The SAP IQ 16.0 documentation collection contains new documentation, redesigned manuals, and retitled manuals. This topic helps you locate content in the 16.0 collection.

Table 11: Documentation Collection Changes in SAP IQ 16.0

Location in 15.4 Collection New Location in 16.0 Collection

● Sybase Central online help ● SAP Control Center online help, available from:○ The SCC GUI○ The SAP IQ documentation collection

● System Administration Guide: Volume 1● System Administration Guide: Volume 2

● Administration: Database● Administration: Backup, Restore, and Data Recovery● Administration: Globalization● Administration: User Management and Security● Administration: Load Management● Programming

● Advanced Security ● Administration: User Management and Security > Advanced Security Options in SAP IQ

● Using Sybase IQ Multiplex ● Administration: Multiplex

● Installation and Configuration Guide for HP-UX > Database Upgrades

● Installation and Configuration Guide for AIX > Database Upgrades

● Installation and Configuration Guide for Linux > Database Upgrades

● Installation and Configuration Guide for Solaris > Database Upgrades

● Installation and Configuration Guide for Windows > Database Upgrades

● Migration (Linux and UNIX)● Migration (Windows)

In this section:

Documentation (deprecated) [page 155]Refer to this summary to locate information about specific subject areas.



10.8.1 Documentation (deprecated)

Refer to this summary to locate information about specific subject areas.

New Release Information

Document Name Contents

Installation and Configuration Guide Installation and configuration procedures.

Release Bulletins Late-breaking product information.

Guide to Licensed Options Features you can buy separately.

What's New in SAP IQ 16.0 Release-specific feature summaries.

Getting Started


Introduction to SAP IQ Hands-on introduction to SAP IQ.

Quick Start (UNIX/Linux), Quick Start (Windows) Steps to create and query a SAP IQ demo database.

Migration (UNIX/Linux), Migration (Windows) Steps to install maintenance releases, steps for upgrading your database, and information on upgrading to the role-based security model.

Administration


Administration: Database Database setup and troubleshooting.

Administration: Backup, Restore, and Data Recovery Data preservation strategies.

Administration: Globalization Locales, collations and character set configuration.

Administration: Load Management Data import and export procedures.

Administration: User Management and Security User and Security implementation and administration.

Administration: In-Memory Row-Level Versioning Row-level versioning configuration and administration.

Administration: Spatial Data IQ catalog store spatial data administration.



Reference


Reference: Statements and Options Syntax and parameters for SQL statements and options.

Reference: Building Blocks, Tables, and Procedures SQL, functions, procedures, tables, and views.

Error Messages Error and warning messages.

Utility Guide Command line utility reference.

Performance and Tuning Guide Database, system, and query tuning options.

Programming Developer reference for building and deploying database applications.

Interactive SQL Guide Interactive SQL tasks and reference.

Optional Features


Unstructured Data Analytics Binary Large Object (BLOB) and Character Large Object (CLOB) storage and retrieval.

User-Defined Functions C/C++ interface for user-defined functions.

Administration: Multiplex Multiplex setup and administration.

Administration: User Management and Security Contains Advanced Security option information:

● LDAP User Authentication configuration● Implement Kerberos authentication

Licensing


Sybase Software Asset Management (SySAM) 2 Users Guide

License generation, options, and management.

SySAM 2 Quick Start Guide SPDC and SAP Service Marketplace license generation.

FLEXnet Licensing End User Guide FLEXnet Licensing utilities.



Important Disclaimers and Legal Information

Coding SamplesAny software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

AccessibilityThe information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral LanguageAs far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet HyperlinksThe SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://help.sap.com/disclaimer).

What's New in SAP IQ 16.0Important Disclaimers and Legal Information


http://help.sap.com/disclaimer/

go.sap.com/registration/contact.html

© 2016 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 http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

https://go.sap.com/registration/contact.html

https://go.sap.com/registration/contact.html

http://www.sap.com/corporate-en/legal/copyright/index.epx

http://www.sap.com/corporate-en/legal/copyright/index.epx

what's new in sap iq 16 · new features were introduced in sap® iq 16.0 sp 10. if you are...

Documents