PCP Setup is not working properly, unable to start the concurrent manager on N2

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Problem:     PCP Setup is not working properly, unable to start the concurrent manager on N2

Configured the PCP setup after cloning but the Concurrent manager is not starting on node 2 when node 1 was down.

Symptoms:

Failover issue, if Node 1 is down Node2 is not coming up.

Managers are running on both nodes, ICM is on node 1.

FNDIMON is running on both nodes before that node 1 is down? {FNDIMON is running on only 2nd Node.}

Solution:

FNDIMON should run on both nodes. 
So it should run on Node 1 before you put it down. 
Go to System Administrator / Concurrent / manager / define 
and query the fndimon for node 1. 
Click on Work shifts button and check that you have declared 1 process. If not please do it .
Save and go to Concurrent / manager / Administer 
Check that FNDIMON is ok on both nodes. 
Retest the issue after you are sure the FNDIMON is running on both nodes (Actual= Target =1)

 How do you put the node 1 down ? 
Using adstpall.sh

this is why you are not getting a failover! 
Adstpall.sh will not give you a failover. 
To get a failover you should bring down your node . Failover will happen when it is not possible to ping the node 1 . 
adstpall only shutdown services normaly and we can still ping the node . 
Summary : if Node1 is still available and pingable , there will not be a failover.

References:

Note 743716.1 How to Setup and Test Failover of PCP on Non-RAC Environments.

Get Oracle Certifications for all Exams
Free Online Exams.com