I'm using Oracle 8.1.7 on Solaris 8. I've had this occur on an exported 8.1.7/RH7.3 database, too, which, BTW, just crashed hard.
I noticed our app having intermittent problems, so I tried some tests via sqlplus. I could do selects, but if I tried deleting a few rows (no integrity issues in deleting), sqlplus just hangs indefinitely and never deletes. So I try using svrmgrl to shutdown and once again, it just hangs. So I reboot the server and things are fine (except for the new, dead machine).
I checked the alert log, and found nothing within the last 18 months -- not even the last reboot, which seems weird. A friend suggested a pessimistic lock problem, so I also checked the v$lock table, but don't really know how to interpret it.
I remember that 184.108.40.206 had similar problems (even strange memory errors about the shared pool) that went away as soon as i switched to 220.127.116.11, which is as stable as a rock.
On both Solaris and Linux.
Yes, the alert log was elsewhere, but still no help -- nothing unusual looking. I'm afraid to try your wait message, as this issue seems to lead to critical failures and we have only one production machine now. I'll try it off hours, though.
We're running 18.104.22.168. We have a license (bought from another company w/ all their assets) but there is no documentation to prove we own it, so metalink is off-limits. We're planning on buying new licenses, but the purse-strings are awfully tight these days.
Is there a work-around? Not having access to metalink has been a nightmare, but there's nothing I can do about it