Sybase数据库技术,数据库恢复

• 首页
• 关于
• 订阅
• 归档
• 留言
• 标签
• 免费ASE测试环境
• 镜像站
• 恢复工具

CR:645254

CR Number:   645254 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   AIX Original Version:   15.2 e01.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 e01.x 27 Oct 2010 Fixed 15.3 28 Oct 2010 Fixed Description Coordinator node failed while creating a procedure containing temporary table declarations. Workaround Description  1. Use only DBisql(C) 2. Define owner name "Owner.procedure_name"

CR:645552

CR Number:   645552 Product Name:   IQ Product Component:   SA Component Status:   Open OS:   Solaris Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description DBISQL cannot encode the Japanese character string set to the program argument correct. And this issue is reproduced only by Solaris.

CR:645997

CR Number:   645997 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Solaris Original Version:   12.7 e05.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 15 Dec 2010 Fixed 12.7 e11 15 Dec 2010 Fixed 15 Dec 2010 Fixed Description The order of results was incorrect, when the PARTITION BY and ORDER BY clauses had the same column in the case of DESC order for the DENSE_RANK function.

CR:646028

CR Number:   646028 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   HP-UX Original Version:   15.2 e01.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 10 Jan 2011 Fixed 18 Feb 2011 Presently Not Targeted For Any Future Release Of This Product 31 Mar 2011 Fixed Description select statement returns the internal error dfjo_Hash.cxx:1635.

CR:646311

CR Number:   646311 Product Name:   IQ Product Component:   Utility Status:   Closed OS:   Solaris Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 09 May 2011 Fixed Description The dbping -l option can be used to specify an ODBC driver or driver manager library. If the Unix driver manager included with SQL Anywhere (libdbodmX.so) was used as the argument for the dbping -l option, dbping returned the error ""FailedtoloadODBCdriver" . dbping has been fixed so that it can be used with libdbodmX.so.

CR:646497

CR Number:   646497 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Windows 2008 Original Version:   15.2 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description document the use of raw devices under windows properly

CR:646775

CR Number:   646775 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Red Hat Original Version:   15.1 e03 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 e03.x 10 Mar 2011 Fixed 17 Aug 2011 Fixed 23 Mar 2011 Presently Not Targeted For Any Future Release Of This Product 15.2 e03 31 Mar 2011 Fixed 27 Dec 2013 Fixed Description The server failed at s_dpByteFetch::Find, if a table was referenced in a query with an aggregate function (min, max) with a NOT EQUAL "<>" operator, such that the column involved was not a HG or FP index.

CR:646863

CR Number:   646863 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   12.7 e05.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e11 02 Feb 2011 Fixed Description Server failure was caused due to an issue in the handling of heap memory associated with procedures having Window functions. This has been fixed now.

CR:647068

CR Number:   647068 Product Name:   IQ Product Component:   Install Status:   Closed OS:   HP-UX Original Version:   15.2 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 e01 01 Dec 2010 Not reproducible with latest version of the product available as of Resolution Date Description 15.2 ESD1 Installer does not work with no previous database and lmp files (same as CR 621325) Customer platfrom HP-UX B.11.23 U on IA64 IQ 15.2 GA - installing ESD 1 Also repro'd on Windows x86 Once the installer is started and it asks for the location of the Installation, user sees the screen where the Installation wants to validate licenses of existing databases. If you select browse to locate you .lmp file being used successfully for the IQ 15.2 GA instalation and try use that you get and error... "There is not a valid license to associate with <the givem lmp file>. This upgrade is not covered by your maintenance agreement. You must acquire an appropriate license before you can continue." The skip check box is available but the customer feels this is not addressing the issue of why his 15.2 GA license files are not valid anymore for the purpose of the ESD installation Workaround Description  use skip check box ??

CR:647333

CR Number:   647333 Product Name:   IQ Product Component:   other Status:   Closed OS:   Linux Suse Original Version:   15.1 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 06 Dec 2012 Not a Bug Description Forwarding 'select @@version to ASE 15.0.3 from IQ 15.1 results in error 706 - Remote server does not have the ability to support this statement

CR:647462

CR Number:   647462 Product Name:   IQ Product Component:   Sybase Central Status:   Open OS:   Windows 2008 Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description The database creation wizard of IQ15.2 can change DBA user. This is the new feature of IQ15.2. IQ15.2 can change a DBA user's user name and password. However, when the autostart option is validated with the database creation wizard of Central, Central cannot log in to the created new database automatically.

CR:647809

CR Number:   647809 Product Name:   IQ Product Component:   other Status:   Closed OS:   Windows XP Original Version:   15.2 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 24 Nov 2010 Fixed Description Previously, if a JDBC application connected using jConnect, and if the application subsequently called DatabaseMetaData.getSchemas(), then the server would fail the request with the error "the 'FileVersion' property is no longer supported". This problem has now been fixed and the proper list of userids now gets returned to the application. Workaround Description  Run sp_asa11.sql in DBISQL and this will correct the jCONNECT stored procedures

CR:647834

CR Number:   647834 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Red Hat Original Version:   15.2 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.3 13 May 2013 Fixed Description Wrong result set when table has PK Workaround Description  Drop PK

CR:648004

CR Number:   648004 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Red Hat Original Version:   15.2 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 e02 11 Jan 2011 Fixed 15.3 12 Jan 2011 Fixed 15.2 e03 10 Mar 2011 Fixed Description Attempting to cancel a query to drop a local temporary table sometimes caused the server to fail.

CR:648159

CR Number:   648159 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Red Hat Original Version:   12.7 e06 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e11 04 Feb 2011 Fixed Description When perseat licensing was used, the error "Database server connection limit exceeded" may have been reported inappropriately. In order for this to have occurred, in addition to perseat licensing, the -gm server option or http connections to disabled databases must have also been used. If this problem occurred, the first time the error was reported was correct behavior, but after disconnecting connections, the error may have reported when it should not have.

CR:648167

CR Number:   648167 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   HP-UX Original Version:   12.7 future Fixed Version Build Resolution Date Closure Code (If Appropriate) Description The customer is frequently hitting an issue where the get transactions in a COMMITTED state holding a huge amount of version space. The transaction is not progressing to an APPLIED state so that the versions space can get releases because there is some connection stuck in the system that is holding a shared lock and has not committed. There is a convoluted way to do this manually with existing utilities etc (see below) but the customer would like a new Feature Request to create a new utility that would simplify this and make it easy to identify and kill problematic connections that cause this. PSE note on how this is achieved manually... If you look at the sp_iqtransaction output at the COMMITED transaction that you suspect is holding the resources. (BTW If the name and userid is (NULL) then the connection that this commit was for is probably no longer in the system). If you look at the CmtID that is the transaction ID for the commit action. You can use this along with the connection id to cross reference what it was doing in the IQ logs. To see if there are any connections holding locks preventing the commit from being applied and flushed out the system look for transactions with TxnID's that are earlier then the CmtID (i.e. smaller numbers). Use the ConnHandle information of these transactions to cross reference with sp_iqlocks to then determine what tables they are still holding locks still for and determine if any of these are tables involved in the committed transaction. The iqmsg and request level log will help in determining this too. From this you can work out which connections most likely have not themselves done a COMMIT and there for are still holding locks preventing the COMMITED transaction from above being applied and the versions released. In order to more easily identify this situation the transactions involved would of course needed to of been in the system a while so they are easy to identify from the current work load (long running transactions). In most cases it is usually very easy to spot the most likely connections causing the issue, i.e. they are usually the ones that have been in the system a long time but are not really doing anything. So if you monitor them over a short period you will see the locks for them are not being released, the commit id / transaction id's for them are not changing.

CR:648431

CR Number:   648431 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   AIX Original Version:   15.2 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.4 01 Jun 2011 Fixed 15.2 e00.x 10 Mar 2011 Fixed 23 Mar 2011 Presently Not Targeted For Any Future Release Of This Product 15.2 e03 30 Mar 2011 Fixed Description A query having a GROUP BY clause and Coalesce/Isnull clause failed. Workaround Description  If omit isnull() in alias a, it's ok to run. ==> Part of alias A (select 扁霖老, 惑淬磊流锅, max(惑淬流盔弊缝id) as 惑淬流盔弊缝id, sum(烹拳己傍备盒夯牢冉荐+烹拳己傍备盒啊练冉荐+烹拳己傍备盒扁鸥冉荐 +烹拳角菩备盒何犁吝冉荐+烹拳角菩备盒扁鸥冉荐+烹拳角菩备盒锅龋绝澜冉荐 +isnull(烹拳角菩备盒烹拳芭何冉荐,0)+isnull(烹拳角菩备盒烹拳抗距冉荐,0)) as 楷搬妮荐, sum(措惑利侩厚啦) as 措惑利侩厚啦 from PMS篮青惯脚惑淬盔老烹拳 where 扁霖老 between '20060901' and '20100314' group by 扁霖老, 惑淬磊流锅) as a ==> If omit isnull(), it's ok. sum(.....+烹拳角菩备盒烹拳芭何冉荐+ 烹拳角菩备盒烹拳抗距冉荐) as 楷搬妮荐,

CR:648455

CR Number:   648455 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   AIX Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Functional requirement for IQ to keep track of temp tables in its system tables like ASE.

CR:648598

CR Number:   648598 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16 Nov 2011 Fixed 06 Feb 2012 Fixed Description Long running update table query runs out of virtual memory after about 20 minutes in certain circumstances and crashes IQ server.

CR:648635

CR Number:   648635 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Red Hat Original Version:   15.2 e01.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 09 Mar 2011 Fixed 20 Apr 2011 Fixed 15.4 27 May 2011 Fixed Description IQ server was failing with non fatal internal error if select query has view and view definition has union of selects which has more than 13 nested ISNULL() functions in select list. Workaround Description  *** Wed Feb 02 2011 16:57:07 GMT+0530 (India Standard Time) *** manishas *** The workaround for this issue is as below, set temporary option dml_options5 = 1073741824 This will avoid CASE simplification associated with COALESCE implementation. This workaround should not impact the result of query. *** Wed Jan 12 2011 09:41:36 GMT+0530 (India Standard Time) *** manishas *** The workaround for this issue is as below, set temporary option DML_OPTIONS2 = 536870912 set temporary option DML_OPTIONS4 = 2097152 This will disable the split group by optimization which avoids the reinitialization of vectors for each node. Please note that it might have some performance degradation for queries having group by clause with Union All Operator.

CR:648731

CR Number:   648731 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   AIX Original Version:   15.2 e01.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 04 Oct 2011 Fixed Description SELECT query fails at dfo.cxx 9060 in 15.2 ESD 2 when merge join node gets wrongly ordered input from it's child. Workaround Description  set temporary option join_preference=-1

CR:648771

CR Number:   648771 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Original Version:   15.2 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 17 Nov 2010 Consult Complete Description 15.2 Is there an option to limit temp cache used by connection/operation?

CR:648773

CR Number:   648773 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Original Version:   15.2 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.4 08 Jul 2011 Added to user documentation Description 15.2 More info on error "Insufficient buffers for operation"

CR:648843

CR Number:   648843 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Red Hat Original Version:   15.2 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.4 09 Jun 2011 Fixed 13 Jul 2011 Fixed 13 Jun 2011 Fixed 03 Jan 2012 Consult Complete Description An issue with cursor handling in combination with the option setting CHAINED='OFF' could result in an Assertion failure "Page number on page does not match page requested". The issue was most likely to occur in Sybase central when clicking on "procedures and functions" folder. The issue has been fixed.

CR:649421

CR Number:   649421 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   AIX Original Version:   15.2 e01.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 e03 06 Jan 2011 Fixed Description If an expression containing an IN list was used in the SELECT list of a query and also the GROUP BY clause of the query, then it was possible for the query to fail with an error such as: INVALID_GROUP_SELECT 53003 -149L "Function or column reference to '%1' must also appear in a GROUP BY." ---- In order for this problem to occur, the IN list must have contained 20 or more elements, and the element type of the IN list must have been string literals, hex strings, or exact NUMERIC literal with a decimal point. ---- For example, this statement could generate this problem: select count(*), IF T.x IN ( '0', '1', '2', '3', '4', '5', '6', '7', '8', '9', '10', '11', '12', '13', '14', '15', '16', '17', '18', '19', '20', '21', '22', '23', '24', '25', '26', '27', '28', '29' ) THEN 1 ENDIF from T group by IF T.x IN ( '0', '1', '2', '3', '4', '5', '6', '7', '8', '9', '10', '11', '12', '13', '14', '15', '16', '17', '18', '19', '20', '21', '22', '23', '24', '25', '26', '27', '28', '29' ) THEN 1 ENDIF ---- This problem is fixed, but the expressions containing the IN lists must contain the elements in exactly the same order or the error is returned. For a server without the fix, a recommended workaround is to rewrite the query to compute the expression in a derived table. ---- For example: ---- select count(*), D.yyy from ( select T.*, IF T.x IN ( '0', '1', '2', '3', '4', '5', '6', '7', '8', '9', '10', '11', '12', '13', '14', '15', '16', '17', '18', '19', '20', '21', '22', '23', '24', '25', '26', '27', '28', '29' ) THEN 1 ENDIF as yyy from T ) as D group by D.yyy Workaround Description  1) Modified QUERY: -> delete T alias in group by clause Question-> even if customer use alias, why does problem query occur error? select... into.. from (select.. from.. where...) as T group by T.gigwan_code,T.customer_no,T.customer_gubun,T.budo_occur_date,T.budo_type_code,T.bujum_code,T.cancel_yn; ==> If i changed group by clause like below, the query run well. (That is,delete T alias in group by clause). select... into.. from (select.. from.. where...) as T group by gigwan_code,customer_no,customer_gubun,budo_occur_date,budo_type_code,bujum_code,cancel_yn; 2) Modified QUERY: -> decreased in value in the case..when clause. Question-> Why does below query ok ? select... into.. from (select...... ...... (case when bullang_cause_code in( '0101','0102','0103' ) then '51' when bullang_cause_code in( '0901','0902','0903','0904' ) then '53' when bullang_cause_code in( '0401','0402','0403','0404','0501','0502','0503' ) then '54' when bullang_cause_code in( '1003','1004','1006','1101','1201','1301','1403','1701','1901' ) then '55' when bullang_cause_code in( '0601','0602','0603' ) then '56' when bullang_cause_code in( '0604','0605','0606' ) then '57' when bullang_cause_code in( '0611','0612','0613' ) then '58' when bullang_cause_code in( '0701','0702','0703' ) then '59' when bullang_cause_code in( '0801' ) then '60' when bullang_cause_code in( '0802','0803','0804' ) then '61' end) as budo_type_code, from.. where...) as T group by ....

CR:649440

CR Number:   649440 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Linux Original Version:   15.2 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description creating HG indices in parallel is slower than in serial. Thread calculation of parallel create is also off by magnitudes

CR:649529

CR Number:   649529 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   AIX Original Version:   15.2 e01.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 21 Dec 2010 Fixed 15.3 22 Dec 2010 Fixed 15.2 e03 13 Jan 2011 Fixed Description A query sometimes returned incorrect result if it was processed in parallel, or if it was neither a correlated subquery nor an NLPD join.

CR:649533

CR Number:   649533 Product Name:   IQ Product Component:   Sybase Central Status:   Closed OS:   Windows XP Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 e02 16 Jan 2011 Fixed Description The 15.2 Sybase Central plug-in exhibited poor performance when displaying a list of tables or information of a single table when a database has around 100 tables and 30000 indexes. Performance degradation was caused by plug-ins repeated loading of the table or index information (metadata). This has been resolved.

CR:649576

CR Number:   649576 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   AIX Original Version:   15.2 e01.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 e01.x 03 Dec 2010 Fixed 04 Feb 2011 Fixed Description Queries with a self outer join having the same base table as "preserved" and "null-supplying sides" can return incorrect result sets.Conditions under this could happen are: - the outer join is of the form : T as T1 LEFT OUTER JOIN T as T2 ON(p) - the ON predicate p has only equijoins, and at least two equijoins - p is of the form : T1.c1 = T2.c1 and T1.c3 = T2.c2 - there exists an unique index on T < c1,c2>

CR:649595

CR Number:   649595 Product Name:   IQ Product Component:   SA Component Status:   Open OS:   Windows XP Original Version:   15.2 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Query ordering by computed column raises assertion 106104 in 15.2 ESD1

CR:649601

CR Number:   649601 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Windows 2003 Original Version:   15.2 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.3 01 Dec 2010 Not a Bug Description unable to add temp dbspace or dbfile in -iqnotemp mode after dropping last temp space

CR:649777

CR Number:   649777 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   AIX Original Version:   15.2 e01.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 e01.x 22 Dec 2010 Fixed 15.3 21 Feb 2011 Fixed 15.2 e02.x 10 Feb 2011 Fixed 15.2 e03 31 Mar 2011 Fixed Description Under the following circumstances an outer join which was processed using the hash based algorithm returned incorrect results: 1. The outer table of the outer join had unique multi-column HG (MCHG) index; 2. Part of the columns of the MCHG index were used as EQ-join condition and the rest of the columns were used as local comparison predicates; 3. The comparison predicates were comparing columns (used in the MCHG index) to constants. All columns in the MCHG index MUST BE used in the query. Workaround Description  1) rewrite 2) Set Temporary Option join_preference = '-4' ;

CR:649858

CR Number:   649858 Product Name:   IQ Product Component:   SA Component Status:   Closed OS:   Solaris Original Version:   12.7 e10.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e12 04 Feb 2011 Fixed Description In very rare cases, the server asserts with assertion error 102300 "File associated with given page id is invalid or not open" if request level debugging is enabled, query plan logging is enabled, and schema changes exist. This has been fixed. Workaround: turn off plan caching (option Max_plans_cached = 0) or turn off plan logging (switch -zr without "plan" and "all"). Workaround Description  if the customer sets MAX_PLANS_CACHED=0 they are not able to recreate the problem (so they are using this as a work around).

CR:649959

CR Number:   649959 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   HP-UX Original Version:   12.7 e08 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description IQ Store full at recovery, no connection possible. How to add a new dbspace?

CR:650125

CR Number:   650125 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Unknown Original Version:   15.2 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 07 Nov 2013 Duplicate Description 15.x CASE expr IS NOT NULL return wrong result

CR:650418

CR Number:   650418 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Windows 2008 Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description sp_iqtable does not support over 128 bytes of remarks. Workaround Description  Please chage "STRING_RTRUNCATION" option to OFF.

CR:650421

CR Number:   650421 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   AIX Original Version:   15.2 e01.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 09 Mar 2011 Presently Not Targeted For Any Future Release Of This Product 08 Mar 2011 Fixed 15.3 23 Mar 2011 Fixed 08 Mar 2011 Fixed 05 Apr 2011 Fixed Description Incorrect & different count(*) result may be returned when a query uses sort merge join with parallel order by retrievers and redundant ordering columns get eliminated from the Order By nodes Workaround Description  If i set "Max_Query_Parallelism = 1" option, count(*) result value is always same. If Join_Preference=5 option, it works also.

CR:650457

CR Number:   650457 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Solaris Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description LOAD TABLE cannot insert a blank character string in a VARCHAR column.

CR:650822

CR Number:   650822 Product Name:   IQ Product Component:   SA Component Status:   Open OS:   Unknown Original Version:   15.2 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description 15.2 Many CASE WHEN in main SELECT and derived table take long parsing time

CR:651158

CR Number:   651158 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Red Hat Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Jan 2011 Workaround Description Joining a small ASE table to a large IQ table via a proxy table in IQ is slow

CR:651197

CR Number:   651197 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 23 May 2011 Not a Bug Description ceiling function returns incorrect result on user table, works correctly on system tables

CR:651272

CR Number:   651272 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   HP-UX Original Version:   12.7 e08.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 09 Jan 2011 Fixed Description The issue was caused due to a race condition between disconnect and getting a connection property. This has been fixed now.

CR:651318

CR Number:   651318 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Linux Red Hat Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description create unique clustered index against an IQ table really creates a unique HG index.

CR:651331

CR Number:   651331 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Linux Red Hat Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description IQ does not error on 'exec <function>' or 'call <function>

CR:651808

CR Number:   651808 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   AIX Original Version:   15.2 e01.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 10 Jan 2011 Fixed 13 Jan 2011 Fixed 31 Mar 2011 Fixed Description A Query having nested blocks with case and group by caluses was giving different results on each run. This issue could occur mostly when the outer query blocks's CASE clause would depend on the evaluation of the inner query block's CASE clause. eg. When the query pattern is somewhat like this: SELECT B.col1 as col1 FROM ( SELECT CASE WHEN A.col2 THEN ... ... END AS col 1 FROM ( SELECT CASE WHEN col3 THEN ... ... END AS col2 FROM ... GROUP BY ... ) A GROUP BY ... ) B Workaround Description  From my test, the query always returned correct result set under one of below conditions. 1) dml_options8=8; 2) set temporary option join_preference = '-4'; 3) set temporary option Max_Query_Parallelism = 1; 4) Modified Query like below CASE WHEN A.MDR <= 0.015 THEN '021' WHEN A.MDR > 0.015 and A.MDR < 0.020 THEN '022' WHEN A.MDR = 0.020 THEN '023' WHEN A.MDR > 0.020 and A.MDR <= 0.027 THEN '024' WHEN A.MDR > 0.027 and A.MDR <= 0.033 THEN '025' ELSE '026' END AS

CR:652287

CR Number:   652287 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   15.1 e03.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 e03.x 23 Mar 2011 Fixed 15.2 e02.x 22 Jun 2011 Fixed 16 Aug 2011 Consult Complete Description In heavy load scenarios server become unresponsive due to contention between FL lock and busy buffers. This problem has been fixed now.

CR:652379

CR Number:   652379 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Dec 2012 Fixed Description If a query used the user_name() or suser_name() builtin function, then the described length of the column was LONG VARCHAR, even though the value would be at most 128 bytes. This has been corrected so that the described type is now VARCHAR(128). Any materialized views that use these builtins in the select list should be rebuilt after this change. Workaround Description  use CAST to cast to a different datatype. e.g. SELECT cast(suser_name() as varchar(256)) as audit_user into #temp5 from atime;

CR:652550

CR Number:   652550 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   AIX Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 07 Nov 2013 Duplicate Description single CPU causes single thread pool creation resulting in incorrect result set IQ 15.2 ESD2 (and IQ 15.1 ESDx) on RS6000 AIX 64bit running the following query.. SELECT V_traffic_TIME.WEEK_NUMBER_OF_YEAR, V_traffic_TIME.DATE_KEY_DATE, COUNT (Distinct ( convert(char(5),SYBMDM.V_TRAFFIC_FACT.TIME_SID)+ ': ' + SYBMDM.V_TRAFFIC_FACT.WEBID + ': ' + convert(varchar,SYBMDM.V_TRAFFIC_FACT.VISIT_ID))) FROM sybmdm.V_TIME_DIM V_traffic_TIME, SYBMDM.V_TRAFFIC_FACT WHERE (V_traffic_TIME.TIME_SID=SYBMDM.V_TRAFFIC_FACT.TIME_SID ) AND V_traffic_TIME.DATE_KEY_DATE BETWEEN '2010-08-21' AND '2010-10-04' GROUP BY V_traffic_TIME.WEEK_NUMBER_OF_YEAR, V_traffic_TIME.DATE_KEY_DATE If run this on a box with a single CPU on IQ 15.1 ESDx (this can also be simulated by specifying -iqnumbercpus = 1) the query returns 0 rows and the Threads info in the query plans show the query had only a single thread used in a single pool. The left hand side of the hash push down should produce about 39 million rows , it produces 0 rows. If you run the same query with two or more CPUs the query runs fine and produces a expected result set of 45 row. The Threads info in the query plan shows multiple thread pools set up with multiple threads used. Also NOTE !!! .... using IQ 15.2 ESD1 the problem goes away (i.e. the query run in a single CPU configured environment runs fine with multiple thread pools and threads set up.) HOWEVER IQ 15.2 ESD2 regresses to the failure again. Workaround Description  *** Wed Feb 09 2011 11:49:28 GMT+0530 (India Standard Time) *** manishas *** The workaround for this issue is setting DML_OPTIONS4 to 128, use statement below for same. set temporary option DML_OPTIONS4 = 128 <OLD LOGS> Make sure IQ runs with 2 or more CPU's

CR:652732

CR Number:   652732 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Unknown Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11 Mar 2011 Fixed 16 Mar 2011 Fixed 31 Mar 2011 Fixed Description Query returns wrong results when it has a correlated subquery having a number of conjunctions of disjunctions of predicates. This happens when some predicates in the disjunctions are invariant (e.g. table.column = 4)

CR:652828

CR Number:   652828 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Red Hat Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12 Jan 2011 Not a Bug Description sp_iqaddlogin on IQ15.x can not use '&' as login password Workaround Description  Please using "CREATE USER" statement.

CR:652929

CR Number:   652929 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Windows 2003 Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 23 Mar 2011 Fixed 23 Mar 2011 Fixed Description When using the ADO.NET driver to connect to older versions of Sybase IQ (12.x and under) the driver would raise an exception. This has now been fixed.

CR:653057

CR Number:   653057 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Unknown Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.3 29 Mar 2011 Added to user documentation Description Only period is supported as decimal separator.

CR:653234

CR Number:   653234 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   15.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.3 01 Feb 2011 Fixed Description On rare occasions, the sql function "NEWID" may return a duplicate value.

CR:653585

CR Number:   653585 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11 Mar 2011 Duplicate 15.2 e02.x 11 Mar 2011 Fixed Description IQ server was failing if query having group by cause and Coalesce/Isnull clause. Workaround Description  *** Wed Feb 02 2011 16:57:07 GMT+0530 (India Standard Time) *** manishas *** The workaround for this issue is as below, set temporary option dml_options5 = 1073741824 This will avoid CASE simplification associated with COALESCE implementation. This workaround should not impact the result of query.

CR:654023

CR Number:   654023 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Windows 2008 Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 20 Jan 2011 Duplicate Description The Sybase IQ server could fail when executing a query involving the sort merge push-down algorithm.

CR:654840

CR Number:   654840 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Windows 2008 Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description iqsrv15.exe does not have a message resource for event viewer.

CR:655553

CR Number:   655553 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   15.2 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 27 Apr 2012 Duplicate Description Data exception - operation resulted in division by zero when no rows are returned select 0/0 from iqdummy where 1=2

CR:655737

CR Number:   655737 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Linux Red Hat Original Version:   15.2 future Fixed Version Build Resolution Date Closure Code (If Appropriate) Description This is follow on Feature Request steaming from the investigation done in CR 644807 and case 11629524. This is an issue to do with customer trying to do a partial width insert on a table which contains columns with DEFAULT VALUE column definitions. This causes errors like... >> Could not execute statement. >> In table 't', the START ROW ID value (1) must be greater than 3. Data >> has already been inserted at this location. >> -- (db_insrt.cxx 1855) >> SQLCODE=-1000132, ODBC 3 State="HY000" >> Line 1, column 1 SQLCODE -1002001 error in s_dpins.cxx:1349 "Data has already been inserted into index DBA.t.ASIQ_IDX_T943_C3_FP for row 1." As concluded in CR 644807 this is expected behavior and the correct way to do this is either remove the DEFAULTS constraint or set DEFAULTS OFF on the load. HOWEVER the error message in these situations is confusing and misleading. Customer would like a feature request to enhance this messaging to be more meaningful and report something like... "you cannot perform partial loads in tables with column defaults, drop the default to load the data and then add it again"

CR:655755

CR Number:   655755 Product Name:   IQ Product Component:   Documentation Status:   Closed OS:   Linux Red Hat Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 30 Aug 2011 Insufficient priority to fix Description Please refer to CR 652713 raised for this issue to do with Rowid not reused unless NULL is explicitly defined . IQ will only fill in unused rowids and reuse space during "full width" inserts or loads (so NULL columns must also be specified). This issue can cause an excessive amount of space wastage / fragmentation, however this is working as designed. Currently in development are improvements to column stores and compression which will help alleviate this problem. However the documentation describing this behavior and the issues described in CR 652713 needs to be improved / clarified. In particular the documentation regarding partial width inserts are analogous to APPEND_LOAD='ON' in terms of rowid and space behavior needs to be made clear and that APPEND_LOAD='OFF' will only reuses the first available row IDs and space from deleted rows on full width inserts. If there are columns defined with NULLS these must also be included in the load or insert statement. Also the documentation on Controlling Index fragmentation on page 88 of the Performance Tuning guide (IQ 15.2) (Chpt. 4 Managing Database Size and Structure) needs to be enhanced with this information and the aspects covered in CR 652713.

CR:656232

CR Number:   656232 Product Name:   IQ Product Component:   SA Component Status:   Closed OS:   Unknown Original Version:   15.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 01 Feb 2011 Fixed Description The server could fail when running queries containing 2000 or more OR-ed equality conditions over a view that contains a many-arm UNION. This has been fixed.

CR:656268

CR Number:   656268 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 09 Dec 2013 Not reproducible with latest version of the product available as of Resolution Date Description optimizer makes bad aggregation choice with a GROUP BY - grouped leaf used Version: 15.2.0.5615/101123/P/ESD 2/Enterprise Linux64 - IBM pSeries 2.4.21-32.0.1.EL/64bit Running the following simple select with GROUP BY is taking over 4 minutes and is resolved in the leaf node grouping using the HG index. The query plan shows this is being single threaded. select count(*) from ( SELECT Col_A FROM repro_grouped_leaf GROUP BY Col_A HAVING 1 < COUNT(*) ) D Forcing aggregation_preference = 1 (prefer sort) and the query takes 30 seconds and it is resolved sorting the the data from the base table with 126 thread in parallel.

CR:656995

CR Number:   656995 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Unknown Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.4 e02.x 12 Oct 2012 Fixed Description Feature request for LOAD TABLE command to allow loading from compressed files. LOAD TABLE has been enhanced to load from compressed files. The compressed file-type is recognozed by the file extension.

CR:657029

CR Number:   657029 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11 Mar 2011 Fixed 15.3 16 Mar 2011 Fixed 23 Mar 2011 Fixed 15.2 e03 31 Mar 2011 Fixed Description The IQ Server generated an incorrect result, if a query plan had "Index BitMap Disjunction(parallel)" as the execution method for a condition with an IN LIST clause.

CR:657160

CR Number:   657160 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Windows 2003 Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 e02.x 10 Mar 2011 Fixed 31 Mar 2011 Fixed 15.4 e03 31 Mar 2011 Fixed Description A SELECT query may throw exception "Non-Fatal IQ Internal Error" from dfo.cxx. "Internal error at node: # Can not evaluate expression" when the query has an outer join node and scalar correlated subquery. Workaround Description  reorder the inner join

CR:657332

CR Number:   657332 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Red Hat Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 e03.x 09 Feb 2012 Fixed 15.4 09 Feb 2012 Fixed 16.0 03 Apr 2012 Fixed Description IQ server aborts at st_server.cxx:1409 while generating graphical plan with statistics level 3 for DML statements like SELECT .. INTO, UPDATE in IQ 15.2 ESD 2. Workaround Description  set option QUERY_PLAN_TEXT_CACHING = 'on'

CR:657663

CR Number:   657663 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 e02.x 10 Mar 2011 Fixed 15.4 01 Jun 2011 Fixed 23 Mar 2011 Presently Not Targeted For Any Future Release Of This Product 15.2 e03 30 Mar 2011 Fixed Description A query with a GROUP BY ORDER BY DESC clause failed with "Internal error at GROUP BY node."

CR:657690

CR Number:   657690 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Red Hat Original Version:   12.7 e05.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e05.x 08 Apr 2011 Fixed 12.7 e12 12 Apr 2011 Fixed 15.3 e01 20 Apr 2011 Fixed 16.0 10 May 2011 Fixed Description A server failure may occur at s_blockmap::RegisterPhysicalBlockId() file s_blockmap.cxx line 2440. This failure may occur when trying to write a block with block id greater than 4GB. This requires a database large enough to have dbspaces with physical block numbers greater than 4GB.

CR:657810

CR Number:   657810 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10 Mar 2011 Fixed 15.3 e00.x 30 Sep 2011 Fixed 15.2 e03 31 Mar 2011 Fixed 15.4 27 May 2011 Fixed Description The IQ server failed with an error, if a select query had more than 20 decimal elements in the IN LIST clause.

CR:657962

CR Number:   657962 Product Name:   IQ Product Component:   SA Component Status:   Open OS:   Unknown Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description -

CR:657996

CR Number:   657996 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 20 May 2011 Fixed Description In attempting to connect to a Cluster Edition instance and it is unreachable, secondary or alternate instances (dataservers) are attempted, but a failure is returned to the IQ user and the connection is not established. Workaround Description  Use asejdbc class for the remote servers: e.g. create server asejdbcTest class 'asejdbc' using 'paisley:11101,paisley:11102/master?request_ha_session=true&secondary_server_hostport=paisley:11102'

CR:658446

CR Number:   658446 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Red Hat Original Version:   15.2 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.4 18 May 2011 Fixed 16.0 23 May 2011 Fixed 15.2 e03 23 May 2011 Fixed 15.3 e00.x 21 Jun 2011 Fixed 15.2 e00.x 07 Jul 2011 Fixed Description LOAD TABLE incorrectly reported a data conversion error.

CR:658660

CR Number:   658660 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Red Hat Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 e03 31 Mar 2011 Fixed 17 Mar 2011 Fixed 15.1 e03.x 10 Mar 2011 Fixed 15.2 e02.x 11 Mar 2011 Fixed 15.4 01 Jul 2011 Fixed Description A SELECT query sometimes returned an incorrect number (fewer) of rows when all of these conditions were true: 1. Parallel sort-merge join was chosen as join algorithm; 2. "Parallel Output Order By" nodes were child nodes of a sort-merge join; 3. The IQ optimizer performed optimization on ordering expressions. Workaround Description  JPMorgan can avoid this problem by setting join_preference=-1 ( 'J:-1') to avoid sort-merge however this increases the query response time considerably. In the test example query from 2 seconds to 25 seconds.

CR:659343

CR Number:   659343 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   15.3 beta Fixed Version Build Resolution Date Closure Code (If Appropriate) 14 Apr 2011 Fixed Description When executing a distributed query in IQ 15.3 with the QUERY_PLAN_AS_HTML option set, HTML query plans are created for each fragment executed on each server in the MPX in addition to the full HTML query plan for the leader node. If those HTML files are placed into a common directory, it is impossible to determine which server the query plan is from as the plans do not include the name of the server that executed the query.

CR:659543

CR Number:   659543 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   AIX Original Version:   15.2 e01.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 e03.x 24 Dec 2012 Fixed 15.4 24 Dec 2012 Fixed 15.3 24 Dec 2012 Fixed 16.0 17 Dec 2012 Fixed 15.4 e01 24 Dec 2012 Fixed 15.4 e02.x 27 Feb 2014 Fixed 15.2 e02.x 04 Mar 2014 Fixed Description Table versions which are opened by read-only HOLD cursors may be incorrectly dropped during multiplex version collection (ev_iqmpxstatus). Later the connection holding the cursor may see random crashes during DestroyCursor. This problem only affects in multiplex setup and secondary nodes only. Workaround Description  No

CR:659720

CR Number:   659720 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Red Hat Original Version:   15.3 beta Fixed Version Build Resolution Date Closure Code (If Appropriate) 26 Feb 2011 Fixed Description Signal 11 raise from s_LOBCursor when executing UDF

CR:660003

CR Number:   660003 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Solaris Original Version:   15.2 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description -

CR:661486

CR Number:   661486 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Solaris Original Version:   15.2 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Query selects HJ instead of sort-merge and performs very poorly

CR:661531

CR Number:   661531 Product Name:   Sybase IQ ETL Product Component:   Docs Status:   Closed OS:   Unknown Original Version:   Denali Fixed Version Build Resolution Date Closure Code (If Appropriate) 03 May 2011 Added to user documentation Description We should describe for configure.sh in manuals (Installation Guide or User's Guide).

CR:661686

CR Number:   661686 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Solaris Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description error msg for load table when it fails with duplicate column is not very descriptive, Could not execute statement. Duplicate insert column SQL CODE=-637, ODBC 3 State= "42000" Line 1, column 1 it should include line number and column name as well, as is for syntax error: Could not execute statement. Syntax error near 'Appropriate_Trade_Types' on line 77 SQLCODE=-131, ODBC 3 State="42000" Line 1, column 1

CR:661809

CR Number:   661809 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   12.7 e05.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.4 e01 22 Nov 2011 Fixed Description sp_iqdbspaceinfo and sp_iqindexinfo fail with error Exception Thrown from db_iqutility.cxx:4893, Err# 14 O/S Err#: 0, ErrID: 2071 (s_dbextexception); SQLCode: -1006002, SQLState: 'QBA02', Severity: 23 IQ Internal error. Please report this to Sybase IQ support. db_iqutility.cxx

CR:662657

CR Number:   662657 Product Name:   IQ Product Component:   Documentation Status:   Closed OS:   Unknown Original Version:   15.3 beta Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.3 06 Apr 2011 Added to user documentation Description In description of the following "CREATE DATABASE", the maximum of IQ SIZE is written to be 128GB. However, the maximum of IQ SIZE is extended to 4TB.

CR:662704

CR Number:   662704 Product Name:   IQ Product Component:   Utility Status:   Closed OS:   Solaris Original Version:   15.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 28 Mar 2014 Insufficient priority to fix 15 Mar 2013 Presently Not Targeted For Any Future Release Of This Product Description CR#410218 fixed the stop_asiq script. This is the issue as which a stop_asiq script does not show 15 or more PID. However, the actually fixed details are not correct. This mistake was inherited IQ15.3. A stop_iq script ignores 16 or less PID. Workaround Description  Please change a stop_iq script. 318 if ( $2 < 16 || index( $0,"<defunct>" ) > 1 ) next; to 318 if ( $2 < 15 || index( $0,"<defunct>" ) > 1 ) next;

CR:662737

CR Number:   662737 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Unknown Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description -

CR:662892

CR Number:   662892 Product Name:   IQ Product Component:   Documentation Status:   Closed OS:   Unknown Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16 May 2011 Added to user documentation Description -

CR:662926

CR Number:   662926 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Linux Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Problem = when using a database created with collation ISO1LATIN1, a select with a GROUP BY on columns containing special extended characters returns an incorrect result. This only happens if there is a LF index created on the column and only after a certain number of rows have been inserted. The data in the table is fine , just the result returned by the SELECT is incorrect.

CR:663747

CR Number:   663747 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Red Hat Original Version:   12.7 e09 Fixed Version Build Resolution Date Closure Code (If Appropriate) 08 Apr 2011 Presently Not Targeted For Any Future Release Of This Product Description sp_iqcheckdb can not check join indexes

CR:664053

CR Number:   664053 Product Name:   IQ Product Component:   SA Component Status:   Open OS:   Linux Red Hat Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description "-ot" server option was added to IQ 15.x. However, IQ server ignores "-ot" server option.

CR:664276

CR Number:   664276 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Linux Red Hat Original Version:   15.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Certification of Veritas Volume Manager, Cluster Server and Volume Replicator on raw devices for IQ simplex and Multiplex.

CR:664721

CR Number:   664721 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Linux Red Hat Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description IQ Server will make a fragment the packet which sends to a client, when character set conversion is valid. Workaround Description  Please try change of the next two connection parameters. However, change of Charset may garbled a multi-byte character. 1. Charset=none 2. PrefetchRows=1000

CR:664993

CR Number:   664993 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   HP-UX Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 08 Jul 2011 Presently Not Targeted For Any Future Release Of This Product 15.4 22 Jun 2011 Fixed 15.2 e03.x 08 Jul 2011 Fixed Description A query on two tables having multi-column HG indexes on a different set of columns which does sort merge join on the leading column in both indexes, gives non-fatal failure. This failure occurs in the presence of shadow query parallelism and OrderedLeafs.

CR:665099

CR Number:   665099 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   HP-UX Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 08 Jul 2011 Presently Not Targeted For Any Future Release Of This Product 15.4 22 Jun 2011 Fixed 08 Jul 2011 Fixed Description IQ gives non-fatal internal failure for a query which has a where clause containing a coalesce expression which is aggregated as part of an inner query. Workaround Description  If group by column has isnull() column, "dfo.cxx:9772 " error occurred. As below's modified sql, if remarked the isnull() column, and the query was ok. Below SQL is ok in IQ12.7. I suggested customer to modify the query as w/r. select count(1) from ( select '20110331' as gijun_date -- ,isnull(b.CUST_NO,0) as customer_number ,b.CUST_NO as customer_number ,a.RNNO as real_name_number ,0 as total_delay_cnt ,case when a.CRIN_ENR_RSCD in ('1101','1301') then a.CRIN_ENR_RSCD else '' end as defect_code ,count(*) as defect_cnt ,0 as money_delay_cnt ,0 as interest_delay_cnt from TB_SOR_LOE_CDJI_DPC_DL a ,OT_DWA_INTG_CUST_BC b where isnull(RLS_DT,'') = '' and b.STD_DT = '20110331' and b.NFFC_UNN_DSCD = '2' and b.CUST_INF_STCD = '1' and b.CUST_AVL_CD = '1' and a.RNNO *= b.CUST_RNNO group by gijun_date,customer_number,real_name_number,defect_code ) x -- where x.customer_number = 0 ; where x.customer_number is NULL ;

CR:665249

CR Number:   665249 Product Name:   IQ Product Component:   Sybase Central Status:   Closed OS:   Windows XP Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 27 Apr 2011 Consult Complete Description The server message viewer feature was added to entral from Sybase IQ 15.x. This feature shows the result which called the sa_server_messages system procedure at a fixed period on the window of Central. However, the method of setting this feature to disable does not exist. Refresh rate = when 0 is set up, sa_server_messages is called at intervals of 1 second.

CR:665254

CR Number:   665254 Product Name:   IQ Product Component:   Sybase Central Status:   Open OS:   Windows XP Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Refresh Rate=999999999 cause the internal error of Central.

CR:665482

CR Number:   665482 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 e03.x 12 Sep 2011 Fixed Description SELECT query fails with non fatal error at dfo_Join.cxx:288 in 15.2 ESD 2.6 when Nested Loop Pushdown Join algorithm is used. Workaround Description  set Early_Predicate_Execution = 'OFF'

CR:665510

CR Number:   665510 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Red Hat Original Version:   15.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.4 26 May 2011 Fixed Description Full Virtual Encapsulated backup of READONLY dbspace will hang the client running it and prevent checkpoints being done. 1. Virtual backup _should_ be used with ALL type backup alone. There is no value in using it for either RW or RO only backups. 2.The current CR is about virtual back RO DBSPACE hang. This should be returning an error that a selective backup of RO DBSPACE isn't supported/implemented. 3. Documentation need to change to reflex this.

CR:665764

CR Number:   665764 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Original Version:   15.2 e02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11 Apr 2011 Duplicate Description Crash on select graphical_plan( 'SELECT * into #tmp FROM iq_table')

CR:666196

CR Number:   666196 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Red Hat Original Version:   15.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.4 09 May 2011 Fixed 15.2 e02.x 06 May 2011 Fixed 15.2 e03 09 May 2011 Fixed Description The new option CORE_OPTIONS67 sets the rollover limit for turning off tokenized FP to Flat Style FP. This is a PUBLIC option and is DBA settable only. This option sets the rollover point for all styles of tokenized FP. It effects all indexes on all tables. To turn off creation of FP(3), set this option to 65536. The next LOAD/UPDATE to a FP index over 65536 distincts converts the index into FLAT style.

CR:666312

CR Number:   666312 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   AIX Original Version:   15.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 May 2011 Fixed 30 Jun 2011 Fixed 15.3 13 May 2011 Added to user documentation Description Occasionally when using the Distributed Query feature of IQ on heavily loaded MPX servers a leader node can crash if the distributed query is using a table that was modified in the same transaction and has uncommitted changes

CR:666365

CR Number:   666365 Product Name:   IQ Product Component:   SA Component Status:   Closed OS:   Solaris Original Version:   15.1 e03 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16 Jun 2011 Consult Complete Description -

CR:666612

CR Number:   666612 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Unknown Original Version:   15.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 02 Aug 2011 Fixed 10 Sep 2011 Fixed Description In 15.3 GA, under some circumstances a query executed using DQP might return the wrong results when a column included NULL values and the NULL values were needed to compute the correct result.