| D8Y011 for Solaris for x64 |
| Data Integration Studio 4.904 |
| Issue(s) Addressed: | Introduced: |
| 63434 | Advanced options for a Join transformation are not retained after a job is saved, closed, and reopened |
D8Y001 |
| 65712 | The "Register Tables" or "Update Metadata" function can fail with the error message "Invalid connection options. Lack USER option." |
D8Y001 |
| 68145 | The "Update Metadata" function fails on a work table, and you see the message "The object ... is not found in the ptable container ..." |
D8Y001 |
| 64172 | Registering OLE DB tables using SAS® Management Console in SAS® 9.4M6 (TS1M6) fails when the authentication domain is not set |
D8Y002 |
| 64285 | The SCD Type 2 Loader transformation in SAS® Data Integration Studio generates "ERROR 22-322: Syntax error, expecting one of the following:..." |
D8Y002 |
| 64412 | Jobs that contain SQL transformations might fail to open in SAS® Data Integration Studio 4.904 |
D8Y002 |
| 64459 | A SAS® Data Integration Studio job receives an error that states "The name 'index_name' has the wrong number of qualifiers" |
D8Y002 |
| 64508 | Archiving metadata content with SAS® Data Integration Studio can cause errors when you use the Git Version Control plug-in |
D8Y002 |
| 64537 | The Set Operators transformation generates incorrect code when the option "Set Pass Through to yes for new SQL transformations" is enabled |
D8Y002 |
| 64581 | The Insert Rows transformation generates incorrect explicit PROC SQL pass-through code when the source and target tables are in different databases |
D8Y002 |
| 64601 | A SAS® Data Integration Studio job that contains the Merge transformation might be incorrect when it is opened in the Job Editor window |
D8Y002 |
| 64842 | SAS® 9.4 software references Apache Struts libraries that contain known vulnerabilities |
D8Y003 |
| 64606 | File events for Platform Process Manager flows are not mapped correctly after you import a SAS® package file |
D8Y004 |
| 60622 | Redeploying a job using SAS® Management Console fails with the "UNKNOWN_ORIGINAL_SOURCE_FILE" error when the deployed job is defined by importing |
D8Y004 |
| 65225 | You click X in the Confirm Undo Check Out window, but the displayed object is still checked in unexpectedly and changes are lost |
D8Y005 |
| 65295 | The order of columns is not maintained when you select columns for output in the Business Rules transformation |
D8Y005 |
| 65349 | The Register Tables wizard returns "ERROR 22-322: Syntax error, expecting one of the following...HOST, ID..." when you run the METALIB procedure |
D8Y005 |
| 65707 | The "Last Modified By" field for a table object is not updated after you select "Update Metadata" |
D8Y005 |
| 65708 | You select "Choose Columns" on the "Inputs and Outputs" tab in a Business Rule transformation, and column mappings are then lost |
D8Y005 |
| 65709 | You remove links to table objects within jobs, but the links are still referenced after you promote these jobs across metadata environments |
D8Y005 |
| 65715 | Unexpected results can occur because the SYSCC automatic macro variable does not reset to zero within SAS® Data Integration Studio job code |
D8Y005 |
| 65723 | Changes to properties in the SPD Server Table Loader transformation are not retained when saving a job |
D8Y005 |
| 65726 | Incorrect code is generated for the SQL Join transformation when you use a PROC SQL pass-through query for an Impala table |
D8Y005 |
| 65724 | A REST transformation in SAS® Data Integration Studio causes issues for a RESTful service that uses the Content-Type header attribute |
D8Y005 |
| 66134 | SAS® Management Console contains an XML External Entity (XXE) processing vulnerability |
D8Y006 |
| 66540 | SAS® Management Console and SAS® Data Integration Studio might return the message "table failed to update" when you use the Update Metadata tool |
D8Y007 |
| 67069 | The Number of Records field in the Basic Properties pane of SAS® Data Integration Studio might contain an incorrect value |
D8Y008 |
| 67094 | The Register Tables wizard displays warning messages about database connections after you apply Hot Fix D8Y005 |
D8Y008 |
| 67157 | A SAS® LASR™ Analytic Server Loader transformation incorrectly reports an error condition when physical names of the source and target do not match |
D8Y008 |
| 67171 | A job that contains a Model Scoring transformation fails with the message "ERROR: Invalid hexadecimal constant string..." |
D8Y008 |
| 67172 | The Register Tables wizard fails with the message "ERROR: The submitted line exceeds maximum line length - 32768 bytes" |
D8Y008 |
| 67173 | Errors occur in pass-through code when options for DBMS library definitions in metadata are incorrectly included or omitted from the CONNECT statement |
D8Y008 |
| 67188 | A "Compare Tables: java.lang.NullPointerException" error occurs when deploying a job that contains a Compare transformation using a hash lookup method |
D8Y008 |
| 67771 | SAS® LASR™ Analytic Server Loader ignores "Use runtime lookup for credentials for statements requiring credentials" in SAS® Data Integration Studio |
D8Y009 |
| 68521 | The export wizard in SAS® Data Integration Studio does not retain the expected column order in the composite index or composite primary key |
D8Y009 |
| 68522 | SAS® Data Integration Studio 4.905 displays "Error writing metadata:Repository ABCDEFGH is not registered" when you add a new responsibility |
D8Y009 |
| 68540 | SAS® Data Integration Studio jobs contain extraneous metadata content that might negatively impact metadata performance |
D8Y009 |
| 68545 | The command-line batch deployment tool fails to include the Metadata Server and Port information in the job header comments |
D8Y009 |
| 68546 | "...Multiple lengths were specified for the variable recreate by input data set(s). This may cause truncation..." occurs after you submit a job |
D8Y009 |
| 68566 | A DeployJobs command with the REDEPLOY option creates a new job with the name of the original job, even though you entered a new Deployed Job Name |
D8Y009 |
| 68924 | SAS® Data Integration Studio jobs contain extraneous metadata content that might negatively impact metadata performance |
D8Y011 |
NOTE: If you install this hot fix, you must also install hotfix D9T075 to surface the fix documented in SAS Note 65724
If you install this hot fix, you must also install hotfixes D8T021 and D8N020 to surface the fix documented in SAS Note 68924 |
|
| 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