Aditi -
The 5.30-T2 oracle hot fix which is currently posted to the CA UIM Hotfix Index site addresses the problem you noted where some checkpoints enabled in the RAC templates are not enabled after the templates are applied to the RAC monitoring profile.
If Server 2 is one of the nodes in the Oracle RAC cluster you are monitoring from Server 1, then it should appear in the RAC profile you created in the oracle probe on Server 1 as one of the RAC specific nodes
You might be able to make a backup copy of the RAC checkpoints you want to enable so that you can get these setup by default in a new oracle probe deployment as follows (this assumes you are using the 5.30-T2 oracle probe in all cases).
1. From an oracle 5.30-T2 probe deployment delete all RAC profiles.
2. Enable the checkpoints you need to monitor in the RAC Common and RAC specific templates defining thresholds that you want for the enabled checkpoints. Disable the checkpoints you do not want to monitor. NOTE: Do not disable the check_dbalive checkpoint in the RAC common template. If this checkpoint is disabled, the probe may not execute any of the other enabled checkpoints.
3. Save the changes.
4. Drag and drop a copy of this oracle probe from the robot to the local archive on your primary hub to create a configuration only oracle probe package - make sure your rename the package before saving it.
5. Edit the new oracle configuration only package you created, then edit the oracle.cfx file in the package. Remove all sections from the oracle.cfx file except the <rac_common_checkpoints> and <rac_specific_checkpoints> sections and their contents. Save the change to the oracle.cfx file then save the modified oracle configuration only package.
6. After deploying the 5.30-T2 probe to an new robot, deploy the oracle configuration only package then from the Admin Console create your RAC connection profile followed by the RAC profile
For the connection error you are now seeing from the probe, have you tried testing the connection to the configured Oracle RAC cluster? Does the connection test succeed? If not, you need to determine what is preventing the probe from connecting to the configured Oracle RAC cluster. If the connection test succeeds, then you need to change the oracle probe's loglevel to 5 and logsize to 80000, apply the changes and restart the probe. Allow the probe to run for a couple of monitoring intervals then check the logs to see if you can determine why the checkpoint is failing. If you cannot figure this out from the logs, then open a case posting the logs and the oracle_monitor.cfg file to track down the problem.
Hope this helps.