Retrieve Apps password in R12 or Forgot Apps Password in R12

Steps to retrieve forgotten apps password in R12.

Step 1 : login to DB-Node

sqlplus / as sysdba

STEP 2 : Create Function for to decrypt the encrypted password


SQL> create FUNCTION apps.decrypt_pin_func(in_chr_key IN VARCHAR2,in_chr_encrypted_pin IN VARCHAR2)
RETURN VARCHAR2
AS
LANGUAGE JAVA NAME 'oracle.apps.fnd.security.WebSessionManagerProc.decrypt(java.lang.String,java.lang.String) return java.lang.String';
/

Function created.

STEP 3 : (Query for password)


SQL> select ENCRYPTED_FOUNDATION_PASSWORD from apps.fnd_user where USER_NAME='GUEST';


Output

ENCRYPTED_FOUNDATION_PASSWORD
--------------------------------------------------------------------------------
ZG37E123746712BDB2D99E048FE44AE662F2713E2EDB443391BABA0414CADDB7A2E6DD45BBAFA7270A663E5EEBA837F5548A

STEP 4:

SELECT apps.decrypt_pin_func('GUEST/ORACLE','ZG37E123746712BDB2D99E048FE44AE662F2713E2EDB443391BABA0414CADDB7A2E6DD45BBAFA7270A663E5EEBA837F5548A') from dual;




Output

APPS.DECRYPT_PIN_FUNC('GUEST/ORACLE','ZG37E123746712BDB2D99E048FE44AE662F2713E2EDB443391BABA0414CADDB7A2E6DD45BBAFA7270A663E5EEBA837F5548A')
--------------------------------------------------------------------------------
DEMONSTRATE

STEP 5: (Test apps password)
SQL> conn apps/DEMONSTRATE;
Connected.

FRD TRACE in R12

Enable FRD Trace for Application User

login to Oracle ebiz R12 as sysadmin.
Navigate to profile options
Enter profile option : ICX: Forms Launcher
Enter User Name : ABC

Copy the url from site level and append ?record=collect to the url and paste the url at user level

http://waseem.learning.com:8000/forms/frmservlet?record=collect

save it.

Provide the url to the user tell user to login using the url mentioned. Reproduce the issue.
once the Issue is reproduced revert back the changes.

location of trace file  : $FORMS_TRACE_DIR is the place where trace file will be generated.
trace file name will be with collect*
uploade the collect* to oracle.
$FORMS_TRACE_DIR = $INST_TOP/logs/ora/10.1.2/forms

After enabling FRD TRACE : User may get the below error messsage after entering login credentials :
Application is not authorized to access the database
Take backup of the context_file
search for the parameter s_appserverid_authentication change the value of this parameter from SECURE to OFF as shown below:

change the value of "s_appserverid_authentication" to OFF from SECURE and run autoconfig
e.g
<appserverid_authentication oa_var="s_appserverid_authentication">SECURE</appserverid_authentication>
to
<appserverid_authentication oa_var="s_appserverid_authentication">OFF</appserverid_authentication>

Stop the Application Services.
Run Autoconfig.
Start the Application Services again.
Inform the user to login and test.

unable to Authenticate the session while opening multiple Instance in IE8

IE 8 Acessing or opening mutiple Instance simultaneously Unable to Authenticate the session

This is an IE Issue.

Solution :
Step 1:

Click on start menu  type run in the search box
You will get a  dialog box: type the below command in run prompt and hit ok or enter Key
iexplore -noframemerging

Another IE explorer will open. open the another ERP Instance.

or

Step 2:

Create a shortcut of IE 8 on your desktop.
Right click on IE icon
Click on Shortcut
in Target field :- append -noframemerging
e.g below:
"C:\Program Files\Internet Explorer\iexplore.exe" -noframemerging

Now click on theIE  shorcut created on desktop and open Instances.

Using IE8 to access two EBS Instances runs in error "Unable To Authenticate Session" [ID 1098563.1]

Time drift detected. Please check VKTM trace file for more details in alert log file

Time drift detected. Please check VKTM trace file for more details.

Message in alert log file. Opening the database takes time

Follow below mentioned the note-id :
Time Drift Detected. Please Check Vktm Trace File For More Details. (Doc ID 1347586.1)

Download and apply patch 11837095 as available for your release/platform.
NOTE:
Patch 11837095 extends to functionality of event 10795 (set to level 2) for VKTM tracing and limits alert log entries.

After applying the patch, enable event 10975 at level 2:
alter system set event="10795 trace name context forever, level 2" scope=spfile;

After applying the patch the issue is fixed.

Below Warning can be ignored while applying opatch:
OPatch found the word "warning" in the stderr of the make command.
Please look at this stderr. You can re-run this make command.
Stderr output:
ld: warning: symbol '_start' has differing types: