| SOS - facing problems with concurrent manager [message #184510] |
Wed, 26 July 2006 18:59  |
srkiran23
Messages: 38
Registered: March 2006
|
Member |
|
|
Hi everyone
I use Oracle 11i Financials at home for practice purpose ...I am trying to create a new SOB which supports Multi-Org strcuture but I am having problems…. When I submit request … it says “No active manager” … I went into services and checked if everything are started …. I saw that the one that says “OracleConcMgrVis” doesn’t start at all …. I tried all possibilities like starting myself but after sometime it stops …. I also tried to change the “Startup Type” from Automatic to Manual and restart the system but again the same thing happens.. Please advise me as to what to do …. I cannot continue my practice coz of this.....
your response is solicited ...
thanks
|
|
|
|
|
|
|
|
| Re: SOS - facing problems with concurrent manager [message #184538 is a reply to message #184510] |
Thu, 27 July 2006 00:02  |
manojr
Messages: 38
Registered: January 2006
Location: Pune India
|
Member |
|
|
Hi,
Please find the attached note, and check out if your problem gets resolved
Please
Problem Description
====================
You are having difficulties running concurrent requests and receiving
a status of:
ACTIVE NO MANAGER
Within Oracle Applications, log on as SYSADMIN
Navigate to: Concurrent/Manager/Administer
click on: Conflict Resolution Manager to show the requests.
When a concurrent request is submitted, the requests receive a
status of:
ACTIVE NO MANAGER
Problem Explanation
====================
All requests submitted to the Conflict Resolution Manager are receiving a
status of:
ACTIVE NO MANAGER.
Solution Description
=====================
After reviewing the concurrent processes, it was discovered that
the bar code process had been submitted twice and there were
two different managers that were attempting to process the bar code
requests.
The bar code process was a custom manager and no exclusions
were made against the standard manager for it. Once an
exclusion was made for the standard manager for the requests
running under the bar code manager, the requests were not locked.
Canceling the request running under the standard manager allowed
the bar code process request to run to completion.
Solution Explanation
=====================
When a new manager is created to run a request, be sure to exclude
the request(s) from other managers to keep the requests from locking
and holding up any other processes.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
