OpenTP1 Version 7 Messages
cannot start aaaa (xx...xx) journal file service. reason code=bbbb
Reason code | Meaning | Countermeasure |
---|---|---|
101 | Insufficient memory | Check the amount of used memory. |
103 | Network failure | Recover the system from the failure and restart it. |
114 | The message queue ID table in the system does not have a free area. | Re-configure the kernel by changing the maximum allowable number of message queues specified in the system parameter. For details, see the relevant OS documentation. |
116 | An attempt was made to re-create the deleted message queue, but failed due to lack of free area in the message queue ID table in the system. | Use the current node for journal operation until the next normal start or restart. Reconfigure the kernel by changing the maximum allowable number of message queues specified in the system parameter. For details, see the relevant OS documentation. |
405 | An error is detected during definition analysis processing. | Check and correct the definition file. Then, restart the system. Message KFCA002XX shows details of the error. |
414 | The number of valid journal file group definitions is smaller than the minimum number of generations required for system startup. | Correct the system journal service definition or the jnladdfg definition for the archive journal service definition, and then restart the system. |
416 | The number of jnladdpf definition commands having the same file group name is smaller than the value specified in the jnl_min_file_dispersion operand. | Correct the system journal service definition or the jnladdpf definition for the archive journal service definition, and then restart the system. |
418 | The value specified in the jnl_min_file_dispersion operand is greater than the value specified in the jnl_max_file_dispersion operand in the system journal service definition or archive journal service definition. | Correct the values of the jnl_max_file_dispersion and jnl_min_file_dispersion operands in the system journal service definition or archive journal service definition. |
420 | The set jnl_arc_name operand is specified in the system journal service definition. TP1/Multi, however, is not installed. | Install TP1/Multi if it is not installed. If it is installed, check the multi_node_option operand is specified in the system common definition. |
425 | The value specified in the jnl_arc_max_datasize operand in the system journal service definition is incorrect. | Correct the value of the jnl_arc_max_datasize operand, and then restart the system. |
426 | A value greater than 1020 is specified in the jnl_arc_max_datasize operand in the system journal service definition or archive journal service definition, but a small value is specified in the rpc_max_message_size operand in the system common definition. | Correct the value of the jnl_arc_max_datasize operand or the rpc_max_message_size operand, and then restart the system. |
427 | The value specified in the jnl_arc_buff_size operand in the system journal service definition is invalid. | Correct the value of the jnl_arc_buff_size operand, and then restart the system. |
503 | An error occurred during I/O processing of the status file. | Investigate the cause of error, correct the error, and restart the system. |
506 | An error occurred while starting the journal I/O service process. | |
510 | An error occurred during the journal file check processing. | Investigate the cause of error, correct the error, and restart the system. Details of the cause of the error are displayed before this message. |
513 | An error occurred while starting the service recovery journal service. |
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.