Record at dbkey <num>:<num>:<num> in table "<str>" version <num>
  does not match current version

  Explanation:  The specified record in  the  after-image  journal
  was  found  with a record version number that is not the same as
  the current highest  version  of  the  record  in  the  database
  metadata.  This may be caused by changes to the table definition
  while the  LogMiner  is  running  or  during  the  span  of  the
  after-image journal that is being unloaded.

  User Action:  The LogMiner does not handle different versions of
  table metadata during an unload operation.  The correct sequence
  of events when using the  LogMiner  and  making  table  metadata
  changes  is  to  unload  all of the AIJ files, then shutdown the
  LogMiner  (if  needed),  make  the  metadata  changes  and  then
  re-start  unloading form the after-image journal.  This sequence
  ensures that the LogMiner always processes records that  are  of
  the current metadata version.