IJ34198: MIGRATION COLLECTION VALIDATION STARTED BUT DOES NOT FINISH.

APAR status

• Closed as program error.

Error description

• ERROR DESCRIPTION:
  Migration Collection validation started but does not finish.
  
  PROBLEM:
  Migration validation started but did not finish. If you have a
  migration collection that you previously ran validation on, and
  attempt to run Validation Migration Collection again, Maximo
  will say the validation is already running. When you click
  refresh status the status block remain blank.
  The attempt to start the validation can take a couple of hours
  and nothing happens.
  
  Here is a sample of the errors found :
  
  ERROR] [dMX76MIF01] [CID-CRON-5207] BMXAA6713E - The MBO fetch
  operation failed in the mboset with the SQL error code -4470.
  The record could not be retrieved from the database. See the
  log file for more details about the error.
  com.ibm.db2.jcc.am.SqlNonTransientConnectionException:
  [jcc][t4][10335][10366][3.68.61] Invalid operation: Connection
  is closed. ERRORCODE=-4470, SQLSTATE=08003
  at com.ibm.db2.jcc.am.gd.a(gd.java:739)
  at com.ibm.db2.jcc.am.gd.a(gd.java:66)
  at com.ibm.db2.jcc.am.gd.a(gd.java:128)
  at
  com.ibm.db2.jcc.am.Connection.checkForClosedConnection(Connectio
  n.java:5829)
  at
  com.ibm.db2.jcc.am.Connection.nativeSQLX(Connection.java:1094)
  at com.ibm.db2.jcc.am.Connection.nativeSQL(Connection.java:1074)
  at psdi.server.ConRef.nativeSQL(ConRef.java:581)
  at psdi.mbo.MboSet.getNextRecordData(MboSet.java:3380)
  at psdi.mbo.MboSet.fetchMbosActual(MboSet.java:2948)
  at psdi.mbo.MboSet.fetchMbos(MboSet.java:2905)
  at psdi.mbo.MboSet.getMbo(MboSet.java:2121)
  at
  psdi.dm.collection.DmCollAsyncJobHandler.addRelatedOutOfOrderObj
  ects(DmCollAsyncJobHandler.java:1739)
  at
  psdi.dm.collection.DmCollAsyncJobHandler.findOutOfOrderRelatedOb
  jects(DmCollAsyncJobHandler.java:1907)
  at
  psdi.dm.collection.DmCollAsyncJobHandler.asyncProcess(DmCollAsyn
  cJobHandler.java:160)
  at
  psdi.common.asyncjob.AsyncJobCron.cronAction(AsyncJobCron.java:1
  49)
  at
  psdi.server.CronTaskManager.callCronMethod(CronTaskManager.java:
  2519)
  at
  psdi.server.CronTaskManager.access$1100(CronTaskManager.java:105
  )
  at
  psdi.server.CronTaskManager$CronThread.run(CronTaskManager.java:
  3429)
  at
  java.util.concurrent.Executors$RunnableAdapter.call(Executors.ja
  va:522)
  at java.util.concurrent.FutureTask.run(FutureTask.java:277)
  at
  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFuture
  Task.access$201(ScheduledThreadPoolExecutor.java:191)
  at
  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFuture
  Task.run(ScheduledThreadPoolExecutor.java:304)
  at
  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
  utor.java:1160)
  at
  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
  cutor.java:635)
  at java.lang.Thread.run(Thread.java:822)
  [10/16/20 0:30:45:708 CDT] 000002c6 SystemOut O 16 Oct 2020
  00:30:45:708 [ERROR] [dMX76MIF01] [CID-CRON-5207] The related
  records for the DMCOLLECTIONOBJECT could not be added to the
  migration collection. The DMCOLLECTIONOBJECT has a unique ID of
  360 in the validation job 1020. The error occurred when
  out-of-order related records were being added to the migration
  collection.
  psdi.util.MXSystemException: BMXAA6713E - The MBO fetch
  operation failed in the mboset with the SQL error code -4470.
  The record could not be retrieved from the database. See the
  log file for more details about the error.
  at psdi.mbo.MboSet.fetchMbosActual(MboSet.java:3114)
  at psdi.mbo.MboSet.fetchMbos(MboSet.java:2905)
  at psdi.mbo.MboSet.getMbo(MboSet.java:2121)
  at
  psdi.dm.collection.DmCollAsyncJobHandler.addRelatedOutOfOrderObj
  ects(DmCollAsyncJobHandler.java:1739)
  at
  psdi.dm.collection.DmCollAsyncJobHandler.findOutOfOrderRelatedOb
  jects(DmCollAsyncJobHandler.java:1907)
  at
  psdi.dm.collection.DmCollAsyncJobHandler.asyncProcess(DmCollAsyn
  cJobHandler.java:160)
  at
  psdi.common.asyncjob.AsyncJobCron.cronAction(AsyncJobCron.java:1
  49)
  at
  psdi.server.CronTaskManager.callCronMethod(CronTaskManager.java:
  2519)
  at
  psdi.server.CronTaskManager.access$1100(CronTaskManager.java:105
  )
  at
  psdi.server.CronTaskManager$CronThread.run(CronTaskManager.java:
  3429)
  at
  java.util.concurrent.Executors$RunnableAdapter.call(Executors.ja
  va:522)
  at java.util.concurrent.FutureTask.run(FutureTask.java:277)
  at
  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFuture
  Task.access$201(ScheduledThreadPoolExecutor.java:191)
  at
  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFuture
  Task.run(ScheduledThreadPoolExecutor.java:304)
  at
  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
  utor.java:1160)
  at
  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
  cutor.java:635)
  at java.lang.Thread.run(Thread.java:822)
  
  
  STEPS TO REPRODUCE:
  Steps to recreate migration collection problem.
  
  1. Create an automation script with a launchpoint on the POLINE
  object, for initialize value event.
  2. Create a Migration Collection, with AUTOSCRIPT application,
  DMSCRIPT object structure
  3. Define relate data rule to capture launch point
  4. Try to validate the Migration Collection, it will hang
  forever.
  
  
  CURRENT ERRONEOUS RESULT:
  Migration Collection validation started but is hanging.
  
  EXPECTED RESULT:
  Migration Collection validation started but does not hang.
  
  ENVIRONMENT (SYSTEM INFO):
  Server Information:
  App Server IBM WebSphere Application Server 9.0.5.5
  Version
  Tivoli's process automation engine 7.6.1.2-IFIX20200921-1601
  Build 20200715-0100 DB Build V7612-284 HFDB Build HF7612-07
  IBM Maximo Asset Management Work Centers 7.6.0.4 Build
  20200715-0100 DB Build V7604-119
  IBM Tpae Integration Framework
  7.6.1.2-MIF_7612_IFIX.20200909-1113 Build 20200715-1444 DB
  Build V7612-11
  Interloc Solutions, Mobile Informer 5.8.6. Build 20200813-1152
  DB Build V1000-01
  IBM Maximo Asset Management 7.6.1.2 Build 20200715-0100 DB
  Build V7611-01
  IBM Maximo for Transportation 7.6.2.5-20200103-1758 Build
  20180730-2210 DB Build V7625-10 HFDB Build HF7625-11
  IoT Connection Utility 7.6.0.3 Build 20200701-1409 DB Build
  V7603-32
  Server OS Linux 3.10.0-1127.19.1.el7.x86_64
  Server DB DB2/LINUXX8664 11.1 (SQL11014)
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * IJ34198 MIGRATION COLLECTION VALIDATION STARTED BUT DOES NOT *
  * FINISH                                                       *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package: release\fix pack for Release 7.6.1.3 Product
  

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:

Fix information

• Fixed component name

  SYSTEM CONFIG

• Fixed component ID

  5724R46S1

Applicable component levels