Defining Session Identifiers fails with "GenericJDBCException: Could not execute JDBC batch update"

Document ID : KB000047981
Last Modified Date : 14/02/2018
Show Technical Document Details


When specifying a Business Application and saving "Session Identification parameters", APM fails with the message:
"Internal Application error: JDBC exception on Hibernate data access; nested exception is org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch update"

Figure 1


  1. Make an APM Database Backup. (This is an important step.)

  2. Stop the Introscope Enterprise Manager running the CEM Services and MOM

  3. Run the SQL commands: ALTER TABLE ts_session_id_parameters MODIFY (ts_nameVARCHAR2(500)); commit;

  4. Restart the stopped EMs.

  5. Create or recreate the "Session Identification parameter".