Suggestion on running critical Oracle DBs on OVM


Login or Register to Reply

 
Thread Tools Search this Thread
Login or Register to Reply

|
Thread Tools Search this Thread
Search this Thread:
Advanced Search

More UNIX and Linux Forum Topics You Might Find Helpful
OVM Server for SPARC ... Need Your Help Guys !
Mack1982
I have two SPARC T4-2 servers: - Oracle Solaris 11.1 Installed. - Oracle VM Server for SPARC 3.0 software Installed. - Shared LUN provisioned to both servers from Clariion CX4 storage box (shared LUN to be used for the Live Migration of the VMs). - Oracle VM Agent 3.2.1 for SPARC installed. ...... Solaris
14
Solaris
Oracle/Xen/OVM/OCFS2/Multipath/SAN Problems
pludi
Setup: Multiple Virtual Machines running OEL5 / Oracle RDBMS 11.2 OVM 2 / Xen 3.4.0 Cluster consisting of 3 Machines Shared SAN Storage synced with OCFS2 SAN connected with 4GB FC on 4 Paths per LUN SAN target are 2 EMC Clariion mirroring each other The problems we're facing are that...... Emergency UNIX and Linux Support
6
Emergency UNIX and Linux Support
CRITICAL_ENTER(9)					   BSD Kernel Developer's Manual					 CRITICAL_ENTER(9)

NAME
critical_enter, critical_exit -- enter and exit a critical region
SYNOPSIS
#include <sys/param.h> #include <sys/systm.h> void critical_enter(void); void critical_exit(void);
DESCRIPTION
These functions are used to prevent preemption in a critical region of code. All that is guaranteed is that the thread currently executing on a CPU will not be preempted. Specifically, a thread in a critical region will not migrate to another CPU while it is in a critical region. The current CPU may still trigger faults and exceptions during a critical section; however, these faults are usually fatal. The critical_enter() and critical_exit() functions manage a per-thread counter to handle nested critical sections. If a thread is made runnable that would normally preempt the current thread while the current thread is in a critical section, then the preemption will be deferred until the current thread exits the outermost critical section. Note that these functions are not required to provide any inter-CPU synchronization, data protection, or memory ordering guarantees and thus should not be used to protect shared data structures. These functions should be used with care as an infinite loop within a critical region will deadlock the CPU. Also, they should not be inter- locked with operations on mutexes, sx locks, semaphores, or other synchronization primitives. One exception to this is that spin mutexes include a critical section, so in certain cases critical sections may be interlocked with spin mutexes.
HISTORY
These functions were introduced in FreeBSD 5.0.
BSD
October 5, 2005 BSD

Featured Tech Videos