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 !
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
Oracle/Xen/OVM/OCFS2/Multipath/SAN Problems
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
Emergency UNIX and Linux Support
Ns_Master(3aolserver)					   AOLserver Library Procedures 				     Ns_Master(3aolserver)


Ns_MasterLock, Ns_MasterUnlock - Enter and leave the single master critical section lock
#include "ns.h" void Ns_MasterLock(void) void Ns_MasterUnlock(void) _________________________________________________________________
The single master critical section lock is used throughout the core server to protect portions of code from being run by more than one thread at a time. These are convenience functions which actually make calls to Ns_CsEnter and Ns_CsLeave to perform the locking and unlock- ing function. You should not use these functions in your modules. To protect critical sections in your modules you should create and initialize your own named locks, then wrap your critical sections with calls to Ns_CsEnter and Ns_CsLeave. Ns_MasterLock() Enter the single master lock. The thread that holds this lock is guaranteed exclusive access to the section of code that follows the call to Ns_MasterLock. Other threads that attempt to enter the master critical section while another thread owns the master lock will block until the owning thread releases the master lock. Be extremely careful with code you place within the master critical section. If the thread that owns the master lock blocks for any reason while in the master critical section, other threads that need to enter that section of code will block until the master lock is released. Ns_MasterUnlock() Leave the single master critical section. The thread that owns the lock must release it after the critical section of code has com- pleted so that other threads may execute the critical section code.
nsd(1), info(n), Ns_CsEnter(3), Ns_CsLeave(3)
AOLserver 4.0 Ns_Master(3aolserver)

Featured Tech Videos