| G2T010 for Linux for x64 |
| SAS Infrastructure for Risk Management 3.6 |
| Issue(s) Addressed: | Introduced: |
| 64322 | You encounter a null pointer exception when migrating from SAS® Infrastructure for Risk Management 3.4 to 3.6 |
G2T001 |
| 64688 | "500:java.lang.IllegalArgumentException..." occurs when you upload an input data set in SAS® Infrastructure for Risk Management 3.6 |
G2T001 |
| 64689 | Pooled files are not cleaned up properly when you delete an instance in SAS® Infrastructure for Risk Management 3.5 |
G2T001 |
| 64701 | The button to view results is disabled in SAS® Infrastructure for Risk Management 3.6 |
G2T001 |
| 64750 | SASServer 8 start-up takes a long time to start in SAS® Infrastructure for Risk Management 3.6 |
G2T001 |
| 64788 | You can access instances that should not appear to you if you have the "IRM: Change Owner" role |
G2T001 |
| 65121 | The IRM_REST_GET_INSTANCES macro fails with "ERROR: Overflow has occurred..." when a one-time password begins with a number |
G2T001 |
| 65128 | Year values for the BASE_DTTM macro variable are saved with two digits by default in the system_options table |
G2T001 |
| 65133 | It is not possible to run any job-flow instances |
G2T001 |
| 65406 | Loading jobflow instances is slow during server start-up in SAS® Infrastructure for Risk Management |
G2T001 |
| 65407 | Cloned instances in SAS® Infrastructure for Risk Management contain old input data after restarting SASServer8 |
G2T001 |
| 65221 | Live ETL fails to detect impacted job flow instances in SAS® Infrastructure for Risk Management 3.5 |
G2T002 |
| 65674 | Unable to select base dates and entities beyond the top 100 entries in SAS® Infrastructure for Risk Management 3.6 |
G2T003 |
| 65681 | "ERROR org.hibernate.jdbc.AbstractBatcher - Exception executing batch..." occurs when you create instances in SAS® Infrastructure for Risk Management |
G2T004 |
| 65684 | Tasks fail due to reused metadata credentials in SAS® Infrastructure for Risk Management |
G2T004 |
| 65685 | Improvements to task logs in SAS® Infrastructure for Risk Management |
G2T004 |
| 66095 | The message "ERROR: Could not move and link one or more files to..." occurs while running a job-flow instance |
G2T005 |
| 66515 | SAS® Infrastructure for Risk Management 3.6 task logs are filtered |
G2T006 |
| 66516 | The message "ERROR: setupSymbolicLinks returned false but did not set exception..." occurs when creating an instance |
G2T006 |
| 66517 | You see the message "HTTP Status 500 - Internal Server Error" when accessing SAS® Infrastructure for Risk Management 3.6 via a WebDAV URL |
G2T006 |
| 66518 | Generating a TGT for SAS® Infrastructure for Risk Management 3.6 tasks works only for internal users |
G2T006 |
| 66520 | Deleting an instance during live ETL causes the error "LiveETL failed for Input Area…" and a crash of the IRM Web Application Server |
G2T006 |
| 66523 | SAS® Infrastructure for Risk Management 3.6 now has functionality regarding viewing collection data |
G2T006 |
| 66521 | Support is added for JSON files in Python tasks for SAS® Infrastructure for Risk Management 3.6 |
G2T006 |
| 67000 | The HTML Commons component in SAS® 9.4 Web Infrastructure Platform is affected by the JQuery vulnerability that is described in CVE-2020-11022 |
G2T007 |
| 67254 | The current period cycle fails during the Initialize Cycle task in an upgraded SAS® Solution for IFRS 9 v10.2020 environment |
G2T007 |
| 67873 | An issue with entity IDs occurs when both dynamic and static library definitions include the %et macro variable |
G2T009 |
| 65592 | SAS® Infrastructure for Risk Management fails to execute parallel Current Expected Credit Loss scenario jobs |
G2T010 |
| 68089 | Persistent data for SAS® Infrastructure for Risk Management 3.6 is inaccessible after you publish an instance |
G2T010 |
| 68090 | You see the error message "...Could not write JSON..." when you attempt to drill down into tasks in SAS® Infrastructure for Risk Management |
G2T010 |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
Important changes to Hot Fixes!