IJ41708: INTEGRITY CHECKER IN REPAIR MODE PRODUCES EXCEPTION DUE TO AUTO-COMMIT

APAR status

• Closed as program error.

Error description

• ERROR DESCRIPTION:
  When integrity checker runs in repair mode, and when fixing
  woancestor, it tries to commit, however, the connection passed
  to the process has auto-commit already set, which causes the
  following exception:
  BMXAA0443E -- Error - BMXAA6247E -- Ancestor table WOANCESTOR
  has bad data. Run Integrity Checker in repair mode to fix this
  data. Wed Jul 20 08:48:04 MST 2022
  Could not commit with auto-commit set on
  	at
  oracle.jdbc.driver.PhysicalConnection(PhysicalConnection.java:
  2171)
  	at
  oracle.jdbc.driver.PhysicalConnection(PhysicalConnection.java:
  2207)
  
  ENVIRONMENT
  Tivoli's process automation engine 7.6.1.2-IFIX20220506-1004
  Build 20200715-0100 DB Build V7612-284 HFDB Build HF7612-119
  Server DB: Oracle 19.0 (Oracle Database 19c Enterprise Edition
  Release 19.0.0.0.0 - Production Version 19.14.0.0.0)
  

Local fix

Problem summary

• ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * INTEGRITY CHECKER IN REPAIR MODE PRODUCES EXCEPTION DUE TO   *
  * AUTO-COMMIT                                                  *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the future release
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• MAXIMO
  

Fix information

• Fixed component name

  MAXIMO SYSTEMS

• Fixed component ID

  5724R46AV

Applicable component levels