This content has been marked as final. Show 20 replies
oh. Sorry, did not correctly understand your post. When you said you "cancelled it here", you ment the output. I was thinking you stopped cluvfy again, because it "stalled" the listener again...
So it worked for you now, with the GI user and without problems?
cluvfy stage -pre crsinst -upgrade -n db1,db2 -rolling -src_crshome /oracle/app/11.2.0/grid -dest_crshome /oracle/app/grid/184.108.40.206/grid -dest_version 220.127.116.11.0 worked for me from the cluster verify downloaded/bin... Than you for your suggestion.
I have resolved one other cluvfy failure was something ntp related... Only PATCH 9413827 is missing, any suggestion please? Do I need to apply this patch directly or some other PSU which will cover this patch?
Check for Oracle patch "9413827" in home "/oracle/app/11.2.0/grid" failed Check failed on nodes: db1,db2
no you need this patch seperately on the 18.104.22.168 GI (to 22.214.171.124.X PSU, before you can upgrade to 126.96.36.199):
That is what the patch means...
Yes, that is why I asked, yes patch for bug 9413827 or some other bug fix, because actually it is also a bug :) I guess I need to apply 9655006 to 188.8.131.52 GI home before upgrade, right?
The problem is that the upgrade test actually tests for the presence of patch 9655006 and if not found reports that 9413827 is not installed.
Just this little confusion, then I am about to close this thread as "answered"
P.S: Shönes wochende :-)
Thank you very much.
As the cluvfy suggests that 9413827 is missing, and the MOS note id you suggested also says to apply this patch instead of something else.
Thank you for continuously following this thread.