提供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:327958
CR Number:   327958
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.5 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e04 15 Sep 2003 Fixed
Description
Java memory exhaustion could cause a java (TDS) client to get stuck in CANCEL, causing an unresponsive server. TDS connections stuck in CANCEL more than 30 seconds are now dropped from the server.



CR:329013
CR Number:   329013
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e04 22 Sep 2003 Fixed
Description
Under rare circumstances, a deadlock could occur when active connections exceeded iqgovern and a cancel or drop connection was in progress.



CR:329097
CR Number:   329097
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e04 17 Sep 2003 Fixed
Description
A UNION ALL VIEW query returned a non fatal exception from dfe_PartitionedColumn.cxx (line 489) if a selected column was not type CHAR or VARCHAR and lacked a LF, HG or FP index. Duplicate of CR 313832.



CR:329263
CR Number:   329263
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.0.2 (GA)
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 13 Feb 2004 Fixed
Description
This is a feature request that the first parameter to the IQ DATEFORMAT function should accept a string as it would in ASA.

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

While in ASA and ASA documentation, there is no such limit.
Workaround Description
 Convert the 1st parameter in dateformat() to one of the supported proper data type (date, time, or timestamp)

e.g.

1> select count(*)

2> from fact

3> where date_hour_int = convert(integer,dateformat(cast ('2003-06-01' as date),'YYYYMMDD00'))

4> go



CR:329275
CR Number:   329275
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e05 28 Oct 2003 Fixed
Description
Under certain conditions, s_bufman_exception or free list verify errors could occur. Running sp_iqcheckdb could report duplicate block errors. The problem is corrected. [Duplicate of CR 327733]



CR:329306
CR Number:   329306
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 04 Mar 2004 Fixed
12.5 e08 22 Jan 2004 Fixed
Description
An issue existed in queries where the number of selected items is less than the number of columns produced from a derived table or a view. If split group by optimization is applied, these queries could be rejected with the "Unable to evaluate expression" error from dfo.cxx. If split group by optimization is disabled, these queries work correctly. CR 330657 and CR 333813 are duplicates.



CR:329963
CR Number:   329963
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   12.5 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e08 28 Jan 2004 Fixed
Description
Multiplex: if you follow the procedure in "Replacing write servers" in the Adaptive Server IQ Multiplex User's Guide to replace the write server with a query server, and use the name of an existing query server for the new write server, the procedure will fail. Although the documentation is clear on this point, the stored procedures should prevent use of an incorrect server name.



CR:330192
CR Number:   330192
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   12.4.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 02 Apr 2004 Fixed
Description
Setting to limit the place where files with Temp_Extract_Name1 can be put.



CR:330391
CR Number:   330391
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 05 Dec 2005 Fixed
15.0 09 Oct 2006 Fixed
Description
Infrequently, a multiplex server with many recovered transactions to checkpoint may run out of space during the recovery checkpoint. If you cannot connect and add a dbspace, restart the database in single node mode, which causes retained versions to be deallocated and the checkpoint to succeed.



CR:331014
CR Number:   331014
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e04 22 Sep 2003 Fixed
12.6 05 Mar 2004 Fixed
Description
Join queries that tried to insert data longer than the length of the field caused the server to fail at hos_dfe_SIN64_SIN16_NUMERIC_EQ on both HP and SUN systems.



CR:331015
CR Number:   331015
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 22 Jan 2004 Fixed
12.5 e08 14 Jan 2004 Fixed
Description
Under some circumstances for queries specifying an ORDER BY

with one or more descending direction indicators (DESC),

the query was rejected with an internal error because of

incorrect propogation of the ordering direction information

within the query optimizer.



CR:331141
CR Number:   331141
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.5 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e04 17 Sep 2003 Fixed
Description
Interrupting a DELETE command could cause a deadlock.



CR:331286
CR Number:   331286
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.4.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.4.3 e11 10 Nov 2003 Fixed
Description
Certain queries with all null columns in the select list may run slower than expected.



CR:331451
CR Number:   331451
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.4.3 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 12 Apr 2004 Fixed
Description
During defragmentation, indexes must be dropped and recreated. This leaves a production table without a critical index. Being able to copy an index, then drop and recreate the original, then drop the copy would eliminate this gap.



CR:331987
CR Number:   331987
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.4.3 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.4.3 e12 12 Oct 2003 Fixed
12.5 e08 11 Feb 2004 Fixed
Description
If a connection using TDS protocol failed, returning NULL from the CreateConnection function, the server failed at TDSPres::RequestLoginFinish().



CR:332003
CR Number:   332003
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 19 Feb 2004 Fixed
Description
The server may fail with error "Index is active. db_cati.cxx line 531." under the following circumstances:

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



CR:332004
CR Number:   332004
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e04 02 Dec 2003 Fixed
Description
The database option SignificantDigitsForDoubleEquality controls how many significant digits to the right of the decimal point in exponential notification are used in double equality testing. Allowed values range from 0 to 15. The default, 0, meands "use all digits."



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

1.23456789012345

1.23456789012389



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



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



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



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



CR:332044
CR Number:   332044
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   12.5 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 02 Dec 2003 Fixed
12.6 09 Aug 2004 Fixed
Description
Request the document cleanup in the next major release for consistent use of filename for srvlog, which is sometimes spelt as svrlog in the document.

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



CR:332162
CR Number:   332162
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e08 14 Jan 2004 Fixed
Description
The query SELECT SUM(m1), SUM(m1*0.08) FROM T1

was rejected at dfe_ArithmeticExpression::209

(ASA Error -1001006: Data exception -

data type conversion is not possible.)



This query failed for m1 of datatype INT

or NUMERIC on both Sun and NT.



CR:332851
CR Number:   332851
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   12.5 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 06 May 2004 Fixed
12.5 e06 14 Nov 2003 Fixed
Description
When a query server is deleted via Sybase Central, the SQL Remote process is inadvertently stopped on the writer server.



CR:332940
CR Number:   332940
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 05 Mar 2004 Fixed
12.5 e08 14 Jan 2004 Fixed
Description
If a user executed a LOAD command to load a table

that has a primary key and/or unique constraint and



- IGNORE CONSTRAINT UNIQUE was specified, AND

- one or more UNIQUE constraint violations occurred



then it was possible that the primary key and/or

unique constraint would have been incorrectly built.



The user would have noticed this either by a query

returning wrong results or sp_iqcheckdb reporting

that a HG index used to represent the primary key

or unique constraint was inconsistent and missing

various keys and row ids.



CR:332962
CR Number:   332962
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5-03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 03 Dec 2003 Fixed
12.5 e07 03 Dec 2003 Fixed
Description
While running sp_iqcheckdb to verify the database in either IQ 12.4.3 or IQ 12.5, if a bitmap verify problem was encountered, the line titled `Bitmap Verify Errors' from the sp_iqcheckdb output reported double the number of errors that it actually detected. For example, the following portion of sp_iqcheckdb indicated 2 bitmap problem, but there was actually only 1 bitmap problem:



Container Statistics

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

Database Objects Checked','485012'

B-Array Count','4643'

.

.

'Bitmap Count','468536'

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



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



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



and



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



CR:333314
CR Number:   333314
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e05 29 Sep 2003 Duplicate
Description
Using VARCHAR strings greater than 255 bytes in databases with multi-byte collations could return unexpected results. [Duplicate of 331462 and 330102]



CR:333865
CR Number:   333865
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e10 23 Apr 2004 Fixed
Description
The sp_iqcheckdb procedure verify mode could incorrectly report DTTM and TIME indexes as inconsistent when the indexes were actually correctly built.



CR:334016
CR Number:   334016
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.0.2 (GA)
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e05 28 Oct 2003 Fixed
Description
REPEAT string function used in databases with multi-byte collations could return unexpected results.



CR:334088
CR Number:   334088
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e08 06 Feb 2004 Fixed
Description
Under some circumstances a predicate of the form:

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

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

index to compute a precise selectivity estimate.
Workaround Description
 The alternate workaround to the one the customer found (reordering

the predicates), is to drop the HG index on their dt_datevt column

and to add an LF index instead. If they do that, the LF index

will be used for the selectivity estimation instead



CR:334262
CR Number:   334262
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.4.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.4.3 e12 12 Oct 2003 Fixed
12.5 e08 01 Jan 2004 Fixed
Description
An issue existed where queries that processed many rows against a non-correlated IN-subquery predicate and where very few rows passed the predicate could not be interrupted by CTRL-C.



CR:334761
CR Number:   334761
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.4.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e08 03 Feb 2004 Fixed
Description
Queries against view dbo.syscolumns could return

unexpected results depending on datatype due to

an incorrect condition check.
Workaround Description
 create a new view, changing the condition to check the value 113 instead of 108 .



> CREATE view dbo.psecolumns (id,

> number,

> colid,

> status,

>



CR:335108
CR Number:   335108
Product Name:   IQ
Product Component:   other
Status:   Open
OS:   AIX
Original Version:   12.5 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Added to user documentation
Description
Customer is moving their server via copying raw devices and need to move the .iqmsg file to a new filesystem. They would like to rename/relocate the .iqmsg file but has a very large database so RESTORE/RENAME is impractical.



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



CR:335845
CR Number:   335845
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 01 Dec 2004 Fixed
12.5 e08 17 Dec 2003 Fixed
Description
When the IQ buffer cache monitor was invoked with the

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

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



CR:336032
CR Number:   336032
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e07 04 Dec 2003 Fixed
Description
A new startup switch was added in order to specify the number of CPUs in the processor set available to Adaptive Server IQ. See "Setting number of CPUs" in "Special installation and migration instructions" in the Adaptive Server IQ Release Bulletin.



CR:336038
CR Number:   336038
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e08 04 Jan 2004 Fixed
Description
The threads for the automatic cache resize and a CREATE TABLE operation were each waiting for the other to complete, but each held a lock that the other needed released, causing a deadlock and an unresponsive server.
Workaround Description
 From IQ eng:



In terms of workarounds, the only thing that comes to mind

is to start the server with a much larger SA cache.



-- Neil Burkhard



CR:336198
CR Number:   336198
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Unknown
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e07 14 Nov 2003 Fixed
Description
After replacing a write server and then marking one of the query nodes as excluded, creating a temporary dbspace on the writer may fail.



CR:336200
CR Number:   336200
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Unknown
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 29 Nov 2004 Fixed
12.5 e07 18 Nov 2003 Fixed
Description
Creating a new database via Sybase Central fails if the create uses an existing IQ server and the IQ Agent process is not running on the supporting host machine. Creating a new database via an existing IQ server should not require the agent process.



CR:336205
CR Number:   336205
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   AIX
Original Version:   12.5 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e08 06 Jan 2004 Fixed
Description
Dynamic catalog cache resizing did not work on AIX 5.x, and

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

memory exhausted" reported in the IQ server log.



CR:336353
CR Number:   336353
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e08 22 Jan 2004 Fixed
12.6 14 Jan 2004 Fixed
Description
A syntax error in the table.column expression caused a SEGV error in a multibyte collation database. Correct syntax requires a single ".".



CR:336491
CR Number:   336491
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.4.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 21 Feb 2004 Fixed
Description
The non-ANSI support for BLANK PADDING OFF for the CREATE DATABASE statement has been removed from the product. The changes will not affect databases previously created with BLANK PADDING OFF.
Workaround Description
 The work-around is to use only CHAR datatype for columns used in the where and having clauses for blank padding off databases:



For varchar col 'mycol' in table 'T':

1) Create matching char column

Alter Table T Add mynewcol char(n);



2) Copy the con



CR:336657
CR Number:   336657
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 19 Feb 2004 Fixed
12.5 e08 22 Jan 2004 Fixed
Description
Using improper FILLER() syntax on a LOAD command

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

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

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



CR:336658
CR Number:   336658
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   12.5 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 10 May 2004 Fixed
Description
RI concurrency checking is done for insert/load, update, and delete even if the user sets DISABLE_RI_CHECK=ON.



CR:336659
CR Number:   336659
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e08 17 Dec 2003 Fixed
12.6 17 Feb 2004 Fixed
Description
The INSERT...LOCATION does not identify itself to ASE. During INSERT...LOCATION execution, running sp_who does not show the hostname from which the INSERT...LOCATION has connected. Also, the connecting program name does not appear in the sysprocesses row in the MASTER database.



CR:337548
CR Number:   337548
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 06 May 2004 Fixed
12.6 14 May 2004 Fixed
Description
Change the Load_Memory_MB upper limit from 500MB to 2GB (or 2000MB).



CR:337572
CR Number:   337572
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   12.5 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Jul 2005 Presently Not Targeted For Any Future Release Of This Product
Description
CREATE TABLE may take longer as the volume of catalog information

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



CR:337603
CR Number:   337603
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.4.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e08 01 Jan 2004 Fixed
Description
An issue existed where a case expression that returned a character datatype was rejected with a conversion error when different arms of the case expresion mixed values less than 255 bytes and values more than 255 bytes.



CR:338002
CR Number:   338002
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e08 30 Jan 2004 Fixed
Description
An IQ server may become unresponsive during CREATE DATABASE on a raw device if the path to the raw device is incorrect. This problem is more likely to happen on single-CPU systems.



CR:338288
CR Number:   338288
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 05 Mar 2004 Fixed
Description
The sql statement "ALTER TABLE tablename REPLICATE ON" causes the server to fail.



CR:338423
CR Number:   338423
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e08 14 Jan 2004 Fixed
12.6 23 Jan 2004 Fixed
Description
Sybase IQ has a one terabyte file size limit. The limit has been removed.



CR:338827
CR Number:   338827
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 04 Mar 2004 Fixed
12.5 e08 22 Jan 2004 Fixed
Description
Under some circumstances involving moderate numbers of active users

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

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

then was optimal for a server that heavily loaded.



CR:339149
CR Number:   339149
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Unknown
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e07 02 Dec 2003 Fixed
Description
The system tables IQ_MPX_SYNC and IQ_TLV_LOG are incorrectly listed in the section "System tables and views" in Chapter 1, Adaptive Server IQ Administration and Performance Guide. These tables have been removed from Adaptive Server IQ.



CR:339441
CR Number:   339441
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   HP-UX
Original Version:   12.4.3 e12
Fixed Version Build Resolution Date Closure Code (If Appropriate)
02 Dec 2003 Fixed
Description
IQ 12.4.3 on HP-UX will generate an error on the first statement send to IQ via Open Client:

Msg 102, Level 15, State 0:

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

All subsequent statement will go fine
Workaround Description
 1 - Remove -ct switch from server startline.



2- In combination with 1:

Change the entry in the locales.dat file that the third party OC application

is using in the HP machine:



from :

[hp ux]

...

locale = default, us_english, roma



CR:339752
CR Number:   339752
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.4.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e08 22 Jan 2004 Fixed
12.6 25 Feb 2004 Fixed
Description
Statements involving a CASE, IF, NULLIF, or COALESCE

expression where the result of the expression can be

determined at query optimization time are now simplified

by the query optimizer.



CR:339756
CR Number:   339756
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e08 13 Jan 2004 Fixed
Description
sp_iqcheckdb stored procedure could stop responding if duplicate blocks are detected.



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

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

server contained a frame with the name SetBitsGetDuplicates.



CR:340204
CR Number:   340204
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.5 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e08 12 Dec 2003 Fixed
Description
Multiplex: committing a transaction on the write server after a DROP of a temporary table incorrectly advanced the write server's catalog version and put query servers out of synchronization.



CR:341119
CR Number:   341119
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Windows NT
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e08 06 Feb 2004 Fixed
Description
ASIQ plug-in in Sybase Central displays all objects despite filter settings for objects.



CR:341538
CR Number:   341538
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Solaris
Original Version:   12.4.3 e12
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e08 07 Jan 2004 Fixed
Description
The Encryption check box in the Sybase Central Create Database Wizard was selectable, which indicated that the IQ database could be created as encrypted.

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



CR:341659
CR Number:   341659
Product Name:   IQ
Product Component:   other
Status:   Closed
OS:   Solaris
Original Version:   12.4.3 e12
Fixed Version Build Resolution Date Closure Code (If Appropriate)
06 Jan 2004 Presently Not Targeted For Any Future Release Of This Product
Description
After alter database upgrade from isql, sp_iqcolumn returns error 195



CR:341738
CR Number:   341738
Product Name:   IQ
Product Component:   Utility
Status:   Closed
OS:   AIX
Original Version:   12.5 e07
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e08 28 Jan 2004 Fixed
Description
On AIX platforms only, if the IQ performance monitor

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



CR:342298
CR Number:   342298
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   future
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 03 Aug 2004 Fixed
Description
Feature request for encryption for data storage in IQ



CR:342404
CR Number:   342404
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 13 Feb 2004 Fixed
Description
The server fails when trying to execute a LOAD statement using an input file that has a double colon ("::") in its name. An "invalid filename" error is now displayed.



CR:342615
CR Number:   342615
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.5 e08
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e01 10 Feb 2005 Fixed
Description
An IQ server could become unresponsive during concurrent execution of REVOKE from

multiple user connections.



CR:342827
CR Number:   342827
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 05 Mar 2004 Fixed
12.5 e08 03 Feb 2004 Fixed
Description
An issue existed where queries that used the parallel group by hash algorithm and the database had a multi-byte character set collation could be rejected with an assert from "dfe_BaseColumn.cxx". This issue has now been resolved.



CR:343004
CR Number:   343004
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.4.3 e12
Fixed Version Build Resolution Date Closure Code (If Appropriate)
05 Feb 2004 DEFER
Description
Allow option to mask password when sql logging is turned on



CR:343104
CR Number:   343104
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.5 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 06 May 2004 Fixed
12.5 e08 03 Feb 2004 Fixed
Description
An issue existed where a query that had more than one sort-merge join against a complex derived table could in rare circumstances return too few rows.



CR:343230
CR Number:   343230
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Windows 2000
Original Version:   12.4.3 e12
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e08 23 Feb 2004 Fixed
Description
ODBC Administrator lists Adaptive Server IQ User Data Sources created using the dbdsn command as "Adaptive Server Anywhere" instead of "Adaptive Server IQ 12" sources.



CR:343809
CR Number:   343809
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 02 Apr 2004 Fixed
12.5 e12 23 Jan 2005 Fixed
Description
Fixed a server failure that could occur with a query

containing all of the following:

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

had selected the sort-based execution algorithm

(2) at least one additional subquery predicate

(3) both subquery predicates involved columns from

a single large table

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

(5) the optimizer had selected the NLPD join algorithm

to execute that join



CR:343902
CR Number:   343902
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e05 27 Jan 2004 Fixed
12.5 e08 27 Jan 2004 Fixed
12.6 23 Feb 2004 Fixed
Description
Certain join queries where some selected columns contain nulls and where at least one 'AND' is in the 'WHERE' clause could fail at s_bufman.cxx:3717 with a message 'Destroying Locked Logical Buffer'. If a detail query plan is available, this issue can further be identified if it contains a nested loop push down.
Workaround Description
 set temporary option Join_Preference = '-3'

set temporary option DML_Options25 = 'off'



CR:344667
CR Number:   344667
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e09 20 Feb 2004 Fixed
Description
For databases with multibyte collations, queries using LF and HG indexes on columns with BINARY datatype returned incorrect results.



CR:344765
CR Number:   344765
Product Name:   IQ
Product Component:   Utility
Status:   Closed
OS:   AIX
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 01 Oct 2004 Fixed
Description
Add ability to find UNIX process ID & host info for an IQ user using ISQL
Review Status
 Reviewed June 2004. This CR is targeted (but not committed) for the 15.0 release.



CR:345466
CR Number:   345466
Product Name:   IQ
Product Component:   Install
Status:   Closed
OS:   AIX
Original Version:   12.5 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 28 Jun 2004 Fixed
Description
sybinstall gave improper warning of 32 bit on the correct 64 bit Aix platform
Workaround Description
 The customer can run the "smit load64bit" command to update

their /etc/inittab file and prevent the IQ installation warning.



CR:346152
CR Number:   346152
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   12.5 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 22 Feb 2006 Fixed
Description
Allow ability to create HG unique index with columns containing null values.



CR:346215
CR Number:   346215
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.5 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e09 24 Feb 2004 Fixed
Description
On Windows servers only, an unnecessary one-second pause

would occur when opening a TCP/IP connection.



CR:346346
CR Number:   346346
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   12.5 e08
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 15 Mar 2004 Fixed
12.5 e11 11 Jun 2004 Fixed
Description
SELECT DISTINCT on DATE COLUMN FROM TABLE where the DATE column has multiple NULL values will incorrectly repeat the NULL values if the COLUMN does not have a LF or HG index defined.
Workaround Description
 Create a HG or LF on columns.



CR:347014
CR Number:   347014
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 Mar 2004 Presently Not Targeted For Any Future Release Of This Product
Description
Allow ability to create node via a script rather than Sybase Central



CR:347794
CR Number:   347794
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 03 May 2004 Fixed
Description
Feature request to add mechanism to adjust many-to-many join estimates to be more conservative.



CR:348738
CR Number:   348738
Product Name:   IQ
Product Component:   other
Status:   Closed
OS:   Solaris
Original Version:   12.4.3 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
24 Mar 2004 Presently Not Targeted For Any Future Release Of This Product
Description
Customer simply wants the ability to perform a read on the table while in any state.



**Resolution**

Not targeted for any future release of ASIQ



CR:349333
CR Number:   349333
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.4.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 21 Apr 2004 Fixed
12.5 e10 21 Apr 2004 Fixed
Description
Under the following circumstances, queries might

return inconsistent results or cause server failure:



1) There was a simple predicate on a column

2) That column contained one or more NULL values

3) The column was being compared to one or more

constants that were beyond the dynamic range

of the column's data type

4) The effect of the predicate should have been to

pass all non-NULL values in the column



For example:



T.COL_TINYINT < 300.



The specific symptoms of this problem depended

on the precise combination of data and query.

Duplicate of CR 351513.



CR:349338
CR Number:   349338
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e09
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 14 May 2004 Fixed
Description
A query using a view that contained both a user defined function and

CONTAINS in the WHERE clause would ignore the CONTAINS criteria.



CR:350034
CR Number:   350034
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows NT
Original Version:   12.5 e08
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 19 May 2004 Fixed
12.5 e11 16 Jun 2004 Fixed
Description
INSERT...LOCATION from ASE TEXT and IMAGE columns can now be inserted to appropriately typed columns in an IQ table (LONG VARCHAR (VARCHAR for esd11) and LONG BINARY respectively). It is possible that TEXT and IMAGE can be inserted into other IQ datatypes if internal conversion supports it. All data to be inserted will be silently truncated at 32767 bytes.



CR:350039
CR Number:   350039
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows NT
Original Version:   12.5 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 08 Dec 2004 Fixed
Description
LOAD table from named pipe on NT gives error "ASA Error - 1006096: Backup device is busy \\.\pipe\a2 -- (hos_ion.cxx:415)" This error occurs in v12.5 Sybase IQ. The problem is fixed in v12.6.



CR:350162
CR Number:   350162
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e09
Fixed Version Build Resolution Date Closure Code (If Appropriate)
08 Apr 2004 Presently Not Targeted For Any Future Release Of This Product
Description
IQ "hangs" when you reach your connection limit to the server and at that moment you get

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



CR:350411
CR Number:   350411
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
future 30 Mar 2004 Not a Bug
Description
Customer wants a more meaningful error status other than -6 "Miscellaneous user error" when a failed attempt to write to a table due to another user writing to the same table occurs.



CR:350729
CR Number:   350729
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.6 23 Nov 2004 Fixed
Description
sp_iqcheckdb incorrectly reports error during VERIFY of a non-unique, multi column hg index. The following sequence will show the error.



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

insert t1(c3) values (9)

create hg index hg1 on t1(c1, c2)

sp_iqcheckdb 'verify index hg1'



CR:350847
CR Number:   350847
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e09
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e10 27 Apr 2004 Fixed
12.6 12 Apr 2004 Fixed
Description
Non-fatal messages reported to the IQ Message file during sp_iqcheckdb could cause an incorrect report of a bitmap verify error at s_bmn.cxx:99.



CR:350982
CR Number:   350982
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e09
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e10 03 May 2004 Fixed
12.6 06 May 2004 Fixed
Description
Running queries or sp_iqcheckdb could produce a non-fatal error with hos_mvbio.cxx:466 and s_buf.cxx:1137 in the stack trace. You might also get a message about a 'Bad block number passed to object' in the IQ Message file. This failure could occur with non-unique HG indexes or word indexes.



CR:351107
CR Number:   351107
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   12.5 e09
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e10 03 May 2004 Fixed
Description
On AIX64, the limit of 1024 open file descriptors has been removed.

Reaching the 1024 open file descriptor limit could result in

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

to fail with "Connectivity libraries cannot be found".



CR:351590
CR Number:   351590
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.5 e09
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10 Jan 2005 Not a Bug
12.6 e01 01 Feb 2005 Fixed
Description
When performing forced recovery or leaked blocks recovery, you must start the database with the ".db" extension, not ".DB". For example:



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

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



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



CR:352758
CR Number:   352758
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e08
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 18 Apr 2005 Fixed
Description
Users requested the ability to disable compression

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

The reason for this request is that certain types

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

users to disable compression, the cost of trying

to compress data that won't compress is avoided thereby

saving CPU cycles.



CR:353482
CR Number:   353482
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 05 Aug 2004 Fixed
12.5 e11 07 Jul 2004 Fixed
Description
A complex query containing an outer join and arithmetic

expressions or functions over columns from the NULL

generating side of the outer join could be rejected

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

stack trace will contain "dfo_Join::NeedCloneDFE".



CR:353523
CR Number:   353523
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.5 e09
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e11 21 Jun 2004 Fixed
Description
On Windows servers only, some language files (locales) for the Open Client SDK were missing from the IQ 12.5 installation.



CR:353537
CR Number:   353537
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.6 01 Jun 2004 Fixed
12.5 e11 24 Jun 2004 Fixed
Description
The option "Dbcc_Log_Progress" has been added to the product that will output sp_iqcheckdb progress messages to the iqmsg file during sp_iqcheckdb execution. When the option is ON, each time a table, field, or index is processed by sp_iqcheckdb two messages will be written to the iqmsg file. One message will indicate that processing of the object has begun and the other message will state that processing of the object is complete. Sample of some messages for sp_iqcheckdb 'allocation table nation':



Start ALLOCATION table: nation

Start ALLOCATION processing index: ASIQ_IDX_T445_C1_FP

Start ALLOCATION processing index: nationhg1

Done ALLOCATION table: nation

Done ALLOCATION processing index: nationhg1

Done ALLOCATION processing index: ASIQ_IDX_T445_C1_FP



CR:353538
CR Number:   353538
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e09
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 06 Nov 2004 Fixed
Description
It is now possible to specify an indextype for all of the sp_iqcheckdb modes. The new syntax is:

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

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

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

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

sp_iqcheckdb 'check indextype fp database'

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

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



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

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

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



CR:353695
CR Number:   353695
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Unknown
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 28 Nov 2004 Fixed
21 Jun 2004 DEFER
Description
When creating a new query server, the IQ agent could generate a time-out error if the dbbackup process took longer than five minutes. Instead of reporting the error, the Create Query server wizard tried to start the new server, only to fail in startup.



CR:353819
CR Number:   353819
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e09
Fixed Version Build Resolution Date Closure Code (If Appropriate)
06 May 2004 Duplicate
Description
upper(),lower() functions do not convert accented characters appropriately



CR:353823
CR Number:   353823
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.5 e09
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 17 May 2004 Fixed
12.5 e11 24 Jun 2004 Fixed
Description
The sp_iqcheckdb (check index...) procedure did not return a completed verified list for all indexes submitted.



CR:353999
CR Number:   353999
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Unknown
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 13 Dec 2004 Fixed
21 Jun 2004 DEFER
12.6 25 Aug 2004 Fixed
Description
Synchronization via sybase central could fail if the dbbackup process took longer than five minutes. This is because the IQ agent had a built in time-out value set at five minutes. But some database files were too large to back up in five minutes and Sybase Central therefore could not be used. The agent needed to support a configurable time-out value.



CR:354034
CR Number:   354034
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   12.5 e09
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 09 Jul 2004 Fixed
12.5 e11 18 Jun 2004 Fixed
Description
A checkpoint, for example as part of backup, might cause server failure if the database was in an out-of-space condition.



CR:354688
CR Number:   354688
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e10
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 24 May 2004 Fixed
12.5 e11 07 Jul 2004 Fixed
Description
The server could fail on an insert, load, or update

when the following conditions were true:



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

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

exceeded 200



b) the user performed an incremental insert into the table



CR:354983
CR Number:   354983
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.5 e10
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 05 Oct 2004 Presently Not Targeted For Any Future Release Of This Product
12.5 e11 16 Jun 2004 Fixed
Description
A database that was created with IQ v12.4.0 cannot be restored to IQ version 12.5.0 or later. This is fixed in 12.5.0 esd11 and 12.6.



CR:355250
CR Number:   355250
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Windows XP
Original Version:   12.5 e10
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 05 Jul 2004 Fixed
12.5 e11 21 Jun 2004 Fixed
Description
WATCOM stored procedure with a SQLCODE or SQLSTATE as parameter with a T-SQL variable assignment SELECT @AAA=col1 from table will crash IQ silently.
Workaround Description
 Do note use SQLSTATE or SQLCODE in the parameter list.



CR:355297
CR Number:   355297
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 07 Jul 2004 Fixed
12.5 e12 05 Jan 2005 Fixed
Description
Issue was the result of improper handling of

expressions containing a varying host variable

plus constants or additional host variables,

but containing no columns or aggregates.



CR:356067
CR Number:   356067
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 07 Sep 2004 Fixed
12.5 e11 21 Jun 2004 Fixed
Description
A query can cause the IQ Server to fail with a Signal 11 and a stacktrace. The stacktrace contains v2s_bmcontext::InitializePrevBit()
Workaround Description
 There are two ways I can think of that might workaround the problem of the index not being reported.



1. Run sp_iqcheckdb in check mode against the table. In the Index Statistics section of the output, it will list all indexes that verified correctly and then provide a count of them at the bottom of this section. If the count at the bottom is greater then the number of indexes that were verified, then an index (or indexes) did have a problem. You can look to see what index the table has that did no show up in the "Index Statistics" section.



2. Run sp_iqcheckdb in check mode on each index. Monitor the IQ message file for a message about "Bad block number" around hos_mvbio.cxx:466. When this message appears, the index that was being checked at the time is inconsistent.





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

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