Load Balancer Configuration High Level Steps in EBS

High Level Steps Involved in Load Balance configuration in EBS R12.2

 

 
Configuration Topologies: 

Using Hardware Load Balancers with Single Web Entry Point:

•     Update Applications Context File
•     Common Steps**

Using Hardware Load Balancers with Multiple Web Entry Points:

•     txkChangeProfH.sql SERVRESP
•     Update Applications Context File
•     Common Steps**

Using Hardware Load Balancers with Functional Redirection:

•     txkChangeProfH.sql SERVRESP
•     Update Applications Context File
•     Update profiles responibility level  (afservrespval.sql)
•     Common Steps**

Using Domain Name Server (DNS) Load Balancing with Single Web Entry Point:

•     Configure DNS
•     Update Applications Context File
•     Common Steps**

Note: DNS Load Balancing requires Oracle HTTP Server to be configured on all the nodes


Common Steps**

•     Run the AutoConfig utility on all the application tier Servers
•     Restart application server processes
•     Test sign on from the load balancer entry point

Oracle EBS Upgrade R12.2

In this post, explained an overview of the Oracle EBS upgrade paths and high level steps involved in Upgrading Oracle E-Business Suite 11i/R12.1 to R12.2.

Before Starting, review the below images to understand EBS Roadmap and Oracle support limits.

Overview: 

The process of upgrading Oracle E-Business Suite to Release 12 involves updating the middleware technology stack and a new APPL_TOP on the application tier. The primary utilities used in the R12 upgrade process are Rapid Install and AutoPatch. 

Rapid Install installs the new R12 technology stack and AutoPatch upgrades the Oracle E-Business Suite database to Release 12.

For 11i requirement for upgrading to Release 12.2 is that the Oracle E-Business Suite version be at 11.5.10.2 along with minimum baseline patches.

For R12, the requirement is that the Oracle E-Business Suite versions be at 12.0.4 (or higher) or 12.1.1 (or higher) prior to upgrading to 12.2.

11.5.10.2, 12.0.4+, 12.1.1+  ⇨  R12.2

Note: The database must be upgraded to the latest patchsets of 11gR2 or 12cR1 prior to the 12.2 upgrade.

Similarly to Oracle Application, Oracle Database releases also has direct upgrade paths, if direct path not available, we need to upgrade to intermediate release to reach the target release (Example: Target Release, 12cR1). 

Below listed Oracle Database releases which has direct upgrade paths to 12cR1.

10.2.0.5,11.1.0.7,11.2.0.2+  ⇨ 12cR1

High Level Steps involved in Upgrade Oracle EBS R12.2:

• Install Oracle Home 12c -- If rapidwiz not used, Oracle Examples should be installed on top of Oracle Home.
• Refer appropriate interoperability notes and upgrade Database to 12.1.0 
• Complete post upgrade scripts
• Install R12.2 File System (Core Tree Structure)
• Run the American English upgrade patch driver

Note: Run Gather Stats prior running american driver for better performance and add adequate space to the tablespace.

• Database Configuration -- eg: autoconfig
• Configure Release 12.2 EBS -- Run rapidwiz and provide the run file system contextfile during the configuration.
• Online Patching Enablement patch -- Enable ADOP 
• Apply AD/TXK Latest Patches
• Create Custom Top, if required
• Apply Release Update Pack (Example, R12.2.8)

Oracle Database Cloud Backup

Oracle Database Backup Service -- securely backup your database using RMAN interface for seamless backup and restore operations.

Step 1: Create a container in Oracle Cloud to save the backup.

Step 2: Install Oracle Cloud Backup Module 

[orauser@test opc_wallet]$ ls

cwallet.sso  cwallet.sso.lck

[orauser@test dbs]$ cat opcDEV.ora

OPC_HOST=https://storage_container_url

OPC_WALLET='LOCATION=file:/u01/orauser/dbtest/dbhome/dbs/opc_wallet CREDENTIAL_ALIAS=alias_opc'

Step 3: RMAN Configuration and backup

RMAN> CONFIGURE CHANNEL DEVICE TYPE sbt PARMS='SBT_LIBRARY=/u01/orauser/dbtest/dbhome/lib/libopc.so, SBT_PARMS=(OPC_PFILE=/u01/orauser/dbtest/dbhome/dbs/opcDEV.ora)';

RMAN> SET ENCRYPTION ON IDENTIFIED BY '<Password>' ONLY;

RMAN> CONFIGURE COMPRESSION ALGORITHM 'MEDIUM';

RMAN> CONFIGURE DEVICE TYPE sbt BACKUP TYPE TO COMPRESSED BACKUPSET;

RMAN> CONFIGURE DEFAULT DEVICE TYPE TO 'sbt_tape';

$ rman target /

RMAN>  backup database plus archivelog;

Verify the backups are created in container.

Step 4: Using backup for restore operation.

Using the backup created in Oracle cloud, we can use it to restore/recovery during any failure of on-premises database and can also be used to create the database in Oracle cloud i.e. we can migrate Oracle Database from On-Premises to Oracle Cloud.

RMAN> SET DECRYPTION IDENTIFIED BY '<Password>';

RMAN> SET DBID=<Database_ID>;

RUN {

ALLOCATE CHANNEL t1 DEVICE TYPE sbt PARMS='SBT_LIBRARY=/u01/orauser/dbtest/dbhome/lib/libopc.so, SBT_PARMS=(OPC_PFILE=/u01/orauser/dbtest/dbhome/dbs/opcDEV.ora)';

RESTORE ...;

}

Creating Database service using cloud backup.

Create Oracle Database Service in Oracle Cloud

Process Flow:

 Step1: Create SSH key

Note: 

We can provide Passphrase to enhance security. 

To save public key use copy & paste, save it as .pub file.

Step2: Create the Database Cloud Service

Note: In Advanced setting, we can define the port and timestamp for the database.

Step 3: Apply security rules to access the cloud the service (Database).

Step 4: Use dbaas_monitor

Database Partitioning -- Oracle EBS (Part 1)

Database Partitioning -- process of logically and/or physically segmenting data (and it’s associated storage, tables and indexes) into more manageable pieces, in order to improve manageability and accessibility.

A good partitioning design lies the choice of a suitable partitioning key, typically be the column that is most frequently used as the predicate to access the data.

Partitioning Methods:

• Range Partitioning -- Example: partitioning the GL_BALANCES table as ranges by "Period Name".
• List Partitioning -- Example: Partitioning OE_ORDER_LINES_ALL table to have categories listed like open & closed Orders using OPEN_FLAG.
• Hash Partitioning -- Hash function to the partitioning key to stripe data into partitions.
• Composite Partitioning -- Data is partitioned by using both the range method and then sub-partitioned by the hash method. Example: WF_ITEM_ACTIVITY_STATUSES Partitioned with Range of Item Type and then sub partitioned using Hash Method.

Index Partitioning & Methods: 

Partitioned or non-partioned indexes can be used with partitioned or non-partitioned tables.

• Global Non-partitioned (prefixed)
• Global Partitioned (prefixed)
• Local Partitioned Prefixed
• Local Partitioned Non-Prefix

Advantages:

• It brings significant benefits in performance - Improves access path/scanning the current partition
• Easy to manage the table and index can be rebuild at partition level
• Improves purge performance
• Improves Upgrade performance
• No modifications to application queries are necessary when accessing a partitioned table.
• CBO is partition aware.

Note: If an incorrect partitioning design is chosen, partitioning can actually degrade rather than enhance performance.

Important Database Views:

DBA_TABLES

DBA_PART_TABLES

DBA_TAB_PARTITIONS

DBA_PART_KEY_COLUMNS

DBA_PART_HISTOGRAMS

DBA_PART_COL_STATISTICS

DBA_SUBPART_KEY_COLUMNS

DBA_IND_PARTITIONS

DBA_IND_SUBPARTITIONS

DBA_PART_INDEXES

adcfgclone java.lang.OutOfMemoryError: Java heap space

Environment: 
Oracle EBS R12.2.5 
Oracle Linux 7

Issue:
When running adcfgclone on appstier with dualfs option below error occurred at a stage of weblogic EBS_DOMAIN creation,

Exception in thread "Thread-1" java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOfRange(Arrays.java:2694)
at java.lang.String.<init>(String.java:203)
at java.io.BufferedReader.readLine(BufferedReader.java:349)
at java.io.BufferedReader.readLine(BufferedReader.java:382)
at com.oracle.cie.common.util.CRLF.readData(CRLF.java:129)
at com.oracle.cie.common.util.CRLF.processFile(CRLF.java:67)

Solution:

we tried defining the variable value like in below combinations but the issue persists. 

export CONFIG_JVM_ARGS="-Xms512m -Xmx1024m"

MEM_ARGS="-Xms512m -Xmx1024m -XX:+UseParalle lGC"

MEM_ARGS="-Xms512m -Xmx1024m"

export CONFIG_JVM_ARGS="-Xms1024m -Xmx2048m"

Later it was identified to be abnormal growth of a file in $EBS_DOMAIN_HOME. File -- aferror.log consumed more space (size was around 4GB)

After moving that file, completed pre-clone in source.

Taken fresh backup and this time cloning was successful in appsTier. 

Oracle 18c

Oracle Database 18c, its now available in Oracle Cloud and on Engineered System. 

It is expected to be a core component in Autonomous Database Cloud Services. It has new functionality and improvements to existing 12c features like Multitenant, Sharding, In-memory. 

Snapshot Carousel: Defining regular snapshots of PDBs that can then be used for a full PITR clone. It is ideally suited to development environments.

Refreshable PDB Switchover: PDB, incrementally updated copy of a master PDB, that may subsequently be switched over between each other, i.e. master PDB becomes the clone and the old clone the master. This enables to gracefully switch workloads between different CDBs.

Oracle In-Memory: Managing column store content can now be automated, i.e. database automatically takes care of populating objects into the IM column store and removing those that are no longer relevant. Optimizer routes analytic and transactional queries to column and row format respectively, the IM column store is extended to flash on Exadata storage (both on-premises and Oracle Cloud) to hold enlarging columnar formatted data. 

Distributed Realtime Analytics: Maintaining an IM column store on an Active Data Guard standby database running on Oracle Cloud and Oracle Exadata, making more productive use of standby databases and delivers high performance analytics.

MemOptimized RowStore: Designed for fast query performance that require very fast and low latency lookups based on primary key values. Attribute, MEMOPTIMIZE FOR READ, is used to indicate which tables are to be pinned into the buffer cache with this new hash index.

Oracle Clusterware 18c: Enhances new deployment options introduced in Oracle 12cR2 called Oracle Cluster Domain, . Oracle 18c allows both new installations to be deployed as a Cluster Domain model while allowing standalone Clusters to be converted to Member Clusters.

Oracle Domain Services Cluster provides centralized services to other clusters within the Oracle Cluster Domain. These services include:

• A centralized Grid Infrastructure Management Repository 
• Trace File Analyzer(TFA), for diagnostic data collection 
• Consolidated Oracle ASM storage management service
• Rapid Home Provisioning (RHP) Service to install clusters, and provision, patch, and upgrade Oracle Grid Infrastructure and Oracle Database homes.

Oracle ASM 18c: Enhances the database-oriented storage management using new ASM Flex Disk Group. It Includes,

• Modifiable redundancy at individual database file level 
• Snapshot capabilities 
• Quota management at the database level for consolidated environments.