Login or Register to Ask a Question and Join Our Community


Red Hat

Oracle ha from rgmanager to pacemaker

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat Oracle ha from rgmanager to pacemaker
# 1  
Old 06-12-2016
Oracle ha from rgmanager to pacemaker
Hi,

I've got one question about oracle rgmanager resource agent and ocf script.

Rgmanager oracledb.sh script has an options called "vhost" which set the "ORACLE_HOSTNAME" value when you have different different cards on the same machine and different oracle instances.

In ocf: heartbeat: oracle script there is no the possibility to set that value. The question is:

Can I use the same rgmanager script oracledb.sh (and dependencies) copying it to /usr/lib/ocf/resource.d/rgmanager/?

If yes, then I think that to insert the oracle resource I have to do:

#pcs resource create my_resource ocf:rgmanagerSmilieracledb.sh name=test_rgamanager user=oracleuser home=/oracle/app/oraclehome/ type=base vhost=10.139.5.144 op monitor interval=0s

Is it correct?

Thanks

Daniele
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. Red Hat

Linux PaceMaker Equivalent to a SharedAddress Resource Type

In HA platforms, there is the concept of a "Scalable Resource Type, which included the sharedaddress" that is used in commonly Web Servers resource groups. The sharedaddress resource type is provided so a developer can use this Resource type to build their own scalable resource group. I see... (1 Reply)
Discussion started by: mrmurdock
1 Replies

2. Shell Programming and Scripting

Bash script to add multiple resources to NFS pacemaker cluster

All, I'm looking for some guidance on how to accomplish automating the addition of exports to an HA Pacemaker NFS cluster. I would like to do it in bash for logistics reasons. The resource creation command looks like this: pcs resource create nfs-b2b-hg-media-10.1 exportfs... (6 Replies)
Discussion started by: hburnswell
6 Replies

3. Red Hat

[HA] Red Hat 7, pacemaker and start/stop scripts

Hi there, I am wondering if I could add start/stop ksh scripts provided by 3rd party to cluster... I read that script must be ocf/lsb compliant, however, in AIX I can just set up two separate scripts for starting and stopping application. Can similar be done under RH Linux cluster? Cheers, c (1 Reply)
Discussion started by: cyjan
1 Replies

4. Red Hat

RHEL 7 PaceMaker Fence Agent Options

my options are getting very limited very fast on what agent to use with my 2 Node RHEL 7 VM Cluster. fence_vmware_soap "plug id"? I have a ESX resource cluster of 7 blades being managed by a Vsphere 6.0 server. I found the blade that the Cluster VM(s) is housed on. WTF is the plug id... (3 Replies)
Discussion started by: mrmurdock
3 Replies

5. Red Hat

PaceMaker Cluster Fence Device

I have 2 VM's setup with a shared VMware disk running RHEL 7.1 (just updated to 7.2 with yum update), and would like to know what is the easiest Fence device to implement for testing purposes. Apparently, I need a fence device before my IP resources will come online. I have the cluster... (1 Reply)
Discussion started by: mrmurdock
1 Replies

6. UNIX and Linux Applications

Identify a specific environment Oracle variable to connect a remote Oracle database ?

Good evening I nned your help pls, In an unix server i want to connect to a remote oracle databse server by sqlplus. I tried to find out the user/passwd and service name by env variable and all Ive got is this: ORACLE_SID_REPCOL=SCL_REPCOL ORACLE_SID=xmeta ORACLE_SID_TOL=SCL_PROTOLCOL... (2 Replies)
Discussion started by: alexcol
2 Replies
Login or Register to Ask a Question

LEARN ABOUT CENTOS

ocf_heartbeat_lvm

OCF_HEARTBEAT_LVM(7)						OCF resource agents					      OCF_HEARTBEAT_LVM(7)

NAME

       ocf_heartbeat_LVM - Controls the availability of an LVM Volume Group

SYNOPSIS

       LVM [start | stop | status | monitor | meta-data | validate-all]

DESCRIPTION

       Resource script for LVM. It manages an Linux Volume Manager volume (LVM) as an HA resource.

SUPPORTED PARAMETERS

       volgrpname
	   The name of volume group.

	   (required, string, no default)

       exclusive
	   If set, the volume group will be activated exclusively. This option works one of two ways. If the volume group has the cluster
	   attribute set, then the volume group will be activated exclusively using clvmd across the cluster. If the cluster attribute is not set,
	   the volume group will be activated exclusively through the use of the volume_list filter in lvm.conf. In the filter scenario, the LVM
	   agent verifies that pacemaker's configuration will result in the volume group only being active on a single node in the cluster and
	   that the local node's volume_list filter will prevent the volume group from activating outside of the resource agent. On activation
	   this agent claims the volume group through the use of a unique tag, and then overrides the volume_list field in a way that allows the
	   volume group to be activated only by the agent. To use exclusive activation without clvmd, the volume_list in lvm.conf must be
	   initialized. If volume groups exist locally that are not controlled by the cluster, such as the root volume group, make sure those
	   volume groups are listed in the volume_list so they will be allowed to activate on bootup.

	   (optional, boolean, default false)

       tag
	   If "exclusive" is set on a non clustered volume group, this overrides the tag to be used.

	   (optional, string, default "pacemaker")

       partial_activation
	   If set, the volume group will be activated even only partial of the physical volumes available. It helps to set to true, when you are
	   using mirroring logical volumes.

	   (optional, string, default "false")

SUPPORTED ACTIONS

       This resource agent supports the following actions (operations):

       start
	   Starts the resource. Suggested minimum timeout: 30.

       stop
	   Stops the resource. Suggested minimum timeout: 30.

       status
	   Performs a status check. Suggested minimum timeout: 30.

       monitor
	   Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 10.

       methods
	   Suggested minimum timeout: 5.

       meta-data
	   Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.

       validate-all
	   Performs a validation of the resource configuration. Suggested minimum timeout: 5.

EXAMPLE

       The following is an example configuration for a LVM resource using the crm(8) shell:

	   primitive p_LVM ocf:heartbeat:LVM 
	     params 
	       volgrpname=string 
	     op monitor depth="0" timeout="30" interval="10"

SEE ALSO

       http://www.linux-ha.org/wiki/LVM_(resource_agent)

AUTHOR

       Linux-HA contributors (see the resource agent source for information about individual authors)

resource-agents UNKNOWN 					    06/09/2014						      OCF_HEARTBEAT_LVM(7)