Oracle Solaris Cluster (MOSC)

MOSC Banner

Cluster 3.2: (Oracle 12c database resource error) 412106 unable to get fault monitor name

edited Jun 20, 2016 10:29AM in Oracle Solaris Cluster (MOSC) 5 commentsAnswered

We'd like to know if anyone is running Oracle 12c on Cluster 3.2 successfully. We're hoping to defer an upgrade to Solaris Cluster 3.3 from 3.2 to resolve: "412106  Internal Error. Unable to get fault monitor name." On a two-node Cluster 3.2, SPARC, Solaris 10 u11 we added and oracle.server resource to an existing working resource group that runs Oracle database 11. We set permissions in the new database per Data Services Guide, ran root.sh in the new ORACLE_HOME $PATH. The new resource momentarily starts but immediately shuts down due to a monitor fault.

Tagged:

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