After a System crash / Power Outage the Dollar Universe node does not work properly
Article ID: 86873
Updated On:
Products
CA Automic Dollar Universe
Issue/Introduction
Error Message :
Depending on what was happening at the time of the shutdown/crash, there could be many different error messages, such as:
|FATAL|X|IO |pid=1972.2608| o_ord_cycle | Launcher cannot submit jobs anymore: stopping. Please purge executions before restarting
-- Or the data file may have been marked as invalid, with a _inv added to the end of the data file name.
Patch level detected:Dollar Universe 6.3.00
When Dollar Universe is not stopped properly, or there is a power failure and the system crashes, a data file corruption may occur.
Depending on what was happening at the time of the shutdown/crash, there could be many different error messages, such as:
|FATAL|X|IO |pid=1972.2608| o_ord_cycle | Launcher cannot submit jobs anymore: stopping. Please purge executions before restarting
-- Or the data file may have been marked as invalid, with a _inv added to the end of the data file name.
Patch level detected:Dollar Universe 6.3.00
When Dollar Universe is not stopped properly, or there is a power failure and the system crashes, a data file corruption may occur.
Cause
Cause type:
Other
Root Cause: Dollar Universe was not shutdown properly.
In case it was, the following message should be displayed in the universe.log file:
|INFO |X|IO |pid=1972.2024| u_io_srv_main | End of IO server: company [COMPANY_NAME] area 'X
Other
Root Cause: Dollar Universe was not shutdown properly.
In case it was, the following message should be displayed in the universe.log file:
|INFO |X|IO |pid=1972.2024| u_io_srv_main | End of IO server: company [COMPANY_NAME] area 'X
Environment
OS: All
Resolution
Depending on the type of data corruption,it may be necessary to restore or reinitialize one of the affected data files.
2) Load the environment: unienv.bat
3) Backup the impacted data file
4) Fix the impacted data file either by restoring it or by a reinitialization.
5) Launch a reorganization:
%UNI_DIR_EXEC%\unireorg > reorg.log
6)Start $U
2) Load the environment: . ./unienv.ksh
3) Backup the impacted data file
4) Fix the impacted data file either by restoring it or by a reinitialization.
5) Launch a reorganization:
$UNI_DIR_EXEC/unireorg > reorg.log
6)Start $U
Fix Status: No Fix
The procedure for Windows is:
1) Stop Dollar Universe2) Load the environment: unienv.bat
3) Backup the impacted data file
4) Fix the impacted data file either by restoring it or by a reinitialization.
- a) Either restore the impacted data file from a system backup
- b) Or reinitialize the impacted data file via the command uxrazfic
- %UNI_DIR_EXEC%\bin\uxrazfic NAME_OF_THE_FILE AREA
5) Launch a reorganization:
%UNI_DIR_EXEC%\unireorg > reorg.log
6)Start $U
The procedure for Unix is:
1) Stop Dollar Universe and all the processes2) Load the environment: . ./unienv.ksh
3) Backup the impacted data file
4) Fix the impacted data file either by restoring it or by a reinitialization.
a) Either restore the impacted data file from a system backup
b) Or reinitialize the impacted data file via the command uxrazfic
$UNI_DIR_EXEC/uxrazfic NAME_OF_THE_FILE AREA
5) Launch a reorganization:
$UNI_DIR_EXEC/unireorg > reorg.log
6)Start $U
Fix Status: No Fix
Additional Information
Workaround :
N/A
N/A
Feedback
Powered by
