kb sql release notes version 4 - oracle · kb_sql release notes version 4.6 knowledge based...

KB_SQL Release Notes Version 4.6

Knowledge Based Systems, Inc.

Last Updated: Wednesday, May 02, 2007

© Copyright 2007 by Knowledge Based Systems, Inc. All rights reserved. Knowledge Based Systems, Inc., Ashburn, Virginia, USA. Printed in the United States of America. No part of this manual may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from Knowledge Based Systems, Inc., as governed by United States and international copyright laws. The information contained in this document is subject to change without notice. Knowledge Based Systems, Inc. does not warrant that this document is free of errors. If you find any problems in the documentation, please report them to us in writing.

Knowledge Based Systems, Inc. 43053 Midvale Court Ashburn, Virginia 20147

Alternatively you can suggest the correction in the KBS eService Center at www.knowledgebasedsys.com/support. Website: www.knowledgebasedsys.com Email: [email protected] KB_SQL is a registered trademark of Knowledge Based Systems, Inc. MUMPS is a registered trademark of the Massachusetts General Hospital. All other trademarks or registered trademarks are properties of their respective companies.

Release Notes Version 4.6 Knowledge Based Systems, Inc.

http://www.knowledgebasedsys.com/support

http://www.knowledgebasedsys.com/

mailto:[email protected]

TABLE OF CONTENTS INTRODUCTION......................................................................................................................... 1

NEW FEATURES......................................................................................................................... 2 KB_SQL SERVER ........................................................................................................................ 2

Transaction log reports accept TIME range restriction......................................................... 2 Users with run-only privileges can now see queries needing to be compiled. ....................... 2 Conversion utility will correct the FREE_ROUTINE table.................................................... 2 New QUERY QUEUE OPTIONS menu.................................................................................. 2 A New XML_SIMPLE format is added for download queries................................................ 2

KB_SQL QRE PROFESSIONAL .................................................................................................... 3 Provide a consistent set of Query functions............................................................................ 3 Allow Multiple Query selection .............................................................................................. 3 Queue Inspector – Filters ....................................................................................................... 3 Image Inspector – Filters........................................................................................................ 3 Saved Query Lists ................................................................................................................... 4 Add Menu Option Support for Saved Query Lists .................................................................. 4 MyReports ............................................................................................................................... 4

KB_SQL ODBC DRIVER ............................................................................................................ 5 Corrections affect Microsoft SQL Server Integration Services (SSIS) ................................... 5

KB_SQL ADO.NET DATA PROVIDER........................................................................................ 6 All new data provider provides compatibility with Microsoft ADO.NET............................... 6

FIXED ITEMS .............................................................................................................................. 7 KB_SQL SERVER FIXES .............................................................................................................. 8 KB_SQL QRE PROFESSIONAL FIXES ........................................................................................ 14 KB_SQL ODBC DRIVER FIXES ................................................................................................ 18 KB_SQL JDBC DRIVER FIXES.................................................................................................. 19 KB_SQL DOWNLOAD AGENT FIXES ......................................................................................... 20 KB_SQL ADO.NET DATA PROVIDER FIXES............................................................................ 21 KBS ESERVICE CENTER FIXES................................................................................................... 22

KNOWN PROBLEMS ............................................................................................................... 23

KB_SQL SERVER KNOWN PROBLEMS....................................................................................... 23 KB_SQL QRE PROFESSIONAL KNOWN PROBLEMS................................................................... 25 KB_SQL ODBC DRIVER KNOWN PROBLEMS........................................................................... 26 KB_SQL JDBC DRIVER KNOWN PROBLEMS ............................................................................ 27 KB_SQL DOWNLOAD AGENT KNOWN PROBLEMS.................................................................... 28 KB_SQL ADO.NET DATA PROVIDER KNOWN PROBLEMS ...................................................... 29 KBS ESERVICE CENTER KNOWN PROBLEMS ............................................................................. 30

Release Notes Version 4.6 Knowledge Based Systems, Inc.

Introduction The Release Notes provides information about the product's new features, fixes, and known problems for Knowledge Based Systems' VARs and enterprise clients. The features are documented to provide the reader with information regarding the purpose of the feature and its intended use. Key fixes are documented to provide the problem definition and possible symptoms of the problem. Known problems are documented to provide a detailed description of the problem, situations that may cause the problem, and in situations where possible, a workaround.

1 Release Notes Version 4.6 Knowledge Based Systems, Inc.

New Features

KB_SQL Server

Transaction log reports accept TIME range restriction. Good news for those of you that rely on the various Transaction Log reports. You can now specify a TIME range restriction allowing you to see just the items that are logged in a time period.

Users with run-only privileges can now see queries needing to be compiled. Previously, a run-only user could only see queries for which they had privileges if the queries were in a compiled state. We will now show the queries even if they need to be compiled. When run, the query will be compiled on-the-fly, reporting errors as necessary. This should further reduce the requirement to compile all queries as part of a data dictionary change or software update.

Conversion utility will correct the FREE_ROUTINE table. Over the past several releases, we have encountered problems with the management of routines that are marked as available for use by queries. A conversion utility is included with this release that will automatically fix the FREE_ROUTINE table to match the reality of how routines are allocated.

New QUERY QUEUE OPTIONS menu. A new menu of options related to the Query Queue is added to the SYSTEM STATUS menu. The menu options allow administrators to easily enable or disable the queue, halt a specific task, or print a list of tasks in the queue.

A New XML_SIMPLE format is added for download queries. This release includes a new format that will produce a very simple XML document for a query that produces a tabular result. See the demonstration query DEMO_FORMAT_XML_SIMPLE for an illustration.


KB_SQL QRE Professional

Provide a consistent set of Query functions Whenever we present a list of queries, we will offer a complete set of query functions to the user, including the Open, Delete, Copy, and Properties functions.

Allow Multiple Query selection When the user selects multiple queries, we will offer a limited set of functions to the user, including the Open and Delete functions.

Queue Inspector – Filters In order to make it easier to manage large lists of query tasks in the background queue, we’ll provide the ability to filter the display of tasks in the Queue Inspector. The following filters can be applied:

• Query Name • Start Date • Start Time • Status • Device • Rule • User

The user can apply multiple filters in order to achieve the desired focus on the tasks that are available. The user can print the filtered list of tasks.

Image Inspector – Filters In order to make it easier to manage large lists of query results that are saved as images, we’ll provide the ability to filter the display of images in the File Image Inspector. The following filters can be applied:

• Query Name • Created Date • Created Time • User • Rows • Bytes • Purged Date • Saved Date • File Name

The user can apply multiple filters in order to achieve the desired focus on the images that are available. The user can print the filtered list of images.


Saved Query Lists In order to make it easier to focus on important groups of queries, we’ll provide a grouping mechanism. A group of one or more queries can be placed into a list. The list will be given a name and description. The list will appear in the Query Manager and will support the standard set of query functions. Additional menus will allow the user to manage the lists themselves, including renaming, changing the description, adding or removing queries, or deleting the list. Lists can be expanded or collapsed depending on the focus of the user.

Add Menu Option Support for Saved Query Lists Whenever we present a list of queries, we will allow the user to add one or more selected queries to a new or existing list. As new lists are created, they will appear in the Query Manager.

MyReports The functionality of MyReports will be relocated from the Main menu to the Query Manager as a built-in Query List of the same name. Users will enjoy the consistency of functions available to other lists with the exception of being able to rename or delete the MyReports list.


KB_SQL ODBC Driver

Corrections affect Microsoft SQL Server Integration Services (SSIS) The KB_SQL ODBC Driver was modified to return specific meta-data elements that were critical to the operation of the Microsoft SQL Server Integration Services (SSIS) utility. Note that Microsoft has depreciated the Data Transformation Services (DTS) utility in favor of SSIS starting with SQL Server 2005.


KB_SQL ADO.NET Data Provider

All new data provider provides compatibility with Microsoft ADO.NET The KB_SQL ADO.Net Data Provider is a native driver that allows Microsoft ADO.NET applications to connect to KB_SQL Server. Microsoft .NET Framework Version 2.x is required.


Fixed Items This section has been categorized based on the affected component.

• KB_SQL Server • KB_SQL QRE Professional • KBS Download Agent • KB_SQL ODBC Driver • KB_SQL JDBC Driver • KB_SQL ADO.NET Data Provider • KBS eService Center

Within each section, a table below lists the key items that were fixed in this release. The following information is included: KBS Number This is the unique development database identifier. This value is searchable in the KBS eService Center. Description This is a high level description of the problem.

Answer ID In those situations where additional documentation is available, the information can be found in the KBS eService Center using the Answer ID provided. If you do not have an account to the KBS eService Center, please contact us at [email protected] to request an account. To search the online knowledge base with the provided id:

1. Log on to the KBS eService Center at http://www.knowledgebasedsys.com/support. 2. Select the “Answers” tab.

3. In the “Search Text” field, enter the answer id.

4. Select “Answer ID” from the “Search by” list. 5. Click the “Search” button.

For a complete update of incidents submitted by your company, please log onto our web site at http://www.knowledgebasedsys.com/support and select the “My Knowledge Base” tab.




KB_SQL Server Fixes KBS Number

Description Answer ID

1340 The SITE EDIT procedure will automatically populate the date input format code based on the selected output format.

1339 The SITE EDIT procedure will now restrict the setting of a default date format to those that include the complete Year, Month, and Day only.

1338 Swedish date formats are added, including: YYYY-DD-MM YYYY/DD/MM

1337 The ISO date format YYYY-MM-DD was omitted from the list of acceptable SITE default date formats. This has been corrected.

1336 The COMPILE STATISTICS procedure has been corrected for a problem that could have caused index tables to be skipped when compiling statistics. The logic has been corrected so that all index tables will be counted.

1329 KB_SQL supports a custom feature named MAX_SORTKEY_LENGTH that can be set in SITE EDIT and in individual queries. The default is 30 characters. It can be disabled by setting the value to zero (0). When set, it will truncate all sort key columns to that length. An informational message will be created for queries that invoke this logic and truncate keys. 918: One or more sort keys truncated by MAX_SORTKEY_LENGTH

1307 The DBA MESSAGE LOG, DBA RESET LOG, DBA TX MAINT LOG, and LOGIN FAILURE LOG reports are added to the System Manager menu at \UTILITIES\REPORTS.

1306 For sites that allow null valued expressions, the LIKE predicate will include rows where the tested host expression is null. where value like :xyz When the value of :xyz is the empty string, the LIKE predicate will work the same as the following tests: where value = ‘’ where value like ‘’ Note: This only applies to sites that all NULL valued expressions.

1292 The default value for the "Thru date" prompt is now controlled by the SITE_DEFAULT_THRU_DATE_OFFSET column. The value of the column is initially empty, which results in a default of TODAY. Enter 1 to create a default of TODAY-1.


1285 A new site parameter, SITE_QM_STUCK_THRESHOLD is added to allow customers to control the generation of messages regarding tasks that appear to be stuck in the Queue. The default is 100.

1284 New internal checking was added for queue manager tasks in order to help diagnose situations where a task will not run. This "try" data is reset after successful completion of a task when it is being resubmitted based on a custom start date rule.

1283 In cases where a LIKE expression is used against a host expression and the constraint is not optimized, an error can occur. The error could be cleared if the query was compiled separately, but could recur if compiled as part of a group in COMPILE ALL QUERIES.

1264 A correction was made to the maintenance of failed login attempts. 1214 When a RUN-only user is presented with a list of queries, it may now

include ones that need to be recompiled. If selected, these queries will be recompiled on-the-fly. If errors are found, they will be presented to the user and the query will not run. This change was made to help avoid the problem of queries not showing up on menus because they were not compiled. This feature must be enabled by a SITE setting.

741


1204 System table changes can be tracked using a new audit feature, currently enabled for the following tables: TABLE_ID TABLE_NAME ------------------------------------------------ 201 BASE_ROUTINE 2 CATALOG 6 DATA_TYPE 30 DEVICE 43 DEVICE_TYPE 329 ERRORS 287 FILE_TYPE 198 KEY_FORMAT 67 OUTPUT_FORMAT 3 SCHEMA 1 SITE 53 SQL_API 895 SQL_API_CONNECT_OPTION 767 SQL_API_DATATYPE 56 SQL_API_GET_INFO 65 SQL_API_SQLSTATE 894 SQL_API_STMT_OPTION 441 SQL_CUSTOM_START_DATES 164 SQL_DEFAULT_VALUE 134 SQL_DELIMITER_TOKEN 131 SQL_KEY_WORD 447 SQL_METHOD 846 SQL_TCP_HOST 847 SQL_TCP_PORT 204 SQL_USER_QUERY 215 SQL_USER_TABLE 10 USER 22 USER_GROUP

The feature can be turned on using the \SECURITY\SITE SECURITY EDIT procedure. A report of audit data is available at \SECURITY\REPORTS.

1203 New XML_SIMPLE format is added to provide a simple XML representation of a tabular result set. See the query DEMO_FORMAT_XML_SIMPLE for an illustration.

742

1200 A correction was made to the Foreign Key optimization strategy so that it would not be disabled because of the use of parentheses.

1199 A correction was made to fix the entries in the FREE_ROUTINE table as a part of this release.

1198 The Server API is modified to skip over routines that happen to be defined for other purposes. For example, using the default routine prefix of SQLY, there can be situations where a routine is left over as a result of an error. Now, if the Server API tries to allocate a routine that is already defined, it will simply continue on to assign the next routine in sequence.

1195 A correction was made so that queries are locked for exclusive access when being compiled. This is to avoid collisions when working with high activity volumes being run through the Server API.

1194 A correction was made so that queries are locked for shared ("Run") access when being executed via the Server API.


1193 A correction was made to the Server API so that high activity volume would not cause routines to be allocated to two or more queries.

1185 An error was corrected with the Server API so that it will name queries and routines correctly when using a 4 digit suffix. Note that when allowing this many routines, it works best if the routine name prefix is only 1 or 2 characters in length. For example, using the prefix 'AA' for 9999 queries is ok.

1184 An error was corrected that caused the TABLE PRINT report to show obsolete data. This would happen if the table data was changed in between runs of the report in a single session.

1183 An error was corrected so that the READ prompt handler would use the output size rather than the internal storage size. This was preventing the input of certain DATE and TIME values.

1175 An error was corrected so that we will no longer create an empty string for the COLUMN_LABEL value in the QUERY_DESCRIBE table.

1164 Errors could occur when the internal array of diagnostics information became full. The individual error variable (SQLERR) is now removed from the symbol table when the diagnostics array is full.

1160 Removed non-working “Clear” option from the QREPro Screen Preview area.

1157 An error that returned weekend days for functions designed for weekdays has been corrected.

1131 A correction was made to the table statistics compiler so that MSE Tree-3 data was accurately counted.

1130 If either of the Background Query or Table Statistics system locks is set, the SYSTEM STATUS window will display the message text as “[LOCKED]”.

1129 A new menu option is added to the SYSTEM STATUS procedure. The new option is QUERY QUEUE options and includes tags to Enable or Disable the queue, edit a task, or print the task list.

1067 Certain error conditions are now detected and reported to avoid compilation errors. Previously, these error conditions were overlooked and could lead to confusing behaviors.

991 A problem was corrected that could have corrupted the display of physical column listings in the TABLE PRINT Report.

981 A conversion utility is included in this release that will clean up the BASE_ROUTINE and FREE_ROUTINE tables. This will ensure that the maximum number of routines is available for use and that no routine will be allocated more than once.

978 A problem was corrected that allowed the FREE_ROUTINE table to contain names of routines that were allocated to queries.

917 There should no longer be any local variables holding clear text password values after they have been used. This is an effort to avoid showing passwords via system utility functions that show the process variables to system administrators.


694 A correction was made to the Queue Manager so that it will not be hung up if it encounters two or more adjacent tasks that cannot be opened. This can happen when a query is open for edit at the time when the task is ready to run. Now, these tasks will be skipped allowing other tasks to run.

285 The Query Transaction Log reports will now accept a range of TIME values to limit the scope of the report.

260 The TCP/IP testing utility, TEST^SQL0TCP, is corrected for the MSE, HBOM, and M21 versions. These environments present a limitation involving multiple open connections. The utility can be used for testing with one (1) connection only. The utility is useful for testing connectivity to the KB_SQL Server. D TEST^SQL0TCP| KB_SQL Server Connect Test Server Name or Address: 192.168.1.110// Port Number : 8090// UserName : dba PassWord : Connection limit : 4//1 Connecting to 192.168.1.110 (8090) Connected to #1: 8060~192.168.1.110~8094~30~~~2~~~~~2048 Disconnecting #1: 8060~192.168.1.110~8094~30~~~2~~~~~2048

29 The GTM Socket interface is implemented in this release. 8 A correction was made to the JOB WATCH utility so that it would

correctly invoke the UNDO function on an active process.


KB_SQL QRE Professional Fixes

KBS Number


1335 The folder type (Dynamic or Static) and description will show when the cursor hovers over the Query folder name in the Query Manager.

1334 A new option on the Query Folder menu allows the edit of the description.

1333 The option for deleting a query folder is renamed from “delete” to “remove” in order to reserve the more ominous “delete” option for permanently removing queries from the database.

1332 The default answer will be “NO” when attempting to delete a query folder.

1331 The default answer will be “NO” when attempting to convert a query folder from dynamic to static.

1324 The Table|Copy|Select All Query function is corrected to be more efficient. In cases where the table had many columns, this feature was quite slow.

1314 A message will be displayed when the user has created the maximum number of Query Folders.

1303 If a query folder was created as dynamic, and then converted to static, but never opened, the folder would be empty. We have modified the conversion process to always populate the folder to ensure that the contents are up-to-date when the folder is converted to a static list.

1301 File Image Inspector filter icon will show “green” when filters are defined, and “red” when no filters are defined. The color is now correctly set when re-opening the inspector after it was closed.

1300 Queue Inspector filter icon will show “green” when filters are defined, and “red” when no filters are defined. The color is now correctly set when re-opening the inspector after it was closed.

1296 When viewing a Query Folder, the user can select queries to add to another static folder, but the results cannot be used to create a new dynamic folder. This sort of recursive definition is not allowed.

1297 When changing the search type using the Query Search control, the new folder options will be dimmed out and not accessible.

1295 When searching for queries by [Table] or [View], the user can now specify the schema name qualifier using the format [Schema.[Name]].


1294 When searching for queries by [Name] in the Query Search control, the user can enter ‘*’ for a listing of all queries. The ‘*’ is meant to be supported as a special search for query names only and is not allowed to create a new dynamic folder from the result listing.

1291 We are consistently referencing the “My Reports” folder by the correct display name.

1290

When using the Query Search results to add queries to static folders, the user will see a progress dialog. It can be cancelled. A listing will appear at the end to show the queries added to the folder.

1289 The curly brace characters {} are recognized by the colorized syntax parser of the Query Editor. They appear as endpoints like parentheses and quote characters.

1287 The ‘My Reports’ folder will appear at the top of the list, along with other built-in folders. All user-defined folders will follow.

1282 Renaming a query folder did not make all of the formatting checks that were done when creating a folder in the first place. This could lead to the use of illegal names for query folders. This has been addressed.

1280 Dynamic query lists based on a search of query text where the search term contains space characters could return unexpected results. This was due to the spaces being incorrectly removed from the token prior to the search. This has been resolved.

1278 Certain dynamic query lists could return unwanted query names due to wildcard evaluations. For example, the search on ‘DEMO_’ needed to include the search pattern escape character when creating the search token as ‘DEMO\_’. This is now corrected.

1274 When using a query search list to edit query name with the “Properties” option, subsequent attempts to work with that row of the query list would generate an error. This is now corrected.

1249 A 3rd color (yellow) is added to the filter icon in Image and Queue Inspector to show that filters exist, but a refresh is required.

1234 Once open in the query editor, a query can be associated with a query folder. A new menu option is added.

1227 When you attempt to open a query folder that has no queries, there will be a message to let you know that the folder is empty.


1226 Queries can be opened by dragging a query reference from a list onto the QRE desktop. If the package is dropped into the grey area of the desktop, this will open the query in the query editor. Previously, if dropped into the white area of an editor, the object signature would be inserted as text into the query. To avoid this, always drop onto the grey area. This has been corrected.

1216 The Navigator could crash if a 2nd connection could not be achieved. We will now use the primary connection to avoid this complication. As a side effect, this allows using the Navigator functions while running the server in foreground for debugging.

1215 The SAVE method of the SQL_FILE_IMAGE Export Method will now reference the SITE Custom Execute for host file names.

1212 Users without query save rights cannot edit or delete queries, or save query properties.

1197 A correction was made to the READ prompt handler to avoid leaving input values un-saved. The [Ok] button is no longer set as the default button. Pressing the [Enter] key will have no effect unless the user has selected the [Ok] button.

1192 The functionality of the MyReports option has been relocated to a special “built-in” saved list of queries.

744

1191 Menu options expose the functions available for working with saved lists of queries.

1190 A new feature allows the user to save lists of queries in folders that will appear in the Query Manager window.

738

1189 The File Image Inspector is modified to support filters. These filters apply to the Refresh and the Print functions.

740

1188 The Queue Inspector is modified to support filters. These filters apply to the Refresh and the Print functions.

739

1187 When presented with a list of queries, the user can now highlight multiple queries to be Opened or Deleted as a group. Previously, the user would have had to perform the actions one at a time.

1186 Whenever a list of queries is presented, the user will have access to the same set of actions, including: - Open - Delete - Copy - Properties Note that when the user highlights two or more queries, the Copy and Properties options will not be accessible. Note also that Run-only users will only have access to the Open option.


1182 The line number display option of the query editor has been disabled.

1180 The Explorer column list window can no longer be minimized. The window can be resized to allow for readability but it cannot be minimized and left in an active state.

1172 A correction was made to the filename references for certain Windows Program Group entries.

1169 Bug: Include query name in error message window for parse 1168 An option to allow splitting of editor windows has been

disabled.

1167 The query name field will no longer accept characters other than alpha (A-Z,a-z), number (0-9), and the underscore character. Note that the entry of the space character will be converted on input to the underscore character. This is to avoid creating illegal query names.

1166 The Shifted drag and drop of a column name from the Explorer will now correctly include the qualified table name reference. For example, using Shifted drag and drop on the NAME column from the EMPLOYEES table will drop in the text "EMPLOYEES.NAME".

1163 Bug: Filename input ignored by output selection 1162 An error that allowed a Run-only user to Copy and Create

queries has been corrected.

1151 File Image Inspector will restrict the [Save] operation to files that are smaller than 500mb.

1142 A correction was made to restrict a Run-only user from overwriting existing queries.


KB_SQL ODBC Driver Fixes KBS

Number


1153 A correction to the metadata for column information has been made to support the Microsoft SQL Server Integration Services (SSIS) utility.

Note: The KB_SQL ODBC Driver v4.6 requires the latest version of the KB_SQL Server v4.6.


KB_SQL JDBC Driver Fixes KBS

Number


Note: The KBS JDBC Driver v4.6 requires the latest version of the KB_SQL Server v4.6.


KB_SQL Download Agent Fixes KBS

Number


Note: The KBS Download Agent requires the Java Runtime Environment (JRE)


KB_SQL ADO.NET Data Provider Fixes KBS

Number


1342 The KBSDbConnection class was not closing the connection properly for database metadata calls.

1341 Corrected the handler for the KB_SQL FLAG (Boolean) data type values.

1204 Implement KB_SQL ADO.NET Data Provider. 737 Note: The KB_SQL ADO.NET Data Provider requires the Microsoft.NET Framework 2.x.


KBS eService Center Fixes KBS

Number


n/a Answer searches should be more refined now that “all” keywords are required instead of “any”.

n/a The question listing allocates more space to the Subject field making the result more readable.

n/a The question listing will show more items (10) per page. n/a The new question input area is now larger to make it easier to

enter the information.

n/a The font for questions is changed to use CourierNew so that code formatting is left intact. We still encourage using a Notepad file if you really want to be clear in your communication about a code block and it might be obscured using this interface.

n/a The table of questions is expanded to make better use of the available display space.


Known Problems Below are some of the known problems that still exist in this release. For updates on these or other known problems, please visit our website.

KB_SQL Server Known Problems KBS

Number

Customer Incident # Answer ID

1179 Alias can be rejected if name matches a site-defined pseudo column name. To ensure that column names are not confused with site-defined keywords, use a table alias. To ensure that pseudo columns are not confused with column names, use open and close parentheses.

1161 Just-in-time compilation (at compile time) can fail. Under certain situations where queries have a combination of features, they might fail to compile when requested by the compile-time just-in-time compiler.

1019 Views with fully qualified columns can generate ‘818: Fixed value Predicate’ errors. We have duplicated the "Fixed value predicate" error with the following queries: CREATE VIEW AA (EMPNAME) AS SELECT SQL_TEST.EMPLOYEES.NAME FROM SQL_TEST.EMPLOYEES SELECT * FROM AA WHERE EMPNAME IS NOT NULL As a workaround, please do not include the schema name on the reference to the columns in the SELECT clause.

955 The LIKE and FIND functions can fail to find strings when the value is split across nodes in the temporary storage area. This can sometimes be overcome by using a large value for the GVMAX setting.


KBS Number

Customer Incident # Answer ID

874 SQLColumns reports incorrect COLUMN_SIZE for view columns based on expressions. This error manifests itself in MSAccess by retrieving only 20 characters (the default size) for view columns based on expressions. The problem is that SQLColumns can only retrieve the column size from the base_column definition. In the case of an expression, there is no base_column reference.

760 In some circumstances, when a query is run from the background queue, and that query has to be compiled, the query can run without being “locked”.

712 The query planner can sometimes consider “bad” plans despite an apparently high setting for the COST_CEILING parameter.

614 In some cases, illegal event block command references can go unnoticed by the SQL language parser. An example is the typo “INTIAL” meant to be the INITIAL event. The parser goes right past this without a warning.

572 In some cases, tables submitted to the statistics queue using a non-zero sample size can remain in the queue, trying over and over to calculate stats.

455 In some cases, views using an outer join query that includes a constraint on the non-preserved table, can fail.

363 Accessing tables with 'Programmer Only' columns via SQL Server linked server can return the following message:

Server: Msg 7355, Level 16, State 1, Line 3 OLE DB provider 'MSDASQL' supplied inconsistent metadata for a column. The name was changed at

execution time.

508

92 The QUERY_COMMAND table (72) can sometimes grow without bound when processing of DML queries against user defined tables. We have added some controls to try to limit this problem, but don’t have the full correction.


KB_SQL QRE Professional Known Problems KBS

Number


1299 It has been requested that we add an icon to the toolbar for access to the Queue Inspector filter options. Currently, this option is available through the View|Filter option.

1298 It has been requested that we add an icon to the toolbar for access to the Queue Inspector filter options. Currently, this option is available through the View|Filter option.

1277 The queries shown in the query search list will not collate as expected for names containing adjacent underscore characters. This is due to a limitation in the Windows listview control.

1211 QREPro maintains an open connection for the duration of the active session even when no database work is being requested.

805 There is a pop-up menu including options such as ‘Delete’ that is raised from a right click after using the File|Open Query option. When the same functionality is raised from the Query Manager “Search” option, the pop-up options do not appear.

759 There can be a number of blank lines apparently “wasted” at the bottom of the Table Print when printed from QRE Pro.

749 From the Dictionary Explorer, the refresh date and time details are not always correct.

526 The “Mark All” feature doesn’t always clear previously marked items when doing additional searches.

150 If the TCP/IP connection is broken, QRE can become unresponsive.


KB_SQL ODBC Driver Known Problems KBS

Number


1159 When the ODBC Driver is asked to create many thousands of Statement handles for a single connection, memory can be corrupted. This has been seen to occur when using the ODBC.NET Data Provider especially in Microsoft.NET Framework version 1.x.


KB_SQL JDBC Driver Known Problems KBS

Number



KB_SQL Download Agent Known Problems KBS

Number



KB_SQL ADO.NET Data Provider Known Problems KBS

Number


1253 KB_SQL ADO.NET controls cannot be added to some Express editions of Microsoft Visual Studio products.


KBS eService Center Known Problems KBS

Number


1309 After KBS updates an incident, the KBS eService Center queues up a notification to send to the user by email. In some cases, these messages can be delayed by internal processing issues, email glitches, and network traffic. If you are looking for a reply that hasn't arrived, please check the status of your incident directly in the KBS eService Center.

1308 In some cases, incident responses are not processed correctly by the email gateway. The response is entered between the lines, but the incident sees the entire email including headers and other irrelevant text. Use the KBS eService Center at www.knowledgebasedsys.com/support to modify your incidents.



This page intentionally left blank.


kb sql release notes version 4 - oracle · kb_sql release notes version 4.6 knowledge based...

Documents