At the bottom of the Module Handling window, you may see the error “Updating of modules completed with errors.”

NOTE: In PITSS.CON 12.1.3, you may see instead a glitch where the update says it completes, but the library is not actually updated:

In this case, the “Fmb Old Path” in the INIT_PARAMETER table for the PITSS.CON user is set incorrectly. It should be set to the user’s old directory. The screenshot below shows it set incorrectly:

To change the path, double-click in the text box next to Path Name. A dialog window will appear. Make sure you are in your PITSS.CON user folder. Next, select the “old” directory and click “Open”.

The path name will now be the correct directory. Click on another path location to save the changes.

Return to Module Handling. You should be able to successfully update the libraries back to the file system:

This is because the later versions of Android SDK (ADT bundle) moved the SDK Home to the location “Android/android-sdk/sdk” directory. Instead of “Android/android-sdk“, as shown below.

Selecting the proper SDK location, lets you continue error free.

You might run into an ADF Mobile deployment error below:

Cannot run program “… platform-tools\aapt”

CreateProcess error=2, The system cannot find the file specified.

The cause of the error was that the “Android SDK Tools” was updated from Rev. 21.1 to Rev 22. 

The reason Rev. 22 causes the error is more on the side of JDeveloper. It moved appt.exe to a different directory, however you can’t configure JDeveloper where to find this executable.

To fix the issue, take your SDK version back to Rev. 21.1, by extracting the Rev 21.1 zip. You will have to re-install the Android APIs, but it shouldn’t take long to get re-setup. However, if you want use Rev 22, copy the contents of %SDK_Home%/build-tools/android-4.2.2 to%SDK_Home%/platform-tools.

Until Oracle changes how JDeveloper can find the binary, you can use this workaround!

Update (05/21/2013): Per Chris Muir, ADF Product Manager, this issue has been officially logged at Oracle as a bug 168376554. You can monitor the status of this bug in My Oracle Support (http://support.oracle.com) – as long as you have access to viewing Oracle Bugs.
Source: https://blogs.oracle.com/onesizedoesntfitall/entry/adf_mobile_deploying_to_android

The latest release of JDeveloper 11.1.2.4, brought some new issues to address for the installation process. Below is a guide on making your 11.1.2.4 JDeveloper installation a breeze.

1. Download and Install JDK 1.6.0_39+ or higher. I installed JDK 1.6.0_43.
   Java Download Location: http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase6-419409.html
   Note: Even if you download the JDEveloper installation kit with a bundled JDK, the bundled JDK will not work. This is because Oracle bundled in an unsupported JDK version. Installing the wrong JDK will result in an error message when trying to start up JDeveloper
   
   
2. Download the JDeveloper 11.1.2.4 release that applies to your system. If you do not know which type to get, the “Generic” installer will always work.
   Download location: http://www.oracle.com/technetwork/developer-tools/jdev/downloads/index.html
   Note: Mac OS X users must download the “Generic” Installer.
   
   
3. Start up the JDeveloper 11.1.2.4 Installer
   For those whom downloaded the Windows JDeveloper Installation kit, simply double click on the “jdevstudio11124install.exe” installer.
   For “generic” jar folks: either double click on the jar, or run the command “%JAVA_JDK_HOME%/bin/java -jar name_of_jar_file.jar” in your command-line utility.
   Note: %JAVA_JDK_HOME% should be replaced with actual file system installation path of your JDK 6. and
   
   
4. Choose your Middleware Home Directory. Make sure the directory you chose is clean/empty. For instance, I have multiple JDevelopers installed. Thus i have a separate middleware home for each JDeveloper install – to keep each environment clean.
   
   
5. At the “Choose Install Type” screen, select “Custom“.
   
   
6. At the “Products and Components” screen, leave all options checked unless you have a preference otherwise.
   
   
7. The following steps are very important, please follow carefully!
   
8. At the “JDK Selection” screen, uncheck the SUN JDK 1.6.0_24. (Its not supported to run JDeveloper 11.1.2.4!)
   
   
9. In the “JDK Selection” screen, click “Browse” to locate the JAVA_HOME of your JDK 1.6.0_39+. Click “Select” on the JDK Home.

   

10. After selecting your JDK Home, your JDK should show up under “Local JDK”, as shown below. You can now proceed to the next screen!
    
    
11. Confirm your “Product Installation Directories”. and click through the rest of the installer and you have a vanilla installation!

Important For ADF Mobile Developers:

1. Use the JDeveloper “Help > Check for Updates” utility to download the ADF Mobile Bundle – its quick and easy to do.
   
2. If you are developer native OS apps for Android devices, you need to go into your Android SDK Manager, and download the “Google Cloud Messaging for Android Library“, as shown below.
   

   If you do not download this SDK component, you’ll be greeted with deployment errors in JDeveloper:
   Failed to locate the Google Cloud Messaging for Android Library file named “gcm.jar”. (oracle.adfmf.framework.dt.deploy.android.deployers.ValidatePreferencesDeployer)
   

If you have any questions, please contact PITSS.

Oracle Database 11gR2 Setup Prerequisites for IBM AIX on POWER Systems

1.     Minimum System Requirements

1.1.    Oracle Supported DB Platforms:

1.1.1. Version 5.3 UL 9+

1.1.2. Version 6.1 UL2+

1.1.3. Version 7.1 UL0+

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

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

1.4.    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.5.    OS User Access Requirements:

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

1.5.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 Unix 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 AIX Packages

3.1.    Below is a list of packages/libraries that need to be installed prior to installing Oracle Database 11gR2. Please note the difference between the release types.

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

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.

Oracle Database 11gR2 Setup Prerequisites for Solaris

1.     Minimum System Requirements

1.1.    Oracle Supported DB Platforms (x86_64):

1.1.1. Solaris 10 Update 6+

1.1.2. Solaris 11 (Oracle Database 11.2.0.3 only)

1.2.    Oracle Support DB Platforms (SPARC):

1.2.1. Solaris 10 Update 6+

1.2.2. Solaris 11 (Oracle Database 11.2.0.3 only)

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 Solaris 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 Packages

3.1.    Below is a list of packages/libraries that need to be installed prior to installing Oracle Database 11gR2. Please note the difference between the processor and release types

For Solaris 11 (SPARC or x86_64), the following fonts will need to be installed:

• system/font/daewoo-misc
• system/font/gnome-fonts
• system/font/isas-misc
• system/font/jis-misc
• system/font/misc-ethiopic
• system/font/misc-meltho
• system/font/sun-ja-bitmap
• system/font/sun-ja-bitmap-unicode
• system/font/truetype/arphic-ukai
• system/font/truetype/bh-luxi
• system/font/truetype/bitstream-vera
• system/font/truetype/fonts-core
• system/font/truetype/gentium
• system/font/truetype/google-droid
• system/font/truetype/hanyang-ko
• system/font/truetype/ipafont-mincho
• system/font/truetype/sil
• system/font/truetype/unfonts-ko-core
• system/font/truetype/unfonts-ko-extra
• system/font/truetype/unifont
• system/font/truetype/wqy-zenhei
• system/font/xorg/cyrillic
• system/font/xorg/iso8859-10
• system/font/xorg/iso8859-11
• system/font/xorg/iso8859-13
• system/font/xorg/iso8859-14
• system/font/xorg/iso8859-15
• system/font/xorg/iso8859-16
• system/font/xorg/iso8859-2
• system/font/xorg/iso8859-3
• system/font/xorg/iso8859-4
• system/font/xorg/iso8859-5
• system/font/xorg/iso8859-7
• system/font/xorg/iso8859-8
• system/font/xorg/iso8859-9

After the fonts are installed, 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/cd/E11882_01/install.112/e24351/toc.htm#CHDHFGBJ (x86-64)

http://docs.oracle.com/cd/E11882_01/install.112/e24349/toc.htm#CHDHFGBJ (SPARC)

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.

Oracle Database 11gR2 Setup Prerequisites for Linux

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.

Oracle Database 11gR2 Setup Prerequisites for Windows

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.

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.

“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