5
1) Unable to access Login Page in Oracle Apps R12 or Login Page appears blank in Oracle Apps R12 ==================================================================== ========= Issue: ------- When trying to access application front-end the Login Page appears blank. Temporary Fix: ---------------- Stop all the application services and clear the cache under COMMON_TOP. Compile all the jsp’s: $cd $FND_TOP/patch/115/bin $perl ojspCompile.pl –compile –flush -p 2 Restart the application services and test the issue. Permanent Fix: Set the parameter “s_jsp_main_mode” in XML file from “just run” to “recompile” <jsp_debug_parameters oa_var=”s_jsp_main_mode”>justrun</jsp_debug_parameters> change it to <jsp_debug_parameters oa_var=”s_jsp_main_mode”>recompile</jsp_debug_parameters> Execute autoconfig to apply the change done in XML File.

Login Issues in Apps

Embed Size (px)

DESCRIPTION

Very Useful to solve Login page issues 11i & R12

Citation preview

Page 1: Login Issues in Apps

1) Unable to access Login Page in Oracle Apps R12 or Login Page appears blank in Oracle Apps R12

=============================================================================

Issue:

-------

When trying to access application front-end the Login Page appears blank.

Temporary Fix:

----------------

Stop all the application services and clear the cache under COMMON_TOP.

Compile all the jsp’s:

$cd $FND_TOP/patch/115/bin

$perl ojspCompile.pl –compile –flush -p 2

Restart the application services and test the issue.

Permanent Fix:

Set the parameter “s_jsp_main_mode” in XML file from “just run” to “recompile”

<jsp_debug_parameters oa_var=”s_jsp_main_mode”>justrun</jsp_debug_parameters>

change it to <jsp_debug_parameters oa_var=”s_jsp_main_mode”>recompile</jsp_debug_parameters>

Execute autoconfig to apply the change done in XML File.

Autoconfig will update file $INST_TOP/ora/10.1.3/j2ee/oacore/application-deployments/oacore/html/orion-web.xml

Re-start the applications and test the issue.

Note: However it is not recommended to change the default value of parameter

s_jsp_main_mode (i.e. just run) as it may lead to performance issue.

Page 2: Login Issues in Apps

R12 Blank Login Page

This may happen some times, mainly after the clone or even after some bounce.

1. The first thing you need to check always is DB is running fine.In case you are are not aware then I must tell you, its better to check if "apps" user is working fine.

1. One more thing you should check is the Alert Log, as there may be issues related to Database.

2. Later comes the Apache logs. Location is "$LOG_HOME/ora/10.1.3/Apache".The files are error_log and access_log, check the latest ones.And if that looks OK.

3. Go for a clear cache bounce.Well in R12 clear cache bounce means clearing the file from -pages directory, and regenerating the .jspBelow link may help you with the process of clear cache bounce at R12.http://tk-appsdba.blogspot.com/2011/01/clear-cache-bounce-in-r12.html

4. And in addition to that we can clear the persistence too. For that :-Delete or move the files under below directories$INST_TOP/ora/10.1.3/j2ee/oacore/persistence $INST_TOP/ora/10.1.3/j2ee/oafm/persistence $INST_TOP/ora/10.1.3/j2ee/forms/persistence

5. Now restart the services and retest the issue.

Page 3: Login Issues in Apps

Clear Cache bounce in R12There are two ways to clear cache in R12.1. Functional level (individual product/all product cache)Functional Administrator -> Core Services -> Caching Framework -> Global Configuration -> "Go to specific cache or Clear All Cache"

2. Server levelIn R12 apache bounce (which is actually opmn services here) takes a little more time then 11i, and we too have to take care of few things.Basic steps for a clear cache bounce is as below:-Set you application environment and go to $ADMIN_SCRIPTS_HOME

1. ./adopmnctl.sh stopall2. wait for command to complete3. ./adopmnctl.sh status -l4. cd $COMMON_TOP/_pages5. ls -l|wc -l (note it down)6. rm -rf * (to remove all files)Note:- For step 4 to 6, better to take backup of _pages by renaming it, and create a new directory as _pages at the same place.7. ls -l|wc -l (it should be 0 now)8. cd $FND_TOP/patch/115/bin9. which perl (should come from $IAS_ORACLE_HOME/perl/bin)10. ojspCompile.pl --compile --flush -p 10 (to compile all JSPs,-p is for parallel and value (i.e. 10 here) can be varied accourding to your server)11. wait for successful completion12. cd $COMMON_TOP/_pages13. ls -l| wc -l (check whether count is same or more than before (pre-remove) - sometimes a little difference may be there)14. Go to $ADMIN_SCRIPTS_HOME again15. ./adopmnctl.sh startall16. wait for proper services startup17. ./adopmnctl.sh status -l18. check front-end and JSPs and FORMs should open up fine

You can avoid the step of regenrating the jsps like 11i but for that we need to make below changes in R12 context file (XML file):

parameter s_jsp_main_mode - you will find it justrun by default.

change it to - recompile

and run autoconfig to make the changes take place.

Page 4: Login Issues in Apps

This will generate the jsps at run time saving bounce time, but obviously affect the performance.4) Oracle apps r12 login error 404 not found

============================================

Login page error: 404 - The url /OA_HTML/AppsLogin not found

The access_log shows no errors. error.log from $LOG_HOME/ora/10.1.3/Apache shows

[Tue Jan 18 11:27:51 2011] [error] [client 123.238.255.152] [ecid: 1295330271:127.0.0.1:10897:0:2,0]

File does not exist: /oracle/CLON/inst/apps/CLON_obaserver/portal/OA_HTML/AppsLogin

I recreated the jar files using adadmin and compiled the jsp using

cd $FND_TOP/patch/115/bin

perl ojspCompile.pl --compile --flush -p 20 -log /tmp/ojspc_error2.log

Nothing worked out.

Fix:

-----

This problem occurred because wsrp_service.wsdl was owned by root but the services were being started by applmgr.

Ensure that the file

$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/application-deployments/oacore/html/server-wsdl/wsrp_service.wsdl

it shows it is owned by root. Somebody started the services of Apps as root user.

Changed the owner of the file to Apps Owner.

Restarted the service.

Page 5: Login Issues in Apps