Re: ODA update to 12.1.2.5.0 node 2 hostname reset

I guess either ODAs are not very popular, or I have all the luck in the world, finding arcane bugs..

Just to document it in case anyone needs it in the future: somehow the hostname was changed in /etc/sysconfig/network. Changing it back and a reboot solved the problem. Simple on hindsight, but it just took Oracle more than 6 hours of pouring over logs to come up with the solution.

Cudos to the MOS support guy who was very diligent and helpful! Should happen more often.

Cheers,
Tony

On 13/07/16 21:15, De DBA wrote:
> G'day
>
> I'm in the process of patching the least significant of a number of ODAs from OAK 12.1.2.2.0 to 12.1.2.5.0. Everything seemed to go swimmingly until the reboot, some 80 minutes after starting the first stage (INFRA).
>
> The first node came back up perfectly, CRS and ASM started normally - no errors. However, somehow the host name on one node (node 2) was reset to 'oak2' and nothing besides the OS and oakd started. Has anyone seen this before?
>
> OHASD complains that the autorun file is missing. I admit that I haven't a lot of experience with CRS and OHASD, but I wonder if that can be reduced back to the changed hostname? Provided that nothing else was destroyed by the update, would changing the hostname back to what it should be allow OHASD to start?
>
> Cheers,
> Tony
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

--
http://www.freelists.org/webpage/oracle-l