Create "A CRS Managed" ACFS Filesystem On a Cluster RAC Configuration Through the Command-Line


Environmental details:

Hosts: dbsrv01, dbsrv02 

Clusterware and database version :12.1.0.2 

Applied Patches: 30070257 


1. Create the ACFS volume from the existing DATA disk group as "grid" user:

 [root@dbsrv01 ~]# su - grid

Last login: Fri Aug 16 14:00:21 IST 2024 from gateway on pts/0

[grid@dbsrv01 ~]$ echo $ORACLE_SID

+ASM1

[grid@dbsrv01 ~]$ asmcmd volcreate -G DATA -s 8G OGGVOL


2. Verify the volume was created and obtain the new volume device name:

[grid@dbsrv01 ~]$ asmcmd volinfo --all

Diskgroup Name: DATA

         Volume Name: OGGVOL

         Volume Device: /dev/asm/oggvol-329

         State: ENABLED

         Size (MB): 8192

         Resize Unit (MB): 512

         Redundancy: UNPROT

         Stripe Columns: 8

         Stripe Width (K): 1024

         Usage:

         Mountpath:


[grid@dbsrv01 ~]$ /u01/app/12.1.0/grid/bin/crsctl stat res -w "TYPE = ora.volume.type"

NAME=ora.DATA.OGGVOL.advm

TYPE=ora.volume.type

TARGET=ONLINE           , ONLINE

STATE=ONLINE on dbsrv01, ONLINE on dbsrv02

 

3. From the first node, create the ACFS filesystem on the new volume device ("/dev/asm/oggvol-329") as "root" user:

[root@dbsrv01 ~]# /sbin/mkfs -t acfs /dev/asm/oggvol-329

mkfs.acfs: version                   = 12.1.0.2.0

mkfs.acfs: on-disk version           = 39.0

mkfs.acfs: volume                    = /dev/asm/oggvol-329

mkfs.acfs: volume size               = 8589934592  (   8.00 GB )

mkfs.acfs: Format complete.


4. Register the ACFS filesystem and new volume with the CRS as "root" user. 

[root@dbsrv01 ~]# /u01/app/12.1.0/grid/bin/srvctl add filesystem -d /dev/asm/oggvol-329 -g 'DATA' -v OGGVOL -m /ogg -u oracle

 

[root@dbsrv01 ~]# /u01/app/12.1.0/grid/bin/crsctl stat res -w "TYPE = ora.acfs.type"

NAME=ora.data.oggvol.acfs

TYPE=ora.acfs.type

TARGET=OFFLINE, OFFLINE

STATE=OFFLINE, OFFLINE

 

5. Start the new ACFS CRS resource as "root" user :

[root@dbsrv01 ~]# /u01/app/12.1.0/grid/bin/srvctl start filesystem -d /dev/asm/oggvol-329 

[root@dbsrv01 ~]# /u01/app/12.1.0/grid/bin/crsctl stat res -w "TYPE = ora.acfs.type"

NAME=ora.data.oggvol.acfs

TYPE=ora.acfs.type

TARGET=ONLINE           , ONLINE

STATE=ONLINE on dbsrv01, ONLINE on dbsrv02

 

[root@dbsrv01 ~]# df -h /ogg

Filesystem           Size  Used Avail Use% Mounted on

/dev/asm/oggvol-329  8.0G   93M  8.0G   2% /ogg

 

[root@dbsrv02 ~]# df -h /ogg

Filesystem           Size  Used Avail Use% Mounted on

/dev/asm/oggvol-329  8.0G   93M  8.0G   2% /ogg

 

6. Set the desired new ownership and permissions as "root" user.

[root@dbsrv01 ~]# chown oracle:oinstall /ogg

[root@dbsrv01 ~]# chmod 775 /ogg


Comments

Post a Comment

Popular posts from this blog

How to Reposition Extract, Data Pump and Replicat in GoldenGate During Trail File Corruption

In this blog, we will walk you through the steps to reposition the Extract, Data Pump and Replicat processes in the event of Extract trail file corruption.   The environment consists of: Host: dbsrv01.localdomain: Source Database (19c) named "master" running on OEL 8.8, Extracting HR.REGIONS table using GoldenGate 21.3. Host: dbsrv02.localdomain: Target Database (19c) named "orcl" running on OEL 8.8, Replicating HR.REGIONS table using GoldenGate 21.3. Source (master) Target (orcl) 1. We have an integrated Extract running on the source database.   [oracle@dbsrv01 ~]$ ggsci   Oracle GoldenGate Command Interpreter for Oracle Version 21.3.0.0.0 OGGCORE_21.3.0.0.0_PLATFORMS_210728.1047_FBO Oracle Linux 7, x64, 64bit (optimized), Oracle Database 21c and lower supported versions on Jul 29 2021 03:59:23 Operating system character set identified as UTF-8.   Copyright (C) 1995, 2021, Oracle and/or its...
Read more

OEM 13cR5 Host IP Change and Repository Database 19c Migration to Another Datacenter via Data Guard Failover

Image
This blog outlines the high-level steps taken to execute two major Oracle Enterprise Manager (OEM) infrastructure changes with minimal downtime to monitoring continuity. Change the IP address of the OEM 13cR5 host server. Migrate the OEM repository database (Oracle 19c) to secondary datacenter using Data Guard failover. Environment details: Component CMO (Current Mode of Operation) FMO (Future Mode of Operation / Post-Migration) OS Oracle Linux 8 (All Nodes) Oracle Linux 8 (All Nodes) OEM Installation Host/IP dbsrv09.localdomain / 192.168.56.110 dbsrv09.localdomain / 192.168.56.109 OEM Version 13c Release 5 (13.5.0.0.0) 13c Release 5 (13.5.0.0.0) Repository DB Node (Primary) dbsrv05.localdomain dbsrv06.localdomain (Post Data Guard Failover) Repository DB Node (Standby) dbsrv06.localdomain ...
Read more

How to Enable Monitoring for GoldenGate 23ai Microservices with Oracle Enterprise Manager 13cR5

Image
Please refer to the steps outlined in the blog: Step-by-Step Guide to Configure Oracle GoldenGate for deploying the GoldenGate plugin 13.5.2.0.0 in OMS and EM Agent(s). In this blog, we will guide you through the steps to enable monitoring for GoldenGate 23ai Microservices using Oracle Enterprise Manager 13cR5. The Environment Consists of: Host: dbsrv01.localdomain OMS Server 13cR5 Source Database (19c) named "master" Operating System: OEL 8.8 Host: dbsrv02.localdomain GoldenGate 23c AI Microservices configured as a simple " HUB ARCHITECTURE " between source and target databases Running EM Agent 13c Host: dbsrv03.localdomain Target Database (19c) named "masters" Operating System: OEL 8.8 1.Log in to the OEM 13cR5 console and discover the Oracle Goldengate Microservices targets.  Go to Setup   -> Add Target   -> Configure Auto Discovery   In...
Read more