Exadata General (MOSC)

MOSC Banner

Node Reboot due CRS issue

edited Jun 4, 2015 10:06AM in Exadata General (MOSC) 6 commentsAnswered
Hi

We have two node cluster in Exadata X2 env and on 15th Aut at 5pm EST  node 2  got hang and reboot.After inititial investigation we found that it happened because of CRS but don't understand why crs rebooted node 1

Here are are the logs.

********************&**************

ctssd(23059)]CRS-2409:The clock on host ed1qdb01 is not synchronous with the mean cluster time. No action has been taken as the Cluster Time Synchronization Service is running in observer mode.
2013-08-15 12:18:00.047
[ctssd(23059)]CRS-2409:The clock on host ed1qdb01 is not synchronous with the mean cluster time. No action has been taken as the Cluster Time Synchronization Service is running in observer mode.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center