提供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:534679
CR Number:   534679
Product Name:   IQ
Product Component:   SA Component
Status:   Open
OS:   Windows NT
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
When using dbisql and the jConnect driver if you call a procedure that tries to insert a duplicate value into a table column with a primary key constraint , the insert fails but no error message is produced. Using the JDBC driver you get the "Tried to insert a duplicate value into a unique Index. SQLCODE = -1002003 HY000" error message.



CR:535214
CR Number:   535214
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.7 e04.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
05 Sep 2008 Consult Complete
Description



CR:535465
CR Number:   535465
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Linux Red Hat
Original Version:   12.7 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
IQ will output a conversion error, when data including a different character code is used for load table. However, a conversion error may not be outputted at the time of "STRIP ON."



CR:535527
CR Number:   535527
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   12.7 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 30 Sep 2008 Fixed
Description
In order to avoid the problems described by this CR, one should not begin or end dabtabase object names with space characters.



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

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

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

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



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



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

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

For example,

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

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

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

An exception is:

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

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



CR:535561
CR Number:   535561
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Unknown
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e05.x 3632 07 Jul 2009 Fixed
12.7 e06 3632 06 Apr 2009 Fixed
Description
For a statement of the form "EXEC

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

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

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

single integer parameter for binding with a status of

DB_E_UNAVAILABLE. As such, the EXEC statement failed

with an error.



CR:535796
CR Number:   535796
Product Name:   Sybase IQ ETL
Product Component:   ETL Connectivity
Status:   Open
OS:   all
Original Version:   4.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25688
15 Jul 2008 Failed
09 Nov 2008 Fixed
19 Dec 2008 Fixed
19 Dec 2008 Fixed
Description
Problem: DB-Lookup takes additional memory for every block

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



CR:536049
CR Number:   536049
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2003
Original Version:   12.7 e04.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e05.x 18 Jul 2008 One-off Provided
09 Jul 2010 One-off Provided
Description
IQ will crash silently, when a certain SQL is executed. A lot of GROUP BY is included in SQL. And this issue is not reproduced when an index is deleted from a table.



CR:536059
CR Number:   536059
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Linux Red Hat
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.2 22 Sep 2009 Added to user documentation
Description
System Administration Guide for IQ 12.7.

chapter 10: Transactions and Versioning

How transaction information aids recovery

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



CR:536672
CR Number:   536672
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Windows 2000
Original Version:   12.7 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 future 29 Jan 2009 Not a Bug
23 Nov 2009 Not a Bug
Description
The error code defined as "ERROR" by ODBC State exists in IQ error message guide.

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

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



CR:537056
CR Number:   537056
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   AIX
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 23 Jun 2009 Fixed
Description
There is no description in a manual about "-wait" option of stop_asiq.



CR:537079
CR Number:   537079
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Windows XP
Original Version:   12.7 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
When update/delete a local table, if it join with remote data, an error will occur. This is the specification of IQ.



CR:537395
CR Number:   537395
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   12.7 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e06 3667 18 Jul 2008 Fixed
12.7 e06 14 Oct 2008 Fixed
12.7 e06 14 Oct 2008 Fixed
Description
The following would cause the server to fail.



create table t1 ( c1 date, c2 time );

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

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



An error is now reported. "Invalid type for field reference."
Workaround Description
 *** Friday, July 18, 2008 12:24:15 PM *** aldrich ***

The following will cause the server to fail:



create table t1 ( c1 date, c2 time );

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

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



c1.foo() is an invalid field reference. It doesn't make sense to use invalid field references, but listing it in the non-first position will cause a proper error to be reported.



CR:538102
CR Number:   538102
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e05.x 12 Aug 2008 Fixed
12.7 e05.x 15 Oct 2008 Fixed
12.7 e06 12 Aug 2008 Fixed
12.7 e06 16 Oct 2008 Fixed
15.0 15 Aug 2008 Fixed
15.0 05 Mar 2009 Fixed
Description
You cannot create a raw device of more than 4 tb

on Linux.



CR:538252
CR Number:   538252
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e06 14 Nov 2008 Fixed
15.0 Beta2 17 Nov 2008 Fixed
12.7 e06 21 Jan 2009 Fixed
24 Feb 2009 Fixed
Description
In IQ version 12.7GA and later, html plan of the query executed by the "event" and the "stored procedure" does not contain the correct "query-text". For events, the query text is "Statement text unavailable" inspite of the actual query while in case of stored procedure, the query text is "Call proc_name(...)" instead of the actual queries present in the procedure.



CR:539090
CR Number:   539090
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.7 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e06 3684 07 Nov 2008 Fixed
12.7 e06 11 Dec 2008 Fixed
Description
Using isql, running in an IQ server (e.g., IQ 12.7 ESD #4) a stored procedure that was

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

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



Msg 13732, Level 16, State 0:

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



This has been fixed.
Workaround Description
 use a customized login procedure which sets quoted identifier to ON ?? but that might mess up other OC TDS connections ??



CR:539237
CR Number:   539237
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Sep 2008 Duplicate
Description
Simple SELLECT using TOP and ORDER BY on table with 1 billion rows takes more that 13 minutes in IQ yet less than 10 seconds in DB2.



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





need a possible Feature Request to have ORDER BY optimization for TOP/FIRST put in
Workaround Description
 select top 10 prd_id into #t from iwsdwh.f_acct_rst order by prd_id;

select top 10 act_rst_id from iwsdwh.f_acct_rst where prd_id in (select

prd_id from #t ) order by prd_id;



CR:539428
CR Number:   539428
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Unknown
Original Version:   12.7 future
Fixed Version Build Resolution Date Closure Code (If Appropriate)
06 Aug 2009 Insufficient priority to fix
Description
BNP, an Alliance customer, asks if it could be possible to enhance an error message.



Here is the scenario:



create table mytab(att int) in SYSTEM;

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



Could not execute statement

Feature 'location' not implemented

SQLCODE=-134



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



Could we get a message like

Feature 'location' not implemented in SYSTEM dbspace

instead?



CR:539484
CR Number:   539484
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows NT
Original Version:   12.6 e09.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e11 29 Aug 2008 Consult Complete
24 Oct 2008 Insufficient priority to fix
15.1 17 Mar 2009 DEFER
15.1 25 May 2009 Added to user documentation
Description
On Windows 32-bit and 64-bit, starting in IQ 12.6 ESD #8, after a remote ASE server is created using either class 'aseodbc' or class 'asejdbc' and before executing a SQL statement that contains a string with double quotes against the remote server using the FORWARD TO statement, you need to do one of the following to make the SQL statement work:



1. Change the double quotes to single quotes

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

FORWARD TO <remote server name> {

set quoted_identifier off

<SQL statement>

}

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

FORWARD TO <remote server name> { set quoted_identifier off }
Target Version
 12.6 e11
Workaround Description
 two possibilities - set Quoted_identifier off into Forward command or use single quotes is Forward command :



1. explicitly for use of Quoted_identifier off



i.e. :

forward to ambev {set quoted_identifier off if exists (select 1 from pubs2..sysobjects where name="tABCDEFGHIJKLMNOPQRSTUVXZABCDE" and type="U") drop table pubs2..tABCDEFGHIJKLMNOPQRSTUVXZABCDE}



2. use of single quotes instead of double quotes

i.e. :

forward to ambev { if exists (select 1 from pubs2..sysobjects where name='tABCDEFGHIJKLMNOPQRSTUVXZABCDE' and type='U') drop table pubs2..tABCDEFGHIJKLMNOPQRSTUVXZABCDE}



CR:539566
CR Number:   539566
Product Name:   Sybase IQ ETL
Product Component:   ETL Connectivity
Status:   Closed
OS:   Windows XP
Original Version:   4.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
06 Oct 2008 Fixed
06 Oct 2008 Fixed
Description
Problem:

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



Resolution:

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



CR:539604
CR Number:   539604
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)
14 Aug 2008 Consult Complete
12.7 e06 10 Oct 2008 Fixed
Description
A statement with PARTITION BY 2 columns may be incorrectly evaluated when the WHERE clause has an equality predicate.

For example:

select MarketDateTime,LastPrice,count(*)

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

unbounded preceding and current row) PriceRank from test

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

and NumericalInstrCode=1;
Workaround Description
 The fix for this problem is to use



dml_options5 = 524288



CR:540233
CR Number:   540233
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.7 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 Jun 2009 Duplicate
Description
The IQ server may crash or hang when the main or temporary cache is severely stressed

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

fixed.



CR:540430
CR Number:   540430
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   12.7 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e06 3684 07 Nov 2008 Fixed
12.7 e06 15 Dec 2008 Fixed
Description
If a conversion error occurred while constructing the string to be executed by EXECUTE IMMEDIATE within a procedure, the error might not be reported, and the server may fail.



CR:540641
CR Number:   540641
Product Name:   Sybase IQ ETL
Product Component:   GUI
Status:   Closed
OS:   Windows XP
Original Version:   4.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
06 Oct 2008 Fixed
Description
Problem:

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



Resolution:

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



CR:541590
CR Number:   541590
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows XP
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e06 24 Oct 2008 Fixed
15.0 Beta1 Refresh 24 Oct 2008 Fixed
15.1 e01 27 Apr 2009 Fixed
12.7 e06 02 Dec 2008 Fixed
Description
The following SQL will cause the server to report a

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



create table T1 (C1 varchar(10));

insert into T1 values ('Tabla 1');

create table T2 (C1 varchar(10));

insert into T2 values ('Tabla 2');

commit;



select top 10 * from (

select 1 as M from T1 union all

select 2 as M from T2

) as R order by M asc;
Workaround Description
 *** Tuesday, October 14, 2008 3:42:29 PM *** aldrich ***

A workaround for the query given in the Repro is



set option dml_options5 = 65536;



CR:541875
CR Number:   541875
Product Name:   Sybase IQ ETL
Product Component:   Docs
Status:   Closed
OS:   all
Original Version:   4.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
22 Sep 2010 Insufficient info provided
Description
Refer to the Release Bulletin for fixed bugs and more information on this release.



CR:541879
CR Number:   541879
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e06 3684 18 Nov 2008 Fixed
12.7 e06 14 Jul 2009 Fixed
Description
In rare cases, executing an invalid ALTER PROCEDURE statement, e.g., ALTER PROCEDURE WITH RECOMPILE ..., could cause a server failure or an incorrect error message.



CR:542300
CR Number:   542300
Product Name:   Sybase IQ ETL
Product Component:   ETL Connectivity
Status:   Closed
OS:   all
Original Version:   4.5.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
08 Sep 2008 Fixed
Description
Problem:

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



Resolution:

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



CR:542502
CR Number:   542502
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e06 17 Sep 2008 Fixed
12.7 e06 16 Oct 2008 Fixed
Description
In IQ 12.7 ESDs #4 and #5, an UPDATE or DELETE statement against an IQ table with rows affected returns SQLCODE of 100 and SQLSTATE of 02000 as opposed to the correct values of 0 and 00000 respectively.
Workaround Description
 Add SQLSTATE=02000 or SQLCODE=100 to the check if the DELETE statment was successfull

DELETE FROM AAA where dt>'2008-01-01'

IF SQLCODE<>0 THEN.... need to be changed to

IF SQLCODE NOT IN (0,100)

OR

IF SQLSTATE <> '00000'.. need to be changed to

IF SQLSTATE NOT IN ('00000',02000').



CR:543249
CR Number:   543249
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e11 22 Sep 2008 Fixed
12.7 e06 24 Oct 2008 Fixed
12.6 e11 03 Oct 2008 Fixed
15.0 Beta2 22 Oct 2008 Fixed
22 Oct 2008 Fixed
12.7 e06 26 Nov 2008 Fixed
Description
When using the Sybase IQ BACKUP command, users can parallelize the operation to multiple devices by specifying multiple TO clauses. Backups created using a backup statement with more than 36 TO clauses may create backup archives that are unreliable. While these archives appear to be correctly written, they may contain invalid headers and cannot be restored. Sybase strongly recommends that customers who have created backup archives to more than 36 devices test the archives by restoring them to a test area. Do not attempt to restore the archive to a production database unless this test has completed successfully. If the test restore fails, create new backup archives using 36 or fewer TO clauses. The Sybase IQ Backup should limit the BACKUP statement to a maximum of 36 TO clauses.



CR:543834
CR Number:   543834
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e07 01 May 2009 Fixed
12.7 e06.x 01 May 2009 Fixed
12.7 e05.x 01 May 2009 Fixed
Description
In the 12.7 System Administration Guide, Chapter 5, "Dbspace Management Example," the line "sp_iqrelocate 'empdb'" should read "sp_iqrelocate 'database'."



CR:543864
CR Number:   543864
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e07 03 Mar 2009 Fixed
16 Mar 2009 Fixed
12.7 e06.x 01 May 2009 Fixed
Description
On occasion the reader can become unresponsive when multiple create procedure statements are run in batch on the writer. There is a dead lock between dbremote thread and tlv replay thread. This problem is fixed by restricting dbremote thread to not lock tlvstore.



CR:544567
CR Number:   544567
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Unknown
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.2 02 Sep 2009 Presently Not Targeted For Any Future Release Of This Product
Description
The example of connection currently written to 26 pages of Installation and Configuration Guide Sybase IQ 12.7 for WINDOWS is a mistake. The correct example of connection is "<hostname>: <portnumber>" and "fiona_asiqdemo:1870."



CR:545179
CR Number:   545179
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Unknown
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.2 21 Jul 2009 Presently Not Targeted For Any Future Release Of This Product
Description
IQ 12.7 documentation inconsistency



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



CR:545216
CR Number:   545216
Product Name:   Sybase IQ ETL
Product Component:   pEngine
Status:   Closed
OS:   all
Original Version:   4.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
06 Oct 2008 Fixed
Description
Problem:

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



Resolution:

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



CR:545613
CR Number:   545613
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows XP
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e06 08 Oct 2008 Fixed
15.0 Beta1 Refresh 09 Oct 2008 Fixed
12.7 e06 17 Nov 2008 Fixed
15.0 Beta1 Refresh 10 Oct 2008 Fixed
Description
The following sql will cause the server to fail:

select * into t from sp_iqstatus();

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



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

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



CR:545673
CR Number:   545673
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e06 04 Dec 2008 Fixed
15.0 Beta2 Refresh 03 Mar 2009 Fixed
12.7 e06 11 Feb 2009 Fixed
Description
The optimizer was performing incorrectly while executing constant virtual Column Substitutions. As a result of the problem, the ordering between join node and order by node is out of sync which is causing the "Input to merge join X from child Y not ordered as required" error.



CR:545763
CR Number:   545763
Product Name:   IQ
Product Component:   Install
Status:   Closed
OS:   Linux Red Hat
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Oct 2008 Consult Complete
Description
EBF installation steps of Linux x86 and Linux x86-64 differ.



CR:546338
CR Number:   546338
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
03 Nov 2008 Not a Bug
12.7 e06 11 Nov 2008 Fixed
15.0 Beta2 11 Nov 2008 Fixed
12.7 e06 10 Feb 2009 Fixed
Description
The server fails running sp_iqcheckdb 'verify database' for a database where there is a mismatch between the number of rows for an FP index and the number or rows for an LF index.



CR:546789
CR Number:   546789
Product Name:   IQ
Product Component:   Utility
Status:   Open
OS:   Windows XP
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Sybase Central cannot show Database Propery of 1024000MB of IQ Store. And an issue will be reproduced also at the time of 1024000MB of IQ Store, and its multiple.
Workaround Description
 Please use sp_iqdbspaceinfo in DBISQL.



CR:546817
CR Number:   546817
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e06 17 Dec 2008 Fixed
12.7 e06 28 Jan 2009 Fixed
12.7 e05.x 09 Jul 2010 Fixed
12.7 e05.x 29 Jan 2009 Fixed
Description
If an application uses a badly formed update statement of the form "update test X set X..a = 2" where test is a proxy table, then there is a chance the server may fail.
Workaround Description
 As an interim possible workaround, I've suggested the user to increase the main and temp cache.



CR:546821
CR Number:   546821
Product Name:   Sybase IQ ETL
Product Component:   pEngine
Status:   Closed
OS:   Solaris
Original Version:   4.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Frodo 24 Dec 2008 Not a Bug
Description
Problem:

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



Workaround:

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



CR:547135
CR Number:   547135
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 24 Mar 2009 Fixed
Description
sample of "Encrypted Columns in Sybase IQ" is wrong. INSERT INTO t (cipherCol) VALUES ( AES_ENCRYPT (CAST 1 AS UNSIGNED INTEGER), 'key' )) ---> INSERT INTO t (cipherCol) VALUES ( AES_ENCRYPT (CAST (1 AS UNSIGNED INTEGER), 'key' ))



CR:547532
CR Number:   547532
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Solaris
Original Version:   15.0 Beta1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
22 May 2009 Fixed
09 Jun 2009 Fixed
Description
While creating Simplex node using Sybase Central, only CreateDB.sql is created in DB directory. To avoid confusions, on Create database wizard changed the label to "Create sql script" from "create Admin shell script".



CR:547636
CR Number:   547636
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
08 Jul 2010 Consult Complete
Description
DELIMITED and ROW DELIMITED are required for LOAD TABLE ENCRYPTED.



CR:547690
CR Number:   547690
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2003
Original Version:   15.0 Beta1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Sep 2009 Fixed
22 Apr 2009 Fixed
Description
Support column default special value, LAST USER and TIMESTAMP, is in 1270.

It is missing from Atomic GA.



CR:547747
CR Number:   547747
Product Name:   Sybase IQ ETL
Product Component:   GUI
Status:   Closed
OS:   all
Original Version:   4.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Nov 2008 Fixed
Description
Problem:

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



Workaround:

When the OPEN dialogue opens, cancel it, click on the auto-update button in the component, then return to the OPEN dialogue, and open the file.
Workaround Description
 There is a work around. When the OPEN dialogue opens, cancel it, click on the auto-update button in the component, then return to the OPEN dialogue, and the file opens.



CR:548227
CR Number:   548227
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Unknown
Original Version:   12.7 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e06 25 Nov 2008 Fixed
12.7 e06 14 Jul 2009 Fixed
Description
Some queries involving a full outer join and a left or a right join may return incorrect results in IQ 12.7 ESDs #4 and #5.



CR:548329
CR Number:   548329
Product Name:   Sybase IQ ETL
Product Component:   other
Status:   Closed
OS:   all
Original Version:   4.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
04 Nov 2008 Fixed
Description
Sybase IQ Wide Table Support and Limitations in ETL 4.5 EBF 1



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



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



Observations and Recommendations



Repository:



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



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



InsertLocation:



- Insert Location is supported using a 3000 column table.



Migration Wizard:



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



Load Table:



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

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



User Interface Experience



General Limitations:



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



Insert Location Component:



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



Load Table Component:



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



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



Workaround:

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



Migration Wizard:



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



Query Designer:



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



CR:548363
CR Number:   548363
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Unknown
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 24 Apr 2009 Fixed
Description
"Encrypted Columns in Sybase IQ" says the default value of ASE_BINARY_DISPLAY option is ON.However, the default value of IQ12.7 is OFF.



CR:548884
CR Number:   548884
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Solaris
Original Version:   15.0 Beta1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 e01 23 Mar 2009 Fixed
Description
In SCJ: Triggers are not supported for IQ tables hence this option is disabled for IQTables.Only SA tables will be listed as a choice to create triggers.



CR:548898
CR Number:   548898
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.0 22 Dec 2008 Added to user documentation
Description
Add "ASA Error -267: COMMIT/ROLLBACK not allowed within atomic operation" to IQ error messages.



CR:549633
CR Number:   549633
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Nov 2008 Presently Not Targeted For Any Future Release Of This Product
Description
Server crash during dbspace resizing operation on raw partition.



CR:549802
CR Number:   549802
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e06 31 Mar 2009 Fixed
12.7 e06 17 Dec 2008 Fixed
12.7 e06 28 Jan 2009 Fixed
Description
The server sometimes failed, when an ORDER BY clause in

certain queries contained a reference to a null column.



CR:550298
CR Number:   550298
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e06 11 Feb 2009 Fixed
11 Feb 2009 Fixed
12.7 e06 12 Mar 2009 Failed
Description
In rare instance, when a user cancels an operation that

involves a local temporary table, the server may fail.



CR:550477
CR Number:   550477
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e06 10 Dec 2008 Fixed
12.7 e06 08 Feb 2009 Fixed
17 Dec 2008 Fixed
17 Dec 2008 Fixed
12.7 e05.x 19 Apr 2009 Fixed
Description
If an Open Client or jConnect application executed a query that involved the use of host variables within a batch, then the server would have crashed, rather than giving the "Host variables may not be used within a batch" error message. This problem has now been fixed.



CR:552413
CR Number:   552413
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.6 e10
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e06 29 Jan 2009 Fixed
12.7 e06 11 Feb 2009 Fixed
12.6 e11 29 Apr 2009 Fixed
Description
If an application executed a remote query that involved a

UDF, and the UDF call passed in column references as

parameters, and the server ran the query in partial passthru

mode, then there was a chance of server failure.



CR:553049
CR Number:   553049
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 e07 03 Mar 2009 Fixed
12.7 e07 30 Mar 2009 Fixed
12.7 e07 08 Jul 2009 Fixed
Description
The IQ_MPX_VERSIONLIST table of the query server to be promoted to become the writer may

not include an entry for one of the other query servers, resulting in the

"IQ_MPX_VERSIONLIST is missing row" error when sp_iqmpxvalidate is run after the writer

server replacement steps are completed. This has been fixed. In the 12.7 System Administration Guide, step 2 "Replacing a write server that has no SYSTEM dbspace and/or

transaction log file" on page 668 should read:

2 Choose the query server with the largest value in "DBA".IQ_MPX_STATUS.catalog_version

(or any one of those query servers, if the largest value exists in more than one query server) to be the new write server.



CR:553166
CR Number:   553166
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Unknown
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
27 Aug 2009 Added to user documentation
Description
Description does not exist in a manual about the output value of sys_iqsysmon.



CR:553685
CR Number:   553685
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e07 23 Mar 2009 Fixed
15.0 21 Jan 2009 Fixed
10 Sep 2009 Fixed
Description
Result exceeded when query with 15 left outer joins and 6 equijoins is executed. This results into failure of the server. The datatype of the resultant variable is changed from 4 bytes to 8 bytes.



CR:554163
CR Number:   554163
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e07 17 Mar 2009 Fixed
15.0 20 Jan 2009 Fixed
Description
A stuff function cannot replace a multibyte strings correctly. A stuff function attaches the null character to the end of a strings. This problem is now resolved and STUFF returns correct results regardless the character set used.



CR:554706
CR Number:   554706
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.6 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e07 05 Feb 2009 Fixed
03 Jun 2009 Not reproducible with latest version of the product available as of Resolution Date
12.6 e11 19 Apr 2009 Fixed
Description
On certain processors other than x86 and x86_64 (64 bit

HP-UX for example), the server failed in

extremely rare conditions, when using a connection number to

get connection information. Examples of getting this type

of connection information include getting a connection

property for another user, or calling sa_conn_info.



CR:554902
CR Number:   554902
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Solaris
Original Version:   15.0 Beta2 Refresh
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 e01 19 Mar 2009 Fixed
Description
In SCJ : The "New Dbspace" and "New DBSpace file" creation menus are disabled (greyed out) on secondary reader nodes.



CR:555329
CR Number:   555329
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Solaris
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
19 Apr 2009 Not a Bug
Description
restore command does not trim off the blank char of end of an extension.



CR:555571
CR Number:   555571
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 e07 27 Apr 2009 Fixed
15 Jun 2009 Fixed
Description
If an application defined a view containing a remote query,

and if the remote query contained a GROUP BY ... HAVING

clause, then using the view in a query caused a server

failure.



CR:555949
CR Number:   555949
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Unknown
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e07 02 Feb 2009 Fixed
Description
If a connection string containing the "verify=no" TCP

parameter was passed to dbisql and the -jconnect switch was

used, the client failed.



CR:556113
CR Number:   556113
Product Name:   IQ
Product Component:   Install
Status:   Closed
OS:   Unknown
Original Version:   15.0 Beta2 Refresh
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.2 26 12 Mar 2010 Fixed
15.1 e03 26 12 Mar 2010 Fixed
Description
The JRE for windows has been updated from version 1.6.0_10 to version 1.6.0_16
Workaround Description
 *** Friday, January 16, 2009 4:53:07 PM *** rsinghai ***

We have two workarounds for it:



1. Disabling the Vista AERO theme and selecting Windows clasic color scheme:

a. Right click on an empty part of the desktop.

b. Select "Personalize".

c. Click "Theme".

d. If currently using Aero/Vista, then select "Windows Classic" in the combo box and then click OK.

e. Click "Window Color and Appearance".

f. If currently using Aero/Vista, then click "Open classic appearance properties" link at bottom.

g. In the Color scheme list, click "Windows Classic" and then click OK.

h. Restart your broken Java application (Sybase Central or DBISQL Java).



2. Reverting back to JRE ver 1.6.0_3, where this regression was not present.



CR:556474
CR Number:   556474
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Unknown
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e06 28 Apr 2009 Fixed
12.7 e07 22 Jun 2009 Fixed
Description
Fixed as part of 12.7 esd 6. With this fix users with spaces can be dropped.
Workaround Description
 The workaround is to to put the single quotes around the login and run the correct syntax in DBISQL to drop the user.

Ex: sp_iqdroplogin 'John Smith'



CR:556489
CR Number:   556489
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.7 e05.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
03 Jun 2009 Workaround
Description
A command line longer than the catalog page size can cause the "Syntax error near 'parse

stack overflow' ..." error. The workaround is to use a larger catalog page size when

creating a new database, and is to split long statements into shorter ones for existing

databases.



CR:557256
CR Number:   557256
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Windows XP
Original Version:   15.0 Beta2 Refresh
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 e01 30 Mar 2009 Fixed
Description
In SCJ: Now the zooming scale can be persisted and restored in topological view.



CR:557378
CR Number:   557378
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Windows XP
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 e01 17 Mar 2009 Fixed
Description
In SCJ : For Recycled MPX node, the old MPX information like MPX name is retrieved from MPX Coordinator node.



CR:557477
CR Number:   557477
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e07 12 Feb 2009 Fixed
Description
If an application makes use of one of the remote data access JDBC classes, and if the application then disconnects abnormally, then the connection to the remote server is never closed. The problem does not exist if the application uses one of the remote data access ODBC classes instead. This problem has now been fixed.



CR:557571
CR Number:   557571
Product Name:   IQ
Product Component:   Install
Status:   Closed
OS:   Solaris
Original Version:   15.0 Beta2 Refresh
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 e01 20 Mar 2009 Fixed
Description
Improved logging information in log.txt to help debugging problems.



CR:557787
CR Number:   557787
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e07 18 Mar 2009 Fixed
12.7 e05.x 01 Apr 2009 Fixed
12.7 e07 21 May 2009 Fixed
Description
Query - In some cases, when issuing a rollback with open cursors, cursor cleanup was not properly done which was causing a server failure. This has been fixed.



CR:558267
CR Number:   558267
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   15.0 Beta2 Refresh
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 e01 17 Apr 2009 Fixed
15.1 23 Apr 2009 Fixed
Description
If a reader node attempts to modify any object in main store, earlier release threw following error:

A query server may not modify objects in the main store.

with following error codes:

SQLSTATE: QXA19

SQLCODE: -1010019

Sybase Error: 21113



The error message has been changed to following:

Cannot modify object <object name> on dbspace <dbspace name>. A query server may not modify objects in the main IQ store.

with following error codes:

SQLSTATE: QXA31

SQLCODE: -1010031

Sybase Error: 21131



CR:558429
CR Number:   558429
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   AIX
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
23 Apr 2009 Fixed
03 Jun 2009 Fixed
Description
Back-end query sent to the server has been corrected in Sybase Central.



CR:558448
CR Number:   558448
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Linux Red Hat
Original Version:   12.7 e07
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Create a new function at IQ like rowtype function at Oracle.



CR:559090
CR Number:   559090
Product Name:   IQ
Product Component:   SA Component
Status:   Open
OS:   Windows XP
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
ADORecordSet.MoveFirst does not obtain the correct result.



CR:559255
CR Number:   559255
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Windows XP
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e07 26 Jun 2009 Fixed
Description
When a NUMERIC or DECIMAL column with precision greater than 47 is fetched using OLE DB, ODBC, or JDBC, a memory buffer overrun will occur. This will result in a corrupted heap. The client application may then terminate unexpectedly because of the corrupted heap.



This problem has been fixed.



CR:559311
CR Number:   559311
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.6 e10
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e07 10 May 2009 Fixed
11 Jun 2009 Fixed
Description
When trying to send message greater than 2k size to client, server was not responding when charset conversion is needed between server and client. This problem is fixed in this release.



CR:559518
CR Number:   559518
Product Name:   IQ
Product Component:   Install
Status:   Closed
OS:   AIX
Original Version:   15.0 Beta2 Refresh
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 e01 23 Mar 2009 Fixed
Description
A jvm not found message should no longer be displayed during an installation. If the user encounters this message the user should pass -is:jvmtimer 30 to the setup launcher.

Example. ./setupHP-UXi64 -is:jvmtimer 30

If the problem still persists try increasing the value from 30 to something larger.



CR:560032
CR Number:   560032
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.1 e01 24 Mar 2009 Fixed
15.1 28 Apr 2009 Fixed
Description
The stored procedures sp_iqbackupsummary and sp_iqrestoreaction now accepts either a timestamp or backup id.

Since the store procedure definition has changed, user will need to run ALTER DATABASE UPGRADE.



CR:560074
CR Number:   560074
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Windows XP
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 e01 23 Mar 2009 Fixed
Description
From SCJ: In an existing table, a new column can be added and made the partition key before saving.



CR:560295
CR Number:   560295
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Windows XP
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 e01 19 Mar 2009 Fixed
Description
In SCJ: Appropriate property dialogs for Primary, Foreign and Unique Constraints. This enhances the information in the Primary and Foreign key properties dialogs.



CR:560392
CR Number:   560392
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   15.0 Beta2 Refresh
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10 Jan 2011 Fixed
15.2 e01.x 16 Nov 2010 Fixed
10 Jan 2011 Fixed
Description
The third argument to the LOCATE() function cannot be

CAST larger than BIGINT.



CR:560760
CR Number:   560760
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e07 16 Jun 2009 Fixed
15.1 e01 10 Jul 2009 Fixed
Description
The optimizer might incorrectly decide on optimization

by inversion for a query with a range predicate.



CR:561320
CR Number:   561320
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.0 e01 16 Mar 2009 Fixed
15.1 16 Mar 2009 Fixed
12.7 e07 01 Apr 2009 Fixed
12.7 e05.x 18 Jun 2009 Fixed
Description
Engine may become unresponsive when tearing down a sort used in a query or other DML operations.



CR:561364
CR Number:   561364
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.0 e01 05 Mar 2009 Fixed
12.7 e07 05 Mar 2009 Fixed
Description
LOAD TABLE may fail to load any rows during a binary load

to a table with default values.



Here is a sample to illustrate the failure.



create table t1( c1 int, c2 date default current date,

c3 time default current time );

load table t1( c1 ascii(4), filler(1) )

from 'data.inp'

format binary

quotes off escapes off;



select count(*) from t1;



NOTE: datafile 'data.inp' must contain the following



1234

1234



CR:561682
CR Number:   561682
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 e01 14 Apr 2009 Fixed
12.7 e07 10 Jun 2009 Fixed
Description
b-tree corruption could result in rare circumstances causing index corruption and checkdb "Missing Key" errors.



CR:561788
CR Number:   561788
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Linux Red Hat
Original Version:   12.7 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
A simple query returns incorrect result (empty column output).



CR:561791
CR Number:   561791
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e07 14 May 2009 Fixed
Description
Complex SELECT CASE query causes server failure when catalog cache memory(-c) is not sufficient to execute the query. This problem has been fixed. Now the server will return error saying "Query Complexity exceeds server limit" whenever it runs out of catalog cache memory while executing SELECT CASE query, '-c' value need to be increased in that case.



CR:562229
CR Number:   562229
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows XP
Original Version:   15.0 Beta2 Refresh
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 e01 09 Mar 2009 Fixed
Description
If you add a file to IQ_SYSTEM_TEMP and that file either happens to have a name starting with n or is in a directory that has a name that starts with n, no error is reported but the secondary server fails to open the file and cannot use it.



The file gets created correctly but the TLV log has an incorrect entry. On replay the replay fails silently and the file is never opened
Target Version
 



CR:562255
CR Number:   562255
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Unknown
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 e01 23 Mar 2009 Fixed
Description
In SCJ : In "Convert to MPX wizard", "Add Server wizard", and "Create database wizard", the agent field is blank. It has been requested that this is inconvenient to users. If the agent port is already known, the field should be initialized with that port number. Otherwise, the field should be initialized with the default agent port (i.e. 1099).



CR:562308
CR Number:   562308
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Windows XP
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 e01 18 Mar 2009 Fixed
15.0 e01 05 Mar 2009 Fixed
Description
In SCJ : The Upgrade (File | Upgrade when a database has been selected OR select a Database and right click followed by Upgrade) should be enabled for IQ 15.0 e01. This menu option was grayed out for 15.0.



CR:562371
CR Number:   562371
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 e01 26 Mar 2009 Fixed
Description
For a scenario where 'alter dbspace ... readonly' command is executed on coordinator and followed by 'readonly selective restore' operation immediately, then a secondary node may crash in earlier release.

With this release, in this scenario, the restore operation may either succeed or give following error:

Cannot execute 'restore <dbspace or dbfile name>' since previous alter command is not yet propagated through the multiplex. Try again.

SQLSTATE: QSA66

SQLCODE: -1009066

Sybase Error: 20087



CR:562403
CR Number:   562403
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   12.7 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e07 17 May 2009 Fixed
12.7 e07 11 Jun 2009 Fixed
Description
When the process sending DDLs to the reader was terminated

with a user interrupt, the reader became unresponsive due

to a deadlock.



CR:562654
CR Number:   562654
Product Name:   IQ
Product Component:   Utility
Status:   Closed
OS:   HP-UX
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 e01 30 Mar 2009 Fixed
15.1 30 Mar 2009 Fixed
12.7 e07 30 Mar 2009 Fixed
Description
The scripts start_asiq/start_iq now set by default on the HP-UX O/S the following environmental variables to help reduce memory fragmentation: _M_ARENA_OPTS=1:4096 & _M_SBA_OPTS=65536:50:256



CR:562705
CR Number:   562705
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.0 e01 12 Mar 2009 Fixed
Description
When running iqunload if a value for ms_size was specified and was smaller than the required size the verification step for the iqunload would fail. The iqunload tool will now detect that the user specified size was overridden and verification will succeed.



CR:563004
CR Number:   563004
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.1 e01 24 Mar 2009 Fixed
15.0 10 Mar 2009 Added to user documentation
12.7 e09 28 Sep 2009 Fixed
21 Sep 2009 Duplicate
Description
If the first IQ_SYSTEM_MAIN or first IQ_SYSTEM_TEMP file was without file extension, instead of restoring to those files, restore tried to create (or write into if already existing) files with default extension (.iq or .iqtmp). However, the catalog remained unchanged. Post restore, the database tried to open the files without extension, thus referring to stale content.

The problem has been fixed.



CR:563338
CR Number:   563338
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e07 14 May 2009 Fixed
15.1 27 Mar 2009 Added to user documentation
15.1 e01 15 Jun 2009 Fixed
15.2 22 Jan 2010 Fixed
Description
The server may assert and fail in s_ohcqry.cxx if the option HG_Search_Range is set too high.



CR:563435
CR Number:   563435
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Windows XP
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
19 Jan 2015 Fixed
Description
A PHP module is not attached to IQ. However, it is written to the manual that it is attached.





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

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