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

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

CR:563681

CR Number:   563681 Product Name:   IQ Product Component:   Sybase Central Status:   Closed OS:   Windows XP Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 e01 18 Mar 2009 Fixed Description In SCJ : Set Clustered Index menu item now works for Catalog store tables. This option is grayed out for IQ Tables.

CR:563682

CR Number:   563682 Product Name:   IQ Product Component:   Sybase Central Status:   Closed OS:   Windows XP Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 e01 18 Mar 2009 Fixed Description In SCJ: Indexes created on catalog store tables listed under the Indexes Tab. Further, it is possible to view properties and mark index as clustered from the properties dialog of catalog store table indexes.

CR:563691

CR Number:   563691 Product Name:   IQ Product Component:   SA Component Status:   Closed OS:   Solaris Original Version:   12.7 e05 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 30 Mar 2009 Fixed Description A failed COMMENT ON PROCEDURE statement could prevent the procedure from being dropped. This has been fixed. A workaround is to stop and restart the database before attempting to drop the procedure.

CR:564035

CR Number:   564035 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Unknown Original Version:   12.7 e05 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 19 Mar 2009 Fixed 12.6 e12 19 Mar 2009 Fixed 15.0 e01 19 Mar 2009 Fixed Description Using "dateformat( colname, 'hh:mm:ss' )" does not output the correct time. For example: create table t1 ( c1 time ); insert t1 values ( current time ); select dateformat( c1, 'hh:mm:ss' ); Will output 09:mm:33

CR:564092

CR Number:   564092 Product Name:   IQ Product Component:   Sybase Central Status:   Closed OS:   Windows XP Original Version:   12.7 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 12 May 2009 Fixed 12.7 e07 10 Jun 2009 Fixed 15.1 03 Jun 2009 Fixed Description Using jconnect gives rises to a number of issues while using SCJ. Changing default driver to iAnywhere from jconnect.

CR:564252

CR Number:   564252 Product Name:   IQ Product Component:   SA Component Status:   Closed OS:   Unknown Original Version:   12.7 e05 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 27 Apr 2009 Fixed Description IF EXISTS( SELECT * FROM A,B), where A is an ASA object and B an IQ object, caused an IQ server failure with a signal 11. Workaround Description  Create the join table in the catalog.

CR:564512

CR Number:   564512 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 e07 30 Mar 2009 Fixed Description The server failed starting a database with the "-iqro 1" server option set after restoring the database. This database was a Multiplex Reader database being started using the "-iqmpx_ov 1 -iqmpx_sn 1" options as well. Workaround Description  The workaround is to start the database without the -iqro switch right after the restore, then shut it down and reopen it in RO mode with -iqro. Looks like IQ or SA wants to write something in the database right after a restore.

CR:565133

CR Number:   565133 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Windows 2008 Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0 20 Nov 2012 Fixed Description First, I want to state, for the record, that we received excellent support from John Barton during this eval He was always only a phonecall/email away, and he and I spent many hours of quality time together on the phone and virtual room, looking at problems and solutions together. Johns support was excellent, and so I feel confident that our test results are not skewed by any lack of understanding of the product on my part.. he was there with me every step of the way to keep me straight! Regarding follow-up, we are currently taking stock of our findings and roadmap options. Dom Ruffatto is my product management counterpart, and will be the one to contact you regarding any follow-on discussions. I CCed Dom on this email, by way of introduction. Dom Peter Do is the Sybase account rep for HP. Regarding testing results.. here is a very quick summary of my findings: - Select Star Schema queries degraded in performance very quickly as the fact table grew, due to expensive hash joins on queries that matched larger number of dimension records. See chart below. We experimented with join indexes which did speed up the query, but prohibitively slowed down the data loads. John has all the supporting information and query plans So we modified the schema (and indices) and test queries to focus on a flat fact table structure, where facts and dimensions were pre-joined during loading, with the goal that hash joins could be avoided. However, data loading times are problematic.. You can see from the chart below that load times increase with the size of the fact table. John helped me profile this behavior.. the elapsed time was almost all involved in the maintenance of two HG indexes applied to high cardinality name columns.. Disk I/O was pegged at 100% (iostats x) during these loads.. This implies that performance cannot be improved by further parallelization.. in fact the addition of additional parallel workloads can be presumed to compound the problem by competing for the same I/O resource. Removing the HG indices dramatically speeds up the load times, but also dramatically slows down queries which filter on the name columns. LF indices are not an option as the name columns have more than 10,000 unique values. So, thats the summary of findings.. Please let me know if you feel these findings are in any way inaccurate or unrepresentative of SybaseIQ 15_0 behavior, or if there are any solutions we havent explored relating to the load I/O performance issues mentioned above. NOTE: We tested Sybase 15.0 beta, understanding that it had improved parallelization of HG index updates, but unfortunately the bottleneck is disk I/O, not CPU. Also, please let me know if you are aware of any upcoming product features that might improve the load performance of fact tables with HG indexes, specifically enhancements that might reduce the disk I/O associated with these updates and therefore remove or diminish the effects of I/O saturation noted above. Detailed log: I. 01/23 18:23:34. 0000025215 [20895]: Insert Pass 1 completed in 5 seconds. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C2_HG: Thread 7 Inserting 98210 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C2_HG: Thread 0 Inserting 98210 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C2_HG: Thread 2 Inserting 98210 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 4 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 0 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 5 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 2 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 3 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 6 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 1 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 7 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C2_HG: Thread 6 Inserting 98210 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C2_HG: Thread 4 Inserting 98210 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 DBA.fact_tmp.ASIQ_IDX_T733_C2_HG Sort Insert Statistics: 30 pages over 1 run(s) (Min: 30 Max: 30 Avg: 30) from 1 inserter(s). I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 4 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 5 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 0 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 2 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 7 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 6 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 3 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 1 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 5 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 4 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 0 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 7 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 6 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 1 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 3 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 2 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 5 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 4 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 0 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 7 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 6 Inserting 16370 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 [20024]: Index DBA.fact_tmp.ASIQ_IDX_T733_C1_HG: Thread 1 Inserting 16320 Recs, 0 Secs. I. 01/23 18:23:35. 0000025215 DBA.fact_tmp.ASIQ_IDX_T733_C1_HG Sort Insert Statistics: 30 pages over 1 run(s) (Min: 30 Max: 30 Avg: 30) from 1 inserter(s). I. 01/23 18:23:35. 0000025215 [20895]: Insert Pass 2 completed in 1 seconds. I. 01/23 18:23:35. 0000025215 [20896]: Insert for 'fact_tmp' completed in 6 seconds. 491050 rows inserted. I. 01/23 18:23:36. 0000025215 Cmt 85137 I. 01/23 18:23:36. 0000025215 PostCmt 0 I. 01/23 18:23:36. 0000025215 Cmt 85139 I. 01/23 18:23:36. 0000025215 PostCmt 0 I. 01/23 18:23:38. 0000025215 Insert Started. I. 01/23 18:23:46. 0000025216 Cmt 85142 I. 01/23 18:23:46. 0000025216 PostCmt 0 I. 01/23 18:23:47. 0000025215 [20895]: Insert Pass 1 completed in 11 seconds. I. 01/23 18:23:50. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 6 Inserting 16380 Recs, 2 Secs. I. 01/23 18:23:51. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 4 Inserting 16380 Recs, 4 Secs. I. 01/23 18:23:51. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 2 Inserting 16375 Recs, 4 Secs. I. 01/23 18:23:52. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 3 Inserting 16380 Recs, 5 Secs. I. 01/23 18:23:52. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 0 Inserting 16390 Recs, 5 Secs. I. 01/23 18:24:00. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 5 Inserting 16305 Recs, 13 Secs. I. 01/23 18:24:05. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 4 Inserting 16380 Recs, 18 Secs. I. 01/23 18:24:05. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 1 Inserting 16380 Recs, 18 Secs. I. 01/23 18:24:06. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 6 Inserting 16380 Recs, 19 Secs. I. 01/23 18:24:06. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 5 Inserting 16380 Recs, 19 Secs. I. 01/23 18:24:06. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 7 Inserting 16380 Recs, 18 Secs. I. 01/23 18:24:06. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 2 Inserting 16380 Recs, 19 Secs. I. 01/23 18:24:06. 0000025217 Cmt 85144 I. 01/23 18:24:06. 0000025217 PostCmt 0 I. 01/23 18:24:07. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 3 Inserting 16380 Recs, 20 Secs. I. 01/23 18:24:07. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 0 Inserting 16380 Recs, 20 Secs. I. 01/23 18:24:14. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 3 Inserting 16380 Recs, 22 Secs. I. 01/23 18:24:17. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 7 Inserting 16360 Recs, 30 Secs. I. 01/23 18:24:21. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 4 Inserting 16380 Recs, 16 Secs. I. 01/23 18:24:22. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 6 Inserting 16380 Recs, 16 Secs. I. 01/23 18:24:22. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 1 Inserting 16380 Recs, 16 Secs. I. 01/23 18:24:23. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 5 Inserting 16380 Recs, 17 Secs. I. 01/23 18:24:25. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 2 Inserting 16380 Recs, 19 Secs. I. 01/23 18:24:25. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 3 Inserting 16360 Recs, 11 Secs. I. 01/23 18:24:25. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 1 Inserting 16375 Recs, 38 Secs. I. 01/23 18:24:25. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 7 Inserting 16380 Recs, 19 Secs. I. 01/23 18:24:26. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 5 Inserting 16390 Recs, 26 Secs. I. 01/23 18:24:26. 0000025218 Cmt 85146 I. 01/23 18:24:26. 0000025218 PostCmt 0 I. 01/23 18:24:26. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 7 Inserting 16315 Recs, 9 Secs. I. 01/23 18:24:29. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 3 Inserting 16380 Recs, 22 Secs. I. 01/23 18:24:29. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 0 Inserting 16380 Recs, 22 Secs. I. 01/23 18:24:29. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 3 Inserting 16435 Recs, 4 Secs. I. 01/23 18:24:37. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 1 Inserting 16340 Recs, 11 Secs. I. 01/23 18:24:37. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 2 Inserting 16380 Recs, 46 Secs. I. 01/23 18:24:37. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 5 Inserting 16435 Recs, 11 Secs. I. 01/23 18:24:43. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 6 Inserting 16475 Recs, 53 Secs. I. 01/23 18:24:46. 0000025219 Cmt 85148 I. 01/23 18:24:46. 0000025219 PostCmt 0 I. 01/23 18:24:47. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 4 Inserting 16380 Recs, 26 Secs. I. 01/23 18:24:48. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 6 Inserting 16380 Recs, 26 Secs. I. 01/23 18:24:48. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 1 Inserting 16380 Recs, 26 Secs. I. 01/23 18:24:51. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 2 Inserting 16380 Recs, 26 Secs. I. 01/23 18:24:51. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 5 Inserting 16380 Recs, 27 Secs. I. 01/23 18:24:53. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 7 Inserting 16380 Recs, 27 Secs. I. 01/23 18:24:53. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 6 Inserting 16380 Recs, 10 Secs. I. 01/23 18:24:57. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 0 Inserting 16380 Recs, 28 Secs. I. 01/23 18:24:58. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 3 Inserting 16380 Recs, 29 Secs. I. 01/23 18:24:59. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 3 Inserting 16350 Recs, 30 Secs. I. 01/23 18:25:02. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 0 Inserting 16380 Recs, 70 Secs. I. 01/23 18:25:03. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 6 Inserting 16375 Recs, 9 Secs. I. 01/23 18:25:04. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 0 Inserting 16350 Recs, 2 Secs. I. 01/23 18:25:04. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 6 Inserting 16400 Recs, 1 Secs. I. 01/23 18:25:06. 0000025220 Cmt 85150 I. 01/23 18:25:06. 0000025220 PostCmt 0 I. 01/23 18:25:08. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 3 Inserting 16375 Recs, 9 Secs. I. 01/23 18:25:09. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 0 Inserting 16050 Recs, 5 Secs. I. 01/23 18:25:12. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 4 Inserting 16380 Recs, 24 Secs. I. 01/23 18:25:13. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 7 Inserting 16395 Recs, 47 Secs. I. 01/23 18:25:13. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 6 Inserting 16380 Recs, 25 Secs. I. 01/23 18:25:13. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 2 Inserting 16380 Recs, 22 Secs. I. 01/23 18:25:14. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 1 Inserting 16380 Recs, 26 Secs. I. 01/23 18:25:14. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 5 Inserting 16380 Recs, 23 Secs. I. 01/23 18:25:14. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 4 Inserting 16370 Recs, 83 Secs. I. 01/23 18:25:14. 0000025215 [20024]: Index DBA.fact.fact_dim_config_qualifiedifname_HG: Thread 7 Inserting 16030 Recs, 21 Secs. I. 01/23 18:25:14. 0000025215 DBA.fact.fact_dim_config_qualifiedifname_HG Sort Insert Statistics: 120 pages over 1 run(s) (Min: 120 Max: 120 Avg: 120) from 1 inserter(s). I. 01/23 18:25:15. 0000025215 [20024]: Index DBA.fact.fact_dim_time_datetime_min_HG: Thread 1 Inserting 98210 Recs, 0 Secs. I. 01/23 18:25:15. 0000025215 [20024]: Index DBA.fact.fact_dim_time_datetime_min_HG: Thread 4 Inserting 98210 Recs, 0 Secs. I. 01/23 18:25:15. 0000025215 [20024]: Index DBA.fact.fact_dim_time_datetime_min_HG: Thread 3 Inserting 98210 Recs, 0 Secs. I. 01/23 18:25:15. 0000025215 [20024]: Index DBA.fact.fact_dim_time_datetime_min_HG: Thread 5 Inserting 98210 Recs, 0 Secs. I. 01/23 18:25:15. 0000025215 [20024]: Index DBA.fact.fact_dim_time_datetime_min_HG: Thread 2 Inserting 98210 Recs, 0 Secs. I. 01/23 18:25:15. 0000025215 DBA.fact.fact_dim_time_datetime_min_HG Sort Insert Statistics: 30 pages over 1 run(s) (Min: 30 Max: 30 Avg: 30) from 1 inserter(s). I. 01/23 18:25:18. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 2 Inserting 16380 Recs, 41 Secs. I. 01/23 18:25:19. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 5 Inserting 16390 Recs, 41 Secs. I. 01/23 18:25:26. 0000025221 Cmt 85152 I. 01/23 18:25:26. 0000025221 PostCmt 0 I. 01/23 18:25:32. 0000025215 [20024]: Index DBA.fact.fact_dim_config_dev_name_HG: Thread 1 Inserting 16400 Recs, 55 Secs. I. 01/23 18:25:32. 0000025215 DBA.fact.fact_dim_config_dev_name_HG Sort Insert Statistics: 90 pages over 1 run(s) (Min: 90 Max: 90 Avg: 90) from 1 inserter(s). I. 01/23 18:25:32. 0000025215 [20895]: Insert Pass 2 completed in 105 seconds. I. 01/23 18:25:32. 0000025215 [20896]: Insert for 'fact' completed in 114 seconds. 491050 rows inserted. I. 01/23 18:25:40. 0000025215 Cmt 85153 I. 01/23 18:25:40. 0000025215 PostCmt 0 I. 01/23 18:25:41. 0000025215 Cmt 85155 I. 01/23 18:25:41. 0000025215 PostCmt 0 I. 01/23 18:25:41. 0000025215 Cmt 85157 I. 01/23 18:25:41. 0000025215 PostCmt 0 I. 01/23 18:25:41. 0000025215 Cmt 85159 I. 01/23 18:25:41. 0000025215 PostCmt 0 I. 01/23 18:25:46. 0000025222 Cmt 85161 I. 01/23 18:25:46. 0000025222 PostCmt 0

CR:565290

CR Number:   565290 Product Name:   IQ Product Component:   SA Component Status:   Open OS:   Unknown Original Version:   12.7 e04.x Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Carriage return introduced into output header of select statement from view.

CR:565410

CR Number:   565410 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 e05.x 05 Apr 2009 Fixed 12.7 e06.x 05 Apr 2009 Fixed 12.7 e07 09 Jun 2009 Fixed 15.1 e01 07 Jul 2009 Fixed 15.2 07 Jul 2009 Fixed Description IQ 12.7 aggressively resets partition striping to mitigate freelist fragmentation that was seen in 12.6. When running workloads with a high number of truncates and deletes, this aggressive reclamation caused more time to be spent in searching for free space.

CR:565509

CR Number:   565509 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   12.7 e05 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 02 Apr 2009 Fixed 12.7 e07 27 May 2009 Fixed 27 May 2009 Fixed Description Recovery was failing due to the failing permission checks at the time of startup. Since the statement got executed successfully these checks are not required at the time of recovery.

CR:566175

CR Number:   566175 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Red Hat Original Version:   12.7 e05 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 02 Jul 2009 Fixed 15.1 e01 11 Jun 2009 Fixed 15.1 e01 13 Jul 2009 Fixed Description We was getting server failure while doing "ReEstimateWithinPushDownSubTrees " operation for the unflattened views, derived tables . Now Problem is resolved.

CR:566188

CR Number:   566188 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   AIX Original Version:   12.7 e04 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e09 28 Sep 2009 Fixed 15.1 e03 28 Sep 2009 Fixed 15.2 28 Sep 2009 Fixed Description IQ server fails with the bufman error followed by stacktrace when a query containing load and dropping table executed. The valid lbn checks are added in the IQ code to understand the reason of the server failure, if customer gets any in the future. Workaround Description  For issue involving drop table command, ct used force_option parameter. For issue involving the queries/ ct droppped and recreated the tables involved on this .

CR:566205

CR Number:   566205 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Original Version:   12.7 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e09 01 Feb 2010 Fixed 15.1 e03 25 Jan 2010 Fixed 15.2 03 Feb 2010 Fixed Description Under certain circumstances the join optimizer incorrectly rejected the pushdown join algorithm. It also refused to honor a join preference from the user requesting the use of a pushdown join in such cases. This has been fixed.

CR:566324

CR Number:   566324 Product Name:   IQ Product Component:   Documentation Status:   Closed OS:   Unknown Original Version:   12.7 Fixed Version Build Resolution Date Closure Code (If Appropriate) 26 May 2011 Insufficient priority to fix Description Some ASA modules are not attached to IQ. (PHP Module, Perl Module) However, only an ASA 9 programmer guide is attached to IQ. A customer cannot know why these modules are not attached to IQ.

CR:566382

CR Number:   566382 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 e07 08 Apr 2009 Fixed Description It was possible for the server to enter a loop while processing some statements that included an implicit or explicit use of the table SYS.DUMMY. This has been fixed.

CR:566457

CR Number:   566457 Product Name:   IQ Product Component:   SA Component Status:   Closed OS:   Windows XP Original Version:   15.1 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 e01 30 Mar 2009 Fixed Description iqunload would fail on windows if a directory name begins with \n.

CR:566634

CR Number:   566634 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Windows 2000 Original Version:   12.7 e05 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Would like the ability to define an alias and/or synonym for a table name so that users don't have to fully qualify (specify the owner.tablename) when another user other than owners the object.

CR:566696

CR Number:   566696 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Unknown Original Version:   12.7 e06 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 07 Apr 2009 Fixed 12.7 e07 11 Jun 2009 Fixed 15.1 17 Apr 2009 Fixed Description For a join index, - inserting into, or deleting from, or truncating the top table, or - inserting into, or deleting from, or truncating the non-top table, and then synchronizing the join index may lead to incorrect results for subsequent queries using the join index. This has been fixed.

CR:567076

CR Number:   567076 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   HP-UX Original Version:   12.7 e06.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 24 Sep 2009 Fixed 12.7 e06.x 24 Sep 2009 Fixed 15.1 e01 25 Sep 2009 Fixed 12.7 e07 05 Jun 2009 Fixed 12.7 e06.x 05 Jun 2009 Fixed 09 Jun 2009 Fixed Description Some queries that execute successfully in 12.7 ESD #5 and earlier versions failed in 12.7 ESD #6 at opt_Select.cxx:1996.

CR:567159

CR Number:   567159 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 e01 06 Apr 2009 Fixed 15.1 06 Apr 2009 Fixed Description A new option has been added to allow the maximum number of unique keys for a LF index to be configured. The LF index previously had a fixed limit of 10000 keys. LF_Max_Unique_Values Default: 10000 Min: 1 Max: 200000

CR:567172

CR Number:   567172 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   15.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 06 Apr 2009 Fixed 12.7 e07 20 Apr 2009 Fixed 12.7 e06.x 24 Sep 2009 Fixed Description If an application connects via Open Client, and if that application is using a newer version of Open Client 15, canceling a request may give a protocol error on the next request to the server. This problem has now been fixed.

CR:567188

CR Number:   567188 Product Name:   IQ Product Component:   Documentation Status:   Closed OS:   Unknown Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 03 Apr 2009 Fixed Description In the 15.0 Sybase IQ Quick Start, the @ sign was omitted before the configuration filename in step 4 of "Creating and using an IQ demo database." The error is corrected and an updated version of the Sybase IQ Quick Start is available on the Sybase Product Manuals web site.

CR:567502

CR Number:   567502 Product Name:   IQ Product Component:   Install Status:   Closed OS:   Solaris Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 22 Apr 2009 Fixed Description A product name when checkout of a license fails is not "Sybase IQ".

CR:567555

CR Number:   567555 Product Name:   IQ Product Component:   SA Component Status:   Closed OS:   Unknown Original Version:   12.7 e06.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 10 May 2009 Fixed 12.7 e07 11 Jun 2009 Fixed Description The group_member() function caused the IQ server to fail with Assertion 101506, if the user in question belonged to a large number of groups.

CR:567582

CR Number:   567582 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 e01 29 Jun 2009 Fixed Description ABORT from s_bufman::Rollback while running stored-procedure/batch if db goes out of temp space during drop temp table on end/close batch. Workaround Description  *** Thursday, April 16, 2009 2:05:34 PM *** sbandyop *** Added a Temp file of 30 GB to IQ_SYSTEM_TEMP and restarted the server. This is the only workaround available so far to increase the temp dbspace if we encounter the issue.

CR:567595

CR Number:   567595 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Unknown Original Version:   12.7 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 22 Apr 2009 Fixed 12.7 e07 10 Jun 2009 Fixed Description Running sp_iqrebuildindex on an SA type index now reports new error code -1009416, rather than an internal error.

CR:568066

CR Number:   568066 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 e01 16 Apr 2009 Fixed Description The coordinator will not start on the wrong host when the -iqmpx_ov 1 switch is used to start the server.

CR:568222

CR Number:   568222 Product Name:   IQ Product Component:   SA Component Status:   Closed OS:   Solaris Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 e01 18 May 2009 Fixed Description Server side bulk loader already supports named pipes. Extended this support in client-side bulk loader as well.

CR:568306

CR Number:   568306 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   HP-UX Original Version:   12.7 e05 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 future 17 May 2009 Fixed 12.7 e06.x 17 May 2009 Fixed 24 May 2009 Fixed Description A server failure may occur at hos_mutex.cxx line 813. While this failure should not occur under normal conditions, this error has been changed to an error that will not cause the server to fail and stop. If the error occurs, diagnostic information will be output to the iqmsg file that should be sent to sent to Sybase Support. This failure has occurred on HP and Linux platforms. The error has been found and fixed per CR #461826

CR:568446

CR Number:   568446 Product Name:   IQ Product Component:   Documentation Status:   Closed OS:   AIX Original Version:   15.0 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 e01 28 Apr 2009 Added to user documentation 16 Jun 2009 Added to user documentation Description IFIX IZ16878 from IBM is needed to install in graphical mode on AIX 6.1.

CR:568620

CR Number:   568620 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   AIX Original Version:   12.7 e05.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 07 Jul 2009 Fixed Description A stored procedure consisting of a declare local temporary table with a SELECT of the same local temporary table disappeared after a server sync.

CR:568799

CR Number:   568799 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Suse Original Version:   12.7 e04 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16 Jun 2009 Duplicate Description The IQ server may hang when the main or temporary cache is severely stressed and the emergency buffer pool is involved. This is a duplicate of CR 273582 and has been fixed.

CR:568830

CR Number:   568830 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   12.7 e06 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 26 Jun 2009 Fixed 15.1 e01 01 Jul 2009 Fixed 28 Jun 2009 Presently Not Targeted For Any Future Release Of This Product 15.2 01 Jul 2009 Fixed Description The output of the Join Node of the query containing outer join and large nested CASE statements was blank. Now the output of the Join node contains the required entry. Workaround Description  set FORCE_NO_SCROLL_CURSORS option to ON.

CR:569115

CR Number:   569115 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Unknown Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 e01 21 Apr 2009 Fixed 15.1 21 Apr 2009 Fixed Description This is an AIX only problem. Adding a file to a tempdb on a secondary node failed if the user wanted to store the raw partition on a secondary node.

CR:569129

CR Number:   569129 Product Name:   IQ Product Component:   SA Component Status:   Closed OS:   Solaris Original Version:   12.7 e05 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 06 May 2009 Fixed Description Attempting to return a result set from within a BEGIN ATOMIC block leaked server memory. Note that returning a result set from an atomic block is not allowed and an error is issued in this case; this behavior has not changed.

CR:569472

CR Number:   569472 Product Name:   IQ Product Component:   SA Component Status:   Closed OS:   Unknown Original Version:   12.7 e05 Fixed Version Build Resolution Date Closure Code (If Appropriate) 09 Jun 2009 Fixed 22 Jun 2009 Fixed Description Corrected back-end query used in SCJ for retrieving User related information from server.

CR:569729

CR Number:   569729 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   12.7 e04 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 27 Jul 2009 Fixed 10 Jun 2009 Fixed Description The server failed whenever a table with foreign keys was dropped and the FORCE_DROP option was set. Workaround Description  Customer is able drop the table after dropping FKeys.

CR:570077

CR Number:   570077 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   AIX Original Version:   12.7 e05.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 24 Jun 2009 Fixed Description Query -- Server failed while a running query was interrupted. Workaround Description  Not Yet

CR:570125

CR Number:   570125 Product Name:   IQ Product Component:   SA Component Status:   Closed OS:   Solaris Original Version:   12.7 e06 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16 Jun 2009 Fixed Description Using an aggregate function with the PRINT statement sometimes caused a server failure.

CR:570151

CR Number:   570151 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Unknown Original Version:   12.7 e05 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 01 May 2009 Fixed Description When creating a table with an identity column, the IQ server became unresponsive waiting on the GetIdentityEnforceUniqueness call.

CR:570275

CR Number:   570275 Product Name:   IQ Product Component:   SA Component Status:   Closed OS:   AIX Original Version:   12.7 e05.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 09 Jul 2010 Fixed 27 Oct 2009 Fixed Description Some queries with incorrect syntax like <TableName>.<ColumnName>.substring(1,4) caused a server failure. An error message is now returned. Workaround Description  CASE WHEN A.ORG_CD.substring(4,8) = '0101' THEN A.ORG_CD.substring(0, 4) ELSE A.ORG_CD END ORG_CD ... It sould be like below ... CASE WHEN SUBSTRING(A.ORG_CD,4,8) = '0101' THEN ...

CR:570417

CR Number:   570417 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   12.7 e04 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15 Jun 2009 Fixed 12.7 e07 29 Jun 2009 Fixed 24 Sep 2010 Fixed 15.3 28 Sep 2010 Fixed Description A bitwise operation with one of the operands having scaled data type throws a conversion error. This behavior has now changed to do automatic data type conversion so that the bitwise operation succeeds. Workaround Description  do explicit convert on power function like :- select a & convert(int, power(2,3) ) from t1

CR:570489

CR Number:   570489 Product Name:   IQ Product Component:   Sybase Central Status:   Closed OS:   Linux Red Hat Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 e01 07 May 2009 Fixed 09 Jun 2009 Fixed Description "Select" button in "Dbspace File Wizard" was provided to add multiple files in DBSpace, but it also required edit operation to give details. "Add" button is more handy for the same purpose. Hence "Select" button is removed from the wizard.

CR:570732

CR Number:   570732 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   AIX Original Version:   12.7 e05 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 12 Aug 2009 Fixed 12.7 e07 10 Aug 2009 Fixed 12.7 e09 13 Aug 2009 Fixed 15.1 e01 13 Aug 2009 Fixed Description When FORCE_NO_SCROLL_CURSOR is 'On' there is constant growth in Dynamic Memory used by IQ, this is due to holding data type info even after the cursor is destroyed. This problem has been fixed now.

CR:570735

CR Number:   570735 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Unknown Original Version:   12.7 Fixed Version Build Resolution Date Closure Code (If Appropriate) 09 Jul 2010 Fixed Description This is raised for a minor messaging error. If you try to execute a non existant stored procedure you correctly get this error..... Msg 504, Level 11, State 0: ASA Error -265: Procedure 'xxxxx' not found If you try execute the non existant procedure but this time give it a parameter you should expect to just get the same error message say the procedure does not exist. However you get the following error instead.... Msg 201, Level 16, State 0: ASA Error -615: Parameter '' not found in procedure '???' This is misleading as it implies the procedure is OK but the parameter is incorrect.

CR:571223

CR Number:   571223 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Solaris Original Version:   12.7 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description customer is trying to redirect query output to a file using set option Temp_Extract_Name1 and have control of the file permissions used to create the resultant file. They have been trying to do thuis with umask as per documented in CR 570627. As per the resolution in CR 570627.... IQ is coded to create the extract output files with permissions rw-r--r--. umask acts on the permissions as follows: When a file is created, its permissions are set to what the creating program asks for minus what the umask setting forbids. So, the bottom line is that umask can't add any permissions that the creating program hasn't given. We need a FR that allow control. Workaround Description  Stored procedures or events using xp_cmdshell to run chmod, etc, or just using chmod via some script.

CR:571471

CR Number:   571471 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Unknown Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 e01 25 Sep 2009 Fixed Description Table partitioning functionality is not available without license. IQ_VLDBMGMT license is required to create partitions in table.

CR:571589

CR Number:   571589 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Unknown Original Version:   12.7 e07 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 08 Jun 2009 Fixed 12.7 e07 12 Jun 2009 Added to user documentation 15.2 18 Aug 2009 Fixed 15.2 10 Jul 2009 Fixed Description Client Side Plan will available for UPDATE/DELETE/INSERT SELECT/SELECT INTO also, when QUERY_PLAN_TEXT_CACHING = OFF.

CR:571720

CR Number:   571720 Product Name:   IQ Product Component:   Install Status:   Closed OS:   Solaris Original Version:   15.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 e01 22 May 2009 Fixed Description The _jvmIQ directory (used for uninstalling IQ15.x) is missing if IQ15.1 is installed after installing other Sybase products. This has been fixed.

CR:571749

CR Number:   571749 Product Name:   IQ Product Component:   Install Status:   Closed OS:   Solaris Original Version:   15.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 e01 22 May 2009 Fixed Description The IQ Plugin was not being registered if IQ15 was installed if there was an existing SySAM install on the machine. This has been fixed. Workaround Description  1. register IQ plug-in manually. 2. Or delete existed 'lmutil' before silent install IQ 15.1. 3. Or install IQ 15.1 in GUI mode.

CR:571954

CR Number:   571954 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Original Version:   12.7 e06.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 29 May 2009 Consult Complete Description An IQ query node can fail in different ways: 1. Fail with a signal 11. The IQ server continues to run. Only an incomplete stacktrace is generated. 2. Fail with signal 5 or 11. This may be followed by a message "Memory corruption detected", another signal 11 (in which case the server continues to run with no complete stacktrace generated), or by multiple signal 5's (in which case the server fails with a full stacktrace generated). This has been fixed.

CR:572341

CR Number:   572341 Product Name:   IQ Product Component:   Sybase Central Status:   Open OS:   AIX Original Version:   12.7 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description IQ 12.7 AIX - Feature request - When starting up the dbremote via SCJ, allow to user define an unique dbremote log file name to be used in all startup times, instead of to rename the Dbremote log file name using the string like this : engine_name.xxx.dblog where xxx is incremented each time that DBremote is started . When starting dbremote via script, the unique dbremote log file name is defined used -o switch . Workaround Description  start the DBremote via script where the dbremote log file name is defined using -o switch.

CR:572524

CR Number:   572524 Product Name:   IQ Product Component:   Install Status:   Closed OS:   Unknown Original Version:   15.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15 May 2009 Presently Not Targeted For Any Future Release Of This Product Description Installing Sybase IQ 15.0 ESD #1 over Sybase IQ 15.0 GA gives an waring message about overwriting newer version of scvwen600.jar. This warning should be ignored and newer one overwritten

CR:572540

CR Number:   572540 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   12.7 e05 Fixed Version Build Resolution Date Closure Code (If Appropriate) 26 May 2009 Consult Complete Description The problem encountered is due to a one time cost when a table, that existed in 12.6, is opened for the first time in 12.7. A feature was added to 12.7 to construct a null bitmap on each nullable column defined on the table. This bitmap is constructed when the table is opened readwrite for the first time on 12.7 after the upgrade has been done. Subsequent readwrite operations on the table will not incur this cost. The cost is a function of the number of NULL and non-NULL cells on a given column in conjunction with the number of rows in the table. This null bitmap was added, to address performance issues, to greatly improve query performance when a query needed to take into account NULL values.

CR:572640

CR Number:   572640 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   HP-UX Original Version:   12.7 e05.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 27 May 2009 Consult Complete 12.7 e07 02 Jul 2009 Fixed Description Creating tables with the same name and same column names, but in different case, was allowed after the server was restarted in CASE RESPECT database. Workaround Description  Nothing.

CR:572648

CR Number:   572648 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   AIX Original Version:   12.7 e05.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 22 Jul 2009 Fixed 12.7 e09 13 Aug 2009 Fixed 15.2 08 Oct 2009 Fixed 15.1 e03 01 Oct 2009 Fixed 15.2 01 Oct 2009 Fixed 07 Oct 2009 Fixed Description The maximum value supported in SQL Anywhere for the numeric function is 255. If the precision of the numeric function exceeds the maximum value supported in SQL Anywhere, the following error occurs: "The result datatype for function '_funcname' exceeds the maximum supported numeric precision of 255. Please set the proper value for precision in numeric function, 'location'" Target Version  12.7 e08 Workaround Description  re-writting SQL : SELECT s.ItemA , s.ItemB , s.ItemC , convert(numeric, sum(CASE WHEN s... => SELECT s.ItemA , s.ItemB , s.ItemC , convert(numeric(18,0), sum(CASE WHEN ...

CR:572733

CR Number:   572733 Product Name:   IQ Product Component:   SA Component Status:   Closed OS:   Unknown Original Version:   12.7 future Fixed Version Build Resolution Date Closure Code (If Appropriate) 10 Jan 2011 Fixed 15 Jul 2009 Fixed Description Request to change the SQL_SEARCH_PATTERN_ESCAPE to backslash.

CR:573449

CR Number:   573449 Product Name:   IQ Product Component:   Install Status:   Closed OS:   Unknown Original Version:   15.0 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 e01 21 May 2009 Consult Complete Description Please be aware that a minor inconsistency has been introduced into the IQ 15.0.0 ESD#1 version string. This release will incorrectly report its version as 15.0.1 ESD#1. This issue has no effect on the functioning of the software.

CR:573637

CR Number:   573637 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Unknown Original Version:   15.1 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 e01 16 Jul 2009 Fixed Description The maximum allowable length of a binary argument to a UDF has been increased from 256 bytes to 32KB.

CR:573995

CR Number:   573995 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Solaris Original Version:   12.7 e06 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Third argument to LOCATE() function can be CAST to larger than BIGINT.

CR:574043

CR Number:   574043 Product Name:   IQ Product Component:   Sybase Central Status:   Closed OS:   Windows XP Original Version:   12.7 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 19 Aug 2009 Fixed Description The Tables/Indexes tab of each Dbspace were not being populated in the view panel. This has been corrected.

CR:574057

CR Number:   574057 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   HP-UX Original Version:   12.7 e05.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 15 Jun 2009 Fixed Description When 'sa dummy' was used in a particular query instead of IQ dummy, the server failed. An appropriate NULL check was added in the function to avoid a server failure.

CR:574699

CR Number:   574699 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   AIX Original Version:   12.6 e11 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e09 16 Oct 2009 Fixed 15.1 e03 28 Oct 2009 Fixed 15.2 25 Jan 2010 Fixed Description A stored procedure with the following loop may result in incorrect data written to the table: loop savepoint; fetch next from cursor; update table where current of cursor; end loop

CR:574927

CR Number:   574927 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   12.7 e05 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 15 Jun 2009 Fixed 12.7 e05.x 21 Jul 2009 Fixed Description In certain cases where nested functions were used in negated predicates, query performance degraded when using 12.7 instead of 12.6.

CR:574933

CR Number:   574933 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 e09 29 Oct 2009 Fixed Description The FORWARD TO statement could have truncated the forwarded statements to roughly a database page size in length. This has been fixed.

CR:574976

CR Number:   574976 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Windows 2000 Original Version:   12.7 e06 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Feature request for load balancing where user can automatically login to predefined group of query engines.

CR:575036

CR Number:   575036 Product Name:   IQ Product Component:   Documentation Status:   Closed OS:   Unknown Original Version:   12.7 e05 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 24 Jul 2009 Fixed Description When many index statements are executed on the IQ writer server, there are hundreds of versions sent to IQ reader servers. On the IQ reader servers, when lots of versions are coming in and there are users connected to it, the IQ reader servers need more memory than the IQ writer servers to manage those versions. Even when there are no users connected to the IQ reader servers, there are internal event connections happening. To verify this, disable ev_iqmpxq2w on the IQ reader servers and ensure there are no user connections. Run the ddl on IQ writer server and observe the IQ reader server is consuming same memory as the IQ writer. Once the TLV replay is completed, the IQ reader server releases the extra memory that it consumes while managing the versions. However, on UNIX, that memory is never returned to the operating system. Once memory is allocated for a process, the process retains that memory until the operating system is restarted. To avoid having the memory consumed and not released, the indexes must be grouped in BEGIN PARALLEL IQ and END PARALLEL IQ. See "The CREATE INDEX statement" in Chapter 6, "Using Sybase IQ Indexes" in System Administration Guide: Volume 1 and "BEGIN PARALLEL IQ ... END PARALLEL IQ statment" in Chapter 1 "SQL Statements" in Reference: Statements and Options.

CR:575104

CR Number:   575104 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Original Version:   12.7 e06 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 28 Oct 2009 Fixed Description The issue is fixed for IQ 15.0 GA and above. For IQ 12.7, use this workaround: cast the select list as appropriate. For instance, in the following case: create table test (c1 decimal(15,2), c2 decimal(18,2)); select abs(c1) + c1 + c1 + c2 into #tmp from test; change the select statement to select cast((abs(c1) + c1 + c1 + c2) as decimal(15,2)) into #tmp from test;

CR:575686

CR Number:   575686 Product Name:   IQ Product Component:   Documentation Status:   Closed OS:   AIX Original Version:   12.6 e11 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 10 Mar 2010 Added to user documentation Description Need to document row-by-row update in long transaction can use up a lot of main dbspace.

CR:575773

CR Number:   575773 Product Name:   IQ Product Component:   SA Component Status:   Closed OS:   Solaris Original Version:   12.7 future Fixed Version Build Resolution Date Closure Code (If Appropriate) 23 Jul 2009 Duplicate Description Request to document Check_Alias_Enabled option.

CR:575896

CR Number:   575896 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   HP-UX Original Version:   12.7 e05.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 17 Jun 2009 Fixed 02 Jul 2009 Consult Complete 12.7 e06.x 08 Jul 2009 Fixed 12.7 e07 08 Jul 2009 Fixed Description If an application executed a remote query containing many tables, and if the query contained many tables, then there was a chance the server would give assertion 101508, instead of giving the "syntactic limit exceeded" error. Workaround Description  Re-written to aviod 'Statement size or complexity exceeds server limits' ... UNION ALL SELECT '02020229' 瘤钎魂免备盒, Null S00, Null S01, Null S02, Null S03, Null S04, Null S05, Null S06, Null S07, Null S08, Null S09, Null S10, Null S11, Null S12, Null 乞闭 UNION ALL SELECT '02040230' 瘤钎魂免备盒, Null S00, Null S01, Null S02, Null S03, Null S04, Null S05, Null S06, Null S07, Null S08, Null S09, Null S10, Null S11, Null S12, Null 乞闭 ==> ... UNION ALL SELECT '02020229' 瘤钎魂免备盒, Null S00, Null S01, Null S02, Null S03, Null S04, Null S05, Null S06, Null S07, Null S08, Null S09, Null S10, Null S11, Null S12, Null 乞闭 from inst1.dummy UNION ALL SELECT '02040230' 瘤钎魂免备盒, Null S00, Null S01, Null S02, Null S03, Null S04, Null S05, Null S06, Null S07, Null S08, Null S09, Null S10, Null S11, Null S12, Null 乞闭 from inst1.dummy

CR:576902

CR Number:   576902 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 e07 24 Sep 2009 Fixed 16 Oct 2009 Duplicate 16 Oct 2009 Duplicate 16 Oct 2009 Duplicate 16 Oct 2009 Duplicate Description Performance degrades when predicates containing complex expressions are used in 12.7 code. To get better performance for queries containing complex expressions in predicates, set following internal option: set [temporary] option dml_options6 = 32768 Note: Some queries might show performance degradation after setting this option. This option should be set to get better performance for queries which do not show better performance by default.

CR:576907

CR Number:   576907 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Linux Red Hat Original Version:   12.7 e05 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Request a procedure that list defaults & current IQ startup configuration parameters.

CR:577098

CR Number:   577098 Product Name:   IQ Product Component:   SA Component Status:   Closed OS:   Solaris Original Version:   12.7 e06 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 18 Jun 2009 Fixed Description In exceptionally rare circumstances, the engine failed while rewriting a very large and complex SELECT statement. This happened if the engine was close to running out of stack size or was low on cache size. The problem occurred with queries containing UNION, EXCEPT, INTERSECT, or deeply nested sub-selects. The engine now returns the error "-890: Statement size or complexity exceeds server limits."

CR:577112

CR Number:   577112 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   HP-UX Original Version:   12.7 e03 Fixed Version Build Resolution Date Closure Code (If Appropriate) 08 Sep 2009 Consult Complete 12.7 e09 16 Sep 2009 Fixed 13 Nov 2009 Fixed Description The failure was caused by a bug in the error handling during TLV replay. This has been fixed. Workaround Description  Created the view that was prior to alteration and the restarted query server and it worked.

CR:577313

CR Number:   577313 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Red Hat Original Version:   15.0 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 06 Jul 2009 Duplicate Description *** Tuesday, September 22, 2009 2:36:35 PM *** agarwala *** LOAD aborts the engine during 2 to 3 byte FP rollover while destroying a locked buffer. Workaround Description  From Lou Stanton, By setting IQ Unique(20000000) on the hi card columns we were able to load. One column rolled over to flat and we saw a non fatal error about a hash for that FP. Before had had many which probaly caused the stacktrc. that's my guess.

CR:577383

CR Number:   577383 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   AIX Original Version:   12.7 e06.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e09 18 Nov 2009 Fixed 12.7 e09 10 Sep 2009 Fixed Description Running a query with recursive cases resulted in an unresponsive server. Now an error is reported. Workaround Description  Not Yet.

CR:577733

CR Number:   577733 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Unknown Original Version:   12.7 future Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Provide "all" syntax for sp_iqrebuildindex.

CR:577889

CR Number:   577889 Product Name:   IQ Product Component:   other Status:   Closed OS:   Windows XP Original Version:   12.7 e06 Fixed Version Build Resolution Date Closure Code (If Appropriate) 28 Jun 2010 Presently Not Targeted For Any Future Release Of This Product Description Feature request for IQ ODBC driver to support TDS protocol.

CR:578116

CR Number:   578116 Product Name:   IQ Product Component:   Documentation Status:   Closed OS:   Unknown Original Version:   15.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 23 Jun 2009 Fixed 15.2 31 Jul 2009 Fixed Description The "Sybase IQ binary load format" section in Chapter 3 of the Building Blocks Reference Manual has incorrect information. There is a formula that reads For a given year, month, and day: year = current_year - 1; days_in_year_0000 = 366; binaryDateValue = (year * 365) + (year / 4) - (year / 100) + (year / 400) days_in_year_0000 day_of_current_year -1; It should read For a given year, month, and day: year = current_year - 1; days_in_year_0000 = 366; binaryDateValue = (year * 365) + (year / 4) - (year / 100) + (year / 400) + days_in_year_0000 + day_of_current_year -1;

CR:578390

CR Number:   578390 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Windows 2000 Original Version:   15.0 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 e01 13 Jul 2009 Fixed Description When index advisor is turned on, the IQ server may crash. This problem is now resolved. Workaround Description  Either use 64bit windows or turn off Index advisor on 32bit windows install.

CR:578793

CR Number:   578793 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Unknown Original Version:   12.7 e07 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.0 21 Jul 2009 Presently Not Targeted For Any Future Release Of This Product Description Joining an SA stored procedure and an IQ table in a CASE statement condition will cause the server to crash. This is a known issue that has been fixed in version 15.0 and later. Expressions of the form: create table t1(num as integer, name as varchar(30)) ... case when (select count(*) from sa_conn_properties(),t1) > 1 then ... else ... end case ... Will cause the server to crash. To prevent the crash, declare t1 IN SYSTEM or execute the predicate query outside the case statement and assign it to a variable, then use the variable in the case predicate. Workaround Description  The workaround is as follows +++++++++++++++++++++++++++++++++++++++++++++++++ Problematic query involves an IQ table and an SA sproc. Work around is to create table in SYSTEM store. This will eliminate the error. Another workaround I can think of is - instead of putting query in "Case" statement, execute it first and store the result in some variable and the use the variable in "Case" e.g. blah = select count (*) from <IQ TABLE>, <SA PROCEDURE> Case when blah > 1 <do something> +++++++++++++++++++++++++++++++++++++++++++++++++

CR:578804

CR Number:   578804 Product Name:   IQ Product Component:   Install Status:   Closed OS:   Linux Red Hat Original Version:   12.7 Fixed Version Build Resolution Date Closure Code (If Appropriate) 23 Oct 2009 Fixed Description The IQ 12.7 Network Client for Linux 32-bit file Linux-iq1270_client.tgz you download from the EBF's section in http://downloads.sybase.com (release date 21 Nov 2008) is corrupt / problematic. If you download thuis file and use tar -xzvf to unzip it, then run sybinstall. The jConnect 6.0 part throws tar an gzip erros (see below). The sybiqntwkclnt127lin.tgz file from SPDC download site for the same software is fine and works OK. ----------------------- Installing jConnect 6.0 ----------------------- jConnect-6_0/ jConnect-6_0/index.html jConnect-6_0/netimpct.gif jConnect-6_0/version.txt jConnect-6_0/tools/ jConnect-6_0/tools/decode-tli jConnect-6_0/sp/ jConnect-6_0/sp/sql_asa.sql jConnect-6_0/sp/sql_server.sql jConnect-6_0/sp/sql_server12.5.sql jConnect-6_0/sp/sql_server12.sql tar: Skipping to next header tar: Archive contains obsolescent base-64 headers gzip: stdin: invalid compressed data--crc error gzip: stdin: invalid compressed data--length error tar: Error exit delayed from previous errors Install failed for the following reasons ---------------------------------------- Copying of jConnect 6.0 failed tar: Skipping to next header tar: Archive contains obsolescent base-64 headers gzip: stdin: invalid compressed data--crc error gzip: stdin: invalid compressed data--length error tar: Error exit delayed from previous errors Workaround Description  use the sybiqntwkclnt127lin.tgz file from SPDC download site instead

CR:578993

CR Number:   578993 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   15.1 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 e01 10 Jul 2009 Fixed Description LOAD aborts the engine during 2 to 3 byte FP rollover while destroying a locked buffer.

CR:579036

CR Number:   579036 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   12.7 e06 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 21 Jul 2009 Fixed Description Backup/Restore : Restore failed while trying to restore a backup taken on 12.6 release to 12.7. This was an issue with the dbspace size reported on 12.6 vs 12.7.

CR:579409

CR Number:   579409 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   12.7 e06.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e09 30 Jul 2009 Fixed 15.0 e01 31 Aug 2009 Fixed 15.2 08 Sep 2009 Fixed Description An unnecessary emergency shutdown for unresolved dynamic collisions occurred in some situations.

CR:580065

CR Number:   580065 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   HP-UX Original Version:   12.6 e11 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e07 22 Jul 2009 Fixed 15.2 13 Aug 2009 Fixed 12.6 e11 13 Aug 2009 Fixed 12.6 e11 23 Sep 2009 Fixed Description If an application executed a remote query that involved the use of ROWID, and if the table specified to ROWID was a remote table, and if the query was processed in partial passthru, then there was a chance the server would fail.

CR:580527

CR Number:   580527 Product Name:   IQ Product Component:   Sybase Central Status:   Closed OS:   Windows XP Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 e01 16 Jul 2009 Fixed Description New code now ensures a Chinese locale will only show localized resources in the zh_CN locale - otherwise it shows English. sybasecentral600.jar and jsyblib600.jar were updated. Workaround Description  modify %SYBASE%\Shared\Sybase Central 6.0.0\win32\scjview.ini by adding -Duser.language=en to VM_ARGUMENTS line :- VM_ARGUMENTS=-Xmx300m;-Duser.language=en

CR:580578

CR Number:   580578 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Linux Red Hat Original Version:   15.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 e01 10 Jul 2009 Duplicate Description In some situation , when Query contain case expression with having clause so we was getting Internal error at dfo.cxx (Can not evaluate expression) .The Problem is now fixed .

CR:580742

CR Number:   580742 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Solaris Original Version:   12.7 e06 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e09 06 Aug 2009 Fixed 15.1 e01 07 Aug 2009 Fixed 15.2 27 Jul 2009 Fixed Description The MINIMIZE_STORAGE database option that is set to ON or OFF prior to the creation of a table sometimes affected the result of calculations involving the numeric columns of the table.

CR:580808

CR Number:   580808 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 e09 29 Oct 2009 Fixed Description The engine may incorrectly rewrite the WHERE, ON, or HAVING clause and return no or too few rows. This happens if the engine has found redundant conjuncts and try to remote it. An example of this is the query select 1 from T where a = 1 and ( b = 2 or c = 8 ) and ( d = 4 or e = 10 ) and ( a = 1 or e = 7 or c = 9 ) This has been fixed.

CR:581012

CR Number:   581012 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Solaris Original Version:   15.0 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 22 Jul 2009 Workaround Description Insert .. select may not be parallelized in 15.1 and result in performance degradation from 12.7. To force parallel insert - select, set option DML_Options8=65536. This option should be used only when the table does not have any join indexes. Workaround Description  DML_Options8=65536

CR:581158

CR Number:   581158 Product Name:   IQ Product Component:   SA Component Status:   Closed OS:   Solaris Original Version:   15.1 l10n Fixed Version Build Resolution Date Closure Code (If Appropriate) 17 Sep 2009 Fixed Description A Japanese message is not included in DBISQL attached to IQ15.

CR:582105

CR Number:   582105 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   HP-UX Original Version:   12.7 e06.x Fixed Version Build Resolution Date Closure Code (If Appropriate) 28 Jul 2009 Consult Complete 12.7 e09 24 Sep 2009 Fixed 15.1 e03 21 Dec 2009 Fixed 15.2 04 Jan 2010 Fixed Description While running a query involving a large number of UNION ALL, the server became unresponsive after detecting a stack overflow.

CR:582634

CR Number:   582634 Product Name:   IQ Product Component:   IQ Component Status:   Open OS:   Unknown Original Version:   12.7 future Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Request a way to determine global temporary table connection usage.

CR:582732

CR Number:   582732 Product Name:   IQ Product Component:   IQ Component Status:   Closed OS:   Unknown Original Version:   15.1 e01 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.1 e01 08 Aug 2009 Fixed 15.2 08 Aug 2009 Fixed Description The group_member() function causes the IQ server to crash with Assertion 109506 ("Allocation size too large when re-allocating memory") if the user in question belongs to a large number of groups. This has been fixed.

CR:583190

CR Number:   583190 Product Name:   IQ Product Component:   Install Status:   Closed OS:   Solaris Original Version:   12.7 e09 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.7 e09 03 Nov 2009 Fixed 01 Mar 2010 Fixed 09 Dec 2009 Failed Description Server files that support "Java in the database" in 12.7 are no longer released with any ESD beyond ESD #8. Customers who did not install 12.7 ESD #8 will be required to install ESD #8 to update to the latest supported version, before any newer update can be applied.

CR:583233

CR Number:   583233 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) 30 Aug 2009 Fixed 15.1 e03 21 Sep 2009 Fixed 15.2 21 Jan 2010 Fixed Description While loading into a LOB or a CLOB column with LOAD_MEMORY_MB = 0, the server requests for a large amount of memory. This could lead to the query to fail on some platforms. This has been fixed. Workaround Description  Change the LOAD_MEMORY_MB option from zero (the default) set temporary option LOAD_MEMORY_MB=400;

CR:583724

CR Number:   583724 Product Name:   IQ Product Component:   Documentation Status:   Closed OS:   Unknown Original Version:   15.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15.2 07 Dec 2009 Fixed Description Request to document the preceding database options.