https://mdinh.wordpress.

com/2014/12/14/goldendate-ha-maa-rac-acfs-xag/

Configure ACFS for OGG MA

--------------------------

1) Verify that the ACFS/ADVM modules are present in memory (on each node):

# lsmod | grep oracle

oracleacfs 5438460 0
oracleadvm 1104207 0
oracleoks 732987 2 oracleacfs, oracleadvm

The above output shows that modules are present. If your output is not the same,
then reinstall them as root user:
# cd /u01/app/19.3.0/grid/bin
# ./acfsroot install
# ./acfsload start

2) Create a separate DISKGROUP called GGDG for the GoldenGate software (from the
1st nodes of each cluster).
To create a new DISKGROUP, use the following sample script:
SQL> CREATE DISKGROUP "GGDG" NORMAL REDUNDANCY
FAILGROUP "PRIMRAC1" DISK '/dev/primrac1.lun4' NAME "PRIMRAC1$LUN4" SIZE
20480M
FAILGROUP "PRIMRAC2" DISK '/dev/primrac2.lun4' NAME "PRIMRAC2$LUN4" SIZE
20480M
QUORUM FAILGROUP "PRIMRACQ" DISK '/dev/primracq.lun2' NAME "PRIMRACQ$LUN2"
ATTRIBUTE 'au_size' = '4M' ,'compatible.asm' =
'19.0.0.0' ,'compatible.rdbms' = '19.0.0.0';

SQL> ALTER DISKGROUP GGDG SET ATTRIBUTE 'failgroup_repair_time' = '2400h'

3) Make sure that DISKGROUP is mounted on all nodes.

4) From the first nodes of each cluster, create ACFS volumes:

$ sudo su - grid
$ asmcmd volcreate -G GGDG -s 19G ACFSGG

5) Identify the device name of the volume (from the 1st nodes of each cluster):
[grid@primrac1 ~]$ asmcmd volinfo -G GGDG -a

[grid@stbyrac1 ~]$ asmcmd volinfo -G GGDG -a

6) Create an ACFS filesystem on the volume:

[grid@primrac1 ~]$ mkfs -t acfs /dev/asm/acfsgg-91
[grid@stbyrac1 ~]$ mkfs -t acfs /dev/asm/acfsgg-211

7) As a root user, create a directory named GG_HOME on all nodes of each cluster:
# mkdir /GG_HOME # chmod 775 /GG_HOME # chown oracle:oinstall /GG_HOME

8) As a root user register the file system with Clusterware (from the 1st nodes of
each cluster):
[root@primrac1 ~]# srvctl add filesystem -device /dev/asm/acfsgg-91 -path /GG_HOME
-volume acfsgg -diskgroup GGDG -user oracle -fstype ACFS -description “Primary ACFS
for Golden Gate” [root@stbyrac1 ~]# srvctl add filesystem -device /dev/asm/acfsgg-
211 -path /GG_HOME -volume acfsgg -diskgroup GGDG -user oracle -fstype ACFS -
description “Standby ACFS for Golden Gate”

9) Start the filesystem service:

[root@primrac1 ~]# srvctl start filesystem -device /dev/asm/acfsgg-91
[root@stbyrac1 ~]# srvctl start filesystem -device /dev/asm/acfsgg-211

10) Check the filesystem service status:

[root@primrac1 ~]# srvctl status filesystem -device /dev/asm/acfsgg-91

[root@stbyrac1 ~]# srvctl status filesystem -device /dev/asm/acfsgg-211

Configure and setup OGG MA

--------------------------

Install the Oracle GoldenGate Software

Download the Oracle GoldenGate 19c Microservices software from Oracle Technology
Network (OTN) at:
http://www.oracle.com/technetwork/middleware/goldengate/downloads/index.html

1) Install Oracle Grid Infrastructure Standalone Agents Oracle Grid Infrastructure

Standalone Agent (XAG) automates start/stop of the GG deployment when relocating
between nodes. During relocation, automatic mounting of ACFS and DBFS shared
filesystems is managed by XAG.

Install Oracle Grid Infrastructure Standalone Agents using the following procedure:
Download the software from https://www.oracle.com/technetwork/database/database-
technologies/clusterware/downloads/xag-agents-downloads-3636484.html.

2) Place the downloaded software in /tmp/Install. From the 1st node of each
cluster, run the following via grid user:
# chown -R grid:dba /tmp/Install
# su - grid
$ cd /tmp/Install
$ unzip xagpack91.zip
From primrac1:
[grid@primrac1 Install]$ ./xag/xagsetup.sh --install --directory
/u01/app/grid/xag --all_nodes

Installing Oracle Grid Infrastructure Agents on: primrac1

Installing Oracle Grid Infrastructure Agents on: primrac2 Done.
Updating XAG resources. Successfully updated XAG resources.

From stbyrac1:

[grid@stbyrac1 Install]$ ./xag/xagsetup.sh --install --directory /u01/app/grid/xag

--all_nodes
Installing Oracle Grid Infrastructure Agents on: stbyrac1
Installing Oracle Grid Infrastructure Agents on: stbyrac2 Done.
Updating XAG resources. Successfully updated XAG resources.
Create application VIP
---------------------

A dedicated application VIP is required on a GoldenGate target host only. If you

are setting up bidirectional replication, then you will need to set up VIP on both
clusters. The VIP is a cluster resource that Oracle Clusterware manages. It is
assigned to a cluster node and if the server hosting the VIP goes down, then Oracle
Clusterware will migrate the VIP to a surviving server. The VIP must be an
available IP address on the public subnet and cannot be determined through DHCP.

1) As a root user, create application VIP on the first node of the target cluster:

./crsctl status resource -p | grep -ie .network -ie subnet | grep -ie name -ie
subnet

NAME=ora.net1.network
USR_ORA_SUBNET=23.2.1.0

Here ora.net1 in NAME indicates the network number as 1, and USR_ORA_SUBNET is the
subnet under
which the VIP will be created. Next, create the application VIP for GoldenGate,
where ggs-vip is the name of
the application VIP that you will create.

[root@stbyrac1 ~]# /u01/app/19.3.0/grid/bin/appvipcfg -help

[root@stbyrac1 ~]# /u01/app/19.3.0/grid/bin/appvipcfg create -network=1 -
ip=192.168.1.150 -vipname=gg_vip -user=root

2) Use the configuration parameter file:

/u01/app/19.3.0/grid/crs/install/crsconfig_params

3) The log of current session can be found at:

/u01/app/grid/crsdata/stbyrac1/scripts/appvipcfg.log

4) Start VIP:
# crsctl start resource gg_vip

5) Allow Oracle user to start the vip:

You can modify attributes for the resource ggs-vip as shown here:
$ crsctl modify resource ggs-vip -attr "RESTART_ATTEMPTS=3, START_TIMEOUT=300,
STOP_TIMEOUT=300, CHECK_INTERVAL=10"

# crsctl setperm resource gg_vip -u user:oracle:r-x

6) Check the status of the vip:

[root@stbyrac1 ~]# crsctl status resource gg_vip

7) Now you should be able to ping the VIP from the other nodes. Ping the VIP from
rac2-ravinpc
ping -c4 23.2.1.4
Creating the GoldenGate Clusterware Agent
-----------------------------------------

Register Oracle GoldenGate with XAG. The registration with XAG must be run as the
root user.

From primrac1: [root@primrac1 Install]# /u01/app/grid/xag/bin/agctl add goldengate

gg_replicate \
--gg_home /GG_HOME/ma \
--service_manager \
--config_home /GG_HOME/deploy/etc/conf \
--var_home /GG_HOME/deploy/var \
--port 9001 \
--adminuser oggadmin \
--user oracle \
--group oinstall \
--filesystems ora.ggdg.acfsgg.acfs \
--db_services ora.orclcdb.orclcdbserv.svc \
--use_local_services
Enter password for ‘oggadmin’ :

From stbyrac1: For the target server indicates VIP that was created in the previous
section as a value for the --vip_name option:

[root@stbyrac1 Install]# /u01/app/grid/xag/bin/agctl add goldengate gg_replicate \

--gg_home /GG_HOME/ma \
--service_manager \
--config_home /GG_HOME/deploy/etc/conf \
--var_home /GG_HOME/deploy/var \
--port 9001 \
--adminuser oggadmin \
--user oracle \
--group oinstall \
--vip_name gg_vip \
--filesystems ora.ggdg.acfsgg.acfs \
--db_services ora.orclcdb.orclcdbserv.svc \
--use_local_services
Enter password for ‘oggadmin’ :

Check newly added resource status:

# /u01/app/grid/xag/bin/agctl status goldengate gg_replicate

# /u01/app/grid/xag/bin/agctl start goldengate gg_replicate

# /u01/app/grid/xag/bin/agctl status goldengate gg_replicate

-------------------------------------------
one more example:

[root@rac01 rac01]# /u01/app/grid/xag/bin/agctl add goldengate ogg_ms_ha –

gg_home /u01/app/oracle/goldengate –service_manager –config_home /ogg/sm/etc/conf –
var_home /ogg/sm/var –vip_name ogg_vip –port 9100 –adminuser oggadmin –user oracle
–group oinstall –filesystems ora.acfs.oggvol.acfs –db_services ora.cdb.ogg_cdb.svc
–use_local_services

Enter password for ‘oggadmin’ :

[root@rac01 rac01]# /u01/app/grid/xag/bin/agctl start goldengate ogg_ms_ha

[root@rac01 rac01]# /u01/app/grid/xag/bin/agctl status goldengate ogg_ms_ha

Goldengate instance ‘ogg_ms_ha’ is running on rac01

[root@rac01 rac01]# /u01/app/grid/xag/bin/agctl config goldengate ogg_ms_ha

Instance name: ogg_ms_ha

Application GoldenGate location is: /u01/app/oracle/goldengate

Goldengate MicroServices Architecture environment: yes

Goldengate Service Manager configuration directory: /ogg/sm/etc/conf

Goldengate Service Manager var directory: /ogg/sm/var

Service Manager Port: 9100

Goldengate Administration User: oggadmin

Database Services needed: ora.cdb.ogg_cdb.svc

File System resources needed: ora.acfs.oggvol.acfs

VIP name: ogg_vip

-----------------------------------------------------------------------------------
------------
hard

For example,
if resource A has a hard start dependency on resource B,
then resource B must be running before resource A can start.

weak

If resource A has a weak start dependency on resource B,

then an attempt to start resource A attempts to start resource B, if resource B is
not running.
The result of the attempt to start resource B is, however, of no consequence to the
result of starting resource A.

attraction

If resource A has an attraction dependency on resource B, then Oracle Clusterware

prefers to place resource A on servers hosting resource B.
Dependent resources, such as resource A in this case, are more likely to run on
servers on which resources to which they have attraction dependencies are running.
Oracle Clusterware places dependent resources on servers with resources to which
they are attracted.
pullup

Use the pullup start dependency if resource A must automatically start whenever
resource B starts.
This dependency only affects resource A if it is not running.
As is the case for other dependencies, pullup may cause the dependent resource to
start on any server. Use the pullup dependency whenever there is a hard stop
dependency, so that if resource A depends on resource B and resource B fails and
then recovers, then resource A is restarted.