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.
Subscribe to:
Post Comments (Atom)
Find below few useful scripts for Performance Management:: # Important MOS notes for TRACING: There are several ways to trace a particul...
-
On a new VIS R12.1 installation, the OHS (oracle http server) failed to start and give status 204. Upon querying the status of opmn manage...
-
Recently when I was tasked to do a cloning of my production Oracle Apps instance to a target single-node server, I hit a dead-end with the ...
-
A nice story about RMAN. The story begins, when one of my associate DBAs did an RMAN restoration & recovery 2 days back...
No comments:
Post a Comment
Kindly make your valuable and progressive comments here.
Junks will be deleted without notice :-)