Loading...

Follow K21 Academy - Oracle Trainings Blog on Feedspot

Continue with Google
Continue with Facebook
or

Valid

This post covers the Oracle GoldenGate Tokens.

Oracle GoldenGate tokens are attributes to store environment variable values, which are available on the header of trail record header. Using Oracle GoldenGate built-in function @token within the parameter files retrieves the token value.

Types of Tokens:

There are two types of tokens. They are:

  1. Pre-defined token
  2. User Tokens

1. Pre-defined Tokens:

Below lists pre-defined Oracle GoldenGate tokens.

TK_HOST Stores the hostname
TK_GROUP Stores the operating system group name
TK_OSUSER Stores the operating system user name
TK_DOMAIN Stores the hostname domain
TK_COMMIT_TS Stores the current commit transaction sequence number
TK_POS Stores the current read position
TK_RBA Stores the relative byte address (RBA)
TK_TABLE Stores the table name
TK_OPTYPE Stores the operation types (INSERT, UPDATE, DELETE or DDL)

The replicat rep2202 parameter file illustrates a basic implementation of the token by associating each row with Oracle GoldenGate environment pre-defined tokens values that can be used by other applications such as auditing.

T1C1>DESC dept

Name                            Null?    Type

———————————- ——– ———

DEPT_NO                          NOT NULL NUMBER

Loc                                       NOT NULL VARCHAR2(128)

 HOST                              VARCHAR2(100)

 GG_GROUP                  VARCHAR2(100)

 OSUSER                         VARCHAR2(100)

 DOMAIN                        VARCHAR2(100)

 BA_IND                          VARCHAR2(100)

 COMMIT_TS                 VARCHAR2(100)

 POS                                   VARCHAR2(100)

 RBA                                   VARCHAR2(100)

 TABLENAME                 VARCHAR2(100)

 OPTYPE                           VARCHAR2(100)

REPLICAT rep2202

USERID ***, PASSWORD ***

MAP ggtraining1.dept, TARGET ggtraining2.dept, &

COLMAP (USEDEFAULTS,

Dept_no = dept_no,

Loc     = Loc

        host      = @TOKEN (‘TK_HOST’),

        gg_group  = @TOKEN (‘TK_GROUP’),

        osuser    = @TOKEN (‘TK_OSUSER’),

        domain    = @TOKEN (‘TK_DOMAIN’),

        ba_ind    = @TOKEN (‘TK_BA_IND’),

        commit_ts = @TOKEN (‘TK_COMMIT_TS’),

        pos       = @TOKEN (‘TK_POS’),

        rba       = @TOKEN (‘TK_RBA’),

        tablename = @TOKEN (‘TK_TABLE’),

        optype    = @TOKEN (‘TK_OPTYPE’));

2. User Defined Tokens:

These are defined on the source system and moved to the target system for event handling, providing an extendibility for attributes that are not pre-defined by Oracle GoldenGate. Tokens are a way to capture and store data in the header of the trail file.  Once a token has been defined, captured and stored in the header, it can be retrieved, on the apply side, and used in many ways to customize what information is delivered by Oracle GoldenGate.

Follow the below steps to define the token:

  1. You define the token and the associated data.
  2. The token header in the trail file header permits up to a total of 2,000 bytes (token name, associated data, and length of data)
  3. Use the TOKEN option of the TABLE parameter in Extracts

Token data may be used in the COLMAP clause of a Replicat MAP statement, within an SQLEXEC, a UserExit, or a Macro. To retrieve the token data from the Oracle GoldenGate Trail, use the Column Conversion Function @TOKEN as input to any of the previously mentioned parameters.

In order to define a token in an extract, the definition should follow this basic syntax:

Extract ext2202

Userid ***,password ***

TRANLOGOPTIONS INTEGRATEDPARAMS(MAX_SGA_SIZE 1024)

Exttrail /ogg/dirdat/lt

TABLE ggtraining1.dept, TOKENS( SRC_CSN_TS = @GETENV(‘GGHEADER’,’COMMITTIMESTAMP’));

In the example above, the token will be populated with the timestamp of the last commit on the table it is defined against.  After restarting the extract, the token (SRC_CSN_TS) will be included in the header of the trail file.

Once the trail file is shipped to the target side and read by the replicat, the token is mapped to a column in the target table.

MAP ggtraining1.dept, target ggtraining2.dept,

COLMAP (USEDEFAULTS,

SRC_CSN_TS=@token(’SRC_CSN_TS’)

);

Tokens are simple to create, use, and are a powerful feature for mapping data between environments.

Related/Further Reading:

This post is from our Oracle GoldenGate 12c Administration Training, in which we cover the Architecture, Installation, Configuring & Preparing the Environment, DML Replication – Online Change Synchronization, Initial Load, Zero Downtime Migration & Upgrading using GoldenGate, Oracle GoldenGate Security, Performance of Oracle GoldenGate and Troubleshooting and much more.

Did you Register for the FREE GoldenGate Masterclass?

NO? So, your next task is to get yourself registered for our FREE Masterclass on Learn Oracle GoldenGate 12c for Replication & Migration to start your GoldenGate journey. Click on the image below to register for FREE.

Have a question related to Oracle GoldenGate? If YES, post them in comments below.

The post Oracle GoldenGate Tokens appeared first on Oracle Trainings.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

This post covers one of the Q/As asked in our DBA To Cloud DBA Training live session  (for free masterclass register herethat how IP Address Space Allocation In 1-node or 2-node RAC  In compute /bare metal DB system in Oracle Cloud Infrastructure (OCI)

In generic 1-node Oracle database is a single database instance working for your application &  RAC (Real Application Cluster) is (more than one node )multiple databases instances supporting your application at the same time & Oracle RAC (Real Application Cluster) provides high availability and scalability for Oracle Database. To know more about RAC In Cloud check here

Keys Point About RAC In Cloud (OCI)
  • In Oracle Cloud Infrastructure User-Managed Database can be created on 1)Virtual Machine 2)Bare Metal &  3)Exadata. 2-node. You can create a RAC database either on VM based DB System & Exadata based DB System. Note: RAC is not supported in Bare Metal DB System
  • Database editions supported in Oracle Cloud Infrastructure are 1)Standard Edition 2)Enterprise Edition 3)Enterprise Edition – High Performance 4)Enterprise Edition – Extreme Performance & only Enterprise Edition – Extreme Performance supports  2-node RAC DB systems.
  • You can set up the maximum of  2-node RAC in VM DB System
  • You can set up a maximum of 8-node RAC in Exadata DB System
  • When you provision a 2-node RAC DB systems, the system assigns each node to a different fault domain. To know about fault domain check here
Creating RAC Database on Oracle Cloud Infrastructure (OCI)

To create a 2-node DB System in Oracle Cloud Infrastructure (OCI), go to the cloud console and click on launch DB System then under Total Node Count select 2 & Oracle Database Software Edition should be Enterprise Edition – Extreme Performance.

To know the complete the process of Creating DB System in Oracle Cloud Infrastructure check here

IP Address Space Allocation In 1-node or 2-node RAC DB system In OCI

When you create DB System in Oracle Cloud Infrastructure, the very first thing you need to create Virtual Cloud Network and within that network, you create subnets which can be either public or private based on your requirement, so while creating subnets you need to have clarity that what  will be your CIDR range you should give & how many IP’s are required  if you are creating either 1-node or 2-node RAC  In compute /bare metal DB system in Oracle Cloud Infrastructure.

To know more about various Networking Components such as VCN, Subnet (Public /Private), CIDR, IGW, DRG, etc check here

1-Node Bare Metal or Virtual Machine DB System

Below is the complete IP address allocation for 1-node DB System.

  • 1 IP for Client Request
  • 3 IP’s are reserved for Subnet
  • Minimum Subnet CIDR range we should define when we creating 1-Node Bare Metal or Virtual Machine DB System will be /30 ie  equivalent to 4 IP’s
2-Node RAC Virtual Machine

Note: If you are creating DB System In either in VM or Compute in Oracle Cloud Infrastructure, 2-Node RAC is only supported in Virtual Machine DB System. To know more about Database Offerings in Oracle Cloud Infrastructure check here

Below is the complete IP address allocation for 2-node DB System.

  • 4 IPs for Database host  1 IP per node for Client Request, 1 IP per node for Private InterConnect
    3 IPs for SCAN listener
  • 3 IP’s are reserved for Subnet
  • Minimum Subnet CIDR range we should define when we creating 2-Node Virtual Machine DB System will be /28 ie equivalent to 16 IP’s.

Note: Best Practices says always use the larger CIDR value for you subnet as once subnet is created you cannot change the CIDR value.

Hope you find this useful and have a clear understanding of IP Addresses allocation in 1 -node & 2-node DB System in Oracle Cloud Infrastructure.

Stay tuned for my upcoming blogs in Database in OCI

Related/Further Readings

If you want to take your career to the next level by becoming DBA To Cloud DBA even if you are a beginner, then I would like to invite you to Join my FREE Masterclass on DBA To Cloud DBA: What, Why & How to Learn.

Click on the image below to register for Free MasterClass.

The post [QA] RAC Database On Oracle Cloud (OCI) IP Address Requirement appeared first on Oracle Trainings.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

In this post, we are going to cover the issue and fix that one of our trainees were facing while Installing Oracle EBS R12.1. They were getting this error RW-50016: Error: – {0} was not created:

The following error occurs during the post-install check don’t worry we have got you covered in this blog.

RW-50016: FNDWRR.exe

Issue:

The following error occurs during the post-install check:

If you click on the cross before the Login Page you will get this error.

  checking URL = http://<hostname>.<domainname>:<port>/OA_CGI/FNDWRR.exe

  RW-50016: Error: - {0} was not created:
  File = {1}

Symptoms:

If you HTTP is not validated, then other install checks after, HTTP will also fail as they depend on HTTP for their functionality.

For this let’s check the status of Apache Web Server Listener go to scripts home and then check the status of adapcctl.sh.

Using applmgr user run the following command:

  1. cd $ADMIN_SCRIPTS_HOME
  2. adapcctl.sh status

You will find that the HTTP_Server is down.

RW-50015 Error HTTP Listener

Cause:

This error is Cause due to a missing library (/usr/lib/libdb.so.2).

Solution:

For this, open a new terminal and go to your scripts home.

    1. cd $ADMIN_SCRIPTS_HOME
    2. ./adstpall.sh apps/apps (Shut all application services)
    3. Create the below link for library file
    4. ln -s   /usr/lib/libgdbm.so.2.0.0  /usr/lib/libdb.so.2
    5. ./adstrtal.sh apps/apps (Startup all application services)
    6. Now press the Retry button.

      RW-50015 Error HTTP Listener

    7. You will find that all the Validation check completed successfully.

Now check the Apache Web Server Listener and you will find that all the Web server listener is up and running.

Using applmgr user run the following command:

  1. cd $ADMIN_SCRIPTS_HOME
  2. adapcctl.sh status

RW-50015 Error HTTP Listener

You will find that the HTTP_Server is Alive.

Please share this Blog with your friends/Colleagues and stay tuned for our upcoming blogs.

Related/Further Readings

This post is from our Oracle Apps DBA (R12.2) Training, in which we cover  Architecture & Changes in Oracle E-Business Suite R12.2, Staging & Installation, File System & Important Files in R12.2, Start/Stop, Patching, AD Administration, Cloning, Concurrent Managers, AutoConfig, Password Management and Troubleshooting and much more

Next task for you

Want to Know More about R12.2? Click on the image below, and get your FREE Guide 6 Docs Every Oracle Apps DBA Must Read for R12.2

The post [Solved] RW-50016: Error: – {0} Not Created During EBS R12.1 Installation appeared first on Oracle Trainings.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

This post covers an Error encountered while Deploying EBS Cloud Manager 19.1.1 as part of our Hands-On-Lab Exercise for Module 4 (Provision EBS Using EBS Cloud Manager Tool) from our training Build, Manage & Migrate EBS (R12) On Oracle Cloud (OCI) (for free masterclass register here)  and the workaround used.

Error: 
Oci_core_route_table. demoEBSCM_apps_route_table: Service error:NotAuthorizedOrNotFound. Authorization failed or requested resource not found.. http status code: 404
Oci_core_security_list. demoEBSCM_apps_seclist: Service error:NotAuthorizedOrNotFound. Authorization failed or requested resource not found.. http status code: 404

The issue we have faced While performing the steps to Create the Network for the Oracle EBS  Environments while running below script:

 perl ProvisionOCINetwork.pl

Before the Oracle E-Business Suite Cloud Manager can be used to provision environments, a network and associated network profiles must be created. This Script creates two Profiles, one for One-Click Provisioning & another for Advance Provisioning & all the network resources (Subnet, Route Table, Security List) for these profiles.

Before moving into the Issue & its workaround, Lets first understand what is EBS Cloud Manager

What is EBS Cloud Manager?

As an Oracle Apps DBA, EBS Architect, it is important for you to know about EBS Cloud Manager.

EBS CLoud Manager is a Tool (Virtual Machine) that centrally manages all your EBS Environments on the cloud.
Using EBS Cloud Manager you can do:

  • Environment Deployment
  • One-Click provisioning with pre-populated deployment options (Single Node, Demo)
  • Advanced provisioning with user-selected deployment options
  • Lift and Shift Migration to OCI from on-premises backup
  • Lifecycle management
  • Clone the environment
  • Delete the environment
  • Separation of Duties: Multiple Compartment, groups, and Network Profiles
  • Backup & Recovery
  • TDE for Compute DB instance
  • More use cases in pipeline like Adding additional node, HA & DR

if you are working on Oracle E-Bussiness Suite R12 it is important for you to know how Oracle EBS is Deployed on Oracle Cloud Infrastructure (OCI) check here

Separation of Duties in EBS Cloud Manager

As we all know now in 19.1.1 concept of Compartment is implemented broadly and with the same Segregation of Duties with various administrators can be achieved.

With the latest release (19.1.1) Oracle has introduced a Separation of Duties, which means you have 3 different roles, you will define the appropriate privileges & permissions & then the responsible team will pick the task accordingly

Note: To know more about EBS Cloud Manager: New Release 19.1.1 Separation Of Duties, click here

So during the Setup, we have created 3 users

  • Network Administrator (network.admin)- One who manages all network resources and components in network components
  • Cloud Manager Administrator (ebscm.admin)– One who manages Cloud Manager and maintain it.
  • EBS Administrator (ebstest.admin)– One who manages EBS instances on Cloud Manager.
Policy Creation

Now when we go during the setup we create policies as per the role so we give privileges to the Network Administrator for creating Network resources in Network Compartment and other users will have only privileges to use these resources and not to alter or create a new one.

Let’s understand about Policy

What is Policy? 

A policy specifies who can access which Oracle Cloud Infrastructure Resources (Compute, VCN, Object Storage, Database, etc). A policy allows a group to work in certain ways with specific types of resources under a particular compartment

  • Policies are comprised of one or more statements.
  • It specifies which groups can access, what resources. Also, it plays a role in the level of access users have in a particular group.
  • Policy, attached to a group defines who can access what under a Tenancy or Compartment.
ISSUE While performing the steps to Create the Network for the Oracle EBS Environments

Once we complete the setup then towards the end we need to create Network resources in Network compartment for deploying Oracle EBS instances.

We need to run the script for the same:

It takes parameter:

  • Enter tenancy ocid: ocid1.tenancy.oc1..aaaaaaaas6bozx6wkz6a3zy4cniva7jxgxh7eybvvvpdtytakm5qvrln72aq
  • Enter region: eu-frankfurt-1
  • Enter user ocid: ocid1.user.oc1..aaaaaaaaawqh3kwaxwxoo2zb53u2fl33alg5uf4qyqf7y2wvuwl4gloxzcsq
  • Enter fingerprint of the public key: aa:b3:59:43:dc:a7:15:c8:38:f0:bc:da:83:d0:94:e8
  • Enter absolute path of private key of API signing key: /u01/install/APPS/.oci/oci_api_key.pem
  • Enter unique identifier for the EBS network: ebsdemo
  • Enter network compartment ocid: ocid1.compartment.oc1..aaaaaaaa7mduvobj3s6z7wdskw3jyquxbjru6pxqgttxj4rqarmvhksg5jha

Now when we give all the required details at the end it says :

Oci_core_security_list. demoEBSCM_apps_seclist: Service error:NotAuthorizedOrNotFound. Authorization failed or requested resource not found.. http status code: 404 CAUSE

If we analyze the error it means that EBS Cloud Admin user will not be able to create Network resource because it has got privilege only to Use and not to Create.

ISSUE 2

Looking at that when we used network admin user as the creation of network resources is Network administrator responsibility so we use OCID of network user but with that, the network compartment was not recognized at all and it leads to below issue:

Workaround

So as a workaround we added one rule in the policy which gives privileges to manage the network resource to ebscm.admin user (Cloud manager user).

And thus when we ran the Network Provisioning script it went successful.

Well, this is the workaround as it allows the Cloud Manager Administrator to create Network components and thus breaches the Separation of Duties concept which got introduces.

We are in touch with the Oracle for getting the solution for the same and also we are trying and investigating on the same from our side to get this resolved.

But definitely, Compartment concept introduced by Oracle is going to help organizations to execute the tasks in a smoother and secure way. Compartment being logical concepts gives physical imprint on EBS Cloud Manager.

Related/References Next Task For You

If you are an Oracle Apps DBA and just starting out your journey to Oracle public Cloud then we highly recommend you to download our FREE Guide that contains 7 Things Every Oracle Apps DBA & Architect Must Know To Build & Manage EBS (R12) On Cloud in order to Manage & Migrate Oracle EBS R12 on Oracle Cloud.

Click on below image to get the FREE Guide.

The post [Troubleshooting] EBS Cloud Manager 19.1.1 Deployment Issue because of IAM Policy/Compartment: ProvisionOCINetwork.pl appeared first on Oracle Trainings.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

This post covers an Error encountered while Deploying EBS Cloud Manager 19.1.1 as part of our Hands-On-Lab Exercise for Module 4 (Provision EBS Using EBS Cloud Manager Tool) from our training Build, Manage & Migrate EBS (R12) On Oracle Cloud (OCI) (for free masterclass register here)  and the workaround used.

Error: 
Oci_core_route_table. demoEBSCM_apps_route_table: Service error:NotAuthorizedOrNotFound. Authorization failed or requested resource not found.. http status code: 404
Oci_core_security_list. demoEBSCM_apps_seclist: Service error:NotAuthorizedOrNotFound. Authorization failed or requested resource not found.. http status code: 404

The issue we have faced While performing the steps to Create the Network for the Oracle EBS  Environments while running below script:

 perl ProvisionOCINetwork.pl

Before the Oracle E-Business Suite Cloud Manager can be used to provision environments, a network and associated network profiles must be created. This Script creates two Profiles, one for One-Click Provisioning & another for Advance Provisioning & all the network resources (Subnet, Route Table, Security List) for these profiles.

Before moving into the Issue & its workaround, Lets first understand what is EBS Cloud Manager

What is EBS Cloud Manager?

As an Oracle Apps DBA, EBS Architect, it is important for you to know about EBS Cloud Manager.

EBS CLoud Manager is a Tool (Virtual Machine) that centrally manages all your EBS Environments on the cloud.
Using EBS Cloud Manager you can do:

  • Environment Deployment
  • One-Click provisioning with pre-populated deployment options (Single Node, Demo)
  • Advanced provisioning with user-selected deployment options
  • Lift and Shift Migration to OCI from on-premises backup
  • Lifecycle management
  • Clone the environment
  • Delete the environment
  • Separation of Duties: Multiple Compartment, groups, and Network Profiles
  • Backup & Recovery
  • TDE for Compute DB instance
  • More use cases in pipeline like Adding additional node, HA & DR

if you are working on Oracle E-Bussiness Suite R12 it is important for you to know how Oracle EBS is Deployed on Oracle Cloud Infrastructure (OCI) check here

Separation of Duties in EBS Cloud Manager

As we all know now in 19.1.1 concept of Compartment is implemented broadly and with the same Segregation of Duties with various administrators can be achieved.

With the latest release (19.1.1) Oracle has introduced a Separation of Duties, which means you have 3 different roles, you will define the appropriate privileges & permissions & then the responsible team will pick the task accordingly

Note: To know more about EBS Cloud Manager: New Release 19.1.1 Separation Of Duties, click here

So during the Setup, we have created 3 users

  • Network Administrator (network.admin)- One who manages all network resources and components in network components
  • Cloud Manager Administrator (ebscm.admin)– One who manages Cloud Manager and maintain it.
  • EBS Administrator (ebstest.admin)– One who manages EBS instances on Cloud Manager.
Policy Creation

Now when we go during the setup we create policies as per the role so we give privileges to the Network Administrator for creating Network resources in Network Compartment and other users will have only privileges to use these resources and not to alter or create a new one.

Let’s understand about Policy

What is Policy? 

A policy specifies who can access which Oracle Cloud Infrastructure Resources (Compute, VCN, Object Storage, Database, etc). A policy allows a group to work in certain ways with specific types of resources under a particular compartment

  • Policies are comprised of one or more statements.
  • It specifies which groups can access, what resources. Also, it plays a role in the level of access users have in a particular group.
  • Policy, attached to a group defines who can access what under a Tenancy or Compartment.
ISSUE While performing the steps to Create the Network for the Oracle EBS Environments

Once we complete the setup then towards the end we need to create Network resources in Network compartment for deploying Oracle EBS instances.

We need to run the script for the same:

It takes parameter:

  • Enter tenancy ocid: ocid1.tenancy.oc1..aaaaaaaas6bozx6wkz6a3zy4cniva7jxgxh7eybvvvpdtytakm5qvrln72aq
  • Enter region: eu-frankfurt-1
  • Enter user ocid: ocid1.user.oc1..aaaaaaaaawqh3kwaxwxoo2zb53u2fl33alg5uf4qyqf7y2wvuwl4gloxzcsq
  • Enter fingerprint of the public key: aa:b3:59:43:dc:a7:15:c8:38:f0:bc:da:83:d0:94:e8
  • Enter absolute path of private key of API signing key: /u01/install/APPS/.oci/oci_api_key.pem
  • Enter unique identifier for the EBS network: ebsdemo
  • Enter network compartment ocid: ocid1.compartment.oc1..aaaaaaaa7mduvobj3s6z7wdskw3jyquxbjru6pxqgttxj4rqarmvhksg5jha

Now when we give all the required details at the end it says :

Oci_core_security_list. demoEBSCM_apps_seclist: Service error:NotAuthorizedOrNotFound. Authorization failed or requested resource not found.. http status code: 404 CAUSE

If we analyze the error it means that EBS Cloud Admin user will not be able to create Network resource because it has got privilege only to Use and not to Create.

ISSUE 2

Looking at that when we used network admin user as the creation of network resources is Network administrator responsibility so we use OCID of network user but with that, the network compartment was not recognized at all and it leads to below issue:

Workaround

So as a workaround we added one rule in the policy which gives privileges to manage the network resource to ebscm.admin user (Cloud manager user).

And thus when we ran the Network Provisioning script it went successful.

Well, this is the workaround as it allows the Cloud Manager Administrator to create Network components and thus breaches the Separation of Duties concept which got introduces.

We are in touch with the Oracle for getting the solution for the same and also we are trying and investigating on the same from our side to get this resolved.

But definitely, Compartment concept introduced by Oracle is going to help organizations to execute the tasks in a smoother and secure way. Compartment being logical concepts gives physical imprint on EBS Cloud Manager.

Related/References Next Task For You

If you are an Oracle Apps DBA and just starting out your journey to Oracle public Cloud then we highly recommend you to download our FREE Guide that contains 7 Things Every Oracle Apps DBA & Architect Must Know To Build & Manage EBS (R12) On Cloud in order to Manage & Migrate Oracle EBS R12 on Oracle Cloud.

Click on below image to get the FREE Guide.

The post [Troubleshooting] EBS Cloud Manager 19.1.1 Deployment Issue because of IAM Policy/Compartment: ProvisionOCINetwork.pl appeared first on Oracle Trainings.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

If you are running your workload Oracle Cloud (Compute, Databases), read this complete blog and apply the patches as recommended.

Recently Intel has identified a Vulnerability in their processors which they named as Microarchitectural Data Sampling (MDS) Vulnerability and due to which Intel CPUs may allow information disclosure and one can easily enter your system by using some malicious codes.

This post covers things you must know about Microarchitectural Data Sampling (MDS) Vulnerability & what Oracle Recommends to mitigate this.

What is Microarchitectural Data Sampling (MDS) Vulnerability?

It is referred to as Microarchitectural Data Sampling issues (MDS issues) because they refer to issues related to microarchitectural structures of the Intel processors other than the level 1 data cache and one can easily run some malicious code against these and can enter your system and Intel has rated this Vulnerability as severity medium.

These vulnerabilities have received the following CVE identifiers, where CVE stands for The Common Vulnerabilities and Exposures (CVE) system provides a reference-method for publicly known information security vulnerabilities and exposures

  • CVE-2019-11091: Microarchitectural Data Sampling Uncacheable Memory (MDSUM)
  • CVE-2018-12126: Microarchitectural Store Buffer Data Sampling (MSBDS)
  • CVE-2018-12127: Microarchitectural Load Port Data Sampling (MLPDS)
  • CVE-2018-12130: Microarchitectural Fill Buffer Data Sampling (MFBDS)

Where vulnerability CVE-2019-11091 has received a CVSS Base Score of 3.8, the other vulnerabilities have all been rated with a CVSS Base Score of 6.5.  Where CVSS stands for Common Vulnerability Scoring System

Oracle Recommendation to Intel Microarchitectural Data Sampling (MDS) Vulnerabilities Oracle Hardware
  • Oracle suggests the administrators of x86-based Systems to carefully analyze the impact of MDS on their system, and accordingly implement all the security mitigations such as applying OS patches released for these vulnerabilities.
  • If you are using Oracle Engineered System such as Exadata Machine, Database Appliance, SuperCluster, etc Oracle will give you the specific guidance.
Oracle Operating Systems (Linux and Solaris) and Virtualization
  • If you are using  Oracle Linux 7, Oracle Linux 6, &  Oracle VM Server for X86 Products you should immediately apply the OS patches released by Oracle for this Vulnerabilities, in addition to that you should also run the current version of the Intel microcode to mitigate these issues (#  yum update microcode_ctl ).
  • The required versions of microcode_ctl rpms are Oracle Linux 7: microcode_ctl 2.1-47.0.4 & Oracle Linux 6: microcode_ctl 1.17-1002
  • For Oracle Linux customer you can use Oracle Ksplice tool to patch the OS with zero downtime. To know more check here
  • If you are using Oracle Solaris on x86 then it is affected by these vulnerabilities. For more information check  Doc ID 2540621.1 
  • If you are running your workload on Oracle Solaris on  SPARC, then no action required from your end, as it is not affected by this Vulnerabilities.
Oracle Cloud
  • If you are using Oracle Autonomous Database (ATP & ADW) then no action required for this Vulnerabilities. To know more about Autonomous Database check here
  • If you are using Bare Metal Instances and using your own virtualization stack on top of it then you should review the Intel recommendations about these MDS vulnerabilities and make the recommended changes to their configurations.
  • If you are using VM Instances, then you should patch OS to the latest security patch released by Oracle. To know how to patch please check here
  • For Zero Downtime Patching in Oracle Cloud, you can use Oracle Ksplice only available for Oracle Linux Images, to know how to configure check  here
  • Note: If you are using third party OS, then you should reach out to them for these vulnerabilities patches.
  • If you are running your DB System on Virtual Machine or Bare Metal, you should apply the latest OS Patches, to know how to apply  the OS patch to DB System check here
  • For Exadata DB systems, apply the OS patches following the instructions in Updating an Exadata DB System.
  • If you are using Oracle Cloud Infrastructure Classic and Oracle Platform Service on Oracle Cloud Infrastructure Classic then Oracle will be performing mandatory maintenance for Infrastructure and Platform Services on Oracle Cloud Infrastructure Classic, so no action required from customer ends.

Hope you find this blog useful and make sure you update and apply all the security patches as recommended in order to mitigate this Microarchitectural Data Sampling (MDS) Vulnerabilities and comment in the blog & let us if you have any query regarding this Vulnerabilities.

References Related/Further Readings

If you want to take your career to next level by becoming Oracle Certified Cloud Architect even if you are a beginner then I would like to invite you to Join my FREE Masterclass on How To Become Oracle Certified Cloud Architect [1Z0-932] in 8 Weeks

Click on the image below to register for Free MasterClass

The post Intel Microarchitectural Data Sampling (MDS) Vulnerabilities & Its Mitigation in Oracle Cloud appeared first on Oracle Trainings.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

This post covers one of the most common questions we get from trainees in our  Build, Manage & Migrate EBS (R12) On Oracle Gen2 Cloud (OCI) Training (To register for our FREE Master Class, Click here) that is “Can we use Oracle Goldengate tool to migrate EBS to Oracle cloud infrastructure (OCI)?”

Oracle GoldenGate Overview:

Before coming to the question, let me first tell you what is Goldengate. Oracle GoldenGate (OGG) provides near real-time transactional data replication. Replication may be uni-directional, bi-directional or multi-dimensional. For more information, check our blog here.

EBS (R12) Migration on Cloud Overview:

You can migrate EBS(R12) on Cloud using Cloud Manager tool. This tool can be used to Create, Manage, Configure Oracle application on Oracle Cloud (OCI) (To know more about this tool, Click here). After setting all the pre-requisites, you have to run EBSCloudBackup.pl script from Clone utility to backup your EBS (R12) instance to Cloud and then you can provision EBS on Cloud using that backup. But in this method, little downtime will be required. As we can use Oracle Goldengate to migrate the normal database without downtime so can this be possible in case of EBS on Cloud migration as well? We will discuss this query in our post further.

To know more about cloud migrations, check our below blog posts.

So let’s now proceed with the Query.

Que. Can we use Oracle Golden gate tool to migrate E-Business Suite (EBS) to Oracle Cloud infrastructure (OCI)?

Ans. No, Oracle GoldenGate does not currently support the replication of all of the datatypes that are used by the E-Business Suite (EBS). EBS uses Oracle Advanced Queues, which under metadata tables use the ANYDATA data type. This particular data type is not currently supported by Oracle GoldenGate.  As all data types are not supported by Golden gate for EBS migration so we cannot use it.

Then what are the other options to migrate EBS (R12) to Cloud??

1) If your EBS is platform compatible then you can do lift and shift directly using Cloud Manager Tool. To know more check here. But in this case, little downtime will be required. In this manual process, you need to follow below steps:

  • Create Target resources in the Cloud.
  • Clone the Database and Application,
  • Prepare and transfer to the cloud
  • Create and Configure in DB tier and Application Tier in Cloud.

2) If your EBS is on a different platform then you first need to do platform migration and then you can perform the lift and shift directly. You can follow the below Doc IDs from Oracle.

  • Oracle E-Business Suite Upgrades and Platform Migration (My Oracle Support Note 1377213.1)
  • For EBS 12.1 Platform migration, follow Doc ID 2473448.1
  • For EBS 12.2 Platform migration, follow Doc ID 2473449.1

3) If you don’t want any downtime then you can use Dataguard (For now, only compatible with compute systems, not with DB systems). To do the same, you first need to provision compute image on the cloud and then configure dataguard. When you are ready to migrate then switchover which will avoid downtime.

This post is from our Course “Build, Manage & Migrate EBS (R12) On Oracle Cloud (OCI)” where we are using compute to build & manage EBS on Cloud and cover lots of advanced topics as well like Cloning, Backup and Restore, Lift and shift, Troubleshooting, etc.

References:
  1. GoldenGate 12c Certified with E-Business Suite 12.2
  2. Check Deploying Oracle GoldenGate to Achieve Operational Reporting for Oracle E-Business Suite (Doc ID 1112325.1)
  3. Using Oracle GoldenGate to Replicate Data from Oracle E-Business Suite 12.2 (Doc ID 2004495.1)
  4. Low Downtime E-Business Suite Migrations using Oracle GoldenGate
Related Posts: Next Task For You

If you are an Oracle Apps DBA and just starting out your journey to Oracle public Cloud then we highly recommend you to download our FREE Guide that contains 7 Things Every Oracle Apps DBA & Architect Must Know To Build & Manage EBS (R12) On Cloud in order to Manage & Migrate Oracle EBS R12 on Oracle Cloud.

Click on below image to get the FREE Guide.

The post [Q/A] EBS (R12) on OCI : Is Goldengate certified for EBS migration to Cloud?? appeared first on Oracle Trainings.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

This Post Covers javax.net.ssl.SSLHandshakeException PKIX path building failed error while running schedule job IDCS Group Lookup Reconciliation as a part of Oracle Identity Manager (OIM)/Oracle Identity Governance (OIG), Integration with Oracle Identity Cloud Service (IDCS).

Error: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.

If you are new to Secure Socket Layer (SSL), then I would suggest you check our previous post where we have covered in detail.

  • SSL in WebLogic (CA, KeyStore, Identity & Trust Store) : Things you must know – Part I Click Here
  • SSL in WebLogic Server – Part II : Create KeyStore, generate CSR, Import CERT and configure KeyStore with WebLogic Click Here

If you want to know more about Oracle Identity Cloud Service (IDCS) check our previous post where we have covered in detail about Oracle Identity Cloud Serve ice (IDCS) Overview & Concepts 

Issue: 

Oracle Identity Manager (OIM) was integrated with Identity Cloud Service (IDCS) using the OIM IDCS connector.

While Running schedule job IDCS Group Lookup Reconciliation fails with javax.net.ssl.SSLHandshakeException: PKIX path building failed error:

Log Filename = $DOMAIN_HOME/servers/oim_server1/logs/oim_server1-diagnostic.log.

————————————————–

Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1884)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:276)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:270)
at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1341)
at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:153)
at sun.security.ssl.Handshaker.processLoop(Handshaker.java:868)
at sun.security.ssl.Handshaker.process_record(Handshaker.java:804)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1016)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1312)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1339)

at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:290)
at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:259)
at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:125)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:319)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:385)
at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:230)
at sun.security.validator.Validator.validate(Validator.java:260)
at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:326)
at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:231)
at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:126)
at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1323)
… 155 more

Root Cause:

The OIM/OIG and Oracle Identity Cloud Service (IDCS) integration is performed only using an encrypted protocol (HTTPS). This type of communication requires that the Oracle Identity Cloud Service certificate is available in the OIM server trust store.

Whenever OIM Server attempts to connect to Oracle Identity Cloud Service (Target system),  it will only be able to connect to IDCS if it can trust it. The way trust is handled in the OIM Server is when you have Imported IDCS SSL Certificate in OIM and OIM JDK TrustStore Respectively.

OIM JDK TrustStore location: $JAVA_HOME/lib/security/cacerts

OIM Server TrustStore Location:  $WL_HOME/server/lib/DemoTrust.jks

This contains a list of all known Certificate Authority (CA) certificates, and OIM Server will only trust certificates that are signed by one of those CAs or public certificates that exist within that keystore.

These certificates combined are referred to as the certificate chain, and, as they are all within the OIM Server Truststore (DemoTrust.jks) and  OIM JDK Truststore (cacerts) OIM Server will trust any certificates signed by them (in this case, *.identoty.oraclecloud.com).

This problem is therefore caused by a certificate that is self-signed (a CA did not sign it) or a certificate chain that does not exist within the OIM Server TrustStore. OIM Server did not trust the certificate and fails to connect to the Oracle Identity Cloud Service (IDCS).

Troubleshooting:

You export the Oracle Identity Cloud Service HTTPS public certificate and import the same into the OIM trust store and make sure Enable SSL as “True” in IDCS IT Resource Parameter.

HighLevel Steps to export HTTP public certificate & Import them into OIM TrustStore:
  1. Export the HTTPS public certificate (IDCS Public certificate)
  2. Then, Check where to import OIM Trust Store
  3. After checking location, Import IDCS Public Certificate into OIM Trust Store
  4. Enable SSL as “True” in IDCS IT Resource Parameter
  5. Testing
1. How to Export the IDCS HTTPS public certificate:

In this section, you have to access the IDCS Service Console URL and export the HTTPs Public certificates.

  • Access the Oracle Identity Cloud Service UI in Firefox Browser
  • In the address bar, click the lock icon, click Connection>, and then click More Information.

  • Click View Certificate.

  • Click Details and then click Export

  • Select X.509 Certificate (PEM) as type and save the certificate file. Default name of this certificate is -identityoraclecloudcom , change it with idcs.cer
  • Transfer that certificate in the OIM Server under /tmp
  • Next, you need to import the IDCS certificates into the OIM trust store.
2. How to check Identity and Trust Keystore location into OIM
  • Login to WebLogic console http://<hostname>:7001/console and Go to -> Servers->OIM Managed Server (oim_server1)

  • Click on Configuration->keystores (This page let you view and define Identity & Trust keystore configurations)

3. How to import the IDCS HTTPS public certificate into the OIM trust store: 

After exporting the IDCS HTTPs Public Certificates, you have to import them into the OIM Server and OIM JDK trust store.

  • Launch the OIM server terminal and enter the following command to import the certificate into the OIM JDK trust store. (use root user else you will hit error permission denied at the end )

keytool -import -keystore $JAVA_HOME/jre/lib/security/cacerts -file /tmp/idcs.cer -storepass changeit -alias idcs

Click yesThe keytool utility should display the message Certificate was added to keystore.

  • Now, import the certificate into the OIM Server trust store:

keytool -import -keystore $WL_HOME/server/lib/DemoTrust.jks -file /tmp/idcs.cer -storepass DemoTrustKeyStorePassPhrase -alias idcs

  • When prompted, enter yes.

The keytool utility should display the message Certificate was added to keystore.

4.  How to Enable SSL as “True” in IDCS IT Resource Parameter

IDCS always expects SSL communication, so sslEnabled must be set on “true” in the IDCS IT Resource.

  • login to Identity System Administration Console http://<hostname>:14000/syadmin and Go to IT Resource -> Edit -> IDCS IT resource

  • Edit IT Resource Details and Parameters and add sslEnables as “True

  • View IT Resource Details and Parameters and Confirm details

Testing:

We could successfully run the Scheduled jobs in OIM/OIG.

This post is from our Oracle Identity Cloud Service (IDCS) training in which we have covered everything one should know about Oracle Identity Cloud Service like ArchitectureUsers & Groups Application, Branding, Auditing & Reports, Rest APIs, Adaptive security and much more.

Interested? Register for Free Master Class on Cloud Security Using Oracle IDCSCareer Path & What to Learn? 

Related Posts
  • Cloud Security With Oracle Identity Cloud Service (IDCS) Click here
  • Oracle Identity Cloud Service (IDCS): Step By Step Lab Activity Guide for Beginners Click here
  • Oracle Identity Cloud Service (IDCS) Overview & Concepts Click here
  • Cloud Security Using Identity Cloud Service Click here
  • Oracle Identity Cloud Service: Configuring Multi-Factor Authentication (MFA) Click here
  • High-level Steps to Protecting an On-premises Application with IDCS by Using WebGate Click Here
  • OIM/OIG – IDCS Connector Integration : [Troubleshooting] InvalidCredentialException: HTTP 401 Error : User not authorized to execute service Click here
References

Register for Free Master Class on Cloud Security Using Oracle IDCSCareer Path & What to Learn? 

Next Task for You

Download our FREE Guide i.e., 7 Docs Must Read to Become Expert in Cloud Security With Oracle Identity Cloud Service (IDCS).

Click on the image below to Download the Guide:

The post OIM/OIG – IDCS Integration : [Solved] javax.net.ssl.SSLHandshakeException : PKIX path building failed appeared first on Oracle Trainings.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

This post covers the Overview & Concepts of EBS Cloud Manager (EBSCM).

Oracle E-Business Suite Cloud Manager is a key component of the Oracle E-Business Suite automation for Oracle Cloud Infrastructure (OCI).

It is the successor to the EBS Cloud Admin Tool and is first being introduced for Oracle Cloud Infrastructure (OCI). To know more about Cloud Admin Tool check our previous post on Role Of EBS Cloud Admin Tool in Provisioning Oracle EBS (R12) on Cloud

Introduction To EBS Cloud Manager (EBSCM)

EBS Cloud Manager is a tool through which you can manage E-Business Suite on Oracle Cloud Infrastructure (OCI). This tool can be used to Create, Manage, Configure Oracle application on Oracle Cloud (OCI).

EBS CLoud Manager is a Tool ( Virtual Machine ) that centrally manages all your EBS Environments on the Oracle Cloud (OCI).

Features of EBS Cloud Manager(EBSCM)

Using EBS Cloud Manager you can do:

  • Environment Deployment
  • One-Click provisioning with pre-populated deployment options (Single Node, Demo)
  • Advanced provisioning with user-selected deployment options
  • Lift and Shift Migration to OCI from on-premises backup
  • Lifecycle management
  • Clone the environment
  • Delete the environment
  • Separation of Duties: Multiple Compartment, groups, and Network Profiles
  • Backup & Recovery
  • TDE for Compute DB instance
  • More use cases in pipeline like Adding additional node, HA & DR

EBS Cloud Manager Benefits
  • Secure, with a load balancer that works as a TLS termination point.
  • Deployed on a subnet that is not directly exposed to the end user’s network
  • Multiuser, allowing multiple DBAs to manage the same set of Oracle E-Business Suite environments.
  • Fully integrated with Identity Cloud Service (IDCS) for authentication services.
How to Provision EBS Cloud Manager (EBSCM) 

1) Log in to the Oracle Cloud account, go to the OCI Console.
Note: If you haven’t registered for the Oracle Cloud Free Trial account yet, then, please Download Step by Step Activity Guide to Register for Oracle Cloud Trial Account

2) From the navigation menu, click on Marketplace

3) In this Marketplace, you will get the EBS CM image as well as all the Oracle provided Images & partners

4) Simply click on launch instance & it will create a Linux Machine inside your OCI Console using which you can then create or provision other EBS environment, also manage EBS.

How to Check EBS Cloud Manager Version

Access the URL of your Cloud Manager & on the Top Right Side click About

How to Provision EBS (R12) Using Cloud Manager (EBSCM)

Cloud Manager gives 2 options for Provisioning:

  • Simplified Provisioning of EBS: Where preset topologies are defined and we can select and perform quick provisioning.
  • Advance Provisioning of EBS: Here we can define our own topology to provision EBS and is useful in case of complex architectural design. Here we get the option to create the Instance using a backup of the database as well and we can define the backup policies too.

1) On the Oracle E-Business Suite Cloud Manager Environments page, click Provision Environment and select One-Click.

2) Enter the values for your new environment and click Submit

You can see Architecture details of the already created instance Application, Database and Load Balancer what all is included in the Architecture in our previous blog on Oracle E-Business Suite (R12) On OCI for Apps DBAs

How to Migrate EBS From On-premise to Cloud (Lift and Shift ) Using Cloud Manager

We can move the on-premises instance to Cloud using Cloud manager. Cloud manager is capable of creating an instance from the object storage backup. It uses new backup utility which is known as EBS Cloud Backup Utility, as a standalone tool for taking EBS backup to object storage and needs to be run on the source environment.

How to Clone EBS (R12) on Cloud 

One of the most common activity for DBA is Cloning and with this tool, it can be done quickly and conveniently. As of not only Compute clone can be done which will be blocked volume cloning or fast cloning methodology

If you want to know more about Cloning check my previous blog on E-Business Suite (EBS) on OCI | Block Volume Cloning | Automated Way

How to Delete an Environment

An environment created may need to be decommissioned when not needed. The easy way to decommission the environment and release the resource involved and this will further reduce your cloud cost. All this can be done easily using Cloud Manager.

Finally much improved and GUI based tool for managing Oracle EBS environment on the cloud with new EBS backup utility is released and much more addition to coming with time.

Please stay tuned for our future blog on Cloud Manager where we will deep-diving into Cloud Manager & will see various aspects of it.

Related/References Next Task For You

If you are an Oracle Apps DBA and just starting out your journey to Oracle public Cloud then we highly recommend you to download our FREE Guide that contains 7 Things Every Oracle Apps DBA & Architect Must Know To Build & Manage EBS (R12) On Cloud in order to Manage & Migrate Oracle EBS R12 on Oracle Cloud.

Click on below image to get the FREE Guide.

The post Oracle EBS(R12) Cloud Manager Overview : What & How appeared first on Oracle Trainings.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

This post covers what all packages are required (RPM’s) for Oracle E-Business Suite (EBS) R12 On Oracle Linux 7 or Red Hat Enterprise Linux 7.

If you are new to Oracle E-Business Suite, then I would suggest you check our previous post where we have covered in detail about  Oracle E-Business Suite R12.2 Architecture. and also check what all operating system is supported by Oracle E-Business Suite (EBS)R12.

Required Packages

Below are the required packages needs to be installed on your Oracle Linux 7 or Red Hat Enterprise Linux 7  before installing Oracle E-Business Suite (EBS)R12 on it.

Note: Customers on Exadata (Database Machine, Cloud Machine, Cloud Service) should not install the packages listed below as the system already contains all required packages and settings needed to run the Oracle Database.

Packages Need to be Installed In  Application Tier
  • compat-libstdc++-296-2.96-144.0.2.el7.i686
  • openmotif21-2.1.30-11.EL7.i6861
  • xorg-x11-libs-compat-6.8.2-1.EL.33.0.1.i386
  • libXrender-0.9.8-2.1.el7.i686
  • perl-File-CheckTree-4.42-3.el7.noarch
Packages Need to be Installed In  Database Tier
  • compat-libcap1-1.10-7.el7.x86_64
  • compat-libstdc++-33-3.2.3-71.el7.x86_64
  • elfutils-libelf-devel-0.158-3.el7.x86_64
  • libaio-devel-0.3.109-12.el7.i686
  • libaio-devel-0.3.109-12.el7.x86_64
  • xorg-x11-utils-7.5-13.1.el7.x86_64
Packages Need to be Installed In  Database Tier & Application Tier
  • binutils-2.23.52.0.1-16.el7.x86_642
  • compat-libstdc++-33-3.2.3-71.el7.i686
  • gcc-4.8.2-16.el7.x86_64
  • gcc-c++-4.8.2-16.el7.x86_64
  • gdbm-1.10-8.el7.i686
  • gdbm-1.10-8.el7.x86_64
  • glibc-2.17-55.el7.i686
  • glibc-2.17-55.el7.x86_64
  • glibc-common-2.17-55.el7.x86_64
  • glibc-devel-2.17-55.el7.i686
  • glibc-devel-2.17-55.el7.x86_64
  • libgcc-4.8.2-16.el7.i686
  • libgcc-4.8.2-16.el7.x86_64
  • libstdc++-devel-4.8.2-16.el7.i686
  • libstdc++-devel-4.8.2-16.el7.x86_64
  • libstdc++-4.8.2-16.el7.i686
  • libstdc++-4.8.2-16.el7.x86_64
  • libXi-1.7.2-2.1.el7.i686
  • libXp-1.0.2-2.1.el7.i686
  • libXp-1.0.2-2.1.el7.x86_64
  • libXtst-1.2.2-2.1.el7.i686
  • libaio-0.3.109-12.el7.i686
  • libaio-0.3.109-12.el7.x86_64
  • libgomp-4.8.2-16.el7.x86_64
  • make-3.82-21.el7.x86_64
  • redhat-lsb-4.1-24.0.1.el7.x86_64
  • sysstat-10.1.5-4.el7.x86_64
  • util-linux-2.23.2-16.el7.x86_64

If your Application tier & Database tier is on same machine, then these pacakages needs to be installed in same machine only.

You can also directly install all the required packages for Oracle E-Business Suite (EBS) R12 on Oracle Linux 7 or Red Hat Enterprise Linux 7 by using below command, make sure yum is configured on your machine.

yum install oracle-ebs-server-R12-preinstall

Oracle E-Buisness Suite R12 RPMs

Alternatively, on the Database tier & Application tier, you can install the following pre-install rpm available via ULN for both Oracle Linux 7 or Red Hat Enterprise Linux 7

If you like the blog don’t forget to share with your friends, colleagues who are working on Oracle E-Business Suite R12 & post your comments if you have any doubts regarding packages required for installing Oracle E-Business Suite (EBS) R12 on  Oracle Linux 7 or Red Hat Enterprise Linux 7.

Related/Further Readings Next task for you

AppsDBa R12.2 Must Read Guide

Want to Know More about R12.2? Click on the image below, and get your FREE Guide i.e., “6 Docs Every Oracle Apps DBA Must Read for R12.2”. 

The post Required Packages For Oracle E-Business Suite (EBS) R12 On Oracle Linux 7/ Red Hat Enterprise Linux 7 appeared first on Oracle Trainings.

Read Full Article

Read for later

Articles marked as Favorite are saved for later viewing.
close
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Separate tags by commas
To access this feature, please upgrade your account.
Start your free month
Free Preview