java.sql.SQLIntegrityConstraintViolationException - ORA-01400: cannot insert NULL into ("CA_APM"."APM_OWNER"."NAME")
search cancel

java.sql.SQLIntegrityConstraintViolationException - ORA-01400: cannot insert NULL into ("CA_APM"."APM_OWNER"."NAME")


Article ID: 8605


Updated On:


CA Application Performance Management Agent (APM / Wily / Introscope) INTROSCOPE


 In the IntroscopeEnterpriseManager.log file, seeing the error below:

[ERROR] [PO:AppMapAgentPO Mailman 1] [Apm.Data.Model] Root SQL Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-01400: cannot insert NULL into ("CA_APM"."APM_OWNER"."NAME")


All APM Enterprise Managers configured in the role of Collector, version 10.1 and above.


  In this situation, the Collectors were likely upgraded, but the configuration item to enable the Application Triage Map feature is still enabled.


On all collectors in the cluster, change the setting below:

introscope.apm.feature.enabled= true 

to be:

introscope.apm.feature.enabled= false 


Once the change is made, restart the MOM and all Collectors, and the error messages will cease.

Additional Information

 In versions of APM prior to 10.1, each collector contributed entries for the Application Triage Map and/or Team Center into the APM database. Beginning with APM 10.1, the task of populating Team Center became the exclusive responsibility of the MOM, which collects and correlates traces from all collectors, then writes the entries to the APM database. Since the MOM is creating all entries for Team Center, the Collectors are also trying to populate the tables in the APM Database, so disabling the collectors from trying to add entries in the APM Database alleviates this condition.