12.2.3 EBS version is available

The 12.2.3 EBS version has been publicated.
Now it is downloadble from support.oracle.com as 17020683 patch.

I am goind to download and apply it soon. Then of course I report my experience. I am quite curious about this new look and feel the skyros.

Newly publicated features of Oracle EBS 12.2.3 version

The 12.2.2 EBS version is quite new, but the Release Content Documents was updated with some new features what will be available in 12.2.3 version.
Check the 1302189.1 note for the updated RCD PDF files.

Some examples, it's not all of them, I have collected some interesting point for me:

OAF

• New Skyros Skin
• Rich Table Interactions
• Dynamic Views

The new Skyros skin could be a big changes in the look and feel if the following cite is really true:

Some thoughts about how useful could be a migration strategy document.

Do you find yourself in such situation, that you feel at the end phase of your project: "It would have good if we found the solution earlier" , "would have gone much more smoothly", don't you?

I have begin to collect some useful strategy documents I have used at my projects. Check my other blog post. This is the first one, the migration strategy document. Hope you like it.
http://architecttar.blogspot.com/2013/11/useful-strategy-documents-has-to-made.html

Oracle EBS 12.2.2 complete installation diary

12.2.2 installation diary

The new EBS 12.2.2 installation is not so simple as an old EBS, it contains many steps from many notes and based on a partially complete installation media.

In this blog post I will show you my latest 12.2.2 installation, through a "complete" diary.
So what will the post contains?

• all required installation documents and notes
• installation media files - complete list
• installation steps
• detected problems

New blog series

Hi all!

I have begin a new blog series to represent my other experiences that beyond my Oracle EBS knowledge. This will be much more general, much more architectural than this Oracle specific post series. Of course I will continue these one too.

So please check it here:
http://architecttar.blogspot.com

The next post will be in this series is a really complete Oracle EBS 12.2.2 installation guide, that will contains all steps (not only 12.2).

Thanks!
Zoltan

Behind the scenes 2. - the 12.2 online patching

Not advertised "features" of the online patching function

One of the most advertised new feature of the 12.2 system is the new online patching function. The Oracle's marketing was that this new feature will help to cut down the scheduled maintenance outages of an EBS system.

But what are the not publicated, not advertised "(dis)advantages" of this feature?

1. new patch tool
2. doubled/tripled file system
3. new "patch top" directory
4. new patching lifecycle
5. new restrictions
6. new multi node patch procedure
7. online patching db tools
8. FNDLOAD and Online Patching
9. Cloning and Online patching
10. Directory Structure and Online Patching

Cloning a 12.2 EBS with rapid clone

Cloning 12.2 EBS 

The 12.2 EBS cloning has been dramatically changed in the 12.2 version. The main concept still the same, (preclone, copy files, post clone), but the underlying logic was changed.

First you will not find Rapid Clone note for 12.2 on Oracle's Support site (The following document mention the 1383621.1 note, but is just a "rapid clone bug list" now, not a complete step by step note as the earlier notes were). You should open the "Oracle® E-Business Suite Setup Guide Release 12.2" document and read chapter 17 "Cloning Oracle E-Business Suite with Rapid Clone".

12.2 Installation problem - adrunfmw.sh shell script

There is an installation problem with the 12.2 EBS system. After creating the stage and start the installation process the progress bar hang at 38% and nothing happens.

I have looked after into the log files and find that the installation stopped at invoking of the adrunfmw.sh shell script. (it starts the deploying process of the new FMW server and EBS middleware programs).

I have search for it on Oracle Support site - nothing found - second on Google and found this forum:
https://forums.oracle.com/message/11203198

Behind the 12.2 scenes 1. - the new file structure

Behind the 12.2 scenes 1.

Now that the 12.2.2 version of Oracle EBS is publicly available we could go inside, go behind the marketing. We have already downloaded the new software and searching places for creating a new demo site from it. Until it's created I am reading the Concept, Install Guide, admin and etc documentations for searching the documented changes.

First from file directory structure - cause of why is increased the apps tier size from about 40GB to 64GB

Some comments for 12.2 Technology updates

My comments for the technology updates.

"On the application middle tier, Oracle E-Business Suite Release 12.2 now includes Oracle Fusion Middleware 11g Release 1 (11.1.1.6) which provides more flexible capabilities for high availability and performance to Oracle E-Business Suite nodes."  

The good news that the really old OAS software finally dropped out from EBS. But why not 12c version of Weblogic? The 12.2 still contain the old 10.1.2 forms server, why? There is the 11g version of forms server which is using Weblogic too.

12.2 is really near at the gates?

Hi All!

Today I have surfed on edelivery - searching for EBS 12.1 install kit - and amazingly I have found a new full media pack of R12.2.2 for Linux x86-64-bit operating system!

I have downloaded the first zip file to check it's content, it contains a readme.txt with these Support notes.

1. Document 389422.1, Recommended Browsers for Oracle E-Business Suite Release 12.html
• Added Oracle E-Business Suite 12.2
2. Document 1155883.1, Oracle E-Business Suite Desktop Client Hardware and Software Requirements.html
• no changes yet.

And these new documents now available for non beta testers too.

1. Document 1314621.1, Oracle E-Business Suite NLS Release Notes, Release 12.2.html
2. Document 1330701.1, Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Linux x86-64.html
3. Document 1330702.1, Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Oracle Solaris (64-bit).html
4. Document 1330703.1, Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for IBM AIX (64-bit).html
5. Document 1330704.1, Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for HP-UX Itanium.html
6. Document 1355068.1, Oracle E-Business Suite 12.2 Patching Technology Components Guide.html
7. Document 1376618.1, Oracle E-Business Suite Technology Stack Release Notes for Release 12.2.2.html
8. Document 1469456.1, DATAINSTALL AND HRGLOBAL APPLICATION 12.2 SPECIFICS.html
9. Document 1506669.1, Oracle E-Business Suite Release 12.2.2 Readme.html
10. Document 1560906.1, Applying the Release 12.2.2 AD and TXK Release Update Packs.html

12.2.2 Release Update patches are available for Linux x86, HP-UX,  Solaris and IBM AIX.
They are huge! 2.6 GB per a patch file...

Good news :)

The bad news:  12.2 documentations are still not available on OTN. :(

Zoltan

Implementing a demo RAC 12c system

Hi all!

I am working on a new post series. I am trying to build a whole workable demo Oracle 12c RAC system.
The demo system will use only free or trial licencesed downloadable virtual components.

The planned system components:

• Oracle virtualbox for virtualization
• 2 virtual node with Solaris operating system, 
• a ZFS virtual storage node, 
• Oracle 12c Enterprise Edition RAC
• Container and pluggable database instances

The new post series other goal is to show how fastly is possible to create a working Oracle 12c RAC database for demonstrating purposes of RAC, Solaris or ZFS storage functions, features.

I will begin it as soon as possible.

Zoltan

Building a 5 nodes Oracle EBS using RAC and shared appl top 8.

Finish the configuration

What we have got now?

• Grid infrastructure
• RAC database software
• 2 node RAC EBS database
• A to be configured application tier

The already made steps:

1. Prepare the RAC database software
2. Prepare the source database for the conversion
3. Convert database into RAC
4. Post database conversion steps
1. turn on autoconfig
2. server parameter changes
3. create new EBS specific cluster listeners

So I have to configure the application tier to use the new RAC database. The remaining steps are:

1. Configure application tiers for using RAC database service
2. Post configuration steps

Building a 5 nodes Oracle EBS using RAC and shared appl top 7.

Forming the RAC database

What we have got now?

• Grid infrastructure
• RAC database software
• 1+3 node Oracle EBS system

It's time to copy the EBS single node database data into the new RAC database.

I will use the 823587.1 note for transfering data from the single node EBS database into the new RAC one.
The main steps will be:

1. Prepare the RAC database software
2. Prepare the source database for the conversion
3. Convert database into RAC
4. Post database conversion steps
1. turn on autoconfig
2. server parameter changes
3. create new EBS specific cluster listeners
5. Configure application tiers for using RAC database service
6. Post configuration steps

This post will contain the steps until the application tier configuration, all remaining steps will be in the next one.

Building a 5 nodes Oracle EBS using RAC and shared appl top 6.

Add the 2 remaining node to the system

What we have got now?

• Grid infrastructure
• RAC database software
• 2 node Oracle EBS system

It's time to add the 2 remaining node using the shared APPL_TOP method.

I will use the 384248.1 note during the implementation. 

Building a 5 nodes Oracle EBS using RAC and shared appl top 5.

Begin to build the shared APPL_TOP

Now we have a well configured Oracle 11g RAC infrastructure and an installed cluster database software.
All independent tasks are finished so we are ready to begin to build the 5 node system.

First I will create a 1+3 node system, 1 node for database and 3 node for application tier (with shared appl_top). This task could be splitted into 2 subtask. The first one is to create a 2 node Oracle EBS system, the second one is add the remaing 2 application tier node and reconfigure the first application tier node.
The first task is nothing more then an ordinary EBS cloning task, the second subtask is same complexity as the first one :)

So what we will do at this time?

• prepare application tier nodes
• prepare source system
• create 2 node EBS system
• add the additional application nodes

Building a 5 nodes Oracle EBS using RAC and shared appl top 4.

Install Oracle Database Software

In the previuos step we have successfully installed the Oracle Cluster infrastructure. Now it's time to install the RAC enabled Database software.

The installation will takes these steps

• Install the base 11g R2 version 11.2.0.3 software
• Implement EBS - 11gR2 interoperability note's step

Building a 5 nodes Oracle EBS using RAC and shared appl top 3.

Building the RAC infrastructure

This step is an independent step from half of the other step. I you think you could do it at later for example you could made a 1+3 node Oracle EBS system (1 node database and 3 node apps tier) with configured load balancer and SSL.

But now I am starting with this.

The main steps will be:

1. install operating system on the 2 database node,
2. create and configure all necessary storage partitions and mount points,
3. check the installed operating system and configure it for Oracle RAC and EBS database,
4. create unix users and groups,
5. create stage area,
6. create asm disk groups,
7. install Oracle Clusterware 11g Release 2,
8. install latest PSU patches

Building a 5 nodes Oracle EBS using RAC and shared appl top 2.

Requirements

The first part of this series was a good example for small pieces answers. But this will not.
I have collected all requirements what is need for implement and well configure a 5 node EBS system (with RAC and shared appl top of course)

What are these requirements?

1. Documentations
2. Required Software
3. Recommended hardware configuration

Building a 5 nodes Oracle EBS using RAC and shared appl top 1.

Let's begin with the end. First of all I show you what is my goal, what I will reach at the end of this post series.

I like diagrams. Usually a good diagram is much better then any number of text description.
So first here it is what I want to get at the end:

Yes, you see well, this is a simple network diagram.
At the end of the post series we will have these servers in the above configuration:

• a 2 node RAC database, (db01, db02) 
• a 3 node Apps Tier 
• 2 node for web and forms processing, (app01, app02)
• 1 node for concurrent program processing (conc01)
• and a load balancer

And yes again I haven't put on the diagram these hardwares:

• storage
• backup device
• monitoring tool

I will discuss them at a later, in an other post.

In the next post I try to collect all documentations what I had to read and use during the implemenation.

Architecting viewpoint of this configuration

There could be many, many question about this configuration.  I will try to present some architecting viewpoint of this system:

• why I have choosed this configuration,
• what is the benefits of this system,
• what are the risks, the disadvantages of this system,
• what should I look for after implementing the system,
• is there any aftermath for a project if we choose this configuration.

Let's begin the answers.

"why I have choosed this"

In short: because the customer told this one.

I am kidding of course :) The customer usually never tell me what kind of configuration do they want. Instead of they are expecting functional and non functional requirements. Both of them has effect on arhictecture plan.

Functional means what modules, what functions do they want to use. So I have to consider on them, because between function and function there are many differences from resource viewpoint. (for example batch data handling needs other resources then a simple data input transaction).

Non functional means usually hardware, base software requirements (for example supported operating system, hardware vendor, storage type etc), but it means time, operating, maintenance etc requirements (for example operating time, expected response time, maximum outage, user numbers and so on, and so on)

At this example I could talk about non functional requirements

• 24/7 operating time
• minimize the outages
• hundreds of form users
• flexible, scalable architecture
• minimized maintenance cost
• use benefits of virtualization
• etc.

"what is the benefits of this system,"

The benefits? First of all, this architecture offer solutions for all non functioanl requirements above.  Why?
Some answer.

1. The RAC, think on it. It could server 24/7 operating time with minimized outages at database level. 2 node is not so much, but it is more than one :) So any problem with one node, the database will still available, it could still serve the data request. It is a good solution for flexiblity, scalablity requirement. If you need more resource you could easily add more nodes, if the additional resource claim is just a temporarly requirement, than after the resource peek you could easily drop the new nodes.
2. The 2+1 application tier could server many form and web users, with separated batch processing. The 2 node web tier could serv parallely the users through load balancer. The users will know only one URL, they don't have to know anything about the architure. So they don't have to manully switch between application tiers, if one nodes goes down. 
3. Separated batch processing benefit comes out when users start many, many reports, batch data transactions at same time. In this case the web tier will don't stop, the standard user interaction will not stop, the users "only" have to wait for end of their started programs.
4. Using of shared appl top benefits has many, some examples:
1. If you need new application tier, you shouldn't install a new node, you have to configure it only. It's true for both purposes, not depends on that the new node what kind of services will handle.
2. You don't need to patch all nodes, following one by one. You should patch only at once and all nodes will work with the new feature, with the new repaired function.
3. It needs much less disk space. (I hope the new 12.2 EBS system will still support shared appl top, the 2 APPL_TOP sofware will require much more disk space if not)
5. Of course maintance will not so simple as a 2 node EBS system, but RAC and shared APPL_TOP could minimize the extra maintenance resource requirements.

"what are the risks, the disadvantages of this system,"

Under writing...

"what should I look for after implementing the system,"

Under writing...

"is there any aftermath for a project if we choose this configuration."

Yes, of course. There aftermathes in developments, in project technical maintenance, in after go live support and so on.

Usually the development enviroment is much simplier than the configuration above. Allways talk with the project's team about the planned architecture. They have to know about it and of course they have to develop customization that work on planned system. Generally they like to "forget" the database and the application tier will not work on the same server.

The technical maintenance team life will not easier if you choose this kind of configuration. The test and live system implemantion, installation will take more times. Commonly the team could install the whole system much more tries than a simplier configuration. The backup, the restore, the disaster recovery tests will takes much more times too.

After go live, the support tasks takes longer than a simplier one. For example for any error handling on application tier you have to search error messages in much more log files than less complex configuration.

Introduction

Hello

Until today I have read many technical blogs, many support site notes (including Oracle Support), etc when I got task for problem solving, solution architecting and so on. Usually I have found what I looked for but mostly in very small pieces. Every pieces solved only a small part of the big problem and I had to concat them into the big, whole solution. Everybody knows who use Oracle's support site that to search for information on Oracle Support is not so easy as the Oracle's marketing tell us. Many many wrong hit (sometimes totally irrelevant) for the searching keyword, sometimes the really relevant note is not coming up.

Nowadays I quickly find the relevant informations, but it needs the experience to know what could be the really good keywords for good relevant hits. You know knowledge of searching could be an independent science :)

So what is my goal with this new blog?
Instead of writing down small simple answers for small questions I will try to give you full solutions for big problems or huge tasks. Of course I will give you the relevant notes, bug numbers - but not their content - in my blog posts.

First I begin with a tutorial for how to build a Oracle EBS system with RAC, shared appl top, load balancer.

Zoltan