Actian Zen PSQL v13

Patch Release - 12/11/2017

Install Build version 13.01.010
Components Build version 13.01.005

Products

This patch applies to the following Actian PSQL products:

Executables

These patch notes apply to the following executables:

By default, these updates create a patch installation log in the %temp% location. If instead you are using an .msp file extracted from one of these executables, then to create a log file when applying this patch, run the patch executable from a command line with the /l option. In the following example, the patch update creates a verbose log file named patch_install.log:

PSQLv12Patch_type.msp /l*v <path>\patch_install.log

Uninstalling Notes

On Windows systems, in most cases a PSQL patch update can be “rolled back” by uninstalling it. This removal restores PSQL binaries to their versions before the update. (See the note below about unremovable patches.)

To uninstall a product update for PSQL from the command line, you need the following:

·         Original installation package (.msi) or the Product Code GUID for the installation. Each PSQL install type has a different product code GUID.

·         Original Microsoft patch (.msp) file.

Either of the following commands can remove a product update:

·         msiexec /package <{path_to_MSI} or Product_Code_GUID> /uninstall <path_to_MSP> /l*v "%temp%\uninstall_patch.log"

·         msiexec /i <{path_to_MSI} or Product_Code_GUID> MSIPATCHREMOVE=<path_to_MSP> /l*v "%temp%\uninstall_patch.log"

Note that the user executing the command must be able to access the source files installed by the original PSQL installation.

Note: In certain cases, a PSQL patch cannot be removed. A warning message states “Uninstallation of the patch package is not supported,” which also is entered in the installation log file. If the patch must be removed, first uninstall PSQL entirely and then reinstall the version you need, along with the appropriate patches.

 

Issues Addressed

Specific issues addressed in this patch release (Build 13.01.010):

 


 Tracking Number


Description

PSQL-4300

PCC is not closing the JDBC sessions associated with its main screen correctly

PSQL-4628

With Forward only cursor SQLExecute may not double the number of rows with an “INSERT INTO tbl SELECT * FROM tbl” statement

PSQL-4720

PSQL System SP psp_columns call returns “not nullable” for legacy tables

PSQL-4747

Psql Odbc Unicode driver may return only first Japanese character of the error message

PSQL-4859

Engine may Incorrectly spawn extent file though limit Segment Size setting is disabled

PSQL-5002

ORDER BY with COLLATE on SELECT statement may return incorrect results first time run

PSQL-5060

High connection load may buildup handles for login credentials can result in memory leaks

PSQL-5098

Manual authorization may return Status 7113 for a valid Workgroup deployment

PSQL-5168

select @@spid may return the same id number on a second connection on Linux

PSQL-5191

BUTIL syntax output is missing a <cr><lf> at the end of the BUTIL -ROLLFWD line

PSQL-5262 

Partial Index attribute is not properly displayed in PCC for multi-segment partial indexes

PSQL-5263

][SQL Engine][Data Record Manager] (11390) error may be returned when using Dynamic cursor with "SELECT TOP/LIMIT"

PSQL-5269

Incorrectly defined PSQL system tables may crash PSQL engine in some cases

PSQL-5279  

TCP is now the only supported communication protocol

PSQL-5308

Engine may not return all the records when a string constant part of a segmented key is longer than the field length

PSQL-5333 

“Error in Expression” should be returned in queries that have non-uniquely identified columns

PSQL-5347

Large query with CASE and many "OR" may hang the engine

PSQL-5387

Trigger may not work if the database path format in the connection string doesn't match with dictionary path

PSQL-5392

Corrected to return error on merge-able views without uniquely identified columns

PSQL-5407

A Btrieve file may divide at 4GB if the engine is running under an account that does not have sufficient rights to query the hard drive configuration

PSQL-5447

“Duplicate column found in insert list.” was not being returned in some cases

PSQL-5462

Results may be sorted incorrectly when ORDER BY includes an aliased column listed after table.* in the select list

PSQL-5495

PCC Export data should export embedded double quotes in strings with two double quotes

PSQL-5522

SQL engine may not optimize on an available index for a restriction using IN

PSQL-5546

ALTER RENAME can allow objects to be renamed in a secure db by a user without Alter rights

 

 

 

 

Previous issues addressed since release PSQL v13.00


 Tracking Number


Description

PSQL-3992

Export Table Schema in PCC fails to export default if it is a single space

PSQL-4633

Possible hang in the  SQL Manager when many connect requests come in from different clients at the same time

PSQL-4808

Bulk insert via ODBC with multiple dynamic parameters set to be null may cause the engine to crash

PSQL-4832

Incorrect results returned using multiple restrictions on an indexed date column with different operators, such as = and BETWEEN

PSQL-4856

64-bit SQL engine may crash with very large query involving 2000+ conditions in the WHERE clause

PSQL-4864

IN subquery on columns with different data types (such as VARCHAR and INTEGER) may never return

PSQL-4969

Incorrect number of rows may be returned when non-leading index segment is defined as CHAR when ansi_padding is off

PSQL-4981

"SELECT * FROM X$User" is slow to return when USER.DDF is missing

PSQL-5006

Abnormally ending a SQL connection on a Linux server may cause other connections to crash

PSQL-5033

Complex query generating multiple temp tables with nested table subqueries returning a LONGVARCHAR column using a forward-only cursor may crash the SQL engine

PSQL-5060

Excess handles allocated and not released due to legacy delay in communication components.

PSQL-5078

SQLColumns may return multiple instances of columns in some cases with very large databases

PSQL-5101

PCC should prompt to restart engine when changing the “Use Cache Engine” setting

PSQL-5148

Query with CASE in the outer SELECT list and the SELECT list of a table subquery may crash the SQL engine

PSQL-5154

BDU may return "DataLoader | 22: The data buffer parameter is too short" when the data file has many keys.

PSQL-5163

Status 84 may be returned after issuing a SELECT FOR UPDATE query that has an empty result set

PSQL-5164

Updated Setup<product_type>_<platform>.exe launchers address an error 1723 during install

PSQL-5171

Buffer overflow not detected on direct communication to port 1583/3351

PSQL-5185

Corrupt file causes a divide by zero crash in the MKDE

PSQL-5190

Old PSQL Logo displayed in PCC Preferences

PSQL-5193

Actian PSQL Perfmon counters are not properly registered after upgrade install

PSQL-5194

PSQL install/patch on Windows 10 with limited resources uses 100% CPU and does not terminate properly

PSQL-5208

Complex query with CASE and table subqueries with joins may return a Syntax Error

PSQL-5217

BDU is not properly handling empty strings and null entries from import file

PSQL-5247

Status 5 returned when creating a table in a database where X$Field already has an ID=65535

PSQL-5248

Add support for PARTIAL index in Schema Export/Import

 

Technical Support

You can obtain technical support from several online options at the PSQL website:

  • Knowledge Base. Search hundreds of articles for answers and solutions others have found useful.
  • Community Forums. Join a technical discussion or post a question to start a new one.

Disclaimer

ACTIAN CORPORATION LICENSES THE SOFTWARE AND DOCUMENTATION PRODUCT TO YOU OR YOUR COMPANY SOLELY ON AN "AS IS" BASIS AND SOLELY IN ACCORDANCE WITH THE TERMS AND CONDITIONS OF THE ACCOMPANYING LICENSE AGREEMENT.

Copyright ©2017 Actian Corporation. All Rights Reserved.