Actian Zen PSQL v13 SP1

Patch Release - 7/27/2018

Install Build version 13.11.014
Components Build version 13.11.010

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:

PSQLv13Patch_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.11.014):


 Tracking Number


Description

PSQL-5943

PSQL engine can now return  values in nanoseconds when TIMESTAMP values are added or subtracted

PSQL-5968

Alter table Add with Default String using Unicode driver can return incorrect  values

PSQL-5994

Create table after setting a default collating sequence can crash/close the engine on Linux

PSQL-6009

PDAC can return status 35 if both local mapped Drive Letter and DDF location for the database on the server are the same

PSQL-6012

PCC may not return all results in Grid if the Select query includes subquery

PSQL-6024

After a cold reboot all PARC connections may not reopen

PSQL-6028

ALTER TABLE with PSQL_MOVE should not affect the data file when PSQL_PHYSICAL is not specified

PSQL-6035

Engine can return status 103 when updating multiple non-nullable variable length columns in a single table

NA

PSQL V13.11 update 3  is tested with Windows 10 April 2018 Update

 

Previous issues addressed since release PSQL v13.10:


 Tracking Number


Description

PSQL-5035

Substring with out of range parameters may not return correct results

PSQL-5104

Updated the reporting engine so that it can no longer be accessed from a remote client due to licensing issues

PSQL-5392

Select from joined views with ambiguous column references should return an error

PSQL-5446

Insert into view with incorrect number of values should return an error

PSQL-5462

SELECT <table name>.*, C1 followed by an ORDER BY on C1 may not sort results correctly

PSQL-5469

Select with “like '%\%\%\%%” may not find values with three consecutive % characters

PSQL-5495

PCC exports data with embedded double quote characters (") incorrectly; they should be exported as ""

PSQL-5503

Errors returned from a Btrieve Extended Operation using the “LIKE” operator are not written to PVSW.LOG

PSQL-5520

SQL Query from a client using a static cursor may be slower than a forward-only cursor

PSQL-5522

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

PSQL-5538

Table schema export is not including the ISR collation

PSQL-5546

A user without ALTER rights should not be allowed to rename objects in a secured database

       PSQL-5499

The Kanji folder name in the PVSW.LOG on a Japanese OS is sometime not readable

       PSQL-5552

Performance improvement for processing an IN subquery with mismatched datatypes

PSQL-5598

Visual Studio Integration service using the non-Unicode ODBC driver may return garbled database names

PSQL-5625

The command line phone authorization utility (clipaadm/w64clipaadm) may freeze on some Japanese machines

PSQL-5629

Query with three or more joined tables and a subquery may not be optimized when using a Forward Only cursor

PSQL-5630

Export Schema may return "No match available" when exporting a database that has COLLATE in a column name

PSQL-5631

ADO.NET provider may return "Input string was not in a correct format" when updating a DataGrid

PSQL-5658

SQLBindParameter error may occur when executing the same statement with different values in a python ODBC application

PSQL-5678

Calling a User Defined Function with a non-ASCII character in its name in a database with a non-default code page may return “Invalid user-defined or scalar function”

PSQL-5689

Possible SQL engine crash due to non-unique temp table names generated by the engine

PSQL-5711

Incorrect file name created when using non-ASCII characters in the name passed to the FileCreate method of the Btrieve 2 API via Python 3.x

PSQL-5717

GetCurrentDirectory using Btrieve 2 API via Python may return corrupted strings when the current directory contains non-ASCII characters

PSQL-5718

SQL Engine may crash on a query with the same column repeated >250 times in the ORDER BY

PSQL-5730

Possible engine crash when one connection handle tries to drop a table that is in use, and another connection tries to fetch data from the table.

PSQL-5747

PARC and Wire Encryption (Always) enabled  may affect ODBC performance

PSQL-5763

“Unknown provider error” when inserting/deleting data through MS Linked Server 2016 and later

PSQL-5777

Engine may hang using Backup Agent to backup files which are under defragmentation

PSQL-5778

Select query with segmented index with a varchar column with more than 255 bytes may return incorrect data

PSQL-5804

PSQL Engine may crash if the temporary index created for an ORDER BY/GROUP BY/DISTINCT/etc. is more than 250 bytes and the query uses Static/Dynamic cursor

PSQL-5811

Improved Cache Engine Performance on first read

PSQL-5844

CREATE/DROP/ALTER table with IN DICTIONARY may update existing PK/FK relationships incorrectly

PSQL-5856

Incorrect client version format in a JDBC connection string may crash the engine

PSQL-5880

Complex query with a view using several outer joins may crash the engine

PSQL-5882

Added PDAC support for RAD Studio V10.2(Tokyo)

 

 

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.