| M2Q005 |
| SAS Infrastructure for Risk Management 3.7 |
| Issue(s) Addressed: | Introduced: |
| 69995 | SAS® Infrastructure for Risk Management instances do not change to "OUT_OF_DATE" status after Live ETL |
M2Q001 |
| 69996 | Live ETL fails with a "java.lang.NullPointerException" error |
M2Q001 |
| 69997 | Publishing an instance fails with the error "Could not create Java Environment" in SAS® Infrastructure for Risk Management |
M2Q001 |
| 70538 | SAS® Infrastructure for Risk Management tables are not updated to reflect configurable inputs |
M2Q002 |
| 70539 | An error occurs when deleting instances from the SAS® Infrastructure for Risk Management User Interface |
M2Q002 |
| 70540 | The SAS® Infrastructure for Risk Management Live ETL process fails with the error “java.lang.NullPointerException” |
M2Q002 |
| 70541 | SAS® Infrastructure for Risk Management instances that are created from personal federated areas have slower performance |
M2Q002 |
| 70610 | An HTTP 403 error occurs when running SAS® Infrastructure for Risk Management instances in parallel |
M2Q002 |
| 70612 | SAS® Infrastructure for Risk Management batch performance improvements |
M2Q002 |
| 70640 | SAS® Infrastructure for Risk Management enables the use of PooledConnectionProvider |
M2Q002 |
| 70881 | “Error "null" occurred executing SAS task ID="_8493" ("rmb_node_export_cf")” in SAS® Infrastructure for Risk Management |
M2Q003 |
| 70882 | The date does not update after uploading tables to SAS® Infrastructure for Risk Management instances |
M2Q003 |
| 70892 | SAS® Infrastructure for Risk Management cycles fail to run with the error “duplicate key value violates unique constraint “ix_data_path”” |
M2Q003 |
| 70894 | A SAS® Infrastructure for Risk Management tool fails with the error “column "source_federated_area_id" of relation "jobflow_instance" already exists” |
M2Q003 |
| 71069 | Issues introduced by latest the SAS® Infrastructure for Risk Management hot fix |
M2Q005 |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |