提供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:583821
CR Number:   583821
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux
Original Version:   15.0 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e01 31 Aug 2009 Fixed
Description
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.



CR:584121
CR Number:   584121
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Windows XP
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 l10n 29 Sep 2009 Workaround
15.1 l10n 27 Oct 2009 Fixed
Description
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"



CR:584317
CR Number:   584317
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Solaris
Original Version:   12.7 future
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.2 02 Nov 2009 Fixed
Description
Request detail info on sp_iqlocklogin mechanism on MPX environment (12.7)



CR:584334
CR Number:   584334
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Unknown
Original Version:   12.7 future
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.2 26 Jan 2010 Added to user documentation
Description
Request to document the new procedure behavior in IQ 12.7/15.x



CR:584796
CR Number:   584796
Product Name:   IQ
Product Component:   Install
Status:   Closed
OS:   Linux
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
09 May 2011 Presently Not Targeted For Any Future Release Of This Product
Description
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



CR:585094
CR Number:   585094
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
22 Jun 2010 Not reproducible with latest version of the product available as of Resolution Date
Description
IQ15.1 cannot allocate the memory of the class defined by UDF.



CR:586168
CR Number:   586168
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e01 25 Sep 2009 Fixed
12.7 e09 22 Sep 2009 Fixed
15.2 25 Jan 2010 Fixed
Description
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.



CR:586398
CR Number:   586398
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.7 e05.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
18 Nov 2009 Presently Not Targeted For Any Future Release Of This Product
01 Dec 2009 Not a Bug
Description
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.
Workaround Description
 supply server-name or 'all server' argument to sp_iqlocklogin



1. lock user after on all nodes :



(DBA)> sp_iqlocklogin 'mpxuser','lock','all servers' ;

Execution time: 0.025 seconds



2. lock user on specified node:



(DBA)> sp_iqlocklogin 'mpxuser','lock','iq127w'

Execution time: 0.031 seconds



CR:587239
CR Number:   587239
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   15.0 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e01 01 Sep 2009 Fixed
Description
An update statement issued against a partitioned table could cause a server abort in some cases. This is now fixed.



CR:587376
CR Number:   587376
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.7 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e07.x 02 Sep 2009 Fixed
Description
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.
Target Version
 12.7 e07.x



CR:588089
CR Number:   588089
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   15.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
19 Jan 2015 Fixed
Description
This is a test of the Customer Description for IQ EBF generation



CR:588091
CR Number:   588091
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.7 e05.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e09 30 Sep 2009 Fixed
12.7 e05.x 21 Sep 2009 Fixed
17 Dec 2009 Not reproducible with latest version of the product available as of Resolution Date
17 Dec 2009 Not reproducible with latest version of the product available as of Resolution Date
Description
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.



CR:588210
CR Number:   588210
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e10
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e09 23 Sep 2009 Fixed
15.1 e01 23 Sep 2009 Fixed
07 Jun 2010 Presently Not Targeted For Any Future Release Of This Product
Description
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.



CR:588519
CR Number:   588519
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 Sep 2009 Consult Complete
15.1 e03 18 Jan 2010 Fixed
15.1 e02.x 04 Feb 2010 Fixed
15.2 05 Feb 2010 Fixed
Description
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.



CR:588869
CR Number:   588869
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Oct 2009 Added to user documentation
20 Jul 2010 Fixed
20 Jul 2010 Fixed
Description
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.



CR:589023
CR Number:   589023
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e09 21 Oct 2009 Fixed
15.1 e03 21 Oct 2009 Fixed
15.2 29 Oct 2009 Fixed
Description
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.
Workaround Description
 Use a different form of the load table statement to do the load. Instead of "with null byte", use an appropriate NULL clause in the column spec.



CR:589239
CR Number:   589239
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Linux Red Hat
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.2 05 Oct 2009 Added to user documentation
Description
LIKE clause: document supported patterns of length between 127 and 254 chars



CR:589290
CR Number:   589290
Product Name:   IQ
Product Component:   SA Component
Status:   Open
OS:   Linux Red Hat
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
LIKE clause: support patterns of length of 254 chars



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



CR:589727
CR Number:   589727
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   15.1 l10n
Fixed Version Build Resolution Date Closure Code (If Appropriate)
19 Nov 2009 Duplicate
Description
The issue is closed as not a bug, since we donot support heterogeneous charset environment in localization release
Target Version
 15.1 l10n



CR:589813
CR Number:   589813
Product Name:   IQ
Product Component:   SA Component
Status:   Open
OS:   Solaris
Original Version:   12.7 e05.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
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



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



CR:590373
CR Number:   590373
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e03 14 Jan 2010 Fixed
15.2 26 Jan 2010 Fixed
Description
(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.



CR:590388
CR Number:   590388
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Solaris
Original Version:   12.7 e05.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
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.



CR:590578
CR Number:   590578
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e03 15 Dec 2009 Fixed
15.2 21 Jan 2010 Fixed
Description
Query with join between sp_iqmpxincheartbeatinfo, sp_iqmpxincconnpoolinfo and sysiqmpxserver crashed coordinator node. This has been fixed.



CR:590621
CR Number:   590621
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.2 15 Jan 2010 Fixed
14 Jan 2010 Fixed
15.1 e03 18 Jan 2010 Fixed
Description
Inserting the @@identity value into an IQ base or temporary table causes the server to

crash. This has been fixed.



CR:590781
CR Number:   590781
Product Name:   IQ
Product Component:   Utility
Status:   Closed
OS:   Linux Red Hat
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.2 16 Dec 2009 Fixed
Description
dbisql ignores SQLCONNNECT environment variable setting, while other utilities e.g dbisqlc , dbvalid and dbinfo works.
Workaround Description
 Workaround From CR 543350:

[sybase@rhvm mydemo]$ setenv SQLCONNECT "uid#DBA;pwd#sql;eng#iqdemo"

[sybase@rhvm mydemo]$ dbisql -c $SQLCONNECT -nogui



(DBA)>



CR:590928
CR Number:   590928
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
30 Nov 2009 Consult Complete
15.1 e03 21 Dec 2009 Fixed
12.7 e10 07 Mar 2010 Fixed
15.2 20 Apr 2010 Fixed
Description
Performance improvement for WD index for the 0 length, constant, unique data.



CR:591507
CR Number:   591507
Product Name:   IQ
Product Component:   Sybase Central
Status:   Open
OS:   Windows XP
Original Version:   15.1 l10n
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
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)"



CR:591514
CR Number:   591514
Product Name:   IQ
Product Component:   Utility
Status:   Closed
OS:   Windows XP
Original Version:   15.1 l10n
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 l10n 29 Sep 2009 Workaround
Description
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.



CR:591575
CR Number:   591575
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows XP
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.2 06 Nov 2009 Fixed
Description
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.



CR:591586
CR Number:   591586
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows XP
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.2 06 Nov 2009 Fixed
Description
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.



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



CR:592288
CR Number:   592288
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
20 Apr 2010 Fixed
Description
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.
Workaround Description
 Use stored proc and it helps in passing table name



create procedure test_proc_2 (in tablenm char(50))

result (a bigint)

begin

execute immediate with result set ON

'select rowcount from (select count(*) as rowcount from ' || tablenm || ') mdr_count'

end



create procedure test_proc_1 (in tablenm char(50))

result (a bigint)

begin

call test_proc_2(tablenm)

end



call test_proc_1 ('mdr')



CR:593125
CR Number:   593125
Product Name:   IQ
Product Component:   Install
Status:   Closed
OS:   Windows XP
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
08 Mar 2010 Not reproducible with latest version of the product available as of Resolution Date
Description
15.1 ESD1 on windows creates dbisql.ini.token which is a template file used by the installer to build the dbisql.ini file



CR:593288
CR Number:   593288
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   12.7 e07
Fixed Version Build Resolution Date Closure Code (If Appropriate)
22 Jun 2010 Fixed
Description
Server crashes when big string is attempted to be logged in .srvlog using "message" command



CR:593353
CR Number:   593353
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
08 Dec 2009 Duplicate
Description
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



CR:593431
CR Number:   593431
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e03 15 Jan 2010 Fixed
15.2 25 Jan 2010 Fixed
Description
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 )
Workaround Description
 *** Wednesday, January 06, 2010 10:33:12 AM *** aldrich ***

dml_options9 = 8 or dml_options6 = 25165824



CR:593620
CR Number:   593620
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e02.x 28 Apr 2010 Fixed
14 Apr 2010 Duplicate
15.2 e02 11 Oct 2010 Added to user documentation
09 Aug 2010 Fixed
15.4 27 Jul 2011 Fixed
04 Aug 2011 Fixed
Description
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.



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



CR:594278
CR Number:   594278
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Solaris
Original Version:   15.1 l10n
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 l10n 16 Oct 2009 Added to user documentation
15.1 l10n 22 Oct 2009 Fixed
Description
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.



CR:594291
CR Number:   594291
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.7 e07
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e11 08 Dec 2010 Duplicate
Description
Fixed in CR 594295
Workaround Description
 none yet determined



CR:594295
CR Number:   594295
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.7 e07
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e11 04 Jan 2011 Fixed
Description
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.
Workaround Description
 none yet identified



CR:594307
CR Number:   594307
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   12.7 e07
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e09 17 Dec 2009 Fixed
15.1 e03 19 Jan 2010 Fixed
15.2 27 Jan 2010 Fixed
Description
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;



CR:594329
CR Number:   594329
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   15.0 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 l10n 06 Nov 2009 Fixed
15.1 e03 21 Jan 2010 Fixed
15.2 21 Jan 2010 Fixed
Description
Update fails with "Bitmap failed internal checks" on IQ 15.1.



CR:594335
CR Number:   594335
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Unknown
Original Version:   15.0 future
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
NFR: Enhance internal bitmap error to provide index name.



CR:594473
CR Number:   594473
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Unknown
Original Version:   12.7 e07
Fixed Version Build Resolution Date Closure Code (If Appropriate)
19 Nov 2009 Fixed
Description
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.



CR:594477
CR Number:   594477
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
07 Jan 2010 Not a Bug
Description
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)
Workaround Description
 Reboot IQ Server



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



CR:594901
CR Number:   594901
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Unknown
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.2 12 Jan 2010 Fixed
Description
Add to IQ Doc the dbfiles max number and the size limits.



CR:594903
CR Number:   594903
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Linux Suse
Original Version:   15.1 future
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Request to certified IQ on SUSE 11 version.



CR:595216
CR Number:   595216
Product Name:   IQ
Product Component:   SA Component
Status:   Open
OS:   HP-UX
Original Version:   12.7 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
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.
Workaround Description
 Please add "CS=utf8" to a connection strings.



CR:595252
CR Number:   595252
Product Name:   IQ
Product Component:   Install
Status:   Closed
OS:   Solaris
Original Version:   15.1 l10n
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 Aug 2011 Presently Not Targeted For Any Future Release Of This Product
Description
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.



CR:595311
CR Number:   595311
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e03 01 Dec 2009 Fixed
15.2 14 Dec 2009 Fixed
Description
The error message is changed from "Internal programming error" to "Host variable '@varname' is not initialized" in df_Heap.cxx.
Workaround Description
 *** Monday, October 26, 2009 10:45:13 AM *** ate ***

Workaround is: set temporary option tsql_variables = 'OFF'

If they set this option they wil not get the Internal Error. Even when we fix this internal error, they will still get an error returned from the statement unless they

set this because of the documented behavior of tsql variables.



Sybase 365 does not have good work around since they can not use dbisqlc or dbisql in their processing. They must use iqisql or Java.



CR:595315
CR Number:   595315
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Unknown
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e03 02 Feb 2010 Fixed
Description
IF/CASE statement caused IQ server failure when both sides of the expression used IQ tables on IQ15.x release.



CR:595383
CR Number:   595383
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows XP
Original Version:   15.1 l10n
Fixed Version Build Resolution Date Closure Code (If Appropriate)
01 Feb 2012 Not a Bug
15.1 l10n 02 Nov 2009 Fixed
Description
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.
Workaround Description
 A workaround: start the IQ agent using the uaser account who logged onto

the IQ server host:



In the Windwos service list,

right click Sybase IQ Agent 15.1 -> Properties -> the "Log On" tab -> This account,

and enter

<network domain name>\<the user account ID that is used to log on to the IQ server host>

(e.g., sybase\jsmith)

the password, confirm the password, and click the OK button.

Then start the IQ agent by right clicking Sybase IQ Agent 15.1 in the service list and selecting Start.



CR:595873
CR Number:   595873
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e03 15 Jan 2010 Fixed
15.2 21 Jan 2010 Fixed
Description
Server crash with Assertion failed error "Table lock inconsistency" on IQ 15.x/
Workaround Description
 set option PUBLIC.SUBSUME_ROW_LOCKS ='OFF';



CR:595881
CR Number:   595881
Product Name:   IQ
Product Component:   Utility
Status:   Closed
OS:   Windows 2003
Original Version:   15.1 l10n
Fixed Version Build Resolution Date Closure Code (If Appropriate)
27 Oct 2009 Added to user documentation
15.1 e03 04 Mar 2010 Fixed
15.1 l10n 27 Oct 2009 Fixed
Description
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>"



CR:595888
CR Number:   595888
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Suse
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e03 04 Nov 2009 Fixed
15.2 01 Dec 2009 Fixed
Description
IQ 15.1: Query resulted in server failure with "Destroying logical locked buffer".
Workaround Description
 Plausible workarounds to try,

To avoid nlpd join

set temporary option join_preference = '-3'.



If the above WA doesn't help , try disabling prefetch

set temporary option dml_options1='128'



--update by shashi



CR:595990
CR Number:   595990
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Unknown
Original Version:   12.7 future
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Provide better diagnostics instead of "NO COMMAND OR CURSOR ACTIVE" in the stacktrace.



CR:596186
CR Number:   596186
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Linux Red Hat
Original Version:   12.7 future
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Request certification of IQ 12.7 & IQ 15.1 on Red Hat Enterprise Linux 5.4



CR:596192
CR Number:   596192
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Unknown
Original Version:   15.0 future
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Request to implement temp store resources management feature similar to ASE tempdbs feature.



CR:596648
CR Number:   596648
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows XP
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e03 10 Dec 2009 Fixed
15.2 15 Dec 2009 Fixed
Description
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.



CR:605035
CR Number:   605035
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.7 e07
Fixed Version Build Resolution Date Closure Code (If Appropriate)
05 Jun 2013 EOL'd version. Not to be Fixed.
12.7 e09 10 Nov 2009 Fixed
Description
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.



CR:605246
CR Number:   605246
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Unknown
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
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
Workaround Description
 iqunload -au -v -c "UID=DBA;PWD=SQL;DBF=asiqdemo.db;START= -z -zr ALL -o sqldb127.log"



CR:605272
CR Number:   605272
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   SunOS
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.2 06 Jan 2010 Fixed
15.1 e03 08 Jan 2010 Fixed
Description
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.



CR:605407
CR Number:   605407
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
01 Dec 2009 Fixed
15.1 e03 21 Dec 2009 Fixed
15.2 21 Dec 2009 Fixed
Description
Predicate range simplifications have been expanded to be more aggressively simplify range predicates. This enhances performance in many cases.



CR:605410
CR Number:   605410
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.2 e01 07 May 2010 Fixed
15.2 e01 15 Jun 2010 Fixed
15.3 20 Jul 2010 Fixed
Description
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.
Workaround Description
 grante update,delete and references permission to the user.



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



CR:605523
CR Number:   605523
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.7 e07
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 01 Dec 2009 Presently Not Targeted For Any Future Release Of This Product
Description
Sybase IQ will output SQL of the client connected via iAnywhere JDBC using a client character set. It differs from character collation of DB.
Workaround Description
 Please use jConnect for a connection driver.



CR:606047
CR Number:   606047
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Unknown
Original Version:   12.7 future
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Documentation: Update/Delete not allowed when SA functions used on IQ table



CR:606207
CR Number:   606207
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Unknown
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e03 14 Jan 2010 Fixed
15.2 27 Jan 2010 Fixed
Description
Sybase central crashes when we try to add a primary key to a table which does not have one.

This has been fixed.



CR:606223
CR Number:   606223
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   12.7 e07
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e09 10 Nov 2009 Fixed
12.7 e08 16 Nov 2009 Fixed
Description
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.



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



CR:606494
CR Number:   606494
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Unknown
Original Version:   15.1 future
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Feature request to allow update on a view with UNION ALL on IQ.



CR:606813
CR Number:   606813
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Linux Red Hat
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.2 18 Feb 2010 Fixed
24 Feb 2010 Fixed
15.2 18 Feb 2010 Fixed
Description
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
Workaround Description
 supply User ID and Password on sybase central connection screen



CR:607029
CR Number:   607029
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Unknown
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e03 23 Dec 2009 Fixed
Description
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]".



CR:607041
CR Number:   607041
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e03 21 Dec 2009 Fixed
15.2 21 Dec 2009 Fixed
15.1 e02 10 Jan 2010 Fixed
Description
Multiplex -- A server in a multiplex can become unresponsive involving calling the

sp_iqconnection stored procedure. This has been fixed.



CR:607060
CR Number:   607060
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e03 18 Dec 2009 Fixed
15.2 22 Dec 2009 Fixed
Description
Deleting rows from a table which has a multi-column HG index defined may cause the

server to abort. This has been fixed.
Workaround Description
 Customer downgraded to 15.1 GA and problem went away.



CR:607152
CR Number:   607152
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   HP-UX
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.2 future
01 Nov 2011 Fixed
16.0 25 Dec 2011 Not reproducible with latest version of the product available as of Resolution Date
Description
If RANK() function has more than one column in PARTITION BY clause, an exception is thrown from df_MapRecordToDFEs::InitAddDFE.
Workaround Description
 set options DML_OPTIONS9=8



CR:607233
CR Number:   607233
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   SunOS
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.2 24 Nov 2009 Fixed
15.1 e03 02 Dec 2009 Fixed
15.1 e02 02 Dec 2009 Fixed
Description
In some cases where a host variable is assigned to a long varbinary or long varchar, IQ may return an incorrect value.



CR:607427
CR Number:   607427
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Unknown
Original Version:   12.7 future
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e10 09 Feb 2010 Added to user documentation
Description
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



CR:607560
CR Number:   607560
Product Name:   IQ
Product Component:   Install
Status:   Closed
OS:   Linux Red Hat
Original Version:   15.1 l10n
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 Aug 2011 Presently Not Targeted For Any Future Release Of This Product
Description
When a customer generates the license files by SPDC, selecting a different lisence on IQ installer causes the down of an installer.
Workaround Description
 Please set "C" to be a LANG environment variable.



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



CR:607869
CR Number:   607869
Product Name:   IQ
Product Component:   SA Component
Status:   Open
OS:   AIX
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
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



CR:607889
CR Number:   607889
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.7 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e09 02 Mar 2010 Fixed
Description
A query with a large number of OR statements caused

an IQ server failure.
Workaround Description
 Increase SA thread size (-gss) and IQ thread size (-iqtss).



CR:607963
CR Number:   607963
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   12.7 e07
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11 Dec 2009 Presently Not Targeted For Any Future Release Of This Product
Description
dbisql should raise error message instead of quitting if symbolic link to jre142 directory is missing, and returning exit code 0(i.e success)



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



CR:608113
CR Number:   608113
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e10 18 May 2010 Fixed
15.2 e01 18 May 2010 Fixed
12.7 e08.x 18 May 2010 Fixed
15.3 03 Jun 2010 Fixed
Description
The Sybase IQ server appeared to stop processing for a

period of time, when a long running connection was

disconnecting.



CR:608228
CR Number:   608228
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.7 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
23 Dec 2009 Consult Complete
Description
This problem is resolved in OCS 15.0 ESD#23
Workaround Description
 1) Modification Esql/C code :

Long type => Double



CR:608411
CR Number:   608411
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
24 Nov 2009 Presently Not Targeted For Any Future Release Of This Product
Description
Please add ANSI SQL-99 select .. with recursive queries to IQ.



CR:608483
CR Number:   608483
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
26 Oct 2010 Fixed
Description
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.



CR:608611
CR Number:   608611
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows XP
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e02 10 Dec 2009 Fixed
15.1 e02 04 Jan 2010 Fixed
15.1 e03 25 Feb 2010 Added to user documentation
Description
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).



CR:608612
CR Number:   608612
Product Name:   IQ
Product Component:   Sybase Central
Status:   Open
OS:   Windows XP
Original Version:   12.7 e07
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
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.



CR:609079
CR Number:   609079
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   AIX
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
07 Dec 2009 Fixed
15.1 e03 02 Feb 2010 Added to user documentation
Description
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
Target Version
 15.1 e02



CR:609124
CR Number:   609124
Product Name:   IQ
Product Component:   Sybase Central
Status:   Open
OS:   Windows XP
Original Version:   12.7 e07
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
When two IQ servers have started on the same host, dbisql started from Central may be connected to a different IQ server.
Workaround Description
 Please change into jConnect JDBC the connection driver which Sybase Central uses. Or please use "{}" for a TCPIP startup parameter.



CR:609252
CR Number:   609252
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e03 29 Jan 2010 Fixed
15.2 29 Jan 2010 Fixed
15.2 12 Feb 2010 Fixed
Description
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".



CR:609728
CR Number:   609728
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows XP
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e03 12 Jan 2010 Fixed
15.1 e02 12 Jan 2010 Fixed
15.2 21 Jan 2010 Fixed
Description
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.



CR:609918
CR Number:   609918
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   AIX
Original Version:   12.7 future
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e10 24 Mar 2010 Fixed
15.2 24 Mar 2010 Fixed
15.3 24 Mar 2010 Fixed
Description
A performance improvement has been implemented for the

xp_cmdshell procedure on AIX and Linux platforms (already

implemented on Sun).



CR:609935
CR Number:   609935
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   15.1 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 e03 06 Jan 2010 Fixed
14 Jan 2010 Fixed
15.2 22 Jan 2010 Fixed
15.2 18 Aug 2010 Fixed
Description
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.





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

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。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------