Using the "Group Identification" feature under Business Applications to associate a Group with specific customers, you receive a JDBC error while trying toidentify the associated Group using XML.
When creating "User identification" under Business Applications and using XML, it works as expected. When using the same XML for both User ID and Group ID, and trying to "save" the Group ID (XML location), you receive this JDBC error:
Internal Application Error: JDBC exception on Hibernate data access; nested exception is org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch update.
The best recommendation is to change the User Group Identification parameter to be under 200 characters.
If this is not possible, then follow these steps to increase the column size to 2,000 characters. (Note this will be the increased size of the TS_NAME column in APM 9.6 release and later.):
- Make an APM DB Backup. (This is an important step!)
- Stop all EMs running CEM services and the MOM.
- Execute the following SQL query: ALTER TABLE ts_usergroup_id_parameters MODIFY (ts_name VARCHAR2(2000)); commit;
- Restart all EMs
- Try to create/re-create the User Group Identification parameter.