Hot Fix Downloads for Solaris for x64
General Information about Hot Fixes
C63001 was replaced by C63005 |
C63002 was replaced by C63005 |
C63003 was replaced by C63005 |
C63004 was replaced by C63005 |
C63005 for Solaris for x64 | |||||||
SAS Data Integration Studio Server Data 9.2_M2 hot fix for SAS Data Integration Studio 4.21_M2 | |||||||
Issue(s) Addressed: | Introduced: | ||||||
40452 | "ERROR:CLI execute error...Invalid object name..." occurs in the SCD Type 2 Loader transformation when loading data to a Microsoft SQL Server database | C63001 | |||||
40532 | An exception occurs when migrating or importing a SASŪ Data Integration Studio job | C63001 | |||||
40556 | Using the Generate Indexes on the Target Tables transformation option can cause unexpected results | C63001 | |||||
40570 | Descending sort order asscociated with columns in the Extract or SQL Join transformation is lost after a migration or import to SASŪ 9.2 | C63001 | |||||
40571 | "An invalid format is specified" error occurs in the Mining Results transformation | C63001 | |||||
40572 | Large SASŪ Data Integration Studio jobs open slowly | C63001 | |||||
40632 | A new SASŪ Data Integration Studio 4.2 option on the Table Loader transformation Load Technique tab affects _LOADTM column updates in the target table | C63001 | |||||
40633 | "Table WORK.Wnnnnnnn.DATA does not exist" error occurs in SASŪ Data Integration Studio jobs that use the Loop transformation | C63001 | |||||
40769 | An incorrect configuration warning occurs when logging in to a project repository | C63001 | |||||
40775 | SQL Join transformations might be lost when importing or migrating jobs | C63001 | |||||
41026 | Jobs that contain SQL Join transformations might appear with changes after migrating from SASŪ 9.1.3 to SASŪ 9.2 | C63001 | |||||
41027 | The SCD Type 2 Loader transformation fails or experiences performance problems | C63001 | |||||
41028 | ALERT - Processing can terminate prematurely if exceptions occur during ETL metadata migration | C63001 | |||||
41035 | All input and output ports are incorrectly activated for generated transformations after job migration | C63001 | |||||
41037 | Extra table objects appear in job definitions after migrating from SASŪ 9.1.3 to SASŪ 9.2 | C63001 | |||||
41039 | Problems occur with alias definitions in SQL Join transformations after migrating from SASŪ 9.1.3 to SASŪ 9.2 | C63001 | |||||
41040 | The MetadataUpdated field remains unchanged after the source code is altered for generated transformations | C63001 | |||||
41042 | Incorrect output data is generated in the Comparison Results window | C63001 | |||||
41044 | The table options are not surfaced in transformation properties or in generated code after applying Hot Fix B51001 | C63001 | |||||
41053 | Metadata problems occur as a result of using the SQL Join transformation | C63001 | |||||
40348 | Netezza tables accessed using SAS/ACCESSŪ Interface OLE DB cannot be registered in SASŪ Management Console | C63002 | |||||
42066 | Update a time field in an existing data set can result in incorrect time | C63002 | |||||
42077 | SASŪ Clinical Data Integration version 2.2 - CDISC-SDTM to CRT-DDS transformation loses an output connector | C63002 | |||||
42989 | You are unable to map the second instance of a column when you join a table with itself via aliases in SASŪ Data Integration Studio | C63002 | |||||
42990 | Unable to register table metadata with the OLE DB designer template for Netezza in SASŪ Management Console and SASŪ Data Integration Studio | C63002 | |||||
42994 | Mapping multiple tables to a single table when you import a SASŪ metadata package file results in corruption | C63002 | |||||
42995 | A "Table not found" error occurs in SASŪ Data Integration Studio when loading data | C63002 | |||||
43034 | Database management system library options are omitted from explicit SQL pass-through code in SASŪ Data Integration Studio | C63002 | |||||
43174 | You might receive errors when you attempt to generate code or run jobs after they have been promoted using the Export and Import SAS Package wizards | C63002 | |||||
43214 | A table-not-found error occurs when you run a SASŪ Data Integration Studio job using the SQL Join transformation | C63002 | |||||
43215 | The SAS Import Package wizard might fail when you attempt to import jobs that are created in earlier releases of SASŪ Data Integration Studio | C63002 | |||||
43236 | Subquery objects are lost from SASŪ Data Integration Studio SQL Join transformations that contain WHERE, HAVING, or SELECT clauses | C63002 | |||||
43254 | The Teradata Table Loader transformation does not retain load technique settings | C63002 | |||||
43256 | SASŪ Data Integration Studio uses the wrong SQL procedure statement when you clear the contents of a Netezza table | C63002 | |||||
43268 | Applying Hot Fix B51002 can cause SASŪ Data Surveyor for Clickstream Data 2.2 jobs to fail | C63002 | |||||
43290 | After you apply hot fix B51002 an error can occur when jobs are automatically deployed by Adapter Setup Wizard | C63002 | |||||
18957 | ALERT - The Loader transformation's "Update/Insert" technique in SASŪ Data Integration Studio 3.4 might load nonmapped target-table columns with incorrect data | C63003 | |||||
43211 | A Splitter transformation in SASŪ Data Integration Studio generates the error "Data set was not specified on the DATA statement" | C63003 | |||||
44668 | After installing hot fix B51003 for SASŪ Data Integration Studio, jobs fail to generate complete code | C63003 | |||||
44893 | ALERT - New rows containing incorrect data are loaded into the target table | C63003 | |||||
44908 | "Mapped source columns do not match columns used in expression" might occur after you install hot fix B51003 | C63003 | |||||
45796 | Applying Hot Fix B51002 for SASŪ Data Integration Studio triggers "ERROR: LIBNAME ETLSTMP is not assigned" in an SCD Type 2 Loader transformation | C63003 | |||||
45881 | Importing a SASŪ Data Integration Studio 3.4 job into SASŪ Data Integration Studio 4.2 might fail with errors | C63003 | |||||
45896 | Invalid SQL pass-through code is generated after applying Hot Fix B51003 for SASŪ Data Integration Studio 4.2 | C63003 | |||||
48511 | The Column reference property setting for Group By columns in the Extract transformation is set to the default value Name when migrated or promoted | C63003 | |||||
43115 | The Build Expression button is missing from the Filter tab in SASŪ Data Integration Studio | C63004 | |||||
45307 | The traditional Chinese version of SASŪ Data Integration Studio displays simplified Chinese in the menu | C63004 | |||||
45769 | Text written to the Log and the Output tabs in SASŪ Data Integration Studio always wraps at 100 characters | C63004 | |||||
45831 | The Model Universal Unique Identifier value is not shown in the Mining Results transformation properties in SASŪ Data Integration Studio | C63004 | |||||
45846 | A "Maximum data source count will be exceeded (1)" error occurs when migrating jobs containing a Splitter transformation with two or more input tables | C63004 | |||||
45920 | The SCD Type 2 Loader transformation provides no option to suppress index creation on the permanent cross reference table or on the target table | C63004 | |||||
45939 | The error "BY variables are not properly sorted on data set LIBREF.TARGETTABLE" occurs in an SCD Type 2 Loader transformation | C63004 | |||||
45979 | Cannot save a SASŪ Data Integration Studio 4.2 job that contains a user-generated transformation | C63004 | |||||
45996 | The SPD Server Table Loader transformation ignores the "Alternative library for temporary tables" option for target tables | C63004 | |||||
48472 | The message "Error in the LIBNAME statement" appears in SASŪ Data Integration Studio jobs that use the SCD Type 2 Loader transformation | C63004 | |||||
48510 | Business keys in the SCD Type 2 Loader transformation are missing after you migrate or promote jobs from SASŪ Data Integration Studio 3.4 | C63004 | |||||
48571 | Registering Teradata tables fails in SAS Data Integration Studio for libraries using the SAS/Access ODBC or OLE DB engines. | C63004 | |||||
47906 | The target table might not update correctly when using the SCD Type 2 Loader transformation | C63005 | |||||
47908 | "ERROR: Expected open parenthesis after macro function name not found" occurs when using an SCD Type 2 Loader transformation | C63005 | |||||
48456 | "ERROR: A link must be established by executing the SIGNON command ..." occurs in SASŪ Data Integration Studio jobs that use the Loop transformation | C63005 | |||||
48458 | SASŪ Data Integration Studio jobs with Loop transformations incorrectly complete with nonzero return codes | C63005 | |||||
48484 | Values for Additional Data Table Options in the SPD Server Loader transformation are missing after a migration or promotion | C63005 | |||||
48485 | SASŪ Data Integration Studio shows only one Foreign Key Column if multiple foreign keys reference the same primary key table | C63005 | |||||
48531 | The COMPRESS=BINARY option is not included in the selection list for table options in SASŪ Data Integration Studio 4.21 | C63005 | |||||
48532 | Data does not import correctly when using the External File Wizard or the Table Properties window in SASŪ Data Integration Studio | C63005 | |||||
NOTE: If you install this hot fix, you must also install hot fix B51006 for Data Integration Studio 4.21 - M2 on your client machine. NOTE: To implement the fix for the issue described in SN-45307 please contact SAS Technical Support. | |||||||
| |||||||
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
Top ^ |
PLEASE CAREFULLY READ THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT ("AGREEMENT") BEFORE DOWNLOADING MATERIALS FROM THIS SITE. BY DOWNLOADING ANY MATERIALS FROM THIS SITE, YOU ARE AGREEING TO THESE TERMS.
|
You are downloading software code ("Code") which will become part of a product ("Software") you currently have licensed from SAS Institute Inc. or one of its subsidiaries ("the Institute"). This Code is designed to either correct an error in the Software
or to add functionality to the Software. The code is governed by the same agreement which governs the Software. If you do not have an existing agreement with the Institute governing the Software, you may not download the Code.
|
SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration. Other brand and product names are registered
trademarks or trademarks of their respective companies.
|
Copyright © 2014 SAS Institute Inc. All Rights Reserved.
|