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

Document created by Yanna Employee on May 26, 2016Last modified by J.J. Lovett on May 26, 2016
Version 2Show Document
  • View in full screen mode

Document ID:  TEC616523

Last Modified Date:  9/4/2014
Authored By: Yanna

  • Products
    • CA Application Performance Management
  • Releases
    • CA Application Performance Management:Release:9.07
    • CA Application Performance Management:Release:9.08
    • CA Application Performance Management:Release:9.1 SP2
    • CA Application Performance Management:Release:9.1.0
    • CA Application Performance Management:Release:9.1.1
    • CA Application Performance Management:Release:CA APM 9.5
    • CA Application Performance Management:Release:CA APM 9.6
    • CA Application Performance Management:Release:CA APM 9.7
  • Components
    • Integrations with other Products


Description: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"
image: http://search.ca.com/assets/SiteAssets/TEC616523_Embeded/616523a.gifFigure 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".

Search the Entire CA APM Knowledge Base