|
CRS-05014: Agent “string” timed out starting process “string” for action “string”: details at “string” in “string”
Cause: The named agent aborted the named process because the process failed to respond within the timeout period.
Action: Check the agent log files for further information.
CRS-05818: Aborted command ‘string’ for resource ‘string’. Details at string in string.
Cause: Execution of the specified command was aborted due to a timeout.
Action: Restart the resource manually. If the problem persists, contact Oracle Support Services.
CRS-07510: The ‘daemon thread’ of Oracle Grid Interprocess communication (GIPC) has been non-responsive for ‘number’ milliseconds. Additional diagnostics: process name: ‘string’.
Cause: The reason for this issue was one of the following: - The ‘daemon thread’ was not scheduled by the operating system in a timely manner. - The ‘daemon thread’ of Oracle Grid Interprocess Communication (GIPC) was hung.
Action: (a) Check if the ‘daemon thread’ of Oracle Grid Interprocess Communication (GIPC) is hung. (b) Reduce the load on the system or add a new node to the existing cluster, if the system is heavily loaded.
CRS-01612: Network communication with node string (number) has been missing for 50%% of the timeout interval. If this persists, removal of this node from cluster will occur in number.number seconds
Cause: Heartbeat messages were not received from the node. This could be due to network problems or failure of the listed node.
Action: If the node was removed, check that the private interconnect network used by the cluster is functioning properly, including all the cables, network cards, switches, routers, and so forth between this node and listed node. Correct any problems discovered.
CRS-01727: Network communication between this node ‘string’ (number) and node ‘string’ (number) re-established. Node removal no longer imminent.
Cause: None.
Action: None.
CRS-07509: The ‘worker thread’ of Oracle Grid Interprocess communication (GIPC) has been non-responsive for ‘number’ milliseconds. Additional diagnostics: process name: ‘string’.
Cause: The reason for this issue was one of the following: - The ‘worker thread’ was not scheduled by the operating system in a timely manner. - The ‘worker thread’ Oracle Grid Interprocess Communication (GIPC) was hung.
Action: (a) Check if the ‘worker thread’ of Oracle Grid Interprocess Communication (GIPC) is hung. (b) Reduce the load on the system or add a new node to the existing cluster, if the system is heavily loaded.
CRS-05050: HAIP failover due to network interface string not functioning
Cause: There was a problem with the network interface used for highly available IP (HAIP).
Action: Confirm that the network interface is up and running on this node.
CRS-00001 to CRS-48005
|