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)
SPACE MANAGEMENT :: 1. Table space usuage: ============== SELECT tablespaces.tablespace_name, allocated.total_alloc allocated_mb, ...
-
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...
-
A nice story about RMAN. The story begins, when one of my associate DBAs did an RMAN restoration & recovery 2 days back...
-
Recently, I got a complaint from my AS10g users, that they are facing frequent disconnection with the server. May be due to network distrupt...
No comments:
Post a Comment
Kindly make your valuable and progressive comments here.
Junks will be deleted without notice :-)