| J7S008 for Solaris for x64 |
| Data Integration Studio 4.7_M7 |
| Issue(s) Addressed: | Introduced: |
| 66540 | SAS® Management Console and SAS® Data Integration Studio might return the message "table failed to update" when you use the Update Metadata tool |
J7S001 |
| 67069 | The Number of Records field in the Basic Properties pane of SAS® Data Integration Studio might contain an incorrect value |
J7S001 |
| 67157 | A SAS® LASR™ Analytic Server Loader transformation incorrectly reports an error condition when physical names of the source and target do not match |
J7S001 |
| 67171 | A job that contains a Model Scoring transformation fails with the message "ERROR: Invalid hexadecimal constant string..." |
J7S001 |
| 67172 | The Register Tables wizard fails with the message "ERROR: The submitted line exceeds maximum line length - 32768 bytes" |
J7S001 |
| 67173 | Errors occur in pass-through code when options for DBMS library definitions in metadata are incorrectly included or omitted from the CONNECT statement |
J7S001 |
| 67188 | A "Compare Tables: java.lang.NullPointerException" error occurs when deploying a job that contains a Compare transformation using a hash lookup method |
J7S001 |
| 67771 | SAS® LASR™ Analytic Server Loader ignores "Use runtime lookup for credentials for statements requiring credentials" in SAS® Data Integration Studio |
J7S002 |
| 68521 | The export wizard in SAS® Data Integration Studio does not retain the expected column order in the composite index or composite primary key |
J7S002 |
| 68522 | SAS® Data Integration Studio 4.905 displays "Error writing metadata:Repository ABCDEFGH is not registered" when you add a new responsibility |
J7S002 |
| 68540 | SAS® Data Integration Studio jobs contain extraneous metadata content that might negatively impact metadata performance |
J7S002 |
| 68545 | The command-line batch deployment tool fails to include the Metadata Server and Port information in the job header comments |
J7S002 |
| 68546 | "...Multiple lengths were specified for the variable recreate by input data set(s). This may cause truncation..." occurs after you submit a job |
J7S002 |
| 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 |
J7S002 |
| 68840 | Database connection information for a source table is used when creating a new database table with the Create Table transformation |
J7S004 |
| 68924 | SAS® Data Integration Studio jobs contain extraneous metadata content that might negatively impact metadata performance |
J7S004 |
| 69508 | CASLIB options that begin with numbers in SAS® Data Integration Studio 4.905 do not work |
J7S005 |
| 69806 | SAS® Information Delivery Portal 4.4_M7 contains a stored cross-site scripting vulnerability |
J7S006 |
| 70142 | SAS® 9.4M7 (TS1M7) includes end-of-life Log4J version 1 libraries |
J7S007 |
| 70970 | Incorrect results can be generated with the Lookup Transformation when a column in a source table is renamed |
J7S008 |
| NOTE: If you install this hot fix, you must also install hotfixes J2L010 and I9E009 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