How to Install EBS R12.2.14 On OCI Cloud From OCI Marketplace 2025

 Dear All,

in this post will share how to Install Oracle EBS R12.2.14 step by step in Oracle Cloud Infrastructure .

pre-requisites : 

you should have oracle cloud account 

you should have Public & Private keys from your machine ( Optional ), if you dont have you can generate while installing the Software from the Cloud Console .

Basic idea about port open, TNS setup and forms open setup in Your Machine .

==== ==== ====== ==== =====

Reference Documents : 

Oracle EBS On OCI >>>> 2517025.1 

Provision a New Oracle EBS installation on a single node on OCI >>> 2764690.1 

EBS On OCI - 12.2.14 step by step setup 

=========================================

This document is divided into the following sections:

Step 1: Before You Begin

Step 2: Create Instance Using an Image from the OCI Console Marketplace

Step 3: Perform Post-Install Steps

Step 4: Take Steps to Further Secure Your Instance

Step 5: References

Step 1: Before You Begin

In this procedure, you will use an image hosted in Oracle Cloud Infrastructure (OCI) to provision an Oracle E-Business Suite Release 12.2.14 with Oracle Database 19c environment on a single Compute instance (VM) on OCI.

You can provision using the demo install image, and conduct demonstrations and explore new features with the resulting environment, or you can provision using the fresh install image, and tailor the resulting environment to your specific needs.

1.1 Background 

Create an Oracle Cloud Infrastructure Compute instance (VM) containing the Release 12.2.14 database and application tiers from one of the provided images:

Oracle E-Business Suite 12.2.14 Demo Install Image - The instance contains demonstration data and is suitable for conducting demonstrations and exploring new features.

Oracle E-Business Suite 12.2.14 Fresh Install Image - The instance can be configured with your own data and specific, functional setups so that you can test business processes tailored to your needs.

The images can be found in the OCI Console Marketplace and also in the OCI Oracle Images list in your tenancy. Instructions for the OCI Console Marketplace are provided in this document.

The environment you create will have the following embedded technology components: 

Operating System

Component Version YUM Updated Level

Oracle Linux 8 8.10 64-bit

For Oracle E-Business Suite 12.2.14 Demo Install Image: September 11, 2024

For Oracle E-Business Suite 12.2.14 Fresh Install Image: September 11, 2024

Technology Component Versions

Component Version

RDBMS Oracle Home Oracle Database 19c (19.24 RU)

Consolidated patches for database components (July 2024) Oracle E-Business Suite Release 12.2: Consolidated List of Oracle Database Patches and Bug Fixes (Document 1594274.1)

Application Code Level

Oracle E-Business Suite 12.2.14 Release Update Pack (Document 3011520.1)

R12.AD.C.Delta.16 and R12.TXK.C.Delta.16 (Document 1617461.1)

Critical Patch Update (CPU) - Refer to Oracle E-Business Suite Release 12.2 Critical Patch Update Availability Document (July 2024) (Document 3029477.1)

Oracle E-Business Suite Person Data Removal Tool (PDRT) patches (Document 2388237.1)

Oracle Forms and Reports 10.1.2.3

Oracle WebLogic Server 10.3.6.0.231017

Web Tier 11.1.1.9

JDK 1.7.0_431

Consolidated patches for middle tier components (July 2024) Refer to Oracle E-Business Suite Release 12.2: Consolidated List of Oracle Fusion Middleware Patches and Bug Fixes (Document 2877607.1)

Java Client Java Web Start is enabled by default in your environment. Refer to My Oracle Support Knowledge Document 2188898.1, Using Java Web Start with Oracle E-Business Suite, for information about the use of Java Web Start with Oracle E-Business Suite.

Note: Alternatively, you can use the Oracle E-Business Suite Cloud Manager to provision Oracle E-Business Suite in Oracle Cloud, migrate Oracle E-Business Suite environments from on-premises to Oracle Cloud, and conduct subsequent lifecycle management of these cloud environments. See My Oracle Support Knowledge Document 2517025.1, Getting Started with Oracle E-Business Suite on Oracle Cloud Infrastructure, to understand the complete range of options.

1.2 What Do You Need?

An understanding of the relevant information in My Oracle Support Knowledge Document 2517025.1, Getting Started with Oracle E-Business Suite on Oracle Cloud Infrastructure.

An SSH Key Pair which will be used for accessing your instance. See Managing Key Pairs on Linux Instances.

An Oracle Cloud Infrastructure (OCI) tenancy, with the following associated resources:

A compartment

A user who is either a tenancy administrator, or who has privileges to manage all resources in the compartment

A Virtual Cloud Network (VCN) and an associated subnet which will be associated with the Oracle E-Business Suite environment

1.3 (Optional) Prepare a Configuration Initialization Script

A configuration script template (ebs_bootstrap.sh) is attached to this My Oracle Support document. By downloading and customizing this script and providing it as input to the Create Compute Instance dialogue in Step 2 when prompted for a "cloud-init" script, you can achieve the following:

Extend the free space on the instance to allow for future online patching (adop) operations.

Update the operating system with the latest yum update.

Enable instance-level firewall access to Port 8000.

Update the hostname.

Configure the web entry point.

Run AutoConfig and start services.

Alternatively, these tasks can be conducted as post-installation steps by following the steps in Step 2.

Step 2: Create Instance Using an Image from the OCI Console Marketplace

Follow these steps to create and connect to your Compute instance which contains an Oracle E-Business Suite environment when using an image from the OCI Console Marketplace.

Log in to the OCI Service Console.

Select Menu, then Marketplace.

In the Search field, type desired search criteria. For example, e-business, 12.2.14 Demo, or 12.2.14 Fresh.

Click on Oracle E-Business Suite 12.2.14 Demo Install Image or on Oracle E-Business Suite 12.2.14 Fresh Install Image, and on the resulting screen, do the following:

If there are multiple packages, select the latest package version from the dropdown list unless you require an earlier version.

Select the compartment or subcompartment where you wish to install Oracle E-Business Suite.

Review and accept the Oracle Standard Terms and Restrictions.

Click Launch Instance.

In the Create Compute Instance screen, specify the following:

Under Name, enter your choice of name. For example, ebs12214-demo.

Under Create in compartment, verify your choice of compartment or select another.

In the Placement region, select from the Availability domains shown.

In the Image and Shape region:

Under Image, you will see the name of the OCI Console Marketplace image you chose in Step 1.

Under Shape, you will see a default shape. If you want to specify another shape, click on Change Shape.

In the Networking region:

Under Network, select an existing virtual cloud network, for example, my-vcn.

Under Subnet, select an existing subnet, for example, my-subnet.

Note: If the VM is associated with a public subnet and you want to assign a public IP address, then select the Assign a public IPV4 address option.

In the Add SSH keys region, select Choose public key files to specify the file containing your SSH public key generated previously.

In the Boot volume region, make no changes to accept the default volume size.

(Optional) Click on Show advanced options to supply your customized cloud-init script, ebs_bootstrap.sh from Step 1.3, to be run at instance startup.

Click Create to create your Compute Instance.

Establish SSH Connectivity.

Review the security lists associated with the subnet to ensure that an ingress rule exists with the following attributes:

SOURCE TYPE: CIDR

SOURCE CIDR: Enter the CIDR block of your choice. Note that 0.0.0.0/0 corresponds to the public internet. We recommend restricting this to the CIDR block that corresponds to the IP range you want to give access to.

IP PROTOCOL: SSH (TCP/22)

DESTINATION PORT: 22

When the instance is fully provisioned and running, connect to it using SSH as described in Connecting to an Instance.

After the instance has been created (provisioned), it will appear in the instance list. To view full details about it, including IP addresses, click the instance name in the list.

Step 3: Perform Post-Install Steps

After you provision your environment, perform the tasks below to configure access and secure the environment. If you provided a cloud-init script as part of compute instance creation, you can skip tasks performed by the script.

Note: After performing the steps in this section, the steps in Step 4: Secure Your Instance should be followed to ensure that your environment is secure.

In order to perform the tasks in this section, you must first connect as the opc user using ssh to the Oracle Cloud Infrastructure instance that hosts your Oracle E-Business Suite environment.

3.1 Update Operating System (Conditional)

Perform this step if you did not already do so using the cloud-init script as part of compute instance creation.

Switch from the opc user to the root user, and then perform an operating system update using the following commands:

$ sudo su -

# yum update

Is this ok [y/d/N]: y

3.2 Enable Instance-Level Firewall Access to Port 8000 (Conditional)

Perform this step if you did not already do so using the cloud-init script as part of compute instance creation.

In order to access the applications, you must enable firewall access to port 8000 on your instance.

While still logged on as the root user, use the following commands to enable port 8000:

# firewall-cmd --add-port=8000/tcp --permanent

# systemctl restart firewalld

To confirm the change, use the following command:

# firewall-cmd --list-all

3.3 Update Hostname (Conditional)

Your hostname must be updated to reflect the current VCN network configuration.

Perform this step if you did not already do so using the cloud-init script as part of compute instance creation.

Your hostname must be updated to reflect the current VCN network configuration.

While still logged on as the root user, perform a required hostname update using the following command:

# /u01/install/scripts/updatehosts.sh

3.4 Configure Web Entry Point (Optional)

Skip this step if it was performed using the cloud-init script during compute instance creation.

As the oracle user, use the configwebentry.sh script provided in the /u01/install/scripts directory to change the web entry point, which is by default set to the physical hostname of the virtual machine. For instance, you could follow the steps in this example to set the web entry point to myapps.example.com and access the application using http://myapps.example.com:8000/OA_HTML/AppsLogin:

Note: For the ORACLE_SID value, use uppercase for a Fresh Install instance; for example: EBSDB. For a Vision Demo instance, use lowercase; for example, ebsdb.

$ /u01/install/scripts/configwebentry.sh

Enter the Web Entry Protocol (Eg: https/http): http

Enter the Web Entry Host Name(Eg: public): myapps

Enter the Web Entry Domain Name:(Eg: example.com): example.com

Enter the Web Entry Port:(Eg: 443/80): 8000

Enter the ORACLE_SID:(Eg: EBSDB): EBSDB

Running AutoConfig to complete the configuration

Enter the APPS user password:  <apps_password>

As the oracle user, start the application tier services.

# sudo su - oracle

$ /u01/install/APPS/scripts/stopapps.sh

$ /u01/install/APPS/scripts/startapps.sh

3.5 Enable HTTP Access

Follow these steps to enable web access to the applications.

From the OCI console, add a security rule to the security list.

Navigate to Networking, then Virtual Cloud Networks.

Select the VCN associated with your instance, such as my-vcn.

Identify the subnet associated with your instance, and click on the link for the security list.

Click Edit All Rules.

Add an Ingress Rule with the following attributes:

SOURCE TYPE: CIDR

SOURCE CIDR: Enter the CIDR block of your choice. Note that 0.0.0.0/0 corresponds to the public internet. We recommend restricting this to the CIDR block that corresponds to the IP range you want to give access to.

IP PROTOCOL: TCP

DESTINATION PORT: 8000

3.6 Update Local Hosts File on Your Client Machine (Conditional)

Note: If you register your web entry host name and domain in your DNS system, you do not need to perform this step.

While logged on to the Compute instance that hosts your Oracle E-Business Suite environment, run the following command to verify your hostname:

$ hostname -f

Substitute the value that is returned for hostname in the instructions below.

Update the Local Hosts File on Windows:

Find the hosts file you want to modify.

Open the file explorer to open the following directory: C:\\Windows\System32\drivers\etc

As you CANNOT edit in this folder, perform the following:

Copy this hosts file to your desktop.

Edit the hosts file with a text editor.

Add one line with the IP address and host name: <external-IP-address> <hostname>

Once added, save the file as the hosts file without any extension.

Then, you can copy it back to the original folder.

Confirm the replacement as an administrator.

Update the Local Hosts File on Mac:

On your Mac, open the Terminal application.

Change to the folder where you will find the hosts file.

$ cd /etc

Use the following vi command to edit the file:

$ sudo vi hosts

Add your host name and save the file.

<external-IP-address> <hostname>

3.7 Enable and Change SYSADMIN Password

To ensure your environment is adequately protected, you must change your Oracle E-Business Suite account passwords.

While still logged on to the Oracle Cloud Infrastructure instance that hosts your Oracle E-Business Suite environment, switch from the opc user to the oracle user using the following command:

$ sudo -i -u oracle

Start the database:

$ /u01/install/APPS/scripts/startdb.sh

Start the application tier processes:

$ /u01/install/APPS/scripts/startapps.sh

Set the environment:

$ . /u01/install/APPS/EBSapps.env run

To log in through the web interface, you must initially set a password of your choice for the SYSADMIN user. After the SYSADMIN user is active with the new password, you can create new users or activate existing locked users. To enable the SYSADMIN user, run the following commands:

$ mkdir -p ~/logs

$ cd ~/logs

$ sh /u01/install/APPS/scripts/enableSYSADMIN.sh

When prompted, enter a new password for the SYSADMIN user.

The SYSADMIN user can now connect to Oracle E-Business Suite through the web interface and create new users or activate existing locked users.

3.8 Enable Vision Demo Users and Set User Passwords (Conditional)

For a Vision demo environment, you can run another script to unlock a set of 36 application users that are typically used when demonstrating Oracle E-Business using the Vision database. Run this script with the same environment as when running the enableSYSADMIN.sh script. To enable the demo users, run the following commands:

$ cd ~/logs

$ /u01/install/APPS/scripts/enableDEMOusers.sh

When prompted, enter a new password.

Do not run this script on a fresh or production environment.

3.9 Log in to Applications

You can now access the applications using http://<hostname>:8000/OA_HTML/AppsLogin.

For instance, if your host name is myapps.example.com, your login will be:

http://myapps.example.com:8000/OA_HTML/AppsLogin

3.10 Enable Oracle E-Business Suite Integrated SOA Gateway for REST Services (Conditional)

The procedure below can be used to enable Oracle E-Business Suite Integrated SOA Gateway (ISG) for REST services in an environment created from the Oracle E-Business Suite 12.2.14 Demo Install Image.

Additional steps may be required for production environments.

Enable Oracle E-Business Suite Integrated SOA Gateway (ISG) for REST services by using the following commands:

$ cd ~/log

$ /u01/install/APPS/scripts/enableISG.sh

At the start of the script execution, when prompted, enter the APPS Schema password and the WebLogic password.

Note: The required setup tasks for enabling Oracle E-Business Suite REST services provided through Oracle E-Business Suite Integrated SOA Gateway are already preconfigured in your Vision Demo environment. This means that Oracle E-Business Suite integration interface definitions published in Oracle Integration Repository, a component in Oracle E-Business Suite Integrated SOA Gateway, are available for REST service deployment.

Interface types enabled for REST services are PL/SQL APIs, Java Bean Services, Application Module Services, Concurrent Programs, Business Service Objects, and Open Interface Tables and Views.

For more information on deploying and configuring Oracle E-Business Suite REST services, see:

Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12.2, My Oracle Support Knowledge Document 1311068.1.

Administering REST Web Services, Oracle E-Business Suite Integrated SOA Gateway Implementation Guide

For more information on supported interfaces for REST services and on REST service invocations, see:

Oracle E-Business Suite Integrated SOA Gateway User's Guide

Oracle E-Business Suite Integrated SOA Gateway Developer's Guide

3.11 Configure Enterprise Command Center Dashboards (Conditional)

Oracle Enterprise Command Center Framework V14 is installed in Vision Demo environments. To learn more about Enterprise Command Centers and available discovery dashboards, refer to Oracle E-Business Suite Enterprise Command Centers (ECC) - Quick Start Guide.

To use Enterprise Command Centers in your Vision Demo environment, perform the following configuration steps.

Update the source system URL.

Log in to your Oracle E-Business Suite environment as the sysadmin user, and select the ECC Developer responsibility.

Select Source System in the navigation pane of the Oracle Enterprise Command Center Framework administration UI.

In the Source System Definition page, enter your Oracle E-Business Suite login URL in the Source System URL field. The login URL for this environment was derived in Step 3.8.

Initially, the Oracle Enterprise Command Center Framework installation includes data only for the Oracle Assets Command Center (FA). Before you can access an Enterprise Command Center dashboard for any other products, you must perform a full load of the product-specific data into the Oracle Enterprise Command Center Framework installation.

Run the data load concurrent program for your product as listed in Loading Product Data to Enterprise Command Centers, My Oracle Support Knowledge Document 2495053.1, Installing Oracle Enterprise Command Center Framework, Release 12.2. For more details about each data load program, see your product-specific Enterprise Command Center documentation.

Step 4: Take Steps to Further Secure Your Environment

Taking these additional steps will ensure that your Oracle E-Business Suite environment in Oracle Cloud Infrastructure is secure.

4.1 Change Database Passwords for Base Product Schemas

While connected to your instance, switch from the opc user to the oracle user using the following command:

$ sudo su - oracle

Then change the database passwords for the base product schemas:

$ sh /u01/install/APPS/scripts/changeDBpasswords.sh

When the script prompts you to provide the password for the SYSTEM user, enter 'manager'.

Note: Once you have completed the setup tasks described in this document, you can change the passwords for APPLSYSPUB, APPLSYS, APPS, and APPS_NE schemas. See Appendix B, Database Schemas Found in Oracle E-Business Suite, Oracle E-Business Suite Security Guide for details.

4.2 Add IP Restriction to Database TNS Listener

Add the IP restriction to the database TNS listener using the following command after setting the environment for database ORACLE_HOME:

$ . /u01/install/APPS/19.0.0/EBSCDB_apps.env

$ cd $TNS_ADMIN/EBSDB_apps

$ cat > sqlnet_ifile.ora <<EOF

tcp.validnode_checking = YES

tcp.invited_nodes = ( apps.example.com )

EOF

$ lsnrctl stop EBSCDB

$ lsnrctl start EBSCDB

Now the database listener will only accept connection requests from this host apps.example.com.

4.3 Set New Passwords for SYS and SYSTEM Users

With the database environment variables that are set, set the new passwords for the SYS and the SYSTEM users.

$ sqlplus / as sysdba

SQL> alter user SYSTEM identified by <NEW_PASSWORD> ;

SQL> alter user SYS identified by <NEW_PASSWORD> ;

SQL> exit

4.4 Change Default Password for Weblogic (WLS) Administrator User

Change the password for the Oracle WebLogic Server (WLS) administrator user weblogic by using the following steps:

Source the run file system with the oracle user:

$ . /u01/install/APPS/EBSapps.env run

Stop most of the application tier processes, but leave the Node Manager and Admin server running:

$ adstpall.sh -skipNM -skipAdmin

When prompted, enter APPS user name (apps), APPS password, and current WebLogic Server password (welcome1).

Change password for the Oracle WebLogic Server administrator user weblogic:

$ perl $FND_TOP/patch/115/bin/txkUpdateEBSDomain.pl -action=updateAdminPassword

Accept the default apps context file path when prompted, enter the current WebLogic Admin password, new WebLogic Admin password, and APPS password.

Start all the application tier processes again on the run edition file system.

$ adstrtal.sh

When prompted, enter APPS user name, APPS password, and WebLogic Server password.

Replace <NEW_PASSWORD> with the password you just changed earlier for the weblogic user in the following command:

$ cd /u01/install/APPS/scripts/

$ chmod 700 st*apps.sh

$ for f in st*apps.sh ;do sed -i 's/welcome1/<NEW_PASSWORD>/' $f ;done

4.5 Manually Enable TLS

We highly recommend that you perform the following steps to encrypt the traffic between the client and the Oracle HTTP Server. After the encryption setup is complete, you must configure the Oracle E-Business Suite web entry point.

Prepare the environment by applying the prerequisites. See My Oracle Support Knowledge Document 1367293.1, Enabling TLS in Oracle E-Business Suite Release 12.2, Step 5.1: Apply Required Updates and Patches.

Encrypt the traffic from the client to the Oracle HTTP Server by performing the configuration for inbound connections for your Oracle E-Business Suite release. See My Oracle Support Knowledge Document 1367293.1, Enabling TLS in Oracle E-Business Suite Release 12.2, Step 5.2: Configure Inbound Connections.

4.6 Manually Configure Firewall to Limit Client Access

Perform the steps in this section to configure the required firewall rules.

First, on your application tier node, create firewall rules that allow inbound communication to the web entry point from the clients from which you will access the Oracle E-Business Suite URL. To do so, while still logged on to the instance via ssh, switch to the root user:

$ sudo su -

Run the following commands to create the required firewall rules:

# firewall-cmd --zone=public --add-rich-rule='rule family=ipv4 source address=<source_CIDR_range> port port=<web_entry_point> protocol=tcp accept' --permanent

# firewall-cmd --zone=public --add-rich-rule='rule family=ipv4 source address=<source_CIDR_range> port port=<web_entry_point> protocol=tcp accept'

In these commands, replace <source_CIDR_range> with the set of IP addresses from which you will access the Oracle E-Business Suite URL. Replace <web_entry_port> with the appropriate port, for example 4443.

Next, update the security list for the subnet that contains the application tier nodes by adding a security rule that allows inbound communication on the web entry point from the clients from which you will access the Oracle E-Business Suite URL. See Working with Security Lists.

In the Oracle Cloud Infrastructure console, open the security list for the application tier subnet and add a new entry under Allow rules for ingress with the following properties:

Source CIDR - The CIDR block for your on-premises network that includes the relevant clients, as specified in your firewall rules

Protocol - TCP

Destination Port Range - The web entry port, for example 443

4.7 Configure Security and Firewall Rules for Secure Access to Fusion Middleware and Weblogic Server Administration Console

Administration of the Oracle Fusion Middleware 11g components delivered with Oracle E-Business Suite Release 12.2, including Oracle HTTP Server and Oracle WebLogic Server, requires secure access to the WebLogic Server administration ports running on the Oracle E-Business Suite primary application tier node. Ports 7001 and 7002 are the default WebLogic Server administration ports for the dual file system with Oracle E-Business Suite Release 12.2. The examples in this section use these default ports. If you have configured different port numbers, change the port numbers in the instructions to match the port numbers for your environment.

When you create an Oracle E-Business Suite Release 12.2 environment on Oracle Cloud Infrastructure, you should create a security rule and firewall rules that allow inbound communication on the WebLogic Server administration ports on the primary application tier node. These rules are required as a prerequisite so that a system administrator can securely access the administration ports and the Fusion Middleware Control and WebLogic Server Administration Console. See Access the Fusion Middleware Control and WebLogic Server Administration Console with SSH Port Forwarding for Oracle E-Business Suite on Oracle Cloud Infrastructure.

Perform the following steps to configure the required security rule and firewall rules:

Update the security list for the primary application tier node by adding a security rule that allows inbound communication on ports 7001 and 7002. See Working with Security Lists.

In the Oracle Cloud Infrastructure console, open the security list for the Oracle E-Business Suite application tier subnet and add a new entry under Allow rules for ingress with the following properties:

Source CIDR - The CIDR block corresponding to the source machines.

Protocol - TCP

Destination Port Range - 7001-7002

Create firewall rules on the primary application tier node that allow inbound communication on ports 7001 and 7002 from the subnet that contains the source machines you would like to connect from. First, log in to the Oracle Cloud Infrastructure instance that hosts your Oracle E-Business Suite environment, using SSH. See Connecting to an Instance.

Then switch to the root user:

$ sudo su -

Run the following commands to create the required firewall rules:

# firewall-cmd --zone=public --add-rich-rule 'rule family=ipv4 source address=<source_machines_CIDR> port port=7001 protocol=tcp accept' --permanent ;

# firewall-cmd --zone=public --add-rich-rule 'rule family=ipv4 source address=<source_machines_CIDR> port port=7002 protocol=tcp accept' --permanent ;

# firewall-cmd --zone=public --add-rich-rule 'rule family=ipv4 source address=<source_machines_CIDR> port port=7001 protocol=tcp accept';

# firewall-cmd --zone=public --add-rich-rule 'rule family=ipv4 source address=<source_machines_CIDR> port port=7002 protocol=tcp accept';

4.8 Acknowledge the Secure Configuration Recommendations

Access to the environment will be restricted until the system administrator configures or acknowledges the secure configuration recommendations.

To access the Secure Configuration Console, a user must have a responsibility that includes the Applications System (OAM_APP_SYSTEM) function privilege, such as the seeded System Administration or System Administrator responsibilities, and must be registered as a local user with Oracle E-Business Suite. The administrator must log in to Oracle E-Business Suite using the local login page (http(s)://[host]:[port]/OA_HTML/AppsLocalLogin.jsp) to navigate to the console and unlock the system. If a user with local system administrator privileges is not available, you can access the Secure Configuration Console through a command line utility. For more information, see Secure Configuration Console in the Oracle E-Business Suite Security Guide.

Note: Once the system is "Unlocked" for normal usage, the Secure Configuration Console is still available for administrators under the 'Functional Administrator' responsibility.

Step 5: References

For further information about using this component as part of a larger Oracle E-Business Suite deployment, refer to the following documentation:

Oracle Cloud Infrastructure Documentation - Welcome to Oracle Cloud Infrastructure

Oracle Cloud Infrastructure Documentation - Developer Tools and Resources

Thanks,

Srini

What's AI , Genetic AI and Agentic AI introduction and key use cases - Oracle cloud

Hi All,

 Today we are going to discuss on What is AI, Genetic AI, and Agentic AI , what exact differences between these post that we can relate these topics with Oracle Cloud in our next blog posts.

High-level Diagram for Defrances: 

Firstly, what is AI (Artificial Intelligence)

Artificial Intelligence (AI) refers to the field of computer science focused on creating systems or machines that can perform tasks requiring human-like intelligence, such as learning, reasoning, problem-solving, perception, and language understanding.

 

Key Features of AI:

Learning – Through data (machine learning, deep learning).

Reasoning – Drawing conclusions from input data.

Problem-Solving – Making decisions in complex scenarios.

Perception – Recognizing images, speech, or patterns.

Natural Language Processing (NLP) – Understanding and generating human language.

 

Examples of AI:

Chatbots (like ChatGPT).

Self-driving cars (AI for decision-making and perception).

Recommendation systems (Netflix, Amazon).

Fraud detection systems etc..

 

 

 

 

 

 

 

Okay now, our  Second topic is What is Genetic AI?

Genetic AI is an AI approach inspired by the principles of genetics and natural selection (evolutionary biology). It uses Genetic Algorithms (GA) to find optimized solutions to problems by mimicking processes like mutation, crossover, and selection.

How Genetic AI Works:

Population Initialization – Create a set of random solutions (like chromosomes).

Fitness Evaluation – Evaluate how good each solution is using a fitness function.

Selection – Choose the best solutions to “reproduce”.

Crossover – Combine parts of two solutions to create new offspring.

Mutation – Randomly tweak solutions to introduce diversity.

Iteration – Repeat this process until the best solution emerges.

 

Key Features of Genetic AI:

Works on optimization problems where traditional methods fail.

Does not require gradient-based learning like neural networks.

It’s inspired by Darwin's survival of the fittest principle.

Examples of Genetic AI Use Cases:

Traveling Salesman Problem (finding the shortest route).

Neural Network Optimization (selecting architecture or weights).

Robotics (path planning) & Game strategy evolution.

 

 

The final topic is What is Agentic AI?

Agentic AI is a recent evolution of AI where an AI system acts as an autonomous “agent” capable of planning, decision-making, and taking actions in the real or digital world to achieve specific goals.

Key Characteristics of Agentic AI:

Autonomy – Can work independently without continuous human prompts.

Goal-Oriented Behavior – Plans and executes tasks to meet objectives.

Tool Usage – Can call APIs, use databases, or interact with external systems.

Memory & Reflection – Stores past experiences to improve future decisions.

Multi-step Reasoning – Breaks down complex tasks into subtasks.

Examples of Agentic AI:

AutoGPT, BabyAGI, Devin AI – AI agents that autonomously write and debug code.

Customer Service Bots – Not just answering but performing tasks like booking tickets.

AI Workflow Agents – Automating entire business processes (emailing, report generation).

The Key Differences b/w AI, Genetic AI, and Agentic AI.

AI is the umbrella term for all intelligent systems.

Genetic AI is a subfield of AI focusing on optimization through evolutionary algorithms.

Agentic AI is a new paradigm of AI where systems are autonomous, goal-driven, and capable of taking actions without human intervention.

 

Thank You , that is now .. keep learning 

Thanks,

Srini.

Oracle 19C Database Jul-2025 RU patches download and Apply process

 Dear All,

In this post i am going to share Oracle latest Jul-2025 RU patches on Oracle 19C Database and RAC Databases, will share the steps how to download and apply step by step process.

First we need to login to support.oracle.com >> patches & download >> download the below patches as showed in the snaps.

You can watch @RACSINFOTECH YouTube channel for this patch apply live process >>>>>>>>>>>>>>>>>>>

Oracle 19C Non RAC patches : 

Oracle 19C RAC or Grid Patches : 37957391

click on download it will take while and then copy to server .

meanwhile read the read me file .

Once download completed , move those patches to respective databases and apply 

Apply procedure little different between RAC and Non RAC.

> check the conflicts if any 

Opatch utility :

download latest opatch utility

Non RAC apply process : 

- download patch 

- copy to the server

- unzip the patch on database server

-check the pre-requisites like and pre-requisite patches there or not, sufficient storage is there or not, invalids, important configurations backup.

- take downtime and send communication to all.

-shutdown database and listener 

-apply patch using opatch

-startup database and listener 

-take invalids and compare before and after patch.

-run datapatch -verbose

-release the instance .

Non RAC apply process : 

- download patch 

- copy to the server

- unzip the patch on database server  ( common directory that patch should access rdbms and grid homes)

-check the pre-requisites like and pre-requisite patches there or not, sufficient storage is there or not, invalids, important configurations backup.

- take downtime and send communication to all.

-shutdown database and listener 

-shutdown grid , run rootcrs.pl prepatch ( rolling mode) node / node process

./rootcrs.pl -prepatch

-apply patch using opatchauto ( this we need to run from root user)

-this opatchauto apply the patches on grid home and rdbms homes at one go

-post patch start the grid and rdbms servers 

- ./rootcrs.pl -postpatch 

- do the above steps on all the nodes , once done run below steps .

-take invalids and compare before and after patch.

-run datapatch -verbose ( note : run only after patch completed on all the RAC nodes )

-release the instance .

You can watch @RACSINFOTECH YouTube channel for this patch apply process.

Thanks,

Srini

ADPRECLONE.PL Fails With Error 'CLONE-20435 Some of the Oracle Homes are excluded during copy operation EBS R12.2.X

 Dear All,

In this post i am sharing one of the issue which i got the recently in My EBS R12.2.10 with 19C Database issue while running adpreclone.pl got the below error .

When running  $ADMIN_SCRIPTS_HOME/adpreclone.pl on an application node, the below error occurs in $INST_TOP/admin/log/clone/fmwT2PStage/CLONEXXXXXX_XXXXX.error file:

SEVERE : <DATE&TIME> - ERROR - CLONE-20435 Some of the Oracle Homes are excluded during copy operation.

SEVERE : <DATE&TIME> - CAUSE - CLONE-20435 The following Oracle Homes were excluded during copy operation.

[/u07/EBSApps/Oracle/fs1/FMW_Home/webtier, /u07/EBSApps/Oracle/fs1/FMW_Home/oracle_common] , and possible causes were:

1. All the Oracle Homes were not registered with one OraInventory.

2. If all Oracle Homes were registered with a single custom OraInventory, then corresponding inventory pointer file was not provided to T2P operation.

3. Canonical path of Oracle Home registered with OraInventory was not child of Middleware Home.

SEVERE : <DATE&TIME> - ACTION - CLONE-20435 Make sure that all possible causes mentioned in above CAUSE section are taken care.

SEVERE : <DATE&TIME> - ERROR - CLONE-20218 Cloning is not successful.

SEVERE : <DATE&TIME> - CAUSE - CLONE-20218 An internal operation failed.

SEVERE : <DATE&TIME> - ACTION - CLONE-20218 Provide the clone log and error file for investigation.

java.lang.Exception: Some of the Oracle Homes are excluded during copy operation.

at oracle.as.clone.cloner.builder.CreateClonerBuilder.showMessageIfAnyOHIgnored(CreateClonerBuilder.java:1356)

at oracle.as.clone.cloner.builder.CreateClonerBuilder.getMWAndOHCreateClonerObjects(CreateClonerBuilder.java:226)

at oracle.as.clone.cloner.builder.CreateClonerBuilder.getCreateClonerObjects(CreateClonerBuilder.java:147)

at oracle.as.clone.cloner.builder.CreateClonerBuilder.getClonerObjects(CreateClonerBuilder.java:133)

at oracle.as.clone.process.CloningExecutionProcess.execute(CloningExecutionProcess.java:91)

at oracle.as.clone.client.CloningClient.executeT2PCommand(CloningClient.java:236)

at oracle.as.clone.client.CloningClient.main(CloningClient.java:124)

 

The below messages were also seen in the $INST_TOP/admin/log/clone/fmwT2PStage/CLONEXXXXXX_XXXXX.log file

FINE : <DATE&TIME> - [CreateClonerBuilder:isItPossibleToArchiveOracleHome] Trying to find out Oracle home properties for the Oracle home /u07/EBSApps/Oracle/fs1/FMW_Home/webtier and to check its dependency on Middleware home.

FINE : <DATE&TIME> - [OracleHomeDepRefUtil:deriveDepRefOHAndProperty] Deriving dependent Oracle home, reference Oracle home and additional properties for Oracle home /u07/EBSApps/Oracle/<INSTANCE NAME>/fs1/FMW_Home/webtier.....

FINE : <DATE&TIME> - [CreateClonerBuilder:isItPossibleToArchiveOracleHome] Oracle home is associated with Middleware home /u07/EBSApps/Oracle/fs2/FMW_Home

FINE : <DATE&TIME> - [CreateClonerBuilder:isItPossibleToArchiveOracleHome] Checking whether dependent Middleware home /u07/EBSApps/Oracle/fs2/FMW_Home is same as provided Middleware home /u07/EBSApps/Oracle/fs1/FMW_Home or not.

FINE : <DATE&TIME> - [CreateClonerBuilder:isItPossibleToArchiveOracleHome] Oracle home /u07/EBSApps/Oracle/fs1/FMW_Home/webtier has dependency on Middleware home /u07/EBSApps/Oracle/<INSTANCE NAME>/fs2/FMW_Home , but an attempt was made to archive another Middleware home /u07/EBSApps/Oracle/fs1/FMW_Home

FINE : <DATE&TIME> - [CreateClonerBuilder:createOHClonerObjects] Oracle home /u07/EBSApps/Oracle/fs1/FMW_Home/webtier is not possible to archive, adding it to invalid Oracle home list.

FINE : <DATE&TIME> - [CreateClonerBuilder:getOHCloners] Excluding Oracle home /u07/EBSApps/Oracle/fs1/FMW_Home/webtier

FINE : <DATE&TIME> - [CreateClonerBuilder:getOHCloners] All Oracle home(s) size in ascending order are = [1511235425]

INFO : <DATE&TIME> - CLONE-21038 The archive will contain both Middleware Home /u07/EBSApps/Oracle/fs1/FMW_Home and Oracle Home(s) /u07/EBSApps/Oracle/fs1/FMW_Home/Oracle_EBS-app1.

..

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

T2P Summary Begin

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

Error Message :1

<DATE&TIME> - ERROR - CLONE-20435 Some of the Oracle Homes are excluded during copy operation.

<DATE&TIME> - CAUSE - CLONE-20435 The following Oracle Homes were excluded during copy operation.

[/u07/EBSApps/Oracle/fs1/FMW_Home/webtier, /u07/EBSApps/Oracle/fs1/FMW_Home/oracle_common] , and possible causes were:

1. All the Oracle Homes were not registered with one OraInventory.

2. If all Oracle Homes were registered with a single custom OraInventory, then corresponding inventory pointer file was not provided to T2P operation.

3. Canonical path of Oracle Home registered with OraInventory was not child of Middleware Home.

<DATE&TIME> - ACTION - CLONE-20435 Make sure that all possible causes mentioned in above CAUSE section are taken care.

Cause of the issue :

The cause of this issue is incorrect details on either the central inventory, or local inventory of EBS ORACLE_HOME. 

The above error was identified with the incorrect path for the PROPERTY NAME="MIDDLEWARE_HOME" on file "<FMW_HOME>/Oracle_EBS-app1/inventory/ContentsXML/oraclehomeproperties.xml" located under the below directories:

/u07/EBSApps/Oraclefs1/FMW_Home/webtier/inventory/ContentsXML

/u07/EBSApps/Oraclefs1/FMW_Home/oracle_common/inventory/ContentsXML

The reason for checking the above two paths was identified from the error message seen on the $INST_TOP/admin/log/clone/fmwT2PStage/CLONEXXXXXX_XXXXX.error file:

SEVERE : <DATE&TIME> - CAUSE - CLONE-20435 The following Oracle Homes were excluded during copy operation.

[/u07/EBSApps/Oraclefs1/FMW_Home/webtier, /u07/EBSApps/Oraclefs1/FMW_Home/oracle_common] , and possible causes were:

Solution : 

Step 1: Take backup of the instance and the existing "<FMW_HOME>/webtier/inventory/ContentsXML/oraclehomeproperties.xml" file located under the ORACLE_HOME local inventory. 

eg: /u07/EBSApps/Oracle/fs1/FMW_Home/webtier/inventory/ContentsXML

Step : Check the path mentioned for PROPERTY NAME="MIDDLEWARE_HOME" in the file. This should point to the FMW_HOME on the same filesystem.

For example If the file is located in "<FMW_HOME>/oracle_common/inventory/ContentsXML/oraclehomeproperties.xml", then the value of PROPERTY NAME="MIDDLEWARE_HOME" should be "/u07/EBSApps/Oracle/fs1/FMW_Home"

Step 3:  If the path mentioned is incorrect, edit the file to point to correct path.

Step 4: Save the changes.

Step 5:  Rerun the failed adpreclone.pl command.

Step 6:  Confirm  adpreclone.pl command now complete successfully without error.

Note:  test these steps in a non-business critical instance where the problem can be reproduced and then migrate accordingly...

Thanks,

Srini

How to Start and Stop Oracle 13C OEM services including OEM database Serivces

 Hi All,

In this post i am going to share how to start and stop the Oracle OEM 13C services manually.

Database version : 19.27.0.0 

OEM version : 13.5C

OEL Version  : 7

Manual Method to stop OEM services :

Stop MS :

  - export OMS_HOME=/u01/app/oracle/middleware

  - /u01/app/oracle/middleware/bin/emctl stop oms -all

 

Stop Agent :

 -   export AGENT_HOME=/u01/app/oracle/agent/agent_inst

  - /u01/app/oracle/agent/agent_inst/bin/emctl stop agent

 

Stop database : 

 - sqlplus / as sysdba > shut immediate;

 - stop listener :: lsnrctl stop OEMDB

Manual Method to start OEM services :

Start Database : 

 - sqlplus / as sysdba > startup;

 - start listener :: lsnrctl start OEMDB

Start MS :

  - export OMS_HOME=/u01/app/oracle/middleware

  - /u01/app/oracle/middleware/bin/emctl start oms

Start Agent :

   - /u01/app/oracle/agent/agent_inst/bin/emctl start agent

>>> check in detailed OMS status

$OMS_HOME/bin/emctl status oms -details

>>> check repository details

$OMS_HOME/bin/emctl config oms -list_repos_details

>>>  get list of targets monitored by agent

$AGENT_HOME/bin/emctl config agent listtargets

Thanks,

Srini

SQL Troubleshooting Step By Step Lab in Oracle 19c RAC Database

 Hi All,

In this post i am sharing related to SQL Troubleshooting lab excise Step by step Process.

Firstly check the status of database services and load on the servers.

- here i am using 2 Node RAC Database , as we can see from the above snap 2 nodes database are running fine, will bit load on this server.

- Check the database status and confirmed its not a multitenant database 

- For SQL Troubleshooting Lab we can create a Table and load some data 

SQL> CREATE TABLE customer_orders (

    order_id     NUMBER,

    customer_id  NUMBER,

    order_date   DATE,

    order_amount NUMBER,

    status       VARCHAR2(10)

);

Table created.

SQL> select * from customer_orders;

no rows selected

- No data in that table , now i can load some data 

SQL> BEGIN

  FOR i IN 1 .. 500000 LOOP

  INSERT INTO customer_orders VALUES (

      i,

      MOD(i, 1000),

      SYSDATE - MOD(i, 365),

      ROUND(DBMS_RANDOM.VALUE(100, 10000)),

      CASE WHEN MOD(i, 3) = 0 THEN 'NEW'

           WHEN MOD(i, 3) = 1 THEN 'CLOSED'

           ELSE 'PENDING' END

    );

  END LOOP;

  COMMIT;

END;

 /

PL/SQL procedure successfully completed.

SQL> select count(*) from customer_orders;

  COUNT(*)

----------

    500000

- Now i have loaded 5 lakh rows of data.

- From this table we try to access the data and we can identify how much resource it consume like CPU memory and whether its taking full table scan or how we can see it.

-  this sql is insufficient.

SELECT * FROM customer_orders WHERE TO_CHAR(order_date, 'YYYY-MM-DD') = '2025-06-28' AND status = 'NEW';

- Here we can see more rows of data  , problems from this query is TO_CHAR() disables index usage , Causes Full table scan , also it leads to High CPU and I/O usage.

Now here is main point how we can troubleshoot this problematic sql .

- Generate explain Plan for this sql .

EXPLAIN PLAN FOR SELECT * FROM customer_orders WHERE TO_CHAR(order_date, 'YYYY-MM-DD') = '2025-06-28' AND status = 'NEW';

- here can see this sql is full table scan

- we can generate AWR and monitor this sql .

@$ORACLE_HOME/rdbms/admin/awrrpt.sql 

we can check the TOP sql   by Elapsed time / Buffer Gets also look for db file scattered read( sign of Full Table scan).

- Monitor the active sql's which are executing this sql will work from 19C db onwards.

SQL> SELECT sql_id, sql_text, status, elapsed_time, cpu_time

FROM v$sql_monitor WHERE status = 'EXECUTING';

 no rows selected

How to Troubleshoot the above Full table scan ? 

- From the above sql we identified problems which are

Issue 1 :  TO_CHAR() disables index usage , Causes Full table scan 

Fix for Issue 1 : 

SQL> SELECT * FROM customer_orders WHERE order_date = TO_DATE('2025-06-28', 'YYYY-MM-DD') AND status = 'NEW';

no rows selected

- Add index to that table .

SQL> CREATE INDEX idx_order_date_status ON customer_orders(order_date, status);

Index created.

- re-run the explain plan and see the output .

EXPLAIN PLAN FOR SELECT * FROM customer_orders WHERE order_date = TO_DATE('2025-06-28', 'YYYY-MM-DD') AND status = 'NEW';

Explained.

- Now its Index  range scan we avoid the full table scan . 

SQL Monitor report: should show reduced elapsed time

AWR: reduced cost/CPU/IO stats

Post Index creation You should see faster execution and lower logical reads .

SELECT * FROM customer_orders WHERE TO_CHAR(order_date, 'YYYY-MM-DD') = '2025-06-28' AND status = 'NEW';

without Index :

after index : 

Note: Generally we dont see when we used where clause with small amount of data request but in real time when we are accessing huge amount of data then we can understand clearly the power of Indexing .

Thanks ,

Srini