Problem Note 42671: 'org.hibernate.exception.ConstraintViolationException Could not execute JDBC batch update' and 'java.sql.BatchUpdateException Duplicate entry for key'
 |  |  |  |
If you are trying to import adjustment rules from one SAS Financial Management model to another, you might encounter a message similar to
Import Failed.in SAS Financial Management Studio.
Nothing was imported.
See the log for more information.
Checking the client log, you might see entries similar to:
[ModalContext][DEBUGExceptionWrapper] - Could not deserialize Exception: java.lang.ClassNotFoundException: javax.ejb.TransactionRolledbackLocalException
AND
[ModalContext][DEBUGExceptionWrapper] - Returned stack trace of:java.lang.reflect.InvocationTargetException
AND
Caused by: java.rmi.RemoteException: EJB Exception: ; nested exception is: javax.ejb.TransactionRolledbacLocalException: EJB Exception:; nested exception is: org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
AND
Caused by: java.sql.BatchUpdateException: Duplicate entry 'xyz' for key
AND
[ModalContext][DEBUGTransportManagerHttpService] - java.lang.reflect.InvocationTargetException toString() java.lang.reflect.InvocationTargetException
AND
[main][ERRORImportRulesWizard] - java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
The SASFinancialManagement5.x log might have entries similar to what is included in the above client log and might also show errors similar to:
ERROR AbstractFlushingEventListener Could not synchronize database state with session
AND
ERROR RuleManagerBean createRule() - u:sasdemo - Error creating Rule
AND
ERROR ResultRuleManagerBean appendRule() - u:sasdemo - Error appending rule
Similar information will likely also be written to the SASServer3 log.
The above logging information indicates that the source and the target models and not fully synchronized, thus the source adjustment rules or the target model must be modified for the rule import to succeed.
Since a number of the messages in the logs reference org.hibernate.exception, a helpful step to further diagnose the problem is to enable org.hibernate.SQL logging for the SASFinancialManagement5.x log, with a level value of "debug". This change is made to the <SASFinance-log4j.xml> file. You will likely see that org.hibernate.SQL logging is commented out and you will need to remove the commenting to activate this logging. To do so, please remove the
<!--AND
-->characters that precede and follow the entry for <logger name="org.hibernate.SQL".
After updating the logging settings, please try to import the adjustments rules again and then check the output written to the SASFinancialManagement5.x log. Error messages should be written following the steps in the SQL that cause the problem.
For example, if you see error messages immediately following the SQL code
SAS_ALLC_SRC_PROPSthe allocation source properties for the source and the target model analysis member IDs appear to be inconsistent.
(TARGET_ANALYSIS_MEM_ID, SOURCE_ANALYSIS_MEM_ID, PERIOD, FREQUENCY,
SOURCE_MEM_ID, ALLOCATION_ID, ALLC_SRC_PROPS_ID)
Check the analysis member IDs in your target model and then confirm the analysis member IDs in your source adjustment rules. You will likely need to either modify the analysis member IDs in your target model or modify the adjustment rules so that the analysis members/IDs are consistent between the source and the target.
For the default locations of SAS Financial Management log files, please refer to SAS Note 20058.
For information on modifying the logging levels for SAS Financial Management, please refer to SAS Note 19864.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Financial Management | Microsoft® Windows® for x64 | 5.1 | 9.2 TS2M0 | ||
| Microsoft Windows Server 2003 Datacenter Edition | 5.1 | 9.2 TS2M0 | ||||
| Microsoft Windows Server 2003 Enterprise Edition | 5.1 | 9.2 TS2M0 | ||||
| Microsoft Windows Server 2003 Standard Edition | 5.1 | 9.2 TS2M0 | ||||
| Microsoft Windows Server 2003 for x64 | 5.1 | 9.2 TS2M0 | ||||
| Microsoft Windows Server 2008 for x64 | 5.1 | 9.2 TS2M0 | ||||
| Microsoft Windows XP Professional | 5.1 | 9.2 TS2M0 | ||||
| Windows Vista | 5.1 | 9.2 TS2M0 | ||||
| Windows Vista for x64 | 5.1 | 9.2 TS2M0 | ||||
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2011-03-14 10:58:07 |
| Date Created: | 2011-03-14 09:02:36 |