yugandhar
2008-Dec-03 16:53 UTC
[Wine] Re: Unhandled Page Fault ....Help Me...{unixODBC is Crashing in
Hi,> > 2 0x60b51b11 function_return_ex+0x281(level=3, handle=<register ESI not in topmost frame>, ret_code=-1, save_to_diag=0) [/root/unixODBC-2.2.12/DriverManager/__info.c:4791] in libodbc.so.1 (0x7ed37dbc) > > Are you running as root? If so, this may be the cause of your problem. > If you are running as Oracle, why did you install the ODBC as root?As the part of oracle database installation,Unixodbc is installed as root. An user is created as installation process and from that user only am running my application.This worked some times.This crash occurs When tried to run the same application couple of times.> Please install the Windows Oracle Client and see if you can tnsping your Oracle server.I could able to tnsping Oracle Server running in linux from Windows Oracle client. -Yug
James McKenzie
2008-Dec-06 02:38 UTC
[Wine] Unhandled Page Fault ....Help Me...{unixODBC is Crashing in
yugandhar wrote:> Hi, > > > >> 2 0x60b51b11 function_return_ex+0x281(level=3, handle=<register ESI not in topmost frame>, ret_code=-1, save_to_diag=0) [/root/unixODBC-2.2.12/DriverManager/__info.c:4791] in libodbc.so.1 (0x7ed37dbc) >> >> Are you running as root? If so, this may be the cause of your problem. >> If you are running as Oracle, why did you install the ODBC as root? >> > > > As the part of oracle database installation,Unixodbc is installed as root. > An user is created as installation process and from that user only am running my application.This worked some times.This crash occurs When tried to run the same application couple of times. > > > >> Please install the Windows Oracle Client and see if you can tnsping your Oracle server. >> > > I could able to tnsping Oracle Server running in linux from Windows Oracle client. > > >Then use the Windows Oracle Client! unixODBC should not be available to your Wine session. I read this today in this mailing list, but the message series may be from June through today. In other words, someone else had this problem and the only method to fix it was to use the client, not the unixODBC system. James McKenzie