Tuesday, March 25, 2014

EBS-- Oracle EBS 12.2 Vision Installation


Nowadays, we use EBS 12.2 in new projects.
At the begining of our implementation, we first install 12.2 Vision environment.
Because the vision is used for Demo and for some kind of initial training, that s why, customers does not allocate powerful servers for it. They want us install EBS Vision to Virtual Machines running on minimal logical hardware.. If that is the case, the 12.2 vision installation an take some reasonable time, as there several zip files to download & unzip and there are several critical places , which the installation can fail..
In this situation, it is important to do the installation in one go without sticking any errors..

Following approach desribes the installation process while bringing you some important information for the installation. If you consider this document, you will be likely able to install Vision 12.2 in one go.

Note that , the instructions in this document are for Linux 64 bit environments, but similar approaches can be implemented for different environments , as well.

First of all , you should follow the MOS document:
Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Linux x86-64 (Doc ID 1330701.1)

You should follow the above line by line to satisft all the requirements.
Keep that in mind that ,
an insufficent memory can extend your installation time for days.
an insufficient temp size, can make you encounter errors during in the middle of the installation, after waiting for 3 hours maybe.
a corrupted installation file can take you to the start ..

I have seen this, I have done this, you dont want this :)

That's why before the beginning take a look to the following notes too;12.2 Rapid-Install fails on Installing Web Tier Utilities with Error "Fatal Error: TXK Install Service" (Doc ID 1587452.1)
Oracle E-Business Suite Release Notes, Release 12.2 (Doc ID 1320300.1)
 Once you are ready, I mean after all the hardware/disks requirements covered, all the rpms installed,  kernel and limits configured,  users/groups created, firewall disabled , /etc/oraInst.loc created/pointed to relevant oraInventory, and etc, you can continue with the following;

Change you directory to where your zip files are located and unzip following 3 archives with root user;

cd /to_your_stage
unzip -q 'V35215-01*.zip' -d .
This action will create startCD diretory in your stage
Then go to your startCD directory and execute the buildStage.sh script to build the Installation Stage.
cd startCD/Disk1/rapidwiz/bin/
./buildStage.sh
When you exeute the script above, a menu will appear.. Choose Create new stage function, and create your stage by specifying the directory that your zip files reside.
Before starting the installer, you need to open a vncserver or a similar X display server, and grant necessary privileges for everyone to open display on it. (I mean vncserver , and xhost + commands)
--Dont  use manual unzip for building the stage..

So, after building the stage successfully, you may need to adjust your rman restore parallelism according to your resources;
You can add the following line into the restore script restore-single2.sql located in startCD/Disk1/rapidwiz/template/ directory
For 2 parallel processes;

select 'configure device type DISK parallelism 2;' from dual;

Add the above just before the line "select 'catalog start with ''INSTALL'' NOPROMPT;' from dual;"
and then start the rapidwiz installer as follows;

cd /startCD/Disk1/rapidwiz/
./rapidwiz

This will open the installer program.. Installer will want some input from you, as well as want you to push the Next Button :)
And example installation is as follows;
Note that , I will not write any information about the installer screens as they are self explanatory..















If you somehow encounter errors and need to reinstall this, you should to the things below before restarting the installer;
delete the contents of the directories where you tried install the EBS 12.2 in your first try.
delete all the tempfiles in your tmp directory;
clear the contens of the inventory
kill all the oracle processes.


Anyways, after finishing the installation successfully, you should continue with post installation actions documented in 1330701.1, and apply  NLS language patch if necessary.
In 12.2 we use adop (not adpatch) utility to patch our EBS environment. Adop is a tool that is a part of online patching mechanism which also introduced in 12.2
Take a look to the FAQ in MOS to have a quick understanding abot the online patching concept and adop.
Oracle E-Business Suite Release 12.2: Online Patching FAQ (Doc ID 1583902.1)

Following is a graphical description of the new architecture that supports online patching..

R12.2env

As you we see, we have 2 filesystems there.. One for the running env. and one for the patches to be applied.
Also, there is edition-based redefinion used in Database Layer, to supply such a seperation like run system and patch system.

We have also a new script to switch between these 2 environments.. EBSapps.env
We dont need so we dont have a manintanence mode option anymore.


For NLS patching;
1)Download your NLS zip
2)unzip it , for ex: unzip Vpartname.zip -d $APPL_TOP_NE/../patch
3)License your language using Oracle Applications Manager
4)Maintain Multi lingual tables using adadmin
5)cd to patch directory
6)adop phase=prepare
7)adop phase=apply patches=10124646_TR:u10124646.drv  (for turkish)
8)adop phase=finalize , finalize_mode=full gathers statistics to help improve performance. Finalize will take about one hour longer if this mode is specified.finalize_mode=quick does not gather statistics, and therefore completes more quickly. This is the default. So; adop phase=finalize should be run here, by default it will be quick.. (it is vision I felt no need to gather stats)
9)adop phase=cutover
10)adop phase=cleanup

The description of adop phases are below:

prepare - Prepare the instance for patch application. 
 apply - Apply patches (to the patch edition). 
 finalize - Ready the instance for cutover. 
 cutover - Make the patch edition the new run edition.
 cleanup - Drop obsolete objects and data from old editions.


Special phases: 
 abort - Abort the current patching cycle. 
actualize_all - Create new copies of all code objects in the patch edition. 
 fs_clone - Copy the run file system to the patch file system.

So, I desribed  12.2 installation for a Single x86_64 Linux server.
I will make 12.2 fresh installations on Rac environments in upcoming days.. Split configuration will be involved, as well..  I ll keep you informed..
That is it for now. 


Note that: It took 6 hours to complete 12.2 Vision installation on a Vmserver with 4 logical cores and 12GB memory. The stage was on an external drive mounted from usb.

Also, It seems it is also mandatory to upgrade to 12.2.2 or 12.2.3 RUP patch.. It is a required as documented in 1320300.1.

No comments :

Post a Comment