SAP IQ Release Bulletin Linux SAP IQ 16.0 SP10

SAP IQ Release Bulletin Linux SAP IQ 16.0 SP10
PUBLIC
SAP IQ 16.0 SP10
Document Version: 1.2 – 2016-04-13
SAP IQ Release Bulletin
Linux
Content
1
Important SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2
Product Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1
Product Compatibilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2
Network Clients and ODBC Kits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3
Installation and Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1
Problem Solutions from Earlier Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
3.2
Database Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3
SAP IQ and Other SAP Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4
Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1
Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.2
Known Issues for Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.3
Known Issues for SAP IQ Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
SAP IQ Operations Known Issues from Previous Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.4
Known Issues for Interactive SQL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.5
Known Issues for Multiplex Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5
Documentation Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.1
Programming Documentation Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6
Obtaining Help and Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
6.1
Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
SAP Support Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
EBFs and Maintenance Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Platform Certifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Developer Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.2
Information for Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.3
Checklist: Information for Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
2
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
SAP IQ Release Bulletin
Content
1
Important SAP Notes
Read the following SAP Notes before you start the installation. These SAP Notes contain the latest information
about the installation, as well as corrections to the installation documentation.
Make sure that you have the most up-to-date version of each SAP Note, which you can find on SAP Service
Marketplace at https://service.sap.com/notes .
SAP Note Number
Title
2165297
SAP IQ 16.0 SP 10 Release Note
2162805
Optimizing Performance With Queries Configured to Use
Low_Fast (LF) Indexes
2165219
SAP IQ Release Bulletin
Important SAP Notes
IBM XL C/C++ Runtime Environment for Linux on Power
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
3
2
Product Summary
This release bulletin provides late-breaking information about SAP IQ. A more recent version may be available
on the Web.
For information about compatible platform and operating system configurations and minimum patch levels,
see the Installation and Configuration Guide.
For information about new features and behavior changes in this version, see the What's New in SAP IQ 16.0.
In this section:
Product Compatibilities [page 4]
Information about the compatibility of SAP IQ with other products.
Network Clients and ODBC Kits [page 4]
Network Clients and ODBC development kits for are available on the SAP IQ product support page.
2.1
Product Compatibilities
Information about the compatibility of SAP IQ with other products.
These SAP products are certified with this version of SAP IQ:
● jConnect™ for JDBC™ 7.0
● SAP® IQ Cockpit (SCC) 3.3
These SAP products are certified to work as back ends in CIS functionality with this version of SAP IQ:
● SAP® SQL Anywhere® 16.0
● SAP® Adaptive Server® Enterprise (SAP ASE) 15.7
2.2
Network Clients and ODBC Kits
Network Clients and ODBC development kits for are available on the SAP IQ product support page.
See the Technical Release Information on the SAP IQ 16.0 Product Support Page
.
Note
SAP IQ 16.0 does not require an upgrade of the 32-bit ODBC kits, if you use SAP IQ 15.2 32-bit ODBC kits.
4
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
SAP IQ Release Bulletin
Product Summary
3
Installation and Upgrade
This section provides last-minute information about installation and upgrading that was omitted from or
incorrect in your installation guide, or that needs special emphasis.
For detailed information about installing and upgrading SAP IQ, see the Installation and Configuration Guide.
Before you run a new version of SAP IQ, see Restrictions for the most current requirements.
CR#
n/a
Description
SAP IQ 16.0 Requires a License SAP IQ 16.0 uses the SAP Software Asset Management (Sy­
SAM) licensing mechanism that lets system administrators enable and monitor their site’s use of
SAP products.
SAP IQ includes separate SySAM licenses for each product edition and separate licenses for any
optional features available for that edition. See Licensing Your Software in the Installation and
Configuration Guide.
n/a
SAP® IQ Cockpit does not support SAP IQ version 15.4 Use SAP® Control Center 3.3 to manage
and migrate your 15.4 database. Once migrated, you can use SAP IQ Cockpit.
711014
The pluggable authentication module (PAM) configuration file (sybase-csi) supplied with
SCC does not support Linux RedHat 6.0.
For more information on sybase-csi files, see Configuring a Pluggable Authentication Module
(PAM) for UNIX in the SCC online help.
Workaround
For RedHat 6.0 support, create a sybase-csi file that contains:
auth
account
password
session
749005
include
include
include
include
system-auth
system-auth
system-auth
system-auth
Certicom Cryptography Services Replaced
Certicom software, which provides cryptography services for securing storage and transmission
of sensitive information, is no longer supported by SAP products. These services have been re­
placed by alternate providers, as indicated in the documentation for each SAP product.
See Encryption Support Changes in What's New in SAP IQ 16.0.
728377
SAP IQ Release Bulletin
Installation and Upgrade
Extract and Install Installation Packages on the Same Machine The SAP Service Marketplace
is an online software delivery service that provides easy access to the latest versions of your soft­
ware. When you download your software, uncompress the downloaded image and run the instal­
ler on the same machine where you install SAP IQ. Do not copy an uncompressed installation ar­
chive to a secondary machine and run the install.
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
5
CR#
Description
691212
Avoid Using Relative Path to Launch Installer SAP IQ installation fails if you launch the installer
using a relative path. During GUI installation, the installer fails to prompt for the license file infor­
mation and does not install properly.
For example, when launched from the console using a command line:
Installer files directory : /system1/users/jones/installdir
$SYBASE dir : /system1/users/jones/IQ160
cd $SYBASE
../installdir/setup.bin
Workaround Launch the installer from the directory where it is located, or use an absolute
path.
688135
SAP Partners with v3 UDFs Must Specify a License Key When Upgrading to v4 If you are an
SAP design partner using v3 UDFs, your UDFs will not continue to work after you upgrade your
libraries to v4 unless you specify the SAP-provided license key in the
a_v4_extfn_license_info structure. You must implement the
extfn_get_license_info method, and the method must return a valid key. See User-De­
fined Functions for information on upgrading to the v4 API, and adding the
extfn_get_license_info method.
628594
SySAM Licensing Checkout If SAP IQ was licensed using a per-processor license type in previ­
ous releases, the license quantity was determined at startup. In this release, SAP IQ periodically
checks the number of processors it can use and attempts to check-out additional licenses for any
increase. SAP IQ shuts down after 30 days if additional licenses are not made available within this
period. See the SySAM Users Guide for details regarding license grace.
n/a
ALTER DATABASE UPGRADE PROCEDURE ON Required To install new system tables, you
must run ALTER DATABASE UPGRADE PROCEDURE ON on existing databases after instal­
ling SAP IQ 16.0.
For syntax, see Reference: Statements and Options.
615420
Using Remote Server Classes for SAP ASE Component Integration Services (CIS) connectivity
from SAP IQ to SAP Adaptive Server Enterprise (ASE) is available using server class aseodbc.
The aseodbc server class uses the ASE ODBC driver. The ASE ODBC driver requires a separate
installation of SDK 15.5 ESD #8 or higher which can be downloaded from the SAP EBF download
site.
In this section:
Problem Solutions from Earlier Versions [page 7]
SAP IQ includes solutions to problems that were solved in post-release updates to earlier versions.
Database Upgrades [page 7]
Important information about database upgrades.
SAP IQ and Other SAP Products [page 8]
Issues you should know when you install SAP IQ with other SAP Products.
6
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
SAP IQ Release Bulletin
Installation and Upgrade
Related Information
Restrictions [page 9]
3.1
Problem Solutions from Earlier Versions
SAP IQ includes solutions to problems that were solved in post-release updates to earlier versions.
SAP IQ 16.0 contains solutions to problems fixed up to and including these versions:
● SAP IQ 15.1 ESD #3 (N off #7 - SAP IQ 15.1 ESD #3.7)
● SAP IQ 15.2 ESD #1 (N off #8 - SAP IQ 15.2 ESD #1.8)
● SAP IQ 15.2 ESD #2 (N off #3 - SAP IQ 15.2 ESD #2.3 )
● SAP IQ 15.2 ESD #3
● SAP IQ 15.3
● SAP IQ 15.4 ESD #4
● SAP IQ 16.0 ESD #1
3.2
Database Upgrades
Important information about database upgrades.
For detailed information about installing and upgrading SAP IQ, see the Installation and Configuration Guide.
CR#
750748
Description
Shut down all products that use $SYBASE before upgrade The SYBASE variable iden­
tifies the location of the common parent directory shared by SAP applications like SAP
ASE and Sybase Open Client. Failure to shut down all products that use $SYBASE may
generate signal 11 (SIGSEGV) errors when you upgrade SAP IQ.
Workaround Shut down all SAP applications, restart the SAP IQ server, and retry the up­
grade.
702052
Drop all JOIN and all LD indexes. On multiplex, drop all logical servers named AUTO,
COORDINATOR, ALL or DEFAULT If you do not drop these objects and try to run an
ALTER DATABASE UPGRADE in SAP IQ 16.0, the upgrade fails and the server returns a
message that indicates that a database upgrade is not possible when these objects are in
use.
Recovery Information To recover from a failed upgrade, shut down the 16.0 server, open
the database with SAP IQ 15.x, and drop all LD and all JOIN indexes as well as any named
logical servers before proceeding with the migration.
n/a
Block number issues may cause corruption Issues with certain block numbers may
cause corruption in upgraded databases. For more information, see 2034975
SAP IQ Release Bulletin
Installation and Upgrade
.
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
7
3.3
SAP IQ and Other SAP Products
Issues you should know when you install SAP IQ with other SAP Products.
CR #
Description
736702
GUI install hangs with .com.zerog.registry.xml file InstallAnywhere uses a tem­
porary registry file (.com.zerog.registry.xml) to track software installa­
tions. InstallAnywhere normally deletes this file, but in some cases, the registry
may become corrupt and cause the installer/uninstaller to hang.
Workaround If this occurs, force quit InstallAnywhere, re­
name .com.zerog.registry.xml, and rerun the install/uninstall.
On Unix-like operating systems, the location of
the .com.zerog.registry.xml is determined by who performs the install/
uninstall. For root users, this file is located in /var directory; for other users, the
$HOME directory. On Windows, this file is located on the C:\ or D:\ root direc­
tory.
688694
Error message for SySAM when you install SAP IQ on Replication Agent™ 15.2
Installing SAP IQ 15.4 and higher versions after Replication Agent 15.2, creates er­
rors in <$SYBASE>/log/sysam_server.log and <$SYBASE>/log/
sysam_util.log.
These errors occur because the license files in the <$SYBASE>/
SYSAM-2_0/bin directory installed by Replication Agent do not have write per­
mission.
Workaround
Before you install SAP IQ, change the license file permissions in the <$SYBASE>/
SYSAM-2_0/bin directory.
8
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
SAP IQ Release Bulletin
Installation and Upgrade
4
Known Issues
Review known issues and workarounds, listed by Change Request (CR) number.
In this section:
Restrictions [page 9]
Consider information about restrictions to avoid unexpected results from your system.
Known Issues for Installation and Configuration [page 11]
Descriptions of known issues and workarounds for SAP IQ installation.
Known Issues for SAP IQ Operations [page 15]
Descriptions of known issues and workarounds for SAP IQ operations.
Known Issues for Interactive SQL [page 19]
Descriptions of known issues for Interactive SQL.
Known Issues for Multiplex Environment [page 20]
Descriptions of known issues and workarounds for the multiplex environment.
4.1
Restrictions
Consider information about restrictions to avoid unexpected results from your system.
This information applies to servers and databases of this version of SAP IQ16.0 that have been upgraded from
any earlier version of SAP IQ, unless specified otherwise.
CR#
771401
Restriction
Linux on Power Requires IBM LV C/C++ Redistributable Libraries SAP IQ will fail to
start on all Linux on Power Systems unless the IBM LV C/C++ redistributable libraries
are installed:
dbspawn: error while loading shared libraries: libibmc++.so.1: cannot open shared ob­
ject file: No such file or directory
Applies to all SAP IQ 16.x versions.
Workaround
750481
License Required for Multiple User Dbspaces or Table Partitions You must be li­
censed for the IQ_VLDBMGMT option in order to create more than one table partition
or user dbspace. If you are not licensed, SAP IQ returns a No such feature
exists error during dbspace or partition creation.
SAP IQ Release Bulletin
Known Issues
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
9
CR#
Restriction
561366
Dbspace Naming in RESTORE DATABASE Command
If the dbspace name contains a file extension such as .iq or .iqtmp, you must en­
close the dbspace name in double quotation marks when specifying the name in a
RESTORE DATABASE command RENAME clause. For example:
RENAME temp1 TO '/work/temp1_res.iqtmp.iqtmp'
DBSPACENAME "temp1_res.iqtmp"
or
RENAME "test_prod2.iq" TO '/test/test_prod2.iq'
365281
Database Name Length Restriction The dbbackup utility truncates the database
name to 70 characters and creates a target file with a truncated name. SAP IQ uses
dbbackup when synchronizing secondary servers. Due to dbbackup restrictions,
database names must be less than 70 characters long.
n/a
Dbspace Management and File Placement When you allocate file system files for
dbspaces (System, IQ main, or IQ temporary), do not place the files on a file system
that is shared over a local area network. Doing so can lead to poor I/O performance and
other problems, including overloading the local area network. Do not place IQ dbspace
files on network drives or (in a multiplex) Network File System (NFS) file systems. Sim­
plex IQ servers support dbspace files on NFS.
To avoid conflicts, SAP recommends that dbspace management be performed by a sin­
gle database administrator on a single connection.
n/a
Unexpected Query Results
In a few unusual circumstances, differences in semantics between SQL Anywhere and
SAP IQ may produce unexpected query results. These circumstances are:
●
A query is issued from inside a user-defined function
●
A SELECT statement has no FROM clause
●
A FROM clause contains some tables that were created IN SYSTEM and others
that were not created IN SYSTEM
In these circumstances, subtle differences between the semantics of SQL Anywhere
and SAP IQ may be exposed. These differences include:
●
SAP IQ treats the CHAR and VARCHAR data types as distinct and different; SQL
Anywhere treats CHAR data as if it were VARCHAR.
●
When the RAND function is passed an argument, the behavior is deterministic in
SAP IQ and nondeterministic in SQL Anywhere.
Parent topic: Known Issues [page 9]
10
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
SAP IQ Release Bulletin
Known Issues
Related Information
Known Issues for Installation and Configuration [page 11]
Known Issues for SAP IQ Operations [page 15]
Known Issues for Interactive SQL [page 19]
Known Issues for Multiplex Environment [page 20]
4.2
Known Issues for Installation and Configuration
Descriptions of known issues and workarounds for SAP IQ installation.
Table 1: Installer issues
CR#
771401
Description
Install the Runtime Environment for Linux on Power SAP IQ fails to start on all Linux
on Power Systems unless the appropriate IBM XL C/C++ redistributable libraries are
installed:
dbspawn: error while loading shared libraries: libibmc++.so.1: cannot open shared ob­
ject file: No such file or directory
Workaround
Download and install the appropriate runtime environment from the Latest updates
for supported IBM C and C++ Compilers page on the the IBM Support Portal.
SAP IQ Release Bulletin
Known Issues
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
11
CR#
Description
690606
RH 6.x default setting for max user processes may be too low for starting SAP IQ
servers
Red Hat 6.x introduced a change that affects the number of threads that the SAP IQ
engine can start. By default, Red Hat 5.x set the limit dynamically based on the ma­
chine configuration. (For example, an 8-core system would set the limit at 256693.) In
Red Hat 6.x, this limit is hard-coded to 1024 regardless of system size. This change
particularly affects systems with high CPU per core counts and systems where the
same user account starts multiple IQ servers.
Workaround 1
1.
Calculate the number of threads needed. For each server started by any single
user, use the following formula to calculate the number of threads IQ allocates:
numThreads = 60*4 + 50*(numCPUs - 4) +
numConnections + 3
For an 8-core system with 100 users, the <numThreads> is 543 threads per
server.
For a 64-core system with 100 users, the <numThreads> is 3343 threads per
server.
The formula also works for systems with fewer CPUs, for example, on 2-core sys­
tems.
2. To set hard and soft limits, add the following lines to
/etc/security/limits.conf:
sybase soft nproc 7712
-- The soft limit allows for 2 servers on the 64core system plus 1024 default.
sybase hard nproc 16384
-- Powers of 16 work well for kernel and engine
settings. (1024 * 16) is rounded up for extra space.
You can increase the soft limit, but the hard limit is the threshold for the value un­
less raised by a privileged user limit.
To set limits for all users instead of the sybase user, replace sybase with *, for
example:
* soft nproc 7712
* hard nproc 16384
3. Set the process number limit in the shell script of the user who starts servers, for
example:
For the tcsh or C (csh) shell:
limit maxproc 7712
12
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
SAP IQ Release Bulletin
Known Issues
CR#
Description
For the bash or Korn (ksh) shell:
ulimit –u 7712
4. Reboot your machine.
Workaround 2
1.
Return to Red Hat 5.x behavior by commenting out the following line in the
file /etc/security/limits.d/90-nproc.conf:
#*
soft
nproc
1024
2. Reboot your machine.
684311
Install on RH 6.0 fails with java stack trace
Red Hat Enterprise Linux 6 requires 32-bit compatibility libraries to support Javabased applications in SAP IQ, including the SAP IQ installer.
Workaround
These libraries are required to install SAP IQ on Red Hat Enterprise Linux 6:
●
libXext-devel.i686
●
libXtst-devel.i686
If you start the SAP IQ installer in GUI mode without installing these libraries, the in­
staller generates an exception and fails.
665300
Installer stops responding on some UNIX-like platforms On some UNIX-like operat­
ing systems, a network resource may cause the installer to stop responding and return
the error "syntax error near unexpected token 'fi'." The df command also stops re­
sponding in this situation.
Workaround
1.
Identify the network file system (NFS) mounts that may have problems:
strace -e statfs, statfs64 df
2. Use the umount command to unmount an identified NFS mount:
umount -l <path>
3. Repeat the above steps until there are no more NFS mounts that have stopped
responding.
Note
The umount command requires root permission. If umount unmounts the NFS,
you may have to restart your machine.
SAP IQ Release Bulletin
Known Issues
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
13
CR#
Description
664968, 669802
Installer returns "Permission denied" error on Red Hat The installer may return this
error on Red Hat, when the installation DVD has been automatically mounted:
./setup.bin: /bin/sh: bad interpreter: Permission denied
Workaround Remount the installation media and run the installation again:
1.
Unmount the installation media.
2. Manually mount the DVD drive:
Use one of the following commands to remount the drive:
○
mount -t iso9660 /dev/hda /mnt/cdrom
○
mount -o exec /dev/cdrom /media
3. Start the installation using the new mounted directory /mnt/cdrom.
655963
Installer returns error "No filesystem could mount root" on Red Hat The installer
may return this error on Red Hat when installing on IBM P6 and P7 machines:
rhel6 install error: No filesystem could mount root, tried: iso9660
Workaround Follow the steps on http://www.ibm.com/developerworks/forums/
thread.jspa?threadID=357314
641873, 652690, 652696,
652866, 643106
and re-install.
Do not install SAP IQ16.0 into the same directory as older SAP IQ products
Installing SAP IQ 16.0 into the same directory with older SAP products may render
some or all of these products unusable.
Workaround
Install SAP IQ16.0 into a different directory than the one you use for older products.
Parent topic: Known Issues [page 9]
Related Information
Restrictions [page 9]
Known Issues for SAP IQ Operations [page 15]
Known Issues for Interactive SQL [page 19]
Known Issues for Multiplex Environment [page 20]
14
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
SAP IQ Release Bulletin
Known Issues
4.3
Known Issues for SAP IQ Operations
Descriptions of known issues and workarounds for SAP IQ operations.
Table 2: Index issues
CR#
Description
n/a
Tokenized FP issues may cause corruption Issues
with tokenized FP indexes may cause memory corrup­
tion. For more information, see 2034975
.
Table 3: Open Client issues
CR#
662422
Description
Remote query performance degrades with DATETIME column
SAP IQ16.0 and the default Open Client/Server included with SAP IQ16.0 support the
TDS BIGDATETIME data type for remote queries.
When SAP IQ server executes a remote query using Open Client and fetches a
DATETIME column on an IQ/SA remote server, the return data type is
BIGDATETIME, instead of DATETIME. This may degrade performance.
This performance degradation may not occur, when the remote server is an ASE
server.
To prevent the return of BIGDATETIME values, apply this workaround.
Workaround Add these lines to the Open Client and Open Server configuration file
$SYBASE/$SYBASE_OCS/config/ocs.cfg to prevent the return of
BIGDATETIME values:
[SAP Sybase IQ]
CS_CAP_RESPONSE = CS_DATA_NOBIGDATETIME
Table 4: Server startup issues
CR#
682890
Description
Red Hat 6.0 limits number of threads/processes
Starting SAP IQ may return a Resource temporarily unavailable message
if the user process spawns too many processes.
Workaround
1.
Change the login profile of the user starting SAP IQ. For example, in the bash
shell, enter the following command in the .bashrc file:
ulimit -u 32000
2. If the problem persists, try a stronger approach. As root, edit the file /etc/
security/limits.conf and add this line:
sybase -
SAP IQ Release Bulletin
Known Issues
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
15
CR#
Description
663054
Database recovery fails if server started with -iqro 1 flag
A 15.2 database that is archived cannot be recovered if you specify the read-only flag -
iqro 1 on the startup command in SAP IQ 16.0.
In this section:
SAP IQ Operations Known Issues from Previous Versions [page 16]
Descriptions of known issues and workarounds for SAP IQ operations from previous versions.
Parent topic: Known Issues [page 9]
Related Information
Restrictions [page 9]
Known Issues for Installation and Configuration [page 11]
Known Issues for Interactive SQL [page 19]
Known Issues for Multiplex Environment [page 20]
4.3.1 SAP IQ Operations Known Issues from Previous
Versions
Descriptions of known issues and workarounds for SAP IQ operations from previous versions.
Description
CR#
686818
Red Hat 6 Requires Compatibility Libraries Installation of SAP IQ 15.3 on Red Hat 6.0 fails
with an InvocationTargetException error unless you install the required 32-bit com­
patibility libraries:
16
●
libXext-devel.i686
●
libXtst-devel.i686
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
SAP IQ Release Bulletin
Known Issues
CR#
627872
Description
PHP Bound Parameters on Big Endian Platforms In SAP IQ 15.2, PHP: Hypertext Prepro­
cessor (PHP) drivers on big endian platforms require bound parameters to be initialized be­
fore the call to sasql_stmt_bind_param for INT and BIGINT data types.
This example shows the values properly initialized before the call to
sasql_stmt_bind_param:
$stmt = sasql_prepare($conn, "insert into
testdefault(c1, c2, c3, c5) values(?,?,?,?)");
#Binding parameters with statement prepared
$c1=22; $c2=33; $c3="col3data"; $c5="col5data";
sasql_stmt_bind_param
($stmt,"iiss", $c1, $c2, $c3, $c5);
#executing statement
sasql_stmt_execute($stmt);
622928
sp_iqstatus Returns Error on Chinese and Japanese Locale Installations On SAP IQ serv­
ers that are set up for Chinese and Japanese locales, running sp_iqstatus returns an er­
ror similar to:
Could not execute statement.
Syntax error near '2010' on line 1
SQLCODE=-131, ODBC 3 State="42000"
Line 1, column 1
Workaround
1.
Run these commands:
For Chinese locales:
% cd $IQDIR16/res
% rm dblgzh_iq11_eucgb.res
% rm dblgzh_iq11_cp936.res
For Japanese locales:
% cd $IQDIR16/res
% rm dblgja_iq11_eucjis.res
% rm dblgja_iq11_sjis.res
2. Restart SAP IQ.
After this procedure, certain strings in the .iqmsg files and the output of sp_iqmpxinfo,
sp_iqstatistics, and sp_iqstatus are in English, instead of Chinese or Japanese.
SAP IQ Release Bulletin
Known Issues
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
17
CR#
Description
622007
SAP ASE Connections to SAP IQ with BIGDATETIME When a version 15.5 GA SAP ASE
server uses Component Integration Services (CIS) to connect to an SAP IQ server version
that has BIGDATETIME and BIGTIME capability, any chronological data type sent to the
SAP ASE server using CIS results in the error:
Msg 7225, Level 16, State 4:
Line 1:
Unknown datatype token 188 'BIGDATETIME NULL'
encountered.
Exited passthru mode from server 'QA_IQ16_ASECIS'.
SAP IQ sends the data as BIGDATETIME and relies on SAP ASE to convert appropriately.
The BIGDATETIME data type was implemented in CIS in SAP ASE version 15.5 ESD #1, so
this error occurs with SAP ASE 15.5 before any ESDs have been applied.
Workaround SET TEMPORARY OPTION RETURN_DATE_TIME_AS_STRING='ON' in
SAP IQ for each session. The SAP IQ server sends all chronological data as strings and SAP
ASE completes the conversion. This workaround is for SAP ASE 15.5 GA connecting to SAP
IQ in passthrough mode.
You can also use this workaround in the definition of a remote stored procedure, but it is not
a solution for proxy tables created on SAP ASE returning chronological data types from SAP
IQ.
571993
dbisql Does Not Start on Linux Red Hat 5.3
The Interactive SQL utility dbisql fails to start on Linux Red Hat 5.3, and issues a message
similar to:
Error! could not load the Java Virtual machine DLL:
/root/users/user1/050509/shared/JRE6_0_7_32BIT/lib/i386/client/libjvm.so
Workaround Run:
% cd $IQDIR16/bin32
% dbisql -batch # creates below
% dbisql.sh
571627
SELinux Policy Requirement for SAP IQ 15.x on Linux PowerPC x64 You must install seli­
nux-policy-2.4.6-25.e15 or later to use the java -version command with SELinux ena­
bled. If the policy version is incorrect, the system displays this message:
Errorloading: /libjvm.so: cannot restore segment prot
after reloc: Permission denied
This is the preferred method to meet this policy requirement, but alternatively, you can disa­
ble SELinux.
18
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
SAP IQ Release Bulletin
Known Issues
4.4
Known Issues for Interactive SQL
Descriptions of known issues for Interactive SQL.
Use dbisql, instead of dbisqlc, unless instructed to do otherwise for specific tasks. dbisqlc is supported,
but does not contain all the features of dbisql. dbisqlc will be deprecated in a future release.
Table 5: Interactive SQL issues
CR#
762252
Description
Starting Interactive SQL returns stackguard warning On Linux on POWER, starting In­
teractive SQL may return:
Warning: You have loaded library
/libm13qa-c2/users/smith/16sp08_140312/IQ-16_0/lib64/
libjsyblib1600_r.so
which might have disabled stack guard. The VM will try to
fix the stack guard now.
It's highly recommended that you fix the library with
'execstack -c <libfile>',
or link it with '-z noexecstack'.
Workaround Exit Interactive SQL and run the execstack command on the library iden­
tified in the warning message. For example:
% execstack -c libjsyblib1600_r.so
Restart Interactive SQL after you run the recommended commands.
668398
XKEYSYMDB environment variable required for dsedit Before using dsedit, you must
set the environment variable XKEYSYMDB to <path to X11>/XKeysymDB.
For example, for csh:
setenv XKEYSYMDB /usr/share/X11/XKeysymDB
n/a
Creating output files in quiet mode If you run dbisql (Interactive SQL) with the -q
(quiet mode) option, and the data extraction commands (primarily setting the option
TEMP_EXTRACT_NAME1 to an output file) are in a command file, you must first set and
make permanent the dbisql option “Show multiple result sets.” If you do not set this op­
tion, the output file is not created.
n/a
Show multiple result sets To set the option “Show multiple result sets,” click Tools | Op­
tions in the dbisql window, choose "SAP IQ," and select the "Results" tab. Under "Re­
sults Processing" and "For statements that return multiple result sets," select "Show all
result sets."
n/a
Query plan on the Plan Viewer tab The query plan in the dbisql Plan Viewer tab is a
SAP SQL Anywhere style query plan. For SAP IQ query plan, refer to the IQ .iqmsg file.
SAP IQ Release Bulletin
Known Issues
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
19
CR#
Description
n/a
Unable to initialize screen routines If you set the terminal type on UNIX and Linux sys­
tems to “dumb” or “unknown” and then start dbisqlc, SAP IQ returns an error. For ex­
ample:
% setenv TERM dumb
% dbisqlc
error at line 1 Unable to initialize screen routines
Workaround To avoid problems, run dbisql (Interactive SQL) instead, or use an xterm
window to run dbisqlc on UNIX and Linux systems. For example, to start an xterm win­
dow with a scroll bar, enter:
% xterm -sb
Parent topic: Known Issues [page 9]
Related Information
Restrictions [page 9]
Known Issues for Installation and Configuration [page 11]
Known Issues for SAP IQ Operations [page 15]
Known Issues for Multiplex Environment [page 20]
4.5
Known Issues for Multiplex Environment
Descriptions of known issues and workarounds for the multiplex environment.
Table 6: Multiplex issues
Description
CR#
785206
Multiplex queries may fail with Mpx_Work_Unit_Timeout error
Error message is:
Mpx_Work_Unit_Timeout exceeded. Leader timeout waiting for intermediate result from
worker.
See 2178982
20
.
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
SAP IQ Release Bulletin
Known Issues
CR#
782496
Description
Shared-nothing multiplex: Coordinator cannot be member of shared-nothing logical
server If the coordinator node is a physical member of the shared-nothing logical server, at­
tempting to execute the CREATE DBSPACE command to create a DAS dbspace results in an
error.
Workaround: Alter the logical server to either:
●
Remove the coordinator, or
●
Add membership FOR LOGICAL COORDINATOR to specify the coordinator is a logical
(not physical) member.
748684
start_iq fails to restart secondary server with high availability enabled A secondary server
with the high availability option enabled fails, but start_iq fails to restart it:
start_iq @params.cfg database.db
Workaround Specify the full path to restart a high availability server:
start_iq @/system1/IQ16/mydb/params.cfg /system1/IQ16/mydb/
database.db
611990
Emergency shutdown on secondary servers after CREATE TEXT INDEX A secondary
server goes into emergency shutdown when:
●
It is started with the -sf external_library_full_text flag, which disables
loading of external libraries, and
●
The user issues a CREATE TEXT INDEX statement on the coordinator with a text con­
figuration that uses external libraries.
All other servers replay the DDL successfully.
Workaround Start secondary nodes in the multiplex without the -sf
external_library_full_text flag.
Parent topic: Known Issues [page 9]
Related Information
Restrictions [page 9]
Known Issues for Installation and Configuration [page 11]
Known Issues for SAP IQ Operations [page 15]
Known Issues for Interactive SQL [page 19]
SAP IQ Release Bulletin
Known Issues
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
21
5
Documentation Changes
Updates, corrections, and clarifications to the documentation released with SAP IQ.
In this section:
Programming Documentation Changes [page 22]
Read about updates to Programming.
5.1
Programming Documentation Changes
Read about updates to Programming.
.NET API Reference
Topic
Section
Correction
.NET API Reference
All subtopics under .NET API
Reference refer to the product
as SQL Anywhere.
The product is SAP IQ. SQL Anywhere and SAP
IQ use the same .NET API.
Topic
Section
Correction
SAP IQ Database API for C/C++
All subtopics under SAP IQ Da­ The product is SAP IQ. SQL Anywhere and SAP
tabase API for C/C++ refer to
IQ use the same C/C++ API.
the product as SQL Anywhere.
C/C++ API Reference
22
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
SAP IQ Release Bulletin
Documentation Changes
6
Obtaining Help and Additional
Information
Learn more about this product on the SAP Help Portal.
See product documentation at the SAP Help Portal – online documentation that you can access using a
standard Web browser. You can browse documents online or download them as PDFs.
To read or print PDF documents, you need Adobe Acrobat Reader, which is available as a free download from
the Adobe
Web site.
Note
A more recent release bulletin, with critical product or document information added after the product
release, may be available from the SAP Help Portal.
In this section:
Technical Support [page 23]
Customer support, software downloads, certification and maintenance reports are available online.
Information for Technical Support [page 24]
Technical Support needs information about your environment to resolve your problem.
Checklist: Information for Technical Support [page 25]
You can run the getiqinfo script to collect information.
6.1
Technical Support
Customer support, software downloads, certification and maintenance reports are available online.
SAP Support Portal
Technical support is available online at the SAP Support Portal.
Report issues with the SAP Incident Wizard
SAP IQ Release Bulletin
Obtaining Help and Additional Information
. Contact SAP at the SAP Customer Interaction Center
.
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
23
EBFs and Maintenance Reports
EBFs and maintenance report keep your software current and alert you to potential issues.
See the General Information on the SAP IQ Product Support Page
.
Platform Certifications
Certification reports verify performance on a particular platform.
See the Technical Release Information on the SAP IQ Product Support Page
.
Developer Center
The SAP IQ Developer Center provides a forum for users to exchange information about SAP IQ
Visit the SAP IQ Developer Center at http://scn.sap.com/community/developer-center/analytic-server
6.2
.
Information for Technical Support
Technical Support needs information about your environment to resolve your problem.
Before contacting Technical Support, run the getiqinfo script to automatically collect as much information
as possible. You may also need to collect some information manually .
In this list, * indicates items collected by getiqinfo:
● SAP IQ version (for example, 16.0 GA or SP level)
● Type of hardware, amount of memory, number of CPUs*
● Operating system and version (for example, Microsoft Windows 2008 Service Pack 1)*
● Operating system patch level
● Front-end tool used (for example, Business Objects Crystal Reports)
● Connectivity protocol used (for example, ODBC, JDBC, Tabular Data Stream™ (TDS))
● Open Client version
● Configuration type (single user or multiuser)
● (Important) Message log file* – by default, named dbname.iqmsg and located in the directory where you
started the database server
● Stack trace file for the date and time the problem occurred (if applicable), by default named stktrcYYYYMMDD-HHMMSS_#.iq and located in the directory where you started the database server*
● Command or query that produced the error
● Query plan* (recorded in .iqmsg file)
The query plan is collected automatically by getiqinfo. If you manually collect information, enter
commands like these, then re-run the command that produced the error.
24
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
SAP IQ Release Bulletin
Obtaining Help and Additional Information
For UNIX or Linux:
SET TEMPORARY OPTION Query_Plan = 'ON'
SET TEMPORARY OPTION Query_Detail = 'ON'
SET TEMPORARY OPTION Query_Plan_As_Html= 'ON'
SET TEMPORARY OPTION Query_Plan_As_Html_Directory=
'/mymachine1/user/myqueryplans'
The plan is in the message log file.
If you have performance problems, set this database option:
SET TEMPORARY OPTION Query_Plan_After_Run = 'ON'
This enables Technical Support to see which steps in the query processing used the time.
● Server logs
○ For UNIX and Linux: IQ-16_0/logfiles/<servername>.nnnn.stderr and IQ-16_0/logfiles/
<servername>.nnnn.srvlog*
● Startup and connection option settings, from the configuration file (by default, dbname.cfg)*
● Database option settings and output from sa_conn_properties* (if the server is still running)
● Schema and indexes for the database
● Output from sp_iqstatus and sp_iqcheckdb
● On multiplex databases, execute getiqinfo on each node (coordinator and secondary nodes)
● Screen snapshot of the problem, if possible
A checklist for recording this information for Technical Support is provided in this release bulletin.
See Collecting Diagnostic Information Using getiqinfo in Administration: Database.
6.3
Checklist: Information for Technical Support
You can run the getiqinfo script to collect information.
Information Requested
Value
SAP IQ version (for example 16.0 GA or SP number)
sp_iqlmconfig output
Type of hardware
Amount of memory
Number of CPUs
Operating system name and version (for example, Microsoft Windows
2008 Service Pack 1)
Operating system patch level
SAP IQ Release Bulletin
Obtaining Help and Additional Information
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
25
Information Requested
Value
Front-end tool used (for example, Business Objects Crystal Reports)
Connectivity protocol used (for example, ODBC, JDBC, TDS)
Open Client version
Configuration type (single node or multiplex)
Message log file (dbname.iqmsg)
Server log files (server.nnnn.srvlog and
server.nnnn.stderr)
Stack trace file (stktrc-YYYYMMDD-HHNNSS_#.iq)
Command or query that produced the error
Start up option settings
Connect option settings
Database option settings
Schema and indexes for the database
sp_iqstatus output
Query plan: set options (Query_Plan, Query_Detail, Query_Plan_Af­
ter_Run, Query_Plan_As_Html, Query_Plan_As_Html_Directory,
Query_Timing), re-run command or query
Screen snapshot of the problem, if possible.
26
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
SAP IQ Release Bulletin
Obtaining Help and Additional Information
Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended 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.
Accessibility
The 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 Language
As 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 Hyperlinks
The 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).
SAP IQ Release Bulletin
Important Disclaimers and Legal Information
PUBLIC
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
27
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.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising