Service IO Too Many Records for execution

[Jean-Paul GAUGER]

Bonjour à tous,

Depuis la dernière réorg à chaud nous avons un noeud en 6.10.1 sous Windows 2012 Serveur qui ne fonctionne presque plus.

Le journal du noeud se rempli à raison de plus de 60 messages par secondes de ce type  : |ERROR|X|IO |pid=1148.3056| GAGESHIS | Too Many records for execution.

Les traitements semblent s'exécuter correctement, mais au bout d'un certain temps, le noeud arrête les exécutions.

Entre la réorg et l'apparition de ce message, il n'y a pas d'information d'un quelconque problème.

Auriez vous déjà rencontré ce type de problème ?

Ou avez-vous des opérations de maintenance qui pourrait nous aider à stabiliser notre noeud ?

En vous remerciant par avance pour votre aide.

------------------------------
Cordialement,

Jean-Paul GAUGER
Responsable Pôle Opération Informatique - DSI - Groupe Beaumanoir.
------------------------------

[Jean-Paul GAUGER]

Le problème est clos en suivant la procédure ci-dessous :

The errors appear to originate due to an issue with the Launcher data files.

I reinitialized the Launcher data files and the errors stopped being logged.

Before restoring to the previous version, could you please perform the following procedure to see if it resolves your issue:

~~~~~~~~~~

Warnings concerning this procedure :

-THE IMPACT OF THIS MANIPULATION WILL BE THE DELETION OF THE PREVIOUS LAUNCHES.

-THE LAUNCHES GENERATED BY A SCHEDULED TASK MUST BE RECREATED AFTER THE ENGINES ARE STARTED.

-THE MANUAL LAUNCHES OR THE LAUNCHES GENERATED BY AN UXORDRE WILL HAVE TO BE MANUALLY RECREATED.

Procedure :

1. Copy / Paste the jobs in status "Launch Wait / Event Wait" from UVC - Job Runs or via the command "uxlst fla full" to know what was supposed to be launched next.

2. Shutdown the Dollar Universe and check that all process are down

3. Backup the launcher data files of the concerned area (u_fmsb60.dta, u_fmtp60.dta, u_fmsp60.dta)

4. Load the Dollar Universe environment

5. Reinitialize the launcher data files of the concerned area by executing the following commands from the bin folder

Example for the area EXP (X):

 - uxrazfic u_fmsp60 X

 - uxrazfic u_fmsb60 X

 - uxrazfic u_fmtp60 X

6. Reorganize the data files and then start the node again, using the following commands:

 - unireorg

 - unistart

7. If tasks with "Start Date" in the past are not recalculated, launch the following two commands:

uxupd tsk tsk=*

uxupd tsk tsk=* ses=*