SUPPORT / SAMPLES & SAS NOTES
Problem Note 33528: NullPointerException when using adddata or addxlsdata
 |  |  |  |  |
If you applied SAS® OpRisk Monitor 3.4.x Hot Fix 4, you might receive the following exception on your screen, or in a log when using the command line dataload commands addata or addxlsdata:
java.lang.NullPointerException at com.sas.oprisk.server.behavior.DimensionalPointImpl.greatestLowerBound DimensionalPointImpl.java:732) at com.sas.oprisk.server.behavior.FinancialImpactImpl.updateDenormalizedSecurityStuff (FinancialImpactImpl.java:1194) at com.sas.oprisk.server.behavior.FinancialImpactImpl$RedenormalizeSecurityHook.run (FinancialImpactImpl.java:1118) at com.sas.oprisk.server.base.BaseFinancialImpact$FinancialImpactHook.run (BaseFinancialImpact.java:1051) at com.sas.oprisk.framework.server.objects.BusinessObjectImpl$ClassObjectImpl.runPreSaveHooks (BusinessObjectImpl.java:54) at com.sas.oprisk.server.base.BaseFinancialImpactImpl.save (BaseFinancialImpactImpl.java:6470) at com.sas.oprisk.server.behavior.FinancialImpactImpl.save (FinancialImpactImpl.java:1278) at com.sas.oprisk.server.behavior.LockableObjectImpl.saveForSaveCaches (LockableObjectImpl.java:241) at com.sas.oprisk.server.base.BaseOpRiskEventImpl.saveCaches (BaseOpRiskEventImpl.java:6464) at com.sas.oprisk.server.base.BaseOpRiskEventImpl.save (BaseOpRiskEventImpl.java:6563) at com.sas.oprisk.server.behavior.OpRiskEventImpl.save(OpRiskEventImpl.java:721) at com.sas.oprisk.server.behavior.FinancialImpactImpl.save (FinancialImpactImpl.java:1333) at com.sas.oprisk.server.behavior.LockableObjectImpl$1.doSave (LockableObjectImpl.java:205) at com.sas.oprisk.server.behavior.LockableObjectImpl.saveBody (LockableObjectImpl.java:289) at com.sas.oprisk.server.behavior.LockableObjectImpl.save (LockableObjectImpl.java:214) at com.sas.oprisk.server.behavior.FinancialImpactImpl.save (FinancialImpactImpl.java:1376) at com.sas.oprisk.server.dataload.FinancialImpactLoader.saveAndLogResults (FinancialImpactLoader.java:464) at com.sas.oprisk.server.dataload.FinancialImpactLoader$FinancialImpactEntryProcessor.processEntry (FinancialImpactLoader.java:129) at com.sas.oprisk.framework.server.dataload.EntryProcessor.process (EntryProcessor.java:60) at com.sas.oprisk.server.dataload.FinancialImpactLoader.load (FinancialImpactLoader.java:155) at com.sas.oprisk.server.dataload.LoaderInvocationProcessor.invokeLoad (LoaderInvocationProcessor.java:71) at com.sas.oprisk.server.dataload.AddDataDriver.invokeLoaders (AddDataDriver.java:174) at com.sas.oprisk.server.dataload.AbstractDataLoadDriver.loadData (AbstractDataLoadDriver.java:250) at com.sas.oprisk.server.dataload.AddDataDriver.main(AddDataDriver.java:80)
To work around the problem, use the SAS OpRisk Monitor web application with Excel spreadsheets to load the new data.
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS OpRisk Monitor | Microsoft® Windows® for x64 | 3.4.1 | 4.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Microsoft Windows 2000 Advanced Server | 3.4.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows 2000 Datacenter Server | 3.4.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows 2000 Server | 3.4.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows 2000 Professional | 3.4.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows NT Workstation | 3.4.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows Server 2003 Datacenter Edition | 3.4.1 | 4.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 3.4.1 | 4.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
| Microsoft Windows Server 2003 Standard Edition | 3.4.1 | 4.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
| Microsoft Windows XP Professional | 3.4.1 | 4.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
| Windows Vista | 3.4.1 | 4.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
| 64-bit Enabled AIX | 3.4.1 | 4.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
| 64-bit Enabled Solaris | 3.4.1 | 4.1 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||