Aginity Workbench for PureData System for Analytics 4.9 Release Notes – aginity

hese release notes summarize the changes in Aginity Workbench for PureData System for Analytics version 4.9. The release notes also contain system requirements and list the known issues with the release.

What's New? (Also See Full List of Changes)

Aginity Workbench version 4.9 contains a number of bug fixes.

Technical Details and Changes

This section contains details of specific functions and changes that are included in Aginity Workbench 4.9.

Upgrading from Prior Versions

Workbench automatically checks for new updates and displays a dialog box if an update is available. In the dialog box, select Install this update now to download and install the update.

You can also choose to postpone installation of the update until the next time you run Workbench or suppress the update alert.

You can also check for updates manually by clicking Check for Updates on the Help menu and then install an available update by following the instructions in a wizard.

Hardware and Software Support

Aginity Workbench has been tested against Netezza Platform Software (NPS) versions 7.2.1.3-P3, 7.2.0.3-P2, 7.1.0.4-P2, and 7.0.4.6-P3.

System Requirements

Windows XP or later
Windows Installer 3.1
.NET Framework 4.6.1
ODBC (recommended) or OleDB driver. (Drivers must be 64-bit for 64-bit Windows or 32-bit for 32-bit Windows.)
Memory: 256 MB RAM
Disk space: 100 MB, plus any necessary space for .NET Framework and Windows Installer

Full List of Changes Since Aginity Workbench 4.8

Bug Fixes in Build 4.9.1.2686

Severity	Reference	Description	Existed Since Version	Resolution
Moderate	15391	The User ID field is not visible on the connection dialog box after a user changes the 100% display setting to a larger setting.	2.5	The User ID field is visible on all display settings.
Minor	16045	The Discussion Forums menu item exists for the deprecated Aginity Forums.	2.4	The menu item was modified to go to the Aginity Community web forums.
Minor	16306	When importing an Excel file, the Data Import Wizard stops loading rows from the file on the first blank date field. Success is logged for the import job in this case.	2.5.1	Blank date fields are correctly processed, and an whole Excel file is properly imported.

Known Issues in Build 4.9.1.2686

Severity	Reference	Description	Workaround
Major	APD-5627	When importing DB2 tables from an external database, an error may occur indicating that Length cannot be less than zero.	Install the DB2 client on the client machine so you can successfully connect to a DB2 database.
Major	APD-6627	When importing data that includes dates from Excel using the Data Import Wizard, the Data Import Wizard fails to properly identify dates automatically and fails to load dates when manually configured to do so.	Set the column in Excel to text instead of date so you can load the data.
Moderate	APD-1939	A DDL (delta) script generated by the Compare Schemas tool fails with an error if the same table in the source and target schemas contains a foreign key to different tables. The error occurs because when applying the foreign-key update to the target schema, the script first drops the old referenced table in the target schema and then attempts to drop the foreign key to the previously dropped table.	Choose one of the following two workarounds, depending on whether you prefer to generate one or two delta scripts. Workaround 1: Generate one delta script Open the source and target schemas in the Compare Schemas window. Click the appropriate Alter Script button to initiate script generation. In the Generate Delta Script Options window, under Entities to Script, select the Drop these entities check box and select appropriate check boxes under Create these entities and Modify these entities. Save the generated script to a file. Locate the DROP TABLE statements within the script and move them to the end. This will ensure that the foreign key is dropped before the old referenced table. Run the script against the target schema. Workaround 2: Generate two delta scripts Open the source and target schemas in the Compare Schemas window. Click the appropriate Alter Script button to initiate script generation. In the Generate Delta Script Options window, under Entities to Script, clear the Drop these entities check box to not drop any tables, and select appropriate check boxes under Create these entities and Modify these entities. Save the generated script to a file. Generate a delta script for the schemas again, selecting the Drop these entities check box this time. Save the script to another file. First run the script file created in step 4 and then the one created in step 6.
Moderate	APD-6633	When working with multiple schemas with views and tables that have the same name, the population of fields in the drop-down list does not respect the default schema selection.	Avoid using the drop-down list when working with multiple schemas with duplicated view/table names.
Moderate	APD-6835	When selecting vertical blocks of text (as opposed to full lines) and using the Make selection UPPER/lower case function, the selected text is shifted vertically.	Manually adjust the lines.
Moderate	APD-5471	Installation of Workbench on Microsoft Server 2012 fails on the prerequisites.	Do a "Add Features" for .NET 3.5 (which includes 2.0) in the Server Manager.
Moderate	APD-5973	You cannot import from views when using the remote database import from Microsoft SQL.	N/A
Minor	APD-6163	In Standard mode in the Output area, some SQL statements are inadvertently omitted. However, they are correctly displayed in Grid mode.	N/A
Trivial	APD-3711	When the field type is Date, the year 0 (for example, 0000-01-01) causes an error “Year, Month, and Day parameters describe an un-representable DateTime.”	Either cast the date as a VARCHAR or do not use the year 0.

Articles in this section