I am not aware of the installer you are talking about, but you can use service name to connect to the rac instance if the service name is mapped in the tnsnames.ora file.
Processes with status “D” cannot be killed at all. They are in “D” status because they are sleeping and waiting for a resource like “Kernel lock” etc. which they will never get.
If you are seeing these ospid in v$process they will not allow “shutdown immediate” or “shutdown abort”.
The only way to remove such processes is to “reboot” server.
These processes cannot be traced down.
Check If you can apply Dead Connection detection (DCD) to avoid such situations in future.
Check your sqlnet.ora file, if there is any line like: SQLNET.AUTHENTICATION_SERVICES=(NTS)
Remove this line and try again.
2. For vip not getting started “CRS-1006: No more members to consider”:
It is very difficult error to sort out. You have to set tracing to know the exact reason for this.
I had this issue one time and eventually I had to recreate the entire system. But you can try to Remove the VIP resource and add it again and see what happens. Also what is the output of :
With Oracle 8 there was no RAC. It was OPS at that time.
With Oracle 9 and 10 you can install RAC and using VMware will be handy.
It will depend how you will be using RAC in real time and then decide on using virtualization or real environment. If you decide to use virtualization then also check out the paravirtualization support for RAC.
This blog reflect our own views and do not necessarily represent the views of our current or previous employers.
The contents of this blog are from our experience, you may use at your own risk, however you are strongly advised to cross reference with Product documentation and test before deploying to production environments.
Recent Comments