远程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:420388
CR Number:   420388
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   future
Fixed Version Build Resolution Date Closure Code (If Appropriate)
18 Apr 2006 Presently Not Targeted For Any Future Release Of This Product
Description
Request to specify destination file for auditing output other than the trans log



CR:420509
CR Number:   420509
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
05 May 2006 Presently Not Targeted For Any Future Release Of This Product
Description
insufficient SA cache at the point in time the propagated statement is being replayed on a given query node could cause query server to shutdown.



CR:421179
CR Number:   421179
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e01 17 Aug 2006 Fixed
12.6 e07 07 Aug 2006 Fixed
Description
In rare situations, a server could stop processing requests for a database when one user attempted to add/drop/alter a procedure while other users were calling procedures.
Target Version
 12.6 e07



CR:421643
CR Number:   421643
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
02 Mar 2006 Not a Bug
12.7 22 Mar 2006 Fixed
Description
IQ EXTRACT does not appear to work when triggered from an event.



CR:421915
CR Number:   421915
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.7 20 Mar 2006 Fixed
Description
The sp_iqrebuildindex procedure failed in hos_mutex_inline.h.



CR:422126
CR Number:   422126
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e07 05 Apr 2006 Fixed
12.7 05 Apr 2006 Fixed
Description
A query that contained conflicting range predicates in one of its subqueries caused a server failure.
Workaround Description
 To workaround the problem, the customer can either change the expression:

CONVERT(VARCHAR(6),DATEADD(MM,+0,'200409'+'01'),112) so that it evaluates

to a value > '200409'. Or the customer can disable the range predicate simplification

temporarily for this query by turning on dml_options1 = 2097152. In both ways, IQ

will execute the query in normal path without optimizing the range predicate mentioned

above.



CR:422235
CR Number:   422235
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 20 Apr 2006 Fixed
12.6 e07 09 May 2006 Fixed
12.6 e06.x 14 Jul 2006 Fixed
Description
A Sybase IQ server might fail with s_blockmap.cxx; 1295 error when

replaying a ALTER TABLE RENAME command propagated

from the write server to a query server.



CR:422335
CR Number:   422335
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   AIX
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e07 01 May 2006 Fixed
12.7 01 May 2006 Fixed
Description
Under rare circumstances, an IQ server became unresponsive with a JavaVM thread deadlock.
Workaround Description
 There is no real workaround. Not running any DDL while jvm's are running may reduce the situations.



CR:422502
CR Number:   422502
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 28 Apr 2006 Fixed
12.6 e07 28 Apr 2006 Fixed
Description
The following unusual scenario could result in server failure:

1) Connection 1 ran a stored procedure.

2) Connection 2 dropped a table used by the stored procedure in

Connection 1 and recreated it as a view.

3) Connection 1 tried to run the stored procedure again.
Review Status
 In an open session, if a proc refering to a table , then in the same session table is dropped without closing the session , and then subsequently later if a view is created with the same name, and then execute the proc in earlier session, the IQ server



CR:422624
CR Number:   422624
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
04 Apr 2006 Not a Bug
Description
IQ 12.6 on UNIX, when started from the "start_asiq" script, would load the ODBC driver specified in the "Driver=" config prop in the ".odbc.ini" but fail to load its supportive shared object unless one of the followings is true:

+ the path to the 3rd-party ODBC driver library is included in $LD_LIBRARY_PATH_64;

+ the IQ startup script is modified so that the path to the 3rd-party ODBC driver library is included in $LD_LIBRARY_PATH_64.
Workaround Description
 Either

ensure $LD_LIBRARY_PATH_64 in the IQ startup environment contains the path to the third-party ODBC library

Or

modify the IQ start up script "start_asiq" to insert "$ODBCHOME/lib" at the beginning of the environmental variable "$LD_LIBRARY_PATH_64", where "$ODBCHOME" is the path to the third-party ODBC Library that contains the ODBC driver and its supportive shared object files.



CR:423398
CR Number:   423398
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e07 01 Jun 2006 Fixed
Description
Under certain circumstances, a query with a deeply nested expression caused server failure and a stack trace error. Out of stack situations can be alleviated by increasing the -iqtss value.



CR:423745
CR Number:   423745
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e06.x 21 Apr 2006 Fixed
12.7 25 Apr 2006 Fixed
12.6 e07 14 Aug 2006 Fixed
Description
In some cases, server failure could result from attempting to get the GRAPHICAL_PLAN for a temporary table, whether using the function or DBISQL.



CR:424253
CR Number:   424253
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   AIX
Original Version:   12.6 e04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
23 Mar 2006 Duplicate
Description
Request for true single-user mode to restrict multiple connections to server



CR:424572
CR Number:   424572
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e01 14 Nov 2006 Fixed
Description
ALTER DATABASE UPGRADE may hang if an implicit or explicit checkpoint

is started while it is executing.
Workaround Description
 *** Thursday, December 21, 2006 1:17:25 PM *** maryc ***



Updated the workaround information to recommend doing an explicit CHECKPOINT before starting the ALTER DATABASE UPGRADE and setting both -gc and -gr to large values

based on the following feedback from SA engineering:



1. The -gc by itself only says when the next checkpoint should happen even

if there was no activity on the server. An auto checkpoint could happen

earlier if there was a lot pages being dirtied by the server. The -gr

switch controls how dirty things can get before the server feels the need

to force a checkpoint. Setting both -gc and -gr to large values can defer

the checkpoint longer.



2. Doing an explicit checkpoint before starting the ALTER DATABASE can make

sure things are clean before we start and also reset -gc timer if it is

about to fire.



CR:424750
CR Number:   424750
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 05 May 2006 Fixed
12.6 e07 07 May 2006 Fixed
Description
After running ALTER DATABASE UPGRADE to upgrade any Sybase IQ database to version 12.6 ESD#6, connections from an OLEDB application failed with "Procedure sa_oledb_getowner not found". The problem occurred when IQ server and client software were upgraded to 12.6 ESD 6 and OLEDB client applications were built with 12.6 ESD 6 OLEDB DLLs.
Workaround Description
 Run oleschem.sql by hand after executing ALTER DATABASE UPGRADE.



CR:425119
CR Number:   425119
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 25 Apr 2006 Fixed
Description
Loads, updates, and inserts should roll back immediately after an error is encountered and not wait for other parallel threads to complete processing.



CR:425124
CR Number:   425124
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e06 28 Mar 2006 Fixed
Description
Under certain circumstances, UPDATE commands

performed on char, varchar, or varbinary

columns with a defined width greater than 255

bytes or clob/blob columns whoses data widths are less

than 32768 bytes may cause FP index inconsistencies.

The inconsistencies may cause non-fatal s_blockmap

errors.



The issue is extremely data pattern dependent and is

much more likely to occur when updating more than 10,000

rows in a single update command.



The issue does NOT occur if any of the following are true:

- All rows in the column are updated in a single

update command.

- All rows being updated were originally all

NULL or zero-length strings

- All rows being updated are set to NULL or

zero-length strings.

- It is a single table update (no joins involved)

whose WHERE clause specifies single-column

predicates against constraints.



Once you have applied 12.6 ESD6.2, run the following

command to check the FP indexes:



sp_iqcheckdb 'check database indextype FP'



If no errors are reported, then your database was

unaffected by the issue and no further action is

required.



If inconsistent FP indexes are reported, run the

following command for each inconsistent index:



sp_iqcheckdb 'check index index_name'



A list of affected rowids will be printed in the

.iqmsg file preceded by the following line:



DBCC owner.table.indexname: # inconsistent ROWIDS

(where # is the number of rowids)



To resolve the inconsistencies, the following steps

must be repeated for each inconsistent FP index

reported. The sp_iqindex procedure can be used to

determine the column name that corresponds to the

FP indexname.



1) Add a new column to the table with the same

definition as the original column with the

inconsistent FP index. For example:



ALTER TABLE table_name ADD new_colname type

(width) NULL



2) Update the new column with the data from the

original column excluding all rows reported

reported in the .iqmsg file under 'inconsistent ROWIDS'.

For example:



UPDATE table_name SET new_colname =

original_colname WHERE ROWID(table_name)

NOT IN (list of inconsistent rowids)



3) Match each rowid reported in the 'inconsistent ROWIDS'

list to the table's primary key or, if no primary

key exists, use data values from other columns

that in combination uniquely identify the row

Use this information to determine the correct

column value from the original data source used

to populate the column. Update the new column

based on this information. For example:



UPDATE table_name SET new_colname = 'value' WHERE

ROWID(table_name) = rowid value



4) After step 3 is complete for each inconsistent

rowid reported, drop the original column and

rename the new column to the original name.

For example:



ALTER TABLE table_name DROP original_colname;

ALTER TABLE table_name RENAME new_colname

TO original_colname



If the original column was defined as NOT NULL,

alter the column to add the NOT NULL

specification. For example:



ALTER TABLE table_name MODIFY

original_colname NOT NULL



5) If the original column had WD or CMP indexes,

recreate them.



6) After steps 1 through 5 are completed for

each inconsistent FP index reported,

run sp_iqcheckdb 'check database indextype FP' a final

time to confirm that no errors are reported.



CR:425271
CR Number:   425271
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e02 16 Jan 2007 Fixed
Description
Using jCONNECT:ResultSetMetaData.getColumnTypeName would return a different result

on SA versus IQ tables. Both should return the base data type. (Duplicate of CR 442804.)



CR:425580
CR Number:   425580
Product Name:   IQ
Product Component:   IQ Component
Status:   Open
OS:   Linux Red Hat
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Request that for subqueries contained in view, alias_name cannot be defined as aggregate functions column.



CR:425619
CR Number:   425619
Product Name:   IQ
Product Component:   Install
Status:   Closed
OS:   Windows 2003
Original Version:   12.6 port
Fixed Version Build Resolution Date Closure Code (If Appropriate)
27 Mar 2006 Workaround
Description
Sometimes 32-bit installs/updates will not start on the Windows 64-bit platform if TMP or TEMP is set to C:\Windows\TEMP*. Resetting TEMP or TMP to "C:\temp" seems to resolve it. (C:\temp has to exist).



CR:425650
CR Number:   425650
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.6 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e06 31 Mar 2006 Fixed
Description
Under some circumstances, during an update

or incremental insert to a char, varchar, or

varbinary column wider than

255 bytes, the server may fail with a

"Destroying Locked Logical Buffer" error.



CR:425704
CR Number:   425704
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Unknown
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e07 18 May 2006 Fixed
12.7 18 May 2006 Fixed
Description
In very rare circumstances, the server might fail if multiple calls ran the same stored

procedure and the procedure contained statements of the form "SELECT ... INTO #temp ...".



CR:425921
CR Number:   425921
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e07 30 May 2006 Not reproducible with latest version of the product available as of Resolution Date
Description
Under special circumstances, running certain queries caused query server failure without a stack trace. Such queries now fail with the user error "Query stack size exceeded" without affecting other users.



CR:426096
CR Number:   426096
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e07 03 May 2006 Fixed
Description
The dblog utility returned an error because the libdbtsp9.sl.1 library was missing.



CR:426145
CR Number:   426145
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e07 25 Apr 2006 Fixed
12.7 21 Apr 2006 Fixed
Description
The sa_oledb_getowner function may return the error: -706 "Remote server does not have the ability to support this statement" on various sa_oledb_xxx procedures.
Workaround Description
 Change the decalation of the temp tbale so it will be created in the catalog .db by adding IN SYSTEM

declare local temporary table owners(

uid int not null,

user_name char(128),

primary key( uid )

)IN SYSTEM not transactional;



CR:426315
CR Number:   426315
Product Name:   IQ
Product Component:   Install
Status:   Closed
OS:   HP-UX
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e07 11 May 2006 Fixed
12.7 11 May 2006 Fixed
Description
Missing links for libiqtspt12.sl.1 & libiqtspt12_r.sl.1 caused an error running dblog.
Workaround Description
 cd $ASDIR/lib

ln -s libiqtspt12.sl.1 libiqtspt12.sl

ln -s libiqtspt12_r.sl.1 libiqtspt12_r.sl



CR:426797
CR Number:   426797
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Unknown
Original Version:   12.6 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e07 17 May 2006 Fixed
17 May 2006 Fixed
Description
It was possible, although very unlikely, for the server to fail, or for connections to deadlock and appear unresponsive, in the presence of concurrent DDL statements. For one of these failures to have occurred, these concurrent statements would generally have to refer to the same database object (i.e.,table, column or stored procedure, etc.), either directly or indirectly. A workaround is to serialize all DDL requests that references the same object.



CR:426979
CR Number:   426979
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows XP
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 05 May 2006 Fixed
12.6 e07 05 May 2006 Fixed
Description
The server might fail with the error "Cursor not updatable: OLAP function in select list" when the user ran a query that uses the dense_rank function and had a redundant alias in the OVER clause.



CR:427826
CR Number:   427826
Product Name:   IQ
Product Component:   Install
Status:   Closed
OS:   Windows NT
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e07 07 May 2006 Fixed
Description
On Windows systems where Sybase IQ 12.6 ESD 6 or ESD 6.2 was previously installed, an empty util_db.ini file might exist in ASIQ-12_6\win32, preventing users from connecting to the server using the utility database. The workaround was to edit the util_db.ini file and add username and pwd, for example: [UTILITY_DB]

UID=DBA

PWD=SQL.



CR:427864
CR Number:   427864
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 10 May 2006 Fixed
Description
writer crashed during manual sync of reader node



CR:427996
CR Number:   427996
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Windows XP
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10 Oct 2006 Presently Not Targeted For Any Future Release Of This Product
Description
Backup command needs to handle double forward slashes '//', the way ASE Does

This backup database command fails: backup database to 'c://temp//test.bk';

But works in ASE.



CR:429044
CR Number:   429044
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.7 30 May 2006 Fixed
Description
Using sp_iqcheckdb allocation mode could cause a server failure if duplicate block allocation errors were detected.



CR:429413
CR Number:   429413
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 15 May 2006 Fixed
Description
The NOEXEC database option may cause server failure when trying to get a query plan.



CR:429996
CR Number:   429996
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
13 Sep 2006 Presently Not Targeted For Any Future Release Of This Product
Description
IQ needs to be able on a Alter Table, modify the Data Type Like ASE does.
Workaround Description
 Customer is using this work around but they don't like it.



a) add new column to table with the desired datatype

b) run update to update new column with values from old column

c) drop old column



Any non-FP indexes that exist on the old column would have

to be dropped before one can do (c). Any indexes that had

existed on the old column would have recreated with the new

column if they are still needed.



CR:430107
CR Number:   430107
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 28 May 2006 Fixed
Description
Interactive SQL (dbisqlc) with the -q option fails when xp_cmdshell is called.



CR:430123
CR Number:   430123
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
23 Jan 2007 Not a Bug
Description
enhance manual management of dbpsaces in multiplex



CR:430192
CR Number:   430192
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e07 02 Jun 2006 Fixed
Description
A query that joined a view and table with an invalid rowid correlation

returned a SEGV error.



CR:430441
CR Number:   430441
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e01 06 Oct 2006 Fixed
Description
Even with the SQL Anywhere option TEMP_SPACE_LIMIT_CHECK = 'ON',

a Fatal Error could sometimes be returned when SA tmp (tmp_00000000)

filled the disk, depending on the cause of the temp space increase.



CR:430583
CR Number:   430583
Product Name:   IQ
Product Component:   Documentation
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 03 Jun 2006 Fixed
Description
Document max value for LIMIT in load table



CR:430854
CR Number:   430854
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 31 May 2006 Fixed
12.6 e07 02 Jun 2006 Fixed
Description
If a user had permissions on a view but no permissions on the underlying proxy table, then using the view inside an IF or CASE expression gave a "permission denied" error.



CR:431204
CR Number:   431204
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e01 28 Aug 2006 Fixed
15.0 21 Sep 2006 Fixed
Description
If the IQ database had a large schema with huge number of tables, columns and indexes, query server synchronization might be unresponsive and never complete. As a result, a user might not be able to create new query servers or synchronize existing ones.



CR:432176
CR Number:   432176
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.8 04 May 2007 Fixed
12.6 e10 27 Apr 2007 Fixed
12.7 e03 20 Apr 2007 Fixed
Description
When the database option ISOLATION_LEVEL is set to the non-default

value of 3, multiplex synchronize might cause a server Signal 11

failure.



CR:432417
CR Number:   432417
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e03 19 Apr 2007 Fixed
Description
SET OPTION PUBLIC.NON_KEYWORDS='exception' could prevent the IQ server from starting.
Workaround Description
 Only way to fix this is to edit the .db file with a hex editor.

Search for Non_keywords exception!  if the option contains only "exception"

Change this to a non reserved word and restart the iq database.Now it will start with out any problem.



CR:432757
CR Number:   432757
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   AIX
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 19 Jun 2006 Fixed
12.6 e07 19 Jun 2006 Fixed
Description
In very rare circumstances, the engine might fail if multiple calls ran the

same stored procedure for the first time after the database start and the procedure

was used in a select statement.



CR:432794
CR Number:   432794
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e01 31 Jul 2006 Fixed
Description
Each thread doing data conversion for an INSERT or UPDATE statement now posts 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". To write all of the data conversion warning messages to the .iqmsg file, use these statements: SET TEMPORARY OPTION CONVERSION_ERROR='OFF'; SET TEMPORARY OPTION DDL_OPTIONS2=8;



CR:432806
CR Number:   432806
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e01 18 Aug 2006 Fixed
Description
Catalog cache increased and was not released when SELECT resulted in a conversion error.



CR:433149
CR Number:   433149
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.7 e01 01 Sep 2006 Fixed
Description
The Sybase Central plug-in returned "table name not found" errors when listing tables and indexes in a database using the 1254TRK collation.
Workaround Description
 No valid work arrround for SC.



CR:433328
CR Number:   433328
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   HP-UX
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e06 22 Mar 2009 Fixed
12.7 e06 06 Mar 2009 Fixed
15.0 Beta2 Refresh 23 Dec 2008 Fixed
Description
When deleting a database using Sybase Central, an incorrect error message was being shown when the encryption key was incorrect. A correct error message is now being shown. Also the dialog box used to enter encryption key has an error. This has been corrected.



CR:433677
CR Number:   433677
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 e01 16 Jul 2006 Fixed
18 Jul 2006 Presently Not Targeted For Any Future Release Of This Product
Description
An outer join between a table and derived table gave incorrect results when the query contained a count, for example: SELECT col_3, COUNT(*)

FROM js1 LEFT OUTER JOIN( SELECT DISTINCT(col_1) AS col_1, 'R' AS col_3 FROM js2 ) AS t_js3 ON js1.col_1 = t_js3.col_1

GROUP BY t_js3.col_3.



CR:433678
CR Number:   433678
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e07 11 Jul 2006 Fixed
Description
On HP-UX 11.23 (RISC)systems, starting a Sybase IQ server with more than 4GB of memory failed with an error at hos_mem.cxx:348.
Workaround Description
 Change the start_asiq script to avoid the issue:



if ( "'$OS_TYPE'" != "HP-UX64" ) then

instead of:

if ( "'$OS_HW'" != "ia64" || "'$OS_TYPE'" != "HP-UX64" ) then



CR:434598
CR Number:   434598
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.7 e01 15 Aug 2006 Fixed
Description
A password change failed when IQ Login Management was enabled in Sybase Central.



CR:434600
CR Number:   434600
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.7 e01 11 Aug 2006 Fixed
Description
The index owner was unable to view indexes in Sybase Central.



CR:434639
CR Number:   434639
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e01 16 Aug 2006 Fixed
Description
The isqlShowMultipleResultSets option is now true by default.



CR:434643
CR Number:   434643
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e01 01 Aug 2006 Fixed
12.6 e07 01 Aug 2006 Fixed
Description
Command-line or batch dbisql truncated results when a column had an alias name shorter than its column size. The problem did not occur when running dbisql through a GUI.



CR:434849
CR Number:   434849
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
04 Jul 2006 Not a Bug
Description
Tainling blank is not ignored when CHAR or VARCHAR is specified to be LIKE conditions.
Workaround Description
 Trim a tailing balnk.

Or Wildcard(%) is added to end of LIKE conditions.



CR:434897
CR Number:   434897
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.7 e01 27 Jul 2006 Fixed
Description
Under rare circumstances, a non-fatal stack trace occurred at dfo_cOrderBy.cxx:758 when using aggregate functions.



CR:435388
CR Number:   435388
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e01 11 Sep 2006 Fixed
12.6 e07 02 Aug 2006 Fixed
Description
ALTER DATABASE UPGRADE failed with a "Database upgrade not possible" error when a DBA user created a table with the same name as an existing table owned by DBO.



CR:435618
CR Number:   435618
Product Name:   IQ
Product Component:   Install
Status:   Closed
OS:   Linux Red Hat
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e07 18 Aug 2006 Fixed
Description
Installing Sybase IQ 12.6 GA on Linux failed when sybinstall was unable to extract files with the .tgz suffix on RedHat 4.



CR:435644
CR Number:   435644
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 e01 01 Aug 2006 Failed
Description
Under some circumstances stddev function could return NULL results when the values in a group are the same.



CR:435660
CR Number:   435660
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e09 19 Jan 2007 Fixed
Description
A query executed through a TDS cursor could be rejected as not updatable

even if the cursor was not declared for update.



CR:435983
CR Number:   435983
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 15 Aug 2006 Fixed
12.6 e08 03 Nov 2006 Fixed
Description
Sybase IQ inserted a row in IQ_USER_LOGIN_INFO_TABLE for a new user incorrectly.



CR:435985
CR Number:   435985
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 e01 31 Jul 2006 Fixed
Description
Under certain circumstances, Sybase IQ ignored the Temp_Extract_Null_As_Empty setting.



CR:436161
CR Number:   436161
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e01 08 Sep 2006 Fixed
12.8 18 Jan 2007 Fixed
12.6 e08 16 Nov 2006 Fixed
Description
A server could become unresponsive while data was being relocated from readonly dbspaces (in other words, when running sp_iqrelocate).



CR:436264
CR Number:   436264
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Windows XP
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e06.x 21 Jul 2006 Fixed
12.6 e07 31 Jul 2006 Fixed
12.7 e01 27 Jul 2006 Fixed
Description
Creating a dbspace where the start_block exceeded the maximum integer size (2147483647) caused an ASA Error -131: Syntax error.



CR:436476
CR Number:   436476
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e08 17 Oct 2006 Fixed
12.7 e01 24 Sep 2006 Fixed
Description
A user was unable to drop a connection if the number of rows returned exceeded 2^31-1.



CR:436843
CR Number:   436843
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Unknown
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e01 01 Aug 2006 Fixed
Description
The statement "select '' /* empty string*/ into #temp" returned a syntax error.



CR:436945
CR Number:   436945
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   HP-UX
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e01 26 Sep 2006 Fixed
12.6 e08 31 Oct 2006 Fixed
Description
Column names in the first arm of a union are used to form the column names

for the derived table. If the column names of the derived table

happened to be the variable names in the subsequent arms, the query could not complete and the server failed.
Workaround Description
 By adding the alias colname for the column @wkday,

below re-written query runs well.



create variable @wkday char(8);

set @wkday = getdate();



Select x.*

From (select a, @wkday as colb from table1

Union all

select a, @wkday as colb from table2

) x ;



CR:437854
CR Number:   437854
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e01 28 Aug 2006 Fixed
Description
A query node's 'cardinality' value in system table SYS.SYSIQCOLUMN

might be incorrect if an index that maintains cardinality (e.g., LF or HG)

was created on the writer after the query node has been

created or synchronized.



CR:437944
CR Number:   437944
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e07
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e01 02 Aug 2006 Fixed
12.6 e07 31 Jul 2006 Fixed
Description
Under rare circumstances, a DELETE statement containing a

WHERE clause with the ROWID function could cause server failure.



CR:438088
CR Number:   438088
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)
26 Jul 2006 Duplicate
Description
Currently if a SC user clicks on a table, and selects the "Data" tab, a 'select * from ...' is issued, which can be a very long running query depending on the size of the table. In this case, a 'select * from' was kicked off on a table with 43 million rows, unnecessarily tying up system resources during an important production job. Perhaps Sybase Central should display the rowcount instead, and allow the user to select a number of rows to see a sampling of the data, say 15 rows by default, and which could be configurable.



CR:438350
CR Number:   438350
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e08 26 Sep 2006 Fixed
Description
When LC_ALL was set to a non-English language in the Sybase IQ installation scripts, the sybinstall and start_asiq utilities could fail.
Workaround Description
 [ Work-around ]

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



1) Add 'unset LC_ALL' in login shell.



....

unset LC_ALL

....



2) Modifing IQ shell like below



...

if [ -z "$LANG" ] # ... If not english, ignore (for now) ....

then TMP_LANG=""

else TMP_LANG="$LANG"; unset LANG LC_ALL

fi

...



CR:438398
CR Number:   438398
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e02 19 Dec 2006 Fixed
Description
Request for the TDS layer in ASA/IQ to send SPID in the DONECOUNT token as part of the LOGINACK.



CR:438505
CR Number:   438505
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e01 01 Sep 2006 Fixed
Description
A date conversion error occurred during ALTER DATABASE UPGRADE from 12.5 to 12.6 ESD 6

when the date_order option is set to 'DMY' in the 12.5 database.
Workaround Description
 Switch the DATE_ORDER option to 'MDY' just before executing ALTER DATABASE UPGRADE and

switch it back to your usual date_order when the upgrade finishes.



CR:438508
CR Number:   438508
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 25 Sep 2006 Fixed
12.6 e08 25 Sep 2006 Fixed
12.7 e01 03 Oct 2006 Fixed
12.7 e01 28 Sep 2006 Fixed
Description
IQ blocks were released slowly after dropping or truncating tables. This affected query performance in large installations due to fewer resources available to the query optimizer, resulting in increased use of temporary space, or, in some cases, leaked blocks.



CR:438535
CR Number:   438535
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 10 Aug 2008 Fixed
Description
Predicates expressions containing a COALESCE with a column argument and a constant inhibited query performance. This issue has been resolved to make better use of available indexes.



CR:438609
CR Number:   438609
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e02 06 Dec 2006 Fixed
12.6 e08 02 Nov 2006 Fixed
Description
If an insert-select query involves both remote and local tables and the table being inserted into is a view, then the query will fail with a "column not found" error.



CR:439233
CR Number:   439233
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows XP
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 Oct 2006 Not a Bug
Description
IQ server returns the specific wrong CP932 code to OpenClient application.



CR:439278
CR Number:   439278
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e01 26 Sep 2006 Fixed
12.7 e01 26 Sep 2006 Fixed
Description
A long query involving join indexes and a view failed with an exception at opt_TableNode.cxx:926.
Workaround Description
 drop the join indexes



CR:439353
CR Number:   439353
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11 Sep 2006 Presently Not Targeted For Any Future Release Of This Product
Description
Ability to specify column number in GROUP BY clause just like in ORDER BY



CR:439355
CR Number:   439355
Product Name:   IQ
Product Component:   Sybase Central
Status:   Closed
OS:   Unknown
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
30 Apr 2007 Fixed
Description
Sybase Central: IQ Plug-in is missing the web service folder.



CR:439357
CR Number:   439357
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11 Sep 2006 Presently Not Targeted For Any Future Release Of This Product
Description
Ability to supply sql var name in FROM, ORDER BY & GROUP BY clauses



CR:439552
CR Number:   439552
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e08 16 Oct 2006 Fixed
Description
A server could fail with a hos_mutex error after an out-of buffer error occurred.



CR:440259
CR Number:   440259
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows XP
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
04 Oct 2006 Not a Bug
Description
When 'select into' or 'insert select' is used in EXECUTE IMMEDIATE statement, local variable can be used in SQL statement. But this is wrong behavior. It is the correct behavior that local variable cannot be referred to from SQL statement.



CR:440317
CR Number:   440317
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.8 20 Dec 2006 Fixed
12.7 e02 20 Dec 2006 Fixed
Description
Bufman (s_buf) error reporting needs improvement.



CR:440326
CR Number:   440326
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.7 e01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e02 05 Feb 2007 Fixed
12.8 21 Feb 2007 Fixed
Description
A query involving an IS NULL or IS NOT NULL predicate evaluation

with ROWID could fail with an error from vpp_IsNull.



CR:440666
CR Number:   440666
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.7 e02 23 Feb 2007 Fixed
05 Jan 2007 Presently Not Targeted For Any Future Release Of This Product
12.8 01 May 2007 Fixed
Description
In queries containing a join where one of the join keys was a

value expression, and where that expression contained a column

which was used as a join key at a lower level join, then that

query could under some circumstances be incorrectly rejected

with a non-fatal internal error stating that the input to a join

operator was "not ordered as required".
Workaround Description
 The best work around is to disable the optimization which

is causing the problem by:

set temporary option dml_options3 = 8388608;

This option can, if necessary, be set public.



CR:440771
CR Number:   440771
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Windows NT
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e08 30 Oct 2006 Fixed
29 Nov 2006 Fixed
Description
Under rare circumstances, complex disjunctive search conditions in a query's WHERE clause could be incorrectly transformed by rewrite optimizations, yielding a search condition not equivalent to the original, and hence yielding unexpected results. It is difficult to completely characterize the types of search conditions affected by this problem. However, for the problem to occur, the search condition must contain so many disjunctive (OR) conditions that the condition exceeds a generous threshold of the maximal number of potential predicates to generate.



CR:440873
CR Number:   440873
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e02 19 Jan 2007 Fixed
Description
Delete on table reported error "Cursor is not updatable" for non-owner of the table even though that user had full access on the table, if the FORCE_UPDATABLE_CURSORS option was ON. By default this option is OFF.
Workaround Description
 Only option to make sure delete works for non owner of the table is to turn off option "Force_Updatble_Cursors", which is default value.



CR:441334
CR Number:   441334
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e01 19 Sep 2006 Fixed
Description
When one arm of a query's OR predicate was an IN predicate that referred to a column derived from a UNION ALL view, the IQ server might fail. The failure only occurred when the derived column's underlying base column had a one/two-byte FP or a LF/HG index.



CR:441457
CR Number:   441457
Product Name:   IQ
Product Component:   SA Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e08 09 Nov 2006 Fixed
Description
If multiple connections are open with uncommitted changes during a backup command,

upon restore from backup the uncommitted changes may not be rolled back for all connections.

This could produce catalog inconsistencies and subsequent server failures if a command

which creates or alters a table index was running during the backup.



CR:441846
CR Number:   441846
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e02 20 Nov 2006 Fixed
12.8 20 Nov 2006 Fixed
Description
The Index Advisor printed an unnecessary message in the iqmsg file

with advice to rebuild a column with MINIMIZE_STORAGE='ON' even

when MINIMIZE_STORAGE was ON and a 1 or 2 byte lookup FP index existed.



CR:441933
CR Number:   441933
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e01 02 Oct 2006 Fixed
12.6 e08 06 Oct 2006 Fixed
15.0 06 Oct 2006 Fixed
Description
A server could fail with a signal 11 error if RANK() was used inside a view or derived table and the view column containing the RANK() result was used in a predicate.
Workaround Description
 Work-Around ;



Using temp table instead of derivd tables.



Select bas_dt , rank() over (order by bas_dt) as num1

INTO # AA1

from tb_pu_om_dt_hldy

where bas_dt like '200608%'

and hldy_dsc='0'



Select bas_dt , rank() over (order by bas_dt) as num2

INTO #AA2

from tb_pu_om_dt_hldy

where bas_dt like '200609%'

and hldy_dsc='0' ;



Select a.*, b.*

from #AA1 a join #AA2

ON a.num1 = b.num2;



CR:441948
CR Number:   441948
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e07
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e08 20 Oct 2006 Fixed
12.7 e01 20 Oct 2006 Fixed
Description
If login management was enabled, a DML statement made by a

non-DBA connection could roll back despite the CHAINED option being set 'OFF'.
Workaround Description
 Do an explicit commit after the dml execution



CR:442348
CR Number:   442348
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e02 10 Nov 2006 Fixed
12.7 e02 12 Feb 2007 Fixed
12.8 12 Dec 2006 Fixed
12.6 e09 05 Jan 2007 Fixed
12.6 e09 16 Jan 2007 Fixed
12.6 future 10 Jan 2007 Fixed
12.6 e09 08 Jan 2007 Fixed
Description
The ASE date and time data types will be supported for INSERT LOCATION. Support was also added for the ASE data type unsigned smallint. An ASE unsigned smallint value can be inserted to a compatible IQ type.
Workaround Description
 Explicitly Convert datatype.



insert sample location 'SYBASE.pubs2' { select a,b,c from sample } ;

=>

insert sample location 'SYBASE.pubs2' { select q,b,Convert(datetime,c) from sample } ;



For ASE date to IQ date, the following workaround can be used:



insert sample location 'SYBASE.pubs2' { select q,b,convert(char(10),c,111) from sample}



CR:442730
CR Number:   442730
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.6 e07
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e08 31 Oct 2006 Fixed
12.7 e01 19 Oct 2006 Fixed
Other 03 Nov 2006 Fixed
Description
A query including an outer join and an invalid date expression could cause a server failure.
Workaround Description
 Currently it's not easy to consider work-around yet.

If exists, date values in query must be checked carefully

before executes it.



CR:442734
CR Number:   442734
Product Name:   IQ
Product Component:   Install
Status:   Closed
OS:   Unknown
Original Version:   12.7 future
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 10 Sep 2008 Fixed
Description
Request of IQ Client CD on any platform (32/64 bit)



CR:442766
CR Number:   442766
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Windows 2000
Original Version:   12.6 e07
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e08 08 Nov 2006 Fixed
12.7 e02 20 Nov 2006 Fixed
12.8 17 Jan 2007 Fixed
Description
A query involving a view with mixed union and union all joined with a table could cause a server failure.



CR:442841
CR Number:   442841
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   HP-UX
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6 e08 12 Oct 2006 Fixed
Description
Selecting an invalid view with multiple UNION expressions and a column name that doesn't exist in the base table could result in a server failure.



CR:442889
CR Number:   442889
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Solaris
Original Version:   12.6 e06.x
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.8 14 Nov 2006 Fixed
12.6 e08 14 Nov 2006 Fixed
12.7 e02 13 Dec 2006 Fixed
Description
Under certain conditions due to data skew, a HG Delete could choose a non-optimal algorithm.



CR:442913
CR Number:   442913
Product Name:   IQ
Product Component:   IQ Component
Status:   Closed
OS:   Unknown
Original Version:   12.7
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.7 e03 19 Jun 2007 Fixed
15.0 14 Oct 2008 Fixed
Description
Queries involving subqueries that contain joins plus a condition equating one of the subquery join condition columns to a constant could result, in some circumstances, in an IQ internal error.
Workaround Description
 The preferred workaround is to disable the optimizer's replacement

of a column by a constant that it was equated to in the WHERE clause:



set temporary option DML_Options5 = 524288;



This option can be set public, if necessary. Since this was a

new optimization in 12.7, the performance will simply revert back

to what was seen in 12.6.





--------------------------------------华丽的分割线-------------------------------------------------------------------------
之前就已经研发成功了能够从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等等。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------