Wednesday, February 10, 2016

Oracle: J2SE Runtime Environment 5.0 Update 10 Installer giving "Error 1722. There is a problem with this Windows Installer package"

Local system(Client): Windows 7 64 bit, SP1
Oracle Application Instance : R12.1.3
Application server: JRE version: 1.7.0_85-b31
Application server: Java plugin: 1.5.0_10

When we launch forms from home page of an application, sometimes it asks to install "oaj2se.exe" file. When we try to install it, it gives us below error message:


When we reach up to this stage, then on clicking on OK button above, it will do some sort of partial installation. Hence, we have to remove this manually.

Go to Control Panel - Programs and Features

Search "j2se"


Remove this program as usual, by right clicking and choosing Uninstall.

Once removed completely, then go to folder where "oaj2se.exe" file was downloaded. Right click on it and choose "Run as administrator"



Now, this time installation should go smoothly.

Note: You might get a message "Java Virtual Machine Launcher: Could not find the main class. Program will exit" as shown below, but i don't think that it will cause any issues.


Hope this was useful.




Monday, July 28, 2014

Oracle JDeveloper 11g 11.1.1.7.2 Installation, Error - "Could not locate the launcher command"

Operating System version(Client): Windows 7 Professional, Service Pack 1
Two versions of JRE's installed in the system(Client):
1. Earlier "1.6.0_71" version was present.
2. Now, due to system security updates, "1.7.0_55" version was installed.

For installing Oracle Jdeveloper 11g for ADF customization, downloaded zip file. When extracted zip file and tried installing "jdevstudio11117install.exe" by double clicking on it, it shows window:
1. Preparing the installer


2. "Could not locate the launcher command"


Please use the below workaround:

Run "jdevstudio11117install.exe" as Administrator


Hopefully this should resolve your issue.



Wednesday, February 5, 2014

JRE 1.7.0_51, Windows 7, Error "FRM-92095: Oracle JInitiator version too low. Please install version 1.1.8.2 or higher."

Operating System version(Client): Windows 7 Professional, Service Pack 1
Internet Explorer version: 8
Two versions of JRE's installed in the system(Client):
1. Earlier "1.6.0_71" version was present.
2. Now, due to system security updates, "1.7.0_51" version was installed.
eBusiness Suite JRE version: 1.6.0_24

When i try to launch forms applet from e-Business Suite home page, it gives me a pop up:



Please use below workaround:

Go to Control Panel ==> Java


Go to Java tab and View




Add below string in the Runtime parameters corresponding to 1.7.
-Djava.vendor="Sun Micrososystems Inc."



Click on OK to save.
Now, this part is important. Go to Start menu, type "Internet Explorer"



Please open eBusiness Suite with 64-bit version of Internet Explorer only.

Hope this workaround helps.

JRE 1.7.0_51, Windows 7, Error "Your security settings have blocked a self-signed application from running"

Operating System version: Windows 7 Professional, Service Pack 1
Internet Explorer version: 8
Two versions of JRE's installed in the system:
1. Earlier "1.6.0_71" version was present.
2. Now, due to system security updates, "1.7.0_51" version was installed.


When i try to launch forms applet from e-Business Suite home page, it gives me a pop up:



On clicking on "OK", it gives me another pop up message and does not launch forms applet:



Note: Please note that Location has been edited for security purpose and has been replaced with dummy location "http://xyz:xx.yy.local:8000".

We can use a small workaround to resolve this.

Go to Control Panel ==> Java



Go to Security tab



There is a option "Edit Site List", just click on this option and add your URL, like in our example, it should be "http://xyz:xx.yy.local:8000".
Note: While Adding new value for site under exception site list, make sure that URL is valid, otherwise you won't be allowed to save the value. You cannot save any random/invalid value here.



Hope same workaround works for you also.

Sunday, September 22, 2013

Windows 7, PLSQL Developer, Connect Error "ORA-12154: TNS:could not resolve the connect identifier specified"

Operating System version: Windows 7 Professional, Service Pack 1
PLSQL Developer version: 7.0.0.1050

While trying to connect PLSQL developer to a remote database, we might encounter below error:



We have already verified that PLSQL developer is correctly pointing to correct oracle home which contains all the connection entries in tnsnames.ora file needed to connect to remote database.

Generally, whenever we install a new software in Windows 7 operating system, it installs it in "C:\Program Files (x86)", instead of "C:\Program Files".

Resolution is very weird for this issue. We have moved the installed PLSQL developer folder from  "C:\Program Files (x86)" to "C:\Program Files". Now, we started PLSQL executable and we were able to connect to remote database successfully.

Friday, January 25, 2013

Enable/Disable Concurrent Program Parameters

EBS Release : Oracle Applications : 12.1.3

This post is aimed at helping in enabling/disabling concurrent program parameters. This solution focuses on below requirements:

  1. There are two concurrent program parameters, one which has list of values as associated value set attached, whereas second parameter is such that it is free NUMBER type field.
  2. Whenever users choose concurrent program(View - Requests - Submit a New Request - Single Request), both fields must be enabled initially.
  3. Whenever users populate first parameter, second parameter should become disabled.
Let us consider a use case scenario. Suppose you are required to update attributes of HZ_PARTIES table based upon certain logic. So, you can either required to pass unique value to update attributes for that particular PARTY_NUMBER or you can update for all. But Business has advised that due to huge amount of data, they like to have parameter such that number records can be restricted. A new concurrent program has to be created to do the same.

Here is synopsis of the solution:
  1. Create a new concurrent program(let's name it as "XX: AR Update Parties Attributes")
  2. Two concurrent program parameters viz. "Party Number" and "Number of Records to Process"


Step1:
Create required value sets
Navigate to responsibility: System Administrator
Application - Validation - Set

Define Value set "XX_AR_PARTIES_VS" as defined in below screenshots:





Define value set "XX_DUMMY_VS" as define in below screenshots:



Define value set "XX_ENABLE_DISABLE_SPECIAL_NUMBER_VS" as defined in below screenshots:



Add below in Event as "Validate"

FND PLSQL "BEGIN
IF ':$FLEX$.XX_DUMMY_VS' IS NOT NULL THEN
NULL;
END IF;
END;"





Step2:

Create executable, concurrent program, parameters and attach value sets to parameters.

Navigate to responsibility: System Administrator
Concurrent - Program - Executable



Please do not worry about execution file name or logic of program. This has been created only for the name sake. We are only interested in behavior of concurrent program parameters when viewed from SRS(Standard Request Submission Form)

Navigate to responsibility: System Administrator
Concurrent - Program - Define






Value entered in as Default Value "SELECT 'N' from dual where :$FLEX$.XX_AR_PARTIES_VS:NULL IS NULL"



While saving record, click on OK for the error message



Register concurrent program to appropriate request group(Navigate to responsibility: System Administrator, Security - Responsibility - Request)

Navigate to responsibility, where you have registered concurrent program
View - Requests - Submit a New Request - Single Request - Choose concurrent program "XX: AR Update Parties Attributes"



Enter value for "Party Number"



Now, clear the value for Party Number, it should enable Number of Records to Process parameter




You have just learned how to enable/disable concurrent program parameters.

Monday, January 21, 2013

Java - Error Encountered - Warning: Can't read AppletViewer properties file

JDK: External version 6, Internal version 1.6.0 update 25


Warning: Can't read AppletViewer properties file: C:\Documents and Settings\munish\.hotjava\properties Using defaults.

Command:
D:\>appletviewer Applet.html

Resolution:
I ran the same command again and it worked fine. I think that particular thing was created in first run.