AWS / Azure / GCP Cloud | Database | Data Analytics | LakeHouse | Machine Learning | Shrenik Parekh

Oracle E-Business Suite technology layer include: Oracle Applications DBA (AD) Oracle Application Object Library (FND) Oracle Applications Utilities (AU) Oracle Common Modules (AK) Oracle Workflow (WF) Oracle Alert (ALR) Oracle Application Framework (FWK) Oracle XML Publisher (XDO) E-Business Suite Services - Concurrent Managers and Workflow Mailers. Services are composed of one or more processes that must be kept running for the proper functioning of the applications. With Service Management , the Internal Concurrent Manager (ICM) manages the various service processes across multiple hosts. Service processes are very much like concurrent manager and transaction manager processes. Oracle Applications Manager can be used for a wide variety of tasks such as administering services including concurrent managers, examining system configuration, managing Oracle workflow, examining applied patches, and measuring system usage. E-business suite Concurrent programs: 01. Executes programs in b...

Following description about Oracle E-Business Suite is high level and from documentation https://docs.oracle.com/cd/E26401_01/doc.122/e22954/T202991T531062.htm#5281339 for in depth and detail description refer it.   E- Business Suite patching: Oracle E- Business Suite technology layer include: AD - Oracle Applications DBA (AD) FND - Oracle Application Object Library (FND) AU - Oracle Applications Utilities (AU) AK - Oracle Common Modules (AK) WF - Oracle Workflow (WF) ALR - Oracle Alert (ALR) FWK - Oracle Application Framework (FWK) XDO - Oracle XML Publisher (XDO) RUP - Release update pack (RUP) TXK - EBS 12.2 technology stack (TXK) and Applications Database (AD) components CPU - Critical Patch Updates PSUs - Patch set updates ATG - Application technology group PAA - Oracle Patch Application Assistant OAM - Oracle Applications Manager Patch files Structures: The README.txt or README.html file describes what the patch does. Driver File - u<patchnum>.drv, contains...

Oracle E-Business Suite Daily SQL: Current version: SELECT RELEASE_NAME FROM APPS.FND_PRODUCT_GROUPS; Find out application server information from database server:   column name format a20 SELECT NAME, NODE_ID, SERVER_TYPE FROM APPS.FND_APP_SERVERS; NAME                                     NODE_ID       SERVER_TYPE --------------------                      ----------          ------------------------------ <hostname>_EBSDEV_APPS      10113            APPS <hostname>_EBSDEV_DB          10112...

Oracle E-Business Suite Application Tables: APPLSYS FND_APPLICATION APPLSYS FND_APP_SERVERS_U2 APPLSYS FND_APPLICATION_S APPLSYS FND_APPLICATION_SERVERS APPLSYS FND_APPLICATION_SERVERS# APPLSYS FND_APPLICATION_SERVERS_U1 APPLSYS FND_APPLICATION_SERVERS_U2 APPLSYS FND_APPLICATION_TL APPLSYS FND_APPLICATION_TL# APPLSYS FND_APPLICATION_TL_U1 APPLSYS FND_APPLICATION_TL_U2 APPLSYS FND_APPLICATION_U1 APPLSYS FND_APPLICATION_U3 APPLSYS FND_APPL_SESSIONS APPLSYS FND_APPL_SESSIONS# APPLSYS FND_APPL_SESSIONS_N1 APPLSYS FND_APPL_SESSIONS_N2 APPLSYS FND_APPL_TOPS APPLSYS FND_APPL_TOPS# APPLSYS FND_APPL_TOPS_U1 APPLSYS FND_APPL_TOPS_U2 APPLSYS FND_APPS_SYSTEM APPLSYS FND_APPS_SYSTEM# APPLSYS FND_APPS_SYSTEM_U1 APPLSYS FND_APPS_SYSTEM_U2 APPLSYS FND_APP_SERVERS APPLSYS FND_APP_SERVERS# APPLSYS FND_APP_SERVERS_U1 APPLSYS FND_APPLICATION# APPLSYSPUB FND_APPLICATION APPLSYSPUB FND_APPLICATION_TL APPLSYSPUB FND_APPLICATION_VL APPS FND_APPFLDR APPS FND_APPLICATION_TL= APPS FND_APPLET_LAUNCHER APPS FND_AP...

Oracle E-Business Suite FND product tables: APPLSYS FND_PRODUCT_DEPENDENCIES APPLSYS FND_PRODUCT_DEPENDENCIES# APPLSYS FND_PRODUCT_INSTALLATIONS_PK APPLSYS FND_PRODUCT_INSTALLATIONS# APPLSYS FND_PRODUCT_INSTALLATIONS APPLSYS FND_PRODUCT_INIT_DEPENDENCY_U1 APPLSYS FND_PRODUCT_INIT_DEPENDENCY# APPLSYS FND_PRODUCT_INIT_DEPENDENCY APPLSYS FND_PRODUCT_INIT_CONDITION_U1 APPLSYS FND_PRODUCT_INIT_CONDITION# APPLSYS FND_PRODUCT_INIT_CONDITION APPLSYS FND_PRODUCT_INITIALIZATION_U1 APPLSYS FND_PRODUCT_INITIALIZATION# APPLSYS FND_PRODUCT_INITIALIZATION APPLSYS FND_PRODUCT_GROUPS# APPLSYS FND_PRODUCT_GROUPS APPLSYS FND_PRODUCT_DEPENDENCIES_U1 APPLSYSPUB FND_PRODUCT_GROUPS APPLSYSPUB FND_PRODUCT_INSTALLATIONS APPS FND_PRODUCT_INIT_DEPENDENCY APPS FND_PRODUCT_INIT_CONDITION= APPS FND_PRODUCT_INIT_CONDITION+ APPS FND_PRODUCT_INIT_CONDITION APPS FND_PRODUCT_INITIALIZATION_PKG APPS FND_PRODUCT_INITIALIZATION_PKG APPS FND_PRODUCT_INITIALIZATION= APPS FND_PRODUCT_INITIALIZATION+ APPS FND_PRODUCT_INITIALIZ...

Configure MySQL Database parameters for Galera replication in /etc/my.cnf file: #Defines the path to the Galera Replication Plugin. wsrep_provider=/usr/lib/libgalera_smm.so #Semicolon (;) separated list of wsrep options, #https://mariadb.com/kb/en/library/wsrep_provider_options/ wsrep_provider_options="gcache.size=300M; gcache.page_size=300M" # logical name for your cluster. You must use the same name for every node in your cluster. wsrep_cluster_name="my_cluster" #IP addresses of nodes in a comma separated list. wsrep_cluster_address="gcomm://node1,node2,node3" #method or script the node uses in a State Snapshot Transfer, mysqldump, rsync, #rsync_wan, xtrabackup,wsrep_%.sh For instance, giving the node a transfer method of #MyCustomSST causes it to look for wsrep_MyCustomSST.sh in /usr/bin wsrep_sst_method=rsync #logical name for the individual node. wsrep_node_name=node1 #set the IP address for the individual node. w srep_node_address="192.168.0...

Features of Galera Cluster: Multi-master - Galera cluster is real multi master, all the nodes are available for read and write operation. Synchronous replication - Replication in Galera cluster is synchronous. There is no slave, so there is no slave lag, either write to all node or all roll back. Tightly coupled - All nodes in Galera cluster are coupled tightly. Data on all node is same. Performance - Galera cluster support multi threaded to balance workload No failover - As there is no slave so there is not master slave failover. Hot standby - Standby nodes are always available and have same data, so there is hot standby. Automatic node provisioning - While adding new node to cluster family there is no need to manually back up the database, no need to restore backup to new node. InnoDB - Galera cluster supports only InnoDB engine. Transparent to application - Galera cluster is transparent to application No splitting - No read and write node, all nodes are read a...