oracle-databasepatchoracleforms

Oracle Forms 6i crashes with 0xC0000005 at start after installing patch 19


UPD. 0xC0000005 is STATUS_ACCESS_VIOLATION, defined in winnt.h. Meaning the app has tried to access a memory it doesn't have access to. Most of the time it's dereferencing a null pointer.


In short.
After patch 19 has been installed I can't run any form: compiled with patch 18 or 19, by myself or others. Immediately after starting I get Windows error:

--------------------------------
ifrun60.exe ....
--------------------------------
The application failed to initialize properly (0xC0000005). .....
--------------------------------

Details

What I've tried

Why do I need this
The main reason is that this patch fixes some weird behaviour that presents only on my machine (in team of 7) - I'm getting error while trying to assign global variable. It always disappears after re-compilation on any other machine and sometimes (what the... ?!) after my own recompilation later

And the second reason is, well, just curiosity because I've almost broken my brain trying to make this work


Progress
2010.02.11 - I've just found out (thanks to ProcMon), that the last action before crush is loading ifrcm60.dll (with SUCCESS result code).
I've tried to replace this DLL with version from patch 18 and then ifrun60.exe complains about wrong DLL

2010.02.16 - Dr Watson doesn't generate any info

2010.03.02 - Support (including extended) for Designer 6i came to end on 31 dec 2008, so I can't rise support request.
Also the only mention of this problem I was able to find is the dead thread (2 y.o.) on Oracle forums

It seems to me, that the only way to solve this will be to defenestrate my PC... any other suggestions ? :)


Solution
OK, I give up. Just reinstall Windows (love this solution in any situation :) (I've done Win7 32 bit)


Solution

  • If you are installing patches then presumably you have an Oracle Support account. If so, I urge you to raise an SR with them. Or - as I'm not sure that Forms 6i is still supported - search the Metalink Knowledge Base for solutions.

    Because this is going to be something really obscure in your set-up. There is a thread in the Tech Guy forum which covers the sort of techniques you need to deploy in diagnosing this. Find out more.