提供7*24专业Sybase数据库远程及现场技术支持,Sybase ASE及Sybase SQL Anywhere数据库修复服务,
请联系电话: (微信),QQ: 289965371!
We supply technical support for Sybase ASE and Sybase SQL Anywhere, also have many years of experience in recovering data from damanged Sybase devices.
Please contact us:
Phone:
Wechat: 13811580958
QQ: 289965371 联系我们获取数据库技术支持!
Email: 289965371@qq.com
扫描下方微信,联系我们:
扫描雨翰数据恢复官方微信获取专业数据库恢复服务

 

随着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信息!

如有问题,请联系我!

QQ :289965371 联系我们获取数据库技术支持!
Email:
不仅仅包括BUG的详细描述信息,还包括首次报告BUG的平台、数据库版本以及BUG修复历史过程;有些BUG还提供了Workaround来临时解决该BUG带来问题。

 

CR:739718
CR Number:   739718
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   16.0 sp02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp02 16 May 2013 Fixed
Description
During the commit of a transaction the server might hang with the stack indicating WaitForRSN.



CR:739766
CR Number:   739766
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Unknown
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
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.



CR:740102
CR Number:   740102
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.4 e04 03 Jul 2013 Fixed
15.4 e03.x 24 Jul 2013 Fixed
16.0 sp02 04 Oct 2013 Fixed
31 Oct 2013 Fixed
Description
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.



CR:740320
CR Number:   740320
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   16.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp02 04 Jun 2013 Fixed
16.0 sp01.x 25 Jun 2013 Fixed
Description
Various operations would be slower in 15.4 than they were in previous releases.



CR:740774
CR Number:   740774
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   16.0 sp01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
05 Jun 2013 Fixed
16.0 sp01.x 16 Oct 2013 Fixed
Description
HP-UXi64 machines are not setting allowed number of connections correctly. (We now allow 1001.)
Workaround Description
 Nothing Yet.



CR:740777
CR Number:   740777
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   16.0 sp01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
iq utilities main into ta_status status; into a local temporary table can crash IQ



CR:741036
CR Number:   741036
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Linux Red Hat
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
On 15.4 ESD 3. Non-fatal stack trace at dfo.cxx:10637 when SMJ

node gets wrongly ordered input from it's child.
Workaround Description
 Turn on the query plan and index advisor.

Set the indexes sugested by the index advisor and the query does not strace any more



CREATE UNIQUE HG INDEX X1 on C$_1CTR_X_PAR (C13_DOVIZ_KOD asc );

CREATE HG index X2 on C$_0CTR_X_PAR (C7_SRC_STM_CTR_ID_PART4 asc );

CREATE HG index X3 on C$_0CTR_X_PAR (C3_CUST_NO asc );

CREATE HG index X4 on C$_0CTR_X_PAR (C5_SRC_STM_CTR_ID_PART2 asc );



CR:741103
CR Number:   741103
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Linux Red Hat
Original Version:   16.0 sp01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Server could crash if catalog runs out of free pages



CR:741142
CR Number:   741142
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.4 e04 31 Oct 2013 Fixed
16.0 sp03 08 Nov 2013 Fixed
08 Nov 2013 Fixed
Description
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.



CR:741443
CR Number:   741443
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Windows 2003
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Query of form " SELECT ... FROM ... WHERE condition IS TRUE " cause non fatal stack trace in df_Heap::AddToHeap
Workaround Description
 2 workarounds :



1- Remove the "IS TRUE" clause permits the query to run fine and return the correct result.



update c_party c set datum_do = date('2013-05-08') - 1

from c_party c

inner join f_party f on c.id=f.id and f.tec_datum = '2013-05-08'

where not(

((c.rc is null and f.rc is null) or c.rc=f.rc) and

((c.meno is null and f.meno is null) or c.meno=f.meno) and

((c.priezvisko is null and f.priezvisko is null) or c.priezvisko=f.priezvisko) and

((c.datum_narodenia is null and f.datum_narodenia is null) or c.datum_narodenia=f.datum_narodenia)

)

and c.datum_do = '2299-12-31'



2- Rewrite the condition into CASE WHEN



update c_party c set datum_do = date('2013-05-08') - 1

from c_party c

inner join f_party f on c.id=f.id and f.tec_datum = '2013-05-08'

where (

case when (c.rc is null and f.rc is null) or (c.rc = f.rc) then 0 else 1 end = 1 or

case when (c.meno is null and f.meno is null) or (c.meno = f.meno) then 0 else 1 end = 1 or

case when (c.priezvisko is null and f.priezvisko is null) or (c.priezvisko = f.priezvisko) then 0 else 1 end = 1 or

case when (c.datum_narodenia is null and f.datum_narodenia is null) or (c.datum_narodenia = f.datum_narodenia) then 0 else 1 end = 1

)

and c.datum_do = '2299-12-31';



CR:741502
CR Number:   741502
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   15.2 e03.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp03.x 11 Nov 2013 Fixed
16.0 sp02 30 Oct 2013 Added to user documentation
Description
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.



CR:741648
CR Number:   741648
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   AIX
Original Version:   15.4 e01.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11 Jun 2014 Fixed
Description
Fixed an rare crash crash that would occur during execution of a stored procedure due to duplicate memory free. This has now been fixed.



CR:742064
CR Number:   742064
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   16.0 sp01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp02 16 Jul 2013 Fixed
Description
The shell script used to build the sample C++ UDFs (build.sh) was not working on AIX.
Workaround Description
 After working with SA eng, i got a resolution o fthe UDF compile error.

In results, given default 'build.sh' needs to be modified like below.



1) Changing IQ server start-up parameters



-sf -inmemory_external_procedure <-- manual guide



=> changed



-sf -external_procedure_v3



2) In compiling part



elif [ "$platform" = "AIX" ]; then

...



xlC_r -c -q64 ... -I$IQDIR16/sdk/include ${build_files[${counter}]} -o ${object_file_location}/${build_files[${counter}]}.o

=>

xlC_r -c -q64 ... -I$IQDIR16/sdk/include ${build_files[${counter}]} -DAIX -o ${object_file_location}/${build_files[${counter}]}.o



(** added -DAIX parameter in above. It seems to be missed. Other platform has a definition like -DLINUX, -DHP.)



3) In lingking part



elif [ "$platform" = "AIX" ]; then

xlC_r -q64 ... ${object_file_location}/${object_file_list}

=>

xlc_r -q64 ... ${object_file_list}



(** Changed : ${object_file_location}/${object_file_list} => ${object_file_list} )



CR:742315
CR Number:   742315
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   15.4 e03.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.4 e03.x 26 Sep 2013 Fixed
15.4 e03.x 19 Nov 2013 Fixed
Description
A convert function failed with Msg "data type conversion is not possible" while converting varchar string to date format "yymmdd"
Workaround Description
 set temporary option core_options13 = 33554432



CR:742429
CR Number:   742429
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Jul 2013 Consult Complete
Description
Data insert from ASE to IQ taking huge main store
Workaround Description
 Use INSERT LOCATION



CR:742585
CR Number:   742585
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   16.0 sp02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp02 04 Jul 2013 Fixed
Description
Some Deletes in Tiered HG indexes may cause DBCC errors related to btree page count after the delete.



CR:742713
CR Number:   742713
Product Name:   IQ
Product Component:   Documentation
Status:   Open
OS:   Unknown
Original Version:   15.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
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



CR:742715
CR Number:   742715
Product Name:   IQ
Product Component:   Documentation
Status:   Open
OS:   Unknown
Original Version:   16.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
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



CR:742740
CR Number:   742740
Product Name:   IQ
Product Component:   Utility
Status:   Closed
OS:   Windows 2003
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
30 Jul 2013 Not reproducible with latest version of the product available as of Resolution Date
Description
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.
Workaround Description
 Please use schema unload and load table.



CR:742820
CR Number:   742820
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Unknown
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Feature request to have UINTTOHEX and HEXTOUINT functions that can convert an unsigned integer (from 0 to 4294967295) to hex and reversely.



CR:742824
CR Number:   742824
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Unknown
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Feature request to have UBIGINTTOHEX, HEXTOUBIGINT functions that convert an unsigned bigint (from 0 to 18446744073709551615) to hex and reversely



CR:742868
CR Number:   742868
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   16.0 sp01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp02 16 Jul 2013 Fixed
Description
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.



CR:743190
CR Number:   743190
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Solaris
Original Version:   15.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Jul 2013 Added to user documentation
16.0 sp02 31 Jul 2013 Added to user documentation
Description
Shared Memory Link supported on all plaftforms.



CR:743225
CR Number:   743225
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   16.0 sp02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp02 26 Jul 2013 Fixed
16.0 sp03 02 Dec 2013 Fixed
Description
Translation of simplified Chinese(ZH) and Japanese(JP) has been refreshed. See release bulletin for more information.



CR:743236
CR Number:   743236
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.4 e03.x 20 Aug 2013 Fixed
16.0 sp02 18 Sep 2013 Fixed
15.4 e04 05 Aug 2013 Fixed
09 Oct 2013 One-off Provided
Description
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
Workaround Description
 set temporary option dml_options6=16777216;

set temporary option dml_options9=8;



CR:743408
CR Number:   743408
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2008
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
09 Jan 2014 Presently Not Targeted For Any Future Release Of This Product
20 Mar 2014 Fixed
Description
Constraint violation "FOREIGN KEY" and "NULL" is not recorded in row.log for LOAD TABLE.



CR:743848
CR Number:   743848
Product Name:   IQ
Product Component:   other
Status:   Open
OS:   Unknown
Original Version:   16.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
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.



CR:744717
CR Number:   744717
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   15.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10 Nov 2014 Fixed
Description
internal connection called INT:FlushStats prevents normal IQ shutdown resulting in the need to kill the IQ process on Linux 15.4 installs.
Workaround Description
 For some customers increasing -gn to be at least 1.5 * -gm , and / or increasing -iqmt has helped to avoid the problem



using startup option "-hW EnableStatsGovernor" seems to prevent the INT: FlushStats connection from becoming stuck. However we need to know what the consequences / overheads of running in production with this set before suggesting this as a possible work around



further suggested work around from engineering of...

set option public. update_statistics = 'off'

set option public. collect_statistics_on_dml_updates = 'off'

did not prevent the problem of the stuck INT: FlushStats connection.



Also Note as advised from eng

the use -hW EnableStatsGovernor for production system as general setting is not advised unless absolutely necessary. The statistic governor is intended to also delete and fix corrupt histograms or histograms with errors.



- upgrade to IQ 16



CR:744873
CR Number:   744873
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Linux Red Hat
Original Version:   15.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
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.



CR:745018
CR Number:   745018
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   15.2 e03.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp02 02 Sep 2013 Fixed
Description
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.



CR:745203
CR Number:   745203
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   16.0 sp01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp02 20 Oct 2013 Fixed
Description
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.



CR:745393
CR Number:   745393
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   16.0 sp01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
04 Sep 2013 Fixed
Description
IQ 16 sp1 inccorrectly determine raw device size when IQ page size 256



CR:745431
CR Number:   745431
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Solaris
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12 Sep 2013 Fixed
11 Feb 2014 Fixed
Description
*** Wed Sep 25 2013 12:42:18 GMT+0530 (India Standard Time) *** ragarkar ***

Abort at st_globalFlMgrn.cxx:648 has been fixed.



CR:745536
CR Number:   745536
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Solaris
Original Version:   15.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
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.
Workaround Description
 re-code the query containg these functions so they run on the SQL Anywhere side , e.g. either by not coding the FROM clause or using FROM SYS.DUMMY instead.



possibly also use COALESCE instead of ISNULL too.



use lower case i's instead



CR:745538
CR Number:   745538
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Linux Red Hat
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Data insert from ASE to IQ taking huge main store.



CR:745821
CR Number:   745821
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Windows 2008
Original Version:   16.0 sp01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp02 30 Sep 2013 Added to user documentation
Description
Windows Server 2008 R2 is not included in the support platform of SAP Sybase IQ 16.0 installation guide.



CR:745869
CR Number:   745869
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   16.0 sp01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp08.x 16 Jun 2014 Fixed
16.0 sp02 23 Oct 2013 Fixed
16.0 sp09 23 Jun 2014 Fixed
16.0 sp04.x 20 Jun 2014 Fixed
Description
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.



CR:745900
CR Number:   745900
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   HP-UX
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Slow perfromance for certain operations after upgrading to 15.4.
Workaround Description
 Not Yet



CR:746499
CR Number:   746499
Product Name:   IQ
Product Component:   Install
Status:   Closed
OS:   Unknown
Original Version:   16.0 sp02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp02 23 Sep 2013 Fixed
16.0 sp02 24 Sep 2013 Fixed
16.0 sp02 04 Oct 2013 Fixed
16.0 sp03 02 Dec 2013 Fixed
Description
The Java Runtime Environment included in this release has been upgraded to SAP JRE 1.7. Please see release bulletin for more information.



CR:746611
CR Number:   746611
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   15.4 e02.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.4 e04 04 Dec 2013 Fixed
16.0 sp02 29 Oct 2013 Fixed
Description
Optimizations made to the SQL query annotation phase.



CR:746672
CR Number:   746672
Product Name:   IQ Management
Product Component:   Web UI - Administration
Status:   Closed
OS:   Generic
Original Version:   3.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Oct 2013 Fixed
26 Dec 2013 Fixed
Description
Certicom dependencies have been removed from the IQ plugin.



CR:746700
CR Number:   746700
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   16.0 sp01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
30 Sep 2013 Fixed
Description
insert/load job fails with non-fatal IQ Internal Error Detected at slib/s_packedRec.cxx:1291
Workaround Description
 Hi Saroj,



Using the repro for CR 746700 I was able to reproduce the internal error and

*successfully* use the workaround of doing sp_iqrebuildindex on the 7 varchar columns as follows:



sp_iqrebuildindex 'f_Hour_DiagnosticMetrics',

'column "UserTZName"

column "Month"

column "Server Hostname"

column "ExtensionPack"

column "Task Category"

column "Task Type"

column "Task Name"



Then the Load succeeds. I also confirmed sp_iqcheckdb verify database reports no errors.

CR 737611 is a metadata issue and is why the rebuild resolves the problem.



My test version: Sybase IQ/16.0.0.481/130503/P/sp01/Sun_x64/OS 5.10/64bit/2013-05-03 16:23:30

My iqmsg: /sunx12dqp-c2/users/maryc/sp01/perfspi.iqmsg



Your new CR 736467 seems like a potential duplicate of CR 737611.



Can you please confirm this is a viable workaround.



Thanks,

Mary



CR:746905
CR Number:   746905
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Suse
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
02 Oct 2013 Duplicate
Description
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.



CR:746929
CR Number:   746929
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Linux Red Hat
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
utlity to extract ddl for single or all IQ objects and partial or full data



CR:746947
CR Number:   746947
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   16.0 sp02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp03 18 Nov 2013 Fixed
16 Dec 2013 Fixed
16.0 sp08 02 Dec 2013 Fixed
16.0 sp03 02 Dec 2013 Fixed
Description
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.



CR:746948
CR Number:   746948
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   16.0 sp02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp02 25 Sep 2013 Fixed
16.0 sp02 26 Sep 2013 Fixed
16.0 sp02 27 Sep 2013 Fixed
16.0 sp08 22 Jan 2014 Fixed
16.0 sp03 02 Dec 2013 Fixed
Description
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.



CR:747269
CR Number:   747269
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   16.0 sp01.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
04 Oct 2013 Fixed
Description
sp_iqcheckdb 'check dbspace <dbspc>' can stacktrace



CR:747700
CR Number:   747700
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   16.0 sp02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp08 29 Nov 2013 Fixed
Description
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



CR:748014
CR Number:   748014
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.4 e06 05 Jan 2015 Fixed
16.0 sp08 05 Jan 2015 Fixed
16.0 sp09 05 Jan 2015 Fixed
16.0 sp10 05 Jan 2015 Fixed
15.4 e05 05 Jan 2015 Fixed
Description
An update code path with an invalid blockmap conversion sequence could report an

abort from CovertTo6BytePhysicalBlockIdsIfNeeded.



CR:748073
CR Number:   748073
Product Name:   IQ
Product Component:   Utility
Status:   Closed
OS:   AIX
Original Version:   15.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Nov 2013 Fixed
11 Feb 2014 EOL'd version. Not to be Fixed.
Description
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.
Workaround Description
 possible w/a's being explored...



1) Either archive data off, or split data into 2 or more tables to get them less than 2.1 billion rows then run iqlsunload

2) Run iqlsunload only for tables less than 2.1 billion rows using the -t option, then for those that are larger manually extract the schema create DDL for them, and manually write data extracts and LOAD statements.



CR:748234
CR Number:   748234
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Unknown
Original Version:   15.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.4 e04 24 Oct 2013 Added to user documentation
16.0 sp02 24 Oct 2013 Added to user documentation
Description
Wrong description of lock_type of sp_iqlocks procedure.

Please refer sa_locks procedure of ASA12.0.1 manual.



CR:748265
CR Number:   748265
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2003
Original Version:   16.0 sp02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp02 07 Oct 2013 Fixed
Description
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



CR:748702
CR Number:   748702
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Linux Red Hat
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Simple SELECT of 1 column returns wrong result set when:

- several columns are concatenated in SARG

- those columns are not in the SELECT list
Workaround Description
 Put in the SELECT list, the columns in the concatenation follows and the result set is correct



SELECT type, serving_network_mcc ||'_' || serving_network_mnc || '_' || mme_group||'_' || mme_code as concatenation

FROM test

WHERE concatenation = '208_01_32770_2'

AND timestamp_utc >= 1377591000 AND timestamp_utc < 1377594600 ;



CR:748729
CR Number:   748729
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   16.0 sp02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp03 24 Oct 2013 Fixed
Description
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.



CR:748900
CR Number:   748900
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 7
Original Version:   16.0 sp01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp03 07 Nov 2013 Fixed
Description
Cannot execute a LOAD TABLE from a client file when the server is running on Windows and the client is not.



CR:749167
CR Number:   749167
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   16.0 sp02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp02 29 Oct 2013 Fixed
16.0 sp03 12 Nov 2013 Fixed
Description
Failed RLV updates could result in lma memory leaks.



CR:749556
CR Number:   749556
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   15.4 e04.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10 Nov 2013 Fixed
11 Nov 2013 Fixed
Description
A subquery with min/max aggregate on union view may result in crash while estimating selectivity.



CR:749704
CR Number:   749704
Product Name:   Sybase IQ ETL
Product Component:   Execution
Status:   Closed
OS:   all
Original Version:   Denali
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12 Nov 2013 Presently Not Targeted For Any Future Release Of This Product
Description
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"
Workaround Description
 The Load Script must be manually edited to run successfully.



CR:750301
CR Number:   750301
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   16.0 sp03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp08 08 Nov 2013 Fixed
Description
Under some circumstances an insert ... select statement might result in a Non-Fatal IQ Internal Error Detected at vplib/vp_Projections.cxx:1105



CR:750325
CR Number:   750325
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   15.4 e01.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
01 Dec 2013 Fixed
Description
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.
Workaround Description
 If DBA modify query like below, it's ok.



select ln_apc_grp_no

,max(right(' '||incm_dv_cd,2)

||right(' '||incm_evdc_dv_cd,3)

||right(' '||trim(d2.cd_nm),50)

||right(' '||trim(d1.cd_nm),50)) as info1

,substr(info1,1,2) as incm_dv_cd2

,substr(info1,3,3) as incm_evdc_dv_cd2

,substr(info1,6,50) as ncm_dv_cd_nm2

,substr(info1,56,50) as incm_evdc_dv_cd_nm2

,rank() over (partition by ln_apc_grp_no order by incm_dv_cd2,incm_evdc_dv_cd2) as rnk

from eiim_apc_cus_yyincm_dtls a

left outer join eiar_com_cd_dmsn d1

on d1.cd_id = '17098'

and d1.cd = a.incm_evdc_dv_cd

left outer join eiar_com_cd_dmsn d2

on d2.cd_id = '14251'

and d2.cd = a.incm_dv_cd

where incm_tgt_dv_cd in ('01')

group by ln_apc_grp_no

;



CR:750349
CR Number:   750349
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   15.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12 Dec 2013 Duplicate
Description
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.



CR:751112
CR Number:   751112
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Linux Red Hat
Original Version:   15.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
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 ALLs is causing IQ to crash with and abort at st_server.cxx:1430 on calls QOG::addIfOuterReference QOG::FindViewColumn



CR:751113
CR Number:   751113
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Linux Red Hat
Original Version:   15.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Feature Request - full support for Common Table Expressions in IQ



Some aspect of using CTE's work, but others don't like using multiple CTEs , or CTEs containing VIEWs with joins and UNION ALLs, and also CTEs that end with a SELECT INTO.



CR:751477
CR Number:   751477
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   16.0 sp02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp08 28 Apr 2014 Fixed
16.0 sp04.x 08 May 2014 Fixed
Description
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.
Workaround Description
 One Plausible TEMPORARY workaround I can think of is to NOT to do NBit index



Using



sp_iqrebuildindex <tblname>, 'column <colname> [<count>]'



With count value == 0 or greater than 2,147,483,647 (i.e. say 3,147,483,647) will build FP index.



Or specify IQ_UNIQUE while creating table



This will have some performance impact and storage requirement (slightly more than Nbit), however I think it would be better than CRASHING 



CR:751837
CR Number:   751837
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Linux Red Hat
Original Version:   15.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
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'
Workaround Description
 use an object naming convention that will avoid likelihood of a table or view object being called the same



CR:751901
CR Number:   751901
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   15.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.2 e02.x 14 Jan 2014 Fixed
Description
LOAD TABLE may stop processing if not enough buffers are available.
Workaround Description
 drop hung LOAD's connection and restart it.



CR:751932
CR Number:   751932
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Windows 2003
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Sum and nested CASE WHEN run on reader can cause stack trace on writer
Workaround Description
 Do not use DQP

set temporary option DQP_Enabled='OFF'



CR:752513
CR Number:   752513
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   15.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Jan 2014 Consult Complete
Description
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



CR:752700
CR Number:   752700
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Suse
Original Version:   16.0 sp01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp08 12 Dec 2013 Fixed
16.0 sp08.x 22 Sep 2014 Already Fixed by Another CR
Description
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.
Workaround Description
 This issue can be avoided if the columns, oildetail_his.cardno

and oildetail_cur.cardno, and rebuilt as tokenized FPs. The 16.0

tokenized FPs can easily support a couple million distinct values

within a column, especially for varchar values of this size where

there should be a sizable storage space advantage.



CR:752758
CR Number:   752758
Product Name:   IQ
Product Component:   Install
Status:   Closed
OS:   Unknown
Original Version:   16.0 sp08
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp08 13 Dec 2013 Fixed
15.4 e04 13 Dec 2013 Fixed
Description
The Sybase Open Client included with this release has been updated to 15.7 SP122



CR:752851
CR Number:   752851
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   16.0 sp01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp08 15 Jan 2014 Fixed
16.0 sp08 15 Jan 2014 Fixed
17 Nov 2014 Fixed
Description
A server failure may occur on a double throw during a LOAD from a client file.



CR:753244
CR Number:   753244
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   15.4 e03.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
02 Jan 2014 Fixed
02 Jan 2014 Fixed
Description
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.



CR:753289
CR Number:   753289
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   16.0 sp02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp03.x 20 Dec 2013 Fixed
16.0 sp08 02 Jan 2014 Fixed
16.0 sp03.x 15 Jan 2014 Fixed
16.0 sp08 20 Jan 2014 Fixed
16.0 sp03.x 17 Jan 2014 Fixed
16.0 sp03.x 04 Mar 2014 Fixed
16.0 sp08 07 Mar 2014 Fixed
16.0 sp03.x 06 Mar 2014 Fixed
16.0 sp04 15 May 2014 Fixed
Description
Uncorrelated subqueries are not pushed down into a union-all-view if the select list includes nulls, constants, or casts.



CR:753327
CR Number:   753327
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Windows 2008
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
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.
Workaround Description
 Please cast decrypt data to character type.



select cast(aes_decrypt(col1,'key', int) as char(1)) as col1_enc from test001;



CR:753363
CR Number:   753363
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   16.0 sp02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp08 19 Mar 2014 Fixed
Description
Loading a table from a compressed file may not always load the correct number of rows.



CR:753873
CR Number:   753873
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Unknown
Original Version:   16.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp08 03 Apr 2014 Added to user documentation
Description
sp_iqpassword is supported for backward compatibility.

Changing the password using the ALTER USER statement.



CR:754394
CR Number:   754394
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Linux Red Hat
Original Version:   16.0 sp08
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp08 10 Feb 2014 Added to user documentation
15.4 e04 10 Feb 2014 Added to user documentation
Description
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'.



CR:754435
CR Number:   754435
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Unknown
Original Version:   16.0 sp03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp08 15 Jan 2014 Fixed
Description
Description of "-gm" is not correct.

maximum value of "-gm" is as follows.

UNIX/Linux: 1001, Windows: 200



CR:754494
CR Number:   754494
Product Name:   IQ
Product Component:   SA Component
Status:   Open
OS:   Unknown
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
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.



CR:754539
CR Number:   754539
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Linux Red Hat
Original Version:   15.4 e03.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
A combination of GROUP BY and DISTINCT cannot evaluate expression the column.



CR:755399
CR Number:   755399
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   AIX
Original Version:   16.0 sp03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp08 25 Mar 2014 Fixed
Description
OS400 ODBC Connections might report an insufficient length of SATMP. This has been fixed.



CR:755733
CR Number:   755733
Product Name:   IQ
Product Component:   SA Component
Status:   Open
OS:   Windows 2008
Original Version:   15.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
If include an IQ table and IN SYSTEM in the FROM clause, the placeholder does not work.
Workaround Description
 Do not use placeholder with IN SYSTEM.



CR:755823
CR Number:   755823
Product Name:   IQ
Product Component:   Install
Status:   Closed
OS:   Unknown
Original Version:   15.4 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.4 e04 07 Feb 2014 Fixed
15.4 e04 10 Feb 2014 Fixed
Description
The JRE includes with this release has been updated to SAP JRE 6.1.061



CR:755824
CR Number:   755824
Product Name:   IQ
Product Component:   Install
Status:   Closed
OS:   Unknown
Original Version:   16.0 sp08
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp08 22 Feb 2014 Fixed
Description
The JRE included in this release has been upgraded to SAP JRE 7.1.014



CR:756388
CR Number:   756388
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   16.0 sp03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp09 13 Jun 2014 Fixed
16.0 sp04.x 19 Jun 2014 Fixed
16.0 sp08.x 11 Jul 2014 Fixed
Description
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
Workaround Description
 Drop the DTTM index



CR:756578
CR Number:   756578
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   15.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12 Feb 2014 Fixed
Description
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.



CR:757044
CR Number:   757044
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   15.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
04 Mar 2014 Fixed
Description
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.



CR:757547
CR Number:   757547
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Linux Red Hat
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
When temp cache is insufficient, DISTINCT and ORDER BY return the wrong rows.

This problem reappears only when temp cache is short.
Workaround Description
 specify the ORDER BY DESC on the results of the inner join.



select * from (select distinct x.S_NO, x.R_DD from BUG_MAN_P x

inner join (select S_NO from BUG_MAN_Q group by S_NO) y on y.S_NO = x.S_NO) z

order by z.S_NO desc;



CR:758272
CR Number:   758272
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   15.4 e03.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.4 e05 10 Mar 2014 Fixed
16.0 sp08 12 Mar 2014 Fixed
15.4 e05 21 Mar 2014 Fixed
Description
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.



CR:758302
CR Number:   758302
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   15.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.4 e02.x 15 May 2014 Fixed
Description
*** 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.



CR:758405
CR Number:   758405
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   15.4 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp08 05 Mar 2014 Fixed
15.4 e04.x 03 Nov 2014 Fixed
15.4 e05 09 Dec 2014 Fixed
Description
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.



CR:758683
CR Number:   758683
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Solaris
Original Version:   16.0 sp03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Alter/Create Server: remove reference to ASEJDC



CR:758762
CR Number:   758762
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   16.0 sp04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
02 Jul 2014 Fixed
Description
Statistics collection is not working with European locales



CR:758769
CR Number:   758769
Product Name:   IQ
Product Component:   Documentation
Status:   Open
OS:   Unknown
Original Version:   15.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
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.



CR:758876
CR Number:   758876
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   16.0 sp03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
24 Apr 2014 Fixed
24 Apr 2014 Fixed
16.0 sp08.x 28 May 2014 Fixed
Description
Data Extract using named pipe, causes error:

Tape IO Error /tmp/dam

-- (oslib/hos_ion.cxx 147)

SQLCODE=-1006162, ODBC 3 State="HY000"



CR:758904
CR Number:   758904
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Linux Red Hat
Original Version:   16.0 sp03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp03.x 05 Mar 2014 Fixed
16.0 sp08 18 Mar 2014 Fixed
16.0 sp04 Fixed
Description
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.
Workaround Description
 set option dml_options13 = 32



CR:759084
CR Number:   759084
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   16.0 sp03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
05 Mar 2014 Fixed
16.0 sp04 01 May 2014 Fixed
Description
Under some circumstances an INSERT ... SELECT query might return a non-fatal internal error at vp_Projections.cxx:1105 when a word index exists.



CR:759212
CR Number:   759212
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   15.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
18 Aug 2014 Fixed
Description
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.
Workaround Description
 drop the hung connections



CR:759231
CR Number:   759231
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Unknown
Original Version:   15.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.4 e05 20 Nov 2014 Added to user documentation
16.0 sp08.x 21 Nov 2014 Added to user documentation
Description
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;

-- --



CR:759279
CR Number:   759279
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   AIX
Original Version:   16.0 sp03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0 sp08 11 Apr 2014 Added to user documentation
Description
When C compiler has been installed in a system, "IBM XL C/C++ Compiler Update" wil be necessary.





--------------------------------------华丽的分割线-------------------------------------------------------------------------

Sybase SQL Anywhere数据库恢复工具ReadASADB:

之前就已经研发成功了能够从Sybase SQL Anywhere的DB文件中恢复数据的工具: ReadASADB。
此工具支持ASA v5.0, v6.0, v7.0, v8.0, v9.0, v10.0, v11.0, v12.0, v16.0, v17.0等版本。
能够从损坏的SQL Anywhere数据文件(.db)和UltraLite数据文件(.udb)上提取数据的非常规恢复工具。
恢复Sybase SQL Anywhere的工具在国内处于领先水平。

Sybase SQL Anywhere数据库恢复工具ReadASADB功能
能够从损坏的SQL Anywhere数据文件(.db)和UltraLite数据文件(.udb)上提取数据的非常规恢复工具
  1. 适用于所有的SQL Anywhere版本    包括:5.x,6.x,7.x,8.x,9.x,10.x,11.x,12.x,16.x,17.x
  2. 适用于所有的UltraLite版本
  3. 能够恢复出来表结构和数据
  4. 能够恢复自定义数据类型
  5. 能够恢复存储过程等对象的语法
  6. 能够导出到目标数据库
  7. 能够导出到SQL文件并生成导入脚本
  8. 支持多种字符集,包括:cp850、cp936、gb18030、utf8等
  9. 能够恢复未加密或者简单加密类型的数据
  10. 简单易用
  11. 限制:不支持AES加密的数据文件
请参考:研发成功了从Sybase SQL Anywhere的DB文件上恢复数据的工具
            SQL Anywhere数据库非常规恢复工具ReadASADB使用介绍

Sybase SQL Anywhere数据库恢复工具ReadASADB适用场景

各种误操作:

  1. 误截断表(truncate table)
  2. 误删除表(drop table)
  3. 错误的where条件误删数据
  4. 误删除db或log文件
  5. 误删除表中的字段

Sybase SQL Anywhere数据库恢复工具ReadASADB的应用场景:

1.因为物理磁盘故障、操作系统、系统软件方面或者掉电等等原因导致的Sybase SQL Anywhere数据库无法打开的情况;
2.误操作,包括truncate table,drop table,不正确的where条件导致的误删除等;
Sybase SQL Anywhere无法打开时,比较常见的错误是:Assertion failed。
如:
1、Internal database error *** ERROR *** Assertion failed:201819 (8.0.1.2600) Checkpoint log: invalid bitmap page -- transaction rolled back
2、Internal database error *** ERROR *** Assertion failed:201819 (8.0.1.2600) Page number on page does not match page requested -- transaction rolled back
3、Internal database error *** ERROR *** Assertion failed:200502 (9.0.2.2451) Checksum failure on page 23 -- transaction rolled back
4、File is shorter than expected
5、Internal database error *** ERROR *** Assertion failed: 201116 Invalid free list index page found while processing checkpoint log -- transaction rolled back
6、*** ERROR *** Assertion failed: 51901 Page for requested record not a table page or record not present on page
7、*** ERROR *** Assertion failed: 201417 (7.0.4.3541) Invalid count or free space offset detected on a table page
8、Internal database error *** ERROR *** Assertion failed: 201425 (8.0.3.5594) Invalid count or free space offset detected on a free list page -- transaction rolled back.
9、Internal database error *** ERROR *** Assertion failed: 100702 (8.0.1.2600) Unable to modify indexes for a row referenced in rollback log -- transaction rolled back


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

Sybase ASE数据库恢复工具READSYBDEVICE:

一个不依赖数据库管理系统、直接从Sybase数据库设备文件上提取数据的业内领先的恢复工具!
能够从损坏的Sybase ASE设备文件(.dat)上提取数据的非常规恢复工具。

Sybase ASE数据库恢复工具READSYBDEVICE的主要功能:

  1. 被勒索病毒加密数据文件及备份文件情况下的恢复;
  2. 系统崩溃只剩下数据文件的情况下的恢复,甚至数据库文件不存在而只有损坏的备份文件情况下的恢复;
  3. 因断电、硬盘坏道等造成数据库文件损坏情况下的恢复;
  4. delete数据恢复、误update数据恢复、误删除表(drop)恢复、误truncate表恢复 等;
  5. 各种Sybase内部系统表损坏、索引错误的修复;
  6. master数据库损坏而无法正常运行情况下的恢复;
  7. Sybase数据库被标记为可疑,不可用等情况的恢复;
  8. Sybase数据库中数据文件内部出现坏块情况下的恢复;
  9. Sybase数据库无数据文件但有日志文件的情况下的恢复;
  10. Sybase数据库只有数据文件无任何日志文件的情况下的恢复;
  11. Sybase数据文件被误删除情况下的碎片提取恢复;
  12. 磁盘阵列上的Sybase数据库被误格式化情况下的数据库恢复;
  13. 数据库sysobjects等系统表损坏无法正常应用情况下的恢复;
  14. Sybase数据库还原数据库出现失败情况下的恢复;
  15. Sybase数据库只剩下损坏的备份文件情况下的恢复。

Sybase ASE数据库恢复工具READSYBDEVICE支持的版本:

Sybase ASE 11.0.x,11.5.x,11.9.x,12.0.x,12.5.x,15.0.x,15.5.x,15.7.x,16.0.x


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

SQL Server数据库恢复工具SQLRescue:

一个不依赖数据库管理系统、直接从SQL Server数据库文件上提取数据的业内领先的恢复工具!
能够从损坏的SQL Server数据库文件(.mdf)上提取数据的非常规恢复工具。

SQL Server数据库恢复工具SQLRescue的主要功能:

  1. 系统崩溃只剩下数据文件的情况下的恢复,即无日志文件或者日志文件损坏情况下的恢复;
  2. 断电导致数据库文件损坏情况下的恢复;
  3. 硬盘坏道造成数据库损坏情况下的恢复;
  4. 数据文件内部存在坏页情况下的恢复;
  5. 企业管理器误删除数据表记录,管理软件误删除数据表记录的恢复;
  6. 并闩锁错误、格式化、误删除后导致软件不能使用的情况;
  7. 无法读取并闩锁页sysindexes失败情况下的修复;
  8. 数据文件被误删除情况下的碎片提取恢复;
  9. 系统表损坏、索引错误、误删除数据库表、删除记录的数据找回;
  10. master数据库损坏而无法正常运行情况下的恢复;
  11. 数据文件无法附加情况下的数据恢复;
  12. 数据库被标记为可疑,质疑,不可用等情况的恢复;
  13. 数据库sysobjects等系统表损坏情况下的恢复;
  14. 数据被误(drop、delete、truncate)删除表数据的恢复,误update后的数据恢复等;
  15. 还原时报一致性错误,错误823等情况下的数据恢复,各种错误提示的数据库文件修复;
  16. 数据库被误格式化等情况下的数据库恢复;
  17. 日志收缩造成数据库损坏情况下的恢复;
  18. 仅剩损坏的备份文件情况下的恢复。

SQL Server数据库恢复工具SQLRescue技术特点:

只要SQL Server数据库的数据文件存在,我们就有办法帮您从数据文件中找回重要数据。
  1. 从数据文件中直接恢复数据
  2. 不能附加时直接恢复数据并生成新的数据库
  3. 系统表损坏的数据库修复
  4. 快速修复SQL 823错误、连接中断错误

SQL Server数据库恢复工具SQLRescue支持的版本:

Microsoft SQL Server 7.0, 2000, 2005, 2008, 2008R2, 2012, 2014, 2016, 2017,2019。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------