Tuesday, June 30, 2009

PCP in Non-RAC Instances - Pitfalls -- Solutions?

In the last post, I had talked about the pitfalls in configuring PCP in non-RAC instances. I have figured out (is it really the solution? - only time will tell!) workarounds for the 2 pitfalls that I had listed.

1. How would the VNC server failover when using PCP with non-RAC?

Ans: The best bet would be to start the vnc server using the virtual hostname instead of the physical hostname (thanks to my colleague Mansoor who suggested it).

Once the VNC is started using the virtual hostname, set the display variable to this value and run autoconfig so that the changes are reflected in the concurrent manager and the report server startup scripts.

So, when the VIP (and hence, the virtual host) fails over, the VNC would still be running. This solution needs to be tested thoroughly though.

Below is the command that I can use:

$ vncserver -name <VIRTUAL_HOSTNAME>:<PORT_NUMBER>

2. The web tier 806_ORACLE_HOME tnsnames.ora can be modified to include the FNDFS_<PHYSICAL_HOSTNAME> entry for both the primary server and the failover server. This way, there is no need to reconfigure it each and every time.

Of course, this tnsnames.ora should be saved before running autoconfig else it would be overwritten.

Signing off hoping that the above solutions work!

No comments: