SAP IQ的所有已知BUG列表

随着Sybase被完全整合到SAP下,Sybase原来的支持网站被SAP Support Portal取代。
只有购买了SAP服务的用户才能使用账号登录SAP Support Portal进行介质下载、补丁升级、报Incident等。
考虑到Sybase数据库的初学者或者没有购买原厂服务的Sybase客户情况,现提供SAP ASE/IQ/RS/SDK/SQL Anywhere/PB等产品的BUG信息。
在SAP Support Portal网站或者google上搜索Targeted CR List for ASE,可以看到针对不同版本的CR(CR表示Change Request)简单描述信息列表。
需要注意的是:Targeted CR List for ASE列出的CR虽然绝大多数是BUG,但有一些是更改需求。
以下提供SAP ASE/IQ/RS/SDK/SQL Anywhere/PB等产品的BUG信息!
不仅仅包括BUG的详细描述信息,还包括首次报告BUG的平台、数据库版本以及BUG修复历史过程;有些BUG还提供了Workaround来临时解决该BUG带来问题。

CR
Number
Description
297099 Adaptive Server IQ parsed a query incorrectly when the query

combined the CONTAINS predicate and an 'Into #temp' clause.

297235 A query takes 25min to get a query plan while the execution only need 1 seconds.

This happens in version 12.4.3 ESD7.

300063 The IQ server has 2 user event enabled. The event actions gete executed very 3 seconds and contain an INSERT... LOCATION statement. If you stop and start the IQ server the events cannot be executed because if the error:

Exception Thrown from hqm_con.cxx:102, Err# 1, tid 264 origtid 264

O/S Err#: 0, ErrID: 8192 (hqm_exception)

CtLibrary Error: 141, Severity: 0, Origin: 1, Layer: 1

Error Message: ct_con_props(SET,PASSWORD): user api layer: external error: buflen must be 0 or CS_UNUSED when buffer is NULL.

OS Error: 0, OS Message: .

-- (hqm_con.cxx 102)

Probelm reason:

The INSERT... LOCATION statement always takes the user and password from the

current connection to connect to an ASE server. The catalog stores the password

only as hash value created by an one-way algorithm for security reason.

So the password string is not available for the event execution before the end user

using this username has connected to ASIQ.

As soon as an user has connected using the username all subsequent INSERT... LOCATION

in events work file

Its not possible to fix this problem without added new syntax or an new feature.

i'm going to create an Enhancement Request for this.

300064 If 2 user event concurrently run and both execute an insert location then after 15 min (or

1-3 hours) the IQ server gets into one of the following situations:

- the IQ server crashes with the below stacktrace

- the IQ server prints the below stacktrace but still exist as unix process and

consumes about 380 percent CPU usage on a 4 CPU machine

The stack trace is:

ucstkgentrace__FilT2 + 0x70 [/sybase/t/sys/asiq12/bin//../lib/libiq.sl]

hos_ABORT__FPCcUiT1 + 0x1c4 [/sybase/t/sys/asiq12/bin//../lib/libiq.sl]

SigHndlr__Fi + 0x48 [/sybase/t/sys/asiq12/bin//../lib/libiq.sl]

_sigreturn [/usr/lib/pa20_64/libc.2]

_memmove + 0x22c [/usr/lib/pa20_64/libc.2]

mallinfo + 0x1f70 [/usr/lib/pa20_64/libc.2]

_ltostr + 0xb6c [/usr/lib/pa20_64/libc.2]

realloc + 0x1fc [/usr/lib/pa20_64/libc.2]

ut_do_realloc + 0x18 [/sybase/t/sys/asiq12/lib/libdbserv7.sl.1]

ut_realloc + 0x64 [/sybase/t/sys/asiq12/lib/libdbserv7.sl.1]

MsgListAddToRow__FPciT2 + 0xb4 [/sybase/t/sys/asiq12/lib/libdbserv7.sl.1]

300708 The option Ansi_update_constraints is not descripted for ASIQ but has an effect.

This should be corrected. With Ansi_update_constraints = 'strict' an delete statement

returns: "update operation attempted on non-updatabled"

301743 When using collation ISO_1 and grouping using an LF index the returned result set

shows wrong data.

302231 In version 12.4.3 ebf3 and above the SET ROWCOUNT nnn statement has no effect for UPDATE and DELETE (see 260409). Please document this correct at least for the next version
303350 The EBF coverletter for 12.4.3 ebf7 and 8 for HP-UX 64-bit is incorrect for the value shmmax 2147483647 (0x47FFFFFFF). The decimal and the hex value does not fit.
305554 A problem that could potentially cause the server to fail when an application opened two
cursors concurrently in a single connection has been corrected.
306932 Allow concurrent DDL operations to different tables.
307373 Starting the Sybase IQ database without the transaction log could corrupt the IQ database. The transaction log is required.
307380 Feature request to improve performance for small fast queries (a.k.a web queries).
309177 Queries to the metadata for columns of type bigint, unsigned smallint, unsigned int, and unsigned bigint returned the column type as NULL.
309305 Feature request to have the ability to copy/move users' logins and pwd from one database to another, just like the way ASE allows (bcp rows out of the system tables from one database/server and bcp into the same system tables in another database/server after setting a flag (sp_configure "allow updates to system tables" 1) in that ASE server to enable update to system tables).

In IQ, we could select rows for login & pwd data out of the sysuserperm system table, but IQ would not allow the user to add (load/insert) rows to the system tables. So right now, we don't have the functionality in ASIQ to accomplish this though this could be done through scripts by the user.

309459 If you run ASIQ on HP-UX the OS charset is ROMAN8. If you do an INSERT..LOCATION to an ASE

database all characters are converted to ROMAN8 but the ASIQ db is ISO_1.

To prevent this convertion the LC_ALL variable on OS level has to be set.

With the request the connection done by the INSERT..LOCATION should always set the client local info to the same as the IQ db's collation sequence.

309832 On Windows systems, you can now generate a stack trace on an unresponsive server by creating a file named DumpAllThreads or dumpallthreads in the %ASDIR%\logfiles directory. Starting ASIQ as recommended, using the Program Manager or start_asiq, sets the ASDIR variable automatically. If the ASDIR variable is not set, create the dumpallthreads file in the directory where the server started.
310008 When a user issues a CREATE DBSPACE ... SERVER ... (long-form, or "alias" version) of a CREATE DBSPACE that names a server that already has a row in SYSIQFILE for the indicated file_id, the ASA code simply lets it through, although no row is added to SYSIQFILE as would be the case if the SERVER specified did not already have a row in SYSIQFILE. The IQ code assumes that the PRIMARY KEY (file_id, server_name) in SYSIQFILE would have caught the duplicate, and so goes ahead and opens (on a query server) the dbspace all over again. This will cause a fatal Throw if the user subsequently tries to drop this dbspace since it is "open" twice.
310194 If the environmental variable SQLCONNECT was set, and contained the "dbf" parameter, then dbspawn failed with the error:

DBSPAWN ERROR: -81

Invalid database server command line

310263 A problem occurred with queries using parallel GROUP BY where outer references contain switch statements added together. Such statements returned "Can not evaluate expression" errors.
310948 Certain scripts that contain proxy tables referring to Sybase IQ fail with a stack trace.
311043 When running the following remote procedure call the ASIQ server dies.
312448 Errors in prompts returned by the getiqinfo tool have been corrected. The tool is named getiqinfo.bat on Windows systems and iqgetifo.sh on UNIX.
312542 A problem with mismatched datatypes now returns the appropriate conversion error

instead of causing server failure.

312577 If the option QUERY_RUN_AFTER_PLAN is set ON, queries of the form:

INSERT INTO <temp table> ... SELECT ...

did not generate a pre-run query plan as they normally would.

312721 Certain large queries within INSERT statements caused Sybase IQ to fail with a stack overrun. To solve this problem, ASIQ now allows a larger safety margin for thread stack space.

INSERT SELECT statements may be returned with an insufficient stack error

message requesting that you increase the -iqtss setting. Increasing -iqtss by 72KB permits such statements to complete.

On 32-bit systems only, depending on your memory configuration, you may need to decrease

Load_Memory_MB in order to increase -iqtss.

313022 ASE compat: support default values in Load/Insert/Update including automatic TIMESTAMP
313358 Various stored procedure syntax errors, such as improper use of quotation marks or invalid table and variable references could result in a SEGV or Signal 10 server failure. Related CRs are 310843, 312345, 316064 and 317803.
314519 A problem affected the incremental High_Group load algorithm.
315146 Certain queries with complex derived tables could either return incorrect results or cause

server failure. This problem is corrected.

315238 Executing the getdate() function within an insert statement like the following returned zeroes for the milliseconds:

INSERT INTO testtable VALUES (getdate())

315421 A query with certain characteristics could return a "can not evaluate expression" error.

This problem affected a query with a SELECT DISTINCT column in a derived table that was

not used in another query block. The column also happened to be in a case expression that

was an argument of a complex expression.

315571 There is a chance that Sybase IQ on an AIX system will receive an internal

error and create a core file if an attempt is made to generate

an HTML file.

315729 Turning on the ASA option for long plans in java dbisql could cause an IQ server to fail.
315738 Sybase has corrected a problem affecting columns where either all values are null or the

table is empty, have either a 1-byte or 2-byte FP index, and has neither a LF nor an HG index. Such a column, used in a predicate, could potentially cause either a floating point hardware exception and subsequent server failure or an "invalid arithmetic construction" error.

316440 On rare occasions, when multiple users try to extract to the same public file, the server could fail and return only a "no connection to the server" message. Now the client receives "OS error reported on file: xxxx", where xxxx is the file name that Adaptive Server IQ failed to create for the EXTRACT operation, followed by the error code and location (source filename and line number) that triggered the error. In very rare cases, the error "Failed in derived class conductors" may be returned instead.
316661 DBISQL Java stacktrace when numeric column has no precision defined or column has precison > (90,0)
316907 While processing certain unusual queries that contain several joins and that include several join conditions containing the same columns, the server could fail.
317290 While processing certain unusual queries containing numerous joins, the server could fail.
317602 Prior to this release, a server failure might occur when the datatype, precision, and/or scale of a column changed between the cursor describe and open. This error is now corrected and IQ processes the statement and logs a warning in the .iqmsg file.
317650 A problem with the stop_asiq script prevented Sybase IQ from detecting all servers running.
317830 A timing sensitive issue involving scheduling priority of writing information to the server log, connection disconnecting, and server commits/checkpoints is corrected. On active servers with many connections, it would appear that the server was temporarily

suspended during these scheduling conflicts.

317857 On rare occasions while processing a statement containing an IN predicate using an HG index, the server could fail.
317861 On HP-UX, a query with more than 24 individual GROUP BY columns could portentially cause server failure.
318250 Certain queries containing host variables whose values were bound via an Embedded SQL OPEN
statement were incorrectly rejected with a "Non-Fatal IQ Internal Error".
318332 Certain queries could get rejected with an internal error in dfo.cxx
318650 The sp_iqcheckdb procedure verify and repair options incorrectly reported that the LF index was inconsistent.
318942 Certain concatenated statements caused Adaptive Server IQ to fail.
318978 A timing-sensitive issue involving resource management during set options processing and connection open/close is corrected. On servers handling many connects/disconnects, it could make the server unresponsive.
319000 A certain program failed with a stack trace using the embedded-SQL preprocessor and associated libraries shipped for Sun and AIX 64-bit systems, but worked correctly on HP 64-bit and Sun 32-bit systems. Duplicate of CR 329001.
319059 Under certain circumstances, a statement could fail with the error "Cannot find index for

field."

319278 A problem prevented previous versions of Sybase Central and the IQ plug-in from starting, even after documentation instructions for preserving these versions was followed.
319519 A problem with DATE and DTTM indexes has been corrected. After updating a DATE or DTTM index, running sp_iqcheckdb reported that the index was inconsistent due to a bitmap verify error.
319687 If the sp_iqcontext procedure was run on one connection at exactly the same instant that a different connection was destroying a cursor, the server could on rare occasions fail.
320552 A certain query with join keys of different data types ran slower after IQ 12.5 was installed, the database was rebuilt, and the tables were reloaded.
320562 A server failure indicating "v2s_bmseg.cxx" and "Verify error" with "out of order" has been fixed.
320717 Adaptive Server IQ 12.5 does not support the PARTITION BY clause, for example:

SELECT district, grade, avg(math_score),

rank() over (PARTITION BY district ORDER BY AVG(math_score)

desc) AS rank_d

FROM math_report

GROUP BY district, grade

ORDER BY district;

Such statements now return an appropriate error.

320816 Using a Java function call in place of a column name in a select could cause server failure. (Duplicate of CR 277876 and 313199.)
320902 A simple insert with a join between columns of different datatypes

(char(9) and char(10)) returned the error "Non-Fatal IQ Internal Error Detected

at dfjo_Hash.cxx:378 on thread 273" followed by a stack trace.

320910 Certain INSERT ... SELECT operations could result in an unresponsive server. The problem occurred on a statement such as INSERT ... SELECT col1, col2, ... FROM table1 where there were many columns in the select list and each column had a HG index on it.
320930 Sybase IQ did not write "Total number of blocks being restored" messages to the .stderr file.
321050 A single GROUP BY query without a WHERE clause

using a HG index returned the wrong result.

For example:

SELECT col, COUNT(*) FROM T GROUP BY col

321179 A server failure could occur on Windows when running a query with nested string functions.
321182 The support for pushdown joins into a view containing a UNION ALL

over a set of simple base tables has been extended to include

cases where the exact distinct count for the join column from the view

is not available, but the exact distinct counts for all the underlying

base columns are available. In these cases the cost analysis of the

pushdown join can proceed using the worst case collective distinct count.

321699 A query that features a series of disjuncts on the same

column returned incorrect results.

For example:

SELECT * FROM test1 WHERE

(a > 1 AND a <3) OR

(a > 4 AND a <6) OR

(a > 8 AND a <10)

returned values 2,5,6,7,8 and 9.

321946 Running a query containing a Java function on a Sun 64-bit or AIX 64-bit (IQ 12.5. ESD2) system caused server failure. On an HP-UX 64-bit system (ESD2), the same query returned incorrect results.
322287 While loading rows with constraint violations,

a server failure occurred at st_server.cxx; 1037.

322556 When calling a remote stored procedure using class ASEODBC, the following error is

returned if the procedure has an IN parameter of type NUMERIC:

DIAG [HY104] [DataDirect][ODBC Sybase Wire Protocol driver]Invalid precision value. Error in parameter 1. (0) (Duplicate of CR 323070.)

322730 A problem in the join optimization phase for some queries for which the join optimizer selected a join plan where the right join tree below a hash pushdown or sort/merge pushdown join contained additional hash pushdown or sort/merge pushdown joins, could under some circumstances cause server failure. This problem has been fixed.
322760 A problem caused a server deadlock when the buffer caches were stressed.
322939 When a multiplex query server is promoted to be a write server before a backup, a dummy row is left in the sysiqfile and sysfile tables for the original IQ_SYSTEM_TEMP dbspace. The restore operation tries to restore this file, which conflicts with the other temporary dbspaces, and the restore fails.
322940 An incremental restore operation could fail if no database changes were made between the last full backup and a subsequent incremental backup. This could occur for example, during a virtual backup.
322991 An attempt to drop a table with 211,000,000 rows caused server failure and returned a "memory corruption detected" error.
322996 A procedure that created a nested view in a loop failed

with the error "correlation name A not found."

In 12.5 esd2, the error is "column '' not found." Duplicate of CR 324035.

323403 On a machine with a very large number of CPUs,

an ASIQ server may fail while creating

a very large database with the default

main cache size.

323417 In Adaptive Server IQ 12.5, Chained=OFF was not doing an implicit commit after commands like INSERT, UPDATE, or DELETE, or TRUNCATE.
323539 The "Other Versions" display returned by sp_iqstatus was incorrect.
323566 A query with a host variable in the select list could return the non-fatal internal error:

IQ Internal error. Please report this to Sybase IQ support.

-- (dfe_HostVar.cxx 250)

Duplicate of CR 326228.

323760 The below select statement does not show the result set in DBISQLC if the db was created with UTF8 and the engine was started with -ct: select char(233).

The problem does not exist in DBISQL (java)

323869 Committing certain REVOKE statements may result in an unresponsive server.
323983 Using Ctrl-C while processing a multi-level hash push down join with union views caused server failure and the following Signal 11 error:

*** SybaseIQ Abort at st_server.cxx:1037 for PID: 174 ***

324247 Server failure with the error "Memory Allocation size too large" occurred when running a 300+ UNION ALL statement. An expression cannot be larger than the PAGE SIZE of the database. Duplicate of CR 327225.
324254 When a session using Open Client isql makes any reference to a remote server, the

connection to the remote server (from the SA engine) is not closed correctly when the

client disconnects. Connections from dbisql java are handled

correctly with the connection closed on disconnect.

324387 A certain cartesian join query causes the server to fail with the following

Signal 10 error:

*** SybaseIQ Abort at st_server.cxx:1037 for PID: 5410 ***

Same as CR 324390.

325101 A certain query on non-unique HG indexes caused server failure and the following Signal 10 error:

*** SybaseIQ Abort at st_server.cxx:1037 for PID: 15979 ***

Caught signal 10, program abort

325116 Doc enhancement request: add an IQ system tables poster to the IQ doc set, such as we publish for ASE and RepServer (color, approx. 26" x 32"). The customer would like to see the IQ system tables diagram in a poster. The system table diagram currently in the Reference Manual is too small and not easy to be posted to wall for group discussion.
325125 An UPDATE statement caused a server failure with a signal 11 error. The statement contained CASE WHEN clauses, for example:

UPDATE CONCORD

SET A.err_cd =

(case when substr(A.packet,1,10) = 'HOST ERROR' then 'HOST ERROR'

when substr(A.packet,1,3) = 'TXF' then substr(A.packet,56,10)

else '' end),

A.err_gb =

(case when substr(A.packet,1,10) = 'HOST ERROR' or

substr(A.packet,1,3) = 'TXF' then 'E'

else 'O' end)

FROM CONCORD A

WHERE trdate like '20030625%'

325127 On HP-UX systems, a query with more than 24 tables in a view could cause server failure with the error "Sybase IQ Abort at hos_eom.cxx:205."
325436 Not verifying the size of a raw partition during the restore could cause a problem where a dbspace is defined to be larger than the raw partion where it was created.
325501 Executing a certain query sometimes failed, returning the error s_bufman.cxx:1791 or s_bufman.cxx:3717.
325830 An unresponsive server may result when a race condition

occurs between 'backup' and any other connection performing

the first operation of a new transaction.

325890 MPX/SJC: Allow use of other DBA user to control database
326031 A multiplex query server failed in db_catReplRow::OpenMCIndex() while processing Table Level Versioning (TLV) updates.
326723 If a view containing a UNION and defined with SELECT * is no longer valid because columns have been added to the tables referenced in the view, a query referencing that view could cause an unresponsive server.
326839 In an UPDATE statement, omitting the equality token from a SET clause enclosed in parentheses caused server failure and a SEGV error from "static SA_RESULT AnnotateUpdate(a_ptree_info *info, a_statement *stmt)." Duplicate of CR 309290.
326880 If the option HASH_THRASHING_PERCENT has been set to any value other

than the default value, it should appear in the query plan.

327214 "Connection failed: Database server not running" when attempting to connect to the database using ODBC. The problem occurs when there are 3 servers running on the same host machine, and the one having the problem is listening to port #2638 and is started last. There is NO problem if it's started first.
327299 Inserting the date '0001-01-01' into a DATE index or

a value of '0001-01-01 00:00:00' into a DTTM index caused

server failure. Duplicate of CR 327307.

327523 A LOAD statement that explicitly set the BLOCK FACTOR

value greater than 10000 loads zero rows instead of exactly

one row.

To avoid the problem, always set BLOCK FACTOR less than or equal

to 10000 in the LOAD statement.

327563 The following query returned an incorrect result

on a Sun platform and caused a server on HP-UX to

fail with a Signal 10 error:

SELECT ... SUM(b2.num1) AS num1

FROM (SELECT ...) b1,

(SELECT ... sum(1) AS num1

...

GROUP BY char12, date1) b2

...

GROUP BY char12, date1

327958 Java memory exhaustion could cause a java (TDS) client to get stuck in CANCEL, causing an unresponsive server. TDS connections stuck in CANCEL more than 30 seconds are now dropped from the server.
329013 Under rare circumstances, a deadlock could occur when active connections exceeded iqgovern and a cancel or drop connection was in progress.
329097 A UNION ALL VIEW query returned a non fatal exception from dfe_PartitionedColumn.cxx (line 489) if a selected column was not type CHAR or VARCHAR and lacked a LF, HG or FP index. Duplicate of CR 313832.
329263 This is a feature request that the first parameter to the IQ DATEFORMAT function should accept a string as it would in ASA.

Currently, the first parameter must be a date, time, or timestamp and cannot be a string. It is documented in the IQ Reference Manual that the first parameter (datetime-expression) to the DATEFORMAT function MUST NOT be a string.

While in ASA and ASA documentation, there is no such limit.

329275 Under certain conditions, s_bufman_exception or free list verify errors could occur. Running sp_iqcheckdb could report duplicate block errors. The problem is corrected. [Duplicate of CR 327733]
329306 An issue existed in queries where the number of selected items is less than the number of columns produced from a derived table or a view. If split group by optimization is applied, these queries could be rejected with the "Unable to evaluate expression" error from dfo.cxx. If split group by optimization is disabled, these queries work correctly. CR 330657 and CR 333813 are duplicates.
329963 Multiplex: if you follow the procedure in "Replacing write servers" in the Adaptive Server IQ Multiplex User's Guide to replace the write server with a query server, and use the name of an existing query server for the new write server, the procedure will fail. Although the documentation is clear on this point, the stored procedures should prevent use of an incorrect server name.
330192 Setting to limit the place where files with Temp_Extract_Name1 can be put.
330391 Infrequently, a multiplex server with many recovered transactions to checkpoint may run out of space during the recovery checkpoint. If you cannot connect and add a dbspace, restart the database in single node mode, which causes retained versions to be deallocated and the checkpoint to succeed.
331014 Join queries that tried to insert data longer than the length of the field caused the server to fail at hos_dfe_SIN64_SIN16_NUMERIC_EQ on both HP and SUN systems.
331015 Under some circumstances for queries specifying an ORDER BY

with one or more descending direction indicators (DESC),

the query was rejected with an internal error because of

incorrect propogation of the ordering direction information

within the query optimizer.

331141 Interrupting a DELETE command could cause a deadlock.
331286 Certain queries with all null columns in the select list may run slower than expected.
331451 During defragmentation, indexes must be dropped and recreated. This leaves a production table without a critical index. Being able to copy an index, then drop and recreate the original, then drop the copy would eliminate this gap.
331987 If a connection using TDS protocol failed, returning NULL from the CreateConnection function, the server failed at TDSPres::RequestLoginFinish().
332003 The server may fail with error "Index is active. db_cati.cxx line 531." under the following circumstances:

User A creates a table and before inserting data to the table creates an index for every column. While User A is creating the indexes, other users execute SELECTs on the table created by User A.

332004 The database option SignificantDigitsForDoubleEquality controls how many significant digits to the right of the decimal point in exponential notification are used in double equality testing. Allowed values range from 0 to 15. The default, 0, meands "use all digits."

For example, when the option is set to 12, these numbers would compare as equal:

1.23456789012345

1.23456789012389

When the option is set to 13, they would compare as unequal.

Because doubles are stored in binary (base 2) instead of decimal (base 10), this setting gives the approximate number of significant decimal digits used.

This option affects equality tests between two complex arithmetic expressions, not those done by the indexes.

Server restart is not required for the option to take effect.

332044 Request the document cleanup in the next major release for consistent use of filename for srvlog, which is sometimes spelt as svrlog in the document.

In the 12.5.1 release the extention will be ".srvlog" on all platforms.

332162 The query SELECT SUM(m1), SUM(m1*0.08) FROM T1

was rejected at dfe_ArithmeticExpression::209

(ASA Error -1001006: Data exception -

data type conversion is not possible.)

This query failed for m1 of datatype INT

or NUMERIC on both Sun and NT.

332851 When a query server is deleted via Sybase Central, the SQL Remote process is inadvertently stopped on the writer server.
332940 If a user executed a LOAD command to load a table

that has a primary key and/or unique constraint and

- IGNORE CONSTRAINT UNIQUE was specified, AND

- one or more UNIQUE constraint violations occurred

then it was possible that the primary key and/or

unique constraint would have been incorrectly built.

The user would have noticed this either by a query

returning wrong results or sp_iqcheckdb reporting

that a HG index used to represent the primary key

or unique constraint was inconsistent and missing

various keys and row ids.

332962 While running sp_iqcheckdb to verify the database in either IQ 12.4.3 or IQ 12.5, if a bitmap verify problem was encountered, the line titled `Bitmap Verify Errors' from the sp_iqcheckdb output reported double the number of errors that it actually detected. For example, the following portion of sp_iqcheckdb indicated 2 bitmap problem, but there was actually only 1 bitmap problem:

Container Statistics

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

Database Objects Checked','485012'

B-Array Count','4643'

.

.

'Bitmap Count','468536'

***Bitmap Verify Errors','2','*****

The IQ Message File will also contain two errors for each 1 bitmap problem it finds. The Message File will contain two failures that look similar to:

2003-09-20 05:20:20 0000000007 Exception Thrown from s_bmn.cxx:91, Err# 1, tid 231 origtid 231

and

2003-09-20 05:20:20 0000000007 Exception Thrown from s_bmn.cxx:100, Err# 1, tid 231 origtid 231

333314 Using VARCHAR strings greater than 255 bytes in databases with multi-byte collations could return unexpected results. [Duplicate of 331462 and 330102]
333865 The sp_iqcheckdb procedure verify mode could incorrectly report DTTM and TIME indexes as inconsistent when the indexes were actually correctly built.
334016 REPEAT string function used in databases with multi-byte collations could return unexpected results.
334088 Under some circumstances a predicate of the form:

DATEPART(<part-name-constant>, <date_and_or_time_col>) = <constant>

would in the presence of a DATE, DTTM, or TIME index fail to use that

index to compute a precise selectivity estimate.

334262 An issue existed where queries that processed many rows against a non-correlated IN-subquery predicate and where very few rows passed the predicate could not be interrupted by CTRL-C.
334761 Queries against view dbo.syscolumns could return

unexpected results depending on datatype due to

an incorrect condition check.

335108 Customer is moving their server via copying raw devices and need to move the .iqmsg file to a new filesystem. They would like to rename/relocate the .iqmsg file but has a very large database so RESTORE/RENAME is impractical.

Wishes to be able to rename the IQMSG file from IQ, or with an external utility like DBLOG instead.

335845 When the IQ buffer cache monitor was invoked with the

-debug flag, the output lines that began with "CatCountLock" and "CatUserLock"

included incorrect statistics for "Locks", "Waits", and "Wait%".

336032 A new startup switch was added in order to specify the number of CPUs in the processor set available to Adaptive Server IQ. See "Setting number of CPUs" in "Special installation and migration instructions" in the Adaptive Server IQ Release Bulletin.
336038 The threads for the automatic cache resize and a CREATE TABLE operation were each waiting for the other to complete, but each held a lock that the other needed released, causing a deadlock and an unresponsive server.
336198 After replacing a write server and then marking one of the query nodes as excluded, creating a temporary dbspace on the writer may fail.
336200 Creating a new database via Sybase Central fails if the create uses an existing IQ server and the IQ Agent process is not running on the supporting host machine. Creating a new database via an existing IQ server should not require the agent process.
336205 Dynamic catalog cache resizing did not work on AIX 5.x, and

could result in server failure with the error "Fatal error:

memory exhausted" reported in the IQ server log.

336353 A syntax error in the table.column expression caused a SEGV error in a multibyte collation database. Correct syntax requires a single ".".
336491 The non-ANSI support for BLANK PADDING OFF for the CREATE DATABASE statement has been removed from the product. The changes will not affect databases previously created with BLANK PADDING OFF.
336657 Using improper FILLER() syntax on a LOAD command

would cause server failure in 12.5 but was ignored in 12.4.3.

Now an error will occur if FILLER() is specified.

FILLER(1) may be used instead of FILLER().

336658 RI concurrency checking is done for insert/load, update, and delete even if the user sets DISABLE_RI_CHECK=ON.
336659 The INSERT...LOCATION does not identify itself to ASE. During INSERT...LOCATION execution, running sp_who does not show the hostname from which the INSERT...LOCATION has connected. Also, the connecting program name does not appear in the sysprocesses row in the MASTER database.
337548 Change the Load_Memory_MB upper limit from 500MB to 2GB (or 2000MB).
337572 CREATE TABLE may take longer as the volume of catalog information

for Referential Integrity (primary/foreign key relationships) increases.

337603 An issue existed where a case expression that returned a character datatype was rejected with a conversion error when different arms of the case expresion mixed values less than 255 bytes and values more than 255 bytes.
338002 An IQ server may become unresponsive during CREATE DATABASE on a raw device if the path to the raw device is incorrect. This problem is more likely to happen on single-CPU systems.
338288 The sql statement "ALTER TABLE tablename REPLICATE ON" causes the server to fail.
338423 Sybase IQ has a one terabyte file size limit. The limit has been removed.
338827 Under some circumstances involving moderate numbers of active users

(moderate being defined for an N CPU system as between N+1 users

and 2*N users) the query engine would choose to go more parallel

then was optimal for a server that heavily loaded.

339149 The system tables IQ_MPX_SYNC and IQ_TLV_LOG are incorrectly listed in the section "System tables and views" in Chapter 1, Adaptive Server IQ Administration and Performance Guide. These tables have been removed from Adaptive Server IQ.
339441 IQ 12.4.3 on HP-UX will generate an error on the first statement send to IQ via Open Client:

Msg 102, Level 15, State 0:

ASA Error -131: Syntax error near '(end of line)'

All subsequent statement will go fine

339752 Statements involving a CASE, IF, NULLIF, or COALESCE

expression where the result of the expression can be

determined at query optimization time are now simplified

by the query optimizer.

339756 sp_iqcheckdb stored procedure could stop responding if duplicate blocks are detected.

This problem could cause the sp_iqcheckdb stored procedure to stop responding.

The system would appear idle (no CPU/IO activity). A stack trace of the running

server contained a frame with the name SetBitsGetDuplicates.

340204 Multiplex: committing a transaction on the write server after a DROP of a temporary table incorrectly advanced the write server's catalog version and put query servers out of synchronization.
341119 ASIQ plug-in in Sybase Central displays all objects despite filter settings for objects.
341538 The Encryption check box in the Sybase Central Create Database Wizard was selectable, which indicated that the IQ database could be created as encrypted.

The check box has been removed because IQ databases do not currently support data encryption.

341659 After alter database upgrade from isql, sp_iqcolumn returns error 195
341738 On AIX platforms only, if the IQ performance monitor

was running, the server could fail with no error message.

342298 Feature request for encryption for data storage in IQ
342404 The server fails when trying to execute a LOAD statement using an input file that has a double colon ("::") in its name. An "invalid filename" error is now displayed.
342615 An IQ server could become unresponsive during concurrent execution of REVOKE from

multiple user connections.

342827 An issue existed where queries that used the parallel group by hash algorithm and the database had a multi-byte character set collation could be rejected with an assert from "dfe_BaseColumn.cxx". This issue has now been resolved.
343004 Allow option to mask password when sql logging is turned on
343104 An issue existed where a query that had more than one sort-merge join against a complex derived table could in rare circumstances return too few rows.
343230 ODBC Administrator lists Adaptive Server IQ User Data Sources created using the dbdsn command as "Adaptive Server Anywhere" instead of "Adaptive Server IQ 12" sources.
343809 Fixed a server failure that could occur with a query

containing all of the following:

(1) an uncorrelated IN subquery, for which the optimizer

had selected the sort-based execution algorithm

(2) at least one additional subquery predicate

(3) both subquery predicates involved columns from

a single large table

(4) that large table was joined to a smaller table

(5) the optimizer had selected the NLPD join algorithm

to execute that join

343902 Certain join queries where some selected columns contain nulls and where at least one 'AND' is in the 'WHERE' clause could fail at s_bufman.cxx:3717 with a message 'Destroying Locked Logical Buffer'. If a detail query plan is available, this issue can further be identified if it contains a nested loop push down.
344667 For databases with multibyte collations, queries using LF and HG indexes on columns with BINARY datatype returned incorrect results.
344765 Add ability to find UNIX process ID & host info for an IQ user using ISQL
345466 sybinstall gave improper warning of 32 bit on the correct 64 bit Aix platform
346152 Allow ability to create HG unique index with columns containing null values.
346215 On Windows servers only, an unnecessary one-second pause

would occur when opening a TCP/IP connection.

346346 SELECT DISTINCT on DATE COLUMN FROM TABLE where the DATE column has multiple NULL values will incorrectly repeat the NULL values if the COLUMN does not have a LF or HG index defined.
347014 Allow ability to create node via a script rather than Sybase Central
347794 Feature request to add mechanism to adjust many-to-many join estimates to be more conservative.
348738 Customer simply wants the ability to perform a read on the table while in any state.

**Resolution**

Not targeted for any future release of ASIQ

349333 Under the following circumstances, queries might

return inconsistent results or cause server failure:

1) There was a simple predicate on a column

2) That column contained one or more NULL values

3) The column was being compared to one or more

constants that were beyond the dynamic range

of the column's data type

4) The effect of the predicate should have been to

pass all non-NULL values in the column

For example:

T.COL_TINYINT < 300.

The specific symptoms of this problem depended

on the precise combination of data and query.

Duplicate of CR 351513.

349338 A query using a view that contained both a user defined function and

CONTAINS in the WHERE clause would ignore the CONTAINS criteria.

350034 INSERT...LOCATION from ASE TEXT and IMAGE columns can now be inserted to appropriately typed columns in an IQ table (LONG VARCHAR (VARCHAR for esd11) and LONG BINARY respectively). It is possible that TEXT and IMAGE can be inserted into other IQ datatypes if internal conversion supports it. All data to be inserted will be silently truncated at 32767 bytes.
350039 LOAD table from named pipe on NT gives error "ASA Error - 1006096: Backup device is busy \\.\pipe\a2 -- (hos_ion.cxx:415)" This error occurs in v12.5 Sybase IQ. The problem is fixed in v12.6.
350162 IQ "hangs" when you reach your connection limit to the server and at that moment you get

You have run out of IQ STORE dbspace in database D:\Sybase\ASIQ-12_5\demo\asiqdemo.db. In another session, please issue a CREATE DBSPACE ... IQ STORE command and add a dbspace of at least 8 MB.

350411 Customer wants a more meaningful error status other than -6 "Miscellaneous user error" when a failed attempt to write to a table due to another user writing to the same table occurs.
350729 sp_iqcheckdb incorrectly reports error during VERIFY of a non-unique, multi column hg index. The following sequence will show the error.

create table t1 (c1 int, c2 int, c3 int)

insert t1(c3) values (9)

create hg index hg1 on t1(c1, c2)

sp_iqcheckdb 'verify index hg1'

350847 Non-fatal messages reported to the IQ Message file during sp_iqcheckdb could cause an incorrect report of a bitmap verify error at s_bmn.cxx:99.
350982 Running queries or sp_iqcheckdb could produce a non-fatal error with hos_mvbio.cxx:466 and s_buf.cxx:1137 in the stack trace. You might also get a message about a 'Bad block number passed to object' in the IQ Message file. This failure could occur with non-unique HG indexes or word indexes.
351107 On AIX64, the limit of 1024 open file descriptors has been removed.

Reaching the 1024 open file descriptor limit could result in

"too many files" or connection errors and could cause INSERT/LOCATION

to fail with "Connectivity libraries cannot be found".

351590 When performing forced recovery or leaked blocks recovery, you must start the database with the ".db" extension, not ".DB". For example:

start_asiq -n my_db_server -x 'tcpip{port=7934}'

-gd dba -iqdroplks my_db /work/database/my_db.db

This information was omitted from "Repairing allocation problems" in Chapter 2, Sybase IQ Troubleshooting and Error Messages Guide.

352758 Users requested the ability to disable compression

on columns having datatype 'long varchar' or 'long binary'.

The reason for this request is that certain types

of data (e.g., jpeg) do not compress. So by allowing

users to disable compression, the cost of trying

to compress data that won't compress is avoided thereby

saving CPU cycles.

353482 A complex query containing an outer join and arithmetic

expressions or functions over columns from the NULL

generating side of the outer join could be rejected

with an internal error. If this error is hit, the

stack trace will contain "dfo_Join::NeedCloneDFE".

353523 On Windows servers only, some language files (locales) for the Open Client SDK were missing from the IQ 12.5 installation.
353537 The option "Dbcc_Log_Progress" has been added to the product that will output sp_iqcheckdb progress messages to the iqmsg file during sp_iqcheckdb execution. When the option is ON, each time a table, field, or index is processed by sp_iqcheckdb two messages will be written to the iqmsg file. One message will indicate that processing of the object has begun and the other message will state that processing of the object is complete. Sample of some messages for sp_iqcheckdb 'allocation table nation':

Start ALLOCATION table: nation

Start ALLOCATION processing index: ASIQ_IDX_T445_C1_FP

Start ALLOCATION processing index: nationhg1

Done ALLOCATION table: nation

Done ALLOCATION processing index: nationhg1

Done ALLOCATION processing index: ASIQ_IDX_T445_C1_FP

353538 It is now possible to specify an indextype for all of the sp_iqcheckdb modes. The new syntax is:

sp_iqcheckdb ' mode target' (Where 'mode' is as it was before.)

target:[indextype idxtyp] database | database resetclocks | { [indextype idxtyp] table table-name | index index-name [...] }

idxtyp: is one of FP, CMP, LD, LF, HG, HNG, WD, DATE, TIME, DTTM

Example: To CHECK all of the FP indexes in database asiqsemo...

sp_iqcheckdb 'check indextype fp database'

Example: To VERIFY the FP and HG indexes in table customer and the lf indexes in table tableau...

sp_iqcheckdb 'verify indextype fp indextype hg table customer indextype lf table tableau'

If the user specifies an indextype that does not exist in the target, error "The specified indextype does not exist in the given target. -1000219" will result. For example, if there are no indexes of type "date" in table "blah", then

sp_iqcheckdb 'check indextype date table blah' will result in this error. If there are some hg indexes in the table, then

sp_iqcheckdb 'check indextype date indextype hg table blah' will check only the hg indexes.

353695 When creating a new query server, the IQ agent could generate a time-out error if the dbbackup process took longer than five minutes. Instead of reporting the error, the Create Query server wizard tried to start the new server, only to fail in startup.
353819 upper(),lower() functions do not convert accented characters appropriately
353823 The sp_iqcheckdb (check index...) procedure did not return a completed verified list for all indexes submitted.
353999 Synchronization via sybase central could fail if the dbbackup process took longer than five minutes. This is because the IQ agent had a built in time-out value set at five minutes. But some database files were too large to back up in five minutes and Sybase Central therefore could not be used. The agent needed to support a configurable time-out value.
354034 A checkpoint, for example as part of backup, might cause server failure if the database was in an out-of-space condition.
354688 The server could fail on an insert, load, or update

when the following conditions were true:

a) it had a table (already loaded) with a date or datetime

column, and number of distinct year values in the DATE or DTTM index

exceeded 200

b) the user performed an incremental insert into the table

354983 A database that was created with IQ v12.4.0 cannot be restored to IQ version 12.5.0 or later. This is fixed in 12.5.0 esd11 and 12.6.
355250 WATCOM stored procedure with a SQLCODE or SQLSTATE as parameter with a T-SQL variable assignment SELECT @AAA=col1 from table will crash IQ silently.
355297 Issue was the result of improper handling of

expressions containing a varying host variable

plus constants or additional host variables,

but containing no columns or aggregates.

356067 A query can cause the IQ Server to fail with a Signal 11 and a stacktrace. The stacktrace contains v2s_bmcontext::InitializePrevBit()
356217 On IBM RS/6000 systems, when the Sybase Central Agent started up the dbremote process, the password parameter could have been obtained via the ps command.
357273 IQ 12.5. Incorrect results returned when using a case insensitive database and data that includes special characters like n tilde (�) and the search argument has has the character in upper case. The behaviour differs depending on the collation being used.
357358 During the execution of predicates using an FP index

from a very large table, several minutes could pass

between checks for whether the user had requested

that the statement be cancelled or the connection

dropped. Additional cancellation checks were added

to make the maximum delay during this type of

operation be a few seconds.

357533 The customer does not want to change all of their statements to "column1 >= constant and column2 <= constant" and are requesting that an index be used when using a constant in the following predicate statement: "constant between col1 and col2".
358638 ASIQ 12.5 esd 10. When the iqmsg file hits the IQMSG_Length_MB (setting and wraps to the top, the following re-starts of IQ are writing the initial db open and start up messages at the end of the iqmsg file then re-wraping to the top instead of restarting at the <next msg insertion place> message. This will grow the iqmsg file further past the IQMSG_Length_MB setting size each restart.
358707 In unchained mode, The UPDATE CURSOR operation may have gotten a stack trace.

IQ Server should return an error message correctly.

358882 29 oct 2004 update: Default Open CLient Library password encryption is supported only when connecting to SQL Server (v10 and later), ASE, and Open Server (v10 and later). In order to allow users to specify whether or not they wish to use password encryption while connecting, the INSERT statement syntax has been enhanced. The new syntax is:

INSERT [ INTO ] owner.tablename [ ( column-list ) ]

insert-load-options

[ LOCATION 'servername.dbname' [ ENCRYPTED PASSWORD ] [ PACKETSIZE packetsize ] ]

{ select-statement }

If "ENCRYPTED PASSWORD" is specified and the remote server does not support Open Client Library default password encryption, an error will result indicating an invalid userid or password was used. Sybase IQ, when used as the remote server, does not support this password encryption.

(-end of update-)

Password encryption always on when connecting to OpenClient with INSERT.... LOCATION.

10 aug 2004 update: Default Open Client Library password encryption has been enabled for INSERT...LOCATION when IQ connects to ASE. This new functionality has been added for the 12.6 release.

359391 The following example shows how you can prevent a user from connecting after five failed login attempts. This example uses a ConnectFailed event handler to total the number of failed connect attempts. The totals are stored in table dba.event_table. The first time a user fails a connection attempt a row will be inserted to dba.event_table for that user. On subsequent failed connections, the count in that user抯 row will be updated. A ConnectFailed event cannot prevent a user from continuing to try to connect. The login procedure must be used to deny access if the allowed number of failed login attempts has been exceeded. This example will keep track of failed login attempts for all users including those who may be database administrators.

First, create the table to hold the user information and insert a row for each user.

create table dba.event_table ( username char(128) not null,

failed_login_attempts integer,

primary key (username) );

Create the event handler that will increment the number of failed login attempts.

create event ev_badlogin type ConnectFailed handler

begin

declare uid char(128);

declare xx integer;

set uid = event_parameter(慤ser�);

if exists (select * from dba.event_table

where ucase( uid) = ucase(username)) then

-- The user is already in the table.

update event_table set failed_login_attempts =

failed_login_attempts+1

where ucase(username) = ucase(uid);

else

-- Insert the user for the first time.

insert dba.event_table values (ucase(uid), 1);

end if;

select failed_login_attempts into xx from dba.event_table

where ucase(username)=ucase(uid);

-- It抯 not possible to stop the user from attempting to connect after 5 tries.

-- Instead, send a message to the server console to notify the database

-- administrator that a user has exceeding the allowable connect attempts.

if xx > 5 then

raiserror 17001 uid + � has had more than 5 failed login attempts.�;

end if;

end

The login procedure.

Create procedure dba.check_logins()

begin

declare xx integer;

declare uid char(128);

-- See if the connected user is in the event_table and proceed accordingly.

if exists (select * from dba.event_table

where ucase(username) = ucase(current user)) then

select failed_login_attempts into xx from dba.event_table

where ucase(username) = ucase(current user);

if ( xx >= 5 ) then

raiserror 17010 current user + � has been locked out by the

Database Administrator.�;

else

-- The user has connected.

-- Remove the user抯 row from dba.event_table and call

-- the default login procedure for the database.

set uid=current user;

delete DBA.event_table where ucase(username) = ucase(uid);

call sp_login_environment();

end if;

else

-- The user is not in dba.event_table, but has connected. Call the default

-- login procedure for the database.

call sp_login_environment();

end if;

end;

To enable all users to run the login stored procedure and set the login procedure option.

grant execute on dba.check_logins to PUBLIC;

set option PUBLIC.Login_Procedure = 慸ba.check_logins�;

To enable a user that has exceeded the number of allowed failed connection attempts to connect, a database administrator must delete the row for that user from dba.event_table.

359706 The request for the grouping about would be an enhancement to the T-SQL NTILE

functionality.

The rank functionality would need something like:

rank () over ( [query_partition_clause] order_by_clause )

same with dense_rank

dense_rank () over ( [query_partition_clause] order_by_clause )

This partition clause would really be similar to a group by clause.

360194 Under certain conditions, when executing INSERT..LOCATION in conjunction with a mechanism to provide basic connectivity to a non-Sybase data source (for example, DirectConnect), Sybase IQ incorrectly determined that the INSERT..LOCATION operation succeeded, and committed the results instead of rolling back the operation.
361123 The performance of IN predicates has been improved for some

queries where there is a large number of rows in the table.

361125 The performance of IN predicates has been improved for some

queries where there are many rows in the table.

361147 The performance of IN predicates has been improved for some

queries where there is at least one additional restrictive

predicate on a column from the same table.

361254 The following SQL will fail with an "IQ internal error" message.

drop table t2;

create table t2(c1 int, c2 int, c3 int);

create hg index t2c1c2hg on t2(c1, c2);

insert t2 values(1, 2, 3);

insert t2(c3) values(1);

delete from t2 where rowid(t2) = 2;

This is fixed in 12.6

361594 The following sequence of statements will cause the server to fail at hos_bv.h line 603:

create table t1 (c1 int, c2 int, c3 int)

create hg index hg1 on t1(c1)

create hg index hg2 on t1(c1,c2)

sp_iqcheckdb 'verify index hg1 index hg2'

The failure occurs because the two hg indexes overlap on a column.

361871 There was an intermittent problem where the IQ server became unresponsive.
362102 Users are unable to connect if either of the IQ User Admin tables (IQ_SYSTEM_LOGIN_INFO_TABLE or IQ_USER_LOGIN_INFO_TABLE) has been dropped.

Users with DBA privileges will be able to connect if either table is dropped. A message will be output to the server console to notify the dba or operator that non-DBA users will not be able to connect until the table(s) are put back.

The IQ_SYSTEM(USER)_LOGIN_INFO_TABLE cannot be found or accessed.

Non-DBA users will not be able to connect until the table can be accessed.

362141 Feature Request:

Put in for an option IQ that would allow for truncation of the iqmsg log such as "IQMSG_TRUNCATE"? The option would have 2 values, the default being 'NO'.

362600 Request a feature like Oracle's 'OPTIONALLY ENCLOSED BY '"' ' option, which allows input fields to include the indicated delimiter in their text if they enclose it between double quotation marks.
362699 Implicit conversion from CHAR types to NUMERIC types is now allowed. For example,

create table t1 (c1 int)

insert t1 values ('9')

will insert the row.

363023 'create existing table' command from IQ to Oracle gives error 'could not access column information for the table'
363865 Query performance was affected by extensive IFNULL( < expr > ,SPACE(10), < expr > ) or COALESCE( < expr > ,SPACE(10)) expressions; for example, turning empty strings into NULLs. This issue has been resolved.
364386 Users at customer site are looking for certain useful functionality they have in ASE -- a utility like defncopy to extract stored procedures from the server. Customer has asked for an enhancement request to be opened to provide this functionality.
365163 behavior of info available in sa_eng_properties needs to be explained
365435 While running multiple connections that fetch from different proxy tables and different remote servers using ASEJDBC, if one application was terminated, then the Java virtual machine could no longer be started.
367460 Sybase IQ will not propagate CREATE, ALTER, and DROP statements for procedure and function definitions from the write server to query servers in a multiplex. You must use one of the following methods to keep procedure and function definitions consistent across multiplex servers.

1. After executing the DDL statements to modify

procedures and functions at the write server,

execute the same statements on each query

server. Create a SQL script for this approach

to ensure consistent definitions.

2. After executing the DDL statement(s) to modify

procedures and functions at the write server,

synchronize each query server.

ALTER and DROP statements for procedures and functions can fail if the existing definition is in use by another connection to the server. The user should schedule maintenance of procedures and functions for periods when the existing definitions will not be used. This information was omitted from the Sybase IQ System Administration Guide.

368173 The performance of IN and range predicates (<, <=, >, >=, BETWEEN)

has been improved for some queries where there is at least one

additional very restrictive predicate on a column from the same

table.

368318 The sample command for restarting dbremote to truncate the transaction log which has been described

in MPX User's Guide is incorrect. It is necessary to add -x switch.

369558 The output of the sp_iqlistpasswordexpirations stored procedure has been changed as follows: The column "Days_till_Expiration" now is the number of days until the password expires. If the password has expired, "Expired" will appear in the output in this column. A "0" (zero) means that the password does not expire. A new column, "Password_Expiration_Interval" has been added. This column contains what the "Days_till_Expiration" used to contain. That is, the total number of days the password is valid on the date it was created. A "0" (zero) means that the password does not expire. For example, on day 1 a user is created with a password that is valid for 10 days. When the stored procedure sp_iqlistpasswordexpirations is run on day 7, the value of Days_till_Expiration for that user will be "4" and the value of Password_Expiration_Interval for that user will be "10".
369612 When creating an IQ database, a minimum 4k ASA page size will be silently enforced. Larger ASA page sizes may be used, but if the user tries to use a smaller page size, it will be set at 4096 with no notification to the user.
369761 Duplicate of #355297.

Issue was the result of improper handling of

expressions containing a varying host variable

plus constants or additional host variables,

but containing no columns or aggregates.

370316 When creating a main dbspace on a write server, you must create aliases for the query servers before you synchronize them or they cannot open the new file. This was omitted from chapter 5, "Working with Database Objects," in the Sybase IQ System Administration Guide.
370429 Request option to set resources by DBA at server level instead of session level.
370902 3 nov 2004: sp_iqaddlogin will now use the default number_connects from IQ_SYSTEM_INFO_TABLE for a new login.
371155 Some sql statements that have identifiers containing double quotes may fail with a syntax error. For example,

create table "t1""t1" ( c1 int )

will fail with a syntax error without the fix that this CR provides. This statement should create a table, t1"t1, with a single column, c1.

371375 When loading data into a Word Index that is longer than the LIMIT specified while creating the index, the entire load will terminate with an error and rollback.

This enhancement will allow the load to continue when such an error occurs. Rows where data to be loaded into a Word Index is longer than the specified Word Index LIMIT will not be loaded into the table and the rows where data does not exceed the maximum permitted word size will be loaded. If a row is not loaded because a word exceeds the maximum permitted size, a warning will be written to the iqmsg file. WORD size violations can be optionally logged to the MESSAGE LOG file specified in the LOAD TABLE statement.

The existing behavior will be the default and the new behavior will be enabled by an option to the LOAD TABLE statement.

Here is the LOAD TABLE syntax showing this option:

LOAD [ INTO ] TABLE { owner.]table-name [ (column-name, � ) ]

FROM filename-string

[ load-option � ]

load-option:

[ CHECK CONSTRAINTS { ON | OFF } IGNORE ]

[ DELIMITED BY string ]

.

.

.

[ WORD SKIP number ]

� [ ONLY LOG logwhat [,匽 ]

WORD SKIP option : If the option is not specified, the LOAD TABLE will report an error and rollback on the first occurrence of a word that is longer than the specified limit. number specifies the number of times the 揥ords exceeding the maximum permitted word length not supported.� error will be ignored. 0 (zero) means there is no limit.

ONLY LOG option: The keyword WORD has been added to the list.

372186 Loading data into a non-unique HG index would occasionally fail

with an IQ Internal Error at location s_gUtil.cxx; 682. This has been fixed.

372631 If a batch containing a call to an external procedure is executed, and the external procedure is then subsequently canceled, then the batch continues execution instead of being canceled. This problem has been fixed.
372998 When using Open Client 12.5 ESD 14 with IQ 12.5 it is possible for IQ to fail if an active insert location connection is killed at the source server.
373114 Running sp_iqmodifyadmin 'enable' will now add userids with passwords that have been granted group to the admin tables.
373124 #temptable kept old definition in cache if same procedure dynamically created a temp table with the same name within the same session.
373249 Customer feels strongly about having the system procedures for logins maintain data in IQ_USER_LOGIN_INFO_TABLE even though the documentation represents this as an option if one cares to enable "the IQ User Administration.facility." They feel that login information should always be in the IQ_USER_LOGIN_INFO_TABLE and it should be correct.

Customer needs to lock logins and finds the system stored procedures for managing logins are inconsistent and leave holes in security and user administration. They are suggesting the following modification:

"Grant Connect" and "Revoke Connect" do not properly reflect logins in the IQ_USER_LOGIN_INFO_TABLE. Information should be maintained there for all logins. "Grant Connect" and "Revoke Connect" should be wrappered in IQ to do this, or an option should be provided to disable direct access to those commands. The IQ User Administration feature is compromised by having several ways to get around it, intentionally or inadvertently.

We should be updating this table after issuing those commands for 2 reasons:

a) To be consistent with running the "sp_iqmodifyadmin enable" to update the IQ_USER_LOGIN_INFO_TABLE with logins added to the SYSUSERPERM. Why do we offer a way to update what should be the single point of storage for all logins anyway?

b) It is too easy to run "sp_iqmodifyadmin enable" and then issue a "Revoke Connect" thereby orphaning logins in the IQ_USER_LOGIN_INFO_TABLE.

c) To provide a single point of administering logins by using the "IQ User Administration.facility". Administrating/monitoring and controlling logins is currently too messy.

373298 This subcase is to request a CR that IQ certification testing on AIX 5.3, currently scheduled for December, include testing with the Watson algorithm. Likely it is turned on using an environment variable; I don't know the setting but if it is not described in the AIX 5.3 documentaiton we get, I can go through my IBM contacts on this issue and get that information.
373883 A timing race when a database event occurred during database shutdown

caused a failure on an internal consistency check.

374292 A multiplex synchronize may fail with the following error in the Agent log file:

java.io.IOException: Not enough space

This indicates an out of memory condition, not lack of disk space or dbspace. This was

omitted from Chapter 1, Sybase IQ Troubleshooting and Error Messages Guide.

374729 Server fails when the SQL Anywhere index consultant is run after a

query that accesses IQ store tables. The diagnostic information in

the message file shows the dbi_partialopen function at or near the

top of the stack trace.

In ESD1, the "Index Consultant" button is disabled in the dbisql

front-end tool that is distributed with Sybase IQ. If the SQL

Anywhere index consultant is started by other means, it will

run without a server failure.

Note that in general the SQL Anywhere Index Consultant will not

produce any useful information for Sybase IQ databases; the Sybase IQ

12.6 Index Advisor feature is the proper tool for automatically

generating index recommendations for Sybase IQ databases.

374738 On AIX64, the Multiplex stop_server script could fail

with the error "IOT/Abort trap".

The issue is resolved in 12.6 ESD1 by regenerating the Multiplex

Admin Scripts for the Multiplex Servers via Sybase Central.

374825 Make the ASE-compatibility system stored procedures for managing logins -- sp_addlogin, sp_droplogin, sp_locklogin and sp_password.-- call their "iq" counterparts -- sp_iqaddlogin, sp_iqdroplogin, sp_iqlocklogin and sp_iqpassword. This will eliminate one source of inconsistency in user login management. Customer has provided sample modified versions of the "non-IQ" stored procedures. See /remote/cases Repro directory for -12 subcase.
374894 stop_asiq used the wrong PS format on SuSe 9.x, causing it not to identify servers correctly.
375333 The following example shows how to give non-DBA users the

ability to execute commands that require DBA privileges.

This example creates a policy that lets a non-DBA

user (user1) perform backup.

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

create procedure "DBA".do_backup()

begin

backup database

crc on

attended off

block factor 4

full

to 'fileA' size 2000

to 'fileB' size 2000

to 'fileC' size 2000

;

end;

grant execute on "DBA".do_backup to user1;

375585 The ALTER INDEX command returns an "index not found" error if you try to alter an index in a local temporary table. If you try to alter an index that is automatically created, such as a default index, IQ returns a "cannot alter index" error.

Only indexes in base tables or global temporary tables with owner type USER can be altered. This information was omitted from Chapters 5 and 6 of the Sybase IQ System Administration Guide, from Chapter 6, Sybase IQ Reference Manual, and from Chapters 3 through 6, Sybase IQ Troubleshooting and Error Messages Guide.

375822 Due to the virtual memory usage pattern within the Sybase IQ server, virtual memory fragmentation could result, causing excessive process growth on Windows platforms. To reduce the likelihood of this problem, Sybase IQ now supports the use of Microsoft's low-fragmentation heap (LFH) on Windows XP and Windows Server 2003.
376130 It is unclear from the IQ documentation that an update command is not allowed on a table that is part of a join index. It is not mentioned in the section discussing join indexes and it should be.
376134 If an Open Client application opened a cursor which generated the "cursor options

changed" warning, then Open Client would fail to open the cursor. This problem has

now been fixed.

376550 Using "comment" on a local temporary table would result in

server failure. This issue is resolved and "comment" on

local temporary table is now prohibited with an informational

error "Cannot add a comment to a table declared as local temporary".

376618 You cannot connect to a Sybase IQ 12.6 server using an ODBC Data Source Name created for a 12.5 server, even if you specify the same server name, port number, and database name.

Workaround: Use the ODBC Data Source Administrator to remove DSNs created in 12.5

and add new DSNs.

376991 A query server may fail with error "Tried to insert a duplicate entry." at s_hashtb.cxx:290. This error might occur while performing a referential integrity check after replaying an "ALTER TABLE ADD FOREIGN KEY" from a write server where the foreign key is a multicolumn index for which one of the columns contains no data.
377444 The Sybase IQ server failed with a stack trace in s_dpidxfecth.cxx when CTRL-C interrupted a query.
377612 Performing an update on a table that contains a column with a default value of AUTOINCREMENT crashes the server with stack trace.
377882 Password expiration message send back to the client
378084 When using CIS Remote Data Access with a JDBC server class or

Java in a database, there was a chance that a SQL Error could

result in server failure.

378190 If an active IQ server ran out of temporary space with several transactions suspended waiting for additional temporary store, the server became unresponsive when the number of active queries equalled the number of allowed concurrent queries.
378369 Request: Implement a feature similar to ASE 12.4.3 sp_recompile that would allow stored procedures that used a table where a column was just added to see that new column with a SELECT * from table. This would mean both supporting the Transact-SQL WITH RECOMPILE option and implementing a similar stored procedure to that of ASE's sp_recompile.
378606 Using a CASE expression inside the VALUES clause of an INSERT statement generated a stack trace with a signal 11.
378609 After the error "A maximum of one subquery predicate per conjunct is supported

in this release", there was a chance server failure would occur.

378772 A customer was truncating

the .iqmsg file (for example, via the unix

command cp /dev/null <iqmsg file>)

to clear out old information in the file. This let the

customer collect new information from the .iqmsg

file at regular known intervals to help

monitor the database engine.

The ability to truncate the .iqmsg file in this manner

was accidentally removed when the .iqmsg file wrapping functionality

was added to Sybase IQ.

378924 When inserting a local table with rows selected from a proxy table on a remote server, the IQ server might fail if the remote server was down or not available. The failure only occurred if the INSERT ... SELECT statement made the first attempt to connect to the remote server.
378934 When the '-f' server command argument is used, the start_asiq script no longer reports an error from dbspawn that the server was not left open. Shutting down the server after discarding the transaction log is the expected behavior. After using '-f', the server must be restarted normally without the '-f' option. See Chapter 2 System Recovery and Database Repair of the Troubleshooting and Error Messages Guide.

New behavor:

> start_asiq @asiqdemo.cfg -f asiqdemo.db

Starting server demo_8888 on iqsunbld at port 8888 (02/08 09:23:53)

...

Database recovery in progress

Last checkpoint at Fri Feb 04 2005 15:54

Checkpoint log...

I. 02/08 09:24:03. Transaction log: asiqdemo.log...

I. 02/08 09:24:03. Forcing recovery without transaction log

I. 02/08 09:24:03. Rollback log...

I. 02/08 09:24:03. Checkpointing...

I. 02/08 09:24:03. Starting checkpoint of "asiqdemo" (asiqdemo.db) at Tue Feb 08 2005 09:24

I. 02/08 09:24:03. Finished checkpoint of "asiqdemo" (asiqdemo.db) at Tue Feb 08 2005 09:24

I. 02/08 09:24:03. Recovery complete

---IOX: Could not open script file

Wrapping iqmsg: Disabled.

Transaction log: asiqdemo.log...

Forcing recovery without transaction log

Rollback log...

Checkpointing...

Starting checkpoint of "asiqdemo" (asiqdemo.db) at Tue Feb 08 2005 09:24

Finished checkpoint of "asiqdemo" (asiqdemo.db) at Tue Feb 08 2005 09:24

Recovery complete

I. 02/08 09:24:04. Database server stopped at Tue Feb 08 2005 09:24

Database server stopped at Tue Feb 08 2005 09:24

Recovery complete

Make sure to remove the '-f' parameter before restarting the server.

379059 Server no longer displays message "---IOX: Could not open script file" at database open.
379440 A query that loaded invalid data into a FLOAT column failed with the ASA error -1006000 instead of returning a "Cannot convert" error (-157).
379489 The Sybase IQ server became unresponsive when running sp_iqtransaction.
379694 Running REFRESH ALL in Sybase Central returned a stack trace with a null exception.
379695 The LOCK TABLE statement is allowed but undocumented

in Sybase IQ 12.6. This statement prevents other concurrent

transactions from accessing or modifying a table. Syntax

is:

LOCK TABLE table-name [WITH HOLD] IN {SHARE | EXCLUSIVE}

MODE

Parameters are:

table-name - Must be a base table, not a view.

WITH HOLD - Holds the lock until the end of the connection.

Otherwise, releases the lock when current transaction is

rolled back or ends.

SHARE mode - Other transactions cannot modify the table

but have read access. Requires SELECT privileges.

EXCLUSIVE mode - Other transactions cannot execute queries,

updates, or any other transaction against the table. Requires

DBA authority or ownership of the table.

This statement blocks or delays other transactions that may

require access to the table. LOCK TABLE allows direct control

over concurrency at a table level, independent of isolation

level.

379969 When creating a stored procedure in dbisqlc and in isql without qualifying the procedure name and the procedure exists and is owned by another user, an error is thrown.
380038 When an event is executed, it runs on its own connection. If an event connection was dropped (either from Sybase Central or using the DROP CONNECTION statement), the server would have crashed, if it had been started with the -z switch.
380079 When an IQ Data Source Name was created with iqdsn (the IQ version of dbdsn) the new DSN could not be listed, viewed or deleted using iqdsn.
380583 A read-only query server may fail to deallocate all old versions of cached catalog objects.
380590 A race condition involving a user's connection being

explicitly dropped or implicitly timed out and a

different user interrupting a command just scheduled

to run by the IQ resource gate could result in a

deadlock.

380625 There is new default behavior regarding the posting of data conversion warning messages

to the .iqmsg file. The new behavior is that each thread doing data conversion for a LOAD statement will post at most one data conversion warning message to the iqmsg file if

the database option "conversion_error" is set to "OFF".

In order to have all of the data conversion warning messages sent to the iqmsg file

an option must be set. This option is "DDL_OPTIONS2=8". Here is an example of how to

have all of the data conversion warning messages written to the iqmsg file:

set temporary option conversion_error='off';

set temporary option ddl_options2=8;

380959 Under certain circumstances, a read only query node may fail to drop all old and no longer referenced cached catalog objects.
381558 ASE columns of type char or varchar or binary or varbinary with lengths greater than 255 are now correctly inserted into IQ tables with INSERT LOCATION. The data is no longer truncated at 255 provided that the IQ columns are defined large enough to hold the data.
381569 When altering a table, Sybase Central did not restore the Pkey check box correctly after a failure to cut a column.
381604 Changes have been implemented to support cross-platform migration for little endian platforms.
381651 SCJ12.6 abortes if the Server Name is omitted at CONNECT when SCJ started as Japanese Client, e.g. LANG=ja.
381800 A problem running Sybase Central on Linux has been resolved. The scjview script now forces the use of the bash shell instead of the korn shell, which is not installed by default on RedHat 2.1.
382199 Multiplex DML replay of SYNCHRONIZE JOIN INDEX with

an insert to the bottom table of a join caused query server failure.

382357 Assigning data from a binary field to a binary variable resulted in data being displayed incorrectly.
382541 The server could fail if a query was interrupted by the

user at an unlikely but problematic point during the

first few seconds of execution.

382554 A race condition between the checkpoint and sp_iqdbspace could cause an unresponsive server.
382663 Customers using Sybase Central java 4.3.0.2359 with IQ plug-in 12.6.0.041203 were unable to specify cardinality using the IQ UNIQUE column constraint when creating tables.
382669 When creating a new table in Sybase Central, if you made a mistake (like a duplicate column name or a forgotten column data type) and clicked the save table icon (or right-clicked table and save table) Sybase IQ returned the expected SQL syntax error message, but lost the entire table definition.
382730 Feature request for same properties in 12.6 on Table -> Properties -> Miscellaneous plugin as with the 12.5 Table -> Properties -> Statistics panel.
383625 Certain INSERT ... SELECT DISTINCT statements where there

is also a GROUP BY clause could result in either

an internal error from dfo.cxx:6235 or a Max_Cartesian_Result

error from dfo_Root.cxx:785.

383634 A guery containing join and group by clauses under the sort-merge pushdown join algorithm failed at dfo.cxx 5899 with the error: "Input to *** not ordered as required".
383732 On Windows, Sybase IQ 12.6 could not use caches greater than 1.7GB on systems enabled for 4GT.
383741 A query server failed with a stack trace

during replay of TLV log on the query server. This happened

after upgrading the 12.5 multiplex environment to the 12.6 ESD1 release.

383932 On an IQ server, a query with only ASA tables that used an outer join might return a "rowid not implemented" error.
383979 The parser now generates an error message whenever a user

attempts to reference a view that needs to be recompiled

because of changes to the schema of a table used within

that view.

384081 For users with queries containing predicates on numerous

large tables, the thread allocation policies for predicate

execution have been improved. If you have lots of queries

that meet the criteria above, and especially if you have

such queries and are running on a system with multi-core

CPUs, then you should:

set PUBLIC.Enable_Thread_Allowance = 'ON'

384143 In rare circumstances, a multiplex query server executing an operation on its local store could fail with the exception "Abort at s_bufhash.cxx:333."
384154 Request to print the index usage for a query.
384245 For a UNION ALL view, if one (or more than one) arm of the union was a complete empty table, Sybase IQ returned the following stack trace:

Non-Fatal IQ Internal Error Detected at dfe_BaseColumn.cxx:886 on thread 34 (dfe_BaseColumn::GetMaxValue(void))

The view met the following criteria:

1) A UNION ALL view over ungrouped base tables

2) Each of the view's select list items mapped to a set

of identically typed base columns

3) One (or more) of the arms of the UNION referred to an

empty base table

4) The query block referring to that view performed

a GROUP BY or a join on a column from that view, such

that the optimizer requested the distinct count

of that column from the view

5) That view column had an unscaled integer

data type

6) All of the base columns mapped to by that view column

had HG indexes defined

7) The sum of the distinct counts for all the base

columns mapped to by that view column exceeded

~1.5 million

384407 The @@proc_id global variable worked only on Windows systems. On UNIX, it returned '0' instead of the procid of the executing procedure.
384590 When connected to an IQ server, the ODBC driver's SQLGetInfo function would return "Adaptive Server Anywhere" instead of "Adaptive Server IQ" for the SQL_DBMS_NAME.
384743 Within an INSERT statement into a temporary table, a negated disjunction containing a subquery could return an internal error from opt_QueryTree.cxx:3616.
385230 Request to implement Integrated Logon functionality from CT-Lib ISQL to IQ/ASA over named pipes.
385404 When more than 700 GRANT statements were issued, Sybase IQ returned the error "Assertion failed: 101506 (9.0.1.1753) Allocation size too large when re-allocating memory."
385684 Corrected an issue whereby certain queries involving GROUP BY

or SELECT DISTINCT on expressions could be rejected with an

"Internal error" that stated "Can not evaluate expression".

385719 A timing-dependent multiplex issue could cause a query server failure with an Abort at st_server.cxx:1056 during normal use, or an Exception Thrown from db_catx.cxx:416

when trying to restart a query server without synchronizing

if the server had not cleanly shut down.

385759 Queries with IS NOT NULL and IS NULL predicates on large tables are sometimes

less efficient than they could be, causing queries to use more temp space and

execute more slowly than necessary.

The following cases were improved for queries where <col1> contains NULL values:

select ... where <col1> IS NOT NULL,

select ... where <predicate> AND <col1> IS NOT NULL,

select ... where <predicate> OR <col1> IS NOT NULL, and

select ... where <predicate> AND <col1> IS NULL

385837 Starting a named transaction incremented @@trancount by two.
385851 A delete operation on a table with significant number of rows and DTTM, DATE, HNG, LF, and TIME indexes would take a long time to complete before noticing that the user had interrupted the operation.
385915 The IQ server failed when a NULL value was inserted via an ODBC parameterized variable.
386566 Virtual memory used by a write server, as reported via sp_iqstatus,

continuously grew when executing a multiplex usage scenario

that had a query server performing only queries and the write

server performing a repeated pattern of insert/load commit

into one or more tables, always modifying the tables in the exact

same order.

386583 A problem with the improper handling of interrupted jConnect connections when the server is returning results that could result in unexpected server termination has been resolved.
386813 Attempting to restart a multiplex write server could encounter a fatal error if dbremote connected to the database before a user transaction completed.
386867 Simultaneous internal errors could cause stack trace information to be incomplete.
387043 A memory inconsistency was detected and an exception thrown from db_Identity.cxx when SET TEMPORARY OPTION identity_insert was attempted twice for same session. Before you can reset the IDENTITY_INSERT option, you must first unset it. For example:

SET TEMPORARY OPTION identity_insert = ''; (This problem was fixed but undocumented in ESD 4.)

387337 The server might fail after raising error 9216 (Feature, non-constant expression in IN list not supported).
387343 LOAD TABLE processing used the wrong data conversion behavior.
387972 New Future:Password encryption for jConnect connections
388110 When querying a database with Japanese collation, Sybase IQ returned the wrong value for a CLOB value greater than 254 bytes and less than 32768 bytes.
388129 Changing a database from one collation to another is missing in System Administration Guide.
388153 The stored procedure sp_iqprintconstraints might give incorrect results depending upon the setting of the ANSINULL option.
388219 Using the IQ/ASA ODBC Driver, the ODBC API call SQLGetTypeInfo could return the wrong size for decimal columns. This has been fixed.
388509 Currently, IQ does not support the PERCENTILE_CONT or PERCENTILE_DISC function with GROUP BY CUBE operations. Sybase IQ now returns an error instead of a server failure.
388731 The migration stored procedure sp_iqdropconstraints dynamically creates ALTER DROP statements that drop unenforced 12.5 constraints. To handle special cases of owners, tablenames and columnnames, the script delimits the identifiers with quotation marks in these statements. With the default setting for QUOTED_IDENTIFIER = 'OFF' for isql connections, the script failed when run from an isql session. It ran fine from dbisqlc and dbisql. The stored procedure has been corrected to run correctly with isql, dbisqlc and dbisql.
389049 When an undefined column was selected inside a derived table or a view, the IQ server might fail. The failure only occurred when the derived table or the view contained UNION operators.
389295 Request to start the server with the largest page size using the -gp 32768 switch when using the Utility Database via Sybase Central to create an IQ Database to accomodate page sizes of the Catalog store greater than 4KB.
389355 Sybase IQ now returns an error indicating that INSERT VALUES does not support subqueries instead of a server failure.
390125 Internal IQ datatypes should not be listed in the dropdown list provided when creating a new table in Sybase Central.
390440 A query using the intersect keyword (which is not supported by IQ at this time) could cause a non-fatal stack trace instead of generating an error message.
390895 You must only set IDENTITY_INSERT as a temporary option. If you do not, the server may fail with Exception Thrown from db_Identity.cxx:362, and dump all thread stacks at st_server.cxx:504.
390916 When a user renames a table that a stored procedure selects from and then creates a view with the old table name on the renamed table, Sybase IQ must be restarted to avoid server failure on procedure execution.
390969 Temp space is not released if we get an error from dbisql when executing a sp. The temporary block used up is more in 12.5x release as compared to 12.6x release.
391018 String functions such as locate(), charindex(), ascii(), repeat(), patIndex(),

and concatenate slowed down when processing a large number of rows.

391118 Numerous customers have reported Sybase IQ

server fails when starting the IQ monitor

with the '-summary' option. For example:

iq utilities main into DBA.dummy start monitor '-interval 10 -summary'

391185 If an expression contained a reference to a proxy table, the engine failed if that expression was used as an expression in a message or PRINT statement, an expression in a RETURN statement of a function or procedure, a time/delay expression in a WAITFOR statement, or an offset expression of a FETCH statement.
391376 Long varchar update performance involving short strings can be improved.
392322 On Linux and all UNIX platforms, attempts to start IQ after uninstalling Open Client and the language modules returned the error "Could not load the store DLL libiq.so." The error occurred when the default uninstall option was selected during an uninstall of Open Server and the SDK on a system where Sybase IQ was installed.
392616 Thread memory size (the product of the values of -iqmt and -iqtss) no longer has a limit of 2097151KB on 64-bit systems.
392931 Under rare circumstances, a query server became unresponsive during a rollback operation, then suddenly restarted.
393067 Processing of Table Level Versioning Replay could fail to complete if there were insufficient threads to run the replay of a connection that holds locks causing these locks to be retained.
393196 Sybase IQ misinterpreted a white space after a series of digits as

the end of input in loads, inserts, updates, and queries. For

example, it treated "666 7" as "666".

393311 INSERT into a view fails.
393409 Option to mark connection dead when the connection cannot be dropped
393747 Derived table in in-list will generate stack trace as ASA level
393797 If a procedure or function call a java method and the java code uses the current connection to run SQL statement that calls a procedure or function that also call a java method, the engine fails if the two procedures/functions have a return statement.
393819 Request for SA to add functionality to distinguish between BINARY and VARBINARY
393823 In Sybase IQ 12.5, if "select *" is used in a view and the base table(s) used in that view are changed, then you must drop and recreate the view.

There is a related IQ 12.6 CR 362288.

393984 sp_iqpassword does not validate the old password before changing to the new password.
394070 Have a procedure containing a variable in a select run in full pass thru mode
394506 A database experiencing a high rate of commits could starve checkpoints.
394696 Request feature that provides monitoring feature similar to ASE MDA tables.
394739 A "between" predicate is of the form "A between B and C"

In 12.6.0 and prior versions, A, B, and C all had to be

constants, host variables, or columns.

In 12.6.1 either "B" or "C" or both "B" and "C" can now

be subqueries. "A", the left hand argument, must still be

a constant, a column, or a host variable in 12.6.1.

394848 Reference Manual error: Table name should be "SYSIQINFO" instead of "SYSINFO".
395407 To improve performance of queries on a view with UNION ALL, Sybase IQ no longer pushes a predicate through UNION to the base table.
395428 Under certain circumstances, a'Cursor Not Open' error could occur

when inserting into a global or local temp table

396568 Queries containing the FOR XML [RAW|AUTO} clause would get an 'Invalid Expression near forxml' error.
396836 Following a partial width insert, a non-fatal internal error (s_ohcIter.cxx; 789)

could be reported performing an UPDATE operation on a HG index.

397343 ct-describe via CTLIB returns max byte storage when varchar/varbinary > 255
397657 Remove reference to the SYBASE_JRE environment variable from ASIQ-12_6.sh.
397929 In IQ 12.6, the stored procedure "sp_iqdbspace()" returns different column

names depending on how the procedure is called form isql. When called as

"call sp_iqdbspace()" it returns one set of column names, when called as

"select * from sp_iqdbspace()" it returns a different set of names.

398740 Under rare circumstances, a delete operatino on a multiplex cause

server failure reported at s_blockmap.cxx; 974.

398906 Provide some global variable that will provide number of current user connections and the max number user connections configured
399062 Modifying system time does not reflect in sql log (from -zo output).
399149 Results from the Inttohex() function for bigint and numeric types were formatted inconsistently.

The following are the results for bigint, integer and numeric values:

'00000001' '00000001' '00000001'

'ffffffffffffffff' 'ffffffff' 'ffffffffffffffff'

'00000002' '00000002' '00000002'

'fffffffffffffffe' 'fffffffe' 'fffffffffffffffe'

'7fffffff' '7fffffff' '7fffffff'

'ffffffff80000001' '80000001' 'ffffffff80000001'

'ffffffff80000000' '80000000' 'ffffffff80000000'

'80000000' '00008000' '80000000'

'7fffffffffffffff' '00007fff' '7fffffffffffffff'

'8000000000000001' 'ffff8000' '8000000000000001'

'8000000000000000' 'ffff7fff' '8000000000000000'

This problem has been fixed. The following shows typical results now returned for bigint, integer and numeric values:

'0000000000000001' '00000001' '0000000000000001'

'ffffffffffffffff' 'ffffffff' 'ffffffffffffffff'

'0000000000000002' '00000002' '0000000000000002'

'fffffffffffffffe' 'fffffffe' 'fffffffffffffffe'

As well, with 9.0.2, passing a negative value to inttohex() would have resulted result in a "value out of range" error. This to has been corrected

399275 Multiplex -- During multiplex propagation of stored procedures, views, or functions that contain special characters enclosed in single quotation marks, the query server may fail with SQLSTATE: 42WO4. For example, this may occur in the case of a stored procedure containing a load statement with '\n'.
399761 Under rare circumstances, during automatic database recovery, the server could become

unresponsive when deleting an entry from an invalid index instead of reporting

Assertion 200901.

399768 Options changed during ALTER DATABASE UPGRADE process are documented in the Release Bulletin. Use sp_iqcheckoptions to display settings before and after upgrade.
399881 Using Sybase Central Java edition for IQ 12.6, if you uncheck the 'allowed to connect' box in the properties of a user object, it appears to set the password to Null. The user can then still log on to IQ using dbisqlc if you enter a Null password for the user you have just tried to lock out. Dbisql java works fine and prevents access as expected. Also, once you have unchecked the 'allowed to connect' property box and applied it, if you close the properties window then reopen it, the box reappears as checked again.
399882 Under certain circumstances when running sp_iqdbspace a logic error could report Non-Fatal s_bm.cxx error "Bitmap result bitcount not in legal range" and may cause the server to be unresponsive.
400095 The installer has been updated so that shared java components are not removed on uninstall if there is any possiblity that they are being used by another product. ESD #5 must be installed for this change to be included in the uninstall.
400302 Under rare circumstances, a query using nested subqueries might result in server failure.
400486 Running the sp_iqmpxdumptlvlog procedure could cause write or query server failure if the write server is concurrently writing new rows to the Transaction Level Versioning (TLV) log.
400807 Query server might do an emergency shutdown during synchronize when the write server contained Java related domains.
400914 Cannot automatically start IQ Agent on Windows 2003.
401034 A write server occasionally failed to start even when it was previously stopped normally.
401051 Allow new connections while versions are being dropped
401168 When connecting DBISQL java using iAnywhere JDBC driver to Sybase IQ, neither the GUI nor a SET OPTION statement allow you to save options in "Tools" -> "Options" permanently.
401194 A fatal server error occurred when dynamic memory was exceeded.
401247 Creating an IQ local store on a multiplex query server in some situations

may cause the query server to stop with an emergency shutdown message.

401344 provide a new dbisql option to specify a delimiter for column headings and data
401519 Creating an IQ local store on a multiplex query server in some situations

may cause the query server to stop with an emergency shutdown message.

401883 Stored procedure performance during database versions release was improved.
401892 If the system clock was advanced and then moved backward to the current time, major timestamp increases could occur. Moving the time ahead a minute or two (or a day or two), could cause change of perhaps 5 days, or no advance, but when time was moved backwards to the current time, advances in the "-zr" logfile of 23-25 days could result.
401966 When the password in a profile was blank and the profile was set to connect on startup, Sybase IQ returned the error ASA -103: Invalid user ID or password.
402043 If a user was granted permissions on a view but not on one of the underlying IQ or remote tables, then using the view in a subquery failed with a permission denied error.
402152 The IQ server returns a stack trace with a signal 11 if user_id or user_name is used in a query like the following: SELECT user_id() FROM DBA.IQ_DUMMY.
402196 Customer is requesting the same functionality as exists with the LOAD TABLE command where it allows you to control load behavior when integrity constraints are violated and to selectively log information about the violations.
402205 Include table owner to the index advisor advice when outputting <table.column>.
402551 Duplicate create index statements occurred in jcatalog.sql.
402580 Using 12.6 ESD4.3 only, write server recovery could incorrectly restore the state of the transaction manager after a server failure. This could lead to allocation problems.
402901 Checkpoint might deadlock if the IQ temporary cache was very busy.
403182 Sybase IQ 12.6 server startup may take longer if there are a large number

of tables in the database that is being opened on startup.

403319 DBISQL could report an OutOfMemory error during or shortly after executing a statement which returned a large result set. This was most likely to occur if:

1. The "Show multiple result sets" option was turned on, and

2. The "Maximum number of rows to display" option was set to "All rows", and

3. The result set contained a lot of data.

403457 DBA is able to drop views owned by SYS.E.g.:DROP VIEW "SYS"."SYSFOREIGNKEYS";
403496 Needed to build libdbtsp9.sl.1 in order to use dblog.
403601 A query failed to execute when there were three scalar values (complex dfe expression nested with case ansi aggregation functions) and subqueries in the top select list.
403795 A LOAD operation in which constraint violations are being ignored

can occasionally fail with the engine reporting an IQ Internal

Error - s_ohcidx.cxx; 1379.

403817 If a restore operation restored an obsolete path to the file_name column in the SYSFILE table for the SYSTEM dbspace, the file_name column could be incorrect even after the restore provided a new absolute path for the catalog database.
403907 A 12.6 server could not start a 12.5 multiplex database using only the -iqmpx_ov switch.

Workaround: using -iqmpx_sn switch.

403953 After being restarted with many old versions, a write server may report errors in the IQ message file from the ev_iqmpx_status event.
403954 Server failure SEGV at st_server.cxx:1164 might occur running sp_iqrebuildindex while making schema changes in the database.
403965 A query containing an outer join using the hash pushdown algorithm

and using an IN predicate for the pushdown caused a server failure.

404010 The engine may fail under a certain race condition on the write server

when the write server is being changed to single-node mode while

another write server connection is running active transactions and generates tlv entries.

404031 The installation program should end by reminding customers to run an ALTER DATABASE UPGRADE after applying an ESD.
404284 Setting system clock back could cause SQL log time to jump ahead ~25 days.
404394 IQ 12.6 isql exit causes 'Connection terminated abnormally' message in svr log
404599 Errors in a user-defined sp_mpxcfg_<server> stored procedure could set query server PUBLICATION information incorrectly, and cause versions to accumlate on the write server.
404602 Add info from cr 401971 to IQ documentation
404735 dbo.SYSOBJECTS.crdate should display the creation time of IQ objects.
404776 The sp_iqrebuildindex procedure incorrectly creates a 1-byte FP

for a tinyint column if either 'Minimize_Storage' = 'ON' or a

column unique count is specified in the rebuild index.

404788 A user could not create a query server using relative paths for the main and temporary dbspaces.
405203 The following steps generated non-fatal error df_Heap.cxx:1909 on simple query:

create variable @chkey decimal(2);

select @chkey = 1;

select @chkey FROM iq_dummy;

405209 Running the sa_disk_free_space procedure from dbisql caused an IQ server to fail.
405314 Document that if you create a table on the multiplex write server with the same name as a query server persistent table (created on a local store in the query server) then the query server table will be renamed to terminate with the ~ character.
405658 Failure to start HP Itanium ESD 4.1 with caches > 4GB.
405750 Under certain circumstances, after upgrading to 12.6 ESD4.1 or higher,

a delete operation could cause the engine to fail with a SEGV or Signal 8 error

depending on the structure of the FP indexes.

405773 Not declaring a size for a varbinary datatype during the declare statement of the variable and then when doing a select on the variable will cause the server to stacktrace in st_server.cxx.
405831 Running sp_iqtablesize on a global temporary table may return an s_blockmap error.
405841 Running sp_iqstatus concurrently from different connections used to cause errors

due to locking of SYSIQFILE system table.

405870 "Fatal error: memory exhausted" with large IN list
406109 In ALTER DATABASE operations with qualifier..object syntax, Sybase IQ considered the first qualifier to be database rather than owner, causing synchronization problems.
406123 Integrated Logins do not work when connecting to the server via a connection profile.
406135 Request for sqlpp utility to be included along with IQ network client.
406156 Sybase Central takes longer to display Java Classes or column names in a table in Sybase IQ 12.6 than it did in 12.5.
406321 The workaround provided for CR #403965 failed in some cases to avoid the problem.
406430 A query with multiple exclusive ranges returned an error at opt_TableNode.cxx 2099. For example: SELECT COUNT(*) FROM sales_order WHERE (cust_id > 20 AND cust_id < 10 AND id IS NULL) OR id >= 10 AND id <=5;
406712 Request to modify LOAD behavior logic when reading from a named pipe to detect when a determinate amount of time has passed where the process is no longer reading data from the named pipe.
406856 After the IQ connection was dropped, IQ continued calculating found set for a long period of time, and thus caused table version accumulation.
406921 12.6 ESD5 MPX qnode abort at st_txnMgrn.cxx:362, non-fatal at s_buf.cxx:1022
407556 A server stacktrace occurred in add_string when the table or view name had a space or '_'.
407558 The password_created timestamp now gets propagated to query servers.
407778 Adding an alias for a dbspace via the sp_iqmpxaliasdbspace stored procedure, can result in an invalid file_name value in sysiqfile if the path is to a raw device on Windows.
407844 A small subset of queries containing IN pushdown

join conditions or uncorrelated IN subquery

conditions slowed down between ESD3 and ESD4.

408379 A Sybase IQ 12.6 server failed with no error message/stack when query exceeded thread stack space.
408462 A query containing an atypical SELECT AS GROUP UNION ALL, CASE, SUM, IF THEN, and left outer join constructs caused IQ server failure at st_server.cxx:513.
408504 The IQ server might fail while running the Java VM Garbage Collection. This

might occur before a very long array or string was allocated or while pieces of that array/string were being allocated. In this situation, if the Garbage Collection ran multiple times, the IQ server could fail. This typically occurred if a user ran a java

program inside the IQ server or used CIS to connect to remote

servers using jdbc connections and the program was memory intensive.

409024 Database recovery could have failed with assertion 201501 "Page for requested record not a table page or record not present on page". The problem would only have occurred in the event of the database server not shutting down cleanly while dbremote replication was taking place. It would also have been required that another connection revoked CONNECT or REMOTE from the remote user for which the transactions were being replicated. This problem has been fixed. The connection attempting to revoke permissions from the user for which replication is currently occurring will now receive an error indicating "Not allowed while user 'user_name' is actively replicating transactions". The connection attempting to REVOKE permissions will need to wait until replication completes (commit/rollback) before being able to revoke the permissions.
409117 Under rare circumstances related to errors during subqueries, the database close

portion of a server shutdown could report the error "Assertion failed: 101416

Heap left locked at database close" in the server log.

409156 Interrupting a query containing a very large number of unions may result in a server failure.
409164 SQL TEXT field of HTML queryplan to show SQL Statement of queryplan and not the SQL Statement of the query as send by the client.
409385 Accessing table properties using iAnywhere JDBC driver takes over 1 hour for the customer.
409486 Allow column/table comments to propagate without having to manually synchronize
409512 An unusual query that contained a LIKE string with width

greater than the column being queried could cause server failure.

A LIKE query on a column defined as char(5)

with a string of six or more characters is an example of such a query.

409758 The sp_iqconnection procedure does not show Name when client is java application with jConnect.
409769 A server failure resulted when CIS attempted to process a query containing ntile.
409967 When logged in as 'DBA' to either dbisqlc or dbisql (java), when trying to create a permanent base table using the "SELECT INTO" command and specifying owner.tablename, the error "Table <table> not found".
409984 Lock IQ devices to prevent accidental usage by non IQ processes
410127 A query could fail if invariant external host variables were initialized to a maximum length greater than the database page size, so that the key didn't fit on a single page.
410215 A query server failed with an emergency shutdown

while replaying a BEGIN PARALLEL IQ clause that

had previously successfully executed on the write server.

410269 A CTRL-C generated a stack trace from s_bm.cxx during an INSERT INTO #temp operation.
414505 ALTER DBSPACE ADD uses space only from reserved space.
414613 During multiuser dbspace operations, a multiplex query server

could report DBCC Unknown Exceptions.

414639 Server hangs when out of IQ MAIN DBSPACE condition exists
414940 Request feature that forces immediate change of initial/default password.
415153 A query using a PROBABLY_IN pushed join condition on a

join key column with more than 700 million distinct values

could, under unusual circumstances, cause a server failure.

415159 A Sybase IQ server might fail running a query containing an outer reference from a derived table to an alias, if the derived table is a union intersect.
415481 Japanese customer can't use MS Visual Studio .NET with IQ12.6 due to the CR405965.
415510 The Sybase IQ engine failed performing an updatable

cursor operation when no data had been previously

fetched.

415666 Cannot insert into an IQ table with identity column from ASE proxy.
415880 Inconsistent table or index occurred as a result

of a updatable cursor operation.

416089 On 64-bit platforms there was a problem in the implementation of the ODBC API call SQLColAttributes(). A pointer to a 32-bit int was being returned instead of a pointer to a 64-bit int as specified by the ODBC standard. This has been corrected in the ASA/IQ ODBC driver and in other product components that use this interface call.
416382 More examples how to write the load statement,especially if date's are involved.
416669 Queries containing functional expressions over outer references could return

unexpected results.

416859 Option to get original create date/time of a login
416981 Request for option that forces password re-authentication, such as on UNIX.
416986 References to sp_iqcommandstats will be removed in the next revision of the Sybase IQ Reference Manual. New Features in Sybase IQ 12.6 correctly states that this procedure is no longer supported.
417147 Under rare circumstances, on Windows systems only, query server startup could fail with the error "share violation: another process may be using the file."
417507 The result datatype of a REPLACE function is a long varchar when used in a SELECT ... INTO statement.
417521 DESCRIBE not properly reporting NOT NULL attribute for many data types.
417615 When MINIMIZE_STORAGE was set ON, a query containing expressions inside the CASE statement involving only one column returned a conversion error.
418213 When trying to rebuild 19 or more indexes within a single transaction, a multiplex write server might fail.
418252 If a user ran drop leaks on a query server with a local store started with forced recovery and -iqnolocalreplay, subsequent attempts to access objects in the local store might fail.
418344 Update documentation to make it clear that Open Client can be used to create programs that access IQ base table data.
418745 CR 353999 "IQ Agent needs adjustable timeout setting" was a new feature

implemented in 12.6 GA, but it was omitted from documentation. It is now documented in the Sybase IQ Release Bulletin.

418759 Sybase Central 12.6 ESD 5 could not connect to a 12.5 multiplex write server, and returned the error, "Sybase Central cannot connect to a database on a server that is older than version 7.0.0".
418991 New ASA .NET data provider added by ESD#5 is not registered into Assembly Cache of NET Framework 1.1.
419064 SELECT stmt with NTILE() returns Feature 'olap extension' not implemented.
419325 Using 12.6 ESD 5, after starting and stopping an IQ single node database created with a pre-IQ 12.6 version, the next attempt to start the database might fail with a "Bad Block number" error reported in the iqmsg file. This issue only affected IQ single node database created prior to version 12.6 which have the first IQ main dbspace on a RAW partition. Multiplex databases were not affected.
419487 The parser incorrectly returns an error when

trying to determine if CASE expressions in the ORDER BY

clause and the SELECT list match when there is an

IN condition.

419556 Under certain circumstances, a non-fatal internal error

was reported during a large delete.

419567 Problem promoting query server to write server when 2+ query servers exist
419581 The request is for INSERT LOCATION to support Quoted Identifier Object names when inserting from an IQ server.
419678 Provide an option to capture partial loads and allow for rollback.
419867 ASA:INSERT... WITH AUTO NAME should return error message "function not implemented" instead of a non-fatal stack trace.
419908 Add SQL command line length to SQL Reference Manual Chapter 8, "Physical Limitations."
419910 Request to support ASE sp_showplan procedure in Sybase IQ.
419912 Update documentation to recommend editing configuration file when migrating large servers.
419913 Add option for query server to automatically use the parameters in the cfg file of a write server instead of the default parameters.
419939 Reduce startup costs for queries when opening tables.
419994 startup switch -sb lead to error:DBSPAWN ERROR: -81

Invalid database server command line

419997 Correct sqlstate and sqlerrorcode are not returned in case of a warning.
420002 Auditing caused dbtran to report bad transaction log data for IQ databases.
420033 Load fails giving unique constraint violation after IQ server fails when using IDENTITY.
420097 Request a date/time stamp to determine when indexes are created.
420131 Provide utility to convert IQ database from one char set to another something similar to ASE's sqlloc
420264 Request to enhance IQ front-end query tools to support LDAP authentication.
420306 Error Message Severity Levels in iqmsg
420388 Request to specify destination file for auditing output other than the trans log
420509 insufficient SA cache at the point in time the propagated statement is being replayed on a given query node could cause query server to shutdown.
421179 In rare situations, a server could stop processing requests for a database when one user attempted to add/drop/alter a procedure while other users were calling procedures.
421643 IQ EXTRACT does not appear to work when triggered from an event.
421915 The sp_iqrebuildindex procedure failed in hos_mutex_inline.h.
422126 A query that contained conflicting range predicates in one of its subqueries caused a server failure.
422235 A Sybase IQ server might fail with s_blockmap.cxx; 1295 error when

replaying a ALTER TABLE RENAME command propagated

from the write server to a query server.

422335 Under rare circumstances, an IQ server became unresponsive with a JavaVM thread deadlock.
422502 The following unusual scenario could result in server failure:

1) Connection 1 ran a stored procedure.

2) Connection 2 dropped a table used by the stored procedure in

Connection 1 and recreated it as a view.

3) Connection 1 tried to run the stored procedure again.

422624 IQ 12.6 on UNIX, when started from the "start_asiq" script, would load the ODBC driver specified in the "Driver=" config prop in the ".odbc.ini" but fail to load its supportive shared object unless one of the followings is true:

+ the path to the 3rd-party ODBC driver library is included in $LD_LIBRARY_PATH_64;

+ the IQ startup script is modified so that the path to the 3rd-party ODBC driver library is included in $LD_LIBRARY_PATH_64.

423398 Under certain circumstances, a query with a deeply nested expression caused server failure and a stack trace error. Out of stack situations can be alleviated by increasing the -iqtss value.
423745 In some cases, server failure could result from attempting to get the GRAPHICAL_PLAN for a temporary table, whether using the function or DBISQL.
424253 Request for true single-user mode to restrict multiple connections to server
424572 ALTER DATABASE UPGRADE may hang if an implicit or explicit checkpoint

is started while it is executing.

424750 After running ALTER DATABASE UPGRADE to upgrade any Sybase IQ database to version 12.6 ESD#6, connections from an OLEDB application failed with "Procedure sa_oledb_getowner not found". The problem occurred when IQ server and client software were upgraded to 12.6 ESD 6 and OLEDB client applications were built with 12.6 ESD 6 OLEDB DLLs.
425119 Loads, updates, and inserts should roll back immediately after an error is encountered and not wait for other parallel threads to complete processing.
425124 Under certain circumstances, UPDATE commands

performed on char, varchar, or varbinary

columns with a defined width greater than 255

bytes or clob/blob columns whoses data widths are less

than 32768 bytes may cause FP index inconsistencies.

The inconsistencies may cause non-fatal s_blockmap

errors.

The issue is extremely data pattern dependent and is

much more likely to occur when updating more than 10,000

rows in a single update command.

The issue does NOT occur if any of the following are true:

- All rows in the column are updated in a single

update command.

- All rows being updated were originally all

NULL or zero-length strings

- All rows being updated are set to NULL or

zero-length strings.

- It is a single table update (no joins involved)

whose WHERE clause specifies single-column

predicates against constraints.

Once you have applied 12.6 ESD6.2, run the following

command to check the FP indexes:

sp_iqcheckdb 'check database indextype FP'

If no errors are reported, then your database was

unaffected by the issue and no further action is

required.

If inconsistent FP indexes are reported, run the

following command for each inconsistent index:

sp_iqcheckdb 'check index index_name'

A list of affected rowids will be printed in the

.iqmsg file preceded by the following line:

DBCC owner.table.indexname: # inconsistent ROWIDS

(where # is the number of rowids)

To resolve the inconsistencies, the following steps

must be repeated for each inconsistent FP index

reported. The sp_iqindex procedure can be used to

determine the column name that corresponds to the

FP indexname.

1) Add a new column to the table with the same

definition as the original column with the

inconsistent FP index. For example:

ALTER TABLE table_name ADD new_colname type

(width) NULL

2) Update the new column with the data from the

original column excluding all rows reported

reported in the .iqmsg file under 'inconsistent ROWIDS'.

For example:

UPDATE table_name SET new_colname =

original_colname WHERE ROWID(table_name)

NOT IN (list of inconsistent rowids)

3) Match each rowid reported in the 'inconsistent ROWIDS'

list to the table's primary key or, if no primary

key exists, use data values from other columns

that in combination uniquely identify the row

Use this information to determine the correct

column value from the original data source used

to populate the column. Update the new column

based on this information. For example:

UPDATE table_name SET new_colname = 'value' WHERE

ROWID(table_name) = rowid value

4) After step 3 is complete for each inconsistent

rowid reported, drop the original column and

rename the new column to the original name.

For example:

ALTER TABLE table_name DROP original_colname;

ALTER TABLE table_name RENAME new_colname

TO original_colname

If the original column was defined as NOT NULL,

alter the column to add the NOT NULL

specification. For example:

ALTER TABLE table_name MODIFY

original_colname NOT NULL

5) If the original column had WD or CMP indexes,

recreate them.

6) After steps 1 through 5 are completed for

each inconsistent FP index reported,

run sp_iqcheckdb 'check database indextype FP' a final

time to confirm that no errors are reported.

425271 Using jCONNECT:ResultSetMetaData.getColumnTypeName would return a different result

on SA versus IQ tables. Both should return the base data type. (Duplicate of CR 442804.)

425580 Request that for subqueries contained in view, alias_name cannot be defined as aggregate functions column.
425619 Sometimes 32-bit installs/updates will not start on the Windows 64-bit platform if TMP or TEMP is set to C:\Windows\TEMP*. Resetting TEMP or TMP to "C:\temp" seems to resolve it. (C:\temp has to exist).
425650 Under some circumstances, during an update

or incremental insert to a char, varchar, or

varbinary column wider than

255 bytes, the server may fail with a

"Destroying Locked Logical Buffer" error.

425704 In very rare circumstances, the server might fail if multiple calls ran the same stored

procedure and the procedure contained statements of the form "SELECT ... INTO #temp ...".

425921 Under special circumstances, running certain queries caused query server failure without a stack trace. Such queries now fail with the user error "Query stack size exceeded" without affecting other users.
426096 The dblog utility returned an error because the libdbtsp9.sl.1 library was missing.
426145 The sa_oledb_getowner function may return the error: -706 "Remote server does not have the ability to support this statement" on various sa_oledb_xxx procedures.
426315 Missing links for libiqtspt12.sl.1 & libiqtspt12_r.sl.1 caused an error running dblog.
426797 It was possible, although very unlikely, for the server to fail, or for connections to deadlock and appear unresponsive, in the presence of concurrent DDL statements. For one of these failures to have occurred, these concurrent statements would generally have to refer to the same database object (i.e.,table, column or stored procedure, etc.), either directly or indirectly. A workaround is to serialize all DDL requests that references the same object.
426979 The server might fail with the error "Cursor not updatable: OLAP function in select list" when the user ran a query that uses the dense_rank function and had a redundant alias in the OVER clause.
427826 On Windows systems where Sybase IQ 12.6 ESD 6 or ESD 6.2 was previously installed, an empty util_db.ini file might exist in ASIQ-12_6\win32, preventing users from connecting to the server using the utility database. The workaround was to edit the util_db.ini file and add username and pwd, for example: [UTILITY_DB]

UID=DBA

PWD=SQL.

427864 writer crashed during manual sync of reader node
427996 Backup command needs to handle double forward slashes '//', the way ASE Does

This backup database command fails: backup database to 'c://temp//test.bk';

But works in ASE.

429044 Using sp_iqcheckdb allocation mode could cause a server failure if duplicate block allocation errors were detected.
429413 The NOEXEC database option may cause server failure when trying to get a query plan.
429996 IQ needs to be able on a Alter Table, modify the Data Type Like ASE does.
430107 Interactive SQL (dbisqlc) with the -q option fails when xp_cmdshell is called.
430123 enhance manual management of dbpsaces in multiplex
430192 A query that joined a view and table with an invalid rowid correlation

returned a SEGV error.

430441 Even with the SQL Anywhere option TEMP_SPACE_LIMIT_CHECK = 'ON',

a Fatal Error could sometimes be returned when SA tmp (tmp_00000000)

filled the disk, depending on the cause of the temp space increase.

430583 Document max value for LIMIT in load table
430854 If a user had permissions on a view but no permissions on the underlying proxy table, then using the view inside an IF or CASE expression gave a "permission denied" error.
431204 If the IQ database had a large schema with huge number of tables, columns and indexes, query server synchronization might be unresponsive and never complete. As a result, a user might not be able to create new query servers or synchronize existing ones.
432176 When the database option ISOLATION_LEVEL is set to the non-default

value of 3, multiplex synchronize might cause a server Signal 11

failure.

432417 SET OPTION PUBLIC.NON_KEYWORDS='exception' could prevent the IQ server from starting.
432757 In very rare circumstances, the engine might fail if multiple calls ran the

same stored procedure for the first time after the database start and the procedure

was used in a select statement.

432794 Each thread doing data conversion for an INSERT or UPDATE statement now posts at most one data conversion warning message to the .iqmsg file if

the database option "CONVERSION_ERROR" is set to "OFF".

In order to have all of the data conversion warning messages sent to the .iqmsg file

an option must be set. This option is "DDL_OPTIONS2=8". To write all of the data conversion warning messages to the .iqmsg file, use these statements: SET TEMPORARY OPTION CONVERSION_ERROR='OFF'; SET TEMPORARY OPTION DDL_OPTIONS2=8;

432806 Catalog cache increased and was not released when SELECT resulted in a conversion error.
433149 The Sybase Central plug-in returned "table name not found" errors when listing tables and indexes in a database using the 1254TRK collation.
433328 When deleting a database using Sybase Central, an incorrect error message was being shown when the encryption key was incorrect. A correct error message is now being shown. Also the dialog box used to enter encryption key has an error. This has been corrected.
433677 An outer join between a table and derived table gave incorrect results when the query contained a count, for example: SELECT col_3, COUNT(*)

FROM js1 LEFT OUTER JOIN( SELECT DISTINCT(col_1) AS col_1, 'R' AS col_3 FROM js2 ) AS t_js3 ON js1.col_1 = t_js3.col_1

GROUP BY t_js3.col_3.

433678 On HP-UX 11.23 (RISC)systems, starting a Sybase IQ server with more than 4GB of memory failed with an error at hos_mem.cxx:348.
434598 A password change failed when IQ Login Management was enabled in Sybase Central.
434600 The index owner was unable to view indexes in Sybase Central.
434639 The isqlShowMultipleResultSets option is now true by default.
434643 Command-line or batch dbisql truncated results when a column had an alias name shorter than its column size. The problem did not occur when running dbisql through a GUI.
434849 Tainling blank is not ignored when CHAR or VARCHAR is specified to be LIKE conditions.
434897 Under rare circumstances, a non-fatal stack trace occurred at dfo_cOrderBy.cxx:758 when using aggregate functions.
435388 ALTER DATABASE UPGRADE failed with a "Database upgrade not possible" error when a DBA user created a table with the same name as an existing table owned by DBO.
435618 Installing Sybase IQ 12.6 GA on Linux failed when sybinstall was unable to extract files with the .tgz suffix on RedHat 4.
435644 Under some circumstances stddev function could return NULL results when the values in a group are the same.
435660 A query executed through a TDS cursor could be rejected as not updatable

even if the cursor was not declared for update.

435983 Sybase IQ inserted a row in IQ_USER_LOGIN_INFO_TABLE for a new user incorrectly.
435985 Under certain circumstances, Sybase IQ ignored the Temp_Extract_Null_As_Empty setting.
436161 A server could become unresponsive while data was being relocated from readonly dbspaces (in other words, when running sp_iqrelocate).
436264 Creating a dbspace where the start_block exceeded the maximum integer size (2147483647) caused an ASA Error -131: Syntax error.
436476 A user was unable to drop a connection if the number of rows returned exceeded 2^31-1.
436843 The statement "select '' /* empty string*/ into #temp" returned a syntax error.
436945 Column names in the first arm of a union are used to form the column names

for the derived table. If the column names of the derived table

happened to be the variable names in the subsequent arms, the query could not complete and the server failed.

437854 A query node's 'cardinality' value in system table SYS.SYSIQCOLUMN

might be incorrect if an index that maintains cardinality (e.g., LF or HG)

was created on the writer after the query node has been

created or synchronized.

437944 Under rare circumstances, a DELETE statement containing a

WHERE clause with the ROWID function could cause server failure.

438088 Currently if a SC user clicks on a table, and selects the "Data" tab, a 'select * from ...' is issued, which can be a very long running query depending on the size of the table. In this case, a 'select * from' was kicked off on a table with 43 million rows, unnecessarily tying up system resources during an important production job. Perhaps Sybase Central should display the rowcount instead, and allow the user to select a number of rows to see a sampling of the data, say 15 rows by default, and which could be configurable.
438350 When LC_ALL was set to a non-English language in the Sybase IQ installation scripts, the sybinstall and start_asiq utilities could fail.
438398 Request for the TDS layer in ASA/IQ to send SPID in the DONECOUNT token as part of the LOGINACK.
438505 A date conversion error occurred during ALTER DATABASE UPGRADE from 12.5 to 12.6 ESD 6

when the date_order option is set to 'DMY' in the 12.5 database.

438508 IQ blocks were released slowly after dropping or truncating tables. This affected query performance in large installations due to fewer resources available to the query optimizer, resulting in increased use of temporary space, or, in some cases, leaked blocks.
438535 Predicates expressions containing a COALESCE with a column argument and a constant inhibited query performance. This issue has been resolved to make better use of available indexes.
438609 If an insert-select query involves both remote and local tables and the table being inserted into is a view, then the query will fail with a "column not found" error.
439233 IQ server returns the specific wrong CP932 code to OpenClient application.
439278 A long query involving join indexes and a view failed with an exception at opt_TableNode.cxx:926.
439353 Ability to specify column number in GROUP BY clause just like in ORDER BY
439355 Sybase Central: IQ Plug-in is missing the web service folder.
439357 Ability to supply sql var name in FROM, ORDER BY & GROUP BY clauses
439552 A server could fail with a hos_mutex error after an out-of buffer error occurred.
440259 When 'select into' or 'insert select' is used in EXECUTE IMMEDIATE statement, local variable can be used in SQL statement. But this is wrong behavior. It is the correct behavior that local variable cannot be referred to from SQL statement.
440317 Bufman (s_buf) error reporting needs improvement.
440326 A query involving an IS NULL or IS NOT NULL predicate evaluation

with ROWID could fail with an error from vpp_IsNull.

440666 In queries containing a join where one of the join keys was a

value expression, and where that expression contained a column

which was used as a join key at a lower level join, then that

query could under some circumstances be incorrectly rejected

with a non-fatal internal error stating that the input to a join

operator was "not ordered as required".

440771 Under rare circumstances, complex disjunctive search conditions in a query's WHERE clause could be incorrectly transformed by rewrite optimizations, yielding a search condition not equivalent to the original, and hence yielding unexpected results. It is difficult to completely characterize the types of search conditions affected by this problem. However, for the problem to occur, the search condition must contain so many disjunctive (OR) conditions that the condition exceeds a generous threshold of the maximal number of potential predicates to generate.
440873 Delete on table reported error "Cursor is not updatable" for non-owner of the table even though that user had full access on the table, if the FORCE_UPDATABLE_CURSORS option was ON. By default this option is OFF.
441334 When one arm of a query's OR predicate was an IN predicate that referred to a column derived from a UNION ALL view, the IQ server might fail. The failure only occurred when the derived column's underlying base column had a one/two-byte FP or a LF/HG index.
441457 If multiple connections are open with uncommitted changes during a backup command,

upon restore from backup the uncommitted changes may not be rolled back for all connections.

This could produce catalog inconsistencies and subsequent server failures if a command

which creates or alters a table index was running during the backup.

441846 The Index Advisor printed an unnecessary message in the iqmsg file

with advice to rebuild a column with MINIMIZE_STORAGE='ON' even

when MINIMIZE_STORAGE was ON and a 1 or 2 byte lookup FP index existed.

441933 A server could fail with a signal 11 error if RANK() was used inside a view or derived table and the view column containing the RANK() result was used in a predicate.
441948 If login management was enabled, a DML statement made by a

non-DBA connection could roll back despite the CHAINED option being set 'OFF'.

442348 The ASE date and time data types will be supported for INSERT LOCATION. Support was also added for the ASE data type unsigned smallint. An ASE unsigned smallint value can be inserted to a compatible IQ type.
442730 A query including an outer join and an invalid date expression could cause a server failure.
442734 Request of IQ Client CD on any platform (32/64 bit)
442766 A query involving a view with mixed union and union all joined with a table could cause a server failure.
442841 Selecting an invalid view with multiple UNION expressions and a column name that doesn't exist in the base table could result in a server failure.
442889 Under certain conditions due to data skew, a HG Delete could choose a non-optimal algorithm.
442913 Queries involving subqueries that contain joins plus a condition equating one of the subquery join condition columns to a constant could result, in some circumstances, in an IQ internal error.
443135 DBD::ASAny is not included in IQ for UNIX.

Please access the following URL, when you use DBD::ASAny with IQ.

http://www.sybase.com/detail?id=1009063

443138 perl interface(DBD::ASAny) is explained to New Features in Sybase IQ 12.6.

But DBD::ASAny must install ASA. This driver cannot be used only by IQ.

443179 If the schema changed for one or more of the tables that participate

in a join index, then subsequent operations involving tables in the

join index could report an error from db_joinindex_id.cxx.

443300 Request feature that allows ability to log in and reset an expired password like in ASE.
443448 Customer has a query with a convoluted set of nested AND clauses which include DATE comparison and conversion arguments. If there is an incorrect date format entered into the query it crashes the server instead of throwing an error message. This is a regression of behaviour that has come into the 12.6. ESD and 12.7 codeline (prior to 12.6 esd7 the ASA Error -157 with SQLSTATE = ' 53018' error message is thrown OK).
443840 When using Sybase Central to connect to a IQ server running on Linux using an aliased IP address, the Multiplex folder did not open or could not be selected, preventing adding new query servers.
443846 After upgrading from IQ Release 12.6, or earlier, to IQ

Release 12.7 or later, sp_iqrelocate might report an -1006002

"IQ internal error" on any table that contains a column with

NULL values, if that table has not been modified since the

upgrade.

443851 Under certain circumstances, a DELETE statement involving

a view or derived table in the FROM clause that used the

same table alias as the delete table, may delete rows from

the view or derived table with the duplicate alias.

In order for the issue to occur, all of the following

conditions must be true: 1)The DELETE statement has a FROM clause with multiple entries and one of those entries is a view or derived table; 2) An identical alias is used for both the delete table and a table in the view or derived table; 3) The delete table precedes the view or derived table in the FROM clause; 4) The view or derived table does not contain a DISTINCT clause, GROUP BY clause or any aggregates in its select list; and 5) The DELETE statement determines there are rows to be deleted based on the statement criteria.

443862 If a query contains multiple aggregate functions (aggregate on different arguments)

that contains NULL values, an error from dfe_MinMaxAggregate.cxx could be reported.

443878 On Windows, the iqheader utility did not work on RAW partitions.
444016 NFR:MINUS support like UNION[ALL], INTERSECT.
444430 Under rare circumstances, a query containing a SELECT TOP could

return fewer rows than specified.

444471 Column is returned as nullable even if it was created as non-nullable.
444887 A server could fail with a signal 11 if the HG index was used to evaluate a

range and the PBV algorithm was selected.

445745 Inserting a string larger than the column size and having a SELECT in the INSERT caused a non-fatal stack trace in df_Heap.cxx.
446054 ODBC API SQLGetTypeInfo returns wrong SQL data type value with ODBC 3.x.
446660 If a temporary store dbspace UFS file is accidentally overwritten by another file, then the server will detect the damage and not start. In this event, the server will report "Unexpected throw from IQ command" and a message will be logged into the iqmsg file:

To repair this,start the server with the '-iqnotemp' switch and drop the affected temporary dbspace. Then shutdown and restart the server normally.

446704 Incorrect tar file names in the readme provided with download for IQ 12.7 32 bit odbc driver kit
446942 Invalid query with missing group by clause and an invalid expression could result in a server failure
446953 A UNION all view with multiple NULL values doesn't return expected rows.
446964 DROP VIEW from a query server resulted in a misleading error message.
446967 option TEMP_EXTRACT_NAME1 allow user to output the file to local to client
446968 Column headings in isql and dbisql were inconsistent when calling the same procedure.
447061 The start_asiq utility referred to "hard-coded" logfiles directory.
447069 Propagating ALTER TABLE RENAME to query servers caused running query servers to abort if the table_id of the table being renamed was greater than 65535. The workaround for this problem is to manually stop and synchronize all query servers after performing an ALTER TABLE RENAME on a table with table_id greater than 65535.
447374 Add documentation for dblic in IQ docs
447454 Tape diagnostic messages should only be reported to the

console.

447914 Select statement without a FROM clause in UNION ALL returned error intcode: -121 "Permission denied: you do not have permission to select from view01".
447918 A query involving a view that was a UNION ALL of two SELECTs in the FROM clause

and a date comparison in conjunction with an OR operator could cause server failure.

447992 Quick Reference manual of Sybase IQ does not exist.
448072 If a SQL code contains accented characters, the SQL running through ODBC may produce a stack trace in function dfo_cOrderBy.cxx 311
448140 IQ cannot debug procedure by multiple users. As for debugging work, only single user is allowed.
448232 ddl generated using IQ plugin for a dbspace does not contain file size
448244 Support encrypted password feature with ASEJDBC remote class
448641 The JRE patch level has been updated to resolve a situation where the implementation of RSA signature verification in SSL/TLS or other application scenarios may incorrectly verify forged signatures leading to security vulnerability.
448642 The JRE patch level has been updated to resolve a situation where the implementation of RSA signature verification in SSL/TLS or other application scenarios may incorrectly verify forged signatures leading to security vulnerability.
448736 Include complete patch list in addition to RPK
448737 The sybinstall utility failed to recognize existence of LD_LIBRARY_PATH and LD_LIBRARY_PATH_64 variables.
448901 sp_iqindexadvice may cause server failure if the option Index_Advisor_Max_Rows is

set to a value larger than 30 and the server accumulates at least 30 distinct advice messages.

449116 A query on a column with a two-byte FP index and 65536 distinct values might incorrectly return no rows.
449393 The following combination of conditions could result in a IQ server failure with stack trace:

- a stored procedure references a user-defined function in the search-condition of an IF statement

- the function calls a procedure with OUTPUT or INOUT parameters

- the function then calls another procedure

449501 Updating a column with a LF index in an upgraded database experienced slow performance. The performance penalty depended on the number of distinct values in the LF and the number of rows to be updated.
449513 Under certain circumstances, a query containing a correlated subquery

could report a non-fatal error "cannot evaluate expression"

depending on the cardinality of the data.

449521 Insert into a local table with a select from a derived table

where the derived table involves both local and remote tables

may cause server failure.

449573 Ability to load space & zero-length columns at the same time
449578 If the ROWID function was used on an alias to a view,

then server failure occurred instead of reporting the

error that ROWID over a view is not supported.

449707 When executing a .NET application that executes a stored procedure,

the second time the application was executed, a "cursor not open" error was reported.

449762 IQ server failure or an unresponsive server on shutdown could randomly occur when the thread memory size allocated on server startup exceeded 4GB. The thread memory size

is the product of the -iqmt value multiplied by the -iqtss value.

449963 Ability to make a backup based on creator of objects.
451346 Using dbisqlc in IQ 12.6 or 12.7, if we use following method to connect to the server from remote machine, dbisqlc -c 'dsn=shashi_demo', and then after get connected if we issue command, "connect database asiqdemo user DBA identified by SQL' then the connection is failed and any commands issued after this will not work, until this command is issued every thing works fine.

Using dbisqlc for IQ 12.5 ad using IQ 12.5 same thing works without any problem. On IQ 12.6 and 12.7 it fails. So it seems to be problem intoduced in IQ 12.6 and up.

Problem is not observed when connected to the IQ server from same host machine on which IQ is residing.

451471 If a query contains a join with multiple primary join

conditions, where one of the join keys is equated to

a constant value expression in another condition and

where the optimizer selected either the SMJ or the

SMPDJ algorithm for the join, then that query could

under some circumstances be rejected with a non-fatal

internal error stating that the input to a join

operator was "not ordered as required".

451556 Under certain circumstances a query containing case expression, that may return different data types, may return incorrect values or result in a server failure. The result is dependant on various conditions including the case expressions involving computations, data volume and available indexes.
451777 Under certain circumstances, a grouped "union all view" type query

where each arm is grouped may return extra rows.

451844 We have had a number of AIX customers have issues where the IQ process is killed by the OS when the OS detects it is running low on free paging-space blocks and starts hitting virtual memory running low condition. In AIX if this condition is detected the OS sends out a SIGDANGER(33) to active processes. If the condition persists it will chooses processes to kill to alleviate the condition, usually the biggest consuming process.

Can IQ be improved to see if there may be a way to better handle this condition so that IQ is not killed abruptly and cause recovery issues / problems. Could IQ issue a warning, or would there be a way to tell the OS not to select it, or even if IQ tries to dynamically reduces its requirements to alleviate the problem. Obviously this would be dependant on what the OS does, i.e. its not clear yet if the OS issues the SIGDANGER(33) then immediately start killing processes, and if so what signals does it send.

We are already aware that the underlying condition can be avoided by configuring more memory / paging space ... etc. etc. However in reality its not always possible or desirable for a customer site to provide excessively large amounts of these resources, so some degree of tuning is done based on 'normal' requirements, hence from time to time customers can and do hit this issue. Can we make it a little less painfull for them?

451899 On Windows 64-bit, the Sybase IQ Service Manager incorrectly

used a 32-bit file path when entering the service.

452026 A query with many productions (expression evaluations) could take a long time to execute.
452526 When attempting to display a result set that contained numeric data that could not be displayed, dbisql java could return the message "There was an error reading the results of the SQL statement. The displayed results may be incorrect or incomplete." This error message has been replaced with the the textual representation of the value that is returned by the server.
453050 Under certain conditions, an IQ server could fail at s_blockmap.cxx:2198

while executing operations that update HG indexes or LOB columns after

adding a dbspace that was assigned block numbers larger than 4 billion.

453588 sp_iqcheckdb on a read-only database caused the server to fail.
454166 Under certain circumstances, Starting Sybase IQ Service Manager from Start/Programs/Sybase/Adaptive Server 12.6/Sybase IQ Service Manager

might fail with the error "This application has failed to start because

the application configuration is incorrect. Reinstalling the application

may fix this problem."

454490 DBISQL could display LONG VARCHAR, BINARY, LONG BINARY or VARBINARY values as empty, if the "Show multiple result sets" option was ON and the truncation length was set to zero.
454784 Starting a multiplex query server with a local store with

the -iqro 1 startup option failed.

454965 A non-fatal exception error in dfp.cxx could be reported on

a query which involved a view which contained a UNION ALL of

2 SELECTS in the FROM clause and a WHERE clause with a

BETWEEN condition on 2 dates and an OR condition.

455667 In rare circumstances, the server might fail if multiple connections

ran the same procedure concurrently and the procedure contained a

control statement (for example, IF) with a condition that used a subselect.

455702 IQ is unable to resolve index names of same name table and temp table.
455820 The issue does not exist in IQ 15.0 or later, since from IQ 15.0 on, query servers do

not have local stores anymore, eliminating this kind of name collisions causing emergency

shutdown of the query server.

456013 A UNION of a numeric data type column to the NULL value

reported an "Incompatible data types in UNION" error.

456280 The ADO.NET driver of IQ 12.7 registered the wrong file to Visual Studio 2005.
456316 Support of NULLS FIRST|NULLS LAST in ORDER BY Clause
456456 The IQ server failed in attempting to set the option IDENTITY_INSERT on a global temporary table, if the SET OPTION command was the first operation after connecting and was the

first access of the global temporary table.

456533 A complex join involving more than 38 tables in the

join took a long time to be optimized.

456591 A query could return a non-fatal error from s_bm.cxx if it referenced a column

containing null values that was created in 12.6 or earlier and that column

had not yet been modified in 12.7.

456647 When creating a proxy table, if Japanese was contained in the Oracle table name,

creation of the proxy table failed.

456808 A query with search condition "<=ALL" or ">=ALL" may fail to return data. For example,

select col1, col2 from table1 where

col1>=ALL( select col1 from table2 where col1=1 )

order by col1, col2;

460713 temp table not found when created part of the batch & when executed from dbisql
461029 If the 'literal' supplied for the NULL column-spec was wider than 3956 bytes, columns might not be recognized as NULL, even if the data matched the literal specified for the NULL column-spec.
461174 Under certain circumstances, a non-fatal error "cannot evaluate expression"

might occur, if dml_options5=1073741824 was set.

461369 When a query had a single inline view which contained many UNION ALL branches and the first UNION ALL branch had a misspelled function, for example "UBSTR()", a server

failure could occur.

461593 Sybase IQ ignored the declared precision/scale of a variable and promoted the variable to a larger precision that is not supported by Open Client isql, resulting in the CT-LIBRARY error "An invalid numeric precision was received."
461665 stop_asiq on Linux 64-bit failed to find servers to shutdown when username was longer than 8 characters. See the Release Bulletin for information on the new optional stop_asiq parameter -user.
461762 The following conditions in a query could return unexpected results: 1) UNION ALL, 2) DISTINCT on UNION arms, 3) Left outer joins in the union arms, 4) Columns with multi-column HG indexes in the SELECT list of UNION arms.
461876 Incorrect syntax goes into inefficient way of processing, rather than erroring. This causes the connection to hang , if left alone for a long period and sometimes not being able to drop the connection. Only way out is to recycle the reader node.
462158 IQ server crashes if it runs out of main buffer cache instead of giving error
462333 Under certain circumstances, a query server could shutdown when a user canceled commands in transactions waiting on Table Level Versioning (TLV) versions.
462334 Sybase IQ shut down with a fatal error because a call to pthread_mutex_destroy returned EBUSY.
462390 A query returns an internal node error when a derived column is based on a RANK function on a derived column.
462733 When the option INFER_SUBQUERY_PREDICATES is ON, a query

involving a join and a NOT IN subquery where the subquery could

infer the predicate from a join condition could return unexpected

results, since the "NOT" condition was dropped. In order to infer

the predicate from the join condition, the data types of the join column

and subquery column must be identical.

462762 A query with a MIN or MAX aggregate could return an empty result

instead of the expected NULL value under the following conditions:

1) There were no GROUP BY items associated with the MIN/MAX.

2) The argument of the MIN/MAX could be simplified into a constant.

(For example: SELECT MAX(a) FROM t WHERE a=6)

3) No result rows satisfied the query predicate.

462766 Option to log more info when IQ shuts down
462773 Provide option to limit rows returned from a particular object for a user
462788 Allow load/extract table to use file from/to remote file system
463015 An ADO.NET provider 9.0.1.1530 Exception Type "System.ArgumentOutOfRangeException"

could occur when connection pooling is enabled and many users are concurently connected.

463160 The server might fail while running the sp_iqrowdensity stored procedure, reporting a stack trace at st_server.cxx: function.
463195 In a SQL batch, a cursor opened WITH HOLD could keep Temporary IQ

block usages increasing, until the cursor was closed and the connection

was disconnected. The workaround is not to use the cursor WITH HOLD

option.

463558 If a multiplex database was created with IQ PAGE SIZE 512KB (524288) and the write server was started with startup option "-iqnotemp 1", then the server failed, producing a stack trace.
463754 Under certain circumstances, queries involving CLOB or BLOB columns and a subquery could unexpectedly return the error "Feature, DISTINCT or GROUP BY against long binary/varchar data, is not supported."
463774 Under certain circumstances, a query that referenced a BINARY

or VARBINARY UNION ALL view column as a distinct or grouping column

could return a non-fatal internal error.

463784 ECC protocol restriction for ESD #3 clients

Sybase IQ 12.7 ESD #3 clients and servers have been updated to use Certicom v5 libraries

for Transport Layer Security (TLS) encryption, HTTPS encryption, and aes_fips database

encryption on the following platforms: AIX64, Linux AMD64, Sun64, and Windows 32-bit.

This update changes product behavior in a single instance. To connect a version 12.7

ESD #3 Network Client to a 12.6 Sybase IQ server encrypted, you must use the RSA

protocol. Attempts to connect encrypted to unpatched or 12.6servers using the Elliptic

Curve Cryptography (ECC) protocol return error code -829: TLS handshake failed.

463881 An attempt to create a Proxy Table using server class 'aseodbc'

when the remote table name contained an underscore would fail

with the error "The remote table <table name> could not be found."

(Duplicate CR 454785)

463892 provide option to add multiple lines in dbisql -nogui mode
464327 A server could fail with a Signal 11 if the Force_No_Scroll_Cursors

option was set to the non-default value of 'ON' and a client-side cursor

was closed and re-opened. The cursor operations could be called explicitly

from a client library or as the result of a CIS decomposed query

or OUTPUT TO statement.

464331 A server failure might result during an INSERT...LOCATION

of an ASE IMAGE column or IQ LONG BINARY column to an IQ

BINARY or VARBINARY column.

464420 In rare circumstances, the engine could fail when a stored procedure ran after DDL statements against the server caused a schema change involving a

cached stored procedure.

464869 Request feature that allows locking nonactive user account and indicates why the account is locked.
465093 mechanism where IQ re-use the same astmp file or deletes with session end
465663 On some UNIX systems (particularly AIX), files that the installer was trying to update could be held in memory and locked. This problem usually resolved itself in subsequent runs of the installer. However, if the locks continue to be held, run sybinstall with the new -unlock parameter. This parameter installs the files in a shadow directory, links to the correct location, then removes the shadow directory, thereby avoiding lock problems.
465679 Use of procedure references in the UPDATE statement could cause the server to fail under certain circumstances. The server now generates an appropriate error message.
465686 When IP aliasing is used, the plug-in might fail to connect to the agent.

Successful connections by host name might fail when the IP Address is used.

465697 Create a feature similar to ASE's named cache in IQ
465800 Under some circumstances, a query containing multiple nested levels of views or derived tables could encounter an internal error when either (1) the SELECT list of one of the higher level views or derived tables contained an expression that was not a constant, but which could be simplified into a constant value, or (2) some expression in the SELECT list of a higher level view was not used in the query using that view.
465896 An invalid double dot '..' expression in front of an aliased column name

in a GROUP BY clause could cause the server to be unresponsive.

466135 Certain combinations of CURSOR FETCH, COMMIT, and CLOSE CURSOR could server failure. The following sequence will cause a failure:

create table;

insert table;

commit;

open cursor for select from table;

commit;

insert table;

fetch cursor;

commit;

insert table;

commit;

close cursor;

See the Release Bulletin for a description of related behavior changes.

466246 More diagnostic information during dbbackup
466355 feature request to include the cpu cost in the query detail.
466410 Setting the option MAX_QUERY_PARALLELISM did not correctly

control the degree of parallelism used for UNION query processing.

466473 ODBC applications may not process UPDATE and DELETE commands properly, whenever zero

rows are updated or deleted. ODBC SQLROWCOUNT will be -1 instead of 0 for these two

cases.

466564 Under certain circumstances, Sybase IQ could produce incorrect results when an HNG index was created on a column of CHAR type and the logical expression of a WHERE clause contained a comparison operator between that column and a string longer than the column width.
466851 A "Table not found" error is returned if a base table owner is not supplied within a stored procedure that issues a SELECT on the base table and is run by a user who does not own the procedure but has execute permission on the procedure and select permission on the base table.
467394 After a select into a local temporary table returned "ASA Error -1000106: Local temporary table, table1, must be committed in order to create an index", a select, update or drop on the local temporary table caused server failure. Another sequence that caused the same failure: DECLARE LOCAL TEMPORARY TABLE foo (c1 INT);

CREATE foo (c1 INT);

467665 The IQ server fails while trying to resolve a range predicate simplification of the form "a > x OR a > y" where x and y are equal.
467981 The IQGOVERN_PRIORITY database option value might not persist

through a database stop and restart. If the IQGOVERN_PRIORITY

and IQGOVERN_MAX_PRIORITY options were set to 1 for the PUBLIC

group, the warning "Option IQgovern_priority has an invalid

setting: 1." was reported on database restart.

468278 An IQ database may fail to start after restoring a

backup that moves the catalog store.

468370 Depending on the configuration of your Windows system, when running the "Raw Device Access" or "Sybase IQ Service Manager" server applications, the following error message might have been reported: "This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem."
468458 If you used BCP IN to populate a table owned by a user other than the connected user, then BCP IN would fail with either a table not found error or the server would fail. In some cases, if the connected user also owned a table with the same name as the table being populated, then the server would attempt to add rows to the wrong table.
468769 Load table to should compare no. col specified in cmd is same as input file
468975 When '0x5c' is contained in the 2nd byte of a multi-byte character, dbisql cannot output the character to a file correctly. And this issue is reproduced when the character exists in the head of a character sequence.
469023 Changing passwords using the sp_iqpassword procedure fails in ISQL if the VERIFY_PASSWORD_FUNCTION option is enabled.
469093 In rare circumstances, a busy server executing DROP TABLE statements against local

temporary tables could become unresponsive.

469250 A database created with JAVA ON reported a different error on incorrect dotted references than a database created with JAVA OFF.
469460 Using the OUTPUT statement to output an indeterminate result set to a file causes dbisqlc to fail.
469715 Adding join to the view decreases performance , optimizer should choose push down instead of customer having to set join_preference = '-5'
469926 A query involving many UNIONs in combination with the SYS.DUMMY table may return

"ASA Error-300" and cause a stack trace.

469940 Query - Server failure was caused by incorrect logic for handling sort related data structures. Especially, this was a problem with "top n" kind of queries. The problem was not readily reproducible due to the fact that the problem was triggered by a busy temp cache.
469966 Provide option to set AutoPreCommit in the ASA.NET driver
469968 A datatype conversion error was reported when converting a zero length string to DATETIME.
470046 Using UNION ALL to put results from different proxy tables together used the data from the first proxy table to replace the expected data from the other proxy tables used in the query.
470168 Running the stored procedure sa_get_server_messages()

will probably cause the IQ temporary store to fill up.`

470183 With certain types of queries, the IQ 12.7 query optimizer simplifies certain query conditions to avoid unnecessary joins and comparisons. In certain GROUP BY operations, a problem was found due to an incomplete elimination of a sort operation.
470538 "sp_iqindexinfo" returned the wrong value for DBSpPct. It now returns

the correct percent of the dbspace used by the index.

470596 The IQ server may become unresponsive when the caches are heavily used, e.g., multiple connections are constantly loading to and deleting from tables.
470997 Provide an option to estimate space used by join columns between 2 tables
471000 A delete from a varchar column with a HG index defined could fail with

the message "Key too large" or insert ... location ...could fail with

"Page size selected is too small for this datatype".

471003 Executing a "DELETE ... WHERE ROWID(table) BETWEEN ... and ROWID(table) BETWEEN ..." statement could cause a server failure.
471004 sp_iqcolumn truncates column name on the 51st column and after
471075 Attempting to return a result set from within a BEGIN ATOMIC

block (this is not allowed) would not close the cursors that

were created for the SELECT. This would cause the server to fail

at st_txncb.cxx line 2822.

471237 A lot of insert queries freezes IQ without an error.
471297 If you execute a query that involves many tables, then there is a chance the query will cause the server to fail. Such failures are more likely with databases that have a smaller page size. This problem has been fixed and the server now properly gives an error when a query with too many table nodes is executed. The error is "-890 Statement size or

complexity exceeds server limits."

471302 Index Advisor recommends adding a CMP index on DOUBLE and FLOAT columns, when not all versions of Sybase IQ supports this behavior.
471405 iq_bcp cannot blkin data correctly about the combination of a char type and a datetime type.
472271 The sp_sproc_columns stored procedure does not return the parameter mode (IN, OUT, or

INOUT). Instead, it returns 0 for all the modes. This has been fixed.

472273 The procedure sp_iqprocparm() was returning the IN parameter mode for the INOUT parameter for all version of Sybase IQ. sp_iqprocparm() now returns INOUT mode for INOUT parameters.
472435 A non-fatal error could occur when the number of rows was greater than 2 billion and there was a prefix match in the LIKE predicate through a WORD (WD) index.
472803 Using the RANK statement returned data in the requested order, but if a WHERE clause was added, the data was sorted differently, ignoring the ordering requested.
473089 The performance of the sp_iqindex stored procedure degrades as the number of tables increases in Sybase IQ.
473547 A query that involves more than one Remote Procedure Call in the FROM clause could cause server failure. For example:

SELECT col1 from remote_procedure_1() where col2 = (select c1 from remote_procedure 2())

473728 Under certain circumstances, an IQ server could not start with a

freshly created IQ database using a raw partition on Windows.

474007 Execution of a SELECT statement with invalid syntax causes an IQ server failure

when a period is present, instead of a comma, between two items in a SELECT list in

which the second item is an aggregation function.

474371 Sybase Central Java and Sybase IQ plugin cannot create dbspace to a windows network drive.
474620 Allow a function similar to rowid() for views
474893 Server should return an error instead of hanging, if incorrect data is being passed to the variable in the set command
475766 The NOEXEC database option has been enhanced to support INSERT...VALUE, INSERT...SELECT,

INSERT...LOCATION, SELECT...INTO, LOAD TABLE, UPDATE, TRUNCATE, DELETE, SYNCHRONIZE JOIN

INDEX, and updatable cursor operations.

476329 On a default SLES 10 install, Novell moved the rawctl file from /dev to /dev/raw, and IQ fails to find it until it is either copied into /dev or softlinked in /dev.

Now IQ will look into both /dev and /dev/raw to find the rawctl file.

476496 Provide option to find total space used by a particular user
476598 User will be allowed to add columns to existing tables through Sybase Ceneral
477073 Subqueries with a simple predicate could show poor performance if the predicate contains a BETWEEN condition in the WHERE clause and not all of the predicate arguments are constants.
477187 Union All parallel query is serial in Subsequent Fetches phase
477501 Provide option in Insert...Location to move empty string as empty string
477504 A query involving a table with a multicolumn primary key joined to another table could cause the following exception in IQ 12.7 ESD #2 on Solaris and Windows: SQLCode = -1006000. This exception occurs when one condition in the join compares a column from the multicolumn primary key with an expression, rather than with a base column from the other table.
477609 Display an error when truncating column name in dbisql -nogui mode
477612 Allow user to be able to select view B without the need to grant select permission on the based table in the view A
477741 Operations such as INSERT...VALUES, LOAD, and SYNCHRONIZE are not affected by the NOEXEC option because they do not include a query.
477881 If you are using IP aliasing and have started your IQ server with the MyIP tcpip setting set to the alias IP address... for example -x tcpip{MyIP=10.50.7.70;port=6999}

... then if you try and connect from SC to the IQ server using an ODBC data source file (.dsn file), the connection works but you are not able to open the multiplex folder.

478439 The customer is waiting for release of "Multiplex management without Sybase Central."
478486 Restore fails with "not enough threads" if many stripes are involved in the restore.
478886 Subqueries with a simple predicate could show poor performance if the predicate contains a BETWEEN condition in the WHERE clause and not all of the predicate arguments are constants. This has been fixed.
478904 The maximum length of the string that the SORTKEY function can handle is 254 bytes.

The length limit of 254 bytes is now enforced and a new error message "Function not

supported for the string > 254" is reported.

479443 When Insert.. Location command was executed between two servers running on different collation, an error was thrown while trying to insert multi-byte characters. This fix handles such issues and inserts multi-byte characters using Insert.. Location.
480255 iq_bcp may be unable to insert the data of the length defined as charactor column. And the data of a succession column cannot be inserted correctly, either. For example, an issue is reproduced on a table with the column of char (50), char (210), and int.
480259 iq_bcp inserts wrong Japanese data. Moreover, it may cause a conversion error.

This issue relates to CR#480255.

480994 IQ server crashed in s_bufhash while trying to do a insert into a temp table
481251 execution of cleaner dll provided by eng returns "Invalid expression near rowid"
481616 If you attempt to revoke connect permissions from a user who still has an externlogin mapped, the server returns a foreign key error. Logging in as the user being dropped then results in incorrect user permissions. The server now returns an error that externlogins are still mapped for the user, leaving the user permissions unchanged.
481633 The following SQL statement could result in a Non-Fatal Internal IQ Error:

select id, fname into #ltt from customer where id = -99;

commit;

create index hg0 on #ltt(id);

savepoint S4;

create index hg2 on #ltt(fname);

drop table #ltt;

481648 A query with a condition containing thousands of OR-ed equalities in the WHERE clause, plus a FROM clause containing a view whose definition had a UNION with numerous arms, takes an excessive amount of time to get through the optimizer.
481807 In certain circumstances, using user defined functions as a parameter to a procedure call, may cause a server failure. The following conditions must be true:

- a cursor is opened on a procedure call that returns a result set

- a parameter to the procedure is a user-defined function call

- the UDF issues a COMMIT

481820 If a SELECT statement contains proxy tables and a procedure call to a procedure for that server cannot inline the procedure's SELECT statement (the first statement in the procedure

is not a SELECT), the server could fail. This issue could also occur if the SELECT is

used as a subselect in a DML statement. This issue is resolved.

481890 Server stacktrace when trying to release memory, it is stemming from DestroyCursor.

This appears to be a dupe of cr 466135.

482143 Query causes non-fatal stacktrace in dfo_ranking.cxx
482317 The Sybase IQ Administration Guide states: "The JDBC-based server classes are the only classes that can be used with 64-bit UNIX IQ servers." An asejdbc class is also supported by Windows x64.
482387 The server could fail when running queries containing 2000 or more OR-ed equality conditions over a view that contains a many-arm UNION. This has been fixed.
482604 Attempting to extract a VARBINARY column greater than 255 in length results in

the error "Data exception. Data conversion is not possible."

482705 systypes view uses allowsnull column instead of allownull
482989 Sybase central allows a DBA to create a users with a space in the name, but cannot drop them. This is corrected.
482990 Sybase Central.

User cannot uncheck checkkbox "No default or computed value" on "Column property -> Value panel" , after checking it.

483271 sp_iqcheckdb may show leaked blocks for a database on multiplex if the write server is started in read-only mode using the "-r" or "-iqro 1" server startup option. If sp_iqcheckdb does not report leaked blocks if the server is not started for read-only, there are no leaked blocks.
483384 In some situations, a query containing a CASE expression

with a HAVING clause reported Internal error at dfo.cxx

(Cannot evaluate expression).

483417 In certain circumstances, connections can appear unresponsive while the server returns large strings or binary large objects. This problem is more likely to be encountered when using TDS.
483455 Under a heavy load, and while another connection is executing DDL statements, calls to a user-defined function could result in a server failure. This issue has been resolved.
483767 If character data is extracted to a file when the TEMP_EXTRACT_QUOTES option is ON, the

data cannot be loaded successfully if the data contains quotes. For example, if a column

contains a'b'c, the extract file contains 'a'b'c', which cannot be loaded by the

LOAD statement with QUOTES ON.

483824 xp_cmdshell fails on IQ 12.7 when iqtc+iqmc is bigger than a certain value. The failure occurs if iqmc+iqtc is large enough for the server to start, but enough memory is not left over for a fork() to execute. This issue varies by the amount of memory on the system and is specific to Solaris.
484055 In rare circumstances, a complex query involving many derived tables and virtual

columns could cause server failure in dfo::DFEMightBeNullHere().

484204 The DDL version for the ADO.NET 2.0 driver shipped with Sybase IQ 12.7 ESD #3

for Windows did not match the IQ build version. This issue has been resolved.

484268 Sqllog should log complete sql and not limit it to 32K

� The whole query text is now logged in the request log as compared to current limit of 32k.

� If the output of logging is directed to server log/console then only 32k size of query text will be logged.

� Stored procedure sa_get_request_times will truncate the request log record to 64k size.

484702 The IQ server supports TDS password encryption when clients with this capability connect. However, clients shipped with Sybase IQ 12.7 do not support TDS password encryption. In order to use this feature, you must use Open Client 15.0 ESD #7 or later.
484711 Add functionality of IGNORE_DUP_KEY in IQ
484934 Feature request to allow set option Temp_extract_NameN to have value larger than 127 characters.
485021 Problem: The install and readme packaged with the product make reference to 揈TL Development 4.2.1 ESD#1�.

Workaround: Ignore the references to ESD#1 it should read ESD #2.

485022 Problem: The uninstall script for Linux does not remove the products.

Workaround: The user can delete the installation from the install directory manually.

485316 When explicitly inserting values to the DEFAULT AUTOINCREMENT/IDENTITY column of a table is allowed, the "Tried to insert a duplicate value into a unique index" error will occur, if the user:

1. inserted N (an integer or an exact numeric type with scale 0) to the DEFAULT AUTOINCREMENT/IDENTITY column, and

2. inserted N-1 to the DEFAULT AUTOINCREMENT/IDENTITY column, and

3. tries to insert a value to another column of the table.

485470 When connecting to ASE or Microsoft SQL Server, the Remote Data Access layer was setting the QUOTED_IDENTIFIER option to ON at connect time, thus always quoting identifiers when querying data from ASE or SQL Server. Due to a restriction in the ASE server, always using quoted identifiers caused issues if the column name was 29 or 30 characters in length. Now, when connecting to ASE or SQL Server remote servers, the QUOTED_IDENTIFIER option on the remote server is set to match the local setting.
485609 A query server may become unresponsive during multi-user tests and some multiplex

verification tests. This has been fixed.

485692 customer request (Infoco N.V.)enhancement request for the AUDITING option to include userid / connection id information in the audit record created

i.e. who is associated with the failed event being audited

485694 Feature Request: Implement COUNT_BIG function for compatibility with MS Link Server
485741 The current mechanism of generating query plans depends on a user connection to get the query text. Operations like event handling and triggers are connectionless, and

with this fix, the query plan displays a more meaningful message "Statement text unavailable".

485910 Feature request: An error or warning when implicit conversion a numeric data into an integer.
486216 In the sql that follows, no rows are returned from "select * from #temp_t1".

select * into #temp_t1 from sp_iqstatus();

select * from #temp_t1;

This is incorrect and rows will be returned in 12.7 esd5.

486261 nogui dbisql does not display the notification message of login procedure.
486491 A LOAD TABLE could possibly cause the server to stop processing, if the LOAD allocated more threads for processing than the number of indexes in the table. This problem rarely occurs.
486663 Installing Linux 32-bit version of Sybase IQ on a Linux 64-bit system now selects the correct version of the SDK, when an ESD includes the SDK.
487341 On certain Sun Sparc machines, scjview fails to load libdbput9_r.so file, even though the

file is available with proper permissions in lib directory.

487417 A lock table attempt may give a different error from previous Sybase IQ versions. A simple sequence to illustrate the problem is

user1:

create table t1;

lock table t1 in shared mode;

user2: (who does not have select permission to user1.t1)

lock table user1.t1 in exclusive mode;

The lock table attempt by user2 used to report error "Permission denied: you do not have permission to alter t1.". In 12.7 ESD #4 and later, the lock attempt now returns error "User 'user1' has the row in 't1' locked."

487710 Feature request to allow CONSTANT in the ORDER BY clause in the OLAP window.
487746 When 'group by' is used by subquery in view, NULL attribute of column is reset.
487747 When 'group by' is used by subquery in view, NULL attribute of column is reset.
487748 When 'group by' is used by subquery in view, NULL attribute of column is reset.
487749 When 'group by' is used by subquery in view, NULL attribute of column is reset.
488335 A select with a scalar value subquery in the SELECT list causes server failure when a TOP qualifier or ROWCOUNT option is set with an ORDER BY clause, where the first entry is also an outer reference in the subquery.
488546 IQ 12.7 server fails, when closing cursor.
488964 Running the following commands using ISQL will cause tds protocol error:

create table test_table (c1 int);

go

insert into test_table values (1);

go

alter table test_table add c2 bit not null default 0;

go

select * from test_table;

go

The error is:

CT-LIBRARY error:

ct_fetch(): protocol specific layer: external error: There is a tds protocol error. An illegal token was received.

489037 IQ is downed without error message and stacktrace when a query including sum and group is executed.

===Fix by Engineering=== ( Imran )

IQ server crashed on "Group by" while costing was calculated as security_code_cookie check was inserted by MS VC for windows 64 bit platform. Care has been taken security cookie is not set any more for this function.

489069 BuildClient Name displaying internal build name on windows
489234 Selecting from a view involving an outer join may cause an "An illegal token received"

error. This has been fixed.

489327 writer dbremote keeps sending messages to an excluded query server
489624 When sp includes output parameter, execute immediate command fail. execute iimediate returns error of -946.
489674 A server failure may result from memory corruption.
490076 A query involving a subquery may return incorrect results with a join index present.
490477 load table consistent messages when field that exceeded the limit of a column
490478 enhance "load table" for putting problematic data in one of the diagnostic files
490480 IQ 12.7 esd #3 , plugin 12.7.070907 gives error Invalid column index value 15 when using iAnywhere driver
490797 Load was generating wrong identity values if extract column delimiter in the last row.

Now identity values are generating correctly.

490818 If the constant 0.0 (one decimal separator and all digits zero) is used in the target

list of a select INTO <permanent_table> statement, the statement fails with the

"Syntax error near '0' on line 1".

491041 Using a signed value for array indexing may lead to a negative index due to bad code optimization on Windows x64. This has been fixed.
491070 Derived table and proxy table give wrong correlation name.
491377 document how to calculate resources needed for a split group by
491480 The server may fail at s_buf.cxx:1534. This failure should not occur under normal circumstances. It has happened very rarely. In order to help determine the cause, in the event of a failure, diagnostics will be output to the iqmsg file.
491483 The allowed value of the MAX_QUERY_PARALLELISM option is an integer less than, greater

than or equal to number of CPUs. When MAX_QUERY_PARALLELISM is set, the number of parallel

arms in a UNION GROUP BY can be greater than the number of CPUs.

491609 Queries of type

select count(*) from ... where (((... is null) or (... in ...)) and ...)

may cause the IQ server to crash. This is due to an attempt to write to a

read-only bock map. In this case, a copy of the block map needs to be made

and used. This has been fixed.

491748 Server fails at server.css:1192, signal 11 in hos_dfe_datetime_HOUR.

This problem occurred while estimating cost of a correlated sub-query. The fix resolves cost estimation issue and query now runs without error.

491779 Silent install removes 12.4.3 install, but does not install 12.7 client
491964 sp_iqcolumn does not include global temp table. sp_iqcolumn is made only for base table.
491979 On Windows 64-bit machines, running getiqinfo.bat gives the "asiqsrv12 is not running. Can not run stored procedures" error, and the subsequent 5 steps are missing.

What's needed is the x64 version of Psapi.lib to build findproc.cxx. This has been fixed.

492077 SUBCASE NUMBER: 11409837-11

CUSTOMER NAME: RBC DOMINION SECURITIES

ASIQ Version: IQ 12.7 esd #3

PLATFORM and OPERATING SYSTEM: Solaris

BASIC INFORMATION:

Customer will like to have some means that will show table names and blocks usage in TEMP space store (like ASE).

492374 dbisql will not exit when connection is killed or onerror exit is used.
492468 IQ shut down with a fatal error because a call to pthread_mutex_destroy returned EBUSY.

As a part of fix we raised an exception string and report the value returned by the call to pthread_mutex_destroy , in this way, we are ignoring the EBUSY return .

492507 On Windows, the FINDIQVER utility returned 32bit for a

64bit installation.

492996 The IDLE option is not included in Admin Script which Sybase Central generated. The dbremote connection started from script will be disconnected in default timeout of IQ. But the dbremote connection started from Sybase Central is not disconnected by timeout. Please modify script, if timeout is prevented. "idle#0" is added to a SQLCONNECT variable.
493414 The bitwise operators are defined for integer and bit array

data types only. They are not defined for bit type. Because

of this, the input operand of the bit negation operation is

casted to integer first. After applying the bit negation, we

try to cast the resulting integer value to bit again, which

does not work.

493441 A new keyword has been introduced for the

Default.ini file. The keyword is 'timeout'

and it belongs in the Network area of the

.ini file. The valid values for timeout

are specified in seconds in a range from

1 second to 2,147,483 seconds.

An extract of the Default.ini file contents

shows the appropriate syntax. For more

details on default.ini contents, refer to

the User's Guide.

==Begin snippet of default.ini======

# The timeout setting must be in the

# Network section. The beginning of the

# Network section is defined by the line below.

[Network]

timeout=3600

=End snippet of default.ini===========

Please note this timeout affects only

the ETL software acting as an ftp client.

This timeout value will not affect any

timeout setting that are defined on the

ftp server or enforced by the network at

the TCP layer.

493563 SELECT COUNT (*) may return incorrect results in a UNION ALL view.
493567 row_number () is not supported in the current IQ version when used in OLAP context
494004 Adjusting FS cache on RH4 and RH5 to reduce performance problems

High FS cache on Red Hat 4 and Red Hat 5 impacts concurrent transactions on IQ 12.7.

FS-Cache is a kernel facility by which a network filesystem or other service can cache

data to improve performance. Because the current transaction version in IQ 12.7 is

released only after the FS cache is totally flushed to disk, a high FS cache can

impact concurrent transactions.

Reducing the vm.dirty_background_ratio and vm.dirty_ratio parameters increases the

number of flushes, but decreases the duration. Shorter flush times release the current

IQ version more quickly and reduce performance problems.

Note

-- Red Hat 4 has no configuration parameter to limit FS cache size. In Red Hat 4,

FS cache depends on machine memory.

-- With Red Hat 5, this should be worked around by enabling direct I/O on the OS

level to disable FS caching (not available in RH4).

494230 Too Many UNION ALL requires time for creation of a query plan.
494668 A query involving DISTINCT, GROUP BY, and ORDER BY that had a SQL error could return a confusing error. A correct error message is now returned.
494972 The following SELECT executed against the asiqdemo database would cause the server to fail.

select * from (select top 2 cust_id = rowid(t) from sales_order)t;

495183 IQ cannot execute the next SQL. It is ANSI. However, ASE can execute the same SQL. The customer expects that the T-SQL function of IQ nears ASE. 1. select distinct a from tab1 group by a,b order by a,b;2. select distinct a from tab1 order by a,b;
497147 Windowing query with multiple columns in "partition by" clause was returning incorrect results. This issue is fixed now and correct results are returned regardless the number of columns in the "partition by" clause.
497149 Attempting to start a database with -iqro flag may fail to start with

a Sybase IQ Abort error.

497725 Fetch from a hold cursor could return a wrong answer.

As an example (in pseudo code):

drop table xxx;

create table xxx( c1 int );

open curs1 { select * from xxx };

insert into xxx values(1);

open curs2 { select * from xxx };

insert into xxx values(2);

open curs3 { select * from xxx };

insert into xxx values(3);

open curs4 { select * from xxx };

commit;

print 'cursor1 ======'

loop {

fetch curs1 relative 1 into c1

if SQLCODE = SQLE_NOTFOUND then { break loop } endif

print 'c1 = ', c1

} endloop

print 'cursor2 ======'

loop {

fetch curs2 relative 1 into c1

if SQLCODE = SQLE_NOTFOUND then { break loop } endif

print 'c1 = ', c1

} endloop

print 'cursor3 ======'

loop {

fetch curs3 relative 1 into c1

if SQLCODE = SQLE_NOTFOUND then { break loop } endif

print 'c1 = ', c1

} endloop

print 'cursor4 ======'

loop {

fetch curs4 relative 1 into c1

if SQLCODE = SQLE_NOTFOUND then { break loop } endif

print 'c1 = ', c1

} endloop

When running the script, the following results are produced

cursor1 ======

cursor2 ======

c1 = 1

cursor3 ======

c1 = 1

cursor4 ======

c1 = 1

c1 = 2

c1 = 3

The results for cursors 1, 2, and 4 are correct. The results for cursor3

are incorrect. Cursor3 needs to see rows with values 1 and 2; not just 1.

498713 In earlier versions of Sybase IQ, running the stored procedure sp_iqdbspaceinfo on the entire database generated an error if any dbspace in that database was offline. In Sybase IQ 15.1 esd 1 and later, no error is reported if a dbspace is offline.

The dbspace_online column was added to the output of the sp_iqdbspaceinfo stored procedure. A value of Y means that the dbspace is online and that the procedure returned data for that row. A value of N means that the dbspace is offline, meaning that the procedure was unable to return data for that row, and reports 0B (0 bytes) for those data values.

The dbspace_id column was added to the output of the sp_iqdbspaceobjectinfo stored procedure.

If you upgraded the server from a version earlier than 15.1 esd 1, you must run ALTER DATABASE UPGRADE on existing databases. If you do not upgrade the database, running the sp_iqdbspaceinfo stored procedure results in a 揚rocedure no longer valid� error.

498862 Database names are limited to 40 bytes when the limit should be 250. This issue has been resolved.
498912 stop_iq and stop_asiq have a new parameter: -version. Use this parameter to find either 12.x IQ servers and agents, 15.x IQ servers and agents, or both. Default remains the same: stop_asiq finds 12.x servers by default, and stop_iq finds 15.x servers by default.

12.7 Usage: stop_asiq -version [12|15|all]

15.1 Usage: stop_iq -version [12|15|all]

499172 When the multi-byte character which has '5c' in a remote table name is included, IQ cannot define correct remote_location.
499234 In SCJ:Information regarding Referential integrity constraints and Constraints will now be visible in the corresponding tabs.
499572 Utility to reset the DBA password in IQ catalog if the password is forgotten
500305 defncopy ( 5.0/P-EBF13575 ESD #4 ) from IQ 12.7 esd #4 exports stored procedure ddl incorrectly.
523750 IQ was getting an data type conversion error while trying to cast an empty string as double. The error was as follows - "Data exception - data type conversion is not possible". This error is fixed now.
523752 IQ 12.7 improve error message -1001006 ( Data exception - data type conversion)
528319 The server may fail in st_cursor::GetCursorDetailUtilityInfo -> hos_strncpy() when

multiple cursors are being opened and destroyed and information on cursors is being

collected by sp_iqcontext.

528569 iq_bcp cannot copy data to a table with a lot of columns.
529339 Database names are limited to 40 bytes when the limit should be 250. This issue has been resolved.
529798 In SCJ: Create database wizard will not allow user to assign a server port, which is already in use.
530012 The platform-dependent limit on maximum virtual address space has been removed for 64 bit platforms Windows64, IBM Linux, and Linux64 AMD.
530468 Using Sybase Central, the Create Table statement produced by copying a Table definition with a primary key constraint could have incomplete SQL that would return a syntax error when executed. This has been corrected.
530516 Customer (LEHMAN BROTHERS INC on 12.7 on solaris) would like a utility similar to the UDB db2ckbkp utility which will enable them to verify that a IQ backup is valid and restorable.
531097 If an Open Client or jConnect application executed a query that involved the use of host variables within a batch, then the server would have failed. This has been fixed so that the query now correctly fails with the error message "Host variables may not be used within a batch".
531331 Unable to backup a database built on raw partitions on Linux if raw partition's sector size is 4096.
531717 The Sybase IQ Utility Guide documentation for the Backup utility (dbbackup) is incomplete. The option -xo should not be used in multiplex systems and the Sybase IQ servers must be stopped when -xo is used.
531757 As a further enhancement to CR's 396843 and 499055 the customer would like to be able to use the new LOAD TABLE DEFAULTS ON option to do partial-width insertions in tables with an autoincrement without having to change the auoincrement column to allow nulls.
531820 In IQ versions 12.7esd4 and later, sp_password doesn't work correctly. Original sp_password syntax is 'sp_password caller password, new password, [userid]'. In case if 'SQL' is DBA's password, executing command as "sp_password 'DBA', 'abcd'", does not give the syntax error message and changes the DBA's password to new password without verifying the old one.
532151 On HP-UX, when a client application connect to IQ and aborts the connection while IQ is in the process of accepting the connection, IQ's listener thread aborts and no further connections can be made.
532396 Customer has a process where they backup their dtabase and restore it with renames on a different location. There is currently no supplied way or utility to rename the .db catalog file. The way to do this is a simple OS rename of the file and change the IQ startup scripts to point to the new name. However the entry for the name of the .db file is still stored in the SYSFILE system table as the original file name so when you look at the dbspace info in SC you still see the old names. We need a utility or method of changing the name of the ctalog store cleanly and fully.
532409 customer is after a feature request in IQ similar to Database Resource Manger in Oracle where they can set up user groups that have for example the ability to be guaranteed resources allocations. E.g. usergroup1 gets 80% of the CPU and usergroup2 only 20%.
533250 If a TCP/IP connection attempts to connect to IQ and the connection attempt terminates before IQ completes its accept processing, the IQ thread dies and cannot be used again by the server. Existing connections continue to work correctly.
533545 Debugging a stored procedure from SC caused the iqmsg file to fill

rapidly with Txn-Cmt-PostCmt messages.

533619 Backup allocates an array of 2048 byte buffers to use for backup. The array is sized to the number of threads participating in the backup and each thread will work one of the buffers in the array.

LINUX requires that the size of the transfer for read and write must be an integral multiple of the device's blocksize. For a disk, this is its sectorsize, which is normally 512 bytes. The other valid sectorsize values are 1024 and 2048. A blocksize of 4096 will not work.

You may use any of these values: 512, 1024 or 2048. Then, provided raw partitions are correctly setup, IQ backup and restore are successful.

533695 If dbbackup is started and cannot complete its task, an orphan transaction will be left on the server and no further checkpoints will occur until the server is restarted.
533736 Upgrading databases may change system table definitions and certain features may be unavailable. Use ALTER DATABASE UPGRADE to upgrade databases, but for limitations, see SQL Anywhere 11.0.1 > SQL Anywhere Server - Database Administration > Administering Your Database > Database administration utilities > Upgrade utility (dbupgrad). Sybase IQ does not support the dbupgrad utility.
533956 The IQ plugin is now registered for dbisql as part of the install.
534171 Output of the Join Node of the query containing outer join

and large nested CASE statements was blank. Now the

output of the Join node contains the required entry.

534316 Problem:

The ETL Engine Monitor memory foot print grows over a period of time.

Resolution:

This was resolved by modifying our garbage collection, clearing unused objects and removing the saving of some unneeded diagnostic information in memory.

534679 When using dbisql and the jConnect driver if you call a procedure that tries to insert a duplicate value into a table column with a primary key constraint , the insert fails but no error message is produced. Using the JDBC driver you get the "Tried to insert a duplicate value into a unique Index. SQLCODE = -1002003 HY000" error message.
535214  
535465 IQ will output a conversion error, when data including a different character code is used for load table. However, a conversion error may not be outputted at the time of "STRIP ON."
535527 In order to avoid the problems described by this CR, one should not begin or end dabtabase object names with space characters.

Sybase Central and DBISQL incorrectly handle object names that begin with a space character.

If a table (or view) is named "<space>customer", then Sybase Central drops the leading space when

communicating with the server. For example, trying to drop the table with SC results in

"drop table customer" being sent to the server rather than "drop table "<space>customer"".

Embedded spaces in an object's name are handled ok.

Tspaces are also handled ok. Table and view names are database column data

and trailing blanks in character data are ignored for comparison purposes.

For example,

create table "ab<space>" ( c1 iint );

create table ab ( c1 int ); <--------------will get table already exists

drop table ab; <-----------------------------will drop "ab<space>"

An exception is:

create table "ab<space> ( c1 int );

select * from ab; <-----------------will give an abiguous table name error when we should do the select.

535561 For a statement of the form "EXEC

<linked_server_name>..dba.myproc", Microsoft SQL Server

2005 passes a statement of the form {?=call "dba"."myproc"

} to the SQL Anywhere OLE DB provider. It passes in a

single integer parameter for binding with a status of

DB_E_UNAVAILABLE. As such, the EXEC statement failed

with an error.

535796 Problem: DB-Lookup takes additional memory for every block

Resolution: ??????????????????????????????????????????????????????

536049 IQ will crash silently, when a certain SQL is executed. A lot of GROUP BY is included in SQL. And this issue is not reproduced when an index is deleted from a table.
536059 System Administration Guide for IQ 12.7.

chapter 10: Transactions and Versioning

How transaction information aids recovery

[Optionally after incremental backup.] > Is a transaction log truncated by incremental backup truly?

536672 The error code defined as "ERROR" by ODBC State exists in IQ error message guide.

"HY000" is set to ODBC 2 or 3 State of these errors when ODBC or iAnyWhere JDBC is used.

However, description does not exist in a manual about "HY000."

537056 There is no description in a manual about "-wait" option of stop_asiq.
537079 When update/delete a local table, if it join with remote data, an error will occur. This is the specification of IQ.
537395 The following would cause the server to fail.

create table t1 ( c1 date, c2 time );

insert t1 values ( '12/12/12', '05:05:05' );

select c1.foo(), max( c2 ), c2 from t1;

An error is now reported. "Invalid type for field reference."

538102 You cannot create a raw device of more than 4 tb

on Linux.

538252 In IQ version 12.7GA and later, html plan of the query executed by the "event" and the "stored procedure" does not contain the correct "query-text". For events, the query text is "Statement text unavailable" inspite of the actual query while in case of stored procedure, the query text is "Call proc_name(...)" instead of the actual queries present in the procedure.
539090 Using isql, running in an IQ server (e.g., IQ 12.7 ESD #4) a stored procedure that was

created with CREATE PROCEDURE ... AT ... and calls a remote stored procedure residing on

another IQ server (e.g., IQ 12.7 ESD #2) may give an error like the following:

Msg 13732, Level 16, State 0:

ASA Error -660: Server 'sunspot': ASA Error -131: Syntax error near '.' on line 1

This has been fixed.

539237 Simple SELLECT using TOP and ORDER BY on table with 1 billion rows takes more that 13 minutes in IQ yet less than 10 seconds in DB2.

select top 10 act_rst_id into #aa from f_acct_rst order by prd_id

need a possible Feature Request to have ORDER BY optimization for TOP/FIRST put in

539428 BNP, an Alliance customer, asks if it could be possible to enhance an error message.

Here is the scenario:

create table mytab(att int) in SYSTEM;

insert into mytab location 'SYB125.base1' {select * from mytab};

Could not execute statement

Feature 'location' not implemented

SQLCODE=-134

Ct spent lots of time to find out that pb was due to the fact that the table was in the SYSTEM dbspace.

Could we get a message like

Feature 'location' not implemented in SYSTEM dbspace

instead?

539484 On Windows 32-bit and 64-bit, starting in IQ 12.6 ESD #8, after a remote ASE server is created using either class 'aseodbc' or class 'asejdbc' and before executing a SQL statement that contains a string with double quotes against the remote server using the FORWARD TO statement, you need to do one of the following to make the SQL statement work:

1. Change the double quotes to single quotes

2. Include "set quoted_identifier off" before the SQL statement to be executed:

FORWARD TO <remote server name> {

set quoted_identifier off

<SQL statement>

}

3. Set the quoted_identifier to off using a separate FORWARD TO statement:

FORWARD TO <remote server name> { set quoted_identifier off }

539566 Problem:

ETL takes too long to set the query statement via ODBC on a huge table.

Resolution:

A change was done to delay the execution of the sql statement to when the project is run to avoid server load during design.

539604 A statement with PARTITION BY 2 columns may be incorrectly evaluated when the WHERE clause has an equality predicate.

For example:

select MarketDateTime,LastPrice,count(*)

over (partition by NumericalInstrCode, BucketId order by LastPrice rows between

unbounded preceding and current row) PriceRank from test

where MarketDateTime between '2008-01-01' and '2008-01-02'

and NumericalInstrCode=1;

540233 The IQ server may crash or hang when the main or temporary cache is severely stressed

and the emergency buffer pool is involved. This is a duplicate of CR 273582 and has been

fixed.

540430 If a conversion error occurred while constructing the string to be executed by EXECUTE IMMEDIATE within a procedure, the error might not be reported, and the server may fail.
540641 Problem:

When using Insert Location, some table names are truncated at 30 chars when browsing a database.

Resolution:

The code that gathers the table names was changed to use a SQL statement rather than sp_tables when the DBMS is Sybase IQ Version 12.n

541590 The following SQL will cause the server to report a

Non-Fatal IQ Internal Error Detected at dfo_cOrderBy.cxx:217:

create table T1 (C1 varchar(10));

insert into T1 values ('Tabla 1');

create table T2 (C1 varchar(10));

insert into T2 values ('Tabla 2');

commit;

select top 10 * from (

select 1 as M from T1 union all

select 2 as M from T2

) as R order by M asc;

541875 Refer to the Release Bulletin for fixed bugs and more information on this release.
541879 In rare cases, executing an invalid ALTER PROCEDURE statement, e.g., ALTER PROCEDURE WITH RECOMPILE ..., could cause a server failure or an incorrect error message.
542300 Problem:

ETL throws an exception when retrieving data from MSSQL when "AUTO_COMMIT=0" is set.

Resolution:

The transaction handlers for ODBC were modified to recognize when the Auto commit setting is turned off.

542502 In IQ 12.7 ESDs #4 and #5, an UPDATE or DELETE statement against an IQ table with rows affected returns SQLCODE of 100 and SQLSTATE of 02000 as opposed to the correct values of 0 and 00000 respectively.
543249 When using the Sybase IQ BACKUP command, users can parallelize the operation to multiple devices by specifying multiple TO clauses. Backups created using a backup statement with more than 36 TO clauses may create backup archives that are unreliable. While these archives appear to be correctly written, they may contain invalid headers and cannot be restored. Sybase strongly recommends that customers who have created backup archives to more than 36 devices test the archives by restoring them to a test area. Do not attempt to restore the archive to a production database unless this test has completed successfully. If the test restore fails, create new backup archives using 36 or fewer TO clauses. The Sybase IQ Backup should limit the BACKUP statement to a maximum of 36 TO clauses.
543834 In the 12.7 System Administration Guide, Chapter 5, "Dbspace Management Example," the line "sp_iqrelocate 'empdb'" should read "sp_iqrelocate 'database'."
543864 On occasion the reader can become unresponsive when multiple create procedure statements are run in batch on the writer. There is a dead lock between dbremote thread and tlv replay thread. This problem is fixed by restricting dbremote thread to not lock tlvstore.
544567 The example of connection currently written to 26 pages of Installation and Configuration Guide Sybase IQ 12.7 for WINDOWS is a mistake. The correct example of connection is "<hostname>: <portnumber>" and "fiona_asiqdemo:1870."
545179 IQ 12.7 documentation inconsistency

In IQ itself (i.e. select * from SYSCAPABILITY) the column name for SYSCAPABILITY is srvid. However the IQ documentation manuals refer to the column name as svrid

545216 Problem:

ETL fails to properly read some dates when accessing databases using the ct-lib/Open client interface.

Resolution:

Changes were made to ETL's database interface class to properly handle column sizes.

545613 The following sql will cause the server to fail:

select * into t from sp_iqstatus();

select graphical_plan( 'select * into t from sp_iqstatus()',1,'ASENSITIVE','READ-WRITE');

This problem is fixed and a proper error is now given:

-894 Plan cannot be generated for this type of statement.

545673 The optimizer was performing incorrectly while executing constant virtual Column Substitutions. As a result of the problem, the ordering between join node and order by node is out of sync which is causing the "Input to merge join X from child Y not ordered as required" error.
545763 EBF installation steps of Linux x86 and Linux x86-64 differ.
546338 The server fails running sp_iqcheckdb 'verify database' for a database where there is a mismatch between the number of rows for an FP index and the number or rows for an LF index.
546789 Sybase Central cannot show Database Propery of 1024000MB of IQ Store. And an issue will be reproduced also at the time of 1024000MB of IQ Store, and its multiple.
546817 If an application uses a badly formed update statement of the form "update test X set X..a = 2" where test is a proxy table, then there is a chance the server may fail.
546821 Problem:

When configuring DB Data Provider Full Load component using ASE15.0.2 ESD5 with ODBC, ETL will only see dbo in Schema field, other schemas are not present. Manually typing in the schema manually into the schema field with not work either.

Workaround:

There are 2 workarounds for this issue. Use ASE native connectivity instead of ODBC or use the ASE15.0.2 GA version. This will be fixed in the ETL product in future releases.

547135 sample of "Encrypted Columns in Sybase IQ" is wrong. INSERT INTO t (cipherCol) VALUES ( AES_ENCRYPT (CAST 1 AS UNSIGNED INTEGER), 'key' )) ---> INSERT INTO t (cipherCol) VALUES ( AES_ENCRYPT (CAST (1 AS UNSIGNED INTEGER), 'key' ))
547532 While creating Simplex node using Sybase Central, only CreateDB.sql is created in DB directory. To avoid confusions, on Create database wizard changed the label to "Create sql script" from "create Admin shell script".
547636 DELIMITED and ROW DELIMITED are required for LOAD TABLE ENCRYPTED.
547690 Support column default special value, LAST USER and TIMESTAMP, is in 1270.

It is missing from Atomic GA.

547747 Problem:

The ETL UI hangs when opening a file that contains data for 10,000 columns.

Workaround:

When the OPEN dialogue opens, cancel it, click on the auto-update button in the component, then return to the OPEN dialogue, and open the file.

548227 Some queries involving a full outer join and a left or a right join may return incorrect results in IQ 12.7 ESDs #4 and #5.
548329 Sybase IQ Wide Table Support and Limitations in ETL 4.5 EBF 1

Wide tables (tables in Sybase IQ with 100s or 1000s of columns) use a lot of memory. To tune your target IQ system to handle wide tables, read the Sybase IQ Performance and Tuning Guide, especially chapter 5 Managing System Resources.

The following observations and recommendations are based on using Sybase ETL to migrate wide tables from one Sybase IQ instance to a target Sybase IQ instance with tables configured with varying numbers of columns and rows.

Observations and Recommendations

Repository:

- It is recommended to use a SQLAnywhere (SA) repository when using Wide Tables rather than an MS Access or a SQLite repository.

- It is recommended to allocate a 1 gigabyte database for the SA repository with all the other values remaining as the system defaults.

InsertLocation:

- Insert Location is supported using a 3000 column table.

Migration Wizard:

- Migration Wizard is supported using a 3500 column table with both OCS and ODBC interfaces.

Load Table:

- Load Table is supported using a 3000 column table with the OCS interface.

- Load Table is supported using a 10,000 column table with the ODBC interface, although performance suffers as larger numbers of rows are moved.

User Interface Experience

General Limitations:

When working with wide tables, the UI can take a long time to respond to user requests. In general, it is a good idea not to preview any data with this many columns. This could cause the UI to hang for long periods of time.

Insert Location Component:

- There are currently no known user interface specific limitations when configuring the Insert Location Component

Load Table Component:

- The Text Source dialog will truncate the display of data from files containing more than 50,000 bytes of data.

- If the data file contains more than 5800 columns, an error will occur and the output port preview data will not be available. This error will not prevent configuration of the component - the UI will continue to function normally without output port preview data. It is also possible that the UI will hang when previewing tables as wide as 10,000 columns.

Workaround:

- To avoid this, cancel out of the text file selection dialog, click the Auto-update button (to turn it off), and select your text source file.

Migration Wizard:

- Occasionally, the Migration Wizard will fail to generate all of the migration projects. This is usually due to memory limitations or using a non-SA repository.

Query Designer:

- Adding thousands of columns to a query at once can cause the UI to hang.

548363 "Encrypted Columns in Sybase IQ" says the default value of ASE_BINARY_DISPLAY option is ON.However, the default value of IQ12.7 is OFF.
548884 In SCJ: Triggers are not supported for IQ tables hence this option is disabled for IQTables.Only SA tables will be listed as a choice to create triggers.
548898 Add "ASA Error -267: COMMIT/ROLLBACK not allowed within atomic operation" to IQ error messages.
549633 Server crash during dbspace resizing operation on raw partition.
549802 The server sometimes failed, when an ORDER BY clause in

certain queries contained a reference to a null column.

550298 In rare instance, when a user cancels an operation that

involves a local temporary table, the server may fail.

550477 If an Open Client or jConnect application executed a query that involved the use of host variables within a batch, then the server would have crashed, rather than giving the "Host variables may not be used within a batch" error message. This problem has now been fixed.
552413 If an application executed a remote query that involved a

UDF, and the UDF call passed in column references as

parameters, and the server ran the query in partial passthru

mode, then there was a chance of server failure.

553049 The IQ_MPX_VERSIONLIST table of the query server to be promoted to become the writer may

not include an entry for one of the other query servers, resulting in the

"IQ_MPX_VERSIONLIST is missing row" error when sp_iqmpxvalidate is run after the writer

server replacement steps are completed. This has been fixed. In the 12.7 System Administration Guide, step 2 "Replacing a write server that has no SYSTEM dbspace and/or

transaction log file" on page 668 should read:

2 Choose the query server with the largest value in "DBA".IQ_MPX_STATUS.catalog_version

(or any one of those query servers, if the largest value exists in more than one query server) to be the new write server.

553166 Description does not exist in a manual about the output value of sys_iqsysmon.
553685 Result exceeded when query with 15 left outer joins and 6 equijoins is executed. This results into failure of the server. The datatype of the resultant variable is changed from 4 bytes to 8 bytes.
554163 A stuff function cannot replace a multibyte strings correctly. A stuff function attaches the null character to the end of a strings. This problem is now resolved and STUFF returns correct results regardless the character set used.
554706 On certain processors other than x86 and x86_64 (64 bit

HP-UX for example), the server failed in

extremely rare conditions, when using a connection number to

get connection information. Examples of getting this type

of connection information include getting a connection

property for another user, or calling sa_conn_info.

554902 In SCJ : The "New Dbspace" and "New DBSpace file" creation menus are disabled (greyed out) on secondary reader nodes.
555329 restore command does not trim off the blank char of end of an extension.
555571 If an application defined a view containing a remote query,

and if the remote query contained a GROUP BY ... HAVING

clause, then using the view in a query caused a server

failure.

555949 If a connection string containing the "verify=no" TCP

parameter was passed to dbisql and the -jconnect switch was

used, the client failed.

556113 The JRE for windows has been updated from version 1.6.0_10 to version 1.6.0_16
556474 Fixed as part of 12.7 esd 6. With this fix users with spaces can be dropped.
556489 A command line longer than the catalog page size can cause the "Syntax error near 'parse

stack overflow' ..." error. The workaround is to use a larger catalog page size when

creating a new database, and is to split long statements into shorter ones for existing

databases.

557256 In SCJ: Now the zooming scale can be persisted and restored in topological view.
557378 In SCJ : For Recycled MPX node, the old MPX information like MPX name is retrieved from MPX Coordinator node.
557477 If an application makes use of one of the remote data access JDBC classes, and if the application then disconnects abnormally, then the connection to the remote server is never closed. The problem does not exist if the application uses one of the remote data access ODBC classes instead. This problem has now been fixed.
557571 Improved logging information in log.txt to help debugging problems.
557787 Query - In some cases, when issuing a rollback with open cursors, cursor cleanup was not properly done which was causing a server failure. This has been fixed.
558267 If a reader node attempts to modify any object in main store, earlier release threw following error:

A query server may not modify objects in the main store.

with following error codes:

SQLSTATE: QXA19

SQLCODE: -1010019

Sybase Error: 21113

The error message has been changed to following:

Cannot modify object <object name> on dbspace <dbspace name>. A query server may not modify objects in the main IQ store.

with following error codes:

SQLSTATE: QXA31

SQLCODE: -1010031

Sybase Error: 21131

558429 Back-end query sent to the server has been corrected in Sybase Central.
558448 Create a new function at IQ like rowtype function at Oracle.
559090 ADORecordSet.MoveFirst does not obtain the correct result.
559255 When a NUMERIC or DECIMAL column with precision greater than 47 is fetched using OLE DB, ODBC, or JDBC, a memory buffer overrun will occur. This will result in a corrupted heap. The client application may then terminate unexpectedly because of the corrupted heap.

This problem has been fixed.

559311 When trying to send message greater than 2k size to client, server was not responding when charset conversion is needed between server and client. This problem is fixed in this release.
559518 A jvm not found message should no longer be displayed during an installation. If the user encounters this message the user should pass -is:jvmtimer 30 to the setup launcher.

Example. ./setupHP-UXi64 -is:jvmtimer 30

If the problem still persists try increasing the value from 30 to something larger.

560032 The stored procedures sp_iqbackupsummary and sp_iqrestoreaction now accepts either a timestamp or backup id.

Since the store procedure definition has changed, user will need to run ALTER DATABASE UPGRADE.

560074 From SCJ: In an existing table, a new column can be added and made the partition key before saving.
560295 In SCJ: Appropriate property dialogs for Primary, Foreign and Unique Constraints. This enhances the information in the Primary and Foreign key properties dialogs.
560392 The third argument to the LOCATE() function cannot be

CAST larger than BIGINT.

560760 The optimizer might incorrectly decide on optimization

by inversion for a query with a range predicate.

561320 Engine may become unresponsive when tearing down a sort used in a query or other DML operations.
561364 LOAD TABLE may fail to load any rows during a binary load

to a table with default values.

Here is a sample to illustrate the failure.

create table t1( c1 int, c2 date default current date,

c3 time default current time );

load table t1( c1 ascii(4), filler(1) )

from 'data.inp'

format binary

quotes off escapes off;

select count(*) from t1;

NOTE: datafile 'data.inp' must contain the following

1234

1234

561682 b-tree corruption could result in rare circumstances causing index corruption and checkdb "Missing Key" errors.
561788 A simple query returns incorrect result (empty column output).
561791 Complex SELECT CASE query causes server failure when catalog cache memory(-c) is not sufficient to execute the query. This problem has been fixed. Now the server will return error saying "Query Complexity exceeds server limit" whenever it runs out of catalog cache memory while executing SELECT CASE query, '-c' value need to be increased in that case.
562229 If you add a file to IQ_SYSTEM_TEMP and that file either happens to have a name starting with n or is in a directory that has a name that starts with n, no error is reported but the secondary server fails to open the file and cannot use it.

The file gets created correctly but the TLV log has an incorrect entry. On replay the replay fails silently and the file is never opened

562255 In SCJ : In "Convert to MPX wizard", "Add Server wizard", and "Create database wizard", the agent field is blank. It has been requested that this is inconvenient to users. If the agent port is already known, the field should be initialized with that port number. Otherwise, the field should be initialized with the default agent port (i.e. 1099).
562308 In SCJ : The Upgrade (File | Upgrade when a database has been selected OR select a Database and right click followed by Upgrade) should be enabled for IQ 15.0 e01. This menu option was grayed out for 15.0.
562371 For a scenario where 'alter dbspace ... readonly' command is executed on coordinator and followed by 'readonly selective restore' operation immediately, then a secondary node may crash in earlier release.

With this release, in this scenario, the restore operation may either succeed or give following error:

Cannot execute 'restore <dbspace or dbfile name>' since previous alter command is not yet propagated through the multiplex. Try again.

SQLSTATE: QSA66

SQLCODE: -1009066

Sybase Error: 20087

562403 When the process sending DDLs to the reader was terminated

with a user interrupt, the reader became unresponsive due

to a deadlock.

562654 The scripts start_asiq/start_iq now set by default on the HP-UX O/S the following environmental variables to help reduce memory fragmentation: _M_ARENA_OPTS=1:4096 & _M_SBA_OPTS=65536:50:256
562705 When running iqunload if a value for 杕s_size was specified and was smaller than the required size the verification step for the iqunload would fail. The iqunload tool will now detect that the user specified size was overridden and verification will succeed.
563004 If the first IQ_SYSTEM_MAIN or first IQ_SYSTEM_TEMP file was without file extension, instead of restoring to those files, restore tried to create (or write into if already existing) files with default extension (.iq or .iqtmp). However, the catalog remained unchanged. Post restore, the database tried to open the files without extension, thus referring to stale content.

The problem has been fixed.

563338 The server may assert and fail in s_ohcqry.cxx if the option HG_Search_Range is set too high.
563435 A PHP module is not attached to IQ. However, it is written to the manual that it is attached.
563681 In SCJ : Set Clustered Index menu item now works for Catalog store tables. This option is grayed out for IQ Tables.
563682 In SCJ: Indexes created on catalog store tables listed under the Indexes Tab. Further, it is possible to view properties and mark index as clustered from the properties dialog of catalog store table indexes.
563691 A failed COMMENT ON PROCEDURE statement could prevent the procedure from being dropped. This has been fixed. A workaround is to stop and restart the database before attempting to drop the procedure.
564035 Using "dateformat( colname, 'hh:mm:ss' )" does not output

the correct time. For example:

create table t1 ( c1 time );

insert t1 values ( current time );

select dateformat( c1, 'hh:mm:ss' );

Will output 09:mm:33

564092 Using jconnect gives rises to a number of issues while using SCJ. Changing default driver to iAnywhere from jconnect.
564252 IF EXISTS( SELECT * FROM A,B), where A is an ASA object and

B an IQ object, caused an IQ server failure with a signal 11.

564512 The server failed starting a database with the "-iqro 1"

server option set after restoring the database. This

database was a Multiplex Reader database being started

using the "-iqmpx_ov 1 -iqmpx_sn 1" options as well.

565133 First, I want to state, for the record, that we received excellent support from John Barton during this eval� He was always only a phonecall/email away, and he and I spent many hours of quality time together on the phone and virtual room, looking at problems and solutions together. John抯 support was excellent, and so I feel confident that our test results are not skewed by any lack of understanding of the product on my part.. he was there with me every step of the way to keep me straight!

Regarding follow-up, we are currently taking stock of our findings and roadmap options.

Dom Ruffatto is my product management counterpart, and will be the one to contact you regarding any follow-on discussions. I CC抏d Dom on this email, by way of introduction.

Dom � Peter Do is the Sybase account rep for HP.

Regarding testing results.. here is a very quick summary of my findings:

- Select Star Schema queries degraded in performance very quickly as the fact table grew, due to expensive hash joins on queries that matched larger number of dimension records. See chart below. We experimented with join indexes which did speed up the query, but prohibitively slowed down the data loads. John has all the supporting information and query plans�

So we modified the schema (and indices) and test queries to focus on a flat fact table structure, where facts and dimensions were pre-joined during loading, with the goal that hash joins could be avoided.

However, data loading times are problematic.. You can see from the chart below that load times increase with the size of the fact table. John helped me profile this behavior.. the elapsed time was almost all involved in the maintenance of two HG indexes applied to high cardinality name columns.. Disk I/O was pegged at 100% (iostats 杧) during these loads.. This implies that performance cannot be improved by further parallelization.. in fact the addition of additional parallel workloads can be presumed to compound the problem by competing for the same I/O resource.

Removing the HG indices dramatically speeds up the load times, but also dramatically slows down queries which filter on the name columns. LF indices are not an option as the name columns have more than 10,000 unique values.

So, that抯 the summary of findings.. Please let me know if you feel these findings are in any way inaccurate or unrepresentative of SybaseIQ 15_0 behavior, or if there are any solutions we haven抰 explored relating to the load I/O performance issues mentioned above.

NOTE: We tested Sybase 15.0 beta, understanding that it had improved parallelization of HG index updates, but unfortunately the bottleneck is disk I/O, not CPU.

Also, please let me know if you are aware of any upcoming product features that might improve the load performance of fact tables with HG indexes, specifically enhancements that might reduce the disk I/O associated with these updates and therefore remove or diminish the effects of I/O saturation noted above.

Detailed log:

I. 01/23 18:23:34. 0000025215 [20895]: Insert Pass 1 completed in 5 seconds.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C2_HG: Thread 7 Inserting 98210 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C2_HG: Thread 0 Inserting 98210 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C2_HG: Thread 2 Inserting 98210 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 4 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 0 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 5 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 2 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 3 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 6 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 1 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 7 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C2_HG: Thread 6 Inserting 98210 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C2_HG: Thread 4 Inserting 98210 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 DBA.fact_tmp.ASIQ_IDX_T733_C2_HG Sort Insert Statistics: 30 pages over 1 run(s) (Min: 30 Max: 30 Avg: 30) from 1 inserter(s).

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 4 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 5 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 0 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 2 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 7 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 6 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 3 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 1 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 5 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 4 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 0 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 7 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 6 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 1 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 3 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 2 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 5 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 4 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 0 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 7 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 6 Inserting 16370 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 1 Inserting 16320 Recs, 0 Secs.

I. 01/23 18:23:35. 0000025215 DBA.fact_tmp.ASIQ_IDX_T733_C1_HG Sort Insert Statistics: 30 pages over 1 run(s) (Min: 30 Max: 30 Avg: 30) from 1 inserter(s).

I. 01/23 18:23:35. 0000025215 [20895]: Insert Pass 2 completed in 1 seconds.

I. 01/23 18:23:35. 0000025215 [20896]: Insert for 'fact_tmp' completed in 6 seconds. 491050 rows inserted.

I. 01/23 18:23:36. 0000025215 Cmt 85137

I. 01/23 18:23:36. 0000025215 PostCmt 0

I. 01/23 18:23:36. 0000025215 Cmt 85139

I. 01/23 18:23:36. 0000025215 PostCmt 0

I. 01/23 18:23:38. 0000025215 Insert Started.

I. 01/23 18:23:46. 0000025216 Cmt 85142

I. 01/23 18:23:46. 0000025216 PostCmt 0

I. 01/23 18:23:47. 0000025215 [20895]: Insert Pass 1 completed in 11 seconds.

I. 01/23 18:23:50. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 6 Inserting 16380 Recs, 2 Secs.

I. 01/23 18:23:51. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 4 Inserting 16380 Recs, 4 Secs.

I. 01/23 18:23:51. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 2 Inserting 16375 Recs, 4 Secs.

I. 01/23 18:23:52. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 3 Inserting 16380 Recs, 5 Secs.

I. 01/23 18:23:52. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 0 Inserting 16390 Recs, 5 Secs.

I. 01/23 18:24:00. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 5 Inserting 16305 Recs, 13 Secs.

I. 01/23 18:24:05. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 4 Inserting 16380 Recs, 18 Secs.

I. 01/23 18:24:05. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 1 Inserting 16380 Recs, 18 Secs.

I. 01/23 18:24:06. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 6 Inserting 16380 Recs, 19 Secs.

I. 01/23 18:24:06. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 5 Inserting 16380 Recs, 19 Secs.

I. 01/23 18:24:06. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 7 Inserting 16380 Recs, 18 Secs.

I. 01/23 18:24:06. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 2 Inserting 16380 Recs, 19 Secs.

I. 01/23 18:24:06. 0000025217 Cmt 85144

I. 01/23 18:24:06. 0000025217 PostCmt 0

I. 01/23 18:24:07. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 3 Inserting 16380 Recs, 20 Secs.

I. 01/23 18:24:07. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 0 Inserting 16380 Recs, 20 Secs.

I. 01/23 18:24:14. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 3 Inserting 16380 Recs, 22 Secs.

I. 01/23 18:24:17. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 7 Inserting 16360 Recs, 30 Secs.

I. 01/23 18:24:21. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 4 Inserting 16380 Recs, 16 Secs.

I. 01/23 18:24:22. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 6 Inserting 16380 Recs, 16 Secs.

I. 01/23 18:24:22. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 1 Inserting 16380 Recs, 16 Secs.

I. 01/23 18:24:23. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 5 Inserting 16380 Recs, 17 Secs.

I. 01/23 18:24:25. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 2 Inserting 16380 Recs, 19 Secs.

I. 01/23 18:24:25. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 3 Inserting 16360 Recs, 11 Secs.

I. 01/23 18:24:25. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 1 Inserting 16375 Recs, 38 Secs.

I. 01/23 18:24:25. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 7 Inserting 16380 Recs, 19 Secs.

I. 01/23 18:24:26. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 5 Inserting 16390 Recs, 26 Secs.

I. 01/23 18:24:26. 0000025218 Cmt 85146

I. 01/23 18:24:26. 0000025218 PostCmt 0

I. 01/23 18:24:26. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 7 Inserting 16315 Recs, 9 Secs.

I. 01/23 18:24:29. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 3 Inserting 16380 Recs, 22 Secs.

I. 01/23 18:24:29. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 0 Inserting 16380 Recs, 22 Secs.

I. 01/23 18:24:29. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 3 Inserting 16435 Recs, 4 Secs.

I. 01/23 18:24:37. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 1 Inserting 16340 Recs, 11 Secs.

I. 01/23 18:24:37. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 2 Inserting 16380 Recs, 46 Secs.

I. 01/23 18:24:37. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 5 Inserting 16435 Recs, 11 Secs.

I. 01/23 18:24:43. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 6 Inserting 16475 Recs, 53 Secs.

I. 01/23 18:24:46. 0000025219 Cmt 85148

I. 01/23 18:24:46. 0000025219 PostCmt 0

I. 01/23 18:24:47. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 4 Inserting 16380 Recs, 26 Secs.

I. 01/23 18:24:48. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 6 Inserting 16380 Recs, 26 Secs.

I. 01/23 18:24:48. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 1 Inserting 16380 Recs, 26 Secs.

I. 01/23 18:24:51. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 2 Inserting 16380 Recs, 26 Secs.

I. 01/23 18:24:51. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 5 Inserting 16380 Recs, 27 Secs.

I. 01/23 18:24:53. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 7 Inserting 16380 Recs, 27 Secs.

I. 01/23 18:24:53. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 6 Inserting 16380 Recs, 10 Secs.

I. 01/23 18:24:57. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 0 Inserting 16380 Recs, 28 Secs.

I. 01/23 18:24:58. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 3 Inserting 16380 Recs, 29 Secs.

I. 01/23 18:24:59. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 3 Inserting 16350 Recs, 30 Secs.

I. 01/23 18:25:02. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 0 Inserting 16380 Recs, 70 Secs.

I. 01/23 18:25:03. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 6 Inserting 16375 Recs, 9 Secs.

I. 01/23 18:25:04. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 0 Inserting 16350 Recs, 2 Secs.

I. 01/23 18:25:04. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 6 Inserting 16400 Recs, 1 Secs.

I. 01/23 18:25:06. 0000025220 Cmt 85150

I. 01/23 18:25:06. 0000025220 PostCmt 0

I. 01/23 18:25:08. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 3 Inserting 16375 Recs, 9 Secs.

I. 01/23 18:25:09. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 0 Inserting 16050 Recs, 5 Secs.

I. 01/23 18:25:12. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 4 Inserting 16380 Recs, 24 Secs.

I. 01/23 18:25:13. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 7 Inserting 16395 Recs, 47 Secs.

I. 01/23 18:25:13. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 6 Inserting 16380 Recs, 25 Secs.

I. 01/23 18:25:13. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 2 Inserting 16380 Recs, 22 Secs.

I. 01/23 18:25:14. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 1 Inserting 16380 Recs, 26 Secs.

I. 01/23 18:25:14. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 5 Inserting 16380 Recs, 23 Secs.

I. 01/23 18:25:14. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 4 Inserting 16370 Recs, 83 Secs.

I. 01/23 18:25:14. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 7 Inserting 16030 Recs, 21 Secs.

I. 01/23 18:25:14. 0000025215 DBA.fact.fact_dim_config_qualifiedifname_HG Sort Insert Statistics: 120 pages over 1 run(s) (Min: 120 Max: 120 Avg: 120) from 1 inserter(s).

I. 01/23 18:25:15. 0000025215 [20024]: Index DBA.fact.fact_dim_time_datetime_min_HG: Thread 1 Inserting 98210 Recs, 0 Secs.

I. 01/23 18:25:15. 0000025215 [20024]: Index DBA.fact.fact_dim_time_datetime_min_HG: Thread 4 Inserting 98210 Recs, 0 Secs.

I. 01/23 18:25:15. 0000025215 [20024]: Index DBA.fact.fact_dim_time_datetime_min_HG: Thread 3 Inserting 98210 Recs, 0 Secs.

I. 01/23 18:25:15. 0000025215 [20024]: Index DBA.fact.fact_dim_time_datetime_min_HG: Thread 5 Inserting 98210 Recs, 0 Secs.

I. 01/23 18:25:15. 0000025215 [20024]: Index DBA.fact.fact_dim_time_datetime_min_HG: Thread 2 Inserting 98210 Recs, 0 Secs.

I. 01/23 18:25:15. 0000025215 DBA.fact.fact_dim_time_datetime_min_HG Sort Insert Statistics: 30 pages over 1 run(s) (Min: 30 Max: 30 Avg: 30) from 1 inserter(s).

I. 01/23 18:25:18. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 2 Inserting 16380 Recs, 41 Secs.

I. 01/23 18:25:19. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 5 Inserting 16390 Recs, 41 Secs.

I. 01/23 18:25:26. 0000025221 Cmt 85152

I. 01/23 18:25:26. 0000025221 PostCmt 0

I. 01/23 18:25:32. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 1 Inserting 16400 Recs, 55 Secs.

I. 01/23 18:25:32. 0000025215 DBA.fact.fact_dim_config_dev_name_HG Sort Insert Statistics: 90 pages over 1 run(s) (Min: 90 Max: 90 Avg: 90) from 1 inserter(s).

I. 01/23 18:25:32. 0000025215 [20895]: Insert Pass 2 completed in 105 seconds.

I. 01/23 18:25:32. 0000025215 [20896]: Insert for 'fact' completed in 114 seconds. 491050 rows inserted.

I. 01/23 18:25:40. 0000025215 Cmt 85153

I. 01/23 18:25:40. 0000025215 PostCmt 0

I. 01/23 18:25:41. 0000025215 Cmt 85155

I. 01/23 18:25:41. 0000025215 PostCmt 0

I. 01/23 18:25:41. 0000025215 Cmt 85157

I. 01/23 18:25:41. 0000025215 PostCmt 0

I. 01/23 18:25:41. 0000025215 Cmt 85159

I. 01/23 18:25:41. 0000025215 PostCmt 0

I. 01/23 18:25:46. 0000025222 Cmt 85161

I. 01/23 18:25:46. 0000025222 PostCmt 0

565290 Carriage return introduced into output header of select statement from view.
565410 IQ 12.7 aggressively resets partition striping to mitigate

freelist fragmentation that was seen in 12.6. When running

workloads with a high number of truncates and deletes, this

aggressive reclamation caused more time to be spent in

searching for free space.

565509 Recovery was failing due to the failing permission checks at the time of startup. Since the statement got executed successfully these checks are not required at the time of recovery.
566175 We was getting server failure while doing "ReEstimateWithinPushDownSubTrees " operation for the unflattened views, derived tables . Now Problem is resolved.
566188 IQ server fails with the bufman error followed by stacktrace when a query containing load and dropping table executed. The valid lbn checks are added in the IQ code to understand the reason of the server failure, if customer gets any in the future.
566205 Under certain circumstances the join optimizer incorrectly rejected the pushdown join

algorithm. It also refused to honor a join preference from the user requesting the use

of a pushdown join in such cases. This has been fixed.

566324 Some ASA modules are not attached to IQ. (PHP Module, Perl Module) However, only an ASA 9 programmer guide is attached to IQ. A customer cannot know why these modules are not attached to IQ.
566382 It was possible for the server to enter a loop while processing some statements that included an implicit or explicit use of the table SYS.DUMMY. This has been fixed.
566457 iqunload would fail on windows if a directory name begins with \n.
566634 Would like the ability to define an alias and/or synonym for a table name so that users don't have to fully qualify (specify the owner.tablename) when another user other than owners the object.
566696 For a join index,

- inserting into, or deleting from, or truncating the top table, or

- inserting into, or deleting from, or truncating the non-top table, and then

synchronizing the join index

may lead to incorrect results for subsequent queries using the join index.

This has been fixed.

567076 Some queries that execute successfully in 12.7 ESD #5 and

earlier versions failed in 12.7 ESD #6 at opt_Select.cxx:1996.

567159 A new option has been added to allow the maximum number of unique keys for a LF index to be configured. The LF index previously had a fixed limit of 10000 keys.

LF_Max_Unique_Values

Default: 10000

Min: 1

Max: 200000

567172 If an application connects via Open Client, and if that application is using a newer version of Open Client 15, canceling a request may give a protocol error on the next request to the server. This problem has now been fixed.
567188 In the 15.0 Sybase IQ Quick Start, the @ sign was omitted before the configuration filename in step 4 of "Creating and using an IQ demo database." The error is corrected and an updated version of the Sybase IQ Quick Start is available on the Sybase Product Manuals web site.
567502 A product name when checkout of a license fails is not "Sybase IQ".
567555 The group_member() function caused the IQ server to fail

with Assertion 101506, if the user in question belonged to a

large number of groups.

567582 ABORT from s_bufman::Rollback while running stored-procedure/batch if db goes out of temp space during drop temp table on end/close batch.
567595 Running sp_iqrebuildindex on an SA type index now reports

new error code -1009416, rather than an internal error.

568066 The coordinator will not start on the wrong host when the -iqmpx_ov 1 switch is used to start the server.
568222 Server side bulk loader already supports named pipes. Extended this support in client-side bulk loader as well.
568306 A server failure may occur at hos_mutex.cxx line 813. While this failure should not occur under normal conditions, this error has been changed to an error that will not cause the server to fail and stop. If the error occurs, diagnostic information will be output to the iqmsg file that should be sent to sent to Sybase Support. This failure has occurred on HP and Linux platforms.

The error has been found and fixed per CR #461826

568446 IFIX IZ16878 from IBM is needed to install in graphical mode on AIX 6.1.
568620 A stored procedure consisting of a declare local temporary

table with a SELECT of the same local temporary table

disappeared after a server sync.

568799 The IQ server may hang when the main or temporary cache is severely stressed

and the emergency buffer pool is involved. This is a duplicate of CR 273582

and has been fixed.

568830 The output of the Join Node of the query containing outer

join and large nested CASE statements was blank. Now the

output of the Join node contains the required entry.

569115 This is an AIX only problem.

Adding a file to a tempdb on a secondary node failed if the user wanted to store the raw partition on a secondary node.

569129 Attempting to return a result set from within a BEGIN

ATOMIC block leaked server memory. Note that returning

a result set from an atomic block is not allowed and an

error is issued in this case; this behavior has not

changed.

569472 Corrected back-end query used in SCJ for retrieving User related information from server.
569729 The server failed whenever a table with foreign keys was

dropped and the FORCE_DROP option was set.

570077 Query -- Server failed while a running query was interrupted.
570125 Using an aggregate function with the PRINT statement sometimes

caused a server failure.

570151 When creating a table with an identity column, the IQ server

became unresponsive waiting on the GetIdentityEnforceUniqueness

call.

570275 Some queries with incorrect syntax like

<TableName>.<ColumnName>.substring(1,4) caused a server

failure. An error message is now returned.

570417 A bitwise operation with one of the operands having scaled data type throws a conversion error. This behavior has now changed to do automatic data type conversion so that the bitwise operation succeeds.
570489 "Select" button in "Dbspace File Wizard" was provided to add multiple files in DBSpace, but it also required edit operation to give details. "Add" button is more handy for the same purpose. Hence "Select" button is removed from the wizard.
570732 When FORCE_NO_SCROLL_CURSOR is 'On' there is constant growth in Dynamic Memory used by IQ, this is due to holding data type info even after the cursor is destroyed. This problem has been fixed now.
570735 This is raised for a minor messaging error.

If you try to execute a non existant stored procedure you correctly get this error.....

Msg 504, Level 11, State 0:

ASA Error -265: Procedure 'xxxxx' not found

If you try execute the non existant procedure but this time give it a parameter you should expect to just get the same error message say the procedure does not exist. However you get the following error instead....

Msg 201, Level 16, State 0:

ASA Error -615: Parameter '' not found in procedure '???'

This is misleading as it implies the procedure is OK but the parameter is incorrect.

571223 customer is trying to redirect query output to a file using set option Temp_Extract_Name1 and have control of the file permissions used to create the resultant file. They have been trying to do thuis with umask as per documented in CR 570627.

As per the resolution in CR 570627.... IQ is coded to create the extract output files with permissions rw-r--r--. umask acts on the permissions as follows:

When a file is created, its permissions are set to what the creating program asks for minus what the umask setting forbids. So, the bottom line is that umask can't add any permissions that the creating program hasn't given.

We need a FR that allow control.

571471 Table partitioning functionality is not available without license. IQ_VLDBMGMT license is required to create partitions in table.
571589 Client Side Plan will available for UPDATE/DELETE/INSERT SELECT/SELECT INTO also, when QUERY_PLAN_TEXT_CACHING = 慜FF�.
571720 The _jvmIQ directory (used for uninstalling IQ15.x) is missing if IQ15.1 is installed after installing other Sybase products. This has been fixed.
571749 The IQ Plugin was not being registered if IQ15 was installed if there was an existing SySAM install on the machine. This has been fixed.
571954 An IQ query node can fail in different ways:

1. Fail with a signal 11. The IQ server continues to run.

Only an incomplete stacktrace is generated.

2. Fail with signal 5 or 11. This may be followed by a message

"Memory corruption detected", another signal 11 (in which case the server continues to

run with no complete stacktrace generated), or by multiple signal 5's (in which case the

server fails with a full stacktrace generated).

This has been fixed.

572341 IQ 12.7

AIX -

Feature request -

When starting up the dbremote via SCJ, allow to user define an unique dbremote log file name to be used in all startup times, instead of to rename the Dbremote log file name using the string like this :

engine_name.xxx.dblog

where xxx is incremented each time that DBremote is started .

When starting dbremote via script, the unique dbremote log file name is defined used -o switch .

572524 Installing Sybase IQ 15.0 ESD #1 over Sybase IQ 15.0 GA gives an waring message about overwriting newer version of scvwen600.jar. This warning should be ignored and newer one overwritten
572540 The problem encountered is due to a one time cost

when a table, that existed in 12.6, is opened for the first time in 12.7.

A feature was added to 12.7 to construct a null bitmap on each

nullable column defined on the table. This bitmap is constructed

when the table is opened readwrite for the first time on 12.7 after

the upgrade has been done. Subsequent readwrite operations on the table

will not incur this cost.

The cost is a function of the number of NULL and non-NULL cells

on a given column in conjunction with the number of rows in the table.

This null bitmap was added, to address performance issues,

to greatly improve query performance when a query needed

to take into account NULL values.

572640 Creating tables with the same name and same column names, but

in different case, was allowed after the server was restarted

in CASE RESPECT database.

572648 The maximum value supported in SQL Anywhere for the numeric

function is 255. If the precision of the numeric function exceeds the maximum

value supported in SQL Anywhere, the following error occurs: "The result

datatype for function '_funcname' exceeds the maximum supported numeric

precision of 255. Please set the proper value for precision in numeric function,

'location'"

572733 Request to change the SQL_SEARCH_PATTERN_ESCAPE to backslash.
573449 Please be aware that a minor inconsistency has been introduced into the IQ

15.0.0 ESD#1 version string. This release will incorrectly report its

version as 15.0.1 ESD#1. This issue has no effect on the functioning of the

software.

573637 The maximum allowable length of a binary argument to a UDF has been increased from 256 bytes to 32KB.
573995 Third argument to LOCATE() function can be CAST to larger than BIGINT.
574043 The Tables/Indexes tab of each Dbspace were not being populated in the view panel. This has been corrected.
574057 When 'sa dummy' was used in a particular query instead of

IQ dummy, the server failed. An appropriate NULL check was

added in the function to avoid a server failure.

574699 A stored procedure with the following loop may result in incorrect data written to the table:

loop

savepoint;

fetch next from cursor;

update table where current of cursor;

end loop

574927 In certain cases where nested functions were used in negated

predicates, query performance degraded when using 12.7

instead of 12.6.

574933 The FORWARD TO statement could have truncated the forwarded statements to roughly a database page size in length. This has been fixed.
574976 Feature request for load balancing where user can automatically login to predefined group of query engines.
575036 When many index statements are executed on the IQ writer server, there are hundreds of versions sent to IQ reader servers. On the IQ reader servers, when lots of versions are coming in and there are users connected to it, the IQ reader servers need more memory than the IQ writer servers to manage those versions.

Even when there are no users connected to the IQ reader servers, there are internal event connections happening. To verify this, disable ev_iqmpxq2w on the IQ reader servers and ensure there are no user connections. Run the ddl on IQ writer server and observe the IQ reader server is consuming same memory as the IQ writer.

Once the TLV replay is completed, the IQ reader server releases the extra memory that it consumes while managing the versions. However, on UNIX, that memory is never returned to the operating system. Once memory is allocated for a process, the process retains that memory until the operating system is restarted.

To avoid having the memory consumed and not released, the indexes must be grouped in BEGIN PARALLEL IQ and END PARALLEL IQ. See "The CREATE INDEX statement" in Chapter 6, "Using Sybase IQ Indexes" in System Administration Guide: Volume 1 and "BEGIN PARALLEL IQ ... END PARALLEL IQ statment" in Chapter 1 "SQL Statements" in Reference: Statements and Options.

575104 The issue is fixed for IQ 15.0 GA and above. For IQ 12.7, use this workaround:

cast the select list as appropriate. For instance, in the following case:

create table test (c1 decimal(15,2), c2 decimal(18,2));

select abs(c1) + c1 + c1 + c2 into #tmp from test;

change the select statement to

select cast((abs(c1) + c1 + c1 + c2) as decimal(15,2)) into #tmp from test;

575686 Need to document row-by-row update in long transaction can use up a lot of main dbspace.
575773 Request to document Check_Alias_Enabled option.
575896 If an application executed a remote query containing many

tables, and if the query contained many tables, then there

was a chance the server would give assertion 101508, instead

of giving the "syntactic limit exceeded" error.

576902 Performance degrades when predicates containing complex

expressions are used in 12.7 code. To get better

performance for queries containing complex expressions in

predicates, set following internal option: set

[temporary] option dml_options6 = 32768 Note: Some queries

might show performance degradation after setting this

option. This option should be set to get better

performance for queries which do not show better

performance by default.

576907 Request a procedure that list defaults & current IQ startup configuration parameters.
577098 In exceptionally rare circumstances, the engine failed

while rewriting a very large and complex SELECT statement.

This happened if the engine was close to running out of

stack size or was low on cache size. The problem occurred

with queries containing UNION, EXCEPT, INTERSECT, or deeply

nested sub-selects. The engine now returns the error "-890:

Statement size or complexity exceeds server limits."

577112 The failure was caused by a bug in the error handling during TLV replay. This has been fixed.
577313 *** Tuesday, September 22, 2009 2:36:35 PM *** agarwala ***

LOAD aborts the engine during 2 to 3 byte FP rollover while destroying a locked buffer.

577383 Running a query with recursive cases resulted in an

unresponsive server. Now an error is reported.

577733 Provide "all" syntax for sp_iqrebuildindex.
577889 Feature request for IQ ODBC driver to support TDS protocol.
578116 The "Sybase IQ binary load format" section in Chapter 3 of the Building Blocks Reference Manual has incorrect information. There is a formula that reads

For a given year, month, and day:

year = current_year - 1;

days_in_year_0000 = 366;

binaryDateValue = (year * 365)

+ (year / 4)

- (year / 100)

+ (year / 400)

days_in_year_0000

day_of_current_year

-1;

It should read

For a given year, month, and day:

year = current_year - 1;

days_in_year_0000 = 366;

binaryDateValue = (year * 365)

+ (year / 4)

- (year / 100)

+ (year / 400)

+ days_in_year_0000

+ day_of_current_year

-1;

578390 When index advisor is turned on, the IQ server may crash. This problem is now resolved.
578793 Joining an SA stored procedure and an IQ table in a CASE statement condition will cause the server to crash. This is a known issue that has been fixed in version 15.0 and later. Expressions of the form:

create table t1(num as integer, name as varchar(30))

...

case

when (select count(*) from sa_conn_properties(),t1) > 1

then ...

else ...

end case

...

Will cause the server to crash. To prevent the crash, declare t1 IN SYSTEM or execute the predicate query outside the case statement and assign it to a variable, then use the variable in the case predicate.

578804 The IQ 12.7 Network Client for Linux 32-bit file Linux-iq1270_client.tgz you download from the EBF's section in http://downloads.sybase.com (release date 21 Nov 2008) is corrupt / problematic.

If you download thuis file and use tar -xzvf to unzip it, then run sybinstall. The jConnect 6.0 part throws tar an gzip erros (see below). The sybiqntwkclnt127lin.tgz file from SPDC download site for the same software is fine and works OK.

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

Installing jConnect 6.0

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

jConnect-6_0/

jConnect-6_0/index.html

jConnect-6_0/netimpct.gif

jConnect-6_0/version.txt

jConnect-6_0/tools/

jConnect-6_0/tools/decode-tli

jConnect-6_0/sp/

jConnect-6_0/sp/sql_asa.sql

jConnect-6_0/sp/sql_server.sql

jConnect-6_0/sp/sql_server12.5.sql

jConnect-6_0/sp/sql_server12.sql

tar: Skipping to next header

tar: Archive contains obsolescent base-64 headers

gzip: stdin: invalid compressed data--crc error

gzip: stdin: invalid compressed data--length error

tar: Error exit delayed from previous errors

Install failed for the following reasons

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

Copying of jConnect 6.0 failed

tar: Skipping to next header

tar: Archive contains obsolescent base-64 headers

gzip: stdin: invalid compressed data--crc error

gzip: stdin: invalid compressed data--length error

tar: Error exit delayed from previous errors

578993 LOAD aborts the engine during 2 to 3 byte FP rollover while destroying a locked buffer.
579036 Backup/Restore : Restore failed while trying to restore a backup taken on 12.6 release to 12.7. This was an issue with the dbspace size reported on 12.6 vs 12.7.
579409 An unnecessary emergency shutdown for unresolved dynamic

collisions occurred in some situations.

580065 If an application executed a remote query that involved the

use of ROWID, and if the table specified to ROWID was a

remote table, and if the query was processed in partial

passthru, then there was a chance the server would fail.

580527 New code now ensures a Chinese locale will only show localized resources in the zh_CN locale - otherwise it shows English. sybasecentral600.jar and jsyblib600.jar were updated.
580578 In some situation , when Query contain case expression with having clause so we was getting Internal error at dfo.cxx (Can not evaluate expression) .The Problem is now fixed .
580742 The MINIMIZE_STORAGE database option that is set to ON or

OFF prior to the creation of a table sometimes affected the

result of calculations involving the numeric columns of the

table.

580808 The engine may incorrectly rewrite the WHERE, ON, or HAVING clause and return no or too

few rows. This happens if the engine has found redundant conjuncts and try to remote it.

An example of this is the query

select 1 from T

where a = 1 and ( b = 2 or c = 8 ) and ( d = 4 or e = 10 ) and ( a = 1 or e = 7 or c = 9 )

This has been fixed.

581012 Insert .. select may not be parallelized in 15.1 and result in performance degradation from 12.7. To force parallel insert - select, set option DML_Options8=65536. This option should be used only when the table does not have any join indexes.
581158 A Japanese message is not included in DBISQL attached to IQ15.
582105 While running a query involving a large number of UNION ALL,

the server became unresponsive after detecting a stack

overflow.

582634 Request a way to determine global temporary table connection usage.
582732 The group_member() function causes the IQ server to crash with Assertion 109506 ("Allocation size too large when re-allocating memory") if the user in question belongs

to a large number of groups. This has been fixed.

583190 Server files that support "Java in the database" in 12.7

are no longer released with any ESD beyond ESD #8. Customers

who did not install 12.7 ESD #8 will be required to install

ESD #8 to update to the latest supported version, before

any newer update can be applied.

583233 While loading into a LOB or a CLOB column with LOAD_MEMORY_MB = 0, the server requests for a large amount of memory. This could lead to the query to fail on some platforms. This has been fixed.
583724 Request to document the preceding database options.
583821 A query with a SELECT TOP N ROWID clause would execute much slower with descending sort order compared to ascending. This is now fixed and performance of queries with Order By rowid desc would improve as a full table sort is avoided.
584121 On some Windows hosts, converting a single node IQ server to a multiplex using Sybase

Central may fail with an error about the path to the shared IQ store not existing on

the secondary node, if the path to the database file (the .db file) contains Chinese

or Japanese characters. There are two workarounds:

1. Restart the Syabse IQ Agent service using the user account that was used to log

on to the IQ server host. In the list of services, right click Sybase IQ Agent

15.1 -> Properties -> the "Log On" tab -> This account, and enter the user account

id, the password, confirm the password, and click the OK button. Click the OK button

if a box pops up with the message "The new logon name will not take effect until you

stop and restart the service", and then restart the service by right clicking Sybase IQ

Agent 15.1 in the service list and selecting Restart. Or if the service is not already

running, start it by right clicking Sybase IQ Agent 15.1 in the service list and

selecting Start.

Or

2. Stop the Sybase IQ Agent service and start the Sybase IQ Agent as an application:

In a command window:

SybaseIQagent15.exe -r "SybaseIQAgent15"

584317 Request detail info on sp_iqlocklogin mechanism on MPX environment (12.7)
584334 Request to document the new procedure behavior in IQ 12.7/15.x
584796 Possible workarounds:

- run GUI install

- run standalone GUI install; setup from sysam-2_10 dir.

- run standalone Silent install from sysam-2_10 dir. (see the command below)

note: change the "$V(SybRoot_InstallLocation)" below to be the path to the root of the install location (ie. $SYBASE), and change "suite_sysam_sysam_server.active=true" value to be true or false depending if you want to install the sysam server or not and change "suite_sysam_sysam_util.active=true" value to be true or false depending if you want to install the sysam utilities or not

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

./setup -silent -W SybaseLicense.agreeToLicense=true -W setupTypes.selectedSetupTypeID= -P suite_sysam_product_root.active=true -P installLocation=$V(SybRoot_InstallLocation) -P suite_sysam_sysam_server.active=true -P suite_sysam_sysam_util.active=true

585094 IQ15.1 cannot allocate the memory of the class defined by UDF.
586168 Loading more than 2^32 records of the same value in a column can lead to data inconsistency in its enumerated FP index, leading to the server failure on accessing the data in the column. This has now been fixed.
586398 When a user was unlocked for each nodes in the MPX, the command "sp_iqlocklogin username,lock" will silently failed. Customer would like to request a feature to raise a message for this command to indicate that user need to use 'all server' to lock the user.
587239 An update statement issued against a partitioned table could cause a server abort in some cases. This is now fixed.
587376 On HP-UX platform, on trying to destroy a mutex, the OS returns EBUSY and EINVAL signals. In 12.7 ESD 6.3 and 12.7 ESD7, a change was made to make this throw as non-fatal. This led to a server failure. This has been fixed. We no longer throw an error on seeing EBUSY or EINVAL signals on HP and Linux platforms.
588089 This is a test of the Customer Description for IQ EBF generation
588091 Set temporary option dml_options6=32768 added to fix performance issue (CR 576902) gives division by zero error. (-- (dfe_ArithmeticExpression.cxx 372)

In IQ 12.5 and 12.6, conditions involving a simple functional or arithmetic

expression over a single column could be evaluated using a scan of

the FP index. For example, the condition "SQRT(T.X) > 10" could be

evaluated in this manner.

In IQ 12.7 the optimizer and query run-time system were enhanced to

enable any arbitrarily complex condition over a single column, such as

"SQRT(T.X) > (10 + (100 * LN(T.X)))" to be evaluated in the

same manner.

In the vast majority of queries, evaluation of complex conditions using

this optimization results in improved overall query performance. However,

as with most optimizations, there are rare exceptions. This change

provides a mechanism that allows an IQ server to revert its behavior for

this optimization back to applying only to the simpler conditions supported

in IQ 12.6.

588210 TCP listener shut down because of errno 130 which is ECONNABORTED (Software caused connection abort - A connection abort was caused internal to your host machine.). The TCP listener has accepted a connection but the other side has already gone. This problem has been fixed and Listener thread now will ignore this error.
588519 On Solaris, running a query as simple as "select @@version" against a remote server may result in the message "External environment could not be started". This has been fixed for Sun Solaris 10.
588869 If the property email.smtp.host is set in the license (.lmp) file, secondary nodes may crash after a synch. To work around this issue manually edit this file and put the host name in quotes.
589023 LOAD TABLE statements resembling the following statement:

load table (f1 prefix 1, f2 binary with null byte,

f3 binary with null byte) from 'test-iq.001'

format binary quotes off;

are not prohibited by the syntax and may load misaligned data to the table.

589239 LIKE clause: document supported patterns of length between 127 and 254 chars
589290 LIKE clause: support patterns of length of 254 chars
589643 Customer wishes to have two separate schemas, one as "staging" for intial

testing of data, which could them be made "live" by simply changing the owner.

589727 The issue is closed as not a bug, since we donot support heterogeneous charset environment in localization release
589813 stored proc (on 12.7 ESD 5.8)which has code for exception handler, Raiserrror doesn't raise user defined error message instead msg 0 is raised when on_tsql_error is set to 'stop' or 'conditional' . Behavior is same on both 12.7 ESD7 and 15.1
590199 IQ should check and validate each dbspace as it opens them when booting IQ server to verify that they are valid dbspaces for this IQ server and if there is an issue, then explanatory message should be logged in the iqmsg and srvlog. For example, verify all dbspaces when opening database by running 'iqheader' utility on them in the background.
590373 (f_agg_InterfaceMetrics2.Node Family = 'Cisco 2800 Series Routers') clause is raising

"I. 09/11 08:47:35. 0000000171 O/S Err#: 0, ErrID: 9216 (df_Exception); SQLCode: -1009113, SQLState: 'QSB13', Severity: 14

I. 09/11 08:47:35. 0000000171 [20134]: Secondary error noted"

"secondary error noted" message text has been clarified.

590388 Dynamic Collision: Server crash after it failed to drop connection 16 times.

I. 09/09 16:36:31. MPX dynamic collision on dbo.billed_roc -- connection 16975

I. 09/09 16:36:31. User "dbo" dropped connection 16975 ("vkatya")

I. 09/09 16:36:32. -- dropped 1 of 2 connection(s) for table: dbo.billed_roc -- but 1 connection(s) are still holding a lock

I. 09/09 16:36:32. -- Too many retries on dropping user connections. Server is shutting down.

590578 Query with join between sp_iqmpxincheartbeatinfo, sp_iqmpxincconnpoolinfo and sysiqmpxserver crashed coordinator node. This has been fixed.
590621 Inserting the @@identity value into an IQ base or temporary table causes the server to

crash. This has been fixed.

590781 dbisql ignores SQLCONNNECT environment variable setting, while other utilities e.g dbisqlc , dbvalid and dbinfo works.
590928 Performance improvement for WD index for the 0 length, constant, unique data.
591507 Using Sybase Central to create a database may fail on Windows hosts with names using

certain Japanese characters. In this case, the Interactive SQL Classic (dbisqlc.exe) or

Interactive SQL Java (dbisql.exe) tool can be used instead to create the database. If

these tools are started in the command line and a connection string (-c "...") is

provided., ensure either to avoid using the links parameter, or if the links parameter

is provided, to use parentheses instead of curly braces around the host name and the port

number, e.g.,

Instead of

dbisql -c "uid=dba;pwd=sql;eng=mysrv;links=tcpip{host=<host name in Japanese>;port=8888}"

use either

dbisql -c "uid=dba;pwd=sql;eng=mysrv"

or

dbisql -c "uid=dba;pwd=sql;eng=mysrv;links=tcpip(host=<host name in Japanese>;port=8888)"

591514 while creating the database with collation 932JPN and having japanese characters in dbname, dbpath,iqpath or log file name path through interactive dbisql , you need to connect to utility db but not the iqdemo database . Since the server which is started with iqdemo database has different charset than OS charset.
591575 32 bit client cannot be installed with 64 bit IQ server on same window machine. IQ 15.1 doesn't raise error when 32 bit client is installed after installing 64 bit IQ Server, but uninstaller fails because it cannot load 32 bit dll.
591586 32 bit client cannot be installed with 64 bit IQ server on same window machine. IQ 15.1 doesn't raise error when 32 bit client is installed after installing 64 bit IQ Server, but uninstaller fails because it cannot load 32 bit dll.
592017 currently customer can only get client host ipaddress(NodeAddr) of users connected to IQ from sp_iqconnection and sa_conn_info(), due to auditing requirement for security purposes, customer want ipaddress of user connections along with connhandle to be logged in the iqmsg.
592288 Previously, if an application connected via jConnect or Open Client, and if the application subsequently called a stored procedure that had ON EXCEPTION RESUME defined, accessed a proxy table and had local variable names that began with @, then there was a chance the server would crash if the execution of the stored procedure generated an error. This problem has now been fixed.
593125 15.1 ESD1 on windows creates dbisql.ini.token which is a template file used by the installer to build the dbisql.ini file
593288 Server crashes when big string is attempted to be logged in .srvlog using "message" command
593353 10/01 17:53:06. 0000030825 Exception Thrown from df_Heap.cxx:3572, Err# 0, tid 585 origtid 585

I. 10/01 17:53:06. 0000030825 O/S Err#: 0, ErrID: 9216 (df_Exception); SQLCode: -1005028, SQLState: 'QTA28', Seve

rity: 14

I. 10/01 17:53:06. 0000030825 [21092]: Syntax error - RANK/DENSE_RANK/PERCENT_RANK/NTILE/CUME_DIST function ORDER BY

item must be expression over column.

-- (df_Heap.cxx 3572)

I. 10/01 17:53:06. 0000030825 Memory corruption detected

I. 10/01 17:53:06. 0000030825 Idx: 0 Addr: 0x2aaace5c2550 Size: 16 File: df_Heap.cxx Line: 3533

I. 10/01 17:53:06. 0000030825 Usertype: df_Heap::GenerateAggregate _fence bad

593431 A query with duplicate expressions in the select-list

may cause error "Cannot evaluate expression". For example,

SELECT r3.id, Col1 = r3.id

FROM DBA.fin_code r7 cross join DBA.customer r3

GROUP BY ROLLUP (r3.id )

593620 New LOAD TABLE syntax allows you to skip a number of

lines at the beginning of the file. For details on the

HEADER SKIP clause, see the Sybase IQ 15.2 Release

Bulletins.

593642 login trigger enhancement similar to ASE, where one develops a standard stored procedure and tells ASE to run it as a login trigger, such that it gets executed as the last thing in login processing, and there is no tricky process of inserting your logic in what is otherwise standard system behavior.
594278 There is no character set conversion performed on the server name. If the client character set and the database server character set are different, using extended characters in the server name can cause the server to not be found. If your clients and servers are running on different operating systems or locales, you should use 7-bit ASCII characters in the server name. See the following section in the SQL Anywhere documentation: "Connection strings and character sets" from

SQL Anywhere Server - Database Administration 粻Starting and Connecting to Your Database 粻The database server 粻Database server options 粻-n server option

The workaround is to enter other connection information but NOT the IQ server name.

594291 Fixed in CR 594295
594295 The HP compiler was generating pointer assignments as

multiple machine instructions, due to a compiler flag

+u4. This led to a race condition resulting in a server

failure. Sybase IQ now has double byte aligned structures

and has removed the use of +u4, so that the pointer

assignments are atomic. This modification prevents any

race condition on pointer assignment and failures due

to this race condition.

594307 A query with windowing function and order by desc on a column with constant expression crashes the server with "Memory corruption detected" error.

Example:

create table TestDensRank_desc(col1 int,col2 int, col3 int);

select

col1,

col2,

xyz=1,

max(col3),

day_order = dense_rank() over( order by col1,col2, xyz desc )

from TestDensRank_desc

group by

col1,

col2;

594329 Update fails with "Bitmap failed internal checks" on IQ 15.1.
594335 NFR: Enhance internal bitmap error to provide index name.
594473 ASA has introduced a check to see if the maximum number of allowed nulls has been exceeded. This will fix the problem mentioned in the CR.
594477 Msg 21, Level 14, State 0:

SQL Anywhere Error -1003002: CtLibrary Error: 44, Severity: 0, Origin: 1, Layer:

4

Error Message: ct_connect(): protocol specific layer: external error: The

attempt to connect to the server failed.

OS Error: 0, OS Message: ---.

--

(hqm_con

(0 rows affected)

594512 On change of one of the original install directories, and run of dbisql below get errors.

dbisql -c "dsn=Rey" -nogui

Could not connect to the database.

Data source name not found, and no default driver specified

SQLCODE=0, ODBC 3 State="IM002"

594901 Add to IQ Doc the dbfiles max number and the size limits.
594903 Request to certified IQ on SUSE 11 version.
595216 DBISQL for UNIX does not add "CS=utf8" at the time of the 2nd connection.When you use DBISQL for UNIX, please add "CS=utf8" to a connection strings clearly. DBISQL may fail in translation of data, when not using UTF8.
595252 Sybase Central, is not properly evaluating directory names containing multibyte characters. Sybase IQ must be installed in a directory path containing only 7-bit characters.
595311 The error message is changed from "Internal programming error" to "Host variable '@varname' is not initialized" in df_Heap.cxx.
595315 IF/CASE statement caused IQ server failure when both sides of the expression used IQ tables on IQ15.x release.
595383 The Sybase IQ Agent on Windows, is not properly evaluating directory names containing multibyte characters. On Windows, Sybase IQ must be installed in a directory path containing only 7-bit characters.
595873 Server crash with Assertion failed error "Table lock inconsistency" on IQ 15.x/
595881 In some situations when' starting IQ server with chinese server name it might crash. Use of double quotes with server name solves the problem.

e.g. Instead of

start_iq -n <chinese_server_name>

please use:

start_iq -n "<chinese_server_name>"

595888 IQ 15.1: Query resulted in server failure with "Destroying logical locked buffer".
595990 Provide better diagnostics instead of "NO COMMAND OR CURSOR ACTIVE" in the stacktrace.
596186 Request certification of IQ 12.7 & IQ 15.1 on Red Hat Enterprise Linux 5.4
596192 Request to implement temp store resources management feature similar to ASE tempdbs feature.
596648 In 12.7 only Single Quote, Double Quote, Blank and Semicolon could not be used for passwords.

In IQ 15.x

sp_iqpassword and Alter User / Create User can not contain the following chars for the password additional to the ones of 12.7.

And the Password can not start with a numeric Character.

Words used as reserved words, like "select" or "as" neither can be used any more.

IQ Database was setup with Charset 1252

can be used:

char ASCII

# 35

$ 36

0 ... 9 if it is not first character

@ 64

A 65

....

Z 90

_ 95

a 97

....

z 122

€ 128

� 140

...

higher then ASCII 140 some chars can be used some not.

605035 A server failure may occur on rare occasions after opening a cursor on an empty local temporary table in a stored procedure. This has been fixed.
605246 iqunload fail with below error when -o logging switch used with START= connection on IQ 15.x

Sybase IQ Unload Utility Version 15.1.0.5034

Connecting and initializing

***** SQL error: Invalid database server command line

605272 LOAD TABLE may stop processing when an error condition occurs during the

load.

The problem can happen with partitioned or non-partitioned

tables and variable or fixed width loads.

605407 Predicate range simplifications have been expanded to be more aggressively simplify range predicates. This enhances performance in many cases.
605410 If a user did not have ALL privileges (select, insert,

alter, update, delete, references) on a table, loading

a table resulted in the error "Permission denied: you

do not have permission to select from "<table_name>"

SQLCODE=-121, ODBC 3 State="42000". The correct behavior

requires only select, insert, and alter permissions to

perform a load.

605438 The 12.7 ODBC driver(32 bit) on Sun OS had a dependency on libC.so.5. This library is not ANSI compliant and hence was causing application failure at customer end. The dependency has been removed.
605523 Sybase IQ will output SQL of the client connected via iAnywhere JDBC using a client character set. It differs from character collation of DB.
606047 Documentation: Update/Delete not allowed when SA functions used on IQ table
606207 Sybase central crashes when we try to add a primary key to a table which does not have one.

This has been fixed.

606223 Data inconsistencies in a fixed-length High_Group (HG) index may occur during heavy LOAD or DELETE activity. These inconsistencies can cause the server to fail, requiring that the HG index be rebuilt.
606253 - sp_iqindexsize has a parameter size of 128chars and therefore cannot accept indexnames > 128.

However, the input parameter for sp_iqindexsize can easily exceed 128 and cause procedure to fail.

Here is a real life example, of proc failing:

sp_iqindexsize('price.StressPrices_prices_Clone0_46668739_nyrmdla205_ny_fw_gs_com_574_20091030.[i_StressPrices_prices_Clone0_46668739_nyrmdla205_ny_fw_gs_com_574_20091030_3_HG]')

606494 Feature request to allow update on a view with UNION ALL on IQ.
606813 Although UserID and password are defined in file dsn, but sybase central doesn't recognize that, connection fails with :

[Sybase][ODBC Driver][SQL Anywhere]Invalid user ID or password

Error code=-103

SQL state=28000

607029 SSIS sending data over to the IQ OLEDB driver may give the error:

Msg 7343, Level 16, State 2, Line 1

The OLE DB provider "SAOLEDB.11" for linked server "SYB_IQ" could not INSERT INTO table "[SYB_IQ]..[DBA].[emp1]".

607041 Multiplex -- A server in a multiplex can become unresponsive involving calling the

sp_iqconnection stored procedure. This has been fixed.

607060 Deleting rows from a table which has a multi-column HG index defined may cause the

server to abort. This has been fixed.

607152 If RANK() function has more than one column in PARTITION BY clause, an exception is thrown from df_MapRecordToDFEs::InitAddDFE.
607233 In some cases where a host variable is assigned to a long varbinary or long varchar, IQ may return an incorrect value.
607427 Msg 262, Level 16, State 0: SQL Anywhere Error -121: Permission denied: you do not

have permission to grant permissions to "<username>".

Permission is denied trying to add a group member from a group login ID.

You can use Syntax 1 or 2 of the GRANT statement if at least one of these conditions

is met:

1. You are changing your own password using GRANT CONNECT

or

2. You have DBA authority

607560 When a customer generates the license files by SPDC, selecting a different lisence on IQ installer causes the down of an installer.
607862 Performance for queries with distinct and substring is not good, this is a FR to enhance the optimizer to make better choices when dealing with this sort of query using functions like this...

This is 127 ESD 7 on linux power pc 64 bits (but problem reproduceble on linux intel 64).

Take the example query " select distinct(substring (char_column,1,1)) from table1 " under following conditions:

- table1 has several million rows

- Column char_column has a low cardinality and an LF index.

IQ resolved the query applying substring function to all rows and then applying the distinct.

If it would resolve the query calculating the distinct using the index first and then applying substring

then the performance improves a lot. These are examples sent by customer:

select distinct(char_column) from table1 -> 0.063 (seconds LF index is used)

select distinct(substring (char_column,1,1)) from table1 -> 76 seconds (index is not used).

select substring (A,1,1) from ( select distinct(char_column) A from table1 ) t -> 0.063 seconds.

This has also been tried in 15.1 and in this case performance for second query improves a lot comparing to 12.7, as IQ 15.1 uses palalelism and performance is better but not as good and doing first the distinct and second the subsctring.

607869 Enhance dbisql in -nogui mode to provide ability to access historical commands. This is present in GUI mode

such as:

1. home <-, or End ->, up, down key

2. recognise some special key combo ( like ALT+< ) to go back to previous command

607889 A query with a large number of OR statements caused

an IQ server failure.

607963 dbisql should raise error message instead of quitting if symbolic link to jre142 directory is missing, and returning exit code 0(i.e success)
607967 Feature for adding a flag that DBAs can be set to disable grace licenses to prevent accidental use of features which are not licensed in Production
608113 The Sybase IQ server appeared to stop processing for a

period of time, when a long running connection was

disconnecting.

608228 This problem is resolved in OCS 15.0 ESD#23
608411 Please add ANSI SQL-99 select .. with recursive queries to IQ.
608483 Previously, if an Open Client or jConnect application attempted to prepare and execute a statement with a large number of parameters, then the server would either fail the request, or in rare cases, crash. This problem has now been fixed.
608611 Successful migration of a 12.7 database to 15.0, 15.0 ESD 1, 15.1 or 15.1 ESD 1 using the iqunload -au utility may result in migrated system tables containing incorrect data. This incorrect data can result in the inability to modify the schema or rows within the database. If this happens the server may return an internal system exception. The server will also permit you to update the primary key values involved in a referential relationship in a way that violates referential integrity (RI).
608612 When the network information on ODBC DSN is wrong(ex: host=xxxxx:2638), Cental/DBISQL may be unable to be connected to IQ via jConnect. Originally it will connect using Server Name of ODBC DSN.
609079 In order to compile on AIX 6.1 systems, the minimum level of the xlC compiler is 8.0.0.24. The latest updates for supported IBM C and C++ compilers are described here:

http://www-01.ibm.com/support/docview.wss?rs=32&uid=swg21110831

Downloaded and install "vacpp.80.aix53TL6-61.oct2009.ptf.ta" from here:

ftp://ftp.software.ibm.com/aix/products/ccpp/ptfs/vacpp.80.aix53TL6-61.oct2009.ptf.tar.Z

609124 When two IQ servers have started on the same host, dbisql started from Central may be connected to a different IQ server.
609252 INSERT-LOCATION toa numeric column may result in error:

Msg 21, Level 14, State 0:

SQL Anywhere Error -1006256: Invalid arithmetic construction (1)

--

(hos_numeric.cxx 6844)

The circumstances are as follows:

An IQ table is defined as "create table local_t1 ( c1 numeric(19,4) );"

A remote table is defined as "create table remote_t1 ( c1 numeric(19,4) );"

The statement producing the error:

"insert local_t1 location 'remote.db' { select sum(c1) from remote_t1 };"

The remote server will calculate the sum and likely require more storage than is needed for a numeric(19,4). This will cause a buffer in IQ to be written incorrectly.

Now that this correction has been made, a different error may be reported when a numeric data type cannot be converted to a numeric data type of a smaller size.

We may now report error: "SQLCODE -1001006, Conversion is not possible" instead of

"SQLCODE -1001010, Numeric value out of range".

609728 If a table has an identity/autoincrement column and you alter it to no longer be identity/autoincrement before migrating to 15.1, iqunload fails with a validation error.
609918 A performance improvement has been implemented for the

xp_cmdshell procedure on AIX and Linux platforms (already

implemented on Sun).

609935 Cache size growth was observed due to a bug in the handling of in-memory objects. The de-allocation was not done properly leading to cache growth. This has been fixed now.
610065 On UNIX, interrupting an external procedure call (for

example, by pressing CTRL-C in the console to which the

server is attached) sometimes caused a server failure.

611009 On the MPX coordinator, the following sequence of user actions leads to other nodes of

the MPX to crash:

1. dba creates a stored procedure or a table specifying dbo as the owner

2. dba drops the stored procedure or the table without specifying the owner

3. dba re-creates the stored procedure or the table as in step 1

This has been fixed.

611090 The screen of InstallShield is too long when EUC_JIS environment is used by AIX 6.1.
611539 When a query was having the order by rowid desc so we might have wrong result. Now this problem is fixed.
611560 Downloaded IQ 15.1 Enterprise edition for AIX 64 bit from SPDC. The GUI installer and the silent installer do not create bin folders in the SYSAM-2_0 directory.
611815 An IQ Multiplex Reader may crash while doing local TLV replay of create index statements within a begin and end parallel blocks. This has been fixed.
612007 Sybase IQ does not support raw access to a GPT disk. raw access to an MBR disk is possible for IQ.
613003 SELECT query with UNION ALL, ORDER BY DESC, TOP returned

an incorrect result.

613262 Executing a query like the following from SQL Server Management Studio (2005):

select * from saoledblink..SYS.syscollation;

would have failed with the error:

Msg 7356, Level 16, State 1, Line 1

The OLE DB provider "SAOLEDB.11" for linked server "saoledblink" supplied nconsistent metadata for a column. The column "collation_order" (compile-time ordinal 4) of object ""SYS"."syscollation"" was reported to have a "DBCOLUMNFLAGS_ISFIXEDLENGTH" of 0 at compile time and 16 at run time.

The problem occurred for BINARY(n) columns. The DBCOLUMNFLAGS_ISFIXEDLENGTH schema attribute was set true (0x10) at run time. This problem has been fixed.

613601 Multiplex: In Sybase IQ 15.0 and later versions, restore of

a multiplex coordinator requires the utility database to be

started with the same server name. This is a change in

behavior since 12.7 and was also a problem for users

attempting to restore, when the production server was running

using the coordinator server name.

613674 An uninitialized parameter leads to a generic non-fatal IQ internal error message.

This has been fixed. The message is now "Host variable 'xxx' is not initialized"

where xxx is the name of the uninitialized parameter.

613920 IQ/SA Utility cannot recognize the following AIX Japanese locales correct.

Ja_JP

Ja_JP.IBM-932

614055 IQ support for ISNUMERIC()
614148 Secondary nodes are shutting down because of a failure in propagating stored procedures from the coordinator to the secondary nodes. This will only happen when a stored procedure is recreated after being dropped and the stored procedure is not fully qualified. This has been fixed.
614301 Enhancement on sp_iqindexfragmentation.
614557 Core_options13 "PARAMID_COREOPTIONS13_TRACE_SORT_EXCEPTIONS" is added to print the diagnostic information, if needed, for insufficient buffers during sort.
614770 The server randomly becomes unresponsive. This can happen when the main cache and/or

the temporary cache is running low. Please contact Sybase Technical Support for

assistance, if this issue occurs.

614946 We have a sproc that opens a cursor on a table and we fetch each row of the cursor and

update one column of each row with the CURRENT OF clause.

All is fine.

But, in the cursor fetch loop, when we add a select count (*) from another table,

then IQ SILENTLY updates a column that is not specified in the update statement!

615244 Msg 11206 is raised for second subsequent selects after set rowcount nn from IQ proxy table in ASE using latest 15.x OCS
615402 Syntax error is raised with large Skip number which is greater than signed 32bit integer value.
615638 If the optimizer chose to use a push-down algorithm for

join, while executing a query with many predicates

between multiple tables, a non-fatal error sometimes

occurred.

615707 Using the C Unicode data type SQL_C_WCHAR and a buffer length greater than 16K may cause

the "IQ Internal error. Please report this to Sybase IQ support. -- (df_Heap.cxx 2695) "

error. This has been fixed.

615917 Improvements have been made to the query optimizer to improve optimization speed for queries containing deeply nested expressions.
616212 Utility to give information about memory usage, cpu consumed per connection
616343 When using a composite key and all the columns of the composite key are present in the join condition and one of the columns of the join condition is of different length (e.g in

this case numeric(2) and numeric(5)) a wrong result may occur in the case of HPD Join. This has been fixed.

616381 sa_validate will erroneously report missing index entries. For example:

Primary key for "ISYSIDX" has missing index entries

Foreign key "ISYSTAB" has missing index entries

Index name "index_name" has missing index entries

617560 Corrupted values may be returned to a caller for Multibyte CLOB values that span several database pages. Partial chars at the beginning and the end of a page is incorrectly handled in case of mulitbyte chars. This has been fixed.
617617 Request to improve handling error for inaccessible dbfile on the secondary server.
617710 The maximum of Number of tables per join index is 31.
618157 Remove the incorrect extra system call of getrusage which boost up query performance.
618632 Queries with a grouped leaf and conditions on the grouping column could

perform poorly in some cases.

618738 sp_iqcheckdb did not report an error, even if there was

a byte FP lookup table inconsistency error.

619114 If 'From' clause in a subselect section of a delete statement was missing then IQ Server was crashing with:

*** ERROR *** Assertion failed: 201501

Page 0x0:0x0 for requested record not a table page

UpdCur not updatable in IQ

Sample Statement (missing from clause in select statement in where section):

delete Contacts_new

where surname in ( select distinct surname Contacts

union

select distinct surname Contacts

)

Now the above kind of query will not lead to crash. If Contacts_new and Contacts will

1) IQ table- We will get the error "Update operation attempted on non-updatable remote query".

The able mentioned query , internally converted to the following

delete Contacts_new

where surname in ( select distinct surname Contacts

union

select distinct surname as Contacts from SYS.DUMMY

)

SYS.Dummy is the SA table thatswhy we will get this error.

2)SA table - All the rows of Contacts_new will be deleted or Contacts_new table will truncated. Because , Here column "surname" is not found in the subquery, then it will be search in the outer query block. Since table "Contacts_new" has a column "surname" it is a valid out reference and the WHERE clause is always true.

619211 Multiplex: A GRANT or REVOKE statement on an invalid view caused

a multiplex node failure at saint_iqthresholdddl.cxx:6232 with

the error "Unexpected error during commit."

619347 When the SKIP option is set to be load table, even if IQ finds the error included in a data file, it may not execute rollback. Therefore, IQ will insert the read data of a part in IQ.
619352 The guideline about the size of IQ_SYSTEM_MAIN currently written to the administrator guide is aimed at large-scale DB.
619358 INSERT LOCATION may truncate TEXT and IMAGE data from an

OpenServer application to 32k.

619361 A problem with virtual and incremental backups led to

large size backups of Sybase IQ 15.x databases, compared

to backups of 12.7 databases.

619601 Provide LDAP/UA, LDAP User Authentication, for IQ.
619628 Setting Compression option with invalid value 'OFF' causing MPX dbremote to fail.
619803 Feature Request for IQ to support GB18030 as storage format.
619804 Restriction of DB collation and OS locale must be in agreement. However, it is unknown whether this restriction is specification.
620097 If an application connected to IQ using Open Client 15.5 and attempted to fetch a time or timestamp value, then the fetch would fail with a TDS protocol error. This problem has now been fixed. Note that this problem does not affect versions of Open Client prior to 15.5.
620281 The Sybase IQ server sometimes failed during recovery, if

the server was restarted after it stopped for a disk-full

condition on the disk where the transaction log resided.

620444 Using DBISQL ->Tools ->PlanViewer may cause IQ Server to shut down immediately when temporary Tables are used and IQ Server memory is limited.
620458 A driven table that contains UNION ALL and NOT/ EXISTS correlated subqueries with

conjunctive condition cause the query to fail with non-fatal stack trace at

opt_TableNode.cxx.

620636 The sp_iqdbspaceinfo stored procedure returned incorrect

values for the DbspaceSize column, when dbspace sizes were

over 4GB.

621197 @@rowcount is not supported in a Sybase IQ database. However,

in versions 12.7 and 15.1, @@rowcount behaves as expected.

621247 Please see description for CR 594295
621461 A query with aggregate functions (for example, SUM and

AVG) with COALESCE(isnull, ifnull) returned NULL, when the

query optimizer chose parallel GBH.

621473 This problem is duplicate of the problem 620950/615638. while executing a query which had many predicates between multiple tables and when optimizer chooses to use a push-down algorithm for join, a non-fatal error occured. This problem has been fixed now.
621716 A timing sensitive deadlock could occur in the IQ main or

temp buffer cache, if all pages of the cache were locked or

dirty. This error was reported: "main Bufman: All buffer

cache pages are in use, ask your DBA to increase the size

of the buffer cache."

621836 A virtual restore failed with the error: "Msg 21, Level 14,

State 0: SQL Anywhere Error ~1006167: DateTime is invalid

(0)".

622519 NFR: A way to allow mapping all remote logins to one local name.
623179 The error "Non-Fatal IQ Internal Error Detected at

opt_Driver.cxx:5700" was reported by an IQ error checking

routine to ensure that the IQ server did not fail due to

invalid data structures. The routine checked whether a column

from a view or derived table was valid for a partitioned table

optimization, where IQ can treat the output of a UNION ALL

as a single table. The check was modified to permit the

valid query.

623313 NFR Please improve message by providing which value got truncated
623457 Multiplex: A view using a date order different than the

query server date_order did not propagate to the query

server. View creation now propagates to query nodes. After

creating a view using date/timestamp/datetime as filters,

set the date_order option on the query node to the same

value as the date_order option on the writer node to

perform a query on that view.

623511 The default value of Max_Warnings of Linux x86 -64 is too low. The default of this value should be 281479761065
623588 Feature Request: instead of 'NA',sp_iqdbspace run on secondary node should display a warning message.
623701 An IN predicate based query returned an exception from

s_bm.cxx:2807 and the error "O/S Err#: 0, ErrID: 2049

(sbm_exception); SQLCode: -1009045, SQLState: 'QSA45',

Severity: 14 Bitmap failed internal checks. You may have

a damaged index. Please check your IQ message file for

additional information." and rolled back.

623706 ISNULL() is not estimated correctly in an IF statement.
624191 A query that fetched rows in descending order by rowid,

for example, ORDER BY ROWID(table) DESC, returned

incorrect results.

624200 Request the audit text format from the translated transaction log file.
624398 IQ 15.1 ADO.NET policy file not reflecting 15.0 version of provider in bindingRedirect
624551 hextoint() function with a value greater that 8 bytes may

have caused a server failure with inconsistent memory

detected.

624645 DOC: Add example on how to use connection string with ADO.NET.
624968 Creating a dbspace between 1 and 2 TB on a raw

partition on AIX sometimes caused the server to fail in

s_dbmvbio::PlaceNewSegment.

625054 The language set as DB Collation is used for a message language after IQ15.1ESD#1i. The method which changes a message language does not exist.
625129 They would like a FR so that the BACKUP and RESTORE commands also backup and restore the .lmp license key file.
625154 Restoring Multiplex co-ordinator using an incremental/incremental since full backup will fail if the backup was taken immediately after allocation activity from a writer server. All releases post 15.0 till 15.1esd 2 are effected. This has now been fixed in 151esd3.
625208 Running INSERT...LOCATION against a Sybase IQ database

created with collation 950ZHO_TW to import data from a

remote ASE server generated an exception thrown from

hqm_con.cxx:182 and reported the error "SQLCode: -1006000,

SQLState: 'QBA00', Severity: 23 IQ Internal error. Please

report this to Sybase IQ support."

625242 The restriction which adds new conditions to table partition of IQ exists. For example, new conditions cannot be allocated to new dbspace. New conditions are applied within the existing dbspace.
625261 Multiplex: Multiplex nodes were unresponsive and went to

a pending status. A timing sensitive deadlock could occur

in the IQ main or temp buffer cache, if all pages of the

cache were locked or dirty.

625659 Request sa_recompile_views() proc to return meaningful error when encounter invalid view.
625757 incorrect result using local var in where clause and UNION ALL
626416 SELECT datepart(cwk,'2010/01/01') returns 53 coorectly, but returns erroneously 52 when selecting it from a table.

This option must be set: set option Date_First_Day_Of_Week = 1;

626436 Due to a 3 byte FP index inconsistency, a query or sp_iqcheckdb caused a

server failure in s_dpThreeByteFetch::GetCardinalty or inconsistencies in

memory.

626488 Visual Studio: Adding a data grid and database connection

to a windows form resulted in an error. Visual Studio

could not generate DataSets and Entity Framework models

using Sybase IQ data sources.

626489 Visual Studio: Accessing Sybase Central from the tools

menu returned the error "The System could not find the

file specified." Visual Studio was missing entries for

Interactive SQL and Sybase Central.

626490 Visual Studio: The Server Explorer pulldown menu for

DSN did not list any configured DSNs. The Visual Studio

integration component now searches Sybase IQ data sources

using the prefix "SYBASE IQ".

626607 The error "Syntax error - ORDER BY item of WITHIN GROUP

clause must be expression over column" is generated, if the

ORDER BY of the WITHIN GROUP clause of the PERCENTILE_DISC

function is over a constant expression. This error

is correct, since the ORDER BY over a constant expression

makes no sense. The error message is now more accurate.

626644 if output file is not specified with -zo startup parameter, then all logging from -zr (ALL , NONE, or SQL) is logged in srvlog
627003 IQ 15.x fails in restore using backup of readonly dbspace.
627304 A query referencing a view or derived table that

contained a select list item that was not a table

column could cause a server fault, when executing in

an IQ table or a proxy table. The error reported was

"SQLCode: -1001047, SQLState: 'QFA43', Severity: 14

Column: is not accessible in this context. --

(df_GenerateDF.cxx 192)."

627445 Console mode of DBISQL cannot print multiple results.
627485 A server failure was caused by delayed projection

optimization that affected push-down join conditions.

627508 Restoring Multiplex co-ordinator using an incremental/incremental since full backup will fail if the backup was taken immediately after allocation activity from a writer server. All releases post 15.0 till 15.1esd 2 are effected. This has now been fixed in 151esd3.
627514 Documentation Request for the Errors and Warnings of TIME SERIES functions like ts_arma_ar in RAP

A list of IMSL errors are in files imslerr.dat and imsls_e.dat.

A copy of those files can be opened in any text editor.

627568 When additional CPUs are added while IQ is running and IQ repeated fails to check-out licenses for the additional CPUs it should shutdown after 30 days.
627724 The utility which changes a message log and a language to Sybase IQ 15.x is not attached. Probably, IQ should release a message log language change utility.
628049 The Interactive SQL utility option isql_print_result_set was being ignored. This has been corrcted so that it is once again respected.
628222 A query that joined view tables and the join condition

contained CASE statements failed with the error

"IQ Internal error. Please report this to Sybase IQ

support. -- (dfjo.cxx 198) [-1006000] ['QBA00']."

628413 trying to load from a client side pipe on AIX does not work
628455 Under some rare circumstances, when a local temporary table

went out of scope, the server failed at s_blockmap.cxx:2440.

628477 Multiplex: A coordinator shut down, then after a period

of time some of the writers shut down with a non-fatal

IQ internal error detected at s_bm.cxx:1476 and the

message "Bitmap result bitcount not in legal range."

628581 Enhance IQ auding for enterprise customers
628619 Problem due to a replacing CASE predicate for optimization within group by node if NULL due to which IQ optimizer used "sort" algorithm for group by node, as it chose "sort-mege" algorithm in resolving the join node has been resolved.
628667 Server failed if query flattening optimization was be applied to a Subquery aggregate scalar function. This has been fixed.
629012 load table to the partition table which uses a compression column fails.

IQ fails in the dirty page to a buffer cache at creation.

629163 A SELECT TOP N GROUP BY ORDER BY DESC query returns an error "Non-Fatal IQ Internal Error Detected at opt_Driver.cxx:9059", followed by a server failure at st_server.cxx:1376.
629367 Catalog DB and IQ store of IQ do not support NAS.
629497 A SELECT query with a two table join intermittently produced

an incorrect result. The result depended on the method the query

optimizer chose to process the pushed down predicate of a hash

pushed down join.

629523 With the imsl timeseries functions an error number is reported but no error text.

Please document that a list of errors can be found in the files imslerr.dat and imsls_e.dat

629542 When there is a problem with calling time series within the

imsl library functions then only errornumber and no errortext

is put into the logfile or send to the client

629701 multiplex system running a stored procedure which alters some ddl gets st_server.cxx:1376 crash. On HP the stack does not have the sq symbols printed so you see this for example....

/opt/sybase/IQ-15_1/IQ-15_1/lib64/libiqserv15_r.so [0x400011f52d8]

/opt/sybase/IQ-15_1/IQ-15_1/lib64/libiqserv15_r.so [0x400011f5534]

/opt/sybase/IQ-15_1/IQ-15_1/lib64/libiqserv15_r.so [0x400011d6b88]

There is a seperate CR 633385 raised to resolve this stack print error on IBM platforms.

The real stack can be obtained from running s gbd on the core, failure is at _ZN15df_MemGovRegion14DoCanAllocPageEv

629819 IQ catches signal11 and stops in df_Heap::GenerateDF.
629840 Customer uses Replication Server DSI to connect and replicated data into IQ. Under certain rare conditions the DSI TDS connection into IQ hits the following error...

I. 05/18 09:29:13. TDS 178: login: user 'DLNPSPSW04_IQ_maint', database '', application 'RepServer', host 'lns66d-8110a', host_pid '21988', charset 'iso_1'

I. 05/18 09:29:13. Login procedure 'DBA.sp_iq_process_login' caused SQLSTATE '22003'

I. 05/18 09:29:13. Value 2117418877184 out of range for destination

The login is not rejected however and the connection to IQ is allowed (this must surely also be a bug?). Another side affect of the error is that the call to sp_login_environment() is not made meaning that the sp_tsql_environment procedure is not called so database options specific to TDS connections are not set.

The source of the "Value 2117418877184 out of range for destination" error is an incorrect declaration of the column that represents LockName in the stored procedure sp_iq_process_login...

'create procedure DBA.sp_iq_process_login()\x0Abegin

declare @admin_on char(1);

declare @has_perm char(1);

declare @login_locked char(1);

declare @number_connects integer;

declare @number_connects_admin integer;

declare @number_db_connects integer;

declare @password_days integer;

declare @password_days_admin integer;

declare @password_created timestamp;

declare @times_connected integer;

declare c1 integer;

declare c2 varchar(255);

declare c3 varchar(255);

declare c4 integer;

declare c5 varchar(255);

declare c6 varchar(255);

declare c7 integer;

declare c8 varchar(255);

declare c9 varchar(255);

declare c10 varchar(255);

declare c11 integer;

declare c12 integer;

declare c13 integer;

declare c14 unsigned integer;

declare c15 integer;

declare @counter integer;

declare end_of_cursor exception for sqlstate value ''02000'';

declare saconn dynamic scroll cursor for call sa_conn_info();

......

the declare for c14 (which is the LockName) should be unsigned bigint and NOT unsigned integer.

Here is the corresponding declares in sa_conn_info where the connection infromation is obtained from...

'create procedure dbo.sa_conn_info(in connidparm integer default null)

result(Number integer,Name varchar(255),Userid varchar(255),DBNumber integer,LastReqTime varchar(255),ProcessTime varchar(255),Port integer,ReqType varchar(255),CommLink varchar(255),NodeAddr varchar(255),LastIdle integer,CurrTaskSw integer,BlockedOn integer,LockName unsigned bigint,UncmtOps integer)

begin

declare connid integer;

declare local temporary table t_conn_info(

Number integer null,

Name varchar(255) null,

Userid varchar(255) null,

DBNumber integer null,

LastReqTime varchar(255) null,

ProcessTime varchar(255) null,

Port integer null,

ReqType varchar(255) null,

CommLink varchar(255) null,

NodeAddr varchar(255) null,

LastIdle integer null,

CurrTaskSw integer null,

BlockedOn integer null,

LockName unsigned bigint null,

UncmtOps integer null,

)

in SYSTEM not transactional;if(connidparm is not null) then

....

Not an issue for IQ 15 and higher as this use dbo.sp_login_environment instead of DBA.sp_iq_process_login

629950 IQ cannot be started on an AIX machine with 252 or more CPU threads. IQ will output and abort the "Memory allocation size too large" message.
629952 The request of the feature which restores the backup file of readonly dbspace to Updating dbspace.
630020 Referenced view or derived table that contained a select list item which was not a table column caused a crash in IQ at df_GenrateDF.cxx:192. This has been rectified
630516 Feature request for sp_iqdatatype to return for a user-defined datatype/domain, the underlying IQ system data type.
630523 Could not insert, update, delete, or transfer data to Sybase IQ,

when using MS-SQL SSIS. Could not insert, update, or delete,

when using MS-SQL 2008 Link Server to Sybase IQ. The error

"[ADO NET Destination [16]] Error: Length cannot be less than

zero." was returned. ADO.NET drivers were not properly registered

with the system registry for Microsoft Visual Studio 2008.

631239 NFR: provide a way for IQ to return XOpen/SQL99 form
631262 Updatable Cursor could not handle more rows than specified by

the cursor_window_rows option and caused the server to become

unresponsive.

631447 The trigger creation wizard of Sybase Central cannot list a user table.
631478 clarify open cursors to the db are not closed when an auto-commit occurs
631595 A new user's comment set to be a user creation wizard is not shown on the user property dialog of Sybase Central.
631775 Creating WD indices in parallel gives them the default delimiters instead of the one specified.
631863 Support for UTC timestamp format when using load table.
632115 IQ should locate all object data to a partition by range specification. IQ cannot split metadata and index(non FP index) data.
632178 When attempting to replicate data from MS-SQL to Sybase IQ,

no data was sent to Sybase IQ and the connection was dropped

abruptly. The schema definitions that provide input to the

OLEDB driver have been updated to return correct database

metadata for Sybase IQ.

632261 The ISDATE function returned an incorrect result.
632266 Only in case of parallel left outer hash join, when under resource constraints, parallel probing was not possible and it tries to do a serial probing and while doing so the server fails. This has been fixed.
632475 OLEDB not working for linked server for some SQL syntaxes. This has now been fixed.
632548 Improve performance for select * from wide tables (900+ columns)
632876 iqunload -n generate incorrect syntax for IQ table with foreign key. An error "Not NULL foreign key not supported" was raised when executing a reload schema in reload.sql.This issue does not apply to iqunload -au.
633040 Calling a stored procedure that operates on a table column

could cause a server failure, if the specified column did not

exist. A server failure could also occur, when calling stored

procedures that operate on literal names, when quotes were

omitted. For example, sp_helptext dbo.sp_iqstatus

caused a server failure, because without quotes,

dbo.sp_iqstatus was interpreted as a table/column name pair.

633062 For example, when DB Collation of IQ is UTF8 and Client Chaeset is EUC_JIS.

The client for which Japanese included in the result of SQL is using which character set is also converted correct.

633066 IQ does not support a trigger. However, a trigger can be created using DBISQL. However, the created trigger does not work.
633143 Sybase IQ and the installer require .NET v2 and .NET v3.5 for support of the ADO.NET drivers.
633354 xp_cmdshell did not execute the command on UNIX platforms.
633385 On linux the stack is not resolving all symbols so you see something like this....

: ===== Thread Number 1305012544 (IQ connID: 0000514253) =====

/sybase/IQ-15_3/bin64/../lib64/libiq15.so(_Z9pcstkwalkP9stk_traceiP6db_logP6hos_fd+0x31) [0x2aaabf3a4ad1]

&/sybase/IQ-15_3/bin64/../lib64/libiq15.so [0x2aaabf3a3a42]

&/sybase/IQ-15_3/bin64/../lib64/libiq15.so(_Z14DumpAllThreadsPKcji+0xff) [0x2aaabf3a37bf]

&/sybase/IQ-15_3/bin64/../lib64/libiq15.so(_Z9hos_ABORTPKcjS0_PcS1_+0x19a) [0x2aaabf15729a]

&/sybase/IQ-15_3/bin64/../lib64/libiq15.so(SigHndlr+0x4e) [0x2aaabfc6366e]

&/lib64/libpthread.so.0 [0x367520eb10]

&/sybase/IQ-15_3/lib64/libiqserv15_r.so [0x2ad89f7f21e7]

&/sybase/IQ-15_3/lib64/libiqserv15_r.so [0x2ad89f5f9e00]

&/sybase/IQ-15_3/lib64/libiqserv15_r.so [0x2ad89f5fad8f]

&/sybase/IQ-15_3/lib64/libiqserv15_r.so [0x2ad89f8eb42f]

&/sybase/IQ-15_3/lib64/libiqserv15_r.so [0x2ad89f8c314f]

&/sybase/IQ-15_3/lib64/libiqserv15_r.so [0x2ad89f8c3313]

&/sybase/IQ-15_3/lib64/libiqserv15_r.so [0x2ad89f8c490d]

&/sybase/IQ-15_3/lib64/libiqserv15_r.so [0x2ad89f8c4e3c]

..................

The environment has to have a pstack command defined as a symbolic link to the gstack command for Linux. If this is set up then a second print of the stack is done with all the symbols resolved.

Please note the top part of the stack will still show the first thread for the ABORT with the unresolved symbolic names. However if you search on ABORT further down in the stack trace you should see the thread printed again (with the thread number in HEX) this time with the symbolic names resolved.

633466 A simple join between an IQ table and a remote table returned an internal error if the local IQ table did not return any rows.
633606 Sybase IQ server failed from s_blockmap.cxx with message "TEMPORARY blockmap still owns dirty pages -- should have been destroyed".
633825 When sp_addtype was executed on local store, it created

'Create domain ...' entry into local TLV store with Owner

of the domain 'dbo'. If sync followed, sync failed to replay

the domain command due to 'dbo' owner.

633919 Customer has a requirement to be able to create windows services for starting IQ servers via a command line utility similar to windows sc.exe so that this operation can be done via a silent install script with no user interaction or intervention needed. Can SybaseIQservice15.exe be enhanced to be able to run it as a command line tool?
633949 dbisql fails to decrypt command file encrypted with dbfhide utility on solaris
634176 We need an official document that states whether there is backward compatibility

of the IQ 15.2 connectivity drivers with the previous versions of IQ server.

634314 On running "select * from sp_iqmpxincheartbeatinfo()", error

Cannot convert '00:00:0000:00:00:00' to a timestamp

SQLCODE=-157, ODBC 3 State="07006"

maybe thrown.

634333 In Performance and Tuning Guide > Using OLAP >Analytical Functions > Windowing >

Window framing > ROWS, the description of calculation for averages contains five

bullet points. The last two bullet points should be changed to: Row [4] = (120 + 500 + NULL)/2 and Row [5] = (500 + NULL + NULL)/1

634385 Queries containing a CASE statement with a NOT NULL

clause returned incorrect results.

634674 Under exceptionally rare conditions, the server failed when

expanding a very large view definition that contained a

UNION, INTERSECT, or EXPEPT query node and there was

insufficient cache space available.

634959 A query that included both an IQ table and a proxy table

returned the error "Msg 2706, Level 11, State 0:

SQL Anywhere Error -141: Table '<proxy_table_name>' not

found," when the proxy table was qualified by owner and

the user executing the query was not the owner of the

table.

635046 When performing IQUNLOAD -au on a database with

quoted_identifier='off', IQUNLOAD failed on reload

with the syntax error "SQL error: Syntax error

near 'old_IQ_MPX_INFO' on line 1"

635108 If an application executed a remote statement that required

the server to execute the statement in either partial or no

passthru mode, there was a chance the server would fail, if

the statement was overly complex or if the server cache was

exhausted. In addition, if an application executed a remote

query that required partial or no passthru processing and

the query made heavy use of aliases, then the server

could incorrectly return error "-890 statement size or

complexity exceeds server limits." Now the -890 error is

returned only if the statement size or complexity really do

exceed server limits.

635244 When a bit data type is added using a SUM function, IQ may return the wrong result. An index exists in the corresponding table, and it may be reproduced when the column is set to be order by.
635782 During local TLV replay, if comment on procedure statement

encountered a procedure not found error (SQLSTATE:52W09),

then local TLV performed an emergency shutdown.

635832 The option ANSI_SUBSTRING was introduced in the IQ 15.0 time frame but was never honored in IQ's implementation of substr. This option controls whether or not the substr function conforms to the ANSI standards. In particular, it disallows the third argument from being a negative number. The default value for this option is being changed for IQ databases to be 'OFF'. This will maintain the current default behavior of allowing a negative number as the third argument.
635840 ADO.NET Data Provider: The Available objects list was empty

when creating SSIS data source view.

636042 The value of the VersionID column of sp_iqtransaction is always set to 0. However, in non-MPX, the same value as TxnID is set to VersionID.
636175 LOAD TABLE QUOTES ON could not load quoted strings with

columns delimited by TAB, and returned the error "Could

not execute statement. Expected 'column' delimited column

type on input, but encountered a row delimiter instead.

Probable cause is a mismatch between the specified

column delimiter and the column delimiter used in the

input file."

636192 The mapping of the columns of a proxy table to a Microsoft

SQL Server table changed as of Sybase IQ 15.2 ESD #1. A LONG

BINARY column now maps to a Microsoft SQL Server VARBINARY(max)

column. In Sybase IQ 15.2 GA, a VARBINARY column was mapped to

a Microsoft SQL Server VARBINARY(max) column.

636476 The IQ server appeared to be unresponsive, when an

ESQL program that opened many no-scroll cursors

disconnected.

636632 The IQ server failed when the query was using a sort

merge pushdown join on a heavily loaded server.

636953 The Sybase IQ server failed while creating an index,

when the database option MAX_IQ_THREADS_PER_TEAM = 1.

637544 Customer using '-onerror continue' option for dbisql.

However Batch SQL was finished when certain error occurred.

637612 Loading into auto-increment/default columns can fail for a specific scenario. This has been fixed.
637839 When CONTAINS() was used in a CASE expression for empty

string data, a WD index on a VARCHAR column returned an

incorrect result.

637840 ADO.NET driver: SAConnection.State was still open after

the connection was dropped.

637935 A query returned "Non-Fatal IQ Internal Error Detected

at dfo.cxx:9685 on thread 2828 (TID 25) Internal error

at node: #08 Can not evaluate expression:

MIN(MIN(TEST_MIN.col1)) Error detected at DFO #08 Group

By Single"

637953 A SELECT query involving an outer join and scalar correlated

subquery sometimes failed with a dfo.cxx:9562 exception.

638356 There was an issue in the memory handling in the driver code. This has been fixed.
638546 Secondary nodes shut down after executing a few alter table

statements separated by colon ":" on the coordinator/writer

node.

638734 In an MPX environment,backup first RW dbspaces then RO dbspaces.

Inadvertantly, if you restore read only dbspaces (resp. RW dbspaces) from the RW (resp. RO) archive, the restored catalog could be invalid.

639150 Request for Replication Agent IQ.
639229 need ACCENT_RESPECT collation for 1250LATIN2 charset
639243 Multiplex: An update on a table returned a main bufman

error, when executed in the same session after converting

a Reader node to a Writer node without rebooting the

server.

639334 The Redistributable package of VC++2005 and VC++2008 is required for IQ.

The installer of IQ installs these packages in a system.

However, in the system in which VC++ of one of versions was installed, IQ installer cannot install insufficient VC++Redistrabutable.

639368 15.2 IQUNLOAD -au would faile if the database being upgraded has a java class installed with the command: INSTALL JAVA FROM @variable
639512 add a parameter to sp_iqemptyfile to allow specifying which r/w dbfile to relocate data to
639513 allow specification of any r/w dbfile in ANY dbspace rather than just current one
639730 The unnecessary link is included in description of "-cl" starting option in IQ Utility Guide.It does not need to be explained for description of '-cl' after 'For more information'.
639767 It is included in description of 'ALTER TABLE' about EBM. However, the document written about EBM does not exist.

EBM is the short title of Existence Bit Map. EBM : a basic datastructure used for storing metadata information that table/Indexes

639824 A complex query with subqueries that contain no FROM clause may result in an IQ Internal Error along with a stacktrace in the iqmsg file.
640129 When a product requires multiple licenses and the license server has insufficient licenses available to satisfy it's needs, the failure message reported by the product does not show the correct amount that were available (that the product could obtain). E.g. "Replication Server requires 4 REP_SERVER licenses but only 4 could be obtained."
640192 There was a problem in an HG index load algorithm, when the

underlying index contained some deleted keys. "Non-Fatal IQ

Internal Error Detected" was returned.

640331 load table (filename-vaiable) fails with an Exception
640333 Enhance TDS support for 'load table using client file' using iqisql/jConnect
640419 A query involving OLAP and views using extended GROUP BY

syntax was not rejected with a syntax error, when the query

ran as a SQL Anywhere managed and non-passthrough query

(using cis_option=8).

640433 When the 'substr' function was used with 'SELECT....CASE

WHEN' and the value -ve was passed as length to the

function, Sybase IQ returned an invalid parameter error

(SQLCODE -1090), only if the 'substr' function executed

at runtime.

640731 In IQ15, the updating transaction which used cursor requires many time rather than IQ12.7.
640890 When creating a database using an iqinit utility, IQ temp reserve size cannot be set.
640913 add ability to tds layer so that user can log in via ctlib isql if user was created with 'force password change on'
641090 Cleanup for sort object during forceful termination of query has been corrected.
641229 In very rare cases, the Sybase IQ server could stop

processing, if an external environment call was made at

the same time the server began to perform some maintenance

on the database.

641943 IQ 15.1 checks out one IQ_CORE license more than there are actual cores on the machine if floating licenses are in use.
642111 15.2 ALTER TABLE hangs until full BACKUP finishes
642368 v3 Scalar UDF example my_toupper produced wrong results due to a character pointer offset by 1. This has been fixed.
642371 The CREATE PROCEDURE for the v3 Scalar UDF example my_toupper example was not present while creating a new IQ database. This has been fixed.
642507 distinct query with inner joins takes much longer than MySQL
642511 Customer requested fruther documentation on the transaction states reproted in sp_iqtransaction. In particular to help understand when a transaction is placed in an APPLIED state and what it means to versions and locks the transaction was holding.
643258 IQ(SQL Anywhere) JDBC driver cannot handle the DBCS SJIS character including 0x7B correct as an object name.
643282 The Sybase IQ server failed on the parallel execution of

vertical predicates (a SELECT with subqueries).

643926 IQ 15.1 cannot reach ASE 15 through remote server class ASEODBC 64 bits
644031 The Sybase IQ server sometimes failed when executing a query

involving the sort merge push-down algorithm.

644073 We need explanations about temp cache management
644410 Please be sure to install VC++ 2005,2008 Redistributed Package before executing the installer of Sybase IQ 15.x for Windows.

Some programs could not be started when only VC++ 2005 currently written to the installation guide is installed.

644979 Version: 12.7.0/100114/P/ESD 9/ITANIUM/HP-UXi 11.23/64bit

Would like help determining if a poorly performing query is the result of bad optimizer choices , or if working as expected and explaination as to why and whats happening...

Customer has a query that is being executed in 12 seconds, the format for the query is

SELECT ...

FROM ...

WHERE ... AND B.TIMESTAMP_S4B > '2010-08-04 11:00:00.000000'

If customer adds a simple condition in the where for a column that already had a condition

then the query plan changes and the query takes 55 minutes. This is the format

for the new query

SELECT ...

FROM ...

WHERE ... AND B.TIMESTAMP_S4B > '2010-08-04 11:00:00.000000' and

B.TIMESTAMP_S4B < '2010-07-06 11:00:00.000000'

looking at the query plans good and bad that can be found at \\ecss\ts-cases\11629000s\11629275, we can see the performance increase is stemming from the rows returned from leaf node #3 into the join.

In the bad query a table scan is done and the entire 684 million rows from table HOP_OPPERACIONES_6_MESES_EVR is passed to the JOIN and a sort merge join is done on it.

In the good query a condition of

ROW(A.ID_4B, A.CODIGO_OPERACION) = ROW(BV(2, CAST(SUBSTR ((D.REFERENCIA_DOCUMENTAL,2,23) AS NUMERIC(126,38))), BV(1, CAST(D.NUMERO_EXPEDIENTE AS NUMERIC(126,38))))

is pushed out of the join and into Leaf node #03 resulting in only 553 rows passed into the join and a Nested Loop push down is done.

In both queries the B.TIMESTAMP_S4B condition is resolved and an invariant in Leaf #5. For the bad query the extra condition is merged into a single BETWEEN condition.

If the customer uses join_preference -1 or 3 to avoid the sort merge then the query runs quickly again. So why is the optimizer choosing the slower sort merge ?

645066 A user name is not set to analaysis result when request log is analyzed using sa_get_request_profile() or sa_get_request_times().
645127 The problem may occur if a crash occurs after insert/load transaction commits and before checkpoint.

The fix takes care of reflecting most up-to-date identity value into catalog before the objects are closed at the end of insert/load operation.

645254 Coordinator node failed while creating a procedure

containing temporary table declarations.

645552 DBISQL cannot encode the Japanese character string set to the program argument correct.

And this issue is reproduced only by Solaris.

645997 The order of results was incorrect, when the

PARTITION BY and ORDER BY clauses had the same column

in the case of DESC order for the DENSE_RANK function.

646028 select statement returns the internal error dfjo_Hash.cxx:1635.
646311 The dbping -l option can be used to specify an ODBC driver or driver manager library. If the Unix driver manager included with SQL Anywhere (libdbodmX.so) was used as the argument for the dbping -l option, dbping returned the error ""Failed爐o爈oad燨DBC燿river" .

dbping has been fixed so that it can be used with libdbodmX.so.

646497 document the use of raw devices under windows properly
646775 The server failed at s_dpByteFetch::Find, if a table was

referenced in a query with an aggregate function (min, max)

with a NOT EQUAL "<>" operator, such that the column

involved was not a HG or FP index.

646863 Server failure was caused due to an issue in the handling of heap memory associated with procedures having Window functions. This has been fixed now.
647068 15.2 ESD1 Installer does not work with no previous database and lmp files (same as CR 621325)

Customer platfrom HP-UX B.11.23 U on IA64 IQ 15.2 GA - installing ESD 1

Also repro'd on Windows x86

Once the installer is started and it asks for the location of the Installation, user sees the screen where the Installation wants to validate licenses of existing databases.

If you select browse to locate you .lmp file being used successfully for the IQ 15.2 GA instalation and try use that you get and error...

"There is not a valid license to associate with <the givem lmp file>. This upgrade is not covered by your maintenance agreement. You must acquire an appropriate license before you can continue."

The skip check box is available but the customer feels this is not addressing the issue of why his 15.2 GA license files are not valid anymore for the purpose of the ESD installation

647333 Forwarding 'select @@version to ASE 15.0.3 from IQ 15.1 results in error 706 - Remote server does not have the ability to support this statement
647462 The database creation wizard of IQ15.2 can change DBA user.

This is the new feature of IQ15.2.

IQ15.2 can change a DBA user's user name and password.

However, when the autostart option is validated with the database creation wizard of Central, Central cannot log in to the created new database automatically.

647809 Previously, if a JDBC application connected using jConnect, and if the application subsequently called DatabaseMetaData.getSchemas(), then the server would fail the request with the error "the 'FileVersion' property is no longer supported". This problem has now been fixed and the proper list of userids now gets returned to the application.
647834 Wrong result set when table has PK
648004 Attempting to cancel a query to drop a local temporary

table sometimes caused the server to fail.

648159 When perseat licensing was used, the error "Database server

connection limit exceeded" may have been reported

inappropriately. In order for this to have occurred, in

addition to perseat licensing, the -gm server option or http

connections to disabled databases must have also been used.

If this problem occurred, the first time the error was

reported was correct behavior, but after disconnecting

connections, the error may have reported when it should

not have.

648167 The customer is frequently hitting an issue where the get transactions in a COMMITTED state holding a huge amount of version space. The transaction is not progressing to an APPLIED state so that the versions space can get releases because there is some connection stuck in the system that is holding a shared lock and has not committed.

There is a convoluted way to do this manually with existing utilities etc (see below) but the customer would like a new Feature Request to create a new utility that would simplify this and make it easy to identify and kill problematic connections that cause this.

PSE note on how this is achieved manually...

If you look at the sp_iqtransaction output at the COMMITED transaction that you suspect is holding the resources. (BTW If the name and userid is (NULL) then the connection that this commit was for is probably no longer in the system). If you look at the CmtID that is the transaction ID for the commit action. You can use this along with the connection id to cross reference what it was doing in the IQ logs.

To see if there are any connections holding locks preventing the commit from being applied and flushed out the system look for transactions with TxnID's that are earlier then the CmtID (i.e. smaller numbers). Use the ConnHandle information of these transactions to cross reference with sp_iqlocks to then determine what tables they are still holding locks still for and determine if any of these are tables involved in the committed transaction. The iqmsg and request level log will help in determining this too.

From this you can work out which connections most likely have not themselves done a COMMIT and there for are still holding locks preventing the COMMITED transaction from above being applied and the versions released. In order to more easily identify this situation the transactions involved would of course needed to of been in the system a while so they are easy to identify from the current work load (long running transactions). In most cases it is usually very easy to spot the most likely connections causing the issue, i.e. they are usually the ones that have been in the system a long time but are not really doing anything. So if you monitor them over a short period you will see the locks for them are not being released, the commit id / transaction id's for them are not changing.

648431 A query having a GROUP BY clause and Coalesce/Isnull clause

failed.

648455 Functional requirement for IQ to keep track of temp tables in its system tables like ASE.
648598 Long running update table query runs out of virtual memory after about 20 minutes in certain circumstances and crashes IQ server.
648635 IQ server was failing with non fatal internal error if select query has view and view definition has union of selects which has more than 13 nested ISNULL() functions in select list.
648731 SELECT query fails at dfo.cxx 9060 in 15.2 ESD 2 when merge join node gets wrongly ordered input from it's child.
648771 15.2 Is there an option to limit temp cache used by connection/operation?
648773 15.2 More info on error "Insufficient buffers for operation"
648843 An issue with cursor handling in combination with the option setting CHAINED='OFF'

could result in an Assertion failure "Page number on page does not match page requested".

The issue was most likely to occur in Sybase central when clicking on "procedures and functions" folder. The issue has been fixed.

649421 If an expression containing an IN list was used in the

SELECT list of a query and also the GROUP BY clause of the

query, then it was possible for the query to fail with an

error such as: INVALID_GROUP_SELECT 53003

-149L "Function or column reference to '%1' must also

appear in a GROUP BY." ----

In order for this problem to occur, the IN list must have

contained 20 or more elements, and the element type of the

IN list must have been string literals, hex strings, or exact

NUMERIC literal with a decimal point. ----

For example, this statement could generate this problem:

select count(*), IF T.x IN ( '0', '1', '2', '3', '4', '5',

'6', '7', '8', '9', '10', '11', '12', '13', '14', '15',

'16', '17', '18', '19', '20', '21', '22', '23', '24', '25',

'26', '27', '28', '29' ) THEN 1 ENDIF from T group by IF T.x

IN ( '0', '1', '2', '3', '4', '5', '6', '7', '8', '9', '10',

'11', '12', '13', '14', '15', '16', '17', '18', '19', '20',

'21', '22', '23', '24', '25', '26', '27', '28', '29' )

THEN 1 ENDIF ----

This problem is fixed, but the expressions containing the

IN lists must contain the elements in exactly the same

order or the error is returned. For a server without

the fix, a recommended workaround is to rewrite the query to

compute the expression in a derived table. ----

For example: ----

select count(*), D.yyy from ( select T.*, IF T.x IN ( '0',

'1', '2', '3', '4', '5', '6', '7', '8', '9', '10', '11',

'12', '13', '14', '15', '16', '17', '18', '19', '20', '21',

'22', '23', '24', '25', '26', '27', '28', '29' ) THEN 1

ENDIF as yyy from T ) as D group by D.yyy

649440 creating HG indices in parallel is slower than in serial. Thread calculation of parallel create is also off by magnitudes
649529 A query sometimes returned incorrect result if it was

processed in parallel, or if it was neither a correlated

subquery nor an NLPD join.

649533 The 15.2 Sybase Central plug-in exhibited poor performance when displaying a list of tables or information of a single table when a database has around 100 tables and 30000 indexes. Performance degradation was caused by plug-ins repeated loading of the table or index information (metadata). This has been resolved.
649576 Queries with a self outer join having the same base table as "preserved" and "null-supplying sides" can return incorrect result sets.Conditions under this could happen are:

- the outer join is of the form : T as T1 LEFT OUTER JOIN T as T2 ON(p)

- the ON predicate p has only equijoins, and at least two equijoins

- p is of the form : T1.c1 = T2.c1 and T1.c3 = T2.c2

- there exists an unique index on T < c1,c2>

649595 Query ordering by computed column raises assertion 106104 in 15.2 ESD1
649601 unable to add temp dbspace or dbfile in -iqnotemp mode after dropping last temp space
649777 Under the following circumstances an outer join which was

processed using the hash based algorithm returned

incorrect results: 1. The outer table of the outer join

had unique multi-column HG (MCHG) index; 2. Part of the

columns of the MCHG index were used as EQ-join condition

and the rest of the columns were used as local comparison

predicates; 3. The comparison predicates were comparing

columns (used in the MCHG index) to constants. All

columns in the MCHG index MUST BE used in the query.

649858 In very rare cases, the server asserts with assertion error 102300 "File associated with given page id is invalid or not open" if request level debugging is enabled, query plan logging is enabled, and schema changes exist. This has been fixed. Workaround: turn off plan caching (option Max_plans_cached = 0) or turn off plan logging (switch -zr without "plan" and "all").
649959 IQ Store full at recovery, no connection possible. How to add a new dbspace?
650125 15.x CASE expr IS NOT NULL return wrong result
650418 sp_iqtable does not support over 128 bytes of remarks.
650421 Incorrect & different count(*) result may be returned when a query uses sort merge join with parallel order by retrievers and redundant ordering columns get eliminated from the Order By nodes
650457 LOAD TABLE cannot insert a blank character string in a VARCHAR column.
650822 15.2 Many CASE WHEN in main SELECT and derived table take long parsing time
651158 Joining a small ASE table to a large IQ table via a proxy table in IQ is slow
651197 ceiling function returns incorrect result on user table, works correctly on system tables
651272 The issue was caused due to a race condition between disconnect and getting a connection property. This has been fixed now.
651318 create unique clustered index against an IQ table really creates a unique HG index.
651331 IQ does not error on 'exec <function>' or 'call <function>
651808 A Query having nested blocks with case and group by caluses was giving different results on each run. This issue could occur mostly when the outer query blocks's CASE clause would depend on the evaluation of the inner query block's CASE clause.

eg. When the query pattern is somewhat like this:

SELECT

B.col1 as col1

FROM

(

SELECT

CASE

WHEN A.col2 THEN ...

...

END AS col 1

FROM

(

SELECT

CASE

WHEN col3 THEN ...

...

END AS col2

FROM

...

GROUP BY ...

) A

GROUP BY ...

) B

652287 In heavy load scenarios server become unresponsive due to contention between FL lock and busy buffers. This problem has been fixed now.
652379 If a query used the user_name() or suser_name() builtin function, then the described length of the column was LONG VARCHAR, even though the value would be at most 128 bytes. This has been corrected so that the described type is now VARCHAR(128). Any materialized views that use these builtins in the select list should be rebuilt after this change.
652550 single CPU causes single thread pool creation resulting in incorrect result set

IQ 15.2 ESD2 (and IQ 15.1 ESDx) on RS6000 AIX 64bit running the following query..

SELECT

V_traffic_TIME.WEEK_NUMBER_OF_YEAR,

V_traffic_TIME.DATE_KEY_DATE,

COUNT (Distinct ( convert(char(5),SYBMDM.V_TRAFFIC_FACT.TIME_SID)+ ': ' + SYBMDM.V_TRAFFIC_FACT.WEBID + ': ' + convert(varchar,SYBMDM.V_TRAFFIC_FACT.VISIT_ID)))

FROM

sybmdm.V_TIME_DIM V_traffic_TIME, SYBMDM.V_TRAFFIC_FACT

WHERE

(V_traffic_TIME.TIME_SID=SYBMDM.V_TRAFFIC_FACT.TIME_SID ) AND V_traffic_TIME.DATE_KEY_DATE BETWEEN '2010-08-21' AND '2010-10-04'

GROUP BY

V_traffic_TIME.WEEK_NUMBER_OF_YEAR, V_traffic_TIME.DATE_KEY_DATE

If run this on a box with a single CPU on IQ 15.1 ESDx (this can also be simulated by specifying -iqnumbercpus = 1) the query returns 0 rows and the Threads info in the query plans show the query had only a single thread used in a single pool. The left hand side of the hash push down should produce about 39 million rows , it produces 0 rows.

If you run the same query with two or more CPUs the query runs fine and produces a expected result set of 45 row. The Threads info in the query plan shows multiple thread pools set up with multiple threads used.

Also NOTE !!! .... using IQ 15.2 ESD1 the problem goes away (i.e. the query run in a single CPU configured environment runs fine with multiple thread pools and threads set up.) HOWEVER IQ 15.2 ESD2 regresses to the failure again.

652732 Query returns wrong results when it has a correlated subquery having a number of conjunctions of disjunctions of predicates. This happens when some predicates in the disjunctions are invariant (e.g. table.column = 4)
652828 sp_iqaddlogin on IQ15.x can not use '&' as login password
652929 When using the ADO.NET driver to connect to older versions of Sybase IQ (12.x and under) the driver would raise an exception. This has now been fixed.
653057 Only period is supported as decimal separator.
653234 On rare occasions, the sql function "NEWID" may return

a duplicate value.

653585 IQ server was failing if query having group by cause and Coalesce/Isnull clause.
654023 The Sybase IQ server could fail when executing a query involving the sort merge push-down algorithm.
654840 iqsrv15.exe does not have a message resource for event viewer.
655553 Data exception - operation resulted in division by zero when no rows are returned

select 0/0 from iqdummy where 1=2

655737 This is follow on Feature Request steaming from the investigation done in CR 644807 and case 11629524. This is an issue to do with customer trying to do a partial width insert on a table which contains columns with DEFAULT VALUE column definitions. This causes errors like...

>> Could not execute statement.

>> In table 't', the START ROW ID value (1) must be greater than 3. Data

>> has already been inserted at this location.

>> -- (db_insrt.cxx 1855)

>> SQLCODE=-1000132, ODBC 3 State="HY000"

>> Line 1, column 1

SQLCODE -1002001 error in s_dpins.cxx:1349 "Data has already been inserted into index DBA.t.ASIQ_IDX_T943_C3_FP for row 1."

As concluded in CR 644807 this is expected behavior and the correct way to do this is either remove the DEFAULTS constraint or set DEFAULTS OFF on the load.

HOWEVER the error message in these situations is confusing and misleading. Customer would like a feature request to enhance this messaging to be more meaningful and report something like...

"you cannot perform partial loads in tables with column defaults, drop

the default to load the data and then add it again"

655755 Please refer to CR 652713 raised for this issue to do with Rowid not reused unless NULL is explicitly defined . IQ will only fill in unused rowids and reuse space during "full width" inserts or loads (so NULL columns must also be specified). This issue can cause an excessive amount of space wastage / fragmentation, however this is working as designed. Currently in development are improvements to column stores and compression which will help alleviate this problem.

However the documentation describing this behavior and the issues described in CR 652713 needs to be improved / clarified. In particular the documentation regarding partial width inserts are analogous to APPEND_LOAD='ON' in terms of rowid and space behavior needs to be made clear and that APPEND_LOAD='OFF' will only reuses the first available row IDs and space from deleted rows on full width inserts. If there are columns defined with NULLS these must also be included in the load or insert statement.

Also the documentation on Controlling Index fragmentation on page 88 of the Performance Tuning guide (IQ 15.2) (Chpt. 4 Managing Database Size and Structure) needs to be enhanced with this information and the aspects covered in CR 652713.

656232 The server could fail when running queries containing 2000 or more OR-ed equality conditions over a view that contains a many-arm UNION. This has been fixed.
656268 optimizer makes bad aggregation choice with a GROUP BY - grouped leaf used

Version: 15.2.0.5615/101123/P/ESD 2/Enterprise Linux64 - IBM pSeries 2.4.21-32.0.1.EL/64bit

Running the following simple select with GROUP BY is taking over 4 minutes and is resolved in the leaf node grouping using the HG index. The query plan shows this is being single threaded.

select count(*) from (

SELECT Col_A

FROM repro_grouped_leaf

GROUP BY Col_A

HAVING 1 < COUNT(*)

) D

Forcing aggregation_preference = 1 (prefer sort) and the query takes 30 seconds and it is resolved sorting the the data from the base table with 126 thread in parallel.

656995 Feature request for LOAD TABLE command to allow loading from compressed files. LOAD TABLE has been enhanced to load from compressed files. The compressed file-type is recognozed by the file extension.
657029 The IQ Server generated an incorrect result, if a query plan

had "Index BitMap Disjunction(parallel)" as the execution

method for a condition with an IN LIST clause.

657160 A SELECT query may throw exception "Non-Fatal IQ Internal Error" from dfo.cxx. "Internal error at node: # Can not evaluate expression" when the query has an

outer join node and scalar correlated subquery.

657332 IQ server aborts at st_server.cxx:1409 while generating graphical plan with statistics level 3 for DML statements like SELECT .. INTO, UPDATE in IQ 15.2 ESD 2.
657663 A query with a GROUP BY ORDER BY DESC clause failed with

"Internal error at GROUP BY node."

657690 A server failure may occur at s_blockmap::RegisterPhysicalBlockId() file s_blockmap.cxx line 2440. This failure may occur when trying to write a block with block id greater than 4GB. This requires a database large enough to have dbspaces with physical block numbers greater than 4GB.
657810 The IQ server failed with an error, if a select query had

more than 20 decimal elements in the IN LIST clause.

657962 -
657996 In attempting to connect to a Cluster Edition instance and it is unreachable, secondary or alternate instances (dataservers) are attempted, but a failure is returned to the IQ user and the connection is not established.
658446 LOAD TABLE incorrectly reported a data conversion error.
658660 A SELECT query sometimes returned an incorrect number (fewer)

of rows when all of these conditions were true: 1. Parallel

sort-merge join was chosen as join algorithm; 2. "Parallel

Output Order By" nodes were child nodes of a sort-merge join;

3. The IQ optimizer performed optimization on ordering

expressions.

659343 When executing a distributed query in IQ 15.3 with the QUERY_PLAN_AS_HTML option set, HTML query plans are created for each fragment executed on each server in the MPX in addition to the full HTML query plan for the leader node. If those HTML files are placed into a common directory, it is impossible to determine which server the query plan is from as the plans do not include the name of the server that executed the query.
659543 Table versions which are opened by read-only HOLD cursors may be incorrectly dropped during multiplex version collection (ev_iqmpxstatus). Later the connection holding the cursor may see random crashes during DestroyCursor. This problem only affects in multiplex setup and secondary nodes only.
659720 Signal 11 raise from s_LOBCursor when executing UDF
660003 -
661486 Query selects HJ instead of sort-merge and performs very poorly
661531 We should describe for configure.sh in manuals (Installation Guide or User's Guide).
661686 error msg for load table when it fails with duplicate column is not very descriptive,

Could not execute statement.

Duplicate insert column

SQL CODE=-637, ODBC 3 State= "42000"

Line 1, column 1

it should include line number and column name as well, as is for syntax error:

Could not execute statement.

Syntax error near 'Appropriate_Trade_Types' on line 77

SQLCODE=-131, ODBC 3 State="42000"

Line 1, column 1

661809 sp_iqdbspaceinfo and sp_iqindexinfo fail with error

Exception Thrown from db_iqutility.cxx:4893, Err# 14

O/S Err#: 0, ErrID: 2071 (s_dbextexception); SQLCode:

-1006002, SQLState: 'QBA02', Severity: 23

IQ Internal error.

Please report this to Sybase IQ support. db_iqutility.cxx

662657 In description of the following "CREATE DATABASE", the maximum of IQ SIZE is written to be 128GB. However, the maximum of IQ SIZE is extended to 4TB.
662704 CR#410218 fixed the stop_asiq script.

This is the issue as which a stop_asiq script does not show 15 or more PID. However, the actually fixed details are not correct.

This mistake was inherited IQ15.3.

A stop_iq script ignores 16 or less PID.

662737 -
662892 -
662926 Problem = when using a database created with collation ISO1LATIN1, a select with a GROUP BY on columns containing special extended characters returns an incorrect result.

This only happens if there is a LF index created on the column and only after a certain number of rows have been inserted. The data in the table is fine , just the result returned by the SELECT is incorrect.

663747 sp_iqcheckdb can not check join indexes
664053 "-ot" server option was added to IQ 15.x.

However, IQ server ignores "-ot" server option.

664276 Certification of Veritas Volume Manager, Cluster Server and Volume Replicator on raw devices for IQ simplex and Multiplex.
664721 IQ Server will make a fragment the packet which sends to a client, when character set conversion is valid.
664993 A query on two tables having multi-column HG indexes on a different set of columns which does sort merge join on the leading column in both indexes, gives non-fatal failure. This failure occurs in the presence of shadow query parallelism and OrderedLeafs.
665099 IQ gives non-fatal internal failure for a query which has a where clause containing a coalesce expression which is aggregated as part of an inner query.
665249 The server message viewer feature was added to entral from Sybase IQ 15.x.

This feature shows the result which called the sa_server_messages system procedure at a fixed period on the window of Central.

However, the method of setting this feature to disable does not exist.

Refresh rate = when 0 is set up, sa_server_messages is called at intervals of 1 second.

665254 Refresh Rate=999999999 cause the internal error of Central.
665482 SELECT query fails with non fatal error at dfo_Join.cxx:288 in 15.2 ESD 2.6 when Nested Loop

Pushdown Join algorithm is used.

665510 Full Virtual Encapsulated backup of READONLY dbspace will hang the client running it and prevent checkpoints being done.

1. Virtual backup _should_ be used with ALL type backup alone.

There is no value in using it for either RW or RO only backups.

2.The current CR is about virtual back RO DBSPACE hang.

This should be returning an error that a selective backup of RO DBSPACE isn't supported/implemented.

3. Documentation need to change to reflex this.

665764 Crash on select graphical_plan( 'SELECT * into #tmp FROM iq_table')
666196 The new option CORE_OPTIONS67 sets the rollover limit for

turning off tokenized FP to Flat Style FP. This is a PUBLIC

option and is DBA settable only. This option sets the

rollover point for all styles of tokenized FP. It

effects all indexes on all tables. To turn off creation

of FP(3), set this option to 65536. The next LOAD/UPDATE

to a FP index over 65536 distincts converts the index into

FLAT style.

666312 Occasionally when using the Distributed Query feature of IQ on heavily loaded MPX servers a leader node can crash if the distributed query is using a table that was modified in the same transaction and has uncommitted changes
666365 -
666612 In 15.3 GA, under some circumstances a query executed using DQP might return the wrong results when a column included NULL values and the NULL values were needed to compute the correct result.
666710 The IQ server returned an Internal error, when LOAD TABLE

handled large length user defined NULLs.

667051 LOAD TABLE cannot handle row delimiter of a fixed length file.

IQ will output error "said Missing row delimiter detected during a row delimited insert".

667147 The issue was caused by a bug in the server memory handling leading to stale memory reference. This has been fixed.
667221 When "LOAD TABLE" is executed, roll back on the first constraint violation.

The violation should bejavascript:save() written to the message and row logs, but it was not.

667231 The sample DDL of iq_dummy is not written to the reference manual of Sybase IQ15.
667235 In some cases, client was reporting generic error if it failed to establish the connection to the database server. Additional diagnostics have been added so the error messages are more informative.
667480 When rollover of '3' byte 'FP1' column to 'FlatFP' happens for a partitioned table, the value for partition-id referenced is incorrect, because of which we get 'internal state violation error'.

Fix has been done to fetch the correct partition-id value, when rollover of '3' byte 'FP1' to 'FlatFP' happens.

667725 The issue is observed when IQ inserts a CAST implicitly in join predicate where there is mismatch in datatypes for equated condition.
667898 Previously, if an application connected via jConnect and then subsequently attempted to use the {} JDBC escape sequence when making a stored procedure call, then there was a chance the server would return a strange "variable @p0 not found" error at the time the stored procedure statement or result set was closed. This problem has now been fixed.
668009 Sybase Central: Execution of "Refresh All" of table information

caused an internal error.

668312 A Data type conversion error is observed for datetime format 113 ('dd mmm yyyy hh:nn:ss:sss') when used in CONVERT fucntion.
668751 The issue occurs whenever a null-generating side of an outer join is a

flattenable view (or flattenable derived table) and the select list of the

view contains a constant expression (or an expression that can be

simplified into a constant expression). In such cases, the virtual column

should (according to ANSI SQL) have a NULL value for the outer rows

from the join, but the virtual column has already been eliminated by the

view flattening transform before the IQ optimizer ever sees the annotated

parse tree.

669566 This is a recurrent issue with copied postannotated parse trees which IQ and OMNI are generated: these parse trees may not contain valid SQL statements. When trying to annotate again these copied postannotated parse trees syntax errors maybe generated.

The parse tree to be copied in this issue is of the form :

select T1.FK as PK, T2.FK as PK...

after the postannotation which performed join elimination. This is not a valid SQL statement as it contains two aliases with the same name in the SELECT list.

669569 Fixed issue where the menu from mutliplex servers were out of sync. Specifically, ensure the "Execute SQL" option is available at the correct locations.
670092 New Feature Request to have options to suppress the "speculative execution" messages.
671012 IQ gives an non-fatal internal exception when the projection list of a query has a number of inter-dependent case expressions (one case expression as an argument to the other and so on).
671044 Customer Description:

select with group by and union all crashes IQ at _ZN9vp_Cursor10PreExecute on 152 esd 2 this has been corrected.

671160 The administrator guide of IQ15 is written to support jConect JDBC Driver for DBISQL/Sybase Central. But those tools does not support jConnect JDBC driver.
671406 Primary key table is not getting fully qualified before writing the ALTER TABLE SQL to the TLV log. The ALTER TABLE SQL introduces a foreign key to the table. Because of the unqualified DDL in the TLV log, the foreign key constraints were not propagated to the query nodes, sometimes resulting in inconsistent catalog entries, resulting in the internal bufman error.
671444 Sybase recommends using a fiber channel, rather than NAS

(Network Attached Storage) devices, for creating 15.x IQ

dbspaces. Using a NAS device for a Sybase IQ dbspace may

impact performance.

671463 A nested loop join executed using DQP returns wrong results when the columns being joined are not the same datatype (for example, char versus varchar) and an implicit cast is needed.
671544 The problem was caused by some in-memory cleanup that must be performed by the server periodically and was performed on every checkpoint; however, that cleanup doesn't need to be performed when checkpoints are executed in quick succession. Now, server will perform the cleanup during checkpoint at most once every twenty minutes.
671664 In rare circumstances when using multiple writers in IQ MPX the coordinator can become unresponsive when the periodic storage maintenance process happens on a busy cache.

If the periodic storage maintenance process uses a dirty page from the cache it can cause IQ server to hang

671767 IQ server hangs in simplex while running under heavy multi-user query load.
671898 Clarification being sought for wording in documents... The IQ 15.2 System Administrator Guide, Volume 1, page 456 states the following "The collation of the database must match the collation used by the operating system" - is this a new restriction brought in an why as it still appears you are able to do this without issues.
671933 Feature Request to improve TOP performance when used in a select with ORDER BY using DESC keyword. Request to improve IQ's ability backward naviagte the composite HG index to resolve the DESCending requirement in a manner similar to ascending.
672018 A query having an ISNULL expression in the select and groupby list and containing an outer join, gives a syntax error.
672104 A query could return an internal error at dfo.cxx 9060 in Sybase IQ 15.2 when an SMJ or SMPDJ node received input from its child in the wrong order.
672624 The STR() function of Sybase IQ has behavior which is different in AS/ASE.

When zero are set to be numeric-expression and two or more digits are set to be length, STR() is padding blank space back of value.

However, ASE/ASE will padding blank space head of value.

672893 DBISQL of Sybase IQ can set return-code to be an EXIT statement. However, it is not written to the manual.
673310 -
673475 IQ gives a non-fatal internal failure when a parallel group by (hash) operator is used to evaluate a group by query which aggregates average.
673581 LOAD TABLE command run many times slower in 15.2esd8 and later versions

than in previous versions whenever literal strings defined

for NULL must be checked.

673932 Notice is required when deleting the public option. As for change of a user option, the public option needs to exist.
673953 When account is locked using a login policy, the user with DBA authority cannot lock. However, IQ does not output a message about the reason which cannot be locked.
674317 Quotation marks are required for the argument of the READ Statement.
674439 A server failure may occur at

s_blockmap::RegisterPhysicalBlockId() file

s_blockmap.cxx line 2440. This failure may

occur when trying to write a block with block

id greater than 4GB. This requires a database

large enough to have dbspaces with physical block

numbers greater than 4GB.

674807 LOAD TABLE may stop processing if not enough buffers are available.
674881 A LOAD TABLE statement caused the server to fail in st_SAIQInterfacen.cxx with error "Unexpected resource deallocation error from IQ command which originated at s_bmCur.cxx:711."
674944 When authenticating IQ from SCC and using incorrect login information the wrong error is displayed.
675160 In 15.3 GA, certain parallel FP predicate operations are limited to 30 threads on a single IQ server, even if the server has more than 30 CPU cores.

This limit is removed in 15.3 ESD0.1

675425 Disable "check for updates" in DBISQL help menu
675601 If a query involves two or more joins of which first join is a self join of same view on primary key, it can cause IQ server to fail or become unresponsive.
675730 A message log archive is necessarily started from 0 at the time of IQ start. The existing archive file will be overwritten. However, the archive of a request log does not overwrite the existing file.
676047 If the documentation for alter database upgrade is not strictly followed and the server is not started with -iqro then alter database upgrade will fail if a VLDB license is not available. This will make it necessary for customers to restore from backup
676710 A truncate table command executed on a global temporary table

declared with on commit preserve rows may not truncate the

table if executed after some ddl commands. For example,

create GTT on commit preserve rows;

insert rows;

create hg index;

drop hg index;

truncate table;

Will not truncate the table.

677003 Connections that remained connected for long periods of time, for example beyond 24 hours, would report an incorrect LastReqTime. This value would drift away from the expected real time. This has been fixed.
677213 @@rowcount is not included in List of Sybase IQ Global Variables. But Sybase IQ supports @@rowcount global variable.
677283 For the following scenario:

create table p1 ( c1 int, c2 char(5), primary key( c1, c2 ) );

create table c1 ( c1 int, c2 char(5) );

alter table c1 add foreign key fk1( c2, c1 ) references p1 ( c2, c1 );

The foreign key creation should not be allowed. The

documentation is very clear that the foreign key must,

in this case, reference the primary key in table p1.

p1(c2,c1) is not the primary key.

We currently allow the creation of the FK and report an error

when INSERT is attempted.

677746 Don't refer to the changed user password for remote server connection of Sybase IQ.

When it connects with a remote server before password change, a password is saved into a cache. A password is not reflected in remote server connection until it reboots IQ.

678327 A query returns an invalid correlation name error if the same table has been joined with itself directly or indirectly on its primary key column and the columns from that table have been specified using OWNER.TABLE.COLUMNN" syntax in the query.
678702 The behavior of the IQ insert values logic has changed in 15.4 for integer values. The old logic always set the length to 4. The new logic will automatically convert integer values that are greater than or equal to -32767 and less than or equal to 32767 to a short and make the length 2. This will effect the display of the data if the display is binary format. For example,

insert table1 values ( 3 );

will now display in binary as 0x0003 rather than 0x00000003.

679248 IQ 15.3 "dbisql -nogui" does not display multiple results
680294 DBISQL of IQ15 does not support a binary format to OUTPUT.
680337 In a query with multiple joined subqueries containing GROUP BYs returns the wrong results, if the GROUP BY is on a constant(NULL).
680546 The following sql used to report error -118 Table has no

primary key.

create table t1 ( c1 int primary key );

create view v1 as select c1 from t1;

create table t2 ( c1 int );

alter table t2 add foreign key fk( c1 ) references v1( c1 );

The following error is now reported:

Error -729 The specified foreign key cannot be enforced.

680741 Under rare circumstances, Multiplex secondary writer nodes may become unresponsive. This may occur when the server's temporary cache is exhausted while performing main store read/write operations.
680763 The "backup database" command should continue to exploit the remaining available devices, even if one device in the target device list becomes full.
680825 Non-Fatal IQ Internal Error Detected

at s_dpidx.cxx:3457

occurs when running sp_iqrowdensity in a multibyte database

for an FP index on a longvarchar column.

681032 In IQ 15.2, a query using ISNULL() within an IF...ENDIF block might return the incorrect results.
681351 LOAD TABLE command run many times slower in 15.2esd8 and later versions

than in previous versions whenever literal strings defined

for NULL must be checked.

681549 In rare circumstances when using multiple writers in IQ MPX a bookkeeping error can occur that can lead to data corruption.

The bookkeeping error can occur if a transaction on the coordinator uses space freed by the periodic storage maintenance process and commits before the periodic storage maintenance process. If then the coordinator crashes or is killed before the next checkpoint, the crash recovery process will incorrectly mark the space used by the commited transaction as available for new allocation.

682518 If an application that was connected using Open Client or jConnect executed a Transact SQL batch that contained an undefined host variable, then there was a chance the server would have crashed. This has now been fixed so that batch will fail with a "Host variable is not initialized" error.
682609 IQ internal stored procedures indexname column definitions are defined as varchar(125) or char(125). Index names longer than this get truncated in the output from the sp. In IQ 15.x the default for option STRING_RTRUNCATION has changed , so instead of the index name being truncated you now by default you now get error message...

"Right truncation of string data. SQLCODE -638 "

This needs increasing to allow for longer index names. This is particularily so for procedures like sp_iqindexsize where the value put into the indexname column is actually made up of ownername.tablename.indexname

Other procedures that may be affected include sp_iqindexuse, sp_iqunusedindex and sp_iqjoinindexsize.

682644 A query with a probably_in semi-join condition into a column that contains many null values could cause a server abort.
682882 Feature request to improve performance of sp_iqemptyfile.
683016 IQ is designed to abort when it gets any error such as out of space condition while performing a privileged operation. We need a far clearer and less alarming error message for this.
683072 LEFT JOIN and IS NULL to a NOT NULL column grow up CPU of IQ to 100%.
683252 The following information was omitted from the Sybase IQ System Administration Guide. "Dropping a user from a multiplex writer while the user owns local objects (in local stores) on the readers can cause the readers to shut down. Before dropping a user, check for local object ownership on every reader and delete the local objects owned by that user on the local stores. After deleting local objects, drop the user on the writer. The deletion propagates to all the readers."
683266 In rare circumstances when using multiple writers in IQ MPX a bookkeeping error can occur that can lead to data corruption.

The bookkeeping error can occur if a global RW transaction on a secondary writer happens at the same time as the periodic storage maintenance process and the periodic storage maintenance process can free up the space still in use by the global RW transaction.

683487 A CONNECT USING statement does not work by DBISQL of IQ15.
683504 -
683632 Please add IQ server name in .lmp file
683961 @@identity always = 0 at INSERT table (col) SELECT 'constant'
683993 The DBSpace wizard would cause an error if a striping size was entered and then striping set to off. This has been resolved to ensure no error when striping set to off.
684434 SYNCHRONIZE JOIN INDEX randomly fails in db_join.cxx:3759, hdb_hjoinexception
684973 The -iqsmem switch for shared memory allocation will now support values greater than 512MB

on 64-bit IBM AIX platforms. Also the max supported limit for a single shared memory segment

on AIX64 has been increased from 256MB to 32TB.

684998 WITH expression of deraived table causes Assertion failed.
685165 In addition to the INSERT permission on the table, EXECUTE permission must also be set on sp_iqrebuildindex to users in order to rebuild the index on that table.
685728 The IQ scripts: IQ-15_3.sh and IQ-15_4.sh used a non-posix compliant test. This has been fixed.
686062 The server may stop processing while trying to get the

LastStatement properties of another connection while that

connection is attempting to commit or checkpoint.

686288 A query returns an invalid correlation name error if

- a table T is joined with table S on an attribute col1 which is a primary key in table S and a foreign key in table T.

- No other columns from table S are referred in the query.

- owners of table T and S are different

686296 IQ gives non fatal error in some specific scenarios where a group by and aggregate is performed on an alias which refers to a CASE statement.
686500 IQUNLOAD -au, -n, -ax_genscript faile "Feature, aggregate 'list' not supported"
686670 LOAD TABLE incorrectly reported a data conversion error and IQ Internal error.
687564 Group By operation associated with roll-up query does not execute in

parallel.

687679 An update to a table may stop processing while updating a multi-column primary key.
687899 IQ doesn't support WITH clauses.However, IQ reports an error, when SQL is run.
688101 Use the following workaround if the version of Sybase Central installed with IQ 15.4 cannot start after you install ASE 15.7:

1. Recreate the $SYBASE/shared/JavaHelp-2_0 directory JavaHelp-2_0, if necessary.

2. Copy the $SYBASE/IQ-15_4/java/jh.jar file to the $SYBASE/shared/JavaHelp-2_0 directory.

3. Reload or register the IQ plugin in SC, if necessary.

688120 Feature to select past versions of a given table similar to SELECT AS AT '<DATE>'

* Oracle has the "FLASHBACK" feature (SELECT AS AT '<DATE>') implemented since Oracle9i and has been improved in Oracle 10g & 11g

* PARACCEL (MPP database) has it on their roadmap.

When doing a SELECT AS AT '<DATE>' , the DBMS engine would provide a list of all the snapshot versions that were taken on that '<DATE>' for that table.

As with IQ , the snapshot versions only contain the delta of changes since the previous version, to reduce space requirements.

The FR would require a "snapshot" of a table after each version change for a specific period of time before it will be destroyed.

-> This will cost a lot of storage and based on a quick read up on the Oracle documentation this has some down turns.

688152 sp_iqcheckdb may report missing keys checking a

partition for a partitioned table

that has a multi-column primary key.

688319 While committing a global transaction on a coordinator, the coordinator takes ownership of blocks allocated by the corresponding writer transaction. The coordinator commits and updates bookkeeping structures as if those blocks were allocated locally. However, in certain cases, these blocks may be reallocated. Reallocation invalidates ownership transfer from writer to coordinator and writes incorrect information to the transaction log on commit. If the coordinator server fails before the next checkpoint, and recovery of global transaction uses incorrect data, inconsistent bookkeeping structures may result.
688429 IQ database paths may not contain a file extension when using a native file system file and will NOT contain a file extension when using a raw device path. Raw devices are a fully qualified path to a physical device attached to the machine, for example:

Windows:

\\.\E:

\\.\PhysicalDrive1

Unix:

/dev/md/rdsk/bigdb

/dev/md/rdsk/bigtmp

When creating a database, the IQ specific paths no longer check for a file extension, however the SA specific paths (.db, .log and mirror) still check for a file extension.

For the dbspace commands, the server will not require file extensions.

688452 The Sybase IQ 15.4 installer includes 'unknown' product edition and 'unknown' license type options. Sybase includes these options to accommodate potential problems in the license file where the product edition or license type may not be valid.
688884 The procedure sp_iqmodifyadmin exists only for backward compatibility with Sybase IQ 12.7. Use ALTER LOGIN POLICY to change login policies or configure logical server access.
688917 When using DBISQL to connect to the server, you might encounter the following error:

"You cannot user the Host connection parameter and advanced network parameters at the same time."

This has been fixed.

689051 The Sybase IQ 64-bit Windows installer might not install all oledb drivers.
689123 Join which used compressed FP index and Sort/Marge may cause a conversion error.
689608 A query returns an invalid correlation name error if

- a table T is joined with table S on an attribute col1 which is a primary key in table S and a foreign key in table T.

- No other columns from table S are referred in the query.

- owners of table T and S are different

- An alias is given to table T

689775 a query that uses a nested loop push down join and uses early predicate execution may abort.
690097 Support for binary and varbinary datatypes in Java UDF resultsets and

proxy tables was missing for sizes > 255 bytes. It has now been added.

690218 When a partitioned table resides on online and offline dbspaces, data of the table can not be accessed, if any data/index/partition of the table resides on the OFFLINE dbspace.

Also, sp_iqcheckdb doesn't check partitioned table with OFFLINE dbspaces.

To create indexes on a partitioned table, all dbspaces have to be online.

690233 Unable to effectively use TDS client packet sizes greater than 4096(max actually accepted by IQ is 7300).

So for example is you tried connecting with isql -Udba -Psql -Smyserver -A8192

the select connection_property ('PacketSize') will shows 7300. If you then try send a client packet that is 8192 in size this causes

CT-LIBRARY error:

ct_results(): network packet layer: internal net library error: Net-Library operation terminated due to disconnect

690299 On a machine under heavy load, a TCP connection attempt could fail with an incorrect error code. On certain operating systems, the connection attempt could hang. This has been fixed.
690354 iqunload may fail with "Feature, aggregate 'list' at line 0, is not supported."
690410 Writer nodes request coordinator for storage on demand basis. Coordinator maintains certain persistent and recoverable book-keeping structures to track writer allocations. After a successful allocation, these structures are passed to writer nodes so that they can update their local storage structures. If a checkpoint occurs after coordinator creates allocation structures but before it commits them, coordinator allocation transaction loses ownership of the newly created structures to checkpoint. During commit, coordinator transaction creates its own copy from checkpoint owned allocation structures. However, writer node still receives checkpoint owned copy for local update. In a rare scenario, if another checkpoint happens before writer can update the local storage, checkpoint owned copy gets destroyed. Any further update by writer using destroyed copy can result in database crash.
690664 The IQ server crashes if query has HASH JOIN and due to incorrect estimates

the runtime rehashing is required.

690706 Feature request for IQ to use timezone different from local Windows machine timezone, so that getdate() return date/time is base on IQ specified timezone instead of Windows machine timezone.
690939 Improved Load performance of tables having text indexes.
691158 Attempting to make a Kerberos connection with a large Kerberos ticket could incorrectly fail with the error "Kerberos login failed". This could occur with Keberos ticket size approaching 8K, which was possible if the ticket was part of a large number of Active Directory groups.
691164 IQ 15.3 windows network client installer only installs dboledba11.dll, dboledb11.dll is missing. The server installer has it.

also problem with IQ 15.4 installer where dboledb12.dll is missing.

691275 need a switch implemented that disallows checkout of any optional graced license if someone inadvertently tries to use an unlicensed feature
691465 When using the fetch_block() UDF api to retrieve rows from an input table 1 row will be lost for every subsequent block fetch. This is now fixed.
691527 Server failure may occur in st_txncb.cxx when a sql batch is interrupted

by a DROP CONNECTION command.

691609 The JDBC driver sajdbc4.jar might not be installed on Windows.
691733 Recommendations in "MAIN_RESERVED_DBSPACE_MB Option" in Reference: Statements and Options and "Sizing guidelines for main and temporary stores" in System Administration Guide: Volume 1 seem contradictory, but sizing for MAIN_RESERVED_DBSPACE_MB depends on many factors, such as IQ page size and the number of concurrent connections. Set MAIN_RESERVED_DBSPACE_MB to at least 20 percent of the IQ_SYSTEM_MAIN size.
691756 The failure was caused due to access of invalid memory in queries with hash join. The issue is specific to Linux Power Series. This has been fixed.
691839 A derived table that contains UNION ALL and SCALAR correlated subqueries with

conjunctive condition causes the query fail with a non-fatal stack trace at

opt_TableNode.cxx.

691845 The documentation for the sp_iqspaceused stored procedure had inaccurate descriptions for the tempKBUsed and shTempTotalKBUsed columns. tempKBUsed is the number of kilobytes of total IQ temporary store space in use by the database. shTempTotalKBUsed is the number of kilobytes of total IQ global shared temporary store space in use by the database. (Secondary multiplex nodes return '(Null)'.)
692222 If an attempt to insert a value requiring implicit conversion

into a column that results in a conversion error, previously

inserted, uncommitted values are rolled back.

692449 a DQP query under certain circumstances can be slower than the same query run non-dqp
692460 Executing a SELECT * from a procedure that includes an INSERT fails with a non fatal error at df_Heap.cxx:2613 when one of the parameters passed in exceeds the defined parameter length. Subsequent queries from the same client fail with "CURSOR ALREADY OPEN" errors.
692519 If an application connected via jConnect or Open Client to a blank padded UTF8 database and fetched a non-nullable char(n) value, then the client may experience protocol errors if n is less than 3. This has been fixed.
692528 Feature request monthname(getdate()), datename(mm,getdate()) to return localized Japanese month names when LANG is set to Japanese. Also request to support additional languages.
692572 New feature request to allow a way for temp objects to only exist in cache, never to be written to disk unless temp cache gets full.
692575 allow mpx dqp queries to work across locations (if Frankfurt needs London data it will split off part of the query and send it to the London server to get that data for example)
692599 If the server is started with a TLS/HTTPS identity file that requires a password but none is supplied, an unhelpful error message is given ("Error parsing certificate file, error code 20763").

This has been fixed; the error message is now "An identity password must be specified".

692694 The 15.4 documentation describing the permissions required for these permissions is incorrect:

DEFAULT_PROXY_TABLE_ROW_COUNT Option

DEFAULT_TABLE_UDF_ROW_COUNT Option

TABLE_UDF_ROW_BLOCK_CHUNK_SIZE_KB Option

DBA permissions are not required for these options.

692802 Under rare circumstance the server might incorrectly parse the SQL statement for a procedure and result in a crash. This has been now been fixed.
693033 If a column has a data type VARCHAR or VARBINARY greater than 255 bytes, sp_iqrebuildindex does not rebuild a default index. This problem was erroneously reported fixed in the 15.4 Sybase IQ New Features Summary.
693109 When a partitioned table resides on online and offline dbspaces, data of the table can not be accessed, if any data/index/partition of the table resides on the OFFLINE dbspace.

Also, sp_iqcheckdb doesn't check partitioned table with OFFLINE dbspaces.

To create and use indexes on a partitioned table, all dbspaces have to be online.

693122 a union all query may abort in df_heap.cxx: 12140
693311 Modifying a column data type using alter command is not supported.
693421 In the 15.4 Release Bulletin, the section "Network Clients and ODBC Kits" should state: Sybase IQ Network Clients and ODBC kits for development are available on the Sybase download site. A Network Client is available for each platform supported by this version of Sybase IQ. The Linux 32-bit client is also available. The Sybase download site is http://www.sybase.com/downloads.
693648 LOAD TABLE with 3 char ROW DELIMITER ';]\x0a' can not always load the data files
693662 IQ 15.4 and all previous versions of 15, sp_iqdbspaceinfo lists objects residing in a dbspace, customer require ability to list objects residing in a specific dbfile
693833 A query might cause datatype conversion error at dfe_Cast.cxx : 918 and subsequent IQ server failure at hos_mem.cxx:243 while converting varchar column value to numeric datatype.
693904 The following was omitted from the LOCK TABLE statement in Sybase IQ Reference: Statements and Options. Using the WITH HOLD clause in the same statement with WRITE MODE is unsupported and returns the error SQLCODE=-131, ODBC 3 State="42000".
693905 Lock Table: instead of syntax error, return meaningful msg: 'with hold' and in 'write' mode are not allowed in same statement
693970 Customer would like extra diagnostics about objects involved when hitting errors like..

I. 12/19 01:29:26. 0001304510 [20895]: Insert Pass 1 completed in 2 seconds.

I. 12/19 01:31:19. 0001304510 main Bufman: Incorrect page header read;

buffer={btype=12,nlb=16,blk=11084,pbn=447979368,npb=7,uid=1387737518,txn=418596030,sp=1,flgs=0x818 page={btype=12,nlb=16,npb=16,ctr=131,cta

I. 12/19 01:31:19. 0001304510 =131,pbn=447979368,txn=418039238,sp=844,ver=1,pb=104,pus=43966}.

s_trycatch.cxx:1549

I. 12/19 01:31:19. 0001304510 There was an s_buf::Read() error during s_bufman::Find().

I. 12/19 01:31:19. 0001304510 Exception Thrown from s_blockmap.cxx:4469, Err# 0, tid 1089 origtid 1089

I. 12/19 01:31:19. 0001304510 O/S Err#: 0, ErrID: 2100

(s_corruptdiskblkhdrexception); SQLCode: -1009039, SQLState: 'QSA39', Severity: 14

I. 12/19 01:31:19. 0001304510 [20060]: main Bufman: An error was detected on a database page. You may have a damaged index. For additional information, please check your IQ message file or run sp_iqcheckdb.

694467 Customers using Sybase IQ/CIS on SunOS version 5.10 Generic_144488-04 to access remote ASE tables using the 15.7 ASE ODBC driver will get the following message:

"Error when attempting to connect: Unable to connect to server 'MYASE': [Sybase][ODBC Driver Manager] Unable to load driver"

To connect, install the June 30, 2011 OS patch bundle. Kernel version: SunOS 5.10 Generic_144488-17

694685 If a NON zero return status produced by script called by a BACKUP DATABASE FULL VIRTUAL ENCAPSULATED command IQ is not picking this up and not throwing an error on Linux Redhat. Instead the backup is treated as sucessful.
694840 When execute a Java UDF in IQ the server might crash when trying to right truncate data for a binary column whose size is greater than 256 bytes. This has been fixed.
695298 In Sybase IQ 15.4 > System Administration Guide: Volume 1 > Sybase IQ Indexes > Criteria for Choosing Indexes > Number of Unique Values in the Index, the documentation stated that the recommended index type for less than 1000 unique values is HG when the table has <25,000 rows. This is incorrect. Sybase recommends using the HG index when the table has <100,000 rows.
695461 While performing a database backup that required multiple tapes,

the backup stopped with error "Unable to write to archive"

shortly after displaying the message prompting to load tape #2.

695758 SELECT .. UNION SELECT .. ORDER BY COLUMN could returns The field 'COLUMN' specified in the query cannot be found
695904 Customers might experience an error while trying to create a raw database on Windows 2008 R2. This has now been fixed.
695918 In a MPX, if the column id of a table is greater than 65535 and any DML operation is done on the table, during TLV replay the secondary servers will abort with SEGV
696059 There was an issue in the parallel HG index insert logic which could lead to an inconsistent index. The load/insert used to throw a non-fatal error from HG index logic.

This issue has been resolved.

696213 Out of sync R/W lock may cause secondary node emergency shutdown. It is an expected server behavior.
696317 PATINDEX could return wrong results for wildcard chars and latin special chars
696396 NFR: Allow extraction of data from mixed on and offline partitioned objects
696563 A bulk insert of large object data using host variables

will insert, for each

row, the same value that was inserted to the same column

in the first row inserted.

696673 If bulk inserts are sent to the server and one encounters an

error, previous successful bulk inserts may be rolled back.

696880 RESTORE cause utlity_db crash on s_buf*s_blockmap::Find
696885 Assertion failed: 109512 Freeing already-freed memory on SELECT TOP
696982 A query with right outer hash join node could return internal error at s_csort.cxx:3161

in IQ15.4 while sorting output from right outer hash join node.

697069 The LOAD TABLE clauses BLOCK FACTOR, BLOCK SIZE and UNLOAD FORMAT are deprecated. IQ nolonger accepts this syntax and will return syntax errors if these clauses are used.
697153 SybaseIQAgent15 would fail to start the IQ Server if the Windows environment variable PATH was greater than 1024 characters.
697211 A new version of the Sybase IQ 15.4 Quick Start Guide on the Sybase Product Documentation Web site includes some path name changes. Some sections in the 15.4 Quick Start Guide use a variable as part of the path where an absolute path may have been more appropriate. The revised Quick Start includes full and explicit path names.
697212 A new version of the Sybase IQ 15.4 Quick Start Guide on the Sybase Product Documentation Web site includes some path name changes and a note on distributed queries.

Some sections in the 15.4 Quick Start Guide use a variable as part of the path where an absolute path may have been more appropriate. The revised Quick Start includes full and explicit path names. A change in the Running a Distributed Query section notes that the query engine may choose a query plan that does not distribute to the write server.

697314 Sybase IQ has been upgraded to Sybase Open Client 15.7. This will be automatically installed with version 15.4 ESD #1 and up.
697490 The SCC online help for Sybase IQ does not contain information on recent changes to the SCC security modules. See the SCC 3.2.6 Release Bulletin for the updated documentation.
697746 discrepancy in the representation of floating point numbers to the IEEE 754 standard in any version of IQ.

4.70000000000000028865798640254E-1 is the most accurate representation of 0.47000000000000003 for double precision in the IEEE 754 standard But IQ chooses a slightly different representation of 0.47000000000000008437694987150000000000000000000000 when retrieving the number stored in a DOUBLE datatype when using a select convert ( numeric(126,50)

698044 A non-fatal error occurred on NTILE and RANK functions run on tables of a million rows.
698206 This a doc enhancement request regarding the minimum permission's setting for the $IQTMP15 directory.
698347 IQ 15 checkpointing more frequently and spending more time on checkpoints than 12.7
698374 If the identity_insert option was set for a user on a table owned by a user other than DBA, iqunload would be unable to set that option on the new database. This has been resolved.

Workaround: unset the identity_insert option for that table prior to running iqunload and re-establish it on the reloaded database afterwards.

698573 Server failure may occur when loading data with logging turned on and there are

default values for a column.

698659 When the database option Max_Query_Parallelism is set to a decimal value instead of an integer, IQ server can crash.
698811 Feature request. IQ to allow users with expired password to connect and be prompted to change the password as ASE does.
699014 There was a 508 issue where keyboard access in the Domain Wizard did not work properly.
699206 IQ could crash when running multi-table UPDATE when one of the tables is a proxy table.

Multi-table UPDATE is not allowed. It will fire an error instead of crashing

699327 Fixed an internal memory corruption error causing server failure.
699486 A selective restore of a RO dbspace with RENAME to a raw device where the TO device name alread exists causes restore error like this...

Could not execute statement.

Dbspace file with name or path '/dev/rdsk/c1t6d0s2' already exist.

SQLCODE=-1234, ODBC 3 State="42000"

Line 1, column 1

Investigative CR to see if this is expected behaviour / document clarification

699969 Migration from 12.7 to 15.4 could fail if on on 12.7 there is a proxy table to ASE and an index on that proxy table exists.
700118 On data set with large numner of rows, a query resulting aggregated values with large precision and scale via aggregate functions that has a subtree that predicts aggregate value size undergoes shadow transformation might hit an validation error at dfo.cxx:9638 on 15.2 esd 2.x. This has been fixed.
700166 Previous installers did not stop and delete the previous SCC version window service. This has now been fixed.
700647 sp_iqversionuse fail with Function 'hextoint' has invalid parameter or return negative version IDs.
700675 Feature request to reduce disk i/os when doing insert select into temporary table.
700886 Execution times of prefetches increased when comparing IQ version 15 with previous Sybase IQ releases. This has been fixed.
700980 1. The unhandled datatype exception is observed when host variable of type date with 6 digit precision in declared application using jConnect client 5.X onwards, used in query running on IQ table.

2. The Secondary error is observed when query has Sort Merge join executed serially and early resource release option is disabled.

701039 Added new database option 慉ES_Encrypt_Header_Format� for decrypting data upgraded from 12.7 to 15.x or imported from 12.7 to 15.x.

Option usage:

SET OPTION public. AES_Encrypt_Header_Format = VAL ;

Where 慥AL� is an integer and it can have the following possible values:

-1 -> Default: format is that of current release. Data is encrypted and decrypted using the same release. e.g. data is encrypted on 15.3 database and decrypted on 15.3 database.

127 -> Set this option to decrypt data if database is upgraded or imported from 12.7 release. e.g. data is encrypted on 12.7 database and it is upgraded to 15.x.

153 -> Set this option if data is from previous 15.3 release. e.g. Data is encrypted on previous 15.3 database and decrypted on next 15.x release.

154 -> Set this option if data is from previous 15.4 release. e. g. Data is encrypted on previous 15.4 database and decrypted on next 15.x release.

1000 -> Data is from fixed releases.

701052 Grant multiple authority to multiplex users does not propagate on secondary

nodes.

701085 Contents of Permissions of alter index and alter table are not corret.

alter index not required RESOURCE authority.

alter table not required CREATE permission on the new dbspace and be the table owner.

701097 IQ15.4 includes 15.2ESD#3 and 15.3GA updating.
701116 Japanese file name containing "0x5c" makes Temp_Extract fail.
701326 As of 15.4 ESD #1, Sybase IQ no longer supports elliptic-curve

cryptography (ECC) encryption.

701447 Backup FULL and INCREMENTAL a database older than 30 days that has and uses the VLDB license.

On a installation that has no license at all, RESTORE FULL would succeed

but then even after installing a valid VLDB license, the subsequent RESTORE INCREMENTAL could faile with error:

Msg 21, Level 14, State 0:

SQL Anywhere Error -1012008: Database has changed since last restore.

-- (db_backupID.cxx 617)

701474 IQ Multiplex Coordinator node statistcs: No data was found for statistics
701641 In DQP, a simple SELECT COUNT(*) FROM TABLE WHERE COL like '123%' could return incorrect values.
701907 New Clickwrap licenses were received for Australia and Japan.

These have been added to the installer.

701953 A query that contains a parallel orderby over a union with constant values for a column in all arms of the union could fail with an internal error.
702246 32-bit GNU C Libraries package (glibc-2.xx-x.xx.el6.i686.rpm) also need to be installed before installing IQ 15.3 or 15.4 64-bit to a Redhat Enterprise Linux 6.x x86_64.
702363 When proxy table to an Oracle table is created, IQ plug-in maps NUMBER (5,2) to a different type.
702419 When backup full is taken on a coordinator and if it crash,

backup incremental is taken on the new coordinator (failover server),

then restore full or incremental can faile.

702433 dbisql for IQ 15 returns columns in fixed width necessitating resizing to see longer data which is not persistent. 12.7 returned data in variable length columns display.
702454 With IQ 15.4 esd 1 on Windows platform, when you run "iqdsedit" it is missing the network protocols from the drop down box.

This has now been fixed.

702845 A Max_Warnigs option does not affect IQ server. The description about this option will be removed from a manual.
702999 An insert..select query caused the server to crash when the record length exceeded the max record length a Parallel Combiner node can support.
703390 IQ 15.3: LOAD TABLE ... USING CLIENT FILE in SP prompting for options to be ticked

The issue is not with the load table command itself but with calling a stored proc with the load table command in it. If you create a stored proc with the load table command inside and call that stored proc you will see the prompt. (screen prompting for options to be ticked...etc)

(DBA)> call test_load()

A procedure or trigger is requesting to read the file 'E:\temp\BA_F_JOUR_MOUV.out'.

1. Allow this transfer

2. Deny this transfer

3. Allow this and all subsequent transfers for this connection

4. Deny this and all subsequent transfers for this connection

Select an option: 1

2 row(s) affected

Execution time: 5.719 seconds

The customer would like a option similar to set temporary option isql_allow_read_client_file = 'ON' that will prevent the default PROMPT action. Perhaps enhance ALLOW_READ_CLIENT_FILE = 'ON' to have an option like ALLOW_READ_CLIENT_FILE = 'ON NO PROMPT'

703526 when "OFF" is set as a CONTINUE_AFTER_RAISERROR option, procedure does not stop after a RAISERROR statement.
703878 When using a NOT EXISTS subquery, IQ may generate a non fatal internal error when tables are created with minimized storage option.
703882 A non-fatal error occurred on NTILE and RANK functions run on tables of a million rows.
704146 IQ 15.4. Writer crash randomly in hs_csortInsertPkg::NextLoc().
704248 SySAM loses checkout message in a Japanese language environment.

An issue will be reproduced when ja_JP.eucJP and ja_JP.SJIS are specified.

704298 Add non-equijoins by transitivity. When the where clause has these conditions:

T1.c1 >= T2.c2

T2.c2 = constant

then IQ should automatically add this condition:

T1.c1 >= constant

704302 Sybase Central crashes when filter objects by dbo and click on events folder.
704383 A query with two "IN" clauses may return an incorrect result set.
704771 GA version release notes no longer contain CRs fixed in that GA version
705105 make Data movable when splitting a patition in IQ
705108 NFR: possibility to change data in the partitioned key in IQ

Currently data in the partitioned key can not be changed (even if the data will be afterwards in the same partition).

705288 IQ 15.4 on Linux may have I/O failure if the storage devices are raw disks with sector size other than 512 bytes.

There is no work around.

705510 Nested loop pushdown (NLPD) join with more than one uncorrelated IN subquery crashes at st_server.cxx:1412, server abort at dfo::CheckMarkInvariant.

The problem is fixed.

705535 Bookkeeping errors could be caused when all secondary servers are excluded and then immediately the coordinator is killed. During crash recovery the coordinator does not recover the bookkeeping records correctly and can cause database corruption.
705829 sp_iqsysmon/IQ UTILITIES display cumulative InUse% for temp cache and and does not decrease even the temp cache/buffers are released.
706080 The GNOME desktop manager of RHEL5 mounts a DVD volume name to "/media."

However, the blank is included in the IQ15.4 DVD volume name.

IQ15.4 installer is not supporting the file name/path including a blank.

706098 this is a deadlock due to lock order violation due to a defect in IQ. It is a timing dependent issue with no work around
706184 When a client side load operation is either aborted by user, the signal on the thread handling it is not cleaned up. When such thread picks up any other request in future, the new thread gets aborted as well.
706824 If a jConnect or Open Client connection prepared a statement and called a stored procedure with a set of host variables, then the server could have crashed or returned an odd "variable already exists" error if the stored procedure had a parameter or variable named @p0. This problem has now been fixed.
707370 A query that contains an orderby operator with many thread and many sort

runs can use excessive memory.

707398 Fix of issue within the alert subsystem where new alert for MPX node shows twice in the alert table
707612 On the Windows platform only, a random query may abort in st_server.cxx:675 or 690 and leave the connection in a state where it cannot be dropped without restarting the server.
707649 Some queries perform poorly because the IQ optimizer evaluates the less useful predicate(Invariant) first rather than the most useful predicate.
707865 And a lot of data(eg. 50000 rows) was inserted in the table using Load Table.

However, Load Table makes a gap to the value of an AUTOINCREMENT column.

707992 Query using the Rank or the Row_Number function with a partition by clause may return incorrect result.
708061 Toggling the radio button for data type, built-in or domain, did not properly update the system defined list.
708197 add support for global autoincrement that guarantees uniqueness across whole db even when a transaction rolls back (so that no two transactions can get the same value, no matter what commits and what rolls back)
708205 implement autonomous transactions to allow persistent logging no matter whether transaction commits or rolls back
708818 If a user cancels a load operation, the response time to the cancellation request is not adequate. It may take longer for the IQ server to respond to cancel the load transaction.
708860 In order that IQ15.4 is using the path for some Symbolic Link absolutely, it cannot copy an installation image to a different path.
708892 Unable to get task scheduled in windows 7 task manager for an Infoprimer project, 32 or 64bit
709160 erroneous handling of isnull() resulting in division by zero exception
709231 In IQ 16 ALPHA, a hash partitioned table has the following restriction:

All columns in a hash partitioned table must be fixed-width data types and flat (i.e. IQ unique(0)).

709904 NFR: implement ability to push filer predicate down to view or leaf level.
710047 Official answers for compatibility IQ 15.4 + ASE 15.5 + SDK 15.7 ESD3
710054 IQ 15.4 sends wrong char length to JDBC clients when those conditions are met:

- IQ 15.4 runs on LINUX64

- collation must be UTF8

- JDBC retrieves a CHAR column value.

This results in JDBC clients getting "End of data" error.

710120 Table's dbspace for a partitioned table was consuming more space than expected. This fix resolves this issue.
710169 InfoPrimer15.3 installer of the UNIX edition shows Japanese License Agrrement by UTF-8.

License Agreement could not be read when OS character set is except UTF-8.

710208 IQ can report a non-fatal internal error from dfo_Ranking.cxx when there is an uncorrelated subquery on top of a ranking function.
710418 Sybase IQ 16.0 Alpha does not support INSERT LOCATION, BEGIN/END PARALLEL IQ, secondary file LOB LOAD and some other LOB Functionality, the WD and TEXT indexes, database upgrades, or referential integrity (Primary/Foreign Key relationship not enforced).
710442 Fixed a condition where dbstop failed to shut down the IQ server.
710657 On non-Windows platforms, the ROUND SQL function may return a different value from an IQ table than from an SA table. For example, a call of ROUND(convert(double,0.5), 0) returned 0 from an IQ table whereas the same call returned 1 from an SA table. A customer may want to have 1 as the returned value in this case.
711339 data type conversion is not possible dfe_Cast.cxx:918 when data contains blanks, expected behaviour as we can not convert a ' ' blank/space to a numeric. However there is an issue where using MINIMIZE_STORAGE='OFF' and WHERE clause, the convert error is ignored and the query is allowed to run through which is incorrect.
711351 CREATE or ALTER LDAP SERVER takes over a minute to execute when setting the SEARCH DN access account password on some platforms.
711731 Server crashes with CREATE USER and ALTER USER statements with password when VERIFY_PASSWORD_FUNCTION is enabled in 15.4.
712235 When restoring from backup, customer would like the ability to use the RESTORE .... RENAME to change / manage which raw device a dbfile should be restored to (i.e. swap around and reuse existing definitions)

For example if the system backed up contains MY_DBFILE1 on /dev/raw/raw1 and MY_DBFILE2 on /dev/raw/raw2, they wish to be able to restore this swapping which raw device the dbfile resides on, something like this...

restore database '/mydatabase.db'

from 'my-backup-file'

rename MY_DBFILE1 to '/dev/raw/raw2'

rename MY_DBFILE2 to '/dev/raw/raw1'

The currently can not do this as the restore logic and the UNIQUE constraint in ISYSDBSPACE (as identified in CR 649181) does not allow this so you get this error...

Could not execute statement.

Dbspace file with name or path '/dev/raw/raw1' already exist.

SQLCODE=-1234, ODBC 3 State="42000"

712250 While one can create 2 indices of same name in different case, one encounters an 'ambiguous index name' erro trying to drop either variant
712256 sending a NaN for a double form a .net app can crash server dumping core.
712373 Using insert-location to insert time data into a time column

from a time column on a remote IQ server results in error

"Cannot convert to time."

712378 Customers are asking for Sybase to provide a DDL extraction tool as part of the product that works just as well as the 12.7 to 15.x migration tool iqunload.

There is also a specific requirement for this to also be able to extract the user id with password.

712540 Syntax error near 'tables' on line X at end loop if tables is used as a loop name
712589 The union operation now supports up to 2048 table references instead of 512 table references.
712709 A server failure could occur when a query has an IN clause with a subquery that has a filtering condition.
712751 When using ODBC access to MS Access through IQ, you might encounter an error when exporting a table:

Column 'X' has an unknown datatype: 'nvarchar'.

-- (db_catalog.cxx 1162)

This has now bee fixed.

712782 Growcapacity was being called everytime and the release memory was

with the process. This was a major problem once the object size was big.

This use to consume a lot of memory of the system heap thus choking

the memory availability for the process/application.

712864 NFR: implement JDBC driver load balancing between IQ servers
713182 A server failure could occur in s_dpByteFetch::GetDistinctCount while running sp_iqcheckdb on a database containing a corrupt FP index.
713301 AUTO_COMMIT/COMMIT_ON_EXIT is due to discontinue.

But IQ15.4 can use these options.

713838 A Non-Fatal IQ Internal Error Detected at opt_Driver.cxx may occur during a query with a nested loop pushdown join (NLPD). The query will also have an incorrect result.
713919 Events were prevented from being triggered when the coordinator was down. This was not a requirement for the event to be triggered and has been removed.
713941 sp_iqshowpsexe reports data under the incorrect column headers. MAX_STATEMENT_COUNT is reported as 'max_cursors', and MAX_CURSOR_COUNT is reported as 'max_statements'.
715010 Explicitly passing in null as the 3rd parameter

(algorithm) to the encrypt or decrypt function will result in the error

-973 "The string is too long (Parameter 3)", rather than having the

encryption/decryption default to AES128. The work around is to omit the

argument.

See "Known Issues" for more information.

715165 Index advisor may write a message advising rebuilding of index with minimize_storage = on, even though the option is already on in the IQ message file
715316 LOAD TABLE may stop processing if not enough buffers are available
715562 need to document that [T|t]ables is now reserved word as of 15.4
715563 need to document that [T|t]ables is now reserved word as of 15.4
715567 IQ documentation enhancement request to improve details and examples on how to set and define IQ-to-ASE connections with ODBC on Unix/Linux.

There is an excellent article published by Rob Vershoor highlighting this located at http://www.sypron.nl/iq_ase_odbc.html.

715677 server abort in an_id_hash_table::clean()(st_server.cxx:1430)
715997 Certain queries could return different results

- when it is run on Simplex or MPX.

- when it is run several times on MPX

716303 A server failure may occur in s_btParallelCursor::SetDeleteNotifier

when trying to insert a duplicate key.

716358 This resolution fixes an issue which occurs if you go to add an alert to a multiplex and in the alert wizard select on the first step a specific node, or even drill down a bit under that node, then on the Duplicates step all the other nodes for that multiplex should be listed.
716554 Buttons on Table Wizard -> Partitions page not disabled/enabled properly in SCC.
716563 A query containing a Group by over a column with an empty string value reports an IQ Internal error (opt_QueryExp.cxx 309).
716988 incorrect result with nested exists clause
717018 Updated the synchronize server script to allow correct logon.
717140 In IQ MPX on secondary server, call to VERIFY_PASSWORD_FUNCTION is skipped when new password is specified through GRANT CONNECT, CREATE USER and ALTER USER statements.
717361 Conversions on the result of DATEADD could return different values depending on whether the query is executed on the catalog or on IQ, due to the fact that:

select datalength (dateadd(hh,4, date(now()))) from dummy ==> returns 8

select datalength (dateadd(hh,4, date(now()))) from iq_dummy ==> returns 4

717555 sp_iqpassword fires" Syntax error " when the password contains special chars

such as: "!" , "?", "+" , ">" , "<" , "�" , "|" , "*" , "&", "(", ")", etc

717572 A select query with IN sub-query, which compares numeric columns of IQ and "IN SYSTEM" tables may give wrong results.
717619 The Text Index page for table properties was giving an incorrect error about permissions to access functionality on the page.
717877 Fixed issue where a new Text Index would be edited before it is officially created (applied).
718091 A query with outer join, group by and nested CASE statements containing columns from both the tables involved in join may result in exception at dfo.cxx:9689
718155 The DDL created for a Foreign Key was incorrectly including the "NOT NULL" clause.
718373 A 15.4 resource would indicate the user did not have correct authority on the constraints page. This has been resolved.
718919 DQP Query run on reader crash coordinator/writer on hos_dtkeycmp_dtdate
719383 The query below returns wrong result when Nested loop is not used :

select count(1)

from REL_1_CityASM t1

join F_PUP_OrderHeader t2 on (cast(t1.Object_ID as bigint) = t2.PUP_Order_ID/1000000000)

join LU_Cassa t7 on (t1.Object_ID=t7.Object_ID )

where t1.ASM_ID=23

and (REMAINDER(t2.PUP_Order_ID,1000000000) <> 0)

719590 On a machine under heavy load, a TCP connection attempt could fail with an incorrect error code. On certain operating systems, the connection attempt could hang. This has been fixed.
719831 There can be a failure to authenticate when using certain collations.
720503 Space allocation may fail with error "DBSPACE is INVALID" trying allocate physical block numbers greater than 4GB.
720539 INSERT LOCATION performance drops 10 times slower from 15.2 to 15.4 esd 2
720584 jConnect: Request to enhance performance of the Connection methods: .isClosed(), .isReadOnly() & .getAutoCommit()
720701 intermittent st_server.cxx:1412 crases at calls hos_key_uncondA_dtint64 , s_packedRec::DeliverRec
720782 The Text Configuration Wizard did not give an appropriate error for resource user when they attempted to create as a user other than self.
720912 DROP USER will drop any objects owned by this user AND ALSO THE PERMISSIONS GRANTED BY THIS USER WILL BE REMOVED.

Please see reference for the REVOKE CONNECT command in the SA manual:

http://dcx.sybase.com/index.html#1201/en/dbreference/revoke-statement.html .

721615 During load table with header skip option attention check was responding after very long time. This fix resolves this issue.
721667 You cannot create a table with partitioning if you specify that columns are stored in a different dbspace from the table. The workaround is to create the table, place the columns where you want them, and use Table Properties > Partitions to partition after creating the table.
721949 incremental backup crashed st_server.cxx:1409 at _int_free call. This happens right after the backup process completes but before the final checkpoint completes.
722006 Fixes update crash on an RLV enabled range partitioned table.
722122 analysis of the request log containing a CALL statement needs huge catalog cache.

For example, when 50MB of request log contains 30000 times of CALL statements, request log analysis uses 170MB of catalog cache.

722155 running xp_cmdshell from an IQ server on Linux where the execution gives all the appearance of having been successfully run in IQ , but in reality nothing happens. The unix command, even if it is just a touch file, does not execute. It appears to have something to do with when the child process is spawned it seems to think it needs as much virtual memory as the parent process (the IQ server in this case) . The resolution almost always is to make sure that the swap space is at least 1 x the amount or RAM being used by IQ. This is related to CR 633354 - this feature request if to try find a better way to make this unix call / improve the message handling.
722336 This resolution addresses a heat chart issue where alert related information is not accurately reflected unless the chart is refreshed
722356 "SQL, HOSTVARS, PLAN, PROCEDURES, TRIGGERS, OTHER, BLOCKS, REPLACE, ALL and YES, NONE, and NO" can be specified to be "-zr" database starting options.

The details written to the IQ15Utility guide are not correct.

722462 When using distribited query processing in a MPX environment, IQ may crash when using a technique called early grouping sort and hash joins
722485 User with the CREATE TABLE privilege will be prevented from proceeding in the table wizard if they select a user other than self.
722560 An update statement can result in a connection unable to be dropped.
722578 Connections that have a cursor in prepare mode could fail to be able to drop if application abnormally disconnects
722606 Value for field 'columns' of sp_iqdbspaceinfo, while run for IQ_SYSTEM_MAIN and a partitioned table,returns non-zero value, expected is zero. This has been fixed.
722628 Temp buffer pool was running out of buffers for parallel distinct aggregates due to each

thread obtaining its own pin allocation. After a few threads have done so, there was not enough buffers available to initialized the remaining threads.

722661 Updates against an RLV enabled table using NBit could lead to a crash, this has been fixed.
722919 Query with count aggregate on column having NULLs and a grouping column ran

slowly when IQ optimizer performed aggregation using index.

722973 IQ 15.2 infrequent occurence of writer node hangs during a checkpoint. The system never comes back and they end up having to cancel the server. The pstacks prior to cancelling the writer node show no activity / movement. There is a lot of threads waiting on implicit locks and the thread handling the checkpoint seems to be blocked trying to flush version information.
723133 A long delay may have been observed when right-clicking in the SQL Statements panel, especially if the internet connection was slow, or if there was no internet connected at all. This has been fixed. Note, the problem does not occur if the documentation has been installed locally. (ADDL CR728720)
723216 The Foreign Key Constraint Wizard had a 508 issue where the keyboard would not successfully enable a particular drop down menu.
723294 LOAD TABLE may incorrectly report "Warning: Partial input record (x bytes) skipped at EOF" and fail to load the last row from the input file.
723446 LOAD TABLE may incorrectly give error "Number of bytes (xxxxx) exceeds

maximum (yyyyy)" during a LOAD with QUOTES ON.

723476 A query with an outer join and many case expressions in the the select list may consume an unacceptable amount of temporary space.
723503 Windows GPT disk was supported by Sybase IQ 15.4 ESD#1
723697 When a table created in an IQ 15 database with 1, 2, or 3 byte FP is upgraded and joined to a N bit tokenized FP created in IQ 16,the server will crash
723820 When all the 3 conditions are met:

- IQ SERVER is 15.4 esd 2 of any platform

- ISQL client is from 15.4 esd 2 LINUX 64 install (bundled Open Client 15.7.0.1)

- the option RETURN_DATE_TIME_AS_STRING=on

Then:

1> select getdate()

2> go

getdate()

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

2012-11

CT-LIBRARY error:

ct_fetch(): protocol specific layer: external error:

There is a tds protocol error. An illegal token was received.

723829 The following scenario would lead to a server crash.

Client has auto-commit on disconnect enabled.

1) Client 1 tries to insert a row in RLV store and has taken the lock. (this insert is not committed)

2) Client 2 fires non-blocking RLV-main store merge, which blocks on the lock.

3) Insert from client 1 completes, followed by merge from client 2.

4) Run 搒elect� from client 1

5) Disconnect the client 1 � fires auto-commit

6) Re-connect and run 搒elect� again on client 1

This has now been fixed.

723891 The conditions for which insert/load currently written to "System Administration Guide Volume 1" uses a multithread are not correct.
724003 Data is loaded incorrectly to a partitioned table

following a data value constraint violation.

724109 A query that contains a UNION ALL with an uncorrelated subquery executed over a set of tables performs much slower than the same query executed over a single giant base table.
724223 The server could in some cases fail while performing a BCP IN request if an error was generated while servicing the BCP request. This problem has now been fixed.
724297 Use of a special value or a user SQL function generate the incorrect query plan.

However, an issue is not reproduced when a special value with the date types, such as CURRENT TIMESTAMP is used.

724391 If you create a logical server with no servers, the secondary servers can go into an infinite loop during TLV replay giving an impression of a hang
724532 An insert .. select statement containing WITH .. AS fails with a Column not found error in 15.4 esd2.
724591 LOAD TABLE does not output error column information, when the data over string length exists.
724601 Currently LIST function resides in the SA catalog.

Each time it is called from IQ, it needs to go through CIS, which causes some

performance overhead.

The customer would like the LIST function to be implemented in the IQ SYSTEM store to

boost performance.

724627 CR724627 A left outer join on ISNULL() may not return a correct result set. For example, "select * from A left outer join B on IsNull(A.b,9999) = B.b;"

To be more generic any query having leftouter join with all the join condition as invariant predicate (either they are invariant or become invariant because of some simplification by the optimizer) might return wrong result.

After the fix the leftouter join remains as it is rather than getting converted to cross join.

724634 sp_iqcheckdb can return corrupt index error on an LF index created with more than 10000 unique values after setting LF_Max_Unique_Values option to a number as high or higher as actual unique values over 10000
724764 Query plans would not display all fields for RLV enabled tables. This has been fixed.
724804 IQ 12.7 -> 15.2 upgrade - performance degrade in Subsequent Fetch performance returning result set to client in some queries in Solaris environment
724806 Usage of updateable cursors on secondary MPX Writers can cause the Writer to crash
725054 LOAD TABLE will case a server failure if loading from a file with no filename extension.
725055 select dateformat('2012-nov-12 08:05:02','YYYY-MM-DD-HH:NN:SS') errors in 15.4, but not in 12.7 or 15.2.
725181 "select dateformat('2012-nov-12-08:05:02','YYYY-MM-DD-HH:NN:SS') from iqdummy" should throw an error same as the catalog (from dummy) does.
725406 Bad data could be merged from the RLV store into the IQ main store base table, if a column was set to the bit datatype. This has now been fixed.
725639 An IS NULL test in a CASE expression can fail to return rows.
725806 15.4 esd 2 Simple query slower compared to 15.2 esd 3
725871 The description about the fault caused during DQP execution does not exist in the manual of IQ.
726114 The LastReqTime connection property could have had an incorrect time stamp compared to current time. This would have only occurred if the server had been running for more than 24 hours. This has been fixed.
726127 sp_iqrebuildindex will fail with "Invalid expression" if the index_clause is a quoted identifier.
726128 When logging message in the iqmsgfile, the username string may get truncated.
726167 Performing an incremental back of the RLV enabled store could lead to a server crash. This has been fixed.
726373 If the trigger definition resulting from ALTER TRIGGER statement execution conflicted with an existing trigger, the original trigger could be deleted, and wrong error returned. This has been fixed.

This change also introduces a change in the algorithm used to decide the order of firing triggers when ORDER clause is not specified or multiple triggers with the same order and combination of events were created. For example, this may change the order in which triggers created with 揢PDATE ORDER 2�, 揢PDATE, DELETE ORDER 2� and 揢PDATE OF <col> ORDER 2� are fired. Note that documentation explicitly recommends specifying different ORDER values for triggers with the same event. If your database contains such sets of triggers, and the order of firing is important, please alter the triggers to reorder them accordingly.

In general, both UPDATE ORDER 1 and UPDATE OF <col> ORDER 1 triggers will fire before any UPDATE � ORDER2 triggers are fired. A unique ordering between UPDATE and UPDATE OF <col> triggers is still recommended.

726496 When merging updates from the RLV enable store back into the IQ main store, an ordering error might be encountered. This has been fixed.
726541 IQ server generates an error 9216 saying "Feature, ORDER BY in Union View, is not supported." when using a select-into query with an orderby clause
726559 For the grouped queries against the RLV store, wrong results might be returned. This has been fixed.
726794 IQ 15.4 ESD 1.1 Linux64 - IBM pSeries 2.6.18. They have a large partial width update statement that threw an exception at s_bm.cxx:1919 call at _ZN4s_bm7SetBits.
726819 Queries having a combination of Sort merge join and Windows operator might give wrong result. Because of early exit logic of sort mege join this bug got exposed. Fix resolves this issue.
726924 When the data of the duplicate primary key and WD index is inserted, IQ process stops.
727002 LOAD TABLE does not output error column information, when the data over string length exists.
727006 The information on the violation of constraint outputted to a ROW LOG file is outputted based on ROWID.

The function which outputs a data file name and a line number does not exist.

727148 SCC does not have the function which exports performance data etc. to external data.
727155 When using IQ MPX server, the coordinator may hang when doing distributed query processing under heavy load.
727388 A query that includes TOP, a subquery with an alias, and the alias used in the order by clause failed with a Non-Fatal IQ Internal Error Detected at dfo_cOrderBy.cxx:481.
727417 Stack trace on at s_packedRec.cxx:1287, on a query with CAST to varchar > 255
727427 As the number of concurrent requests across the resource gate increases , as expected you see the number of available concurrent commands reported in the Context Server statistics StCntxNResource field drop. However if all concurrent resources are in use and requests start queuing (i.e. the figure in StCntxNWaiting starts increasing) then the data reported in StCntxNResource becomes a nonsensical / corrupt 10 digit figure.
727579 IQ may produce wrong result in some rare cases when probing an nBit index.
727581 When running distributed query processing in a MPX server, all worker threads may crash for that given query
727585 Under rare circumstances, the background automerge of an RLV enabled table would loop repeatedly. This has been fixed.
727648 RLV Update queries involving a join in the FROM clause using aliases might crash. This has been fixed.
727679 An RLV table with char columns might merge incorrect data to the IQ main base table. This has been fixed.
727728 sp_iqindexadvice gives wrong datatype info in the 3rd row of the Advice column if the select has a join with 2 columns of different datatypes.
727747 Concurrent update/load/delete operation into an RLV store followed by a select top20 query crashes IQ. This has been fixed.
727942 Sub query containing NOT EXISTS causes an internal error.
727958 When running distributed queries using IQ MPX, coordinator may crash at stcxtlib/st_server.cxx:1485 under a heavy work load.
727979 CONVERT to BIT gives INT instead of BOOLEAN for the return value datatype
728058 Connection to Coordinator from Sybase Central doing Refresh All/Refresh folder spawns too many syncID_xx connections
728097 After applying the Sybase IQ15.4 ESD#2 on EUCJIS enviroment, would garbled srvlog messages IQ server.
728121 When dml_options2 = 64, query with group by could fire the error:

Input to GROUP BY # from child # not ordered as required

728124 Explanations needed on query plan generating 2 GROUP BY nodes
728153 When using the IQ MPX server, the reader nodes may crash under heavy stress condition that includes a combination of DML and DDL jobs.
728319 When you already have an IQ 15.2 esd 2 or esd 2.x installed, and you upgrade your IQ solfware install to 15.2 esd 3, after applying "ALTER DATABASE UPGRADE",

iqsrv15 -v

select @@version

in IQMSG

still display the old IQ version/esd number.

728435 IQ 15.4 ESD 2 Linux64 - x86_64 - a number of simplex production servers on different host intermittently experience problems shutting the IQ process down.

The final checkpoint completes and the CloseDatabase messages is seen but the IQ process hangs and does not go away. The customer has to issue a kill -9 to resolve.

This appears to happen with dbstop, stop_iq and SQL command STOP ENGINE UNCONDITIONALLY.

728739 Assertion failed: 201501. No stack trace, no assert.dmp, were generated
728927 S99SybaseIQAgent15 sets the wrong value in the environment variable PATH.S99SybaseIQAgent15 refers to the "$IQDIR15/bin". The correct path is "$IQDIR15/bin64".
729095 User was allowed to bypass an invalid DBSpace selection in the Materialized View Wizard.
729154 The Login Policy Wizard was not enabling the Next button based on the sequence of data entry. The issue has been resolved.
729299 The Partition Wizard will now properly check for appropriate "create" permissions on the desired DBSpace. The user cannot proceed without selecting a valid DBSpace (one in which they have create permissions).
729384 Create permission on the desired DBSpace is now verified before you can proceed to the next step for Partition Properties / column Storage.
729413 Performing a Split Partition now ensures correct permission on the destination DBSpace.
729557 The Table Objects page will not be updated when primary key columns are added. Previously the page could get out of sync.
729570 Create permission on the destination DBSpace is now verified for the Table Index Wizard.
729768 There was no way for a user to undo a selection in the various role wizards. This can now be done.
730008 In IQ 16 with the Revert_To_V15_Optimizer option set some queries ran much slower and with different plans than in 15.4.
730018 Edit, move and delete options for indexes were not working correctly on the table objects page.
730137 A UNION ALL query with an aggregate and a group by expression runs slow in IQ 15.4 when the cardinality of the group by expression is low.
730157 The spinbox for the upper range of values was not working correctly.
730225 Non-Fatal IQ Internal Error Detected

at s_garray.cxx:3125 on thread

May be reported deleting from a HG index.

730350 A SELECT with a LIKE clause on a column with a HG index may return wrong results.
730502 A user with DBA authority was unable to comment on a proxy table.
730633 Granting Administrative and Role privileges to a system role was causing a failure.
730784 Deleting Domains from multiple resources is not working. The issue has been resolved.
730898 Insert into a LOB column using a LOB variable containing partial multi-byte characters could fail. This has been fixed now.
730918 Alter table add long varchar column with LOB variable was failing. This fix resolves this issue.
731039 Added missing php files to the installer.
731290 ROLLUP functions are not allowed in a SELECT subquery. It certain situations, IQ executes it without firing an error and returns wrong results.
731615 Load table statement was failing when date clause is mentioned for columns with data type, other that date/date-time/time. This fix resolves this issue.
731738 In the Node Monitor, the Temp Cache statistics were showing the Main Cache statistics.
731757 When running on Solaris systems, if the server had accepted a new connection, but the client side closed its socket right away, the TCP listener would have been stopped and the message "TCP Listener shutting down (130)" would have been displayed on the server console. This has been fixed.
731807 SET USER violation might happen on a secondary node in an IQ Multiplex environment when any of the following DDL statements are synchronized on secondary nodes. This results in an emergency shutdown of secondary node.

1. GRANT/REVOKE AUTHORITY

2. GRANT/REVOKE GROUP MEMBERSHIP

3. GRANT CONNECT

731812 We need an environment variable similar to $SATMP_UMASK to restrict IQ/SA temp files permissions generated in $IQTMP15
731961 Columns were failing to create if the user did not have create permission on the selected DBSpace. The user is now warned up front of this issue.
731973 Creating External Procedure was not allowed for DBA user in 15.4.
732033 Customer repeatedly creating and dropping table might experience slowness due to a case-sensitivity bug. The issue resulted in slower scan times against the system catalog tables. This has been fixed.
732069 In the node monitor, the cache hits and reads were consistently showing as 0.
732141 Registering a multiplex would succeed, but there were invalid errors in the log.
732176 All the options for a database default value has been changed, not been described in the manual or EBF Cover Letter.
732201 When data is loaded with _forceMergeOption 'on', tiers at each level are merged together to process DBM. In case of delete physical delete is performed if _forceMergeOption is 'on'.
732267 When adding a primary key to a table, the DDL was not reflecting the change until the resource was re-authenticated.
732480 In the Materialized View Properties Sheet, the Refresh button was disabled for a user with privilege to refresh.
732481 When loading into an RLV enabled table the SKIP option does not have any effect if as Sybase IQ is single-threaded (max_query_parallelism=1).
732566 compounded statement with a GROUP BY and HAVING within a SET statement fails with

Could not execute statement.

Function or column reference to 'ACCR_NON_INT' must also appear in a GROUP BY

SQLCODE=-149, ODBC 3 State="42000"

Line 1, column 1

This worked fine in IQ 12.7. If you remove the SET statement it works fine.

732624 When adding a column and selecting 'global autoincrement', an invalid SQL error was returned.
732635 Updating a column with CMP index might lead to an inconsistent index. This fix resolves the issue.
732706 Some scalar subqueries which have an aggregate expression wrapped in a case expression in the subquery select list may result in wrong results being returned.
732757 OUTPUT statement of DBISQL cannot output to MS-ACCESS via ODBC.

CHAR-type column can not be output to MS-Access.

732805 what version of IQ will be certified with Windows 8 and in what timeframe
732866 In certain load scenarios involving Foreign key constraints, data inconsistency may be observed by running database consistency check. This has been fixed.
732940 crash at s_blockmap.cxx:3052 at s_blockmap23RegisterPhysicalBlockId . This is CR 657690 fixed in IQ 15.4. This is to request a back port of the fix in CR 657690 into IQ 15.2
732952 Under rare circumstances a deadlock could occur between two threads where one thread is in the process of committing an update to an RLV table and a second thread is in the process of updating the same RLV table. During the commit, the logging system for the RLV table runs out of buffers/pages. Its attempt to increase the space is blocked by a lock that the second thread already owns. This has been resolved.
732956 Product: IQ Network Client 15.4 32-bit installer

OS: Windows Vista 32-bit

Installer does not create the Sybase group icons on Start menu for Windows Vista 32-bits. Works fine in Windows XP.

The icons below should be created:

Interactive SQL - C:\sybase1\IQ-15_4\Bin32\dbisql.exe

ODBC Administrator 32-bit - C:\WINDOWS\system32\odbcad32.exe

Sybase Central v6.1 - Target: "C:\sybase1\Shared\Sybase Central 6.1.0\win32\scjview.exe"

Sybase on the Web - C:\sybase1\IQ-15_4\support\IQweb.htm

733034 a) A non-DBA user with execute privilege on sp_iqmpxdumptlvlog cannot execute the procedure in the SYSTEM PROC AS DEFINER ON model. (The fix will be applicable for databases upgraded to IQ 16.0 sp01 onwards)

b) The stored procedure sp_proc_priv returns incorrect information for system procedures sa_procedure_profile and sa_procedure_profile_summary

733046 During a hash-partitioned load certain combinations of table schema could cause crashes during a load.
733063 Multiple inserts and deletes into tiered HG index may lead to load failure in some scenarios. This has been fixed. In such a case DBCC on the index would report an error on the THG index before the failing load.
733178 When viewing Multiplex Properties, menus were not enabled/disabled appropriate on entry.
733208 Load table statement when executed with multibyte row delimiter failed in specific cases due to error in scanning logic.
733279 If the current load is such that it makes tier 0 go above threshold (by key logic), then send key threshold= 1 regardless of its actual calculated value. This will ensure that full merge occurs before pushing tier 0 to tier 1 incremental.
733376 A new database option CREATE_HG_AND_FORCE_PHYSICAL_DELETE is added in THG. By default the option will do physical delete in all tiers.PreELAN database needs to do alter database upgrade to see the effect of this option. By default the option will be on and HG index will follow physical delete.
733412 Updated delete method for THG to print delete messages if HG_DELETE_MESSAGES is set.
733441 Query using Nested Loop pushdown join algorithm having CASE expression in join

condition might abort with an Internal Error at dfo_Join.cxx: 452 in IQ 15.4.

733449 Doing an insert into with a remote location of partitioned data into an RLV enabled table does not work.
733451 If a multi-column UNIQUE index (including a multi-column primary key) exists on an RLV-enabled table, and the column order in the index definition differs from the column order in the table definition, the server would fails on inserts, updates and loads of that table. This has been fixed.
733973 Running the uninstaller in silent mode will leave more files and directories behind than the graphical uninstaller.

Workaround: add flag -DUNINSTALL_DELETE_USER_FILES=true when running uninstaller in silent mode.

734034 While performing fixed ASCII extract of a column with numeric datatype with precision == scale IQ server would crash as the MaxDataLength/field_size computation for the extracted string was incorrect.
734153 Under some circumstances a query that uses ISNULL in a where clause may return an incorrect number of rows compared to that returned with the same test when run in an IQ 15.2 or earlier server.
734291 During a hash-partitioned load certain combinations of table schema could cause crashes during a load.
734317 Certain types of errors during insertion of data into an IQ table may not be relayed back to the client. The data will not be inserted in these cases and the only indication will be from looking at the iqmsg file.
734336 Text index LOAD may report a non-fatal IQ error in s_bt.cxx.
734699 A SELECT statement with a GROUP BY might raise an error (Non-aggregate select/having expr appear in the group by) when a select item is an integer column computed with a value of more than 18 digits (for example, select (sales + 2000000000000000000) from sale group by (sales + 2000000000000000000)
734717 When membership in a group in a 15.4 database was granted via a mechanism outside SCC, it was not revoked correctly in SCC.
734822 In case of 'alter table add FK' the RO version of candidate key table was opened at very late, this RO version was picking latest schema changes and in case of rollback it remains there in catalog. Fixed this to open RO version of CK table at start.
734849 In the Create Group Wizard, a newly created Login Policy was not displayed correctly.
734855 The IQ server could fail during rollback after an out-of-space error. This issue has been resolved now.
734961 In a 15.4 resource, the user was prevented from adding partitions to an already partitioned table.
735135 On Windows 7 Multiplex creation via SCC was failing to create the local temp db.
735185 Bug exists because of inconsistent handling of multi-column key in HG code. This fix resolves the issue.
735264 Help about the 揙K� button appeared off the screen. This is fixed
735379 No error was reported when trying to register a Simplex as a Multiplex.
735385 A query with a group by expression that contained a very large constant value would not use the expected partitioned grouping algorithms on big endian architectures.
735441 Some range queries when executed on tiered HG index may fail. This has been fixed.
735445 Sybase Central for ASA 12.0.1 and SC for IQ 15.4 client install can not co-exist on the same Windows 7 box. Both can be installed OK and started indiidually OK. However if you try start them both the only the first one starts up. The second SC just does not start , no error.

If you try to add the plugin so one of the SC so that you can access both from the same SC the dbisql from within SC fails to connect throwing this error

"jodbc.jar build does not match the shared object build"

This only appears to be an issue with Windows 7 , other windows platforms like 2003 don't have the issue.

735471 This CR fixes a memory overwrite problem that may expose itself in various ways. One is a server failure at s_dpthreestore.cxx line 924.
735485 Fixed issue where the truncate and refresh options were not working properly for text indexes.
735487 An update statement to update an IQ table fails (SQL Anywhere Error -728: Update operation attempted on non-updatable remote query) when the statement includes the IsNumeric function.
735604 A complex query involving parallel ordered projection from HG index with large amount of data causes a sporadic failure.
735653 Support LOAD TABLE from compressed files with .gz or .gzip file extensions.
735762 Resolved issue where a blank password called LDAP validation to fail.
735797 When we write into garray either we write it from scratch or we open the garray in append mode. This issue has appeared after enabling physical delete for THG. Lets consider a case in which we open the garray in append mode after physical delete. We set the unit list header at the end of execution. This header was set incorrectly. The fix involve setting the header correctly.
736116 When using a UTF8 Collation on a database and inserting into an RLV enabled table with a primary or unique key, in some cases the insert will not fail when there is a unique violation.
736340 When CORE_Options1=10663296, and when the table has over 2 million rows, CREATE WD INDEX on a char (255) could cause IQ to execute the command for over 8 hours and eventually crash.
736366 THG index was merged inconsistently during a DML in few scenarios. This is now fixed.
736445 dbcc was failing for DBCC Hash range or Hash partition table after initial load. This fix resolves this issue.
736485 Previously, if a single user on a computer ran a number of copies of DBISQL, it was possible for the DBISQL options to be reset to their defaults. For this to happen, one DBISQL process would have to be starting when another DBISQL process was shutting down.
736523 MERGE statement is not implemented in IQ. All references to this statement have been removed from the manuals.
736551 For some collations, duplicate values were being allowed in a primary key column for RLV enabled tables.
736565 Resolved issue when using SCC with Portugues (Brazil). The information in the monitor will now display correctly.
736919 A query with a column having UNIQUE index and duplicate values, may return the wrong result when a hash join plan is chosen.
736932 Prior to IQ 16.0 sp02 it was possible to create a table with a table check constraint that included variables or columns that were not part of the table. A SQL error would be generated upon insertion into the table as this is not supported by IQ.

As of IQ 16.0 sp02 a syntax will be generated at table creation time.

736983 Scope of MAX_IQ_THREADS_PER_CONNECTION and MAX_IQ_THREADS_PER_TEAM ware incorrect.

These options can be set for all users.

737049 Two transactions attempting to lock the same RLV row could result in server failure. This is a very rare scenario and has been fixed.
737160 Error "trying to use Direct IO on unsupported system" may occur on a supported system even when IQ_USE_DIRECTIO = 1 was set to enable Direct IO.
737272 In certain cases migration to 15.4 using iqunload -au fails with "Reload of SYSIQINFO failed." error.
737305 A null pointer exception was received when restarting SCC. This prevented correct registration of the managed resources and failure to create a database.
737347 In some scenarios, DMLs may lead to Tiered HG being shown as inconsistent in sp_iqcheckdb ouput. The order-by, join (sort-merge) based queries using HG may also give incorrect results.
737363 When running on Solaris systems, if the server had accepted a new connection, but the client side closed its socket right away, the TCP listener would have been stopped and the message "TCP Listener shutting down (130)" was be displayed on the server console.

Now fixed as of IQ 15.4 ESD3 - request backport to IQ 15.2

737392 As the IQ buffer cache sizes grow, the cost of Rollback and

RollbackToSP increases, even if the volume of data

to be rolled back is small. This has been fixed.

737551 Connection Profile of Sybase Central is transferred to the other columns the Host/Port information.

As a result, 'View Data in Interactive SQL' function does not work correctly.

737646 Calling sp_iqrebuildindex on an unupgraded FP index having an unupgraded HG index on the same column leads to a server failure with error message pointing to slib/s_ohcidx.cxx:814.
737716 When creating a database, there was a misleading error in the log even though the database was successfully created. This error has been removed.
737773 Select SQL statement that uses a MAX function and a where clause that does a > or a < comparison against a DATEADD function that contains a date cloumn name as the date-expression causes the IQ server to crash st_server.cxx:1485 on call s_fetchGroup::Fetch but ONLY if the column has a LF index defined.
738029 The SQL command "ALTER DBSPACE ALTER FILE" could be used to rename a valid dbspace file to point to a filesystem directory. This would lead to failures in starting the database. The command now properly checks to ensure that a path rename does not point to a directory.
738123 Fixed a performance issue when listing views.
738240 IQ 15.4 ESD 3 AIX PowerPC 64-bits

IQ installer with GUI or with silent mode ends quickly with

"Installation complete" but only a few directories are created and no files (exe or lib)

are installed.

738244 Improved the performance for listing IQ Servers and Multiplex Servers.
738374 The IQ process size grows without limit due to LMA allocation. The problem appears to be that there are callers of the LMA that call it for small allocations. Several issues related to this have been fixed is SP02. The LMA allocation now takes the memory alignment into the bookkeeping.
738392 Executing a series of select into operations may eventually result in an error that reports that All IQ large memory has been used [-1013130].
738423 Load may fail doing Tiered HG proportional merge in certain cases.
738672 load engine can take a lot of time to report load finished after physical load is complete
738873 Creating an RLV dbspace was contributing to the overall main dbspace count.
738890 Using java.sql.Statement.setFetchSize(int) with Sybase IQ and the jConnect for JDBC driver results in an empty ResultSet being returned. Eliminating the setFetchSize statement or using the sajdbc4.jar file from the SQL Anywhere bundle resolves the error.
738988 Predicates are not pushed down into union all view when there are multiple predicates resulting in poor performance.
739146 Update on range partitioned table with over 67108864 rows on one partition may result in an inconsistent index.
739274 When connected to an IQ database, or if your DBISQL is configured to use only IQ, the following "Help" menu items have been disabled:

Interactive SQL Help

SQL Syntax

Keyboard Shortcuts

also, on the "Connect" window, the "Help" button has been disabled if you have selected the "SAP Sybase IQ" database type.

739302 IQ crash with signal4 due to a query which involved a distinct operation(with grouping over rowid's) over a from list containing derived tables.
739459 If CESU8BIN was selected as collation to create the database, the resource could not be registered properly. This is now resolved.
739583 A query containing LIMIT to restrict the number of rows returned performs very poorly when run against a large IQ table.
739718 During the commit of a transaction the server might hang with the stack indicating WaitForRSN.
739766 When max_temp_space is set to a too small value for IQ, ex:

set option public.max_temp_space=10;

The value is too small and no operation can be executed.

This value can not be set back to 0.

It results in the whole IQ becomes unsable.

740102 A query having a CASE expression might abort with an Internal Error at dfo.cxx:10637 in IQ 15.4 if a sort based aggregation algorithm is used.
740320 Various operations would be slower in 15.4 than they were in previous releases.
740774 HP-UXi64 machines are not setting allowed number of connections correctly. (We now allow 1001.)
740777 iq utilities main into ta_status status; into a local temporary table can crash IQ
741036 On 15.4 ESD 3. Non-fatal stack trace at dfo.cxx:10637 when SMJ

node gets wrongly ordered input from it's child.

741103 Server could crash if catalog runs out of free pages
741142 A query having sort-merge pushdown join with semi join filter filler going serial caused

IQ server to abort at st_server.cxx from hos_keycond_dtchar.

741443 Query of form " SELECT ... FROM ... WHERE condition IS TRUE " cause non fatal stack trace in df_Heap::AddToHeap
741502 For Syntax 2 of the DELETE statement and Syntax 2 of the UPDATE statement the error detection behavior of the server has been improved. The two syntax forms allow an additional FROM clause that may contain the table-name of the update/delete table, for example

DELETE

FROM [owner.]table_1 [ [ AS ] correlation-name ]

FROM [owner.]table_1 [ [ AS ] correlation-name ] ...

WHERE ...

and

UPDATE [owner.]table_1 [ [ AS ] correlation-name ]

SET columns_1 = ...

FROM [owner.]table_1 [ [ AS ] correlation-name ] ...

WHERE ...

If the DELETE or UPDATE clause and the additional FROM clause have a table reference that contains the same table name, in the above example "table_1", the server can only decide whether both identical table references if one of the following conditions is true:

- both table references are not qualified by specifying a user ID

- both table references are qualified by specifying a user ID

- both table references are specified with a correlation name

In cases that the server cannot decide whether the above table references are identical it will now return an SQL error to prevent the user from unintended semantics, like deleting and updating too many rows.

741648 Fixed an rare crash crash that would occur during execution of a stored procedure due to duplicate memory free. This has now been fixed.
742064 The shell script used to build the sample C++ UDFs (build.sh) was not working on AIX.
742315 A convert function failed with Msg "data type conversion is not possible" while converting varchar string to date format "yymmdd"
742429 Data insert from ASE to IQ taking huge main store
742585 Some Deletes in Tiered HG indexes may cause DBCC errors related to btree page count after the delete.
742713 The documented default for -ti server option for disconnecting inactive connections according to the utility guide is 240 (4hrs) as per

Sybase IQ 15.4 > Utility Guide > start_iq Database Server Startup Utility > start_iq Server Options

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc00168.1540/doc/html/saiq-ti-database-dbengine.html

However on IQ servers started on Unix platforms with start_iq the actuall default set is 4400 (about 72 hours).

This is documented under the section on Idle Connection Parameter [IDLE]http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc00170.1540/doc/html/san1283555399516.html

and also the section on Switches that Limit Inactive Connections

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

But it makes for confusing reading. Either utilities like start_iq need to be changed so the default set is 240, or the documentation updated to make this clear when 4400 will be used.

this applies to IQ 15.4 and 16 documentation

742715 The IQ 15.4 / 16 documentation have notes for functions like LTRIM incorrectly indicating a LOB license is needed, this needs correcting.

This may also need changing for

RTRIM, TRIM, UPPER, LOWER, UCASE, USER_NAME, SUSER_NAME

742740 iqunload can not migrate the DB with a simple encryption algorithm.

It is not possible to directly migrate the SAP Sybase IQ12 database using simple encryption.

742820 Feature request to have UINTTOHEX and HEXTOUINT functions that can convert an unsigned integer (from 0 to 4294967295) to hex and reversely.
742824 Feature request to have UBIGINTTOHEX, HEXTOUBIGINT functions that convert an unsigned bigint (from 0 to 18446744073709551615) to hex and reversely
742868 The server could fail when the following sequence of SQL statements were executed:

1. set snapshot_versioning = 'row-level'

2. insert into #temptable from select * from rlv_enabled_table

3. drop table #temptable

4. select * from rlv_enabled_table

Step 4 would fail due to the transaction's snapshot versioning being changed from row-level to table-level.

This has been fixed.

743190 Shared Memory Link supported on all plaftforms.
743225 Translation of simplified Chinese(ZH) and Japanese(JP) has been refreshed. See release bulletin for more information.
743236 Group by query on view or group by query with subquery, having aggregate expression

on view or column projected by subquery might produce incorrect number of rows in

15.4 ESD 3

743408 Constraint violation "FOREIGN KEY" and "NULL" is not recorded in row.log for LOAD TABLE.
743848 When configuring the SMTP server for email alert, there is no password check

about the sender.

The customer wants the ability to set the pwd for the sender, so that the email server authenticates the sender.

744717 internal connection called INT:FlushStats prevents normal IQ shutdown resulting in the need to kill the IQ process on Linux 15.4 installs.
744873 The startup messages in the iqmsg file and std error report an incorrect number of IQ_CORE licenses being checked out in IQ 15.4 Linux environment configured with 2 physical CPUs x 8 logical processors = 16 cores in total.
745018 A query containing a subquery which incorrectly referenced a column from a different table resulted in server failure which included opt_QueryTree::GenerateInferredPredicates in the stacktrace.
745203 If an application connected via Open Client or jConnect and executed a TSQL procedure that contained a TSQL SELECT INTO statement there was a chance the server would fail. Option CHAINED=OFF was required for this problem to occur.
745393 IQ 16 sp1 inccorrectly determine raw device size when IQ page size 256
745431 *** Wed Sep 25 2013 12:42:18 GMT+0530 (India Standard Time) *** ragarkar ***

Abort at st_globalFlMgrn.cxx:648 has been fixed.

745536 database using 1254TRK collation. Trying to use Functions names that contain capital I's like ISNULL , IFNULL, MINUTE, LTRIM and INSERTSTR in queries that contain IQ tables in the FROM clause all throw the "function not currently supported" df_Heap.cxx exceptions.

Note: not all functions with a capital I cause this exception though , e.g. ISNUMERIC and LIST do not.

745538 Data insert from ASE to IQ taking huge main store.
745821 Windows Server 2008 R2 is not included in the support platform of SAP Sybase IQ 16.0 installation guide.
745869 Trying to load data into a user dbspace created in Releases 15.x, sufficiently large that any block numbers are greater than 4,294,967,295, may fail with s_buf Read exceptions. Queries on updated tables may also report such Read exceptions. Check database (sp_iqcheckdb) will report damaged indexes. This has been fixed.
745900 Slow perfromance for certain operations after upgrading to 15.4.
746499 The Java Runtime Environment included in this release has been upgraded to SAP JRE 1.7. Please see release bulletin for more information.
746611 Optimizations made to the SQL query annotation phase.
746672 Certicom dependencies have been removed from the IQ plugin.
746700 insert/load job fails with non-fatal IQ Internal Error Detected at slib/s_packedRec.cxx:1291
746905 This CR fixes a memory overwrite problem that may expose itself in various ways. One is a server failure in s_dpthreestore.cxx at or about line 925.
746929 utlity to extract ddl for single or all IQ objects and partial or full data
746947 SAP Sybase Open Client and SAP Sybase jConnect included with in this release have been upgraded to version 15.7 SP121. Please see release bulletin for more information.
746948 In previous releases, SAP Sybase IQ included Certicom encryption module to provide strong encryption used throughout the software. The current release has been upgraded to use an OpenSSL encryption module for the strong encryption. The Certicom encryption module has been deprecated. Please see release bulletin for more information.
747269 sp_iqcheckdb 'check dbspace <dbspc>' can stacktrace
747700 When running iqunload on AIX, the iqunload client process may not connect to the 12.7 server started by iqunload. This would cause iqunload to fail
748014 An update code path with an invalid blockmap conversion sequence could report an

abort from CovertTo6BytePhysicalBlockIdsIfNeeded.

748073 Migrating from IQ 12.7 ESD 10 on 64bit AIX to IQ 15.4. Tables that contain more than 2.1 billion rows of data, trying to run the iqlsunload utility against these tables does not work, the utility goes into a loop and has to be canceled.
748234 Wrong description of lock_type of sp_iqlocks procedure.

Please refer sa_locks procedure of ASA12.0.1 manual.

748265 When a table is RLV enabled, IQ incorrectly opened indexes in RW mode. Users might run into this condition when the RLV table is under concurrent modifications. A runtime error would be reported from the buffer manager during a private flush and the stack would look like the following:

Dump all thread stacks at slib/s_bufman.cxx:5569 for PID: 35674

***************** This is the STACKTRACE ***************

===== Thread Number 512173824 (IQ connID: 0000081969) =====

pc: 0x7f761ab54776 pcstkwalk(stk_trace*, int, db_log*, hos_fd*)+0x36

pc: 0x7f761ab549e1 ucstkgentrace(int, int)+0x121

pc: 0x7f761ab55c2e DumpAllThreads(char const*, unsigned int, int)+0x12e

pc: 0x7f761a8e653e hos_ABORT(char const*, unsigned int, char const*, char*, char*)+0x19e

pc: 0x7f761acba77b s_bufman::PrivateFlush(unsigned long long)+0x88b

pc: 0x7f761acba949 s_bufman::ReleaseSavepoint(unsigned long long, unsigned int, unsigned long long)+0x29

748702 Simple SELECT of 1 column returns wrong result set when:

- several columns are concatenated in SARG

- those columns are not in the SELECT list

748729 It is possible that a non blocking merge performed at the same time as an insert on an rv enabled table having a unique key could result in a failure.
748900 Cannot execute a LOAD TABLE from a client file when the server is running on Windows and the client is not.
749167 Failed RLV updates could result in lma memory leaks.
749556 A subquery with min/max aggregate on union view may result in crash while estimating selectivity.
749704 When the following conditions are met, some of the source columns may not get properly inserted into the destination table:

(1) Number of columns on the source table is more than the target table

(2) Column order differs between source and target tables (though names match)

(3) "Create mapping by name" is used in "Mapping Definition"

750301 Under some circumstances an insert ... select statement might result in a Non-Fatal IQ Internal Error Detected at vplib/vp_Projections.cxx:1105
750325 A complex query might result in a server crash due to a stack overflow. Syntax limit checks have been added to prevent the stack crash.
750349 IQ server crash during a LOAD TABLE. The abort was in st_SAIQInterfacen.cxx:150 with "Unexpected resource deallocation error from IQ command, which originated at s_bmCur.cxx:712 ". Rerun of load after IQ restart works fine.
751112 Customer on IQ 15.4 esd 1 Linux 64 bit use SQL with CTEs (i.e using a SQL command construct using WITH tablename AS) coded extensively which mostly work fine no issue. However a combination of trying to use SELECT INTO and pull data in from a nested CTE that has a JOIN on a VIEW with UNION ALL抯 is causing IQ to crash with and abort at st_server.cxx:1430 on calls QOG::addIfOuterReference QOG::FindViewColumn
751113 Feature Request - full support for Common Table Expressions in IQ

Some aspect of using CTE's work, but others don't like using multiple CTE抯 , or CTE抯 containing VIEWs with joins and UNION ALLs, and also CTE抯 that end with a SELECT INTO.

751477 Two pathways that caused NBIT FP memory corruption have been fixed.

1. Starting with pre-existing databases containing NBIT indices in 16.0 GA or in 16.0 SP01. After upgrading to SP02 or SP03 engine, if the very first read/write operation performed on such indices was either a Delete, or an Update affecting zero rows, then subsequent inserts, updates or deletes to the table would cause corruption.

2. If an NBIT index was created in SP02 or SP03 and the same key is repeated at least 4,294,967,296 times at some point in the life cycle of the index and all the rows of the table are removed (via an explicit Truncate or a Delete), then an Insert or Load into the table followed by a Delete would cause memory corruption in the NBIT Index.

751837 If you try DROP a non-existent VIEW object using IF EXISTS, using an object name with the same name as an existing table, it returns an unexpected and incorrect error message.

drop view if exists xxxxx

Could not execute statement.

Table 'xxxxx' not found

SQLCODE=-141, ODBC 3 State="42S02"

Line 1, column 1

Firstly the message should not be produced at all if VIEW xxxxx does not exist.

Secondly the wording of the error message is incorrect , referring to 'table' instead of 'view'

751901 LOAD TABLE may stop processing if not enough buffers are available.
751932 Sum and nested CASE WHEN run on reader can cause stack trace on writer
752513 IQ message log archiving cycle (-iqmsgsz and -iqmsgnum) has an intermmittent problem where the log files are not correctly managed and files are lost or over written or the cycle appears to be restarted
752700 A SELECT query involving JOIN over a UNION ALL view which ran fine under IQ 12.7 using a Hash PushDown join, ran very slowly under IQ 16.0 SP01 and used a Hash join. Setting the Revert_To_V15_Optimizer did not restore the earlier join algorithm selection.
752758 The Sybase Open Client included with this release has been updated to 15.7 SP122
752851 A server failure may occur on a double throw during a LOAD from a client file.
753244 In rare cases a complex query with many predicates may fail to execute a predicate (as shown in the detailed query plan) resulting in wrong results being returned.
753289 Uncorrelated subqueries are not pushed down into a union-all-view if the select list includes nulls, constants, or casts.
753327 Data extraction facility cannot be converted the decrypted numeric type.

Data extraction facility returns a data conversion error.

Only numeric type is decoded, this problem will reproduce.

753363 Loading a table from a compressed file may not always load the correct number of rows.
753873 sp_iqpassword is supported for backward compatibility.

Changing the password using the ALTER USER statement.

754394 The sp_iqshowpsexe procedure output example in the Reference: Building Blocks, Tables, and Procedures document includes incorrect values for the max_statement and max_cursor columns. The current example lists max_cursor='50' and max_statement ='100'; the correct values should be max_cursor='100' and max_statement ='50'.
754435 Description of "-gm" is not correct.

maximum value of "-gm" is as follows.

UNIX/Linux: 1001, Windows: 200

754494 When a domain is created as NOT NULL, adding a new column of this domain datatype to an already populated table

is sucessful and NULLs are inserted in this new column while as, it contradicts with the definition.

754539 A combination of GROUP BY and DISTINCT cannot evaluate expression the column.
755399 OS400 ODBC Connections might report an insufficient length of SATMP. This has been fixed.
755733 If include an IQ table and IN SYSTEM in the FROM clause, the placeholder does not work.
755823 The JRE includes with this release has been updated to SAP JRE 6.1.061
755824 The JRE included in this release has been upgraded to SAP JRE 7.1.014
756388 Create DTTM index could cause the DTTM index to be invalid

if the first few records of a batch to be loaded into DTTM index have

hours:min:sec of 00:00:00

756578 An unhandled datatype exception is observed when a host variable of type date with 6 digit precision is declared in an application using jConnect client 5.X onwards to query a table in IQ. A secondary error may be observed when the query has Sort Merge join executed serially and early resource release option is disabled.
757044 We have backported a fix for an issue where IQ would purge table versions which were in-use by read-only cursors. This would lead to memory corruption and subsequent server aborts at random locations.
757547 When temp cache is insufficient, DISTINCT and ORDER BY return the wrong rows.

This problem reappears only when temp cache is short.

758272 Under some circumstances when a query has been cancelled a crash may occur with the method EstimateNonLocalSelectivity showing up near the top of the stacktrace.
758302 *** Mon May 19 2014 23:25:09 GMT+0530 (India Standard Time) *** agarwala ***

An IQ issue was fixed for restore where it would sometimes throw blockmap exception. This issue only affects restore of multiplex archive.

758405 The server could have failed if a TDS based connection sent a cancel request and a cursor close request at the same time for the same connection. Note that the cancel request could have either been sent explicitly by the application or implicitly by the underlying driver due to a query timeout.
758683 Alter/Create Server: remove reference to ASEJDC
758762 Statistics collection is not working with European locales
758769 To complement the problems encountered in CR 751837 the customer would like further document clarification and enhancements on how IQ handles views and table names.
758876 Data Extract using named pipe, causes error:

Tape IO Error /tmp/dam

-- (oslib/hos_ion.cxx 147)

SQLCODE=-1006162, ODBC 3 State="HY000"

758904 If a query has multiple subqueries in a query block, and one of those subqueries has no from clause, a function to sort the subqueries into a standard order failed due to an attempt to count the nonexistent tables resulting in bringing the server down.
759084 Under some circumstances an INSERT ... SELECT query might return a non-fatal internal error at vp_Projections.cxx:1105 when a word index exists.
759212 During rehash both old hash value and new hash value is calculated for a key. The old hash value was calculated incorrectly which was causing a key to rehash into same bucket. This was resulting into a loop formation and causing hang. Corrected old hash value calculation to fix the problem.
759231 The Statement in http://infocenter.sybase.com/help/index.jsp?

topic=/com.sybase.infocenter.dc38151.1540/doc/html/san1278453378415.html is not correct!

-- extract from docmentation link above --

You can create a dummy table in the Sybase IQ database. For example:

CREATE TABLE iq_dummy (dummy_col INT NOT NULL);

and use this table explicitly:

SELECT NOW() FROM iq_dummy;

-- end of extract--

You have to add at least one value in a table , otherwise you cannot get a value returned

The below is mising in the documentation and has to be added :

-- --

CREATE TABLE iq_dummy (dummy_col INT NOT NULL);

INSERT INTO iq_dummy values (1); -- Add this line

and use this table explicitly:

SELECT NOW() FROM iq_dummy;

-- --

759279 When C compiler has been installed in a system, "IBM XL C/C++ Compiler Update" wil be necessary.
759416 Stored procedure sp_iqcontext can unexpectedly fail while freeing memory.
759565 Count() function is support the range of BIGINT type.
759611 Customer upgraded from IQ 15.4 esd 1 on Linux to esd 3 and now a number of their production queries are failing with Exception Thrown from dfe_Cast.cxx:835, Data exception - data type conversion is not possible.
760106 Simple "select count distinct" on 1 table cause IQ abort with stack trace when an HG index exists. It runs fine when this HG index is removed.

select "campaign_id","count"(distinct("walklist_household_key"))

as "Households" from "sk_prod"."WALKLIST_ROI_PLANNING_TMP"

group by "campaign_id"

760313 A query which is cancelled or fails due to an internal error can result in server failure with EstimateNonLocalSelectivity in the call stack.
760575 DROP DATABASE statement with no directory permission to stop the utility db
760749 INSERT LOCATION between 2 IQ servers can hang or cause IQ fatal abort when

- the source DB is a single byte collation and contains a NON LATIN char (� or �)

- the destination DB is UFT8BIN (INSERT LOCATION is executed on this server)

760880 When running a 16.x server on a 15.x database, if an insert...values statement is run as the first read-write statement on a table and it fails with a simple error such as a "conversion error", the FP index may be corrupted due to partially upgraded metadata.

This problem has been fixed by a proper execution of a rollback upon command failure.

760959 The server fails with a signal 11 during sp_iqrebuildindex.
761033 Under rare circumstances a query may abort and bring down the server if Index Adviser is turned on.
761157 -dt option being ignored by IQ. Need to set IQTMP16 to configure the IQ temporary file directory
761259 Incorrect default value of BT_Prefetch_Max_Miss on Manual.

Correct default values is 1.

761260 Incorrect default value of Cache_Affinity_Percent on Manual.

Correct default values is 75.

761284 SAP IQ did not report any error if the file system on which the backup file was being written was full. The issue has been fixed to handle this situation and errors returned because of no space on the file system will be returned to the user.
761435 select MAX with WHERE clause = DATEADD on table with HG index = crash
761580 Under some conditions, calling a stored procedure that had nested stored procedure calls could cause a server hang if this was the initial load of the involved stored procedures.
761924 Cannot be set 0 to MPX_IDLE_CONNECTION_TIMEOUT.
761938 In rare cases, the server may have crashed while parsing an incorrect IN search condition. This has been fixed.

Syntax parser fails to detect a non existing object in a query and crash IQ.

The query must have two WHERE conditions on the same column with OR/AND:

col1 = <constant value> OR/AND col1 IN <non-existing object name>

Ex: select * from departments where departmentID = 100 and departmentID in NO_Object;

DBSIQL receives this error:

Error! The connection to the database was closed by the server.

Connection was terminated

SQLCODE=-308, ODBC 3 State="HY000"

Line 1, column 1

761954 Under some circumstances a query with an uncorrelated subquery may report a non-Fatal error at dfe_BaseColumn.cxx:1410 when a table in the subquery has no rows.
761995 A query containing a left or right function in a procedure that uses integer variables with some sort of math operation in the call to left or right (for example, my_position + 1) might result in a server failure and stacktrace with hos_FreeHosMem at the top of the stack.
762181 The version of OpenSSL release with this update has been updated to 1.0.1g
762183 The version of Open Client include with this release has been updated to 15.7 SP126
762204 dbisql cannot read sql include japanese("0x5b","0x5d") on aix.

dbisql will output a syntax error.

762222 Query with an uncorrelated subquery predicate hits a non-fatal failure on vpp_In::ExecuteOpus
762390 "COALESCE" and "GROUP BY" return a error "Can not evaluate expression"
762619 QUOTES ON load is read and processed in 16.0 as one thread per file. This results in a performance regression loading a single file with QUOTES ON. The IQ Load Engine has been updated to process QUOTES ON, single file load using multiple threads. This resolves the performance regression.
762668 A simple DELETE on 1 table may cause the following possible errors:

- non-fatal error in hs_subohc::SmallDelete

- fatal abort with "IQ Internal Error Detected: Memory Corruption" in destructors s_dictionary::~s_dictionary or s_dpNBit::~s_dpNBit

These errors are prevented with this fix.

762732 DBISQL will terminated abnormally by Text completion feature
762777 Fatal aborts on " IQ Internal error on FP variable page! "
762963 Under rare circumstances a query with multiple predicates might result in a Non-Fatal IQ Internal Error Detected at vplib/vpp.cxx:6413.
763120 On Linux x86 (RHEL and SuSE), IQ now uses O_DIRECT to open files. This allows IQ to bypass file cache and support IQ MPX on filesystem files including NFS and GPFS.
763588 When you create an IQ database with UTF8BIN collation sequence in a Japanese environment, Japanese some error messages will be truncated.
763678 The fix for CR 761995 was incomplete and could result in wrong results on some platforms under rare conditions.
763801 A safety assert was triggered that caused the query to politely fail.

On investigation, the assert is too restrictive, and will now permit that condition to pass.

763999 grant execute command stop the utility server.
764042 When running sp_iqdbspaceinfo or sp_iqdbspaceobjectinfo on a 1254TRK collation database, error "table sysiqidx not found" or "table sysiqinfo not found" could be fired.
764089 Under rare circumstances IQ could crash while executing a simple query with the following message:

* Error =>

... ** Non-Fatal IQ Internal Error Detected

... ** at dflib/dfo_Combiner.cxx:2099 on thread 1363 (TID 1354)

... ** Error detected at DFO #216 Parallel Combiner

...

... Exception Thrown from dflib/dfo_Combiner.cxx:2099, Err# 0, tid 1354 origtid 1354

... O/S Err#: 0, ErrID: 9216 (df_Exception); SQLCode: -1006001, SQLState: 'QBA01', Severity: 23

... [20239]: IQ Internal error. Please report this to Sybase IQ support.

This has now been fixed.

764235 iqsrv16 will create an entry in the syslog as "Notice" the priority of all messages.
764293 The following fix has been removed from the product for esd 2.27

SwrID CR Description

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

ESD2.26 757044 We have backported a fix for an issue where IQ would purge

table versions which were in-use by read-only cursors. This

would lead to memory corruption and subsequent server

aborts at random locations.

764486 round function does not round off a double value.
764646 Problems causing the following two errors in a database upgraded to SAP IQ 16 from versions 12.7 and 15.4 have been fixed.

'alter table X alter column NULL' fails with error

Internal state violation, please contact SAP IQ support

-- (slib/s_blockmap.cxx 6163)

and

IQ Internal error - s_blockmap.cxx; 3182 during LOAD TABLE.

764874 The bug occurs when querying a table with large number of columns (more than 128). The symptom is that IQ server reports non-fatal internal error at slib/s_barry.cxx.

The workaround for the query is: set temporary option CORE_Options86 = N, where N is number of table columns.

765098 Fixed an issue introduced in 16.0 SP02 where queries that include

a RANK aggregate with a descending ordering key may fail with a

non-fatal internal error.

765242 SELECT with LIKE clause return wrong results use V15 FP Index.
765340 When creating an existing remote table against SAP HANA or Hadoop where the tables a high number of rows, then ODBC call to SQLStatistics can take a long time to execute.

New cis_option to disable fetching of statistics (index info) when creating proxy tables in order to work around issues with back ends that take a very long time to return statistical information.

765543 A SELECT query on columns of a view, which in turn is based on multiple views/tables with UNION ALLs and OUTER JOINS, caused IQ to ABORT.
765824 Temp block leaks.

Create temp #table and insert rows in it.

Disconnect should release all the temp blocks used by this temp table.

Reconnect and use sp_iqstatus, you will see that not all the temp blocks previously used are released.

To reclaim temp space, the #table must be explicitely dropped or IQ must be recycled.

765943 Default port value of SCC is used in IQ16 SP08 installer of non-english.
766131 In rare circumstances, DBCC reported extra RIDS after an update of NULL rows in a Range Partitioned table.
766277 IQ 15.4 esd 2.24 solaris, DBSTOP crashing with hos_throw.cxx:313 at s_bufpool::Rollback after sucessful checkpoint and throwing error "Allocation failed. Dbspace IQ_SYSTEM_TEMP is INVALID"
766287 IQ 15.2 esd 2.26 update statement caused IQ to abort s_blockmap.cxx:1705 "Message: TEMPORARY blockmap still owns dirty pages -- should have been destroyed" with a stack at call s_blockmap::Unlock()
766290 15.4 esd 3 Smaller temp cache has better performance than with larger temp cache.
766931 Typo error in "Subqueries in Search Conditions", in the SQL example,

instead of "lineitemWHERE", it should be a blank in between as "lineitem WHERE".

766989 IQ internal error was detected when a right outer join query was

executed on a table consisting of a combination of varchar column and NBIT FP index.

This has been fixed now.

767122 After upgrading a 12.7/15.x database to IQ 16, a load/insert/update/delete on an existing table (table exists prior to the upgrade) could cause a server failure.

The failure is specific to the following conditions

a) IQ 12.7/15.x table must be empty (i.e., contain zero rows)

b) IQ 12.7/15.x table contains at least one tokenized FP

c) IQ 12.7/15.x database upgraded to IQ 16

d) first readwrite operation on table *must* be one of

- create index on tokenized FP column, OR

- add Primary Key, Foreign Key, Unique Constraint to tokenized FP column

767144 Fixed a performance issue with equality conditions that equate a constant

expression to a column that happens to be the hash partitioning basis

for a hash (or hash and range) partitioned table.

767342 The OpenSSL included with this release has been update to verion 1.0.1h
767679 Update causes IQ crash in hs_dpInsert::FinishedInsert under the following conditions:

a) updating a nullable nbit column

b) updating all rows on the column such that the update

effectively does an insert

c) during the update, the nullable nbit column rolls over to flat

767865 The NOT TRANSACTIONAL clause of declare local|global temporary table throws "Not Supported" error. A database option "Give_Error_On_Not_Transactional_DDL" (default value = 'On') has been introduced and error can be ignored if this option is set to 'Off'.
767908 In an environment where the private network is not registered in the MPX, when you add to MPX multiple hosts, DAS listener will block to stop the IQ server.
767912 A query with a hash join over a grouping operator could fail with error -1001043 (internal error, can not evaluate expression) or -1006000 (internal error in s_packedRec). This has been fixed.
767925 initial setting of uafadmin password is not written anywhere.
767952 Database inconsistencies can occur if the first readwrite operation on an IQ 15.x table, after upgrading the IQ 15.x database to IQ 16, involves rebuilding a column (via sp_iqrebuildindex) on which there exists a non-unique single column HG index.
767977 IQ Cockpit: initial password for sccadmin/uafadmin is not listed in the document
768008 SAP IQ 16.0 SP08 Server and Network Client support Windows Server2012 and 2012 R2.
768096 Database inconsistencies can occur when the very first readwrite operation on an IQ 15.x table, after upgrading the IQ 15.x database to IQ 16, is an insert..values statement that

a) is run with NOEXEC on

b) triggers a data conversion error

768284 SAP IQ Directory Access Server. Copy a file from a directory to another using INSERT SELECT fires no error.

Although the file is copied to the correct directory but the content is empty (fie size 0 byte).

768337 A query that includes a rank function in the select list, a join clause and a group by

clause caused an internal error in dfo_cOrderBy.cxx

768378 Interrupting a query that contains an Order By operator with CTRL-C or

drop connection could cause server threads to hang, leading to version

accumulation and possibly unresponsive server.

768389 DumpAllthreads causes IQ server to crash
768469 There was a bug in query plan generation logic during a 'load/create index' statement when option Query_plan_text_caching is set.
768532 Queries of the form

WITH < temp_table > AS (SELECT * FROM orig_table) (Query using temp_table)

caused the server to fail in IQ 15.4.

768537 SAP IQ returned the error "Non-fatal IQ internal error detected at dfo_Ranking.cxx:197"

when a query running in parallel mode contained both a Number function and a Rank function. Non-deterministic function such as the Number function should not be produced in parallel mode. Parallel mode is now disabled for such queries.

768550 An internal error may get generated from a query containing a correlated scalar value subquery in the SELECT list, and an uncorrelated IN subquery predicate whose body was a

UNION ALL.

768643 executing a procedure created by another user id, a select of rowid fails with db_sqlexception SQLCode: -1000266, SQLState: 'QDB09', Exception Thrown from db_sqlid.cxx:605, Table 'xxxx' not found (fixed in IQ 16)
768677 In IQ 15.4 select count distinct statement containing a WHERE ... OR xxx IN (.... UNION...) may return inconsistent results.
768755 An internal error may get generated from a query containing a simplifiable COALESCE expression that appeared within an aggregate that was then used inside a larger

expression within the HAVING clause.

768832 A query in IQ 15.4 ESD 4.2 caused the "dfo.cxx:11439 Can not evaluate expression" error.

The query involved:

(a) a subquery using a join

(b) an expression using a function in the subquery select list

(c) the expression is used in the inner case expression of a nested case expression

which also shows in the subquery select list

(d) an outer join involving the table resulting from the subquery on a condition

involving the nested case expression

768989 After creating a remote server from IQ to IQ, Assertion failed: 201503
769001 Incremental insert into a range partitioned table may, in certain situations, trigger a server failure.
769091 Under rare circumstances, a crash could occur while executing a SQL SECURITY INVOKER stored procedure. This has been fixed.
769131 IQ 15.2 Solaris, JDBC application using prepared statements containing a batch of SQL statements that use Host Variables fails df_Exceptions "Host variable 'xxxx' is not initialized" (df_Heap.cxx 2711)
769293 An outer join using a non nested loop join algorithm and on a join condition involving

the NULLIF function may return incorrect results. This has been resolved.

769521 A query in IQ 15.4 ESD 4.5 caused the "dfo.cxx:11264 Can not evaluate expression" error.

The query involved:

(a) a complex cast expression that consists of 2 cast sums that are added together

(b) the cast expression showing up in a subquery select list and also in the select list

of a join as a virtual column occluding the cast expression

(c) the join having a group by clause followed by a rollup and a having clause

769609 Non-Fatal Error, s_bm.cxx; loading NULLs into range partitioned table
769864 A SELECT query involving JOIN over a UNION ALL view which ran fine under IQ 15.4 using a Hash PushDown join, ran very slowly under IQ 16.0 SP8.0.2 and used a Hash join. Setting the Revert_To_V15_Optimizer cause non-fatal crash.
769899 This is a correctness bug, related to queries having either

(a) two or more OLAP-style partitioned aggregates having the

same PARTITION BY expressions and ORDER BY expressions, but

having different ordering directions

(b) at least one OLAP aggregate whose PARTITION BY expressions

and ORDER BY expressions together match the query's ORDER BY

clause except for a difference in ordering direction.

769913 When create a mirror file of the transaction log file, dbbackup -xo create a copy of the mirror file.This problem occurs only when use the transaction mirror.
769931 Loading a file created with IQ Binary Extract that contains a varchar or varbinary column may fail with an erroneous conversion error.
769957 Queries that involve a mix of FP-based conditions and HG-Based

conditions that encounter an error during condition execution

(e.g. a data type conversion error) may cause the server to crash.

769980 When the port is changed that the IQ server is running on, the user could not logon to SAP IQ Cockpit. This has been fixed. When the discovery process runs the connection information for the server will be updated if it has changed.
769981 There is an issue where the agent for cockpit could pickup the wrong IQ binaries to use in execution. This has been resolved to ensure we find the appropriate IQ binaries to execute against.
770015 Collation 1256ARA considers '2' and '�' as equal.

Same problem with the chars '3' and '�'

770034 using the row_number() OLAP function twice in a query, once over order by asc and once by desc returns a wrong result
770083 Queries with inter-column comparisons using null-absorbing coalesce, isnull, or case expressions could generate incorrect results.
770147 Installer of IQ 16.0 SP08 raise a java exception during the installation of the SCC.
770177 Performance regression between 15.4 and 16.x from a join

between a small table and a UNION ALL view over a set of

large tables where the 15.4 plan used a HPDJ algorithm

and the 16.0 plan incorrectly claimed that the HPDJ

algorithm was not valid for that join.

770332 Customers using PAM authentication might experience PAM authentication failures or a server crash during the recovery phase of database startup. This was caused by delaying the pam_init() call to post database start. This has been fixed by calling pam_init() prior to database start.
770353 Create Database Wizard of SCC/COCKPIT will fail by "unexpected end of file" in the Bourne Shell(bash) on RHEL6.
770406 The Multiplex Writer node may hang when there are a large number of DML operations happening on the Writer and Coordinator node concurrently when lots of threads on the writer node are attempting to make global free list inquiry to the coordinator node.
770410 Two wrong answer scenarios from GROUP BY ROLLUP aggregates were detected:

(1) COUNT(*) and COUNT(x) are incorrectly be set to NULL (instead of 0) for cases where (a) there are no input tuples flowing into the GROUP BY, and (b) the query plan chose

to execute the GROUP BY in parallel.

(2) The SUM(x) aggregate is incorrectly be set to 0 (instead of NULL)for cases where (a) either there are no input tuples, or where for a given rollup group all the SUM input values for x were NULL, and (b) the default data type for a SUM(SUM(x)) is different than

the data type for SUM(x)

770652 SAP IQ returned internal error "cannot evaluate expression at dfo.cxx:11271" when a query running in parallel mode used the hash group by algorithm and contained group by rollup over an Union All view.
770717 database restore on AIX IQ 16 SP04.04 fails with "Error during backup/restore: unable to close device", "A file descriptor does not refer to an open file", SQLCODE=-697, ODBC 3 State="HY000"
770874 Given certain set of data and under certain database option settings, queries with

an order by clause using items that are different from what is on the select list,

e.g., select 0 as x from t1 order by c1, can cause the IQ server to fail. This has

been resolved.

770899 The option BLOCKING='ON' with 2 connections inserting into the same table:

- When using DBISQL JAVA, both connections hang forever.

- When isuing Open Client ISQL, cause:

SQL Anywhere Error -1000011: Transaction 11480715 attempted to access 'kntest'

created by transaction 11480722.

771163 A double memory free could occur when concurrently executing a stored procedure,

that performs a load table, by more than 1 connection at the same time.

This has been fixed.

771216 Fixed an issue where the discovery mechanism employed by SAP IQ Cockpit may not have discovered the running resources on the host. The resources are now discovered and the system list will be populated.
771329 When you have specified the dbisql-statement, DBISQL might run 2 times a connection process.
771336 MPX coordinator stalled in rebooting from its previous crash if the other MPX secondary servers were not shut down.
771360 disabling dqp_enabled is resulting in the following error in IQ 16:

Msg 102, Level 15, State 0:

SQL Anywhere Error -131: Syntax error near 'dqp_enabled' on line 2

771549 Encrypted password support has been enhanced to restrict use to a particular computer/user and upgraded encryption algorithms. See KBA https://service.sap.com/sap/support/notes/2118895 for full details.
771559 Internal Error (opt_JoinNode.cxx:3043) from within the join optimizer for joins involving multi-column primary keys has been fixed.
771956 The SAP IQ server could fail with a SEGV error when a query contained an ANY, ALL, SOME

IN uncorrelated subquery. For example select * from t1 where c1 > ALL(select...

772215 When the Interactive SQL utility (dbisql) was run as a console application and connection parameters were specified, but the database password was not, dbisql would have exited without connecting. Now, dbisql will prompt for a password, given that the "-q" (quiet) option was not specified. Since a password is not required on the command line, the password will not be visible with OS utilities used to view process command lines.
772339 IQ crashes in dfiio_FP::CompleteOpus during an INSERT..SELECT. This issue may occur if an error is returned when executing the select. This issue has been fixed.
772483 Open Client has been updated to 15.7 SP131 to resolve FIPs not loading on AIX. The fix limited to in this release only.
772547 Under rare circumstances that is very data dependent, a server failure may occur after deletion of NBit rows from a varchar or varbinary column.
772714 IQ crash at will in RelocatableHeap::LoadCrossHeapPtr when:

- a user executes a system proc encapsulated within a stored procedure,

- and this user is not the owner of this stored proc.

772905 On IQ 16, simple INSERT INTO table (SELECT conn_handle FROM "satmp_request_time") or

SELECT conn_handle INTO table FROM "satmp_request_time"

executes for hours depending on the size of the zrlog.

The SELECT without insert runs around 15 mins.

773004 SAP IQ return error "non-fatal error at dfe_MinMaxAggregate.cxx:998".

when a query contained LAG or LEAD OLAP function and used NULL value as default value.

773300 SQL via ODBC does not set the correct value to satmp_request_time.rowcount
773343 The IQUNLOAD tool has been enhanced to support unload of a current iq database schema and data.
773699 SELECT ... FROM several derived tables returns incorrect result.
773817 Open Client has been upgraded to 15.7 SP130
774071 Open Client has been upgraded to 15.7 SP130
774119 Previously, Interactive SQL would fail to set its exit code to non-zero in a number of cases:

1. If no connection parameters are given, but a statement is given.

2. If a READ statement or the name of a SQL file is given on the command line, and the file exists, but the file cannot be read for any reason.

3. If an error is encountered while reading the results of a statement.

4. If a statement was using the TEMP_EXTRACT option

774287 MPX. If a client connection is launched from LINUX to the coordinator and run an IQ backup,

- on the writer, client operations accessing catalog data returns results.

- on the writer, client operations accessing user data hang forever.

774457 SAP IQ no longer support the SSLv3 protocol. All TLS connections must now be TLSv1 or higher.
774469 IQ Server crash during a transaction which involves creation of a local temporary table as a part of transaction.
775120 CREATE ANY OBJECT system privilege overrides REVOKE CREATE on DBSPACE privilege.
775132 When running iqunload against a 15.4 database that had a RAW dbspace file, the utility might suddenly exit without displaying any errors. This has been fixed.
775135 When running iqunload against a 15.4 MPX database, when connecting to the MPX coordinator, the utility might suddenly exit without displaying any errors. This has been fixed.
775138 The iqunload utility when run with the -v argument will now display table specific progress messages.
775139 When running iqunload with the -v argument, it will include additional progress messages about the specific tables being unloaded.
775353 16.0 tokenized FP (nBit FP) for NUMERIC data types may become corrupted resulting in data loss when adding new values that causes the dictionary to be resized. This fix properly resizes NUMERIC nBit dictionaries.
775708 Post multiplex upgrade from IQ 15.2 esd 2.27 on solaris to IQ 16 sp08.20 , coordinator node startup aborting st_server.cxx:1709 with a stack at call inc_iqnwi::SetupSender
775857 IQ 16 sp08.03 LOAD TABLE with ROW LOG aborted IQ process with s_violation::LogDataValueViolationInRowLog -> hos_extract_varchar_ascii

LOAD TABLE... ROW LOG was executed whenever a data conversion error was found at any field. It should be performed after the whole row has been processed.

The ROW LOG will be correctly performed at the end of a row to ensure that we are logging the correct data for the row.

776148 Install instructions for Windows 7 say to use AGREE_TO_SYBASE_LICENSE, but should say use AGREE_TO_SAP_LICENSE.
776295 When upgrading from 15.x to 16.0, tokenized FP (1-byte, 2-byte or 3-byte) indexes may become corrupted when deleting tokens from the nBit dictionary. This may lead to HG index metadata mismatched reported as hos_memmgr::FreeHosMem hs_subohc::~hs_subohc(). This fix properly compacts deleted token to avoid metadata corruption in the nBit index.
776502 LOAD TABLE failed with a double throw error while writing to the row/message log.
776538 dbping might hang if IQ started with -p flag. This has now been fixed.
776588 When using encryption, there is no mean to check that it is enabled.

The customer would like a message displayed in IQMSG/SRVLOG such as:

"SSL context successfully created".

776701 An equi-join query may fail that involved

- in the join predicate an equality comparison of 2 columns from the same table and

- in the select list a SQL function that uses the first column from the equality

comparison and

- in the select list the other column from the equality comparison

Or

- a where clause with an equality comparison predicate of 2 columns from the same

table and

- a join predicate using columns that are from 2 separate tables and are different

from those used in the equality comparison and

- a select list as described above

776708 "IGNORE CONSTRAINT UNIQUE 0" will report the number of incorrect insertion rows.
776709 SAP IQ will always request the libaio package.
776959 Multi-tape backups are failing when 3rd tape is required
777046 In the Entity Framework Data Model Wizard "Choose Your Database Objects and Settings" dialog, the SQL Anywhere .NET Data Provider did not return stored procedure and function names in the "Stored Procedures and Functions" list view for a case-sensitive database. This problem has been corrected.
777203 Fixed an issue where a query over a hash partitioned table that included an equality condition on the table's hash partition basis column equating it to a constant expression resulted in an IQ Internal Error from vpp_Compares.cxx.
777332 LOAD failed with internal error and dump of variable page in IQMSG.

Prior to LOAD, some rows at the end of row id chunk(s) have been deleted.

LOAD reused these deleted row ids, but not all have been reused.

When NBIT column reached rollover limit and partly rolled over to FLAT,

before the entire column rollover, LOAD attempted to merge the deleted

rows which resulted the reported internal error.

This can result s_barray or s_blockmap assertion due to memory corruption.

Potential trigger condition:

NBIT variable column reached rollover limit with prior DELETE operations.

CR762777 and 776088 are duplicates of this CR.

777445 Added logic to detect nbit load/update issues and rollback the operation
777605 SYSAM issue

"Corrupt MS(Max DBSpace) value in license, restricting to 5GB" error message raised in iqmsg file

--EOF--

  • 本文链接地址:http://www.dbainfo.net/sap-iq-cr-number.htm
  • 本文为dbainfo个人原创,请在尊重作者劳动成果的前提下进行转载;
  • 转载务必注明原始出处 : Sybase数据库技术,数据库恢复专家
  • 对《SAP IQ的所有已知BUG列表》有何疑问或见解,请在本文下方发表;
  • 对网站还有其他问题或建议,请提交在留言板,谢谢!
  • 目前还没有任何评论.
    :wink: :twisted: :roll: :oops: :mrgreen: :lol: :idea: :evil: :cry: :arrow: :?: :-| :-x :-o :-P :-D :-? :) :( :!: 8-O 8)