After power failure Jobs fail with status Aborted or remain in Launch Wait status
search cancel

After power failure Jobs fail with status Aborted or remain in Launch Wait status

book

Article ID: 85586

calendar_today

Updated On:

Products

CA Automic Dollar Universe

Issue/Introduction

Affects Release version(s): 5

Error Message :
There might be some errors during offline file Reorganization (ux_vrf_rgz_rst) indicating that u_fmhs50 or u_fmsb50 are corrupted

Patch level detected:Dollar Universe 5.6
Product Version: Dollar.Universe 5.6.0 FX25010
After power failure Jobs fail with status Aborted or remain in Launch Wait status

Environment

OS: All

Cause

Cause type:
Other
Root Cause: File corruption due to a violent stop of Dollar Universe.

Resolution

Follow PROCEDURE 1 (u_fmhs50) and / or PROCEDURE 2 (u_fmsb50), depending on whether your have error messages related to u_fmhs50 or u_fmsb50 :

BEWARE: 
For all procedures: Mandatory Backups / Safety Measures
Please backup all the data files of the concerning area.

PROCEDURE 1:
How to reinitialize and the impact of re-initializing the u_fmhs50 and related data files.

Prerequisites
  • The data files are proven corrupted and the reinitialization of the u_fmhs50 data file is absolutely necessary. The following reasons could be the indications that the dat file is corrupted. This may occur after a system issue : file system full, or a system crash
  • If, each time you submit a job, the history trace only contains :
Execution zzzzzzz unknown in the history file
  • If the IU_PUR cannot purge the old history traces anymore and/or the size of these files is too large.

Explanation.
The data file u_fmhs50 must be reinitialized with another data file u_fmph50. The data files u_fmhs50 and u_fmph50 contain the Execution History and technical pointer, respectively, of the Dollar Universe jobs. These two files are present in each area.

BEWARE:
All the history traces of the previously executed jobs will be lost. The variables of a previously aborted job will be lost, this will impact the relaunch of any job which aborted before the initialization.

Implementation Procedure.
For this example, the data files you want to reinitialize belong to the Production area(X).

On Unix:
(a)Prerequisites
You need to load the Dollar Universe environment and log on as the Dollar Universe administrator.

(b)Stop your Dollar Universe Company
${UXMGR}/uxshutdown

(c)Check that your company is well stopped
Type the following unix command:
ps -ef | grep ux | grep -v cuxxm | grep -v grep
No uxioserv processes should remain alive for this company.

 
(d)Launch the following commands
$UXMGR/ux_raz_fic u_fmhs50 X
$UXMGR/ux_raz_fic u_fmph50 X

${UXMGR}/ux_vrf_rgz_rst > ${UXLEX}/reorg.log 2>&1

(e)Restart your Dollar Universe Company
      ${UXMGR}/uxstartup

On Windows:
(a)Prerequisites
You need to load the Dollar Universe environment and log on as the Dollar Universe administrator.

(b)Stop your Dollar Universe Company
%UXMGR%\uxshutdown

(c)Check that your company is completely stopped
In the Windows services panel or through a net start, please check if your Univer$e _IO_ services are well stopped.

(d)Launch the following commands:
%UXEXE%\uxrazfic u_fmhs50 X
%UXEXE%\uxrazfic u_fmph50 X


%UXMGR%\ux_vrf_rgz_rst

(e)Restart your Dollar Universe Company
%UXMGR%\uxstartup


PROCEDURE 2:
How to reinitialize and the impact of re-initializing the u_fmsb50 and related data files.?

Prerequisites

The data files are proven corrupted and the re-initialization of the u_fmsb50 data file is absolutely necessary. The following reasons could be the indication that the data file is corrupted:
  • No launches are created.
  • The data file size has significant size or it has reached it maximum limit of 2GB
  • There''s an error message on the data files when executing the reorganization.
Application Validation Tests
Explanation

The data file u_fmsb50 must be reinitialized with two other data files :u_fmsp50 and u_fmtp50.

These data files contain the expected launches:

The data file ufmsb50 contains the launch data.
The u_fmsp50 and u_fmtp50 contains the parameters and variables.

The root cause for this issue is usually a file system full or an unexpected stop of the machine.

BEWARE
  • 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.

Mandatory Backups / Safety Measures
  • Please backup all the data files of the concerning area.
  • Implementation Check
In Case The Procedure Is Unsuccessful

Please send us the uxtrace result executed with option -scf9 for Unix or X9CS for Windows.

Implementation Procedure

For this example, the data files you want to reinitialize belong to the Production area(X).

On Unix:
(a)Prerequisites:
You need to load the Dollar Universe environment and log on as the Dollar Universe administrator.

(b)Stop your Dollar Universe Company.
${UXMGR}/uxshutdown

(c)Check that your company is well stopped
Type the following unix command:
ps -ef | grep ux | grep -v cuxxm | grep -v grep
No uxioserv processes should remain alive for this company.

(d)Launch the following commands
$UXMGR/ux_raz_fic u_fmsb50 X
$UXMGR/ux_raz_fic u_fmsp50 X
$UXMGR/ux_raz_fic u_fmtp50 X


${UXMGR}/ux_vrf_rgz_rst > ${UXLEX}/reorg.log 2>&1

(e)Restart your Dollar Universe Company
${UXMGR}/uxstartup

On Windows:
(a)Prerequisites:
You need to load the Dollar Universe environment and log on as the Dollar Universe administrator.

(b)Stop your Dollar Universe Company

%UXMGR%\uxshutdown

(c)Check that your company is well stopped
In the Windows services panel or through a net start, please check if your Univer$e _IO_ services are completely stopped.

(d)Launch the following commands

%UXEXE%\uxrazfic u_fmsb50 X
%UXEXE%\uxrazfic u_fmsp50 X
%UXEXE%\uxrazfic u_fmtp50 X


%UXMGR%\ux_vrf_rgz_rst
(e)Restart your Dollar Universe Company
%UXMGR%\uxstartup


Fix Status: No Fix

Fix Version(s):
N/A

Additional Information

Workaround :
N/A