| W51007 for Windows for x64 |
| Data Integration Studio 4.901 |
| Issue(s) Addressed: | Introduced: |
| 56896 | The Validate Expression action fails and incorrectly reports an invalid expression in Extract transformations in SAS® Data Integration Studio |
W51001 |
| 57131 | SAS® Data Integration Studio jobs that contain an SQL subquery lose subquery metadata after you run the Analyze and Repair Tool |
W51001 |
| 52087 | SAS® Data Integration Studio jobs fail with errors due to metadata server connectivity issues |
W51001 |
| 56746 | The Expression Builder in SAS® Data Integration Studio incorrectly modifies expression content, which might result in run-time errors |
W51001 |
| 56809 | Expressions defined in the SQL Join transformation in SAS® Data Integration Studio are incorrectly modified, which might result in run-time errors |
W51001 |
| 56899 | The Validate Expression action fails and incorrectly reports an invalid expression in File Reader and File Writer transformations |
W51001 |
| 56918 | When you create a new column in SAS® Data Integration Studio, the Expression Builder window fails to open, and a null pointer exception error occurs |
W51001 |
| 56919 | Deleting a table in an SQL Set Operators transformation causes jobs to fail in SAS® Data Integration Studio and returns a null pointer exception error |
W51001 |
| 56926 | The Wait for Completion transformation in SAS® Data Integration Studio fails with the error "No mappings are defined for one or more target tables" |
W51001 |
| 56998 | Jobs that are redeployed in SAS® Data Integration Studio might fail with the error "...Unable to find the Application Server for this file..." |
W51001 |
| 57010 | Performance might be affected when you open and display data in the View Data window in SAS® Data Integration Studio |
W51001 |
| 57103 | Performing command-line batch deployments in SAS® Data Integration Studio generates code that contains USER= and PASSWORD= instead of AUTHDOMAIN |
W51001 |
| 57108 | SAS® Data Integration Studio command-line batch deployments fail and return the error "Unable to initialize the metadata factory" |
W51001 |
| 57202 | Business Rules transformation options in SAS® Data Integration Studio do not persist in the metadata when the job is saved |
W51001 |
| 57204 | The Import SAS Code wizard in SAS® Data Integration Studio creates duplicate tables when registering a table |
W51001 |
| 57299 | A SAS® Data Integration Studio job containing a parameter defined as data library with a SAS® library selected as default generates incomplete code |
W51001 |
| 57313 | The Create Table transformation in SAS® Data Integration Studio 4.901 does not contain options for Database pass-through |
W51001 |
| 57320 | The Enterprise Decision Management transformation in SAS® Data Integration Studio does not support Hadoop tables as input or output |
W51001 |
| 61642 | A grid option set that you select in the SAS® Data Integration Studio 4.901 Loop transformation is not applied at SAS® Grid session launch |
W51001 |
| 61659 | Code execution fails with "ERROR: The HADOOP table...already exists, or there is a name conflict with an existing object..." |
W51001 |
| 58270 | Metadata support for SAS/ACCESS® Interface to Amazon Redshift |
W51002 |
| 56172 | Disabling a cube in SAS® OLAP Cube Studio or SAS® Data Integration Studio might fail if you are using a load-balanced SAS® OLAP Server |
W51002 |
| 59569 | Some database management system library options are omitted from explicit SQL pass-through code in SAS® Data Integration Studio |
W51003 |
| 59403 | "Error reading metadata: Insufficient memory" occurs when you rename a library in SAS® Data Integration Studio or in SAS® Management Console |
W51003 |
| 59936 | The SAS® Data Integration Studio Hive transformation automatically deletes the target table |
W51003 |
| 59942 | The SAS® Data Integration Studio Join transformation generates incorrect code for cross-schema joins of tables using the Hadoop LIBNAME engine |
W51003 |
| 59960 | The Target Table Pass Through Action property in the Join transformation generates improper code |
W51003 |
| 59961 | The Target Table is Pass Through property in the Set Operators transformation generates incorrect code |
W51003 |
| 57962 | The SAS® Data Integration Studio SCD Type 2 Loader transformation generates errors when loading data into an external DBMS |
W51004 |
| 60579 | Performing command-line batch deployments in SAS® Data Integration Studio generates code without performance-statistics macros |
W51004 |
| 60595 | Connections between work tables and database libraries are incorrectly removed when these objects are included in metadata import processing |
W51004 |
| 61015 | Redeploying a stored process returns the "Cannot redeploy because there is no job metadata associated to this stored process" message |
W51004 |
| 60622 | Redeploying a job using SAS® Management Console fails with the "UNKNOWN_ORIGINAL_SOURCE_FILE" error when the deployed job is defined by importing |
W51004 |
| 62579 | You see "...Invalid object name..." after PROC SQL pass-through code creates an INSERT statement that excludes ## symbols from a temporary table name |
W51005 |
| 58469 | When you import a SAS® Data Integration Studio job containing a Lookup transformation, "Error: Lookup has no target column mapping information" occurs |
W51007 |
| 66134 | SAS® Management Console contains an XML External Entity (XXE) processing vulnerability |
W51007 |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
General Information about Hot Fixes