This content has been marked as final. Show 4 replies
I see this all the time with 64-bit SQLDevelope main programr.
It seems to be is harmless.
I suspect it is the initial executable trying to run something that isn't available on 64-bit windows before it launches java.
Thank you for your suggestion. But isn't it strange that a certified combination of software components doesn't work? I agree that it is a harmless phenomenon for the SQL Developer GUI, but it prevents the use of ututil. This is exactly the component I need to use.
I can of course reinstall everything using the 32 bit versions, but I very much would like to hear why this is not listed as a known issue in the 64 bit version of SQL Developer.
I'll admit I don't use ututil, but if I run it with no parameters, it continues after the exec error with a usage message.
Is it that error which is stopping you using it or something else? I've not seen any other reports of it not working on 64-bit windows
D:\progs\sqldeveloper64-3.2.20.09.87\sqldeveloper\bin>ututil _execv() failed, err=2 ututil -run ? ututil -exp ? ututil -imp ?
You are exactly right. I wrongfully assumed that the error meant that ututil didn't work. But is does despite the "_execv() failed, err=2" error.
Thank you for pointing this out to me.