McAllister, Andrew wrote: > Could be hardware, but if it is running fine otherwise, I wouldn't say > it is likely. Your memtest this weekend should help test the hardware. > > Have you run a "relink all" after the install? Any kernel changes > recently? Yast updates? Any time you update the kernel or glibc you > should "relink all" the oracle executables. Perhaps you might downgrade > your Suse kernel if you are running the latest. Are you using async IO? > Is it linked in to the Oracle executables? > > The fact that you get a complete system hang with no error logs anywhere > says to me it is a kernel/oracle compatibility problem. We've had kernel > compatibility issues with SLES8 to the point where nothing would > surprise me.
Haven't done a relink - at least not recently (say in the last 6 weeks). I did a kernel update 14 days ago... rebooted then, and had no issues with restarting Oracle. YaST is up-to-date except for the latest kernel update that has popped up recently (last day or so). I didn't want to apply that yet because every time I update the kernel it messes up my VMWare install. So... the last kernel update to 2.6.11.4-21.8-default was working fine with Oracle.
I did do some software updating this morning... but nothing on Oracle, or system level... I added in the latest builds of cairo and gtk2... both of which I wouldn't expect to have any effect on Oracle. Oracle (at the command line especially) doesn't use/rely on gtk or any Window manager tools/apps.
Don't know if I'm using async IO or not (I'm still learning the whole Oracle thing). It's a default install of Oracle... no tweaking etc. to get it working. No special setup tweaking.
I will try the relink all thing on Monday (after the memtest this weekend).
-- To unsubscribe, email: suse-oracle-unsubscribe@(protected) For additional commands, email: suse-oracle-help@(protected) Please see http://www.suse.com/oracle/ before posting
