R12.2 Environment Overview

Hi all,

Below is the R12.2 Environment Overview.

File System1 (FS1)
– Stores a complete copy of all applications and Middle Tier code

File System1 (FS2)
– Stores a complete copy of all applications and Middle Tier code

File System NON Editioned (FS_NE)
– Stores data that is written or read from the file system
– Report Outputs
– Log Files etc

File System 1 and File system 2 Rotate Run and Patch Designations

New script to setup the Environment: –EBSapps.env

New environment variables for R12.2 to help you navigate the system

$FILE_EDITION:-  Current fs edition type sourced values run or patch
$RUN_BASE:-  RUN file system base directory
$PATCH_BASE:– Patch file system base directory
$NE_BASE:-Non:- Edition file system base directory
$APPL_TOP_NE:- Application top that stores product files considered data

R12.2 E-Business Suite File System layout

File System laid down after 12.2 Rapid Install

New File to choose the environment to set:run or patch EBSapps.env

Non-Editioned File System patch top and logs

Online patching Life Cycle with adop

Please note that the utility we use to apply patch on R12.2 is adop. adop Internally calls adpatch.

New Tools to Manage Online Patching in R12.2

adop replaces adpatch as the R12.2 patching toll

To get The status of Patching Cycle use as below

adop -status

One More thing Interestingly in R12.2 there is no question of putting Application Under Maintenance.  

Microsoft Windows 8 Certified with Oracle E-Business Suite

Microsoft Windows 8 desktop clients are certified for the Oracle E-Business Suite 11.5.10.2, 12.0, 12.1, and 12.2. This certification applies to the following editions:

Windows 8

• Windows 8 Enterprise
• Windows 8 N edition
• Windows 8 Pro N edition
• Windows 8 Pro Pack N edition

Internet Explorer 10

Oracle E-Business Suite 11.5.10.2 Prerequisites

• Oracle Applications 11.5.10.2
• Oracle Applications Technology 11i.ATG_PF.H Rollup 6 (RUP 6) (patch 5903765) or later.
• Oracle Developer 6i patchset 19 (6.0.8.28.x) (Note 125767.1).
• MLR Patch 8888184
• Java client plug-in JRE 1.6.0_37 or later 1.6 updates
• Java client plug-in JRE 1.7.0_10 or later 1.7 updates

Oracle E-Business Suite R12.0 Prerequisites

• Oracle E-Business Suite 12.0.6
• Oracle Applications Technology R12.ATG_PF.A.DELTA.6 (patch 7237006) or later.
• Oracle Forms Version 10.1.2.3 or later.
• Java client plug-in JRE 1.6.0_37 or later 1.6 updates
• Java client plug-in JRE 1.7.0_10 or later 1.7 updates

Oracle E-Business Suite 12.1 Prerequisites

• Oracle E-Business Suite 12.1.3
• Java client plug-in JRE 1.6.0_37 or later 1.6 updates
• Java client plug-in JRE 1.7.0_10 or later 1.7 updates

Oracle E-Business Suite 12.2 Prerequisites

• Oracle E-Business Suite 12.2.2 or higher
• Java client plug-in JRE 1.6.0_37 or later 1.6 updates
• Java client plug-in JRE 1.7.0_10 or later 1.7 updates

Firefox ESR 17

Oracle E-Business Suite 11i Prerequisites

• Oracle E-Business Suite 11.5.10.2.
• Oracle Developer 6i patchset 19 (6.0.8.28.x) or later (note 125767.1)
• Oracle Applications Technology 11i.ATG_PF.H Rollup 6 (RUP 6)(patch 5903765) or later
• Applications Framework Patch 7651759
• Patch 7567782 which removes the use of the jpi-version parameter and switches Firefox to a non-static versioning model.
• Java client plug-in JRE 1.6.0_37 or later 1.6 updates
• Java client plug-in JRE 1.7.0_10 or later 1.7 updates

Oracle E-Business Suite R12.0 Prerequisites

• Oracle E-Business Suite 12.0.6
• Oracle Applications Technology R12.ATG_PF.A.delta.6 (patch 7237006) or later
• Applications Framework Patch 7602616
• Patch 7567840 which removes the use of the jpi-version parameter and switches Firefox to a non-static versioning model.
• Java client plug-in JRE 1.6.0_37 or later 1.6 updates
• Java client plug-in JRE 1.7.0_10 or later 1.7 updates

Oracle E-Business Suite R12.1 Prerequisites

• Oracle E-Business Suite 12.1.3 or higher
• Java client plug-in JRE 1.6.0_37 or later 1.6 updates
• Java client plug-in JRE 1.7.0_10 or later 1.7 updates

Oracle JInitiator Not Compatible

Oracle JInitiator was built on top of Java 1.3.  Java 1.3 is desupported and is not compatible with Windows 8, Windows Vista, or Windows 7.  We have no plans to certify Oracle JInitiator with Windows 8.

Premier Support for Oracle JInitiator 1.1.8 ended in December 2008, and Premier Support for Oracle JInitiator 1.3 ended for EBS customers in July 2009.

Use the Native JRE plug-in

Windows 8 desktop clients are certified only with the native Java Runtime Environment (JRE) with Windows 8.

Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops from JRE 1.6.0_03 and later updates on the 1.6 codeline, and from JRE 7u10 and later updates on the JRE 7 codeline.

The minimum JRE prerequisites for Windows 8 are higher than in previous releases.  These are:

• Java client plug-in JRE 1.6.0_37 or later 1.6 updates
• Java client plug-in JRE 1.7.0_10 or later 1.7 updates

We test all new JRE 1.6 and JRE 7 releases in parallel with the JRE development process, so all new JRE 1.6 and 7 releases are considered certified with the E-Business Suite on the same day that they’re released by our Java team.

You do not need to wait for a certification announcement before applying new JRE 1.6 or JRE 7 releases to your EBS users’ desktops. This applies to all certified Windows desktop operating systems, including XP, Vista, 7, and 8.

12.1.0.1 Database Certified with Oracle E-Business Suite

The base release for the 12c Database is now certified with EBiz. Please check the interoperability notes for R11i and R12 for the most up-to-date requirements for deployment.

• Interoperability Notes EBS 12.0 or 12.1 with RDBMS 12cR1 (Note 1524398.1)

Creating Stage for R12.2

Hi all,

Here I am going to discuss how to create stage for R12.2

Once we finished downloading the software extract below zip files using unzip

V35215-01_1of3.zip
V35215-01_2of3.zip
V35215-01_3of3.zip

Say if you have downloaded all the software in /backup/R12.2

Unzipping the above files will create startCD folder now go to cd startCD/Disk1/rapidwiz/bin/    and run buildStage.sh

Now it will start unzipping all the zip files in the location /backup/R12.2

  

We are going to get below folders in /backup/R12.2 location

EBSInstallMedia

startCD

TechInstallMedia

TechPatches

I will continue with Installation in my coming blogs

Oracle Apps R12.2 Download

Hi All,

Oracle Apps R12.2 can be downloaded and is available at edelivery.oracle.com

We need Metalink Account to login into edelivery.oracle.com

Once after login into we have to select Search criteria as below:

Click on Oracle E-business Suite Release R12.2.2 Media Pack for Linux x86-64-bit

Once we click

Below are the list of zip files that we need download for the Installation of R12.2

V29764-01.zip
V29856-01.zip
V35215-01_1of3.zip
V35215-01_2of3.zip
V35215-01_3of3.zip
V35230-01_1of2.zip
V35230-01_2of2.zip
V35231-01_1of5.zip
V35231-01_2of5.zip
V35231-01_3of5.zip
V35231-01_4of5.zip
V35231-01_5of5.zip
V35802-01.zip
V35803-01_1of3.zip
V35803-01_2of3.zip
V35803-01_3of3.zip
V35804-01_1of2.zip
V35804-01_2of2.zip
V35805-01_1of2.zip
V35805-01_2of2.zip
V35806-01_1of3.zip
V35806-01_2of3.zip
V35806-01_3of3.zip
V35807-01.zip
V35808-01.zip
V35809-01.zip
V35810-01.zip
V35811-01.zip
V35812-01.zip
V35813-01.zip
V37515-01_1of6.zip
V37515-01_2of6.zip
V37515-01_3of6.zip
V37515-01_4of6.zip
V37515-01_5of6.zip
V37515-01_6of6.zip
V39615-01.zip
V39664-01.zip

How to Save putty sessions

Putty has the option to log telnet and SSH traffic session output to disk. I think it’s a good idea to always log the telnet and SSH session output of every session to a file. In this way you always have a great reference/history available, which contains all previous commands and output of earlier telnet and SSH sessions.

Configure Putty

When you want putty to log all your session output, you have to change the default settings. This is pretty simple: open putty and go to Session->Logging. Select all session output and specify a log file.

To automatically save the output to a file, you can set up Putty like this:

1. Start putty.exe
2. Go to Session -> Logging
3. Select "Printable output"
4. Choose the folder, where you want the file to be placed
5. Append a file name like &H_&Y&M&D_&T.log to the path (host_YearMonthDay_time.log)
6. Save the profile as default settings

I am using some putty parameters which will make every session unique, in this case “&H-&Y&M&D-&T.log”, which means:

• &H = hostname for the session
• &Y = year
• &M = month
• &D = day
• &T = time

The next step is save this new log settings to the Default Settings profile in putty; the Default Settings profile contains your….uh…Default Settings :). Every new putty session
will now log its output to a (new) logfile. Already saved sessions will not be affected by this setting, you have to change these sessions separately.

You will now end up with a bunch of unique log files for the various putty sessions and you’re building your own great putty-reference-database in the log directory specified.

ORA-01078: failure in processing system parameters

Error:

SQL> startup;
ORA-01078: failure in processing system parameters

LRM-00109: could not open parameter file '/u01/app/oracle/product/11.2.0/db_1/dbs/initOPROD.ora'


Solution:

down vote

I see two things wrong here. Oracle tries to open a parameter file in the $ORACLE_HOME/dbs directory with the format "spfile" + $ORACLE_SID + ".ora". If it cannot find it, it then tries to open "init" + $ORACLE_SID + ".ora". This is where the problem(s) are. By virtue of the fact that Oracle is trying to open a parameter file named "initXE.ora", your SID must be (or was at one point) equal to "XE". 1) This is the easy part, so try this first. Since (in your comments) doing an echo $ORACLE_SID yields nothing, try setting it. export ORACLE_SID=XE Then try starting Oracle again. 2) In your comments above, you show the file is named "initxe.ora". Is that really the name of the file? Or did your paste into a comment somehow lowercase the output of the ls command? The reason I point this out, is that Ubuntu (Linux) has a case-sensitive filesystem. So initxe.ora and initXE.ora are actually two different files. So if your comment is correct and the file is lower-cased, you'll want to set your ORACLE_SID to "xe" instead: export ORACLE_SID=xe Try that, and see if it works.