Problem Note 44167: Job runs using data in the private SAS® Risk Reporting Repository even if the Shared job parameter is selected
In the Job Parameter window of the SAS® Risk Management for Insurance 2.1_M1 Analysis Wizard, you can select to run a job using data from either the Private or Shared SAS Risk Reporting Repository:
However, regardless of what you select, the job runs using data from the Private SAS Risk Reporting Repository. If data required for the job is not available in the Private SAS Risk Reporting Repository (for example, if you are not using a SAS Risk Management for Insurance stored process to populate that data), then analysis tasks in the job might fail or complete with errors. Analysis tasks might also complete successfully but incorrectly use source data from the Private SAS Risk Reporting Repository when you expected source data from the Shared SAS Risk Reporting Repository to be used.
When jobs fail or complete with errors due to this problem, errors like the following might appear in the analysis task logs:
ERROR: Scenario ID "<ID>" is not found in <table name> RR table. Current run date is "<rundate>".
Please make sure system run date is no later than scenario base date.
ERROR: A system fatal error has occurred. No further processing will be executed.
Note that these errors are not specific to this issue. The first occurs whenever expected data is not present in the source SAS Risk Reporting Repository. The second can have a number of causes.
There is no recommended workaround.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Risk Management for Insurance | Microsoft® Windows® for x64 | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Datacenter Edition | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Enterprise Edition | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Standard Edition | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2003 for x64 | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2008 | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2008 R2 | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2008 for x64 | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows XP Professional | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Enterprise 32 bit | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Enterprise x64 | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Home Premium 32 bit | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Home Premium x64 | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Professional 32 bit | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Professional x64 | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Ultimate 32 bit | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Ultimate x64 | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows Vista | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows Vista for x64 | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
64-bit Enabled AIX | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
64-bit Enabled HP-UX | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
64-bit Enabled Solaris | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
HP-UX IPF | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Linux for x64 | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
Solaris for x64 | 2.1_M1 | 2.12 | 9.2 TS2M3 | 9.3 TS1M2 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | alert |
Date Modified: | 2012-11-06 10:14:30 |
Date Created: | 2011-08-31 12:53:33 |