Database - RAC/Scalability (MOSC)

MOSC Banner

Why does the CRSD daemon stop running?

edited Feb 10, 2014 6:20AM in Database - RAC/Scalability (MOSC) 4 commentsAnswered

Hi,

My customer has a pair of IBM servers running AIX 6.1 and Oracle 11.2.0.3, which run in an active/passive configuration (non-RAC) with IBM’s ‘Power HA’. Oracle ‘Grid Infrastructure’ is also installed as the database uses ASM for its data files, and Oracle Clusterware and the ASM instance are started and run on the active server.

Whilst I appreciate that this may not be the ideal configuration, this is what the customer has, and he cannot change it (at least, not in the short term). The problem is that the crsd daemon stops occasionally and the clusterware has to be bounced to restart it. It is unclear why this daemon stops (I have examined the clusterware alert log, the crsd log and the ohasd log, together with other logs which did not contain a reference to this problem), and my question is – is there any tracing or similar which we could configure before bouncing the

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