Database Software

Having a very wierd problem on a 2-node cluster. I can only bring up on ASM instance at a time. If i bring up the second, it hangs. This is what the second (hung) instance puts in the alert log:

Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as /ORAUTL/oraasm/product/ASM/dbs/arch
Autotune of undo retention is turned off.
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.3.0.
System parameters with non-default values:
large_pool_size = 12582912
instance_type = asm
cluster_interconnects = 192.168.0.12
cluster_database = TRUE
instance_number = 2
remote_login_passwordfile= EXCLUSIVE
background_dump_dest = /ORAUTL/oraasm/admin/+ASM2/bdump
user_dump_dest = /ORAUTL/oraasm/admin/+ASM2/udump
core_dump_dest = /ORAUTL/oraasm/admin/+ASM2/cdump
pga_aggregate_target = 0
Cluster communication is configured to use the following interface(s) for this instance
192.168.0.12
Fri Nov 21 21:10:48 2008
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
PMON started with pid=2, OS id=5428
DIAG started with pid=3, OS id=5430
PSP0 started with pid=4, OS id=5432
LMON started with pid=5, OS id=5434
LMD0 started with pid=6, OS id=5436
LMS0 started with pid=7, OS id=5438
MMAN started with pid=8, OS id=5442
DBW0 started with pid=9, OS id=5444
LGWR started with pid=10, OS id=5446
CKPT started with pid=11, OS id=5448
SMON started with pid=12, OS id=5458
RBAL started with pid=13, OS id=5475
GMON started with pid=14, OS id=5487
Fri Nov 21 21:10:49 2008
lmon registered with NM - instance id 2 (internal mem no 1)
Fri Nov 21 21:10:49 2008
Reconfiguration started (old inc 0, new inc 2)
ASM instance
List of nodes:
0 1
Global Resource Directory frozen
Communication channels reestablished

After this it hangs. i've checked everything. CRS is fine.

I suspect its the kernel revision. This is a cluster of two v890's. Kernel rev is 127127-11. Anyone seen this issue ?

thanks