1.     Minimum System Requirements

1.1.    Supported Operating Systems:

1.1.1. Version 6.1 UL2+ (UL6+ if using WLS 10.3.6 and JDK 7)

1.1.2. Version 7.1 UL0+

1.2.    *RAM: 8GB+

1.3.    HDD Partitioning:

*Software Mount: One file system mount with at least 50GB of free space to store the software and temporary file storage for servers.

*SWAP: 8GB+

1.4.    OS User Access Requirements:

1.4.1. OS User will need to own the software mount.

1.4.2. Root user access must be accessible for the installation.

*RAM and File System Mount Specifications: For production systems, please consult PITSS or Oracle on sizing recommendations. The amount of RAM, HDD Space for SWAP and Software Mounts will vary depending on end-user usage and application characteristics.

2.     Other Unix OS Requirements

2.1.    Open File Limits:

“soft nofile” should be atleast 4096
“hard nofile” should be atleast 4096 (65535 is recommended)

3.     Required AIX Package

Download package X11.motif.lib 2.1.30

For more information, please review: http://docs.oracle.com/html/E25460_01/r2_fr_requirements.htm

4.     Database Requirements

4.1.    Supported Database Versions:

10.2.0.4+

11.1.0.7+

11.2.0.1+

12.1.0.1+

4.2.    A database user with DBA/SYS privileges accessible.

4.3.    The file tnsnames.ora containing the SID of the database will need to be placed in the server in the same location as the other prerequisites.

5.     Software Requirements

5.1.1. IBM JDK 6 (SR11 or higher) (if using WLS 10.3.5)

5.1.2. IBM JDK 7 (SR2 or higher) (if using WLS 10.3.6)

5.2.    WebLogic 10.3.6 Upgrade Patchset

The following steps will help guide you through Oracle’s Support website to find the Oracle WebLogic Server 10.3.6 Patch set. This is the only Oracle Website location where the WebLogic Server 10.3.6 Patch set can be downloaded.

5.2.1. Go to support.oracle.com

5.2.2. Login with your Oracle OTN Login that has your organization’s “oracle support identifier” that lets you download “Patches & Updates”

5.2.3. Click on “Patches & Updates”

5.2.4. In the Patch Search window, type in 13529623 for the patch number. Select the operating system and click Search.

5.2.5. In the Patch Search Results, only one patch should appear. Click on the patch number.

5.2.6. Click on Download.

After clicking Download, you should be able to select the zip file and download to your machine.

5.3.    Forms 11.1.2.1 Patchset

The following steps will help guide you through Oracle’s Support website to find the Oracle Forms 11.1.2.1 Patch set. This is the only Oracle Website location where the WebLogic Server 11.1.2.1 Patch set can be downloaded. NOTE: The Oracle Forms 11.1.2.1 base installer can NOT be used to upgrade Forms 11.1.2.0 to 11.1.2.1.

5.3.1. Go to support.oracle.com

5.3.2. Login with your Oracle OTN Login that has your organization’s “oracle support identifier” that lets you download “Patches & Updates”

5.3.3. Click on “Patches & Updates”

5.3.4. In the Patch Search window, type in 15948641 for the patch number. Select the operating system and click Search.

5.3.5. In the Patch Search Results, only one patch should appear. Click on the patch number.

5.3.6. Click on Download.

After clicking Download, you should be able to select the zip file and download to your machine.

If you have any questions on the above, please contact PITSS.

NOTE: Unless you are using Oracle Portal or Discoverer 11g, it is recommended to upgrade to Oracle Forms and Reports 11gR2 (11.1.2.1).

1.     Minimum System Requirements

1.1.    Oracle Supported Forms Builder Platforms (Development Client):

1.1.1. Windows XP 32-bit SP3+

1.1.2. Windows Server 2003 32-bit R2+

1.1.3. Windows Server 2008 32-bit

1.1.4. Windows 7 64-bit

1.1.5. Windows 7 32-bit

1.2.    Oracle Support Forms & Reports Services Platforms (Server):

1.2.1. Windows Server 2003 32-bit R2+

1.2.2. Windows Server 2008 64-bt R2+

1.3.    *RAM: 8GB+ (16GB+ for production environments)

1.4.    Virtual Memory: 4-8GB (8GB+ for production environments)

1.5.    HDD Partitioning:

*Software Mount: One file system mount with at least 50GB of free space to store the software and temporary file storage for servers.

1.6.    The operating system user that is used for the installation must have Administrative privileges on the machine and “Full Access” to the file system directory where 11g WebLogic and Forms will be installed.

*RAM and File System Mount Specifications: For production systems, please consult PITSS or Oracle on sizing recommendations. The amount of RAM, HDD Space for SWAP and Software Mounts will vary depending on end-user usage and application characteristics.

2.     Software Requirements

2.1.    Java JDK 1.7.0_15 (or latest version of Java JDK 7)

2.1.1. Go to http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html

2.1.2. Click on “jdk-7u15-windows-i586.exe” for 32-bit and “jdk-7u15-windows-x64.exe” for 64-bit.

NOTE: This is the page to download the latest JDK version.

NOTE: Java JDK  1.7.0_7 is the minimum required for Forms 11.1.2.1 if using Oracle WebLogic Server 10.3.6, but we recommend the latest version of JDK (1.7.0_15+) as it is more current and contains critical security updates.

2.2.    WebLogic 10.3.6 Upgrade Patchset

The following steps will help guide you through Oracle’s Support website to find the Oracle WebLogic Server 10.3.6 Patch set. This is the only Oracle Website location where the WebLogic Server 10.3.6 Patch set can be downloaded.

2.2.1. Go to support.oracle.com

2.2.2. Login with your Oracle OTN Login that has your organization’s “oracle support identifier” that lets you download “Patches & Updates”

2.2.3. Click on “Patches & Updates”

2.2.4. In the Patch Search window, type in 13529623 for the patch number. Select the operating system and click Search.

2.2.5. In the Patch Search Results, only one patch should appear. Click on the patch number.

2.2.6. Click on Download.

After clicking Download, you should be able to select the zip file and download to your machine.

2.3.    Forms 11.1.1.6 Patchset

The following steps will help guide you through Oracle’s Support website to find the Oracle Forms 11.1.1.6 Patch set. This is the only Oracle Website location where the WebLogic Server 11.1.1.6 Patch set can be downloaded.

2.3.1. Go to support.oracle.com

2.3.2. Login with your Oracle OTN Login that has your organization’s “oracle support identifier” that lets you download “Patches & Updates”

2.3.3. Click on “Patches & Updates”

2.3.4. In the Patch Search window, type in 13517084 for the patch number. Select the operating system and click Search.

2.3.5. In the Patch Search Results, only one patch should appear. Click on the patch number.

2.3.6. Click on Download.

After clicking Download, you should be able to select the zip file and download to your machine.

If you have any questions on the above, please contact PITSS.

NOTE: Unless you are using Oracle Portal or Discoverer 11g, it is recommended to upgrade to Oracle Forms and Reports 11gR2 (11.1.2.1).

1.     Minimum System Requirements

1.1.    Supported Solaris Platforms:

1.1.1. Solaris 9 Update 9+ SPARC

1.1.2. Solaris 10 Update 4+ SPARC

Note: For more information on supported platforms, please refer to: http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

1.2.    RAM: 4GB+

1.3.    HDD Partitioning:

1.3.1. At least 30GB of free space for the installation directory where you want 11g WebLogic and Forms Installed

1.3.2. At least 1GB of TEMP space*

1.3.3. At least 3GB of SWAP space *
* Note: If TEMP and SWAP use the same file system directory, it is recommended to allocate at least 4GB of space

1.4.    Root user access will need to be available when installing Forms 11g.

1.5.    VNC or a GUI tool like XTerm must be accessible for installing Forms 11g.

1.6.    An operating system user will need to be accessible for installing WebLogic and Forms.

Note for UNIX-Based installations: the operating system user that we will be installing WebLogic as will need to have ownership and full file access of the file system directory that WebLogic is to be installed in. For example, if you want WebLogic installed in a directory “/opt/oracle” by a user called “weblogic”, the directory “oracle” must be owned by “weblogic” and have full read and write permissions on the directory.

2.     Required Packages

2.1.    Below is a list of packages/libraries that need to be installed prior to installing 11g Forms and Reports. Please note the difference between the processor and release types

For more information from Oracle on required package information please go to: http://download.oracle.com/docs/html/E18558_01/fusion_requirements.htm#BABGBCIG

3.     Software Requirements

3.1.    Java JDK 1.7.0_15 (or latest version of Java JDK 7)

3.1.1. Go to http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html

3.1.2. Click on “jdk-7u15-solaris-x64.tar.gz for 64-bit” or “jdk-7u15-solaris-sparcv9.tar.gz for SPARC”

NOTE: This is the page to download the latest JDK version.

NOTE: Java JDK  1.7.0_7 is the minimum required for Forms 11.1.2.1 if using Oracle WebLogic Server 10.3.6, but we recommend the latest version of JDK (1.7.0_15+ as it is more current and contains critical security updates.

For UNIX-Based systems we recommend to install this prior to the WebLogic and Forms installation.

3.2.    WebLogic 10.3.6 Upgrade Patchset

The following steps will help guide you through Oracle’s Support website to find the Oracle WebLogic Server 10.3.6 Patch set. This is the only Oracle Website location where the WebLogic Server 10.3.6 Patch set can be downloaded.

3.2.1. Go to support.oracle.com

3.2.2. Login with your Oracle OTN Login that has your organization’s “oracle support identifier” that lets you download “Patches & Updates”

3.2.3. Click on “Patches & Updates”

3.2.4. In the Patch Search window, type in 13529623 for the patch number. Select the operating system and click Search.

3.2.5. In the Patch Search Results, only one patch should appear. Click on the patch number.

3.2.6. Click on Download.

After clicking Download, you should be able to select the zip file and download to your machine.

3.3.    Forms 11.1.1.6 Patchset

The following steps will help guide you through Oracle’s Support website to find the Oracle Forms 11.1.1.6 Patch set. This is the only Oracle Website location where the WebLogic Server 11.1.1.6 Patch set can be downloaded.

3.3.1. Go to support.oracle.com

3.3.2. Login with your Oracle OTN Login that has your organization’s “oracle support identifier” that lets you download “Patches & Updates”

3.3.3. Click on “Patches & Updates”

3.3.4. In the Patch Search window, type in 13517084 for the patch number. Select the operating system and click Search.

3.3.5. In the Patch Search Results, only one patch should appear. Click on the patch number.

3.3.6. Click on Download.

After clicking Download, you should be able to select the zip file and download to your machine.

If you have any questions on the above, please contact PITSS.

NOTE: Unless you are using Oracle Portal or Discoverer 11g, it is recommended to upgrade to Oracle Forms and Reports 11gR2 (11.1.2.1).

1.     Minimum System Requirements

1.1.    Supported Operating Systems:

1.1.1. RedHat/Oracle Enterprise Linux 4 64-bit: 4 UL7+

1.1.2. RedHat/Oracle Enterprise Linux 5 64-bit: 5 UL3+

1.1.3. SUSE Linux 10 32-bit: All SP Levels Supported

1.1.4. SUSE Linux 10 64-bit: All SP Levels Supported

1.1.5. SUSE Linux 11 32-bit: All SP Levels Supported

1.1.6. SUSE Linux 11 64-bit: All SP Levels Supported

1.2.    *RAM: 8GB+

1.3.    HDD Partitioning:

*Software Mount: One file system mount with at least 50GB of free space to store the software and temporary file storage for servers.

TEMPFS Space: 4GB+ (Minimum: 1GB+)

*SWAP: 8GB+

1.4.    OS User Access Requirements:

1.4.1. OS User will need to own the software mount.

1.4.2. Root user access must be accessible for the installation.

*RAM and File System Mount Specifications: For production systems, please consult PITSS or Oracle on sizing recommendations. The amount of RAM, HDD Space for SWAP and Software Mounts will vary depending on end-user usage and application characteristics.

2.     Other Linux OS Requirements

2.1.    The operating system needs to set Native POSIX Threads Library (NPTL) as the default threads-implementation. To check for us, run the following command:

getconf GNU_LIBPTHREAD_VERSION

The expected results should be: NPTL 2.3.4 or higher.

2.2.    Open File Limits:

“soft nofile” should be atleast 4096
“hard nofile” should be atleast 4096 (65535 is recommended)

3.     Required Linux Packages

3.1. RedHat Enterprise Linux 4 64-bit

The minimum versions of the packages below will need to be installed before the Forms 11g installation can begin:

For more information from Oracle on required packages please go to: http://download.oracle.com/docs/html/E18558_01/fusion_requirements.htm#BABGBCIG

3.2. RedHat and Oracle Enterprise Linux 5 64-bit:

The minimum versions of the packages below will need to be installed before the Forms 11g installation can begin:

For more information from Oracle on required packages please go to: http://download.oracle.com/docs/html/E18558_01/fusion_requirements.htm#BABGBCIG

3.3. SUSE Linux 10 32-bit:

The minimum versions of the packages below will need to be installed before the Forms 11g installation can begin:

* To download “openmotif” packages, please go to http://ftp.novell.com/partners/oracle/sles-11/openmotif_FUSION_SLES11.tgz. This is a single zip file from Novell and includes a README file which details about package names, versions, and source.

For more information from Oracle on required packages please go to: http://download.oracle.com/docs/html/E18558_01/fusion_requirements.htm#BABGBCIG

3.4. SUSE Linux 10 64-bit:

The minimum versions of the packages below will need to be installed before the Forms 11g installation can begin:

* To download “openmotif” packages, please go to http://ftp.novell.com/partners/oracle/sles-11/openmotif_FUSION_SLES11.tgz. This is a single zip file from Novell and includes a README file which details about package names, versions, and source.

For more information from Oracle on required packages please go to: http://download.oracle.com/docs/html/E18558_01/fusion_requirements.htm#BABGBCIG

3.5. SUSE Linux 11 32-bit:

The minimum versions of the packages below will need to be installed before the Forms 11g installation can begin:

* To download “openmotif” packages, please go to http://ftp.novell.com/partners/oracle/sles-11/openmotif_FUSION_SLES11.tgz. This is a single zip file from Novell and includes a README file which details about package names, versions, and source.

For more information from Oracle on required packages please go to: http://download.oracle.com/docs/html/E18558_01/fusion_requirements.htm#BABGBCIG

3.6. SUSE Linux 11 64-bit:

The minimum versions of the packages below will need to be installed before the Forms 11g installation can begin:

* To download “openmotif” packages, please go to http://ftp.novell.com/partners/oracle/sles-11/openmotif_FUSION_SLES11.tgz. This is a single zip file from Novell and includes a README file which details about package names, versions, and source.

For more information from Oracle on required packages please go to: http://download.oracle.com/docs/html/E18558_01/fusion_requirements.htm#BABGBCIG

4.     Software Requirements

4.1.    Java JDK 1.7.0_15 (or the latest version of Java JDK 7)

4.1.1. Go to http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html

4.1.2. Click on “jdk-7u15-linux-x64.tar.gz”.

NOTE: This is the page to download the latest JDK version.

NOTE: Java JDK  1.7.0_7 is the minimum required for Forms 11.1.2.1 if using Oracle WebLogic Server 10.3.6, but we recommend the latest version of JDK (1.7.0_15+) as it is more current and contains critical security updates.

For UNIX-Based systems we recommend to install this prior to the WebLogic and Forms installation.

4.2.    WebLogic 10.3.6 Upgrade Patchset

The following steps will help guide you through Oracle’s Support website to find the Oracle WebLogic Server 10.3.6 Patch set. This is the only Oracle Website location where the WebLogic Server 10.3.6 Patch set can be downloaded.

4.2.1. Go to support.oracle.com

4.2.2. Login with your Oracle OTN Login that has your organization’s “oracle support identifier” that lets you download “Patches & Updates”

4.2.3. Click on “Patches & Updates”

4.2.4. In the Patch Search window, type in 13529623 for the patch number. Select the operating system and click Search.

4.2.5. In the Patch Search Results, only one patch should appear. Click on the patch number.

4.2.6. Click on Download.

After clicking Download, you should be able to select the zip file and download to your machine.

4.3.    Forms 11.1.1.6 Patchset

The following steps will help guide you through Oracle’s Support website to find the Oracle Forms 11.1.1.6 Patch set. This is the only Oracle Website location where the WebLogic Server 11.1.1.6 Patch set can be downloaded.

4.3.1. Go to support.oracle.com

4.3.2. Login with your Oracle OTN Login that has your organization’s “oracle support identifier” that lets you download “Patches & Updates”

4.3.3. Click on “Patches & Updates”

4.3.4. In the Patch Search window, type in 13517084 for the patch number. Select the operating system and click Search.

4.3.5. In the Patch Search Results, only one patch should appear. Click on the patch number.

4.3.6. Click on Download.

After clicking Download, you should be able to select the zip file and download to your machine.

If you have any questions on the above, please contact PITSS.

NOTE: Unless you are using Oracle Portal or Discoverer 11g, it is recommended to upgrade to Oracle Forms and Reports 11gR2 (11.1.2.1).

1.     Minimum System Requirements

1.1.    Supported Operating Systems:

1.1.1. Version 6.1 TL6+

1.1.2. Version 7.1 TL0+

1.2.    *RAM: 8GB+

1.3.    HDD Partitioning:

*Software Mount: One file system mount with at least 50GB of free space to store the software and temporary file storage for servers.

*SWAP: 8GB+

1.4.    OS User Access Requirements:

1.4.1. OS User will need to own the software mount.

1.4.2. Root user access must be accessible for the installation.

*RAM and File System Mount Specifications: For production systems, please consult PITSS or Oracle on sizing recommendations. The amount of RAM, HDD Space for SWAP and Software Mounts will vary depending on end-user usage and application characteristics.

2.     Other Unix OS Requirements

2.1.    Open File Limits:

“soft nofile” should be atleast 4096
“hard nofile” should be atleast 4096 (65535 is recommended)

3.     Required AIX Package

Download package X11.motif.lib 2.1.30

For more information, please review: http://docs.oracle.com/html/E25460_01/r2_fr_requirements.htm

4.     Software Requirements

4.1.1. IBM JDK 6 (SR11 or higher) (if using WLS 10.3.5)

4.1.2. IBM JDK 7 (SR2 or higher) (if using WLS 10.3.6)

4.2.    WebLogic 10.3.6 Upgrade Patchset

The following steps will help guide you through Oracle’s Support website to find the Oracle WebLogic Server 10.3.6 Patch set. This is the only Oracle Website location where the WebLogic Server 10.3.6 Patch set can be downloaded.

4.2.1. Go to support.oracle.com

4.2.2. Login with your Oracle OTN Login that has your organization’s “oracle support identifier” that lets you download “Patches & Updates”

4.2.3. Click on “Patches & Updates”

4.2.4. In the Patch Search window, type in 13529623 for the patch number. Select the operating system and click Search.

4.2.5. In the Patch Search Results, only one patch should appear. Click on the patch number.

4.2.6. Click on Download.

After clicking Download, you should be able to select the zip file and download to your machine.

4.3.    Forms 11.1.1.6 Patchset

The following steps will help guide you through Oracle’s Support website to find the Oracle Forms 11.1.1.6 Patch set. This is the only Oracle Website location where the WebLogic Server 11.1.1.6 Patch set can be downloaded.

4.3.1. Go to support.oracle.com

4.3.2. Login with your Oracle OTN Login that has your organization’s “oracle support identifier” that lets you download “Patches & Updates”

4.3.3. Click on “Patches & Updates”

4.3.4. In the Patch Search window, type in 13517084 for the patch number. Select the operating system and click Search.

4.3.5. In the Patch Search Results, only one patch should appear. Click on the patch number.

4.3.6. Click on Download.

After clicking Download, you should be able to select the zip file and download to your machine.

If you have any questions on the above, please contact PITSS.

There has been an issue where the Forms application can hang or freeze when navigating between a set of radio buttons. This has been seen with Forms 11.1.1.6.0.

An Oracle patch 13652243 is available to download at My Oracle Support which can be applied to fix the problem. To apply the patch, you will need to do the following:

1. Download Patch 13652243 from Oracle Support. Be sure to specify the version of Forms you are using whether it is 11.1.1.6 or 11.1.2.0.
2. Extract the patch into the PC/server.
3. Shut down all WebLogic servers and OPMN processes in the Oracle home for Forms.
4. Open up Command Prompt as an administrator:
5. Navigate to the location where you extracted the patch and go into the 13652243 folder.
6. Run the following commands in Command Prompt:
1. set ORACLE_HOME=Path_to_Oracle_home (Example: set ORACLE_HOME=C:\Oracle\Middleware\as_1)
2. set PATH=%PATH%;%MIDDLEWARE_HOME%\oracle_common\OPatch
3. Double-check your opatch version by running: opatch version (It should be at or greater than the required version specified in the readme file)
4. opatch apply
7. When applying the patch, answer with ‘y’ when it asks if the system is ready for patching.
8. When the patch is applied, start up OPMN and your WebLogic servers.

After the environment is back up, you should no longer experience hanging or freezing when navigating between radio buttons.

NOTE: Please review the README file which comes with the patch before applying any Oracle patch.

Source: Oracle Support note 1489654.1

A problem can occur where if you try to log into the OAM console (Example: http://hostname.domain:7003/oamconsole) using the username created during the Domain Configuration (user weblogic for example) if IPv6 is enabled in the Windows server. What will happen is when you try to log into the OAM console for the first time, an error will come up saying that an incorrect username or password was entered. However, the same credentials can be used to access the WebLogic Administration Console.

If you look in the oam_server1_diagnostic.log file located in %OAM_DOMAIN_HOME%\servers\oam_server1\logs, you will see an error such as “OAMSSA-20005: Error initializing User/Role API : null.” in the log. This can happen when IPv6 is enabled in both the Windows server and the network adapter you are using. To fix the problem, you can complete the following steps:

1. Open up the Registry Editor (NOTE: Make a backup of the registry first!)
2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters
3. Double-click on DisabledComponents (or create it as a DWORD (32-bit))
4. Type in “0ffffffff” in the Value. This will disable IPv6 except for the loopback interface.
5. Open up setDomainEnv.cmd in a text editor. The file is located in %OAM_DOMAIN_HOME%\bin. (NOTE: Make a backup first!)
6. Look for the lines containing “EXTRA_JAVA_PROPERTIES”. Add a new line below each of them:
1. set EXTRA_JAVA_PROPERTIES=-Djava.net.preferIPv6Addresses=false –DuseIPv6Address=false –Djava.net.preferIPv6Addresses=false %EXTRA_JAVA_PROPERTIES%
7. Save and close the file.
8. Restart the Windows server and start up all OID and OAM WebLogic servers.

After applying the steps above, you should be able to log into the OAM Admin Console.

Sources: Oracle Support Notes 1316669.1 and 1311184.1 as well as http://support.microsoft.com/kb/929852 from Microsoft.

This is a temporary post that was not deleted. Please delete this manually. (65d145ae-bad9-4726-b7f6-ac00b6057ba1 – 3bfe001a-32de-4114-a6b4-4005b770f6d7)

If you are new to JDeveloper and ADF, then it is recommend to read the book, “Quick Start Guide to Oracle Fusion Development: Oracle JDeveloper and Oracle ADF” http://www.amazon.com/Quick-Start-Oracle-Fusion-Development/dp/0071744282. It covers all of the basic areas of JDeveloper and ADF including the topics discussed below.  

While you can define a lot of application logic via JDeveloper/ADF declarative components, most logic that you need to add needs to be coded in Java. This is where AM, VO, and EO implementation classes and managed/backing beans come into play.

Every application has business logic and user interface logic. Web Development in general has fallen into a standard way of developing this logic. By which seperates application objects into four basic layers: Data Services, followed by Model, View, Controller (MVC).

• Data Services: Database, Web Services, XML Data, etc…
• Model: Place for queries, C.R.U.D. operations, and any additional business logic
• View: user interface objects
• Controller: Determines how user interface objects interact with one another.

Especially in an object oriented world that programming has become, separating your application logic and objects and making them reusable is key to a well structured and maintainable application. The MVC application architecture allows you to accomplish such a goal.

Before we talk about what and how you would use java implementation classes of each Model layer object (AM, EO, VO), you need to understand the use and significance behind each object.

Entity Objects (EO) are the source code representation of a database table. This is ultimately the layer that executes the insert, update, and delete commands against the database, however, an entity view object will need to present the EO.

View Objects (VO) are read-only database queries or updatable view objects that represent an EO. All VOs are what are ultimately exposed as data controls in your Application Module – so that you can generate tables, forms, and other data-bound objects in your JSF pages.

Application Module (AM) are what allow the ADF application to expose VOs and any other custom java business logic to a JSF page. For example, so you have a an employees database table, by which you have setup an EO and VO to work with that table. You can add the VO to your AM as a data control, so that you can generate an Employee insert or update form on your JSF pages. Basically Application Modules are the glue that allows your JSF Pages to view data of a view object.

You can generate implementation classes on all three of these objects (EO, VO, and AM). When it comes to implementation classes, AM and VO Implementation classes are used the most often. Keep in mind these are very basic examples, you can do so much more with these classes:

• EO: Unless you need to change how records are literally inserted, updated, or deleted, there is almost no need to use these. Once you start getting familiar with how the EO, VO, and AMs work, you’ll understand.

• ViewObjectImplementation Class: This gives you a comprehensive ability to change how your ViewObject is defined, how it queries an entity object or database, and how it functions in general.
  For example, say you want to set a bind variable that is used in your View Object Query. ViewObjectImplementation classes give you the methods to set those bind variables.
• ViewObjectRowImplemtation Class: This gives you the ability to change how the data of your view object attributes are set and retrieved.
  For example, say you have a Project Task table where you have a Start Date, End Date, and Task Duration column. You want Task Duration to be  (Start Date – End Date). RowImplementation Classes allow you to calculate (Start Date – End Date) and set the Task Duration Column.

• Application Module [Implementation] Class:  This gives you comprehensive access to all of the data controls (View Objects) that you added to your AM. In addition, if you need to add any custom business logic, this is the recommended place to “initiate” that logic.
  For example, you can write a custom procedure to move data around or do advanced calculations in your Application Module Implementation class and expose them as a Data Control, so that you can use the data control on your JSF pages.
• There are additional classes like “Client Interface” and “Client Class”, however all you need to know about these, is that they allow you to expose custom methods written in your Application Module Implementation class as a data control.

This article was written to quickly address, on the high level, many questions surrounding the use of implementation classes. More in-depth and comprehensive examples will be written in the PITSS knowledge base in the days to come.

There is a known issue where the Node Manager (when configured to auto-start the WebLogic servers after a reboot of the OS) is unable to start up any of the WebLogic servers after SSL has been configured for the WebLogic servers. Similar to configuring Node Manager to auto-start WebLogic servers, a startup of the WebLogic servers will need to be performed using WLST providing java parameters pointing to your custom keystore. To perform this, please follow these steps:

1. Open up Command Prompt as an administrator
2. Navigate to %DOMAIN_HOME%\bin using the cd command
3. Run setDomainEnv.cmd
4. Start WLST using the following command (all one line): java –Dweblogic.security.SSL.ignoreHostnameVerification=true –Dweblogic.security.CustomTrustKeyStoreType=”JKS” –Dweblogic.security.TrustKeyStore=”CustomTrust” –Dweblogic.security.CustomTrustKeyStoreFileName=”%PATH_TO_TRUSTED_KEYSTORE%.jks” –Dweblogic.security.CustomTrustKeyStorePassPhrase=”%KEYSTORE_PASSWORD%” weblogic.WLST
5. Connect to the WebLogic domain using Node Manager: nmConnect(domainName=’%DOMAIN_HOME%’,username=’weblogic’,password=’%WEBLOGIC_PASSWORD%’)
6. Start up the AdminServer and any managed WebLogic servers using nmStart(‘SERVER_NAME’)
7. When all of the servers are running, restart the PC/server to make sure that all of the WebLogic servers start up.

After running the steps above, Node Manager should be able to start up the WebLogic servers without a problem.

1         Introduction

The following instructions is to install OAM 11.1.1.5 Bundle Patch 2 (Patch Number:  13115859). This patch addresses a login error relating to OAM and JavaScript failures, Oracle Bug 13254371. Oracle Support article “1447194.1” explains how to resolve the error as well.

The primary issue was where a customer was when OAM tries to authenticate the user in any non-IE browser like Firefox, Chrome, and Safari, the customer gets the following message in the browser:

“

<body onLoad="document.myForm.submit()"><noscript><p>JavaScript is required. Enable JavaScript to use OAM Server.</p></noscript>

”

JavaScript is enabled on the browsers, however the message keeps appearing. Installing Bundle Patch 2 for OAM 11.1.1.5, resolves the issue.

2         Oracle Patch Installation

2.1       Download OAM Patch

If you do not yet have BP02 Patch for OAM 11.1.1.5 (“p13115859_111150_Generic.zip”), please follow the instructions below to download the patch. Otherwise continue onto the next step, 2.2.

1.       Go to http://support.oracle.com and login with your valid Oracle Support login credentials

2.       Open the “Patches & Updates” tab.

3.       Fill in “13115859” into the “Patch Number” field, then click the “Search” button.

4.       Click on patch “13115859” and click the “Download” button to download the file.

2.2       Load and Unzip the OAM Patch onto Server’s File System

1.       Put the patch’s zip file in a short directory path like D:\Oracle\Patches\…

2.       Unzip the patch so you have a file structure similar to D:\Oracle\Patches\13115859

2.3       Shutdown all OAM Fusion Middleware Servers

1.       Shutdown managed OAM Server

2.       Shutdown OAM WebGate (If necessary)

3.       Shutdown OAM Domain’s AdminServer

2.4       Backup RREG.tar.gz to a backup location

%OAM_ORACLE_HOME% = OAM Oracle Home.  The path can be something similar to: D:\Oracle\Middleware\Oracle_OAM

1.       Copy the file: “%ORACLE_HOME%/oam/server/rreg/client/RREG.tar.gz”

2.       Create the following directory tree to store RREG.tar.gz: “%ORACLE_HOME%/backup/oam/server/rreg/client/RREG.tar.gz”

2.5       Backup %OAM_DOMAIN_HOME% files

%OAM_DOMAIN_HOME% is the OAM WebLogic Domain Home. It should be something like “D:\Oracle\Middleware\user_projects\domains\oamdomain”.

1.       Navigate %OAM_Domain_Home%/config/fmwconfig/mbeans/oam

2.       Make a copy of the “config.jar” file with the filename “config.jar.13115859”

3.       Make a copy of the file “mapstore-coherence.jar” with the filename “mapstore-coherence.jar.13115859”

2.6       Backup %OAM_ORACLE_HOME% and %OAM_DOMAIN_HOME%

Take a complete file structure backup OAM’s ORACLE_HOME and DOMAIN_HOME.

%OAM_RACLE HOME% can be “D:\Oracle\Middleware\Oracle_OAM”.

%OAM_DOMAIN_HOME% can be “D:\Oracle\Middleware\user_projects\domains\oamdomain”

2.7       Open Command Prompt

Open a command prompt window on the server.

2.8       Set environment variables within Command Prompt

1.       Set “ORACLE_HOME” to the absolute directory path of OAM’s %ORACLE_HOME%.
For example: set ORACLE_HOME=D:\Oracle\Middleware\Oracle_OAM

2.       Set “DOMAIN_HOME” to the absolute directory path of OAM’s %DOMAIN_HOME%.
For example: set DOMAIN_HOME= D:\Oracle\Middleware\user_projects\domains\oamdomain

2.9       Apply Patch via OPatch

1.       In command prompt, cd to the Patch Home, like the example below:
D:\Oracle\Patches\13115859

2.       Run the following command like in the example below:
D:\Oracle\Middleware\Oracle_OAM\OPatch\opatch apply -jdk D:\Java\jdk1.6.0_29

Allow a few minutes for the patch to install.

3.       You will see a warning at the end of the patch installation. This is no error. It is simply a warning stating BP01 patch has been patched over with BP02 patch.

4.       Leave the command prompt window open.

2.10  Run the Script: domainAutomation

1.       Locate “domainAutomation” batch script in the BP02 Patch Folder. It is located in the following directory path: %PATCH_HOME%/13115859/files/oam/server/scripts/opatch

2.       Run the “domainAutomation.bat” script in the command prompt window.

3.       Leave the command prompt window open.

2.11  Backup the oam-config

1.       Navigate to “%Domain_Home%/config/fmwconfig”

2.       Copy “oam-config.xml” to a file name “oam-config.xml.13115859”

2.12  Startup OAM Domain’s AdminServer

Only startup OAM Domain’s Admin WebLogic Server

2.13  Startup WLST from command prompt

1.       Cd to: %ORACLE_HOME%/common/bin.
For example: “D:\Oracle\Middleware\Oracle_OAM\common\bin”

2.       Run the script wlst

3.       Run the connect command: connect(‘%username%’,’%password’,’%host%:%AdminServer_port%’)
For example: connect(‘weblogic’,’Welcome1’,’localhost:7001’)

4.       After you connect, run the following command: patchUpgrade(path=”%OAM_ORACLE_HOME%”)
For example: patchUpgrade(path=” D:\Oracle\Middleware\Oracle_OAM”)
Allow a few seconds for the patch to install.

2.14  Restart the OAM AdminServer

2.15  Startup all remaining OAM servers

OAM Managed Server, OAM WebGate, etc…

3Test your application

There have been many cases where attempting to run a form from Forms Builder (purposes of debugging, testing, etc.) will never load the form in the web browser. The page seems to load indefinitely. The URL in the web browser appears to be strange, e.g. http://localhost:51254/X3mJODZxuhNaw9heH7GByuTd1amw3HKIb1pCfGIfIUOKtYXu

To fix this problem, click into the address bar where the URL is and press the Enter key. This will run the form every time.

NOTE: This issue has been seen with 10g (10gR2), 11gR1, and 11gR2 Forms Builders.

This guide will provide instructions on how to perform tracing for the Oracle Access Manager (OAM) environment. This is useful when trying to debug errors pertaining to OAM and/or using Single Sign-On (not to be confused with Oracle’s Single Sign-On software used before OAM) on a protected ADF, Forms, or Java/JSP application. Using this method will NOT require a shutdown of your WebLogic servers. NOTE: The screenshots were taken from a Windows environment, but this works perfectly in Unix as well.

1. Open up Command Prompt as an administrator
2. Navigate to the %ORACLE_HOME%\common\bin ($ORACLE_HOME/common/bin in Unix) directory using the cd command.
3. Log into WLST:

• Windows: wlst.cmd
• Unix: ./wlst.sh

1. WebLogic username
2. WebLogic password
3. AdminServer URL (Example: t3://server.domain:AdminPort)

1. domainRuntime()
2. setLogLevel(logger=”oracle.oam”,level=”TRACE:16”, persist=”0”, target=”oam_server1”)

1. Restart the OAM managed server
2. Run the following WLST command: setLogLevel(logger=”oracle.oam”,level=”NOTIFICATION:1”, persist=”0”, target=”oam_server1”)

NOTE: You may view the trace level of the OAM managed server at any time in WLST by running the command: listLoggers(pattern=”oracle.oam.*”,target=”oam_server1”). The logger “oracle.oam” will be the one to check.

Source: Oracle Support note 1298296.1.

There is an issue reported with the Forms and Reports 11.1.2.1 configuration at the Access Control step when trying to sync with the Oracle Access Manager (OAM) 11.1.1.7.0 environment. The issue is that when the OAM server information (Hostname, Port, Username, and Password) is entered in, regardless if the information entered is correct or not, the following error is presented:

INST-07543: Could not retrieve OAM information with the given credentials.

Looking in the OAM AdminServer logs also shows the following error:

<OAM-30046><agentvalidate mode failed. Agent does not exist. >

This is a bug reported with OAM 11.1.1.7.0 where even the correct OAM credentials cause this error when configuring Forms and Reports. Fortunately, this bug is only encountered with the validation check within the Forms/Reports Configuration Wizard (config.bat).

As a workaround, close the Configuration Wizard and open up Command Prompt as an administrator. Navigate to the %ORACLE_HOME%\bin directory and start the Configuration Wizard with the following:

config.bat –novalidation

This will turn off all validation checks within the Configuration Wizard. You will be able to successfully complete the Access Control step in the wizard without a problem. WARNING: Make sure all information in the wizard is entered correctly as the wizard will NOT check for any errors or inconsistencies when using the “novalidation” flag. Use the Configuration Wizard at your own risk!

We have performed this workaround in our test environment, and we noticed that everything was configured successfully with the Forms and Reports 11.1.2.1 configuration including the creation of the mod_osso agent required for Forms-OAM synchronization. We have had no problems logging into Forms using OAM as all Single Sign-On functionalities appear to work correctly.

NOTE: This issue has also been reported when configuring Forms with an OAM 11.1.1.5.2 (with BP02) and OAM 11.1.1.5.3 (with BP03) environment.

1.     Minimum System Requirements

1.1.    Supported Operating Systems

1.1.1. Solaris 10 Update 9+ SPARC

1.1.2. Solaris 11 SPARC: All levels supported

1.1.3. Solaris 10 Update 9+ 64-bit

1.1.4. Solaris 11 64-bit: All levels supported

1.2.    *RAM: 8 GB+ (20 GB+ minimum for production environments)

1.3.    File System Mount Requirements:

*Software Mount: One file system mount with at least 80GB free space to store the software

TMPFS space: 4GB+ (Minimum: 1 GB)

*SWAP: 8GB+

Heap space: 8 GB

1.4.    OS User Access Requirements:

1.4.1. OS user to own the software mount

1.4.2. Root user access must be accessible for the installation.

1.5.    IPv6 must be disabled on your network adapter before OAM can be installed. IPv6 is not supported with OAM.

*RAM and File System Mount Specifications: For production systems, please consult PITSS or Oracle on sizing recommendations. The amount of RAM, HDD Space for SWAP and Software Mounts will vary depending on end-user usage and application characteristics. For production environments, a minimum of 20 GB of RAM is required: 4 GB for the WebLogic servers and at least 16 GB for performance for up to 1,000,000 users. Oracle Support note 1468111.1 contains more information.

2.     Other Unix OS Requirements

2.1.    The operating system needs to set Native POSIX Threads Library (NPTL) as the default threads-implementation. To check for us, run the following command:

getconf GNU_LIBPTHREAD_VERSION

The expected results should be: NPTL 2.3.4 or higher.

2.2.    Open File Limits:

“soft nofile” should be atleast 4096
“hard nofile” should be atleast 4096 (65535 is recommended)

3.     Required Packages

Below is a list of packages/libraries that need to be installed prior to installing 11g Forms and Reports. Please note the difference between the processor and release types:

The following environment variables must be set in your profile:

• Solaris x86_64: export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P15 or set the DISPLAY variable to any 64-bit Linux machine
• Solaris SPARC:
• export LC_ALL=C
• export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P15 or set the DISPLAY variable to any 64-bit Linux machine

For more information from Oracle on required package information please go to: http://docs.oracle.com/html/E18558_01/fusion_requirements.htm#BABDGCFA

4.     Database Requirements

4.1.    Database Software

A database for OAM 11g will be needed to store the OAM Repository

Supported Database Versions:

10.2.0.4+

11.1.0.7+

11.2.0.1+

4.2.    A database user with DBA/SYS privileges will need to be accessible.

4.3.    The file tnsnames.ora containing the SID of the database will need to be placed in the server/client in the same location as the other prerequisites.

4.4.    Database Character Set: AL32UTF8

4.5.    Database Parameter Requirements:

·         ag_tm_rpcoesses >= 1

·         db_cache_size >=144M

·         java_pool_size >= 120M

·         shared_pool_size >= 175M

·         open_cursors >= 500

·         db_block_size: 8KB

·         processes >= 500

·         pga_aggregate_target >= 96M

5.     Software Requirements

5.1.    Java JDK 1.7.0_21 (or latest version of Java JDK 7)

5.1.1. Go to http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html

5.1.2. Click on “jdk-7u21-solaris-x64.tar.gz for 64-bit” or “jdk-7u21-solaris-sparcv9.tar.gz for SPARC”

NOTE: This is the page to download the latest JDK version.

NOTE: Java JDK  1.7.0_07 is the minimum required for OAM 11.1.1.7.0 if using Oracle WebLogic Server 10.3.6, but we recommend the latest version of JDK (1.7.0_21+ as it is more current and contains critical security updates.

For UNIX-Based systems we recommend to install this prior to the OAM installation.

5.2.    WebLogic 10.3.6

5.2.1. Can be downloaded from: http://www.oracle.com/technetwork/middleware/ias/downloads/wls-main-097127.html

5.2.2. After accepting the license agreement, scroll down to Oracle WebLogic Server 10.3.6. Do NOT install 12c. You will see a plus box next to “Oracle Weblogic Server 10.3.6”. Click the plus box next to “See all files” and more options will be available.

5.2.3. The “Oracle WebLogic Server 11gR1 (10.3.6) + Coherence Package Installer” is the recommended installer of choice.

5.2.4. Please download the file that corresponds to your system OS.  Note for 64-bit Unix and Windows, the “Generic” Installer will need to be downloaded.

5.3.    Oracle Identity and Access Management 11.1.1.7.0

5.3.1. Can be downloaded from:

http://www.oracle.com/technetwork/middleware/downloads/oid-11g-161194.html

After accepting the license agreement, please download the setup files that correspond to your system OS.

5.4.    Oracle Identity Management 11.1.1.7.0

5.4.1. Can be downloaded from: http://www.oracle.com/technetwork/middleware/downloads/oid-11g-161194.html
After accepting the license agreement, please download the setup file that pertains to your operating system.

5.5.    Repository Creation Utility 11.1.1.7.0

IMPORTANT: RCU is NOT supported to be run from Solaris. RCU is only used to install database schemas for OAM and OID. Access to a Windows or Linux environment is mandatory to run the RCU installer only.

5.5.1. Can be downloaded from:

http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/downloads/bi-downloads-1923016.html

5.5.2. Scroll down until you see “Required Additional Software”. In this section, it will show download links for the Repository Creation Utility 11.1.1.7.0. NOTE: We will not be installing Oracle Business Intelligence 11g.

5.5.3. After accepting the license agreement, please download the setup files that correspond to your system OS.

5.6.    Oracle WebTier Utilities 11.1.1.7

5.6.1. Can be downloaded from:

http://www.oracle.com/technetwork/java/webtier/downloads/index2-303202.html

5.7.    Oracle Access Manager WebGates 11.1.1.7.0

5.7.1. Can be downloaded from:

http://www.oracle.com/technetwork/middleware/downloads/oid-11g-161194.html

After accepting the license agreement, please download the setup files that correspond to your system OS.

If you have any questions on the above, please contact PITSS.

There is no easy way to determine which group a PITSS.CON user belongs to inside PITSS.CON. To find what group a PITSS.CON user belongs to, you can run the following SQL:

1. Log into SQLPLUS (or SQL Developer, Toad) as the MIG user
2. Run the following SQL: select mig_pitsscon_users.user_name,mig_pitsscon_groups.group_name from mig_pitsscon_users inner join mig_pitsscon_groups on mig_pitsscon_users.group_id=mig_pitsscon_groups.group_id;

You should see an output like below:

In the above screenshot, it shows first the name of the PITSS.CON user with the GROUP right below it. For example, the PITSS1 user is a member of the USERS group in PITSS.CON.

In Oracle Forms, there has been a known issue where the following error is presented in the Java console when trying to launch an Oracle Forms application:

“Caused by: java.security.AccessControlException: access denied (java.util.PropertyPermission java.home read)”

When this error appears, the Forms application is unable to launch. When the issue happens, clearing the Java cache has been known to fix the problem. This can happen when hyperthreading is enabled in the client PC who is accessing the Oracle Forms application.

To fix this problem, go into the base.htm file (or webutiljpi.htm) (make a backup first) and remove the following lines:

<!– Registration applet definition (start) –>

<OBJECT classid=”%jpi_classid%”

codebase=”%jpi_codebase%”

WIDTH=”0″

HEIGHT=”0″

HSPACE=”0″

VSPACE=”0″>

<PARAM NAME=”TYPE” VALUE=”%jpi_mimetype%”>

<PARAM NAME=”CODEBASE” VALUE=”%codebase%”>

<PARAM NAME=”CODE” VALUE=”oracle.forms.webutil.common.RegisterWebUtil”

>

<PARAM NAME=”ARCHIVE” VALUE=”%webUtilArchive%” >

<COMMENT>

<EMBED SRC=”" PLUGINSPAGE=”%jpi_download_page%”

TYPE=”%jpi_mimetype%”

java_codebase=”%codebase%”

java_code=”oracle.forms.webutil.common.RegisterWebUtil”

java_archive=”%webUtilArchive%”

WIDTH=”1″

HEIGHT=”1″

HSPACE=”0″

VSPACE=”0″

>

<NOEMBED>

</COMMENT>

</NOEMBED></EMBED>

</OBJECT>

<!– Registration applet definition (end) –>

Save and close the file. You should be able to run the Oracle Forms application successfully without having the exception appear in the Java console. If the problem still continues, you may need to clear the Java cache one more time and/or restart WLS_FORMS first.

Source: Oracle Support Note 601534.1

NOTE: This only applies when upgrading Forms and Reports from 11.1.2.0 to 11.1.2.1.

After a successful upgrade of Forms and Reports 11gR2 from 11.1.2.0 to 11.1.2.1, we successfully start up the WebLogic servers. Due to the REP-52262 bug in Forms 11.1.2.1, we apply the workaround as mentioned in http://pitss.com/us/2012/12/20/running-reports-in-formsreports-11-1-2-1-generates-rep-52262-with-default-settings/. After restarting the WLS_REPORTS server, if we try to run a report, we get errors such as “Error 500 – Internal Server Error”.

What we notice in %DOMAIN_HOME%\config\fmwconfig\servers\WLS_REPORTS\applications\reports_11.1.2\configuration, the rwnetwork.conf, rwserver.conf, and rwservlet.properties are backed up and replaced:

In the three updated configuration files, all directories and server names are replaced with environment variables. You can see the screenshot below as an example as taken from the automatically updated rwservlet.properties:

Steps to Reproduce:

1. Upgrade Oracle WebLogic Server from 10.3.5 to 10.3.6
2. Upgrade Oracle Forms and Reports 11gR2 from 11.1.2.0 to 11.1.2.1
3. Start up the WebLogic Servers
4. Apply the REP-52262 workaround based off our KB article at the beginning of this article
5. Restart WLS_REPORTS
6. Glitch happens here.

Fix: Due to these updates, nothing reports-related can run. To fix the problem, you can complete the following steps:

1. Shut down WLS_REPORTS
2. Delete rwnetwork.conf, rwserver.conf, and rwservlet.properties
3. Rename the backups rwnetwork.conf.bak, rwserver.conf.bak, and rwservlet.properties.bak to rwnetwork.conf, rwserver.conf, and rwservlet.properties respectively.
4. Start up WLS_REPORTS

After completing the above steps, you will be able to run reports without a problem.

1.     Minimum System Requirements

1.1.    Oracle Supported DB Platforms (32-bit):

1.1.1. Windows XP

1.1.2. Windows 7

1.1.3. Windows Server 2003

1.1.4. Windows Server 2003 R2

1.1.5. Windows Server 2008

1.2.    Oracle Support DB Platforms (64-bit):

1.2.1. Windows XP

1.2.2. Windows 7

1.2.3. Windows Server 2003

1.2.4. Windows Server 2003 R2

1.2.5. Windows Server 2008

1.2.6. Windows Server 2008 R2

1.3.    *RAM: 2 GB+ (16GB+ for production environments)

1.4.    Virtual Memory: 4 GB+ (8GB+ for production environments)

1.5.    HDD Partitioning:

*Software Mount: One file system mount with at least 10 GB of free space to store the software and temporary file storage for servers. This value could be significantly higher (hundreds of GB if not TB) depending on the size of the data.

1.6.    OS User Access Requirements:

1.6.1. The operating system user that is used for the installation must have Administrative privileges on the machine and “Full Access” to the file system directory where 11gR2 Oracle Database will be installed.

*RAM and File System Mount Specifications: For production systems, please consult PITSS or Oracle on sizing recommendations. The amount of RAM, HDD Space for SWAP and Software Mounts will vary depending on end-user usage and application characteristics such as the expected size of the data tablespaces you plan to use.

2.     Software Requirements

2.1.    Oracle Database 11gR2 (11.2.0.1)

2.1.1. Can be downloaded from:

http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html

2.1.2. After accepting the license agreement, please download the setup files that correspond to your system OS.

If you have any questions on the above, please contact PITSS.

1.     Minimum System Requirements

1.1.    Oracle Supported DB Platforms (32-bit):

1.1.1. Oracle/Red Hat Linux 4: UL7+

1.1.1.1.              Kernel Requirements: 2.6.9 or later

1.1.2. Oracle/Red Hat Linux 5: UL2+

1.1.2.1.              Kernel Requirements: 2.6.18 or later

1.1.3. Oracle/Red Hat Linux 6 (Only with Oracle Database 11.2.0.3)

1.1.3.1.              Kernel Requirements: Oracle Linux 6: 2.6.32.100 or later

1.1.3.2.              Kernel Requirements: RHEL 6: 2.6.32-71 or later

1.1.4. SUSE Linux 10 SP2

1.1.4.1.              Kernel Requirements: 2.6.16.21 or later

1.1.5. SUSE Linux 11

1.1.5.1.              Kernel  Requirements: 2.6.27.19 or later

1.2.    Oracle Support DB Platforms (64-bit):

1.2.1. Oracle/Red Hat Linux 4: UL7+

1.2.1.1.              Kernel Requirements: 2.6.9 or later

1.2.2. Oracle/Red Hat Linux 5: UL2+

1.2.2.1.              Kernel Requirements: Oracle Linux 5 UL2: 2.6.18 or later

1.2.2.2.              Kernel Requirements: Oracle Linux 5 UL5+: 2.6.32-100.0.19 or later

1.2.2.3.              Kernel Requirements: RHEL 5: 2.6.32 or later

1.2.3. Oracle/Red Hat Linux 6 (Only with Oracle Database 11.2.0.3)

1.2.3.1.              Kernel Requirements: Oracle Linux 6: 2.6.32-100.28.5.el6.x86_64 or later (2.6.32-71.el6.x86_64 or later if using Red Hat Compatible Kernel)

1.2.3.2.              Kernel Requirements: RHEL 6: 2.6.32-71.el6.x86_64 or later (2.6.32-100.28.5.el6.x86_64 or later if using the Oracle Unbreakable Enterprise Kernel)

1.2.4. SUSE Linux 10 SP2

1.2.4.1.              Kernel Requirements: 2.6.16.21 or later

1.2.5. SUSE Linux 11

1.2.5.1.              Kernel  Requirements: 2.6.27.19 or later

NOTE: To check kernel requirements, run “uname –r”

1.3.    *RAM: 2 GB+ (8 GB+ for production environments)

1.4.    Virtual Memory: 4 GB+ (16 GB+ for production environments)

1.5.    HDD Partitioning:

*Software Mount: One file system mount with at least 10 GB of free space to store the software and temporary file storage for servers. This value could be significantly higher (hundreds of GB if not TB) depending on the size of the data.

TEMPFS Space: 4GB+ (Minimum: 1GB+)

*SWAP: 2-16 GB (equal to amount of RAM if between 2-16 GB RAM; 16 GB if more than 16 GB of RAM)

1.6.    OS User Access Requirements:

1.6.1. OS User will need to own the software mount.

1.6.2. Root user access must be accessible for the installation.

*RAM and File System Mount Specifications: For production systems, please consult PITSS or Oracle on sizing recommendations. The amount of RAM, HDD Space for SWAP and Software Mounts will vary depending on end-user usage and application characteristics such as the expected size of the data tablespaces you plan to use.

2.     Other Linux OS Requirements

2.1.    Open File Limits:

“soft nproc” should be at least 2047
“hard nproc” should be at least 16384

“soft nofile” should be at least 1024
“hard nofile” should be 65536

“soft stack” should be at least 10240

3.     Required Linux Packages

3.1. Oracle/Red Hat Enterprise Linux 4 32-bit

The minimum versions of the packages below will need to be installed before the Database 11gR2 installation can begin:

For more information from Oracle on required packages please go to: http://docs.oracle.com/cd/E11882_01/install.112/e24324/toc.htm#CHDHFGBJ

3.2. Red Hat and Oracle Enterprise Linux 5 32-bit:

The minimum versions of the packages below will need to be installed before the Database 11gR2 installation can begin:

For more information from Oracle on required packages please go to: http://docs.oracle.com/cd/E11882_01/install.112/e24324/toc.htm#CHDHFGBJ

3.3. RedHat and Oracle Enterprise Linux 6 32-bit:

The minimum versions of the packages below will need to be installed before the Database 11gR2 installation can begin:

For more information from Oracle on required packages please go to: http://docs.oracle.com/cd/E11882_01/install.112/e24324/toc.htm#CHDHFGBJ

3.4. SUSE Linux 10 32-bit:

The minimum versions of the packages below will need to be installed before the Database 11gR2 installation can begin:

For more information from Oracle on required packages please go to: http://docs.oracle.com/cd/E11882_01/install.112/e24324/toc.htm#CHDHFGBJ

3.5. SUSE Linux 11 32-bit:

The minimum versions of the packages below will need to be installed before the Database 11gR2 installation can begin:

For more information from Oracle on required packages please go to: http://docs.oracle.com/cd/E11882_01/install.112/e24324/toc.htm#CHDHFGBJ

                NOTE: To see what packages are installed, enter “rpm –q package_name”.

3.6. Oracle/Red Hat Enterprise Linux 4 64-bit

The minimum versions of the packages below will need to be installed before the Database 11gR2 installation can begin:

For more information from Oracle on required packages please go to: http://docs.oracle.com/cd/E11882_01/install.112/e24326/toc.htm#BHCGJCEA

3.7. Red Hat and Oracle Enterprise Linux 5 64-bit:

The minimum versions of the packages below will need to be installed before the Database 11gR2 installation can begin:

For more information from Oracle on required packages please go to: http://docs.oracle.com/cd/E11882_01/install.112/e24326/toc.htm#BHCGJCEA

3.8. RedHat and Oracle Enterprise Linux 6 64-bit:

The minimum versions of the packages below will need to be installed before the Database 11gR2 installation can begin:

For more information from Oracle on required packages please go to: http://docs.oracle.com/cd/E11882_01/install.112/e24326/toc.htm#BHCGJCEA

3.9. SUSE Linux 10 64-bit:

The minimum versions of the packages below will need to be installed before the Database 11gR2 installation can begin:

For more information from Oracle on required packages please go to: http://docs.oracle.com/cd/E11882_01/install.112/e24326/toc.htm#BHCGJCEA

3.10.                 SUSE Linux 11 64-bit:

The minimum versions of the packages below will need to be installed before the Database 11gR2 installation can begin:

For more information from Oracle on required packages please go to: http://docs.oracle.com/cd/E11882_01/install.112/e24326/toc.htm#BHCGJCEA

                NOTE: To see what packages are installed, enter “rpm –q package_name”.

4.     Software Requirements

4.1.    Oracle Database 11gR2 (11.2.0.1)

4.1.1. Can be downloaded from:

http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html

4.1.2. After accepting the license agreement, please download the setup files that correspond to your system OS.

If you have any questions on the above, please contact PITSS.