Oracle Golden Gate 21c Microservices Installation

Oracle Golden Gate Microservices Architecture

Oracle Golden Gate Microservices Architecture has been introduced in Oracle Golden Gate version 12.3. A kind of architecture mainly designed on the perspective of Cloud operations. So, the older one is now called as Classic Architecture.

As we all aware that, Oracle Golden Gate Classic Extract for Oracle Database is already de-supported from OGG version 18c and now from OGG 21c, Oracle Golden Gate Classic Architecture itself got deprecated and may be de-supported and unavailable in future releases.

So, Oracle recommends the customers to move to Microservices architecture.

Downloaded the binary and unzipped in the below location.

Before installing OGG 21c MA, you need to create three directories which are below,

Why you need the above three directories ? What is the need of it ?

/u01/ogg/ogg21c_ma       >   OGG_HOME
/u01/ogg/ogg21c_sm       >   Service Manager Home
/u01/ogg/ogg21c_deploy   >   Deployment Home

Installer

Choose software location. This is OGG HOME /u01/ogg/ogg21c_ma

Installed binaries understanding

Deploying OGG Microservices

Run the oggca.sh which takes us to the Deployment screen.

[oracle@ebsazt bin]$ ./oggca.sh

Configure Service Manager. The location of Service Manager is /u01/ogg/ogg21c_sm

If you want to register as a service check the box Register Service Manager as a system service/daemon

Name deployment name like deployment01

Note down the underline directories as well.

Provide Schema name to add it in the GLOBALS file.

c##ggadmin

As we have registered the Service Manager as daemon, it will be started automatically. Check if it is running,

Login to the Service Manager GUI. Provide the username and password.

Once you login to the Service Manager, you can see the other services running. Here Service Manager is just a watch dog

Administration Service is where we can create Extract and Replicate processes. 

Login to the Administration server. Port 7002

(Default is 7001 but in my case I change default due to already user)

 

Distribution Service is where we configure the data push. Where the data needs to be replicated? To which Target.

Oracle Database Appliance – Extend /u01

Verify the actual Situation and the Disk Configuration

As ODA default /u01 space is around 100GB that is not enough as we have all oracle database related binaries on that location including ORACLE_BASE and ORACLE_HOME

Note: ODA-2HA two node, so you have to perform same on both nodes as below

Currently, extending /u01 only node1

1.                 Let’s check the current size of /u01

[root@ODA-2HA-X8~]# df -h /u01

Filesystem                         Size  Used Avail Use% Mounted on

/dev/mapper/VolGroupSys-LogVolU01   99G   43G   51G  46% /u01

 

2.        Let’s verify the physical volume for free space, we can see 7428 free physical extents are available

 

[root@ODA-2HA-X8 ~]# pvdisplay

  --- Physical volume ---

  PV Name               /dev/md126p3

  VG Name               VolGroupSys

  PV Size               <446.15 GiB / not usable 23.00 MiB

  Allocatable           yes

  PE Size               32.00 MiB

  Total PE              14276

  Free PE               7428

  Allocated PE          6848

  PV UUID               fYtdV3-N71S-HKXf-Kov2-tIk8-X0pF-TfRLzn

 

3.                 This is the actual size of the logical volume; the actual logical volume size is 100 GB.

 

[root@ODA-2HA-X8 ~]# lvdisplay /dev/mapper/VolGroupSys-LogVolU01

  --- Logical volume ---

  LV Path                /dev/VolGroupSys/LogVolU01

  LV Name                LogVolU01

  VG Name                VolGroupSys

  LV UUID                VnV8hE-I0yy-yJz4-BOgR-jo3u-nsno-yNdHh1

  LV Write Access        read/write

  LV Creation host, time localhost.localdomain, 2022-06-29 21:17:50 +0300

  LV Status              available

  # open                 1

  LV Size                100.00 GiB

  Current LE             3200

  Segments               1

  Allocation             inherit

  Read ahead sectors     auto

  - currently set to     8192

  Block device           252:39

Extend /u01

4.                Now we extend online the LVM with the lvextend command from 100 GB to 200 GB.

 

[root@ODA-2Ha-X8 ~]# lvextend --size +100G /dev/VolGroupSys/LogVolU01

 

  Size of logical volume VolGroupSys/LogVolU01 changed from 100.00 GiB (3200 extents) to 200.00 GiB (6400 extents).

  Logical volume VolGroupSys/LogVolU01 successfully resized.

 

 

[root@ODA-2HA-X8 ~]# lvdisplay /dev/mapper/VolGroupSys-LogVolU01

  --- Logical volume ---

  LV Path                /dev/VolGroupSys/LogVolU01

  LV Name                LogVolU01

  VG Name                VolGroupSys

  LV UUID                VnV8hE-I0yy-yJz4-BOgR-jo3u-nsno-yNdHh1

  LV Write Access        read/write

  LV Creation host, time localhost.localdomain, 2022-06-29 21:17:50 +0300

  LV Status              available

  # open                 1

  LV Size                200.00 GiB

  Current LE             6400

  Segments               2

  Allocation             inherit

  Read ahead sectors     auto

  - currently set to     8192

  Block device           252:39

 

5.                 Finally, the filesystem has to be resized.

[root@ODA-2HA-X8 ~]# resize2fs /dev/VolGroupSys/LogVolU01

 

resize2fs 1.42.9 (28-Dec-2013)

Filesystem at /dev/VolGroupSys/LogVolU01 is mounted on /u01; on-line resizing required

old_desc_blocks = 7, new_desc_blocks = 13

The filesystem on /dev/VolGroupSys/LogVolU01 is now 52428800 blocks long.

 

6.      Now we have 200GB space of /u01

 

 

[root@ODA-2HA-X8 ~]# df -h /u01

Filesystem                         Size  Used Avail Use% Mounted on

/dev/mapper/VolGroupSys-LogVolU01  197G   43G  146G  23% /u01

 

Summary

Resizing the /u01 on an Oracle Database Appliance is very easy and straightforward. There are no special actions required, it’s just a logical volume, no downtime required. And there is more space left on the physical volume for other resize actions.

Remove an Oracle ACFS File System and a Volume

 

Removing an Oracle ACFS File System and a Volume

To permanently remove a volume and Oracle ACFS file system, perform the following steps. These steps destroy the data in the file system.

1. Deregister the file system with acfsutil registry -d.

   For example:

   $ /sbin/acfsutil registry -d /acfsmounts/acfs1
   acfsutil registry: successfully removed ACFS mount point
      /acfsmounts/acfs1 from Oracle Registry
   

   Dismount the file system.

2. For example:

   # /bin/umount /acfsmounts/acfs1
   

   You must dismount the file system on all nodes of a cluster.

   Remove the file system with acfsutil rmfs.

3. If you were not planning to remove the volume in a later step, this step is necessary to remove the file system. Otherwise, the file system is removed when the volume is deleted.

   For example:

   $ /sbin/acfsutil rmfs /dev/asm/volume1-123

4. Optionally you can disable the volume with the ASMCMD voldisable command.

   For example:

   ASMCMD> voldisable -G data volume1
   

   Delete the volume with the ASMCMD voldelete command.

5. For example:

   ASMCMD> voldelete -G data volume1
   

   
   

Reference:

Oracle Book: Automatic Storage Management Administrator's Guide (E41058-12)

RE-IMAGING AN ORACLE DATABASE APPLIANCE (ODA)

ODA-X7-2-HA

Introduction:

This will provide an overview of tasks to re-image an ODA(ODA-X7-2-HA).

The decision to re-image an ODA should not be taken lightly as the process clean the operating system disks and destroys all data – including databases.  There are a few reasons why one may have a need to re-image an ODA (e.g. testing, version upgrades that span many releases, corruption etc.) but in this case, we need to move from OS and Database as describe below:

Oracle Enterprice Linux 6.8 to Oracle Enterprice 7.8 64-bit

Oracle Grid and Database 18.2. to 19.9.x

For this post, we will follow and mentioned steps of deploying a “Bare Metal” ODA (non-virtualized) on  ODA-X7-2H.

Prerequisites: 

For this install, we will deploy using ODA Software version 19.9 with Database 19cR2.

1. Read the Release Notes
2. 
   
3. Obtain Appliance software from https://support.oracle.com using your Customer Support Identifier (CSI #).

Re-image Procedure:

 To re-image the ODA, you’ll need to connect to the ILOM service to load the ODA with the new OS image.   In this post, I will layout the steps needed to re-image the ODA with brief instructions and screen captures to guide you.  To get started, you’ll need to connect to the ILOM service and launch a remote session from the ILOM interface.  The next figure shows the sign-on page from ILOM.  The default logon is “root” and the password is changeme

Summery:

1.    Clean existing ODA before start reimaging

2.    Download OS ISO Image from oracle support

3.    Mount ISO image on both nodes

4.    Reimage ILOM OS

5.    Configure Network on both nodes

1.  Clean existing ODA before start reimaging

Login ILOM from web browser with ILOM IP address

Oracle EBS R12.2 Online Patching (ADOP)

Apply patches Oracle Apps EBS R12.2.X

(Online Patching Using ADOP Utility)

Introduction:

As we know that applying patch in ORACLE EBS R12.2.X is different than R12.1.X. SO From R12.2.0 onward oracle has introduced online patching functionality called ADOP.

ADO: Stands for Application DBA Online Patching and Introduced in EBS R12.2. The adop utility is used to apply patches to Oracle E-Business Suite without significant system downtime. 

Oracle EBS 12.2 introduces Online Patching, a new feature that seriously reduces the downtime that was needed in previous releases for application of Release Update Packs (RUPs), Critical Patch Updates (CPUs), and other patches and bug fixes of different kinds.

EBS R12.2.X have are 3 File System Installed.

1.  FS1 – RUN_EDITION:
Production file system that is used by online users when system is being patched.
2.  FS2 – PATCH_EDITION:
Exact copy of production (fs1) used by the patching tools. Changes do not affect the running application (RUN_EDITION). 
When patching is completed and we do CUTOVER, then patching tool swaps the FS1 and FS2 file systems. It means, FS2 file system will become FS1, which will be access by the users.
3. FS-NE_Non-Edition:
This is a non-edition file system which stores data that is stored in a file system like log file, report file and patch top files.

Oracle EBS Online patching- ADOP Consists Below Phases:

FIVE PHASES:

1.     PREPARE  

2.     APPLY

3.     FINALIZE

4.     CUTOVER

5.     CLEANUP

Steps:

Ø  Download the Patch and unzip on patch_top.($NE_BASE/EBSapps/patch)

In my case is: /u01/patches/

Ø  Set the environment or Source (. ./EBSapps.env) in my case is: /u01/test/
Ø  Make sure and check run level 

Ø   Check status

$ adop -status

Ø   ADOP Syntax

adop phase=<phase_name>

Ø  Before start phases make sure export JVM  

  export CONFIG_JVM_ARGS="-Xmx3072m -Xms1024m"

1.     PREPARE PHASE

 Prepare to start a new online patching cycle by using below command

$ adop phase=prepare

Wait for the prepare phase to be complete.

Note: Please check log file as mention prepare phase while running commands

Please check the status from below points:

$ adop -status

Enter the APPS password:

Enter the WEBLOGIC password:

Enter the SYSTEM password:

2.     APPLY PHASE

Apply one or more patches to the patch edition of an Oracle E-Business Suite system by executing the following commands:

Syntax:

$ adop phase=apply patches=Patch_Number

$ adop phase=apply patches=Patch_Number1, Patch_Number2, …

$ adop phase=apply patches=26050719

Enter password as required during this phase like below:

Enter the APPS password:

Enter the WEBLOGIC password:

Enter the SYSTEM password:

Wait for the APPLY phase to be complete.

Note: Please check log file as indicate while running this phase command.

At the end status must be like below, In every phase status must be success.

The prepare phase completed successfully.

adop exiting with status = 0 (Success)

3.     FINALIZE PHASE

Perform the final patching operations in this phase by using the following command (which can be executed while the application is still online.

$ adop phase=FINALIZE

Enter password as same as enter in step 1,2.

Wait for the FINALIZE phase to be complete.

Note: Please check log file as indicate while running this phase command 

4.     CUTOVER PHASE

Transition to the patched environment 

$ adop phase=CUTOVER

Enter password as same as enter in step 1,2 and 3.

Wait for the cutover phase to be complete.

Note: Please check log file as mention apply phase after run command..

5.     CLEANUP PHASE

Remove old objects that are no longer needed from the patch process by running below command

$ adop phase=CLEANUP

Enter password as same as enter in step 1,2,3 and 4.

Wait for the cleanup phase to be complete.

Note: Please check log file as indicate while running this phase command 

At the end status must be like below, In every phase status must be success.

The cleanup phase completed successfully.

adop exiting with status = 0 (Success)

Now Check Status.

Keep Smile 😊

Reference:

https://docs.oracle.com

Oracle EBS R12.2 Official Guide