In this posting, we learn how to reset Admin’s Password in Oracle Application Express (APEX).
1. Collect the information of the FLOWS% schema
$ sqlplus '/as sysdba'
SQL> select username,password,account_status from dba_users 2 where username like 'FLOW%'; USERNAME PASSWORD ACCOUNT_STATUS ---------------- ------------------ ---------------- FLOWS_020200 569054L59C7186CB LOCKED FLOWS_030000 240C2BE199B3DB1F LOCKED FLOWS_010600 EDEA2EV8EEE12B6F LOCKED FLOWS_FILES 4D6011I6ACC3FBF2 LOCKED
2. Unlock the latest FLOWS% schema that we used currently.
SQL> alter user FLOWS_030000 account unlock; User altered.
3. Change the password of FLOWS% Schema temporarily
SQL> alter user FLOWS_030000 identified by levicorp01; User altered.
4. Login to FLOWS% Schema
SQL> conn FLOWS_030000/levicorp01 Connected.
5. Create user in Internal Workspace
SQL> BEGIN 2 wwv_flow_api.set_security_group_id(p_security_group_id => 10); 3 wwv_flow_fnd_user_api.create_fnd_user 4 (p_user_name => 'admin2' 5 ,p_email_address => 'me@levicorp.com' 6 ,p_web_password => 'admin2' 7 ); 8 END; 9 / PL/SQL procedure successfully completed. SQL> commit; Commit complete.
6. Open the applications, Login to Internal Workspace with the new user that we created before
http://levicorpap:7777/pls/htmldb Login : - Workspace : Internal - Username : admin2 - password : admin2
at the first time logon, Apex will ask you to change the password
7. Click the tab “Manage Workspaces”
8. Click the link “Manage Developers and Users”
9. Choose the user that you want to change its password.
10. Input new password in the section “Password”
11. Click button Apply Changes
12. Bring back the password of FLOWS% Schema
SQL> alter user FLOWS_030000 identified by values '240C2B7199B3DB1F'; User altered.
13. Lock again the account of FLOWS% Schema
SQL> alter user FLOWS_030000 account lock; User altered.
14. Done
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.
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.
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
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.
Inclient Only.
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.