Has anyone applied Update Bundle 3? I got an error and now ECC is broken

I have come across a couple of UB3 installation issues but not one with the errors mentioned in your upgrade log.

Best to let Support fully investigate the issue.


Regards,
Séamus

I'm not sure why the upgrade failing would have left you in a broken state. It should have backed out anything it did and left you where you started unless it was something really serious. So I just have a few questions to get you thinking in what might be the right direction:

* did you go through the steps to prepare for a rollback prior to starting the upgrade? If so, you should be able to roll back and at least get up and running until Support can figure out what went wrong. It might overwrite something they need to figure it out, but at least you will have a working implementation.

* did you follow the instructions about changing the PATH to ensure you point to the right DLL during the upgrade process. The errors you mentioned look suspiciously like the ones I believe indicate the DLL conflict errors (although I'm sure other things can generate the same errors).

If you didn't do the PATH change before upgrading I would suggest rolling back and then trying the upgrade again with the PATH configured properly.

Otherwise I guess you will just have to wait for Support. Please let us know here what they come back with.

Is this something new with UB3?

I've done lots of patches and service packs in the past and unless I'm remembering wrong, they would typically try to back out the changes if it failed somewhere during the process.

I agree with Mark. You need to roll back manually. However, as Allen mentioned, the PATH could be an issue here, though I faced the same issue with UB3 even after having my PATH set appropriately. Then I had to roll back manually and apply patch 4414 instead, which worked fine.

Hi,

The Repository upgrade requires the use of 2 SSL related dlls ¿ libeay32.dll and ssleay32.dll. These DLL's are shipped with the upgrade software. However there are other applications that can also use these dlls and this can conflict with the upgrade. Our upgrade executable requires the 2 above dlls. The other apps that use these dlls are putting their app paths in the system %PATH%. If this is before our entry for the ramb_scripts folder (where the dlls are shipped to) then the upgrade exe picks these up instead. The problem is that the versions of the dlls are usually different from the ones we ship and it halts our upgrade.

The current work around is to add the \Repository\admin\Ramb_scripts folder to the very start of the %PATH% variable before upgrade.

After changing the path variable, set all the ControlCenter AND Oracle services to manual and then reboot the server. Once it comes back up, restart the Oracle services manually and start the upgrade.

Regards
Nimai