universe.log filled with Type not valid for exchange numlot:XXX Exchange stopped

Products

• Automic Dollar Universe

Issue/Introduction

The universe.log contains a lot of messages every time the exchanger performs an exchange with the following message:

|INFO |X|IO |pid=p.t | o_module_exc_cycle_emissi | Type not valid for exchange numlot:XXXXXX. Exchange stopped

Environment

Dollar Universe 6.x and 7.x

Cause

Incoherence in the exchanger data files, somehow there's just one record of type EVENEXEC in u_fecl60.dta with the numlot XXXXXX, but if we look into the u_fecd60.dta we find one related to EVENEXEC and two related to SIDBATCH which is not normal. 

Resolution

In this kind of case, only the reinitialization of the two exchanger data files (u_fecl60 and u_fecd60) can help.

So the procedure is:

1. Load the environment as the administrator of the node and then stop the node
2. Backup u_fecd60.dta and u_fecl60.dta from the folder data/xxx (being xxx the area, ie. exp for X)
3. Launch the uxrazfic (available on the bin folder) for the two files of the impacted area (replace X by A,I or S if it's another area that is impacted) --- THIS NEEDS TO BE DONE AS THE OWNER OF THE NODE which is the owner of the previously backuped data files:
   uxrazfic u_fecl60 X
   uxrazfic u_fecd60 X
4. Launch a reorganization of the node:
   unireorg
5. Start the node:
   unistart

Additional Information

This procedure is explained in some other articles such as:

https://knowledge.broadcom.com/external/article/87151/duas-error-600-populating-exchange-data.html