Apex 4.1 to 4.2.6 patch issues

This week we thought we'd a simple Apex patch to do but it didn't turn out that way...

So after some time spent fixing the issues after we did this in the dev/test environment (changes to session state protection caused a load of hassle) - something that was introduced in a minor patchset in 4.1 that we hit after upgrading, we then wanted to move forward and upgrade the real system.

So we told all the users to come off the system and began running the upgrade script - to start with all looked fine - this kind of stuff (that big text oracle really didn't paste well....)

So what to do now - did we have to restore everything? Could we run it again?

Well after a bit of checking it seemed the solution was easy - as the upgrade had left the original schema untouched (APEX_040100) we could simply drop the new one and try again - great! However whats blocking the package from being replaced?

We decided to just ran that package header in and see what was blocking it, we tracked down the Apex source file and ran it in - and sure enough again it hung. A bit of investigation then revealed that we had some old rogue connections as the ANONYMOUS account(we are using EPG) that seemed to be holding locks. So we killed these off and the package replaced fine.

So now we just had to re-run....and now it runs through fine and we see this kind of stuff in the end

timing for: Install Internal Applications

Elapsed: 00:13:20.62

Thank you for installing Oracle Application Express.

Oracle Application Express is installed in the APEX_040200 schema.

The structure of the link to the Application Express administration services is as follows: