How to reset Admin’s Password in Oracle Application Express
Posted by Admin on July 2, 2010
Sorry, I am moving into http://levicorp.com/2010/07/02/how-to-reset-password-in-apex/
Levicorp's WebNote Moving into http://levicorp.com
Just another web note
Hear This
Recent Posts
- HOW TO: Create Filesystem and ImportVG on IBM-AIX
- How to reset Admin’s Password in Oracle Application Express
- Troubleshooting during Migration DB and Apps
- MIGRATION Oracle EBS 11.5.9 with Database 10g Part III
- Configuring VLM for Oracle Database
- Recover the Database without Archive Log
- Oracle Forms 10g Using SUN JRE
- Migration Oracle 10g DB From Linux 32bit to Linux 64bit
- Move or Rename the Datafile in Oracle
- How to Extend Or Reduce Logical Volume in Linux
-
-
Farook said
We upgraded from JIinitiator to JRE in 11.5.9 CU2. Every thing is OK, but sometimes the forms applet hangs. Can you please give any suggestion regarding this.
Admin said
Hi Farook, May i know which version JRE that you used? there is some hang issue in some JRE version. JDK 6 Update 18 (1.6.0_18) is stable version that I have used. so far no issue with this version.
Farook said
i tried totally 3 version, same issue on all the three.
1.5.0_22
1.5.0_17
1.6.0_20 which is the current version.
So now we went back to JInitiator 1.3.1.30, which works fine
Admin said
Where did you try it? in server side or client side? actually JRE version should be installed in client side. so please check the version of your pc JRE.
Farook said
Inclient Only.
Admin said
The similar issue you can find it in steve chan blog, recommend version 1.6.0_17 :
Warning: E-Business Suite Issues with Sun JRE 1.6.0_19
By Steven Chan on April 5, 2010 8:50 AM
Sadly, the issues reported in the following article also apply to JRE 1.6.0_19:
•Warning: E-Business Suite Issues with Sun JRE 1.6.0_18
Once again, if you haven’t already upgraded your end-users to JRE 1.6.0_18 or 1.6.0_19, we recommend that you to keep them on a prior JRE release such as 1.6.0_17 (6u17).
We’re working closely with the Sun JRE team to get this issue resolved as quickly as possible. Please monitor this blog for updates.