Re: Windows freezing during SQL*PLUS execution.

In article <3v8mkt$ba6_at_helios.vanderbilt.edu>, Randy Fought <FOUGHTRL_at_CTRVAX.VANDERBILT.EDU> writes:

> When performing data manipulation operations from a client
>Windows i486 machine using SQL*PLUS the client machine gets
>locked up (no other work can be done on the client, can't even
>ALT-TAB to program manager).
> This occurs on long updates, alter tables (adding
>primary keys, enabling foreign keys, etc). All the work is being
>done on the server - no traffic at all over SQL*NET other than
>the SQL code.
> I know Windows (in this case Windows for Workgroups) is
>not a very good multi-tasking OS but this is ridiculous. Or, has
>Oracle written bad code that doesn't return control back to windows
>while the server machine does its task?
> Anybody have the same problem. Is there a system setting of
>some kind on the client to alleviate this problem?
>Thanks in advance - Randy Fought
>
>

That's just the way it is. A windows app has to have some sort of idle-loop (or
main-loop, whatever)[this is the non-windows take on the terminology]. It would
seem that SQL*Plus for win never falls back to it while actually doing something.
If you're running scripts you *can* load the script (_at_myscript) and alt-tab out of
there and it will indeed run in the background. Cheap, but effective.

Chris Kasten Received on Fri Jul 28 1995 - 00:00:00 CEST