1. What is the use of shared appl_top? Let's assume I have shared my appl_top across 4 nodes. How many times I have to apply ADpatch ?
2. How to re-create corrupted oraInventory ?
3. How do I run autoconfig in test mode ( without changing any files and I want to know what will happen, if I run autoconfig) ?
4. What's the purpose of providing 0 and Y, while changing passwords using FNDCPASS ?
5. What happen if someone deleted FNDLIBR? how to recover ?
6. What are .ldf and .ltc files?
7. How to find out the parameters supplied to JVM ?
8. How to find out the java Classpath in oracle apps ?
9. How to troubleshoot java.lang.NoClassDefFound error ?
10. What could be the reason for "network adapter unable to connect to db" error while doing post clone of appsTier ?
11. What is the purpose of adgendbc.sh file? Syntax for adgendbc.sh ? where it is located?
12. How to fix UTL_FILE error while doing autoconfig?
13. What's the purpose of adbldxml ? Syntax and location.
14. How to find out the status of ICM ? Which script is used for that ?
15. What are the two values given at "compile_all=?" while compiling forms ? what's the significance of each value ?
post your answers quoting the question number.
I will be updating this thread with more questions.
Regards,
Sundar K
State of processes and sessions parameters after clone.
After doing post clone of Oracle EBS 11i/R12, the processes and sessions parameters are re-set to default. That is processes=200 and sessions=300.
In particular to R12.1 instance, 200 number of processes are not enough for a single user to submit a few requests. The requests will throw errors which are not related to "max processes reached". You may find it on alert_log, but if you are monitoring concurrent managers and it's logs then, I bet you won't find anything related to max processes.
It must be a practice to increase the processes and sessions parameters on a newly cloned EBS or set as equal as to that of the source EBS.
Otherwise, concurrent managers will keep you on running on toe and you won't get any clue until, you saw the alert log.
In particular to R12.1 instance, 200 number of processes are not enough for a single user to submit a few requests. The requests will throw errors which are not related to "max processes reached". You may find it on alert_log, but if you are monitoring concurrent managers and it's logs then, I bet you won't find anything related to max processes.
It must be a practice to increase the processes and sessions parameters on a newly cloned EBS or set as equal as to that of the source EBS.
Otherwise, concurrent managers will keep you on running on toe and you won't get any clue until, you saw the alert log.
Subscribe to:
Posts (Atom)