远程Sybase数据库技术支持,联系手机:13811580958,QQ:289965371!

 

随着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:356217
CR Number:   356217
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   AIX
Original Version:   12.5 e08
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 23 Nov 2004 Fixed
12.5 e11 30 Jun 2004 Fixed
Description
On IBM RS/6000 systems, when the Sybase Central Agent started up the dbremote process, the password parameter could have been obtained via the ps command.
Workaround Description
 To hide the login and password, I changed the script like this:



1 - scripts of start dbremote.



#!/usr/bin/sh

# File: start_dbremote_orbitall

# Server: orbitall

# Database: orbitall.db

# Script to start SQL Remote for a Write server

# Command line parameter(s): DBA login password





setenv SQLCONNECT "con=dbremote-

orbitall;eng=orbitall;links=tcpip{host=gladiator;port=26000;dobroadcast=none;ver

ify=no};uid=dba;pwd=sql"



dbremote -ud -v -o /glad1/telmo/orbitall/repDirs/logfiles/orbitall.dbrlog



CR:357273
CR Number:   357273
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Windows NT
Original Version:   12.5 e09
Fixed Version Build Resolution Date Closure Code (If Appropriate)
07 Jun 2004 Workaround
Description
IQ 12.5. Incorrect results returned when using a case insensitive database and data that includes special characters like n tilde () and the search argument has has the character in upper case. The behaviour differs depending on the collation being used.



CR:357358
CR Number:   357358
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 e11 21 Jun 2004 Fixed
12.6 29 Jun 2004 Fixed
Description
During the execution of predicates using an FP index

from a very large table, several minutes could pass

between checks for whether the user had requested

that the statement be cancelled or the connection

dropped. Additional cancellation checks were added

to make the maximum delay during this type of

operation be a few seconds.



CR:357533
CR Number:   357533
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   12.5 e08
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 08 Oct 2004 Fixed
Description
The customer does not want to change all of their statements to "column1 >= constant and column2 <= constant" and are requesting that an index be used when using a constant in the following predicate statement: "constant between col1 and col2".



CR:358638
CR Number:   358638
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows NT
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 08 Dec 2004 Not a Bug
Description
ASIQ 12.5 esd 10. When the iqmsg file hits the IQMSG_Length_MB (setting and wraps to the top, the following re-starts of IQ are writing the initial db open and start up messages at the end of the iqmsg file then re-wraping to the top instead of restarting at the <next msg insertion place> message. This will grow the iqmsg file further past the IQMSG_Length_MB setting size each restart.



CR:358707
CR Number:   358707
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 08 Jul 2004 Fixed
Description
In unchained mode, The UPDATE CURSOR operation may have gotten a stack trace.

IQ Server should return an error message correctly.
Workaround Description
 set temporary option Chained='ON'



CR:358882
CR Number:   358882
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.5 e10
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 17 Nov 2004 Fixed
Description
29 oct 2004 update: Default Open CLient Library password encryption is supported only when connecting to SQL Server (v10 and later), ASE, and Open Server (v10 and later). In order to allow users to specify whether or not they wish to use password encryption while connecting, the INSERT statement syntax has been enhanced. The new syntax is:



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

insert-load-options

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

{ select-statement }



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



(-end of update-)



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



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



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



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



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

failed_login_attempts integer,

primary key (username) );



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



create event ev_badlogin type ConnectFailed handler

begin

declare uid char(128);

declare xx integer;



set uid = event_parameter(慤ser);



if exists (select * from dba.event_table

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



-- The user is already in the table.



update event_table set failed_login_attempts =

failed_login_attempts+1

where ucase(username) = ucase(uid);



else

-- Insert the user for the first time.



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



end if;



select failed_login_attempts into xx from dba.event_table

where ucase(username)=ucase(uid);



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

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

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



if xx > 5 then



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



end if;



end



The login procedure.



Create procedure dba.check_logins()



begin



declare xx integer;



declare uid char(128);



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



if exists (select * from dba.event_table

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



select failed_login_attempts into xx from dba.event_table

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



if ( xx >= 5 ) then



raiserror 17010 current user + has been locked out by the

Database Administrator.;



else



-- The user has connected.

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

-- the default login procedure for the database.



set uid=current user;



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



call sp_login_environment();



end if;



else



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

-- login procedure for the database.



call sp_login_environment();

end if;



end;



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



grant execute on dba.check_logins to PUBLIC;



set option PUBLIC.Login_Procedure = 慸ba.check_logins;



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



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



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

failed_login_attempts integer,

primary key (username) );



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



create event ev_badlogin type ConnectFailed handler

begin

declare uid char(128);

declare xx integer;



set uid = event_parameter(慤ser);



if exists (select * from dba.event_table

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



-- The user is already in the table.



update event_table set failed_login_attempts =

failed_login_attempts+1

where ucase(username) = ucase(uid);



else

-- Insert the user for the first time.



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



end if;



select failed_login_attempts into xx from dba.event_table

where ucase(username)=ucase(uid);



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

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

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



if xx > 5 then



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



end if;



end



The login procedure.



Create procedure dba.check_logins()



begin



declare xx integer;



declare uid char(128);



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



if exists (select * from dba.event_table

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



select failed_login_attempts into xx from dba.event_table

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



if ( xx >= 5 ) then



raiserror 17010 current user + has been locked out by the

Database Administrator.;



else



-- The user has connected.

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

-- the default login procedure for the database.



set uid=current user;



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



call sp_login_environment();



end if;



else



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

-- login procedure for the database.



call sp_login_environment();

end if;



end;



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



grant execute on dba.check_logins to PUBLIC;



set option PUBLIC.Login_Procedure = 慸ba.check_logins;



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



CR:359706
CR Number:   359706
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   12.5 e10
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
The request for the grouping about would be an enhancement to the T-SQL NTILE

functionality.

The rank functionality would need something like:

rank () over ( [query_partition_clause] order_by_clause )

same with dense_rank

dense_rank () over ( [query_partition_clause] order_by_clause )

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



CR:360194
CR Number:   360194
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.5 e10
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e12 24 Aug 2004 Fixed
Description
Under certain conditions, when executing INSERT..LOCATION in conjunction with a mechanism to provide basic connectivity to a non-Sybase data source (for example, DirectConnect), Sybase IQ incorrectly determined that the INSERT..LOCATION operation succeeded, and committed the results instead of rolling back the operation.



CR:361123
CR Number:   361123
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 e04 19 Apr 2005 Fixed
Description
The performance of IN predicates has been improved for some

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



CR:361125
CR Number:   361125
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 e04 19 Apr 2005 Duplicate
Description
The performance of IN predicates has been improved for some

queries where there are many rows in the table.



CR:361147
CR Number:   361147
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 e04 20 Apr 2005 Fixed
Description
The performance of IN predicates has been improved for some

queries where there is at least one additional restrictive

predicate on a column from the same table.



CR:361254
CR Number:   361254
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 27 Jul 2004 Fixed
Description
The following SQL will fail with an "IQ internal error" message.



drop table t2;

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

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

insert t2 values(1, 2, 3);

insert t2(c3) values(1);

delete from t2 where rowid(t2) = 2;



This is fixed in 12.6



CR:361594
CR Number:   361594
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 27 Jul 2004 Fixed
Description
The following sequence of statements will cause the server to fail at hos_bv.h line 603:



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

create hg index hg1 on t1(c1)

create hg index hg2 on t1(c1,c2)

sp_iqcheckdb 'verify index hg1 index hg2'



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



CR:361871
CR Number:   361871
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 13 Apr 2006 Fixed
12.6 e05 15 Nov 2005 Fixed
Description
There was an intermittent problem where the IQ server became unresponsive.



CR:362102
CR Number:   362102
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 18 Apr 2005 Fixed
Description
Users are unable to connect if either of the IQ User Admin tables (IQ_SYSTEM_LOGIN_INFO_TABLE or IQ_USER_LOGIN_INFO_TABLE) has been dropped.



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

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

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



CR:362141
CR Number:   362141
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)
19 Jan 2005 Presently Not Targeted For Any Future Release Of This Product
Description
Feature Request:



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



CR:362600
CR Number:   362600
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 10 Mar 2006 Fixed
Description
Request a feature like Oracle's 'OPTIONALLY ENCLOSED BY '"' ' option, which allows input fields to include the indicated delimiter in their text if they enclose it between double quotation marks.



CR:362699
CR Number:   362699
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Other 19 Nov 2004 Failed
12.5 e12 15 Dec 2004 Fixed
Description
Implicit conversion from CHAR types to NUMERIC types is now allowed. For example,



create table t1 (c1 int)

insert t1 values ('9')



will insert the row.



CR:363023
CR Number:   363023
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
13 Sep 2004 Fixed
Description
'create existing table' command from IQ to Oracle gives error 'could not access column information for the table'



CR:363865
CR Number:   363865
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 24 Jan 2008 Fixed
Description
Query performance was affected by extensive IFNULL( < expr > ,SPACE(10), < expr > ) or COALESCE( < expr > ,SPACE(10)) expressions; for example, turning empty strings into NULLs. This issue has been resolved.



CR:364386
CR Number:   364386
Product Name:   IQ
Product Component:   Utility
Status:   Closed
OS:   AIX
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 15 Feb 2006 Fixed
Description
Users at customer site are looking for certain useful functionality they have in ASE -- a utility like defncopy to extract stored procedures from the server. Customer has asked for an enhancement request to be opened to provide this functionality.



CR:365163
CR Number:   365163
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Windows 2000
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
07 Sep 2004 Duplicate
Description
behavior of info available in sa_eng_properties needs to be explained



CR:365435
CR Number:   365435
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e06 20 Jan 2006 Fixed
Description
While running multiple connections that fetch from different proxy tables and different remote servers using ASEJDBC, if one application was terminated, then the Java virtual machine could no longer be started.



CR:367460
CR Number:   367460
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 e01 15 Feb 2005 Fixed
Description
Sybase IQ will not propagate CREATE, ALTER, and DROP statements for procedure and function definitions from the write server to query servers in a multiplex. You must use one of the following methods to keep procedure and function definitions consistent across multiplex servers.



1. After executing the DDL statements to modify

procedures and functions at the write server,

execute the same statements on each query

server. Create a SQL script for this approach

to ensure consistent definitions.



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

procedures and functions at the write server,

synchronize each query server.



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



CR:368173
CR Number:   368173
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 e04 20 Apr 2005 Fixed
Description
The performance of IN and range predicates (<, <=, >, >=, BETWEEN)

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

additional very restrictive predicate on a column from the same

table.



CR:368318
CR Number:   368318
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Unknown
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Dec 2004 Fixed
Description
The sample command for restarting dbremote to truncate the transaction log which has been described

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



CR:369558
CR Number:   369558
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 e04 03 May 2005 Fixed
12.6 e04 20 Apr 2005 Fixed
Description
The output of the sp_iqlistpasswordexpirations stored procedure has been changed as follows: The column "Days_till_Expiration" now is the number of days until the password expires. If the password has expired, "Expired" will appear in the output in this column. A "0" (zero) means that the password does not expire. A new column, "Password_Expiration_Interval" has been added. This column contains what the "Days_till_Expiration" used to contain. That is, the total number of days the password is valid on the date it was created. A "0" (zero) means that the password does not expire. For example, on day 1 a user is created with a password that is valid for 10 days. When the stored procedure sp_iqlistpasswordexpirations is run on day 7, the value of Days_till_Expiration for that user will be "4" and the value of Password_Expiration_Interval for that user will be "10".



CR:369612
CR Number:   369612
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 28 Nov 2004 Failed
Description
When creating an IQ database, a minimum 4k ASA page size will be silently enforced. Larger ASA page sizes may be used, but if the user tries to use a smaller page size, it will be set at 4096 with no notification to the user.



CR:369761
CR Number:   369761
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows XP
Original Version:   12.5 e10
Fixed Version Build Resolution Date Closure Code (If Appropriate)
21 Oct 2004 Duplicate
Description
Duplicate of #355297.



Issue was the result of improper handling of

expressions containing a varying host variable

plus constants or additional host variables,

but containing no columns or aggregates.



CR:370316
CR Number:   370316
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 e01 01 Mar 2005 Fixed
Description
When creating a main dbspace on a write server, you must create aliases for the query servers before you synchronize them or they cannot open the new file. This was omitted from chapter 5, "Working with Database Objects," in the Sybase IQ System Administration Guide.



CR:370429
CR Number:   370429
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
19 Mar 2013 Insufficient priority to fix
Description
Request option to set resources by DBA at server level instead of session level.



CR:370902
CR Number:   370902
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 03 Nov 2004 Fixed
Description
3 nov 2004: sp_iqaddlogin will now use the default number_connects from IQ_SYSTEM_INFO_TABLE for a new login.



CR:371155
CR Number:   371155
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 25 Jan 2006 Fixed
Description
Some sql statements that have identifiers containing double quotes may fail with a syntax error. For example,

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

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



CR:371375
CR Number:   371375
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows XP
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 05 Apr 2006 Fixed
12.7 10 May 2006 Fixed
12.7 14 May 2006 Fixed
Description
When loading data into a Word Index that is longer than the LIMIT specified while creating the index, the entire load will terminate with an error and rollback.

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

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



Here is the LOAD TABLE syntax showing this option:

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

FROM filename-string

[ load-option ]



load-option:

[ CHECK CONSTRAINTS { ON | OFF } IGNORE ]

[ DELIMITED BY string ]

.

.

.

[ WORD SKIP number ]

[ ONLY LOG logwhat [,匽 ]

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

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



CR:372186
CR Number:   372186
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.5 e12 14 Jan 2005 Fixed
Description
Loading data into a non-unique HG index would occasionally fail

with an IQ Internal Error at location s_gUtil.cxx; 682. This has been fixed.
Workaround Description
 Not much, one way is to drop and rebuild the non unique HG index on the table and also drop abd rebuild foreign keys, if any. It is not guaranteed to work always, another drastic measure is to completely remove non unique HG index and load the data in the table.



CR:372631
CR Number:   372631
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e01 01 Feb 2005 Fixed
Description
If a batch containing a call to an external procedure is executed, and the external procedure is then subsequently canceled, then the batch continues execution instead of being canceled. This problem has been fixed.



CR:372998
CR Number:   372998
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 08 Dec 2004 Fixed
12.5 e17 07 Jul 2005 Fixed
Description
When using Open Client 12.5 ESD 14 with IQ 12.5 it is possible for IQ to fail if an active insert location connection is killed at the source server.



CR:373114
CR Number:   373114
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 e04 03 May 2005 Fixed
Description
Running sp_iqmodifyadmin 'enable' will now add userids with passwords that have been granted group to the admin tables.



CR:373124
CR Number:   373124
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows XP
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 04 Apr 2005 Workaround
Description
#temptable kept old definition in cache if same procedure dynamically created a temp table with the same name within the same session.
Workaround Description
 None.



CR:373249
CR Number:   373249
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
01 Mar 2005 Not a Bug
Description
Customer feels strongly about having the system procedures for logins maintain data in IQ_USER_LOGIN_INFO_TABLE even though the documentation represents this as an option if one cares to enable "the IQ User Administration.facility." They feel that login information should always be in the IQ_USER_LOGIN_INFO_TABLE and it should be correct.



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



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

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



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

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

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



CR:373298
CR Number:   373298
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
23 Jan 2007 Presently Not Targeted For Any Future Release Of This Product
Description
This subcase is to request a CR that IQ certification testing on AIX 5.3, currently scheduled for December, include testing with the Watson algorithm. Likely it is turned on using an environment variable; I don't know the setting but if it is not described in the AIX 5.3 documentaiton we get, I can go through my IBM contacts on this issue and get that information.



CR:373883
CR Number:   373883
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 e01 05 Jan 2005 Fixed
12.5 e16 18 Apr 2005 Fixed
Description
A timing race when a database event occurred during database shutdown

caused a failure on an internal consistency check.



CR:374292
CR Number:   374292
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Solaris
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
future 11 Jan 2005 Fixed
Description
A multiplex synchronize may fail with the following error in the Agent log file:



java.io.IOException: Not enough space



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

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



CR:374729
CR Number:   374729
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e01 30 Dec 2004 Fixed
Description
Server fails when the SQL Anywhere index consultant is run after a

query that accesses IQ store tables. The diagnostic information in

the message file shows the dbi_partialopen function at or near the

top of the stack trace.



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

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

Anywhere index consultant is started by other means, it will

run without a server failure.



Note that in general the SQL Anywhere Index Consultant will not

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

12.6 Index Advisor feature is the proper tool for automatically

generating index recommendations for Sybase IQ databases.



CR:374738
CR Number:   374738
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e01 14 Jan 2005 Fixed
Description
On AIX64, the Multiplex stop_server script could fail

with the error "IOT/Abort trap".



The issue is resolved in 12.6 ESD1 by regenerating the Multiplex

Admin Scripts for the Multiplex Servers via Sybase Central.



CR:374825
CR Number:   374825
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e12
Fixed Version Build Resolution Date Closure Code (If Appropriate)
01 Feb 2005 Workaround
Description
Make the ASE-compatibility system stored procedures for managing logins -- sp_addlogin, sp_droplogin, sp_locklogin and sp_password.-- call their "iq" counterparts -- sp_iqaddlogin, sp_iqdroplogin, sp_iqlocklogin and sp_iqpassword. This will eliminate one source of inconsistency in user login management. Customer has provided sample modified versions of the "non-IQ" stored procedures. See /remote/cases Repro directory for -12 subcase.



CR:374894
CR Number:   374894
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Suse
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e01 07 Jan 2005 Fixed
Description
stop_asiq used the wrong PS format on SuSe 9.x, causing it not to identify servers correctly.



CR:375333
CR Number:   375333
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 e01 20 Jan 2005 Fixed
Description
The following example shows how to give non-DBA users the

ability to execute commands that require DBA privileges.

This example creates a policy that lets a non-DBA

user (user1) perform backup.

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

create procedure "DBA".do_backup()

begin

backup database

crc on

attended off

block factor 4

full

to 'fileA' size 2000

to 'fileB' size 2000

to 'fileC' size 2000

;

end;



grant execute on "DBA".do_backup to user1;



CR:375585
CR Number:   375585
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 e01 24 Feb 2005 Fixed
12.6 e01 14 Feb 2005 Fixed
Description
The ALTER INDEX command returns an "index not found" error if you try to alter an index in a local temporary table. If you try to alter an index that is automatically created, such as a default index, IQ returns a "cannot alter index" error.



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



CR:375822
CR Number:   375822
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e01 02 Feb 2005 Fixed
Description
Due to the virtual memory usage pattern within the Sybase IQ server, virtual memory fragmentation could result, causing excessive process growth on Windows platforms. To reduce the likelihood of this problem, Sybase IQ now supports the use of Microsoft's low-fragmentation heap (LFH) on Windows XP and Windows Server 2003.



CR:376130
CR Number:   376130
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   AIX
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5 e12 28 Jan 2005 Fixed
Description
It is unclear from the IQ documentation that an update command is not allowed on a table that is part of a join index. It is not mentioned in the section discussing join indexes and it should be.



CR:376134
CR Number:   376134
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Unknown
Original Version:   12.6 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e01 07 Feb 2005 Fixed
Description
If an Open Client application opened a cursor which generated the "cursor options

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

now been fixed.



CR:376550
CR Number:   376550
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Unknown
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e01 18 Jan 2005 Fixed
Description
Using "comment" on a local temporary table would result in

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

local temporary table is now prohibited with an informational

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



CR:376618
CR Number:   376618
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 25 Apr 2005 Fixed
Description
You cannot connect to a Sybase IQ 12.6 server using an ODBC Data Source Name created for a 12.5 server, even if you specify the same server name, port number, and database name.



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

and add new DSNs.



CR:376991
CR Number:   376991
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 e01 01 Feb 2005 Fixed
Description
A query server may fail with error "Tried to insert a duplicate entry." at s_hashtb.cxx:290. This error might occur while performing a referential integrity check after replaying an "ALTER TABLE ADD FOREIGN KEY" from a write server where the foreign key is a multicolumn index for which one of the columns contains no data.



CR:377444
CR Number:   377444
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 20 Apr 2005 Fixed
12.5 e15 29 Mar 2005 Fixed
Description
The Sybase IQ server failed with a stack trace in s_dpidxfecth.cxx when CTRL-C interrupted a query.



CR:377612
CR Number:   377612
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 e01 26 Jan 2005 Fixed
Description
Performing an update on a table that contains a column with a default value of AUTOINCREMENT crashes the server with stack trace.



CR:377882
CR Number:   377882
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   12.5 e10
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 14 Mar 2005 Not a Bug
Description
Password expiration message send back to the client



CR:378084
CR Number:   378084
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)
Other 16 Feb 2005 Fixed
12.5 e15 23 Mar 2005 Fixed
Description
When using CIS Remote Data Access with a JDBC server class or

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

result in server failure.



CR:378190
CR Number:   378190
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 14 Apr 2005 Fixed
Description
If an active IQ server ran out of temporary space with several transactions suspended waiting for additional temporary store, the server became unresponsive when the number of active queries equalled the number of allowed concurrent queries.
Target Version
 12.6 e03



CR:378369
CR Number:   378369
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Solaris
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2
Description
Request: Implement a feature similar to ASE 12.4.3 sp_recompile that would allow stored procedures that used a table where a column was just added to see that new column with a SELECT * from table. This would mean both supporting the Transact-SQL WITH RECOMPILE option and implementing a similar stored procedure to that of ASE's sp_recompile.



CR:378606
CR Number:   378606
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11 Feb 2005 Fixed
Description
Using a CASE expression inside the VALUES clause of an INSERT statement generated a stack trace with a signal 11.
Workaround Description
 evaluate case expression into a variable and use the variable in the insert in place of the case statement in the values clause.



CR:378609
CR Number:   378609
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e01 17 Feb 2005 Fixed
Description
After the error "A maximum of one subquery predicate per conjunct is supported

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



CR:378772
CR Number:   378772
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 11 Apr 2005 Fixed
Description
A customer was truncating

the .iqmsg file (for example, via the unix

command cp /dev/null <iqmsg file>)

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

customer collect new information from the .iqmsg

file at regular known intervals to help

monitor the database engine.



The ability to truncate the .iqmsg file in this manner

was accidentally removed when the .iqmsg file wrapping functionality

was added to Sybase IQ.



CR:378924
CR Number:   378924
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e10
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 Feb 2005 Fixed
12.5 e15 23 Mar 2005 Fixed
Description
When inserting a local table with rows selected from a proxy table on a remote server, the IQ server might fail if the remote server was down or not available. The failure only occurred if the INSERT ... SELECT statement made the first attempt to connect to the remote server.



CR:378934
CR Number:   378934
Product Name:   IQ
Product Component:   Utility
Status:   Closed
OS:   Unknown
Original Version:   12.6 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e01 11 Feb 2005 Fixed
Description
When the '-f' server command argument is used, the start_asiq script no longer reports an error from dbspawn that the server was not left open. Shutting down the server after discarding the transaction log is the expected behavior. After using '-f', the server must be restarted normally without the '-f' option. See Chapter 2 System Recovery and Database Repair of the Troubleshooting and Error Messages Guide.



New behavor:

> start_asiq @asiqdemo.cfg -f asiqdemo.db



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



...



Database recovery in progress

Last checkpoint at Fri Feb 04 2005 15:54

Checkpoint log...

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

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

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

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

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

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

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

---IOX: Could not open script file

Wrapping iqmsg: Disabled.

Transaction log: asiqdemo.log...

Forcing recovery without transaction log

Rollback log...

Checkpointing...

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

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

Recovery complete

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

Database server stopped at Tue Feb 08 2005 09:24



Recovery complete

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



CR:379059
CR Number:   379059
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 e01 08 Feb 2005 Fixed
future 30 Jan 2006 Fixed
Description
Server no longer displays message "---IOX: Could not open script file" at database open.



CR:379440
CR Number:   379440
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 21 Apr 2005 Fixed
Description
A query that loaded invalid data into a FLOAT column failed with the ASA error -1006000 instead of returning a "Cannot convert" error (-157).



CR:379489
CR Number:   379489
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows XP
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 16 May 2005 Fixed
Description
The Sybase IQ server became unresponsive when running sp_iqtransaction.
Target Version
 12.6 e03



CR:379694
CR Number:   379694
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Unknown
Original Version:   12.6 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e01 24 Feb 2005 Fixed
Description
Running REFRESH ALL in Sybase Central returned a stack trace with a null exception.



CR:379695
CR Number:   379695
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e01 16 Feb 2005 Fixed
Description
The LOCK TABLE statement is allowed but undocumented

in Sybase IQ 12.6. This statement prevents other concurrent

transactions from accessing or modifying a table. Syntax

is:



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

MODE



Parameters are:



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



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

Otherwise, releases the lock when current transaction is

rolled back or ends.



SHARE mode - Other transactions cannot modify the table

but have read access. Requires SELECT privileges.



EXCLUSIVE mode - Other transactions cannot execute queries,

updates, or any other transaction against the table. Requires

DBA authority or ownership of the table.



This statement blocks or delays other transactions that may

require access to the table. LOCK TABLE allows direct control

over concurrency at a table level, independent of isolation

level.
Review Status
 Request documentation of the "lock table" command in IQ.



CR:379969
CR Number:   379969
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 02 May 2005 Fixed
Description
When creating a stored procedure in dbisqlc and in isql without qualifying the procedure name and the procedure exists and is owned by another user, an error is thrown.



CR:380038
CR Number:   380038
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 14 Feb 2005 Fixed
Description
When an event is executed, it runs on its own connection. If an event connection was dropped (either from Sybase Central or using the DROP CONNECTION statement), the server would have crashed, if it had been started with the -z switch.
Workaround Description
 Disable -z or event.



CR:380079
CR Number:   380079
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.6 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e05 29 Jul 2005 Fixed
Description
When an IQ Data Source Name was created with iqdsn (the IQ version of dbdsn) the new DSN could not be listed, viewed or deleted using iqdsn.



CR:380583
CR Number:   380583
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 06 Apr 2005 Fixed
29 Mar 2005 Fixed
Description
A read-only query server may fail to deallocate all old versions of cached catalog objects.



CR:380590
CR Number:   380590
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 23 Feb 2005 Fixed
12.5 e15 29 Mar 2005 Fixed
12.6 e04 24 May 2005 Not reproducible with latest version of the product available as of Resolution Date
Description
A race condition involving a user's connection being

explicitly dropped or implicitly timed out and a

different user interrupting a command just scheduled

to run by the IQ resource gate could result in a

deadlock.



CR:380625
CR Number:   380625
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e05 06 Oct 2005 Fixed
12.6 e05 17 Oct 2005 Fixed
12.6 e05 10 Aug 2005 Fixed
Description
There is new default behavior regarding the posting of data conversion warning messages

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

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

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

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

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



set temporary option conversion_error='off';

set temporary option ddl_options2=8;



CR:380959
CR Number:   380959
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 12 May 2005 Fixed
12.5 e15 23 Mar 2005 Fixed
12.5 e17 06 Jul 2005 Fixed
Description
Under certain circumstances, a read only query node may fail to drop all old and no longer referenced cached catalog objects.



CR:381558
CR Number:   381558
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.5 e11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 28 Apr 2006 Fixed
12.6 e07 11 Jul 2006 Fixed
Description
ASE columns of type char or varchar or binary or varbinary with lengths greater than 255 are now correctly inserted into IQ tables with INSERT LOCATION. The data is no longer truncated at 255 provided that the IQ columns are defined large enough to hold the data.



CR:381569
CR Number:   381569
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Windows NT
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 29 Apr 2005 Fixed
Description
When altering a table, Sybase Central did not restore the Pkey check box correctly after a failure to cut a column.



CR:381604
CR Number:   381604
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   12.6 e02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e02 22 Mar 2005 Fixed
Description
Changes have been implemented to support cross-platform migration for little endian platforms.



CR:381651
CR Number:   381651
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Solaris
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
18 Jul 2006 Not reproducible with latest version of the product available as of Resolution Date
Description
SCJ12.6 abortes if the Server Name is omitted at CONNECT when SCJ started as Japanese Client, e.g. LANG=ja.
Workaround Description
 Specify the Server Name at CONNECT parameters

or Change the LANG environment to English

or use the iAnywhere driver instead of the jConnect driver.



CR:381800
CR Number:   381800
Product Name:   IQ
Product Component:   Utility
Status:   Closed
OS:   Linux Red Hat
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e02 16 Mar 2005 Fixed
Description
A problem running Sybase Central on Linux has been resolved. The scjview script now forces the use of the bash shell instead of the korn shell, which is not installed by default on RedHat 2.1.



CR:382199
CR Number:   382199
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 12 Mar 2006 Fixed
12.6 e07 28 Mar 2006 Fixed
Description
Multiplex DML replay of SYNCHRONIZE JOIN INDEX with

an insert to the bottom table of a join caused query server failure.
Target Version
 12.6 e07



CR:382357
CR Number:   382357
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2000
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
27 Apr 2005 Not a Bug
Description
Assigning data from a binary field to a binary variable resulted in data being displayed incorrectly.



CR:382541
CR Number:   382541
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 e04 21 Apr 2005 Fixed
12.5 e15 23 Mar 2005 Fixed
Description
The server could fail if a query was interrupted by the

user at an unlikely but problematic point during the

first few seconds of execution.
Workaround Description
 Avoid typing ^C for the first few

seconds that a query is running.



CR:382554
CR Number:   382554
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 10 Apr 2005 Fixed
Description
A race condition between the checkpoint and sp_iqdbspace could cause an unresponsive server.



CR:382663
CR Number:   382663
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Windows 2000
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 08 May 2005 Fixed
Description
Customers using Sybase Central java 4.3.0.2359 with IQ plug-in 12.6.0.041203 were unable to specify cardinality using the IQ UNIQUE column constraint when creating tables.
Workaround Description
 if table defs have colums that need IQ UNIQUE specified then use a client other then SC.



CR:382669
CR Number:   382669
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Windows 2000
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 28 Apr 2005 Fixed
Description
When creating a new table in Sybase Central, if you made a mistake (like a duplicate column name or a forgotten column data type) and clicked the save table icon (or right-clicked table and save table) Sybase IQ returned the expected SQL syntax error message, but lost the entire table definition.
Workaround Description
 see main description



CR:382730
CR Number:   382730
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows XP
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 12 Apr 2005 Fixed
Description
Feature request for same properties in 12.6 on Table -> Properties -> Miscellaneous plugin as with the 12.5 Table -> Properties -> Statistics panel.



CR:383625
CR Number:   383625
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 06 May 2005 Fixed
Description
Certain INSERT ... SELECT DISTINCT statements where there

is also a GROUP BY clause could result in either

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

error from dfo_Root.cxx:785.



CR:383634
CR Number:   383634
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 e04 08 Apr 2005 Fixed
Description
A guery containing join and group by clauses under the sort-merge pushdown join algorithm failed at dfo.cxx 5899 with the error: "Input to *** not ordered as required".



CR:383732
CR Number:   383732
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.6 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 28 Mar 2005 Fixed
Description
On Windows, Sybase IQ 12.6 could not use caches greater than 1.7GB on systems enabled for 4GT.
Target Version
 12.6 e03



CR:383741
CR Number:   383741
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 18 May 2005 Fixed
Description
A query server failed with a stack trace

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

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



CR:383932
CR Number:   383932
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 15 Apr 2005 Fixed
Description
On an IQ server, a query with only ASA tables that used an outer join might return a "rowid not implemented" error.



CR:383979
CR Number:   383979
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   HP-UX
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e04 16 Apr 2005 Fixed
Description
The parser now generates an error message whenever a user

attempts to reference a view that needs to be recompiled

because of changes to the schema of a table used within

that view.



CR:384081
CR Number:   384081
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 e04 01 Jun 2005 Fixed
Description
For users with queries containing predicates on numerous

large tables, the thread allocation policies for predicate

execution have been improved. If you have lots of queries

that meet the criteria above, and especially if you have

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

CPUs, then you should:



set PUBLIC.Enable_Thread_Allowance = 'ON'



CR:384143
CR Number:   384143
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Linux Red Hat
Original Version:   12.6 e02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e06 25 Jan 2006 Fixed
Description
In rare circumstances, a multiplex query server executing an operation on its local store could fail with the exception "Abort at s_bufhash.cxx:333."





--------------------------------------华丽的分割线-------------------------------------------------------------------------
之前就已经研发成功了能够从Sybase SQL Anywhere的DB文件中恢复数据的工具:ReadASADB。
此工具支持ASA v5.0,v6.0,v7.0,v8.0,v9.0,v10.0,v11.0,v12.0等版本。
恢复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
  2. 适用于所有的UltraLite版本
  3. 能够恢复出来表结构和数据
  4. 能够恢复自定义数据类型
  5. 能够恢复存储过程等对象的语法
  6. 能够导出到目标数据库
  7. 能够导出到SQL文件并生成导入脚本
  8. 支持多种字符集  包括:cp850、cp936、gb18030、utf8等
  9. 能够恢复未加密或者简单加密类型的数据
  10. 简单易用
  11. 限制:不支持AES加密的数据文件
请参考:研发成功了从Sybase SQL Anywhere的DB文件上恢复数据的工具
            SQL Anywhere数据库非常规恢复工具ReadASADB使用介绍

ReadASADB适用场景

各种误操作:

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

本工具的应用场景:

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