Wednesday, 13 November 2013

Oracle Apps R12 Forms Not Opening

Oracle Apps R12 Forms Not Opening

The forms for Oracle Apps EBS may not open for many reasons. Follow below steps to find out:-

For a particular Form:-
  1. It displays some message which can help you finding out the cause.
  2. Most of the time its related to some database objects or the particular form executable.
a. Compile all ( Mainly Apps owned ) db objects.
b. Compile particular form executable.

For All forms:-
  1. Always check the DB, and alert log.
  2. Check file system space.
  3. Check Apache and Forms log. $LOG_HOME/10.1.3/Apache/Apache/logs and $LOG_HOME/10.1.2/forms/logs
  4. If you are using R12 with IE8 then check Metalink doc 1069497.1, for Cross Site Scripting(XSS) settings (make it to relevant tab of your internet options). Also check 389422.1 for recommended browsers and settings.
  5. Check timestamp for files like $AU_TOP/resource/CUSTOM.* , this will tell you if someone has modified the pll and then the changes should be reverted back.
  6. Try checking the form sessions from your server as below
    ps -ef | grep frm
    This will show the frmsrv and frmweb processes. If it doesn't then the issue is in spawning form session.
    You can check the timestamp for frmsrv/frmweb executable, if this has got changed. You can relink this by below.
    a. Source the Application environment
    b. from location $ORACLE_HOME/forms/lib
    run :-
    make -f ins_forms.mk install
  7. In other case if from sessions are there and you are not able to open the form, then check the direct form login as below.
    http://server:port/forms/frmservlet - for servlet mode
    http://server:port/OA_HTML/frmservlet - for socket mode
  8. If above works then you can go to adadmin and compile jsps, or can have clear cache bounce.
  9. If step 6 doesn't work then check for dbc file present at $FND_SECURE.
    a. The file should have correct entries for Application Server Id, as it is in FND_NODES table.
    b. All the passwords guest,applsyspub etc are ok, or change the guest password using FNDCPASS
    c. You can correct the dbc file manually, or regenerate using  $COMMON_TOP/admin/install/adgendbc.sh
  10. Bounce forms server and retry
  11. Login: Cannot access jtflogin.jsp nor jtfdefaultlogin.jsp:
You are trying to log into the html stack via jtflogin.jsp or jtfdefaultlogin.jsp.
Jtflogin.jsp does not display the page and returns message 'error in error page'.
Jtfdefaultlogin.jsp also does not display the page and returns message like 'system error' followed by several java messages, the most significant
being 'oracle.apps.jtf.base.session.ServletSessionManagerException'.
You have also tried to run the diagnostics via jtfqalgn.htm and the database connectivity tests fail

Cause #1:

There can be several reasons for this problem scenario, including  configuration files not being correct for httpd.conf, jserv.conf,
jserv.properties, and zone.properties.
The following solution is for correcting one specific condition where your  .dbc  file has been manually edited, looks correct but the
connectivity issue persists.
To eliminate this possibility, please perform the following procedure:
Why do we want to do this procedure ?
Because if you have ever manually edited the  .dbc  file,  you may have unknowingly inserted/deleted
some character/space/line feed/carriage return/tab/etc.
Do not manually edit your  .dbc  file. Results are unpredictable and can take a long time to diagnose.

Resolution: 

Perform the following query:


SQL> select * from fnd_application_servers;
The query should return one (1)  row.  If the query returns more than one row, delete the row(s) that is/are most apparently incorrect.  You will probably be able to recognize the invalid row(s) by the IP address column (server_address) that points to an invalid host database tier.
The authentication string in this table (column server_id) must  match the same string in your  'host_sid'.dbc file  (APPL_SERVER_ID).
Make a backup copy of your  .dbc  file.
To insure that everything is in synch, run the  adgendbc.sh  script located in your $COMMON_TOP\admin\install  directory.  This script takes no parameters except  '-deinstall'  which you probably do not want to do.  This script will assign a new authentication string (server_id), update your  .dbc  file  and update your fnd_application_servers  table.
It's OK if you get an error message related to unique key constraint (read the script file).
Double check the information  in your .dbc file and fnd_application_servers table.  It should be in synch. Display or print the .dbc file. Please do not use an editor because you may forget the rule and save it.

Few Test For Logins :

1.  /OA_HTML/jsp/fnd/aoljtest.jsp
2.  tnsping is command used to check the connectivity to the database server node from other nodes.
Ex: tnsping
Note: Tns entry should be there in tnsnames.ora for the database we are trying to work this command.
3.  FND_WEB.PING

Reference:

1.Troubleshooting Login (Doc ID 178437.1)
2.Troubleshooting Login Problems in Oracle Applications 11i (342332.1).
3.Oracle E-Business Suite R12 – Login Page showing a blank page Occuring Intermittently [ID 1491845.1]

No comments:

Post a Comment