R12 Cloning Issues - Very common post Clone Issues:
As I have already discussed about database and application cloning in my previous post and also you can look into below link for cloning:
Now I would like to discuss about some common post clone issues of application
1) Getting no manager and Standard manager not up:
· First check custom.env at appl_top and if not present create custome.env
· source env. Again
· restart all the services of application
· test the issue by checking the status of concurrent manager
2) Oracle APPS R12 Post Cloning issue - Form not launching :
Introduction:
After the successful cloning of R12.1.1, when opening the form, it was not launching.
After troubleshooting with the following steps, form started working fine.
1- Stopped the APPS Tier services.
2- rename the directory "tldcache" under following directories.
a- $ORA_CONFIG_HOME/10.1.3/j2ee/oafm/tldcache
b- $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/tldcache
c- $ORA_CONFIG_HOME/10.1.3/j2ee/forms/tldcache
3- create the emplty directory with the name "tldcache" under the above directories.
4- restart the APPS Tier services.
5- test the issue with starting some forms.
3) log/out files are not getting generated:
For fixing this issue, need to do the following steps:
· stop all concurrent services
· login with functional administrator responsibility.
· Navigate to profile/system
· search for %RRA Enabled%
· set the value to “yes” and save it
· start the concurrent services
· test the issue
No comments:
Post a Comment