Description :After uxioserv receives a signal 11 and crashes, once $U is restarted, the jobs display as RUNNING, when they should be in ABORTED status. Confirmed that the PID was not present on the system, so the status of the job should have been ABORTED after they system was restarted.
Cause
Cause type: Other Root Cause: The issue could be from data file corruptions.
Environment
OS: Linux
Resolution
To fix this issue, we would recommend reinitializing the related data files.
Please note that after this procedure the current execution, history trace, future launch and event wait records will be removed. All of the launches generated from scheduled tasks will be automatically recreated.
(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_raz_fic u_fmcx50 X $UXMGR/ux_raz_fic u_fmfu50 X $UXMGR/ux_raz_fic u_fmsb50 X $UXMGR/ux_raz_fic u_fmsp50 X $UXMGR/ux_raz_fic u_fmtp50 X $UXMGR/ux_raz_fic u_fmpi50 X ${UXMGR}/ux_vrf_rgz_rst > ${UXLEX}/reorg.log 2>&1
(e) Restart your Dollar Universe Company ${UXMGR}/uxstartup