SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 38911: An "interacting with the database" error appears when you save a form that has a blank Base Amount field

DetailsHotfixAboutRate It

In SAS® OpRisk Monitor, you should receive a validation error message when you leave the Base Amount field blank on screens where the field is editable (for example, Edit Financial Effect screen). However, if you edit an object that was saved with a blank Base Amount, the amount shows as 0, and when you attempt to save the object you will be directed to an OpRisk Monitor Error screen that displays the following error:

Message: There was an error interacting with the database: 
ERROR: null value in column "base_loss_amt" violates not-null constraint.
Reason: unknown
com.sas.oprisk.framework.server.persistence.PersistenceException: There was an error interacting with the database: 
ERROR: null value in column "base_loss_amt" violates not-null constraint.
	at com.sas.oprisk.framework.server.persistence.SqlPersistenceStrategy.wrapException(SqlPersistenceStrategy.java:1277)
	at com.sas.oprisk.framework.server.persistence.SqlPersistenceSession$CachedStatement.executeUpdate(SqlPersistenceSession.java:281)
	at com.sas.oprisk.framework.server.persistence.SqlPersistenceStrategy.basicSave(SqlPersistenceStrategy.java:783)
	at com.sas.oprisk.framework.server.persistence.AbstractPersistenceStrategy.insert(AbstractPersistenceStrategy.java:320)
	at com.sas.oprisk.server.base.BaseImpactDetailImpl.save(BaseImpactDetailImpl.java:4494)
	at com.sas.oprisk.server.behavior.ImpactDetailImpl.save(ImpactDetailImpl.java:123)
	at com.sas.oprisk.server.base.BaseFinancialImpactImpl.saveCaches(BaseFinancialImpactImpl.java:7281)
	at com.sas.oprisk.server.base.BaseFinancialImpactImpl.save(BaseFinancialImpactImpl.java:7403)
	at com.sas.oprisk.server.behavior.LockableObjectImpl$1.doSave(LockableObjectImpl.java:205)
	at com.sas.oprisk.server.behavior.LockableObjectImpl.saveBody(LockableObjectImpl.java:289)
...

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS OpRisk MonitorWindows 7 Ultimate x644.14.29.2 TS2M29.2 TS2M2
Windows 7 Ultimate 32 bit4.14.29.2 TS2M29.2 TS2M2
Windows 7 Professional x644.14.29.2 TS2M29.2 TS2M2
Windows 7 Professional 32 bit4.14.29.2 TS2M29.2 TS2M2
Windows 7 Home Premium x644.14.29.2 TS2M29.2 TS2M2
Windows 7 Home Premium 32 bit4.14.29.2 TS2M29.2 TS2M2
Windows 7 Enterprise x644.14.29.2 TS2M29.2 TS2M2
Windows 7 Enterprise 32 bit4.14.29.2 TS2M29.2 TS2M2
Microsoft Windows XP Professional4.14.29.2 TS2M29.2 TS2M2
Microsoft Windows Server 20084.14.29.2 TS2M29.2 TS2M2
Microsoft Windows Server 2003 Enterprise Edition4.14.29.2 TS2M29.2 TS2M2
Microsoft® Windows® for x644.14.29.2 TS2M29.2 TS2M2
Microsoft Windows Server 2003 Datacenter Edition4.14.29.2 TS2M29.2 TS2M2
Microsoft Windows Server 2003 Standard Edition4.14.29.2 TS2M29.2 TS2M2
Windows Vista4.14.29.2 TS2M29.2 TS2M2
64-bit Enabled AIX4.14.29.2 TS2M29.2 TS2M2
64-bit Enabled Solaris4.14.29.2 TS2M29.2 TS2M2
HP-UX IPF4.14.29.2 TS2M29.2 TS2M2
Linux for x644.14.29.2 TS2M29.2 TS2M2
* 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.